This chapter covers the following topics:
If you are automating the import of WebCenter Content files using replication, each batch file is removed as soon as the automatic import is complete. You can view the archiving results by preparing an Archive History report using the Web Layout Editor. For information on the editor, see Developing with Oracle WebCenter Content.
If you are replicating files to a contribution server, you should map the Security Group and/or 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.
Caution:
The Archiver utility cannot be used to move or copy data between two instances that share the same Content Server instance name (IDC_Name). To do so corrupts the data on the target system.
When Archiver automatic replication is configured between instances of WebCenter Content, every action is replicated between environments: Check in, Update, and Delete. For information on preventing Archiver from replicating Delete actions, see the "Preventing Deletes from Replicating In Archiver" blog.
This section covers these topics:
Typical uses for the Replication function include:
Automatically exporting content from one Content Server instance and importing to another Content Server instance to synchronize two websites.
Copying content automatically between two contribution/consumption servers.
Automatically moving certain documents from a contribution server to a higher-security Content Server instance.
Automatically moving old content to a storage location.
Note:
The Replication function does not import content types and user attributes.
You can automate Archiver functions in the following ways:
Automatic Export: Export to a local archive is initiated automatically whenever a content item that meets the export criteria is indexed.
Automatic Import: Import from a local archive is initiated automatically, about once per minute.
Automatic Transfer: Moving archive files to a different Content Server instance over sockets is initiated automatically whenever the source archive is updated.
Note:
You can export expired revisions manually, but expired revisions do not get exported automatically.
When using the Single Revision Replication option on the Edit Export Query (Content) window, be aware of the following considerations:
If the new document matches the archiver query on check-in, 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.
Several tasks are involved in managing the replication process, including setting up automatic exports, imports and transfers. This section provides information about replication tasks.
To set up an automatic transfer:
Set up the transfer and run a manual transfer. See Introduction to Transferring Files.
Open Archiver on the source Content Server instance.
Open the archive collection.
Select the source archive in the Current Archives list.
Click the Transfer To tab.
Click Edit.
In the Transfer Options window, select Is Transfer Automated.
Click OK.
Test the automatic transfer:
In the source Content Server instance, check in a new document that meets the export criteria.
If the export is automated, wait until automated export occurs after indexing. Otherwise, export the source archive manually. The archive should be transferred to the target Content Server instance within a few minutes.
Note:
The Replication function does not import content types and user attributes.
This section provides information about the methods to disable an automatic import.