About VOBs and versioned objects

Versioned Object Bases, or VOBs, are VersionVault repositories that are hosted on an HCL VersionVault server.

Resources controlled by HCL VersionVault are stored on a VersionVault server in repositories called versioned object bases, or VOBs. To access a VOB, you must work in a VersionVault view.

Note: To create a VOB, you must have access to HCL VersionVault administrative tools that run on the HCL VersionVault server. You cannot use the HCL VersionVault Explorer to create a VOB.

Versioned objects in a VOB

VOBs store file system objects and metadata.

File system objects are files and directories. These objects are stored as elements, each of which contains one or more versions. A file element contains one or more versions of a file. A directory element contains one or more versions of a directory, each of which can contain file elements and other directory elements.

A version is a specific revision of a file or directory. Versions of text files are distinguished by changes in their text. Versions of directories are distinguished by changes in their contents (to account for files and subdirectories that have been renamed, removed, or added).

VOB metadata

VOBs also store metadata such as comments, branches, labels, baselines and hyperlinks, which are associated with file system objects and their versions. The HCL VersionVault Explorer provides the VersionVault Navigator view and VersionVault properties view with which you can view and, in some cases, modify VOB metadata.

UCM Project VOBs

When UCM is in use, the HCL VersionVault Explorer has access to special VOBs called Project VOBs. These VOBs typically contain only the metadata that project managers use to define UCM projects. When a project VOB contains definitions of many projects, related projects are often grouped into folders. When you join a UCM project, the Join UCM Project wizard displays a list of Project VOBs so that you can select the appropriate Project VOB and project.