Cloning preparation

Prepare the source and target systems before a web content repository is cloned.

• Disable both search and syndication in the source and target systems before you begin the cloning procedure.

• The source and target environments must be on the same version and fix level
• Ideally the source and target environments use the same LDAP

• If the target server already contains data:

  • To use this data later, take a backup of the target environment before cloning.

  • Note down the syndicator and subscriber setups. The syndication setup on the target environment is lost during the cloning process, and needs to be re-created.

  • Note down the library access control setup. Library access levels for target environment are lost during the cloning process, and need to be reapplied.

Oracle databases

When setting up an Oracle database for JCR, we must have a separate physical Oracle database for each JCR repository. This setup makes it easy to copy a JCR repository from one system to another. If we do choose to store all of the JCR repositories in a single database, then we must use different schema names for each system. HCL WebSphere Portal does not support more than one instance of HCL WebSphere Portal running against a single JCR database or schema.

Parent topic: How to clone a web content repository