Welcome
Administering
Learn how to administer the product.
Administering Rational® ClearQuest® Multisite
Administering Rational® ClearQuest® Multisite
Replica synchronization
Replica synchronization uses the same export-transport-import procedure that is used during replica creation.
Automated synchronization
To automate the phases of synchronization, you can use cron (Linux™ and the UNIX™ system) or at (Windows™) jobs or a third-party scheduling tool.

IBM ClearQuest 10.0.9
Overview
Learn general information about the product.
Installing
Learn how to install the product.
Upgrading and migrating
Learn how to upgrade and migrate data for the product.
Administering
Learn how to administer the product.
- Administering Rational® ClearQuest®
  Learn how to administer the Rational® ClearQuest®.
- Administering Rational® ClearQuest® Web
  This section discusses how to administer Rational® ClearQuest® Web.
- Administering Rational® ClearQuest® Multisite
  Administering Rational® ClearQuest® Multisite
  - Introduction
    and Rational® ClearQuest® MultiSite add a powerful capability to and Rational ClearQuest. With MultiSite, developers at different locations can use the same versioned object base (VOB) or Rational ClearQuest database set (a schema repository and its associated user databases). For Rational ClearQuest, each location has its own copies, or replicas, of the schema repository and user databases. At any time, changes made in one replica can be sent in update packets to other replicas. You can manage replicas by using the command-line tools.
  - Implementation planning
    Before you install and use DevOps Code ClearCase®DevOps ClearQuest® MultiSite, you need to plan your implementation.
  - Packet transportation methods and configuration
    The method you choose for transporting packets between replicas depends on connectivity. If your replicas do not have IP connectivity, you must use a file-based transport method. If your replicas have connectivity, you can use the store-and-forward facility.
  - Database replica creation
    Creating your database replicas requires careful planning and consideration part of which involves making decisions about mastership and methods of packet delivery.
  - Replica synchronization
    Replica synchronization uses the same export-transport-import procedure that is used during replica creation.
    - Manual synchronization
      You can manually synchronize replicas by entering explicit syncreplica commands.
    - Automated synchronization
      To automate the phases of synchronization, you can use cron (Linux™ and the UNIX™ system) or at (Windows™) jobs or a third-party scheduling tool.
    - Assumption of successful synchronization
      The export and import phases of synchronization always occur at different times. A sending replica does not require acknowledgment from a sibling replica that a packet has been received and processed successfully. Instead, the sending replica assumes success. This assumption enables an optimization: subsequent updates from a replica do not include the data sent in previous updates.
    - Schema updates from imported packets
      Packets exported from the working schema repository may include new schema revisions that require database upgrades at other sites. In this case, the syncreplica –import command cannot finish its process until the user database replica is upgraded to the new schema version.
    - Synchronization of multiple user database families with msimportauto.bat
      In certain circumstances, successfully importing of user database update packets may depend on information contained in other user database packets. If your schema repository is associated with multiple user database families, import may fail if the packets are not replayed in the order they were generated.
  - Database replicas administration
    Sustaining a smoothly functioning MultiSite environment requires dedicated administration. Many administrative processes can drastically change your environment and require careful consideration and planning.
  - Mastership management
    The management of mastership affects how database objects are accessed and manipulated by users in your MultiSite environment. Mastership management is an ongoing process as new objects are entered into the database and users' requirements change.
  - Troubleshoot MultiSite operations
    There are common situations in which running a Rational® ClearQuest® MultiSite command produces an unexpected result, sometimes accompanied by a warning or error message.
  - MultiSite command set
    This section summarizes the commands for DevOps ClearCase® MultiSite and DevOps ClearCase that display DevOps Code ClearCase MultiSite information. There are a series of MultiSite commands and API functions that display or modify MultiSite information.
Reporting
Learn how to generate reports for the product.
Developing
Learn how to develop schemas by using the Rational® ClearQuest® Designer.
Managing change and releases
Learn how to manage change and release in the product.
Integrating
You can integrate Rational® ClearQuest® with other software by adding packages to existing schema.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.
Tutorials

Automated synchronization

To automate the phases of synchronization, you can use cron (Linux™ and the UNIX™ system) or at (Windows™) jobs or a third-party scheduling tool.

You can specify a receipt handler in the shipping.conf file (Linux™ and the UNIX™ system) or MultiSite Control Panel (Windows™) to automate the import phase.

On Windows™, you can use the script cquest-home-dir\msimportauto.bat as a template.

automated synchronization with a task scheduler

When you use a scheduling utility, such as the DevOps Code ClearCase® scheduler, to execute Rational® ClearQuest® MultiSite commands, the scheduler process must have access to the Rational® ClearQuest® environment. In Windows™, the user who runs the DevOps Code ClearCase® scheduler must also create the connection to the Rational® ClearQuest® schema and user database for performing the scheduled operations.

On computers running Linux™ or the UNIX™ system, the scheduled task must set up the Rational® ClearQuest® environment by running the cq_setup script prior to running the multiutil subcommands.

For more information, see "Using the DevOps Code ClearCase® scheduler" in the MultiSite Administrator's Guide.