Welcome
Administering
Learn how to administer the product.
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.
Administering replicas
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.
Planning your implementation
Before enabling requests for mastership, the project managers and administrators at the different sites must make specific planning decisions about whether requests for mastership are allowed for specific replicas, branches, and branch types, and which developers are authorized to make requests for mastership.
Hiding request for mastership features
If you do not implement requests for mastership at particular sites, you can hide request for mastership features in the graphical interface for DevOps Code ClearCase® MultiSite on Windows®. The display of these features is controlled by the site-wide setting rfm_gui_visibility.

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 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
    DevOps Code ClearCase® MultiSite and add a powerful capability to DevOps Code ClearCase and . With MultiSite, developers at different locations can use the same DevOps Code ClearCase versioned object base (VOB) or . For DevOps Code ClearCase, 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 DevOps Code ClearCase® 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.
  - 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
    - 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.
      - Overview of a request for mastership
        When a developer requests mastership of a branch, the branch's mastership is transferred to the developer's current replica. When a developer requests mastership of a branch type, mastership of the branch type, along with mastership of all the instances of the branch type that have default mastership, is transferred to the developer's current replica.
      - Requirements and recommendations
        In order to enable requests for mastership in one or more replicas and for those requests to be handled efficiently, specific conditions must be met.
      - Planning your implementation
        Before enabling requests for mastership, the project managers and administrators at the different sites must make specific planning decisions about whether requests for mastership are allowed for specific replicas, branches, and branch types, and which developers are authorized to make requests for mastership.
        Hiding request for mastership features
        If you do not implement requests for mastership at particular sites, you can hide request for mastership features in the graphical interface for DevOps Code ClearCase® MultiSite on Windows®. The display of these features is controlled by the site-wide setting rfm_gui_visibility.
      - Enabling requests for mastership
        To enable requests for mastership for the replicas in a VOB family, you must verify the feature level, add developers to the access control list, specify any objects for which you want to deny requests, and then enable requests at the replica level for each replica in the VOB family.
      - Enabling synchronous requests for mastership (SRFM)
        Synchronous request for mastership (SRFM) means that a request for mastership of a branch is issued synchronously with a checkout of that remotely mastered branch, providing a writable branch before branch mastership is acquired.
      - Customizing synchronization updates for mastership requests
        After a mastership request is processed at the master replica, sync_export_list is invoked to export an update packet to the replica at the requester's site. You can customize the export by specifying one or more of the options and arguments that are valid for sync_export_list, except for –replicas, which is always the replica at the requester's site.
      - Displaying mastership request settings
        To display the mastership request setting for a replica, branch type, or branch, use the describe command or the Mastership page in the Properties Browser (Windows®). These settings are also displayed in the Request Mastership Window on Windows.
      - Troubleshooting mastership requests
        MultiSite provides commands you can use to troubleshoot failed mastership requests. When a request fails, the error messages provide an indication of what happened and what can be done to fix the problem.
      - Serial development scenario
        This is an example of serial development using requests for mastership.
  - 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.
Developing
Learn how to develop software with DevOps Code ClearCase® and ClearCase Remote Client.
Managing change and releases
Learn how to manage change and release in the product.
Integrating
Learn how to integrate DevOps Code ClearCase® with other products.
Tutorials
Complete tutorials with specific learning objectives for the product.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.
Glossary

Hiding request for mastership features

If you do not implement requests for mastership at particular sites, you can hide request for mastership features in the graphical interface for DevOps Code ClearCase® MultiSite on Windows®. The display of these features is controlled by the site-wide setting rfm_gui_visibility.

About this task

Procedure

To use the setsite command to hide request for mastership features:
```
cleartool setsite rfm_gui_visibility=FALSE
```
To use the ClearCase® Administration Console to hide request for mastership features:
1. Navigate to the ClearCase Registry node in the ClearCase® Administration Console.
2. Click Action > Properties.
3. Click Help and follow the instructions.