Configuring TAS 7.x to support HCL VersionVault
About this task
- A TAS service (new or existing) to be used by HCL VersionVault
- Users with permissions to update HCL VersionVault information
- A volume for the storage of VOB data
- A volume for the storage of view data (optional)
- An authentication method for the service
After these values are submitted through the Configure VersionVault Service screen, a new TAS service is
created or an existing service is modified as specified. TAS volumes for VOB and, optionally, view
storage are created and at the paths specified in the VOB Storage Area Path
and View Storage Area Path attributes. These volumes are made
available as shares with names derived from the terminal leaf of the path. For example, a volume
created in /usr2/versionvault/vobdata would be shared as vobdata
. If the terminal leaf is not a
valid name for a Windows® share, the share is named VOB
if it is for VOB
storage and VIEW
if it is for view storage.
- preserve-whitespace is set to on.
- Browse master, null password login, and Windows 95 capabilities are disabled.
- The freespace report method is set to root.
- Opportunistic locks are disabled.
- Filename case is set to preserve.
- umask value is set to 002 (as opposed to the file service default umask 007).
- Username maps are enabled.
To configure a TAS service for HCL VersionVault, select CIFS Realm from the TAS Sphere menu; then click Configure VersionVault Service and complete the steps in the procedure that follows.