Overview of deployment tasks

1. Review MultiSite documentation.
2. Create a MultiSite Workflow document that describes the changes and policies that will be enforced.

   This document should describe the mastership policies, the replication strategy, the synchronization method, pattern, and schedule, and the workflow for users who perform tasks in a replicated environment. The document should also describe the changes necessary to implement MultiSite; for example, adding the mastership field to your schema, modifying existing hooks, and creating hooks that automate transfer of mastership. Representatives of the user community should review this document.

3. Determine the appropriate data code page value for your replicas. See the Administrator topics in HCL Compass Help.
4. Determine whether you need to validate and clean up your production database.

1. Set up a test bed environment with test database instances. See the Schema Developer topics in HCL Compass Help.
2. Install MultiSite in the test environment.

   Remember that installing HCL Compass MultiSite involves a HCL Compass upgrade.

   Note: All user databases associated with a schema repository must be upgraded to the same version of HCL Compass before you can begin using HCL Compass MultiSite.
3. Replicate the test database, set up synchronization, make any necessary schema changes, and test your process. Be sure to test your own backup and recovery processes on the replica.
4. Review the results from the test and make any necessary workflow changes.

1. Set up licensing for MultiSite at the original site.
2. Install MultiSite in your production environment.
3. Back up your databases.
4. Apply schema changes to the production databases.
5. Upgrade the production databases.
6. Upgrade client machines.
7. Activate the production database set.
8. Replicate the production database set.
9. Validate your MultiSite use cases with the replicated databases.
10. Make any necessary schema changes, upgrade the databases, and synchronize.
11. Set up unidirectional synchronization from the original replica to the new one. Test your synchronization scripts to ensure that synchronization is occurring correctly. Do not let users access the new replica. At this point, the new replica can be removed without loss of data if problems develop.
12. Set up licensing for MultiSite at the new site. Install MultiSite on the appropriate machines at the new site.
13. Validate use cases at the new site.
14. Set up bidirectional synchronization between the production replicas.
15. Validate use cases with test data in production databases at the sites.

The new workflow rules are now in effect. Set up a Web server for the new database replica to provide remote access for personnel at other sites.