Setting up an export view

An HCL VersionVault export view allows limited access to one or more VOBs by using standard NFS export facilities.

Each NFS export provides remote access to one VOB through a particular view. The following limitations apply when you use an export view to access a VOB:

  • You cannot check out or check in versions in the VOB. If you need to check out a file, you must perform a remote login to a VersionVault host.
  • Builds in the view do not perform build auditing, configuration lookup, or winkin. The builds do not create derived objects or config records. Any files created during the build are view-private objects.
    Note: You can use remote-shell techniques to overcome this limitation, so that the files built on a non-VersionVault host become derived objects. For more information, see Revising the build script.
  • You cannot reconfigure the view from the non-VersionVault host. If you need to reconfigure the view, you must perform a remote login to a VersionVault host.
    Note: If you modify an export view's config spec, all users who might currently have the view mounted for non-VersionVault access must unmount and remount the view. Remounting the view ensures access to the correct set of files as specified in the updated config spec.

For more information about setting up views and VOBs for export, see the Help for HCL VersionVault.

Note: Export views are used only for non-VersionVault access to VOBs. To make a view accessible on a remote host, use the startview or setview command on that host. An export view can be mounted on a VersionVault host, but never try to mount it on the dynamic-views root directory, /view.