Jump to main content
HCL Logo Product Documentation
Customer Support Software Academy Community Forums
DevOps Code ClearCase version 11.0.0
  • Overview
  • Installing
  • Upgrading and migrating
  • Administering
  • Developing
  • Managing change and releases
  • Integrating
  • Tutorials
  • Extending product function
  • Reference
  • Glossary
  1. Home
  2. Administering

    Learn how to administer the product.

  3. Administering DevOps Code ClearCase® MultiSite

    Learn to configure and manage the DevOps Code ClearCase® MultiSite and Rational® ClearQuest® MultiSite environments to support development activities at different locations.

  4. Administering replicas
  5. Managing mastership
  • Administering

    Learn how to administer the product.

    • Administering DevOps Code ClearCase®

      Learn about performing administrative tasks for a DevOps Code ClearCase® community including managing software licenses, user and group accounts, ClearCase server and client hosts, shared data, and the network that connects them.

    • Administering platforms for DevOps Code ClearCase®

      Learn how to perform DevOps Code ClearCase® administrative tasks on supported platforms.

    • Administering DevOps Code ClearCase® MultiSite

      Learn to configure and manage the DevOps Code ClearCase® MultiSite and Rational® ClearQuest® MultiSite environments to support development activities at different locations.

      • 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.

      • MultiSite operation
      • Implementation planning

        Before you install and use DevOps Code ClearCase®DevOps ClearQuest® MultiSite, you need to plan your implementation.

      • 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.

      • 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 DevOps Code ClearCase®. 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 ClearCase® 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.

        • 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 DevOps Code ClearCase® 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 a DevOps Code ClearCase® 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.

Managing mastership

This chapter describes how to manage the mastership of objects in a replica. Before reading this chapter, read the information in Independent development: Mastership Modification management in multiple replicas: Mastership.

  • Mastership commands for VOB objects
    You can use the command-line interface to manage mastership of VOB objects. On Windows®, many of the ClearCase® 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.

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.

Rate this topic


Comment on this topic
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences