Home
Administering
Learn how to administer the product.
Administering HCL VersionVault MultiSite
Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.
Administering replicas
Managing mastership
Working with type objects
When you create an attribute type, a hyperlink type, or a label type, you can make the type shared or unshared.
Converting a type object from unshared to shared
You can convert an unshared attribute type, hyperlink type, or label type to be shared.

Administering
Learn how to administer the product.
- Administering HCL VersionVault
  Learn about performing administrative tasks for an HCL VersionVault community including managing software licenses, user and group accounts, VersionVault server and client hosts, shared data, and the network that connects them.
- Administering platforms for HCL VersionVault
  Learn how to perform HCL VersionVault administrative tasks on supported platforms.
- Administering HCL VersionVault MultiSite
  Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.
  - Introduction
    HCL VersionVault MultiSite adds a powerful capability to HCL VersionVault. With MultiSite, developers at different locations can use the same HCL VersionVault versioned object base (VOB). For HCL VersionVault, each location (site) has its own copy (replica) of the VOB. 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.
  - MultiSite operation
  - Implementation planning
    Before you install and use HCL VersionVaultHCL Compass MultiSite, you need to plan your implementation.
  - 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.
  - 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.
  - Feature levels
    Feature levels allow different replica hosts in a VOB family to run different versions of HCL VersionVault. You can raise the feature level of either a single replica host or an entire VOB family.
  - Creating VOB replicas
    Before creating a replica, you must make decisions about branching, mastership, identities and permissions preservation, and method of packet delivery.
  - Replica synchronization
    Replica synchronization uses the same export-transport-import procedure that is used during replica creation.
  - Administering replicas
    - Using the CLI and native GUIs
    - Managing mastership
      - Mastership commands for VOB objects
        You can use the command-line interface to manage mastership of VOB objects. On Windows®, many of the VersionVault and MultiSite interfaces (for example, Check Out, the Properties Browser, Request for Mastership, and so on) contain extended functionality that also supports managing mastership.
      - Displaying mastership information for VOB objects
        Mastership information that can be displayed for VOB objects includes the master replica of an object, all objects mastered by a particular replica, the mastership changes for an object, and settings for mastership requests.
      - Assigning branch mastership during element creation
        By default, when you create an element in a replicated VOB, mastership of the branch main for that element is assigned to the replica that masters the branch type main. You can override this default behavior by explicitly assigning mastership of the main branch when you create the element.
      - Changing mastership of VOB objects
        When you create an object in a replicated VOB, your current replica is the new object’s master replica. To transfer mastership of the object to another replica, use the chmaster command or the Properties Browser (Windows®).
      - Fixing an accidental mastership change
        If a mastership change is made in a replica by mistake, you can fix the problem by following the steps that are described in this topic.
      - Working with type objects
        When you create an attribute type, a hyperlink type, or a label type, you can make the type shared or unshared.
        Creating a shared type object
        When you create a type object, you can specify that the type object is shared using the –shared option with the command that creates the object.
        Determining whether a type object is shared or unshared
        On Windows®, the Properties Browser displays the kind of mastership on the Mastership tab. You can also use the describe and lstype commands.
        Converting a type object from unshared to shared
        You can convert an unshared attribute type, hyperlink type, or label type to be shared.
    - Implementing requests for mastership
      To support development of VOB elements that cannot be merged, you can give developers the ability to request mastership of branches and branch types.
  - Using MultiSite for VOB backup and interoperability
    You can use HCL VersionVault MultiSite to back up a VOB and to provide access to VOBs in a heterogeneous network.
  - Troubleshooting MultiSite operations
    When you encounter a situation where running an HCL VersionVault MultiSite command produces an unexpected result, or produces a warning or error message, the information in this section can assist you in troubleshooting the problem.

Converting a type object from unshared to shared

You can convert an unshared attribute type, hyperlink type, or label type to be shared.

About this task

For example, if a project manager at the San Francisco site creates an unshared attribute type called TESTED_BY and the Bangalore project manager also needs to use it, you can convert the type to shared.

Note: You cannot convert a shared type object to unshared. To restrict instance creation of a type to one replica, you must remove all instances of the type, remove the type, and create a new unshared type.

For information about using the Properties Browser on Windows® to convert an unshared type object to a shared type object, see the MultiSite Help.

Procedure

Determine which replica masters the type object:


cleartool describe attype:TESTED_BY@/vobs/stage 
attribute type "TESTED_BY"
  created 03-Oct-00.10:29:06 by John Cole (jcole.user@goldengate)
  master replica: sanfran_hub@/vobs/dev
  instance mastership: unshared
...

At the master replica, enter a mkobjecttype –replace –shared command to replace the definition of the type, where object is one of the object types, such as at (attribute), hl (hyperlink), or lb (label).
For example, to replace the definition of an attribute type:
```
cleartool mkattype –replace –shared –c "needed at multiple sites" TESTED_BY
Replaced definition of attribute type "TESTED_BY".
```
Export and send an update packet to the other replicas that must use the type:
```
multitool syncreplica –export –fship bangalore boston_hub
...
```
At the receiving replicas, import the update packet:
```
multitool syncreplica –import –receive
...
```

At the receiving replicas, confirm that the type object is shared:

cleartool describe –fmt "%n\t%[type_mastership]p\n" 
attype:TESTED_BY@/vobs/dev 
TESTED_BY     shared

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.