Creating an Action

1. From the Management Console, select Actions > Action Repository.
2. In the Action Repository page, click Create New Action.

3. In the General page, populate the following fields, and click Next.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
   

4. In the Action Execution page, populate the following fields, and click Next.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
   

5. In the Availability page, populate the following fields, and click Next.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
   

6. In the Remediation page, populate the following fields, and click Next.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
   

7. (For SQL Actions only) In the Credentials page, select the Credentials Options option button corresponding to one of the following options:

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
   

8. In the Application Schema page, populate the following fields, and click Next.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
   

9. In the Custom Fields page, specify custom fields for this Action and click Next.
   1. Click Add.
   2. Enter the name of the custom field in the Custom Fields Name field. The name used here must match the name used in the template that you load in the Actions Files page.
   3. If this custom field should be a required field, select the Required check box.
   4. Click Add to add the field name to the list.
   5. Repeat these steps for each custom field to be added to this Action.

10. In the Restrictions page, populate the following fields, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
    

11. In the Action Files page, populate the following fields, and click Next.

    Warning

    Note

    BMC Database Automation supports the uploading of zipped content files. The maximum file size supported for a zipped content file is 2 GB.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
    
    

12. In the Summary page, review the provisioning information.
    To make changes, do the following:
    1. Click Go to to return to the provisioning step that you want to edit.
    2. Make your changes.
    3. Click Save and Review to return to the Summary page.
13. Click Create Action to finish creating the Action.

Creating a Remediation Action

Remediation Actions are BDA Actions that have been associated with a specific standard and remediate one or more checks implemented by that standard. When you run a Remediation Action through the BDA GUI, the candidates listed will be restricted to those that have had that particular standard run against them and are currently non-compliant for the checks listed in the Remediation Action.

To create a Remediation Action in BDA, follow the steps to create an Action. Make sure that the scope of the Action is the same as the scope of the standard that it will be remediate. For example, if you write an Action to remediate problems in an Oracle Database-scoped standard, the Action must also be Oracle Database-scoped. Then, in the Remediation section in the Create Action page, select Is Remediation Action.

This enables a menu consisting of all standards that have the same scope as the Action you create. Select the standard that this Action will be associated with (and will remediate failed checks for) and click Add Check. Next, enter the check ID of the check this Action will remediate. If the action will remediate more than one check, click Add Check multiple times and enter one check ID per text field.

Continue with creating the action as you would any other action in BDA.

When the Remediation Action is run, you are presented with a list of candidates that are non-compliant for the checks listed on the Remediation page. However, the Remediation Action is passed no information during the execution of the Action about what checks have failed and what checks have succeeded. The Remediation Action must re-perform whatever checks were performed by the standard and determine what needs to be remediated.

Furthermore, when a Remediation Action has completed running, there is no mechanism for reporting the change in compliance back to the BDA Manager. Once a Remediation Action is complete, you should re-run the compliance standard again against the targets and collect new compliance data that reflects the remediated checks.