Home
Administering
Learn how to administer the product.
Administering HCL VersionVault
Learn about performing administrative tasks for an HCL VersionVault community including managing software licenses, user and group accounts, VersionVault server and client hosts, shared data, and the network that connects them.
Configuring non-VersionVault access on Linux® or the UNIX system
You can configure an HCL VersionVault host running Linux® or the UNIX system to support access to VOBs and dynamic views from computers that do not run HCL VersionVault.
Setting up an export view for non-VersionVault access
An export view for non-VersionVault access exports a view-extended pathname to the VOB mount point.
Exporting multiple VOBs

Exporting multiple VOBs

About this task

If you put each VOB and its export view on the same host, developers working on a non-VersionVault host are likely to access several export views at the same time. For example, to provide non-VersionVault access to three VOBs located on three different hosts, each of which had its own export view, you would need to create NFS mount table entries such as these on the non-VersionVault host:

saturn:/view/beta/vobs/proj /vobs/proj nfs rw,hard 0 0 
neptune:/view/exp_vu/vobs/proj_aux /vobs/proj_aux nfs rw,hard 0 0 
pluto:/view/archive_vu/vstore/tools /vobs/tools nfs rw,hard 0 0

The three VOBs can be accessed on the non-VersionVault host as subdirectories of /vobs. For each VOB and view pair, HCL VersionVault operations as checkout and checkin must be made in the appropriate export view. Other operations, such as building and debugging, do not need to reference any view.