Skip Headers
Oracle® Universal Content Management
10g Release 4 (10.1.4)
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next

Configuring the Target Server for Replication

The Site Studio replication feature copies your site from one content server to another. It it does not, however, copy the content server environment from the source server to the target server.

Before you replicate the site, you must make sure the content server environment on the target server is set up the same way as the source server (at least the parts used by your site). If you skip this step, your Web site experiences problems during the replication process.

The steps to reproduce the content server environment varies from one organization to another and from one Web site to another. As such, we offer these general guidelines.

To manually configure the target server environment, perform these tasks:

  1. Recreate the metadata model used on the source server. This includes all custom metadata fields and new file formats. This metadata is required for your site to operate properly. For example, checking in files generally relies on your metadata settings, and certain features on your site rely on custom metadata fields.

  2. Reinstall all components used by your site on the source server. This includes Dynamic Converter (for native documents) and Check Out and Open (to check native documents out using the contribution icon). For more information in system requirements, see the Site Studio Installation Guide.

  3. Recreate unmanaged resources. This includes custom ActiveX controls or JSP objects that are used by your site.

  4. Recreate any additional configuration settings that you have introduced to the server. This includes anything that has changed the behavior of the server.

If you run version 7.5 or later of Content Server (including 10gR3), then you may be able to use the Content Server Configuration Migration Utility to replicate the content server environment. The next step is to set up an outgoing provider (see Setting Up an Outgoing Provider on the Source Server).