MultiSite use model
There are different aspects of your MultiSite use model that affect the implementation and
deployment of a MultiSite
environment.
- Policies for a single code page in a clan
When you use Rational® ClearQuest, each client that accesses your Rational ClearQuest databases has its own code page. A code page specifies the set of characters that are valid in a given environment. With Rational ClearQuest, a code page defines the set of characters that are manipulated correctly on a particular client. MultiSite requires that all clients use the same code page. - multiutil commands on multiple computers
By default, only one computer per site is configured to administer schema repositories and user databases and use the multiutil commands. - Mastership changes of database objects
Your plan should state which replicas will master records and other objects. After you create the replicas in the family, you can change mastership of objects. - Synchronization
The main factors to consider when planning replica synchronization are method, scheduling, and pattern. - Backup strategy for databases
Perform regular backups of your vendor databases at all sites. If the database server machine crashes or you lose the database storage area, you can restore the database from the backup copy and use the replica restoration procedure to replace any missing operations. - Scrubbing parameters for replicas
When a command makes a change to a replica, an entry is recorded in the replica’s operation log. Also, when you export an update packet, an export_sync record is created for each target replica. These records are used by the recoverpacket command to reset a replica’s epoch number matrix. - Path names that contain spaces
On computers running Windows, if the path name of a receipt handler or a shipping order contains spaces, DOS short name resolution must be enabled for the file system on which the receipt handler or shipping order is located. This property is enabled by default. If this property is not enabled, the shipping server cannot invoke the receipt handler or process the shipping order.
Parent topic: Implementation planning