9.3 Planning Your Implementation

Before enabling requests for mastership, the project managers and administrators at the different sites must make these decisions:

• Which replicas must be enabled to allow requests for mastership. By default, a replica does not allow requests for mastership. You can enable one replica, multiple replicas, or all replicas in a VOB family.

• Which developers are authorized to request mastership. By default, no one is authorized. You can authorize individual developers, everyone in a specific group, everyone in a specific domain, or everyone in your network.

• The branch types and branches (if any) for which mastership requests are always denied. By default, requests are allowed.

Although you can enable requests for mastership in components, you cannot request mastership of a branch or branch type associated with a stream.

To Hide Request for Mastership Features

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

To use the setsite command to hide request for mastership features:

cleartool setsite rfm_gui_visibility=FALSE

To use ClearCase Administration Console to hide request for mastership features:

1. Navigate to the ClearCase Registry node in ClearCase Administration Console.

2. Click Action > Properties.

3. Click Help and follow the instructions in the online help.