Cloning preparation

You must prepare your source and target systems prior to cloning a web content repository.

  • Managed pages must be disabled on both the source and target environments if virtual portals are in use before beginning the cloning procedure.
  • The source and target environments must be on the same version and fix level
  • Ideally the source and target environments will use the same LDAP
  • If the target server already contains data:
    • If you need to use this data later, ensure you take a backup of the target environment before cloning.
    • Note down the syndicator and subscriber setups. The syndication setup on the target environment will be lost during the cloning process, and will need to be recreated.
    • Note down the library access control setup. Library access levels for target environment will be lost during the cloning process, and will need to be reapplied.

Oracle Considerations

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