Phases of use with TMS
This topic provides an overview of how the CAI module is used by the Task Management System (TMS).
Definition phase: Application registration and command definition
Application registration defines the integration attributes to the external applications, such as application name, connection information, and interface form names.
Command definition describes the commands and the command parameters for each integrated component. For example, the Requester console has defined a set of commands for interaction with back-end applications. In TMS, a set of commands is defined for interaction with BMC Configuration Management. In addition, the CAI can include command parameter mappings to the registered applications.
Construction phase: Instantiation of the command definition as events
Command events are instantiated based on the command definitions. The event is constructed using the specific command name, and the command parameter values are populated by the integrated components. CAI provides the form structure and generic workflow for command instantiation. Each integrating component must implement the workflow to control its specific commands.
Execution phase: Event delivery
The mechanism that delivers the command events to the target system depends on the protocol used.
- AR protocol — The target is another BMC Remedy Action Request System (BMC Remedy AR System) application. This plug-in generates the appropriate records as specified in target information of the event.
- UR protocol — Workflow sets the URL string to the appropriate view field for the browser.
CAI provides the generic event plug-in and each integrating component must implement the workflow to control the invocation of the plug-in, or use specific workflow for the delivery.