This topic provides suggested uses for the solution, descriptions of the workflows, configuration tips, and guidelines for customizing the existing workflows.
The BMC ProactiveNet Performance Management Triage and Remediation Solution and BMC Event and Impact Management solution provides prepackaged workflows to help you manage the following system occurrences:
An event notification triggers each workflow. The source of this event can be a BMC PATROL, a BMC Event and Impact Management, or any event that complies with the slot mapping standards which BMC Atrium Orchestrator supports. The event, in turn, is triggered when a specified threshold attribute is breached for the particular monitored component.
You can launch a manual, on-demand workflow from the Events Console of the BMC ProactiveNet Operations Console. You can also define a remote action policy to automate the workflow launch from the BMC ProactiveNet Administration Console.
The parameters for each workflow are defined in the ao_actions.mrl file. The chief difference between the two is that you can specify your input parameters in manual workflows, but the automated workflows use default values. For example, an automated workflow automatically creates incidents and change requests. However, you do have the option in automated workflows of changing the default values in the installationDirectory\pw\server\etc\cellName\kb\bin\ ao_actions.mrl file. (See Configuring BMC ProactiveNet for the BMC ProactiveNet Performance Management Triage and Remediation Solution for the steps to recompile the knowledge base and restart the ProactiveNet server cell.)
You have the option of making most of the workflows context sensitive to PATROL events by uncommenting and commenting code in the ao_actions.mrl file. (See ProactiveNet server configuration for examples.)
You also have the option of customizing the ao_actions.mrl file to make any defined action context sensitive. For more information, see Configuring BMC ProactiveNet Server for the triage and remediation.
In defining a policy, you first define the event selector and then define the policy from the BMC ProactiveNet Administration Console.
Perform the following steps to define the event selection criteria:
$EV.msg contains 'unreachable'.
Perform the following steps to define the remote action policy:
The event selection criteria are applied to the remote action policy.
By default, each workflow applies to all events. From BMC ProactiveNet Operations Console, perform the following steps to select and launch a workflow from the Events Console:
Select the workflow. An Execute Action dialog box opens containing input parameters that are specific to your workflow selection. The following figure shows the Execute Action dialog box for the OS Disk Space Full workflow:
Execute Action dialog box: OS Disk Space Full workflow
For example, you can choose to create an incident ticket and a change request as part of the workflow.
The specific input parameters for each workflow are described in the workflow descriptions later in this topic.
Event notes in the Details pane
Click the Action Results icon to display the Event Remote Action Results dialog box. You can view output, errors, and details associated with the workflow action. The exit code 0 indicates successful execution. Otherwise, the exit code defaults to -1.
Click the Related Events icon.
Related Events option
The Event List window displays where you can view, filter, and perform actions on consequent events that are related to the workflow launch.
Event List window
On the BMC ProactiveNet server side, when you run a BMC Atrium Orchestrator workflow on an event, the system populates the mc_operations field with a message. If you do not see a message in the Details window of the Console, check the ProactiveNet server cell trace file under the installationDirectory\pw\server\log\cellName\trace directory. When the workflow runs, it updates the mc_notes field in the Details window with status information and displays an Action Result icon next to the event. An action exit code of 0 indicates a successful execution. A non zero action exit code indicates unsuccessful execution.
To obtain more debugging information about the BMC ProactiveNet server cell, run the following command:
On the BMC Atrium Orchestrator server side, check the grid.log file to verify whether the workflow action has been received in the grid.log under the C:\Program Files\BMC\AO\tomcat\logs directory path.