AAI Integration for CA7

Unlike other AAI integrations, CA7 does not require a connector to communicate with AAI. There are two ways of integrating AAI with CA7:

After configuring and implementing either the tailored JCLs or the CA7 Server for AAI, you complete the integration by adding a CA7 scheduler to AAI and establishing the connection. For more information, see Configuring CA7 Schedulers (Thick Client) / Configuring CA7 Schedulers (Web UI).

Who Should Read These Topics?

Integrating CA7 and AAI requires the collaboration between mainframe specialists and AAI administrators. To accomplish these tasks, a deep understanding of both mainframe environments and of AAI is required.

Types of Data Retrieved by the CA7 Server for AAI

Using either of the integration methods, the following types of data are retrieved from CA7:

  • Definition data

    Job definitions, triggers, predecessors, calendars, resources and datasets defined in the CA7 database. This data is stored in the LDSN, LJOB, SCAL, TIMEZONE files that AAI requires.

    • With the CA7 Server for AAI

      The CA7 Server for AAI retrieves definition data at intervals that are defined both in the CA7 Server for AAI and in the AAI configuration. This happens usually once a day because this type of data does not change very often. However, you can configure it to happen several times per day. The CA7 Server for AAI dynamically delivers these four files to a directory on the AAI server.

    • With the batch integation

      When using the batch integration method, an instance-specific JCL (JOBDEF JCL job) extracts the definition data from the files that AAI needs ( LDSN, LJOB, SCAL, TIMEZONE). This job should be scheduled within CA7 to run prior to the user-specified interval defined in AAI. It must complete before the AAI server defined interval occurs.

  • Event data

    Event data refers to the real-time activity of jobs as they run inside of CA7. Event data is stored in the RPT70 file, which is created a regular intervals. The information in RPT70 includes when a job moves through the CA7 queues, completes, abends, or is canceled.

    • With the CA7 Server for AAI

      By default, the RPT70 file is created every 30 seconds and delivered to the specified directory location on the AAI server using FTP/SFTP/FTPS. The CA7 instance definition in AAI identifies that event data will be delivered automatically and AAI regularly scans for new RPT70 files arriving in the specified directory.

    • With the batch integration

      The instance-specific EVENT JCL job extracts the event data from CA7 at intervals that are defined in AAI, typically every 30 seconds or less. This allows AAI to provide near real-time status in the CA7 monitored jobs. To perform this event data delivery, AAI initiates an FTP connection to the mainframe and sends a TRIGGER file via FTP or SFTP. CA7 detects the arrival of the TRIGGER file and runs the EVENT JCL job. The AAI server waits (polls) for the arrival of the output from the EVENT JCL job. Once the output is detected, AAI retrieves the file over FTP /SFTP and processes the contents to update the AAI database.

See also: