Defining an Execution Plan to run a script

An Execution Plan provides the interface for a script and its execution. Through an Execution Plan, you specify configuration values for the script, indicate on which Agent Groups the script runs, define the run schedule, and set the blackout periods.

BMC Synthetic Transaction Execution Adapter (TEA) Agents can process up to 120 Execution Plans.

This topic contains the following procedures:

• • Before you begin
  • To view the list of defined Execution Plans
  • To define an Execution Plan
  • To delete a defined Execution Plan
  • To define an Execution Plan to run a Silk Test project
  • Related topics

Before you begin

• Define Business Services before defining Execution Plans. Every new Execution Plan inherits the following settings from the associated Business Service:

  • Execution Plan run frequency
  • Execution Plan timeout period
  • Agent Groups
  • Blackout settings
  • Active or inactive status

  You can modify these settings for individual Execution Plans.

• Upload custom scripts.

To view the list of defined Execution Plans

1. On the BMC Application Management Console, click the Synthetic tab.
2. On the navigation menu, click Execution Plans.
   A list of defined Execution Plans is displayed.
3. To sort the list based on a specific column, click the relevant column heading. To sort in reverse order, click the column heading again.
4. To filter the list, start typing a value in any of the boxes under the column headings, or select an option from the Status list.
5. To see the factor or factors creating an inactive status, hover over the status.
   The following factors can cause an Execution Plan to be inactive:
   • User-induced inactive status of a Business Service
   • User-induced inactive status of an Execution Plan
   • Blackout period of a Business Service
   • Blackout period of an Execution Plan

To define an Execution Plan

Modifications to an Execution Plan modify and override the inherited settings from the associated Business Service.

1. On the BMC Application Management Console, click the Synthetic tab.
2. On the navigation menu, click Execution Plans.
3. Perform one of the following actions:
   • To define a new Execution Plan, on the Execution Plans Action menu, click Add Execution Plan.
   • To edit a previously defined Execution Plan, from the shortcut menu of the specific Execution Plan, select Edit Execution Plan.

4. In the General Execution Plan Settings panel, configure the following settings:

   • To change the the Execution Plan Status, select Activate or Deactivate.
     The status of the Execution Plan determines whether the script runs. The Execution Plan is also affected by the status of the Business Service.
   • Enter a unique name for the Execution Plan and (optionally) a description for the Execution Plan.

   • Select the Business Service with which to associate the Execution Plan.
     Default values, inherited from the Business Service, are populated for Execution Settings and Blackout Settings.
5. For a new Execution Plan: In the Execution Plan Script panel, select the script file that this Execution Plan controls.
   You cannot change the script association when you edit an Execution Plan.

6. Set values for the script attributes that require user input, such as URLs, host names, and passwords.

   Note

   • The system does not validate script values. For information about provided scripts, see Using-a-script-to-simulate-end-user-transactions.
   • If you define the Execution Plan to run a Silk Test project on more than one TEA Agent, ensure that each TEA Agent has a local administrator account that uses the same user name and password.
7. In the Execution Settings panel, the following parameters are set by the Business Service. You can override the settings:
   The referenced document [confluencePage:page:APM26.Defining a Business Service to group Execution Plans] was not found.
8. In the Blackout Settings panel, the parameters are set by the Business Service. You can modify the settings to extend blackout periods:
   The referenced document [confluencePage:page:APM26.Defining a Business Service to group Execution Plans] was not found.
   The relationship between a Business Service blackout period and an Execution Plan blackout period is a logical OR, meaning that the Execution Plan is in a blackout period if either the applicable Business Service, or the Execution Plan, or both are in blackout.
9. Click Save.

Initial configuration operations might take several minutes, depending on the heartbeat interval of the BMC TEA Agent (30 seconds, by default) and the amount of time to download the scripts to the Agent computer.

To delete a defined Execution Plan

1. On the BMC Application Management Console, click the Synthetic tab.
2. On the navigation menu, click Execution Plans.
3. From the shortcut menu of the specific Execution Plan, select Delete Execution Plan.
4. Click OK in the confirmation message.

To define an Execution Plan to run a Silk Test project

On each TEA Agent computer where a Silk Test project runs, the user name and password of the local administrator must be the same. For information about setting up a Silk Test project, see Preparing-Silk-Test-script-execution-for-synthetic-transaction-monitoring.

Related topics

Business-Service-and-Execution-Plan-status

Examining-and-retaining-Execution-Plan-results-files