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.

Note: Non-VersionVault access is not supported on HCL VersionVault Windows hosts.
A host running Linux® or the UNIX system on which HCL VersionVault has not been installed can read VOB data from a VOB server running Linux® or the UNIX system. Typically, the technique is as follows:
  • A host running Linux® or the UNIX system and HCL VersionVault must export a view-extended pathname to the VOB mount point (for example, /view/exportvu/vobs/vegaproj). Edit the file /etc/exports.mvfs to specify this pathname.
  • One or more non-VersionVault hosts access the VOB through a view-extended pathname. For example, a host may have an entry in its file-system table that begins
    mars:/view/exportvu/vobs/vegaproj /usr/vega nfs ...

Restrictions on use

Non-VersionVault access carries several restrictions:
  • VOB access. Users on the non-VersionVault host can read, but cannot modify, data from VOBs on VOB server hosts running Linux® or the UNIX system that have been configured for non-VersionVault access. They are also restricted to using the element versions selected by the specified view; they cannot use version-extended or view-extended pathnames to access other versions of the VOB's elements.
  • Building. Although users cannot modify VOBs that are accessed through an export view, they can write to view-private storage. Users can modify these view-private files with an editor and build them, though not with clearmake. Files created by such builds do not become derived objects; they are view-private files, unless developers take steps to convert them. (For more information, see VersionVault Guide to Building Software.)
  • Because clearmake and other build-management tools do not run on the non-VersionVault host, configuration lookup and DO sharing are not available.