Cloning preparation
You must prepare source and target systems prior to cloning a web content repository.
- 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 would ideally have a separate physical Oracle database for each JCR repository. This will make it very simple to copy a JCR repository from one system to another.
If you do choose to store all of JCR repositories in a single database then it is best to use the same schema name for each, even if it will be difficult to tell which JCR instance each schema belongs too.
If you instead choose to name the schemas differently for each JCR repository instance, copying will be much more difficult. You would have to do a schema export and import first, then a second export of views and triggers into "sqlexport". Then modify the source schema name with the target schema name in the "sqlexport" and finally make another import of the "sqlexport" into the target schema. This is not the recommended approach.
Cloning a web content repository
|
|
| Apr 1, 2011 1:26:17 PM
|
|
|
|
});
|