Running an Action

This topic describes how to run an Action.

To run an Action

1. From the Management Console main page, select Actions > Actions Repository.
2. In the Actions Repository page, locate the Action you want to run and select Run from the list box in that row.
3. In the Action page, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
4. In the Action Parameters page, select or enter the values for any custom fields that appear, and click Next.
5. In the Candidates page, select the candidates on which this Action is run, and click Next.
6. In the Job Options page, specify any of the following Job options, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

7. In the Scheduling page, select when to run this job in the Job Execution field, and click Next. 

   Note

   The UNIX atd daemon must be installed and running on the Manager to schedule Actions. In addition, the crond daemon must be installed and running to schedule recurring Actions.

8. If the Change Control page displays, provision the following fields, and click Next.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

   Note

   The Change Control page appears only when change control is configured for your environment. See Configuring-change-control.

9. 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.
10. If you have uploaded custom verification checks for this Action, specify your verification preferences.
    • To run the Action after the custom verification checks have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.

    • To run the Action without having first run the custom verification checks, select Skip Pre-Verification Tests. 

      Note

      The Skip Pre-Verification Tests option should only be used when you are certain all tests can succeed. The option skips verification and advances directly to running the Action.

11. Click Execute Job or Schedule Job (depending on your selection in the Scheduling step).
     If the Action is running, a progress page appears.
    
    When you schedule an Action, it is added to the Jobs list. You can view scheduled Jobs by selecting Jobs from the Context Frame, specifying a start and end date, and filtering the Jobs list for a Scheduled status. After you schedule a job, the start date and time cannot be modified. If you need to change the schedule for a Job, you must cancel the Action and recreate it. See Cancelling an Action. After a Job has started running, it cannot be cancelled by using the Management Console.
    
    If a target for an Action is in a Down state, or is no longer in the environment when the associated Job starts, the Job will stop due to the unavailability of the target, and the status of the Job changes to Failed.
    
    

    Note

    BMC Database Automation supports the ability to schedule and run multiple Jobs for Actions across different targets in parallel.

    If you have uploaded custom verification checks, the Verification page displays. If all of the checks pass, click Continue to run the Action. If checks fail, resolve the identified issues and click Repeat Verification.