The Replication function is used to automate the Archiver's export, import, and transfer functions.
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 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:
Archiver 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.This section covers these topics:
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.
Typical uses for the Replication function include:
Automatically exporting from one content server instance and importing to another content server instance to synchronize two Web sites.
Copying content automatically between two contribution/consumption servers.
Automatically moving certain documents from a contribution server to a higher-security content server.
Automatically moving old content to a storage location.
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.Several tasks are involved in managing the replication process, including setting up automatic exports, imports and transfers. This section provides information about these tasks.
To set up an automatic export:
Set up the export and run a manual export. See "Manually Exporting".
Open Archiver on the content server that content is to be exported from.
Open the archive collection.
Select the archive to export to automatically in the Current Archives list.
Click the Replication tab.
Click Edit.
The Registered Exporter Screen is displayed.
Select the Enable Automated Export check box.
Click Register.
The current collection is added to the Registered Exporters box.
Click OK.
Each revision that meets the export criteria will be exported to this archive when it is indexed. The batch file is removed as soon as each export is complete.
Note:
You can export expired revisions manually, but expired revisions do not get exported automatically.To set up an automatic import:
Set up the import and run a manual import. See "Import Process".
Open Archiver on the content server that the archive is to be imported to.
Open the archive collection.
Select the archive to import automatically in the Current Archives list.
Click the Replication tab.
Click Register Self.
You are prompted to confirm the action.
Click OK.
The selected archive will be imported automatically, about once per minute. All source batch files are removed as soon as each import is complete.
Note:
The Replication function does not import content types and user attributes.To set up an automatic transfer:
Set up the transfer and run a manual transfer. See "File Transfer Overview".
Open Archiver on the source content server.
Open the archive collection.
Select the source archive in the Current Archives list.
Click the Transfer To tab.
Click Edit.
The Transfer Options Screen is displayed.
Select the Is Transfer Automated check box.
Click OK.
Test the automatic transfer:
In the source content server, 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 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.
Unregistering an Importer from the Replication Tab
To disable an automatic import using this method:
Open the archive collection. See "Opening a Collection".
Select the archive in the Current Archives list.
Click the Replication tab.
Click Unregister.
Automatic importing from the selected archive is disabled.
Disabling a Registered Importer from the Automation for Instance Screen
To disable an automatic import using this method:
Open the archive collection. See "Opening a Collection".
From Options, select View Automation For Instance.
The Automation for Instance Screen is displayed.
Click the Importers tab.
Select the registered importer to delete.
Click Remove.
The registered importer is removed from the list.
To disable automatic export:
Open the archive collection. See "Opening a Collection".
Select the archive in the Current Archives list.
Click the Replication tab.
Click Edit.
The Registered Exporter Screen is displayed.
Clear the Enable Automated Export check box.
Click OK.
Automatic exporting of the selected archive is disabled.
To disable automatic transfer:
Open Archiver on the source content server.
Open the source archive collection. See "Opening a Collection".
Select the source archive in the Current Archives list.
Click the Transfer To tab.
Click Edit.
The Transfer Options Screen is displayed.
Clear the Is Transfer Automated check box.
Click OK.
Automatic transfer of the selected archive is disabled.
This section provides information about the methods to delete a registered exporter.
Deleting a Registered Exporter from the Replication Tab
To delete a registered exporter using this method:
Open the archive collection. See "Opening a Collection".
Select the archive in the Current Archives list.
Click the Replication tab.
Click Edit.
The Registered Exporter Screen is displayed.
Select the Enable Automated Export check box.
Select the content server instance to delete in the Registered Exporters list.
Click Remove.
The registered exporter is removed from the list.
Click OK.
Deleting a Registered Exporter from the Automation for Instance Screen
To delete a registered exporter using this method:
Open the archive collection. See "Opening a Collection".
From Options, select View Automation For Instance.
The Automation for Instance Screen is displayed.
Select the registered exporter to delete.
Click Remove.
The registered exporter is removed from the list.