Home
Administering
Learn how to administer the product.
Administering HCL Compass Multisite
Administering HCL Compass Multisite
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.
Moving or renaming a synchronization server
You can change the synchronization server associated with a replica when, for example, the machine you are using has a hardware failure, or you must rename the existing synchronization server. You must update the properties of the replica associated with that host so that the store-and-forward facility can determine how to route updates to the replicas.

Administering
Learn how to administer the product.
- Administering HCL Compass
  Learn how to administer the HCL Compass.
- Administering HCL Compass Web
  This section discusses how to administer HCL Compass Web.
- Administering HCL Compass Multisite
  Administering HCL Compass Multisite
  - Introduction
    HCL VersionVault MultiSiteHCL Compass MultiSite adds a powerful capability to HCL VersionVaultHCL Compass. With MultiSite, developers at different locations can use the same HCL VersionVault versioned object base (VOB) HCL Compass database set (a schema repository and its associated user databases). For HCL VersionVault, each location (site) has its own copy (replica) of the VOB. For HCL Compass, 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 HCL VersionVaultHCL Compass 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.
  - 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.
    - Displaying properties of a replica
      The lsreplica command lists information about a replica.
    - Rename replicas and sites
      To change the name of a database replica, you must delete the replica and create a new replica using a different name. Renaming sites requires planning and coordination between sites in the clan, particularly the site that is designated for renaming and the working master site. Synchronize all sites before renaming.
    - Moving a replica or changing vendor database software
      Moving a replica or changing vendor database software involves the same tasks that must be performed on a non-replicated HCL Compass database set. The additional step for replicated database sets is to synchronize all sibling replicas once the move process is complete.
    - Moving or renaming a synchronization server
      You can change the synchronization server associated with a replica when, for example, the machine you are using has a hardware failure, or you must rename the existing synchronization server. You must update the properties of the replica associated with that host so that the store-and-forward facility can determine how to route updates to the replicas.
    - Replica deletion
      To remove a replica, you must complete all the necessary steps; if you do not, synchronization and mastership problems can occur in other replicas in the family.
    - Upgrading a schema version
      This procedure describes how to introduce a new schema version to a HCL Compass MultiSite clan by synchronizing the new schema to all sites before upgrading any user databases. You must follow this procedure to help ensure a stable and reliable HCL Compass MultiSite environment.
    - Updating database subscriptions after replicating a database
      When you add a new user database at the working schema repository site, replicate the new user database before subscribing users to it.
    - Database record ID management
      Database record IDs are allocated to replicas in ID blocks. The range of record IDs (for both stateful and stateless records) is broken into blocks that are assigned to each replica to be allocated locally within those replicas.
  - 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 HCL Compass MultiSite command produces an unexpected result, sometimes accompanied by a warning or error message.
  - MultiSite command set
    This section summarizes the commands for HCL VersionVault MultiSite and HCL VersionVault that display HCL VersionVault MultiSite information. There are a series of MultiSite commands and API functions that display or modify MultiSite information.

Moving or renaming a synchronization server

You can change the synchronization server associated with a replica when, for example, the machine you are using has a hardware failure, or you must rename the existing synchronization server. You must update the properties of the replica associated with that host so that the store-and-forward facility can determine how to route updates to the replicas.

About this task

To move the synchronization server:

Install the HCL Shipping Server on the new machine.

Use the chreplica command to associate the new synchronization server with the replica.

multiutil chreplica -clan telecomm -site bangalore -user kumar -password secret -host server3 bangalore

If you automated the synchronization process on the old synchronization server, you must set up synchronization export and import scripts on the new server.
If you use routing hops, update the host name in the shipping.conf file (Linux™ and the UNIX™ system) or MultiSite Control Panel ( Windows™).
Export update packets to all sibling replicas.