Running jobs to test and remediate server software compliance

Step 1. Create a component template

BMC Server Automation

The component template should include a signature that can be used to discover the existence of software applications. The signature can consist of a basic condition that checks for the existence or number of occurrences of a software application object that you choose from the discovered software applications.

For example, when adding parts to the template, you can use the Atrium Discovery object to add a part from the Discovered Software node called Oracle Database Server 10.2.0.1.0. Then you can define a signature specifying that "Atrium Discovery.Software:/DiscoveredSoftware/Oracle Database Server 10.2.0.1.0" exists.

For details on creating a component template, see Creating a component template in the BMC Server Automation documentation.

Step 2. Add a compliance rule to the component template

BMC Server Automation

The compliance rule should check for the existence of a particular software application with a particular name and version number. Or, the rule can analyze the properties of a software application to confirm that the application's properties show the correct name and version number. For example, a simple compliance rule could read:

"Atrium Discovery.Software:/DiscoveredSoftware/Oracle Database Server 10.2.0.1.0" exists

If you want to remediate servers that are not in compliance, the compliance rule should include a BLPackage that can deploy the software package to those servers. The compliance rule can be defined to automatically remediate servers not in compliance, or you can manually determine which servers require remediation.

For details on creating a compliance rule, see Compliance tab for a component template in the BMC Server Automation documentation.

Step 3. Create and run a Component Discovery Job

BMC Server Automation

Using the component template you created in the previous steps, create and run a Component Discovery Job. The components that the job discovers should correspond to instances of a software application.

For details on creating a Component Discovery Job, see Creating Component Discovery Jobs in the BMC Server Automation documentation.

Step 4. Create a Compliance Job

BMC Server Automation

Using the same component template, create a Compliance Job that determines whether servers are in compliance based on the software applications that are discovered on the server.

The Compliance Job can be set up to allow for remediation of servers that are not in compliance. When servers are not compliant, a BLPackage containing the software application can be deployed, either automatically or based on operator intervention.

For details on creating a Compliance Job, see Creating Compliance Jobs in the BMC Server Automation documentation.