Click Remove in the Transfer Destination section. Click Yes. Select Options, and then click View Automation For Instance. Click the Transfers tab. Click Remove.

Managing System Migration and Archiving 8-51

5. Click Edit in the Transfer Destination section.

The Archive Collections Screen is displayed. 6. Select the collection that contains the target archive. 7. Select the target archive.

8. Click OK.

8.6.4.5 Initiating a Manual Transfer

To transfer content manually:

1. Open Archiver on the source Oracle Content Server instance.

2. Open the archive collection that contains the source archive. See

Section 8.3.3.1, Opening a Collection.

3. Select the source archive in the Current Archives list.

4. Select Actions, and then click Transfer.

The transfer process is initiated, and the status bar at the bottom of the Archiver screen displays progress messages.

8.6.4.6 Deleting a Transfer

This section provides information about the methods to delete a transfer. Deleting a Transfer from the Transfer To Tab: 1. Open the archive collection that contains the source archive. See Section 8.3.3.1, Opening a Collection. 2. Select the source archive in the Current Archives list. 3. Click the Main Archiver Transfer Screen .

4. Click Remove in the Transfer Destination section.

You are prompted to confirm the action.

5. Click Yes.

Deleting an Automated Transfer from the Automation for Instances Screen: 1. Open the archive collection. See Section 8.3.3.1, Opening a Collection.

2. Select Options, and then click View Automation For Instance.

The Automation Screen is displayed.

3. Click the Transfers tab.

4. Select the automated transfer to delete.

5. Click Remove.

The automated transfer is removed from the list. Note: The target archive must be identified as targetable. See Section 8.6.4.2, Making an Archive Targetable. 8-52 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server

8.7 Replicating Files

The Replication function is used to automate the Archivers export, import, and transfer functions. ■ Section 8.7.1, Introduction to Replication ■ Section 8.7.2, Managing Replication

8.7.1 Introduction to Replication

If you are automating an import using replication, each batch file is removed as soon as the automatic import is complete. However, you can view the archiving results by preparing an Archive History report using the Web Layout Editor. If you are replicating files to a contribution server, you should map the Security Group andor Account field so that users have only Read permission to the imported files. Otherwise, changed files in the importing instance could be overwritten by exported files during a later replication cycle. For performance reasons, replication is not recommended for large archives approximately 20,000 files or more. Export and import of large archives should be run manually, during periods of non-peak usage if possible. This section covers these topics: ■ Section 8.7.1.1, Single Revision Replications ■ Section 8.7.1.2, Replication Uses ■ Section 8.7.1.3, Replication Methods

8.7.1.1 Single Revision Replications

When using the Single Revision Replication option on the Edit Export Query Content Screen , be aware of the following considerations: ■ If the new document matches the archiver query on checkin, it is archived. If it does not match the query, nothing happens. ■ If a document has multiple revisions and the most recent matching revision is deleted or updated so it no longer matches the query, the next most recent matching revision of that document is replicated. If no revisions match the query, that document is deleted through replication. ■ If a system A is replicating to system B and the Single Revision Replication option is used, system B will at any given time only have one revision of each document. The revLabel of each revision is 1, no matter what the revLabel was on the document that was replicated. This archiving option allows an administrator to create a staging system and a production system. The staging system can archive all documents that have a specific metadata field set to 1. The production system will always have the most recent revision of each document that has this metadata flag set. Setting this flag to 0 on the staging system removes it from the production system and rolls it back to the next most recent revision with that metadata field set to 1. Caution: Archiver cannot be used to move or copy data between two instances that share the same Oracle Content Server instance name IDC_Name. To do so corrupts the data on the target system.