Deployment options

<OS>_DONOT _COPY_TO_UNDO

Determines whether the payload files should be copied to an Undo directory on a target server. Values entered here correspond to the check box, Do NOT copy source to undo directory during deployment, which is located in the Add Software dialog. Choose either:

• True: (Default) Payload files copied to an Undo directory on the target server.
• False: Payload files are not copied to an Undo directory on the target server.

<OS>_ALLOW_ROLLBACK

Controls Job Deployment behavior by determining whether rollback is allowed for the BLPackage being deployed. Values entered here correspond to the Commit Optionsdefined as part of the New Deploy Job wizard definition. Choose either:

• True: Rollback is permitted and requisite files are stored on the target server for later use.
• False (Default): Rollback is not permitted and no files are saved.

<OS>_AUTO_ROLLBACK

Determines whether a deployed BLPackage can be rolled back automatically when Job Deployment fails. Choose either:

• True: The deployed BLPackage is rolled back.
• False (the default): The deployed BLPackage is not rolled back. Patches that are successfully applied remain in the applied state.

<OS>_PRESERVE_STAGING_AREA

Defines what happens to the files pertaining to job deployment upon job completion. Choose either:

• True: All files relating to job deployment contained in the staging area remain in place at job completion.
• False (Default): All files contained in the staging area relating to job deployment are cleared before job completion.

<OS>_LOG_INFO_LEVEL

Determines the level of detail saved to in the Job Log file during job deployment. This value is set when a Deploy Job is created. By default, only errors and some other minimal statements are logged. To access the log, right-click the Job and select Log.

• all_information: All messages, including errors and warnings, are displayed in TrueSight Server Automation Console and saved to a log file.
• errors_warnings: Only error and warning messages are displayed in TrueSight Server Automation Console and saved to a log file.
• errors_only (Default): Only error messages are displayed in TrueSight Server Automation Console and saved to a log file.

<OS>_SUM_OVERRIDE

Patch analysis generates a single user mode setting for each patch included in a BLPackage. Use this parameter to override that setting during job deployment. Choose one of the following:

• use_item_defined_user_mode_setting (Default): During object processing, this Deploy Job will use the user mode setting (single- or multi-user) defined for that object.
• ignore_item_defined_user_mode_setting: Prevents a server from entering single-user mode no matter how many individual objects within the package are defined for that mode.
• use_single_user_mode_without_reboot: The Deploy Job is processed on a target server in single-user mode. The job switches into single-user mode without first rebooting or shutting down.
• reboot_into_single_user_mode: The Deploy Job reboots or shuts down a target server. The server enters single user mode for job processing.

<OS>_REBOOT_OVERRIDE

Patch analysis generates a reboot setting for each patch included in a BLPackage. The value entered for this parameter overrides the BLPackage reboot settings during job deployment. Values entered here correspond to the Reboot Options defined on the Job Options panel. Note that Deploy Jobs that include reboot instructions must be executed in single user mode to prevent interference with other jobs.

Choose one of the following:

• use_item_defined_reboot_setting (Default): Causes the target server to reboot after an object in the BLPackage is processed when the instructions for that object call for a reboot. If the reboot setting, By end of job, is defined for the object and a reboot is not scheduled for this job, then the reboot occurs at the end of the job.
• ignore_item_defined_reboot_setting: Prevents a server from rebooting regardless of package definition unless the object being deployed includes an out-of-band reboot (a reboot that is built into the object and is not part of the BLPackage instructions).
• reboot_at_end_of_job: Causes the target server to perform a final reboot at the end of the job. All other reboots are consolidated into one reboot which occurs at the end of the job. If reboot is not specified for any item in the job, reboot does not occur at the end of the job.

<OS>_BATCH_JOB_PARALLEL

Determines whether the Deploy Jobs included in a Batch Job should execute serially or in parallel. If this parameter is defined as true, Deploy Jobs execute in parallel, and corresponds to selecting the Execute Jobs in Parallelradio button on the Batch Job Options tab of the New Batch Job dialog. Choose either:

• True: Jobs being deployed as part of a batch are deployed in parallel.
• False: Jobs being deployed as part of a batch are deployed serially.

<OS>_BATCH_JOB_CONTINUE_ON_FAIL

Determines whether a Batch Job continues when a single job within the batch fails. Choose either:

• True: Execution of the Batch Job continues when a single job within the batch fails.
• False: Execution of the Batch Job stops when a single job within the batch fails.

<OS>_SWITEM_RETURN_CODES

Applies an override for each return code in the comma-separated list to software items created during patch analysis. Overrides are applied as read-only properties of the software items.

Note: By default, this parameter is commented out (not used) in the jython.conffile and the default values listed below are used.

• E:<list> — Applies an override for each error code specified in the list. By default, any non-zero number indicates failure.
• R:<list> — Applies an override for each reboot request code specified in the list. The default is 3010, which indicates success with reboot.
• S:<list> — Applies an override for each success code specified in the list. The default is zero (0), which indicates success.
• W:<list> — Applies an override for each warning code specified in the list. No default value is applied.

If not commented out, each code specified in the list (<list>) should use one of the following formats:

• Numeric values (for example, 1, 10, or 100)
• Ascending numeric ranges (for example 2..200 or 100..300)
• Relative numeric values with mathematical operators such as greater or lesser than (for example, >100 or <20)

When no values are supplied, overrides are not applied. In the following example, overrides are not applied for Reboot Requests (R):

For information about how to map return codes to existing software items, see Applying-return-codes-to-existing-software-items.

LINUX_TARGET_HEADERS_STAGE_DIR

Determines the operating system native path to the location where headers and other required files are copied on the target server during analysis. The default value is /var/bladelogic.