Configuring bldeploy behavior

The logging and rollback files are stored in the Transactions directory during a Deploy Job. This directory is created during execution of the Deploy Job. You can also control access to the contents of (that is, the subdirectories within) this directory.

 To control permissions on the Transactions directory

To control permissions on the files and subdirectories in the Transactions directory on the target server

1. On the target server, create a file, tx_config.cfg in the Transactions directory (if the file does not exist).

2. Add the Umask property to the file. 
   For example, Umask=002
   The value of this property must be specified as a 3-digit octal number (0-7). For more information see, the following table.

   Important

   The FolderPermissions property is deprecated in TrueSight Server Automation 23.1. The Umask property takes precedence over the deprecated FolderPermissions property. The Umask property is applicable only for Linux and Unix servers. It is ignored on Windows servers.

3. Save the changes.

The following example shows permissions of the files and subdirectories in the Transactions directory when you include the property Umask=027 in the tx_config.cfg file.

 The following table contains some examples of Umask values that you may need, to control permissions on files and subdirectories in the Transactions directory.

To configure the time before restarting the target server

You can configure the time for which the deploy process must wait before the target server is restarted. If the process requires hours to complete running, the target server needs to wait for a long time before the restart. After this configured time is elapsed, any currently running processes are aborted and the target server is restarted. 

To configure this wait time for the target server, do the following:

1. On the target server, create a file, tx_config.cfg in the Transactions directory (if the file does not exist).
2. Add the OutOfBandRebootWaitTime property to the file. 
   For example, OutOfBandRebootWaitTime=700
   The value of this property is set in seconds. The default value is 900 seconds for Windows and UNIX systems.
3. Save the changes.

To configure sleep delay and retry attempts

Installation of some patches requires a system restart of the target server. Except for the Ignore item defined reboot setting, all other settings result in automatically restarting the target server as necessary. For more information about the restart settings, see Specifying-job-options.

After restarting the target server, TrueSight Server Automation waits for the post-restart actions to be completed on the target server. The post- restart actions include few registry modifications made as a result of the deployed patches.

The following additional actions are completed:

• After the restart of target server, TrueSight Server Automation remotely executes the main deploy program (bldeploy.exe) on the target server.
• After the restart of target server, Shavlik engine's deployment program (STDeploy.exe) is executed on the target server to complete the post-restart actions. Shavlik engine schedules a Windows scheduler task (with the trigger as At system startup) to run STDeploy.exe when there are any post-restart actions to be performed after deploying a patch.
• After the RSCD service is up on the target server, bldeploy.exe polls for the post-restart action events that are sent out by STDeploy.exe. Once bldeploy.exe encounters a Finished or Failed state for the post-restart actions, it returns back the status to the TrueSight Server Automation console.

When TrueSight Server Automation waits, it searches for the terminating state (Finished or Failed) in the deployment events file for the specific patch. When it does not find either of the two states, it sleeps for a specific duration and re-tries after some time. This sleep duration and the number of retry attempts are configurable. To configure these values, create a file tx_config.cfg in the Transactions folder on the target server. Include the following properties and specify integer values to the keys within this configuration file: