Unsupported content

   

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

About remediation packages and remediation jobs

When you remediate a Compliance Job failure, BMC Server Automation creates a remediation package containing the BLPackages required to remediate each failed compliance rule.

When checking compliance for multiple components, BMC Server Automation creates a separate remediation package for each distinct set of compliance rules that a component fails. If multiple components fail the same set of compliance rules, BMC Server Automation optimizes by creating only one remediation package to correct all of those failures.

The items in a remediation package are arranged in the same order as compliance rules are arranged in the component template. For example, if the first failed rule specifies that a BLPackage called Fix1 should be deployed and the second failed rule specifies that a BLPackage called Fix2 should be deployed, the remediation package includes the items from Fix1 followed by the items from Fix2. If two or more of the BLPackages being aggregated include local properties with the same name, the properties are renamed and all references to each renamed property are updated.

After creating remediation packages, BMC Server Automation automatically creates a Deploy Job to deploy each remediation package. A single Deploy Job may act upon a single target component or it may act upon multiple components if more than one component fails the same set of compliance rules. If this procedure creates multiple Deploy Jobs, the system combines those Deploy Jobs into a Batch Job so the entire remediation can be launched as one job.

Remediating a Compliance Job is different from synchronizing Audit Job results. An audit is always based on a master server or a snapshot of a server. Using equality and limited parameterization, it compares one server configuration to another. After running an Audit Job, you can build a BLPackage from the audit results. A Compliance Job, on the other hand, is based on rules. It uses comparison operations and parameterization. The complicated logic that is possible when defining compliance rules (for example, strings or clauses and ranges of acceptable values) makes it impossible to automatically generate a BLPackage that can synchronize a server to a component template. For this reason, if you want to remediate a compliance rule failure, you must manually define a BLPackage that can repair failures. The BLPackage must be defined and associated with a compliance rule before you attempt remediation.

When BMC Server Automation automatically creates Deploy Jobs for remediation jobs, it applies default settings to those Deploy Jobs. BMC Server Automation provides a procedure for specifying your own customized settings for Deploy Jobs created for remediation purposes. This procedure can be very helpful if a remediation job launches many Deploy Jobs. For more information about the procedure, see Setting deploy options for remediation jobs.

When BMC Server Automation automatically creates Deploy Jobs or Batch Jobs for remediation, it sets the AUTO_GENERATED property to True for those jobs. Similarly, if BMC Server Automation automatically creates BLPackages for remediation, it sets AUTO_GENERATED to True for those BLPackages. When these objects have AUTO_GENERATED set to True, they are automatically deleted at a later date according to the retention policy you set up for automatically generated objects. For more information about managing BMC Server Automation data and deletion of auto-generated objects, see BMC technical documentation at Marking data for deletion.

Was this page helpful? Yes No Submitting... Thank you

Comments