AAI Integration for Control-M

AAI for Control-M allows you to put the runtime information of executions from different Clients in multiple Control-M systems into a single view. This means that you can see running executions (and possible failed ones) of more than one Control-M system in a single interface, without having to switch from one Control-M interface to another.

This topic gives you an overview of the AAI integration for Control-M. For instructions on how to setup and configure your Control-M Connector, see Setting Up the Control-M Connector.

This page includes the following:

Overview

Click the image to expand it.

Graphic overview of the connection between AAI and Control-M

The Control-M Connector establishes the communication between Control-M and AAI. It is a stand-alone component. As such, it runs in its own process space, has its own installer and writes its own log files. It consists of two main parts:

  1. The universal connector framework, which handles the communication between the Control-M Connector and AAI. It also triggers, or determines, when the Connector fetches job definitions and events (executions) from Control-M.
  2. A mapper, which extracts job definitions and events (executions) from Control-M and translates them into a format that AAI can process.

Therefore, it is recommended to install the Control-M Connector near the Control-M installation.

The Connector connects with the Control-M database to periodically extract job definitions and executions (current and historical runs) and import them into AAI.

The Control-M Connector has different settings that can be modified at any time. For example, you can define the following behaviors:

  • The interval in which the job definitions and events (executions) are fetched. You can set the interval for fetching both individually.
  • Upon starting, how far back should the Connector look the first time it fetches information.
  • How far forward should the Connector look, thus gathering information on planned start times.

Once the Connector is installed and running for the first time, it reaches to AAI and registers itself. The user sets up the Control-M configuration in the AAI client. Once AAI has configured the Connector to talk to Control-M, the Connector schedules retrieving the job definitions and events (executions) from Control-M, translates them into the relevant format and passes the information to AAI.

Java Requirements

Make sure that Java JDK 1.8.x is installed on the AAI application server and configure the JAVA_HOME environment variable accordingly.

Note:

A full JDK installation is required to run the AAI server. The JRE (Java Runtime Environment) is not sufficient.

For more information, see Compatibility Information.

Supported Control-M Objects

The Control-M integration into AAI supports the following objects:

  • Jobs

    A Control-M Job is a definition of a command to run. This definition includes the conditions, execution frequency, and the target machine in which to run the command.

  • Events

    A Control-M Event is the definition of a Job's state change, error, or success. These are used to determine if jobs succeeded, failed, and/or were retried. Dependent jobs occasionally use these events as conditions.

  • Folders (Smart, Simple, Complex and so on)

    A Control-M Folder is a container definition for Jobs and subfolders. Folders enable you to configure various settings such as scheduling, event management, resources, or notifications. Folder-level definitions are inherited by the Jobs or subfolders within the folder.

  • Resources

    A Control-M Resource is something that a Control-M Job depends on and use. Control-M Resources can be Logical or Quantitative. Logical Resources include physical drives, tables, or databases. Quantitative Resources is a physical or logical entity that you can count, such as a CPU, or Table/Data set.

  • Node

    A Control-M Node is a host computer that a Job is sent to, to be executed. Each Node is running a Control-M Agent that orchestrates and monitors the Job and its result.

For more information, please refer to the Control-M documentation at documents.bmc.com.

You can use those Control-M objects to carry out the following actions in AAI:

  • Create (SLA) for different jobstream setups (simple, complex and/or with external dependencies)
  • Locate a possible bottleneck in a jobstream (critical path)
  • Create dashboards

See also: