Oracle® Universal Content Management 10g Release 4 (10.1.4) |
Contents |
Index |
Previous |
Next |
Site Studio Designer Guide > Replicating Your Site > Creating the Import and Exp... > Setting Up the Import Archi...
An import archive resides on the target content server. During replication, content from an export archive (residing on a source server) is copied into the import archive. The import archive then copies the content to the target content server, thus completing the replication process.
After you set up a provider connection (see Setting Up an Outgoing Provider on the Source Server), you're ready to create an import archive. You create (or edit) an import archive on the Manage Site Replication page on the target server.
To set up an import archive, perform these tasks:
Log on to the target content server as an administrator. On the main menu, select Administration, then Site Studio Administration, and then Manage Site Replication.
Or, if you are updating an existing import archive, highlight it in the list of archives and click Change Settings.
Enter a name for the archive beside Archive Name (the name appears in the list of available archives on the Manage Site Replication page).
The archive name should not contain spaces or special characters.
Enter a description of the archive beside Archive Description.
To retain content that contributors assign to each region on the target site, check Retain switched region content on target server during import.
These are the areas where a contributor has switched the data file or native document.
To retain content that contributors edit in each region on the target site, check Retain region content on target server during import.
This prevents any data files and native documents from being copied from the source server to the target server and potentially overwriting files edited by the contributor.
Click Add Archive.
Or, if you are updating an existing import archive, click Update.
You would typically choose to retain region content and switched region content if you're replicating from a development server (source) to a contribution server (target) because in that scenario you want to preserve the changes made by a contributor.
You would likely disable (uncheck) these options if you're replicating from a contribution server (source) to a consumption server (target) because in that scenario you want to overwrite anything that has changed on the consumption server.
The next step is to create an export archive (see Setting Up the Export Archive on the Source Server).