Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Adapter life cycle

This section provides an overview of an adapter life cycle. In general, the life cycle of an adapter is as follows:

  1. To use an adapter, you first need to install it into BMC Atrium Orchestrator's repository. You can install it in one of the following ways:
  2. Add the adapter to a grid.
    The adapter must be enabled on at least one peer on the grid for a workflow or process to use that adapter. See Adding-adapters-to-a-grid.
  3. Configure the adapter. See Configuring-adapters.
  4. Enable (or "activate") the adapter on one or more peers (CDP, HA-CDP, AP, or LAP) in the grid.  See Enabling-and-disabling-adapters.

Other possible events in an adapter life cycle include the following:

  • Starting or stopping an adapter — If you need to do this, see Starting-and-stopping-adapters.
  • Upgrading an adapter — If an adapter type is upgraded in the repository, you can upgrade the adapters that you have already configured on the grid and maintain the existing configuration. See Upgrading-adapters.
  • Disable ("deactive") and remove an adapter — If you no longer need an adapter, you can disable it. See Enabling-and-disabling-adapters. To completely remove the adapter from the BMC Atrium Orchestrator system, navigate to the Repository user interface, select a specific adapter version and click the Delete button.
  • Using custom adapters — You can add custom adapters to the repository by uploading information to define a new adapter type or by uploading a prepackaged adapter in an AROAR file. Custom adapters must be configured and enabled just like any other adapter. See Uploading-a-prepackaged-adapter-to-the-repository.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*