Understanding the role of the administrative VOB

An administrative VOB stores global type definitions. VOBs that are joined to the administrative VOB with AdminVOB hyperlinks share the same type definitions without having to define them in each VOB. For example, you can define element types, attribute types, hyperlink types, and so on in an administrative VOB. Any VOB linked to that administrative VOB can then use those type definitions to make elements, attributes, and hyperlinks.

If you currently use an administrative VOB, you can associate it with your PVOB by creating an AdminVOB hyperlink between the PVOB and the administrative VOB. On Windows® computers, the VOB Creation Wizard creates the AdminVOB hyperlink for you. On UNIX® and Linux workstations, use the cleartool mkhlink command to create the AdminVOB hyperlink. Thereafter, when you create components, AdminVOB hyperlinks are created between the VOBs that store the components’ root directories and the administrative VOB. These hyperlinks enable the components to use the administrative VOB’s global type definitions.

If you do not currently use an administrative VOB, do not create one. When you create components, AdminVOB hyperlinks are made between the VOBs that store the component root directories and the PVOB, and the PVOB assumes the role of administrative VOB.

For details on administrative VOBs and global types, see the DevOps Code ClearCase Administrator's Guide.