Before deploying MultiSite,
test your plan and perform a test run to ensure that your synchronization
and defect-tracking process are effective.
- Plan your deployment.
- Review MultiSite documentation.
- 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.
- Determine the appropriate data code page value for your replicas. See
the Administrator topics in Rational® ClearQuest® Help.
- Determine whether you need to validate and clean up your production database.
- Test your deployment.
- Set up a test bed environment with test database instances. See the Schema
Developer topics in Rational ClearQuest Help.
- Install MultiSite in
the test environment.
Remember that installing Rational ClearQuest MultiSite involves a Rational ClearQuest upgrade.
Note: All
user databases associated with a schema repository must be upgraded to the
same version of Rational ClearQuest before
you can begin using Rational ClearQuest MultiSite.
- 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.
- Review the results from the test and make any necessary workflow changes.
- Replicate the production database.
- Set up licensing for MultiSite at
the original site.
- Install MultiSite in
your production environment.
- Back up your databases.
- Apply schema changes to the production databases.
- Upgrade the production databases.
- Upgrade client machines.
- Activate the production database set.
- Replicate the production database set.
- Validate your MultiSite use
cases with the replicated databases.
- Make any necessary schema changes, upgrade the databases, and synchronize.
- 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.
- Set up licensing for MultiSite at
the new site. Install MultiSite on
the appropriate machines at the new site.
- Validate use cases at the new site.
- Set up bidirectional synchronization between the production replicas.
- Validate use cases with test data in production databases at the sites.
- Inform users that they can begin to use the new replica. Publish workflow
documentation to users at both 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.