Installing HCL VersionVault to support Solaris zones
Before installing HCL VersionVault, configure the zones on your system.
Before you begin
- Configure the Solaris zones. For instructions, refer to Oracle product documentation (http://www.oracle.com/index.html).
- If VersionVault is to be installed on a branded zone, verify that the intended VersionVault version supports the operating systems of both the branded zone and the global zone.
- For each zoned host, determine the number of global and non-global zones that are expected to run the MVFS.
- The procedure below describes use of the IBM® Installation Manager GUI. However, Installation Manager also supports a command-line interface and a "silent" installation, which reads inputs from a response file (refer to the Installation Manager documentation).
Important: Choose the same path for the install location of VersionVault on both the global and non-global zones.
Procedure
- Ensure that the Installation Manager saves host-specific data to a location that is not shared with other systems.
- Install HCL VersionVault on the global zone. If you intend to support dynamic views on non-global zones, do not select the VersionVault Server-only Installation option in this step. (If you select VersionVault Server-only Installation, the MVFS will not be installed and the zones will not support dynamic views.)
- If you have installed the MVFS in the global zone, log in as root and use the cleartool setcache -mvfs expected_zone_count command to specify the number of zones that are to run the MVFS. Refer to the setcache reference page for information on specifying the expected number of zones.
- For each non-global zone, repeat step 1.
- Install VersionVault on each non-global zone.