Configuring the File Vault
To configure the Configuration Management file vault on an Integrity Lifecycle Manager server:
1. Stop the Integrity Lifecycle Manager server.
2. Enable vault support by modifying the following property in the si.properties file under IntegrityServerinstalldir/config/properties:
si.vault.enable=true
When set to true, this property enables support for file vaulting on the Integrity Lifecycle Manager server. When set to false, file vaulting is disabled.
3. Specify the vault location for this Integrity Lifecycle Manager server instance. Modify the following property in the si.properties file under IntegrityServerinstalldir/config/properties:
si.vault.location=root directory of the Configuration Management file vault
For example:
si.vault.location=D:/FileVaultDirectory
|
|
The file vault location specified must be a directory other than the Integrity Lifecycle Manager server installation directory.
The Integrity Lifecycle Manager server requires read/write access to the file vault directory. Ensure that the account that is used to run the Integrity Lifecycle Manager server has read/write access.
The path format used depends on which operating system the Integrity Lifecycle Manager server is running on. If the server is running on Linux or some other form of Unix, the vault path must be a Unix-style path. On a machine running Windows, the vault path must be a Windows-style path, a direct UNC path, or a mapped drive for a network path. Forward slashes “\” are supported but they must be escaped with a second forward slash “\\”.
|
4. Ensure that the vault location directory exists on the file system before starting the Integrity Lifecycle Manager server. If the vault location does not exist, the Integrity Lifecycle Manager server will not start.
5. Start the Integrity Lifecycle Manager server. At startup, Integrity Lifecycle Manager performs a check of vault content to ensure that it is synchronized with the database. The sanity check validates that the latest vaulted revision content exists in the specified vault location. If the server startup check fails and the Integrity Lifecycle Manager server fails to start, an administrator can bypass the server startup check to start the server. Modify the following property in the si.properties file under IntegrityServerinstalldir/config/properties: si.vault.bypassVaultSanityChecksUponStartup=true
When set to true, the server startup check is bypassed on startup. By default, this property is set to false.
|
|
When the server startup check fails, the server failing to start can be an indication of a more serious issue, such as file vault corruption. PTC strongly recommends that you restore the contents of the file vault from a viable backup before attempting to bypass the failure and start the server. For more information, see Backing Up and Restoring File Vaults. |
6. In the Integrity Lifecycle Manager administration client, enable the Use File Vault for Store by Reference Member Revisions configuration management policy. Revision data is not moved to the file vault until this policy is set globally or is set on specific configuration management projects. For more information on setting configuration management policies, see the topic “To set general policies” in the Integrity Lifecycle Manager Server Administration Guide. For more information on this policy, see the topic “General Policy Options” in the Integrity Lifecycle Manager Server Administration Guide.
Once the Integrity Lifecycle Manager server is started, all newly created, eligible revisions are added to the file vault location for all or specific configuration management projects.
