The logging and rollback files that are stored in the Transactions directory during a Deploy Job can get very large. Using server properties, you can store deploy transaction information at a location on a target server other than the RSCD agent's default location. You accomplish this by setting a value for the
TRANSACTIONS_DIR server property.
When you use this procedure, the parent directory for the location that you specify must already exist. For example, if the location that you specify for
TRANSACTIONS_DIR is /tmp/Transactions, then the /tmp directory must already exist, and the Transactions directory is created during execution of the Deploy Job. In addition, the path that you specify must not contain any space characters.
If the alternate location is on a UNIX server, the Deploy Job must have appropriate permissions to create sub-directories in that location.
When you perform this procedure, BMC Server Automation continues to use the default Transactions directory for some files, which are small and typically transient.
When you use the clean-up utility to remove unwanted files on target servers, the clean-up utility uses the current location of the Transactions directory. Clean-up does not affect any previous locations for the Transactions directory.
To define an alternate location for storing a target server's transaction information, specify a value for the
TRANSACTIONS_DIR server property. As the value for this property, specify a local path to an alternate location on the target server. Ensure that no space characters appear in any of the names of directories along this path.
For details on how to define a property value, see Setting values for system object properties.
You can also control access to the contents of (that is, the subdirectories within) the Transactions directory. To do so, create a file named tx_config.cfg in the Transactions folder, and include the
FolderPermissions property within this configuration file. For example: