Creating an Action

This topic describes how to create an Action.

To create an Action

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

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

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

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

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

    

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

8. In the Application Schema page, populate the following fields, and click Next.
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.

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

    Note

    BMC Database Automation supports the uploading of zipped content files. The maximum file size supported for a zipped content file is 2 GB.
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.

Actions scope and provisioning associations

BMC Database Automation Actions can be used as pre-provisioning and post-provisioning scripts during provisioning operations. When the options for Available as Pre-Provisioning Script and Available as Post-Provisioning Script are selected on the Actions Configuration page, the Actions scope determines the relevant scripts to display on the Custom Scripts Configuration page during provisioning.