Overview of the OA module
The AD Operations Actions Module is automatically installed when you install BMC Atrium Orchestrator. You can use the processes contained in this module to simplify the configuration of base adapters. This module provides easy-to-use processes, referred to as adapter wrappers, for each of the actions supported by a base adapter. These adapter wrappers are used to create an XML document that an adapter requires to execute an adapter request. The password field in the Autopilot-AD-Utilities wrappers now supports encrypted password using secure data-type in the configuration item. Any resulting adapter response is returned for use in subsequent activities in the workflow.
Before you begin
- Import and unbundle the AutoPilot-OA-Common-Utilities module.
- Activate the module on the grid in which the adapter wrappers are used.
For details about this supporting module, see Importing-utilities-modules.
The AutoPilot Utilities Module is automatically installed when the first Configuration Distribution peer (CDP) is installed. This module is copied into the Grid Library for each grid created in Grid Manager. The following sections outline the steps required to import a module from the Grid Library, import a module from an external source, unbundle a module, activate a snapshot, and activate individual modules.
Modules are installed from the Library on a specific grid. You can import modules directly from the Grid Library directory, which resides on a CDP or from an external source, such as a CD or hard disk.
The BMC Atrium Orchestrator platform includes an adapter Utilities Module called AutoPilot Utilities (file name AutoPilot-AD-Utilities ) which contains processes that streamline the use of base adapters in workflows. These processes are referred to as adapter wrappers. Each process uses input parameters to create the adapter request and then produces one or more output parameters containing the adapter response.
To use an adapter wrapper in an existing workflow process, drag the desired adapter wrapper on to the process canvas. This creates a Call Process activity for the adapter wrapper.
To configure the Call Process activity, values must be assigned to each Call Process input parameter that is designated as required. Default values are automatically assigned for many optional inputs. If these default values are acceptable, no further assignments are necessary. Output parameters are available as indicated in the following sections. These output parameters can be mapped to Context Items for use in subsequent activities.
For details on assigning input and output parameter values, see the Call Process activity section of Called-processes.