Defining connectivity

This topic describes how to define intercommunication for z/OS and distributed queue managers manually so that 

BMC AMI Ops Automation

 can listen for instrumentation events and issue commands to queue managers.

To manually configure the connections, you must define the queue managers, transmission queues, and sender and receiver channels so BMC AMI OpsA can listen for distributed instrumentation events and issue commands to distributed queue managers.

Related topic

Installation-overview

Setting up z/OS queue manager connectivity

BMC AMI Ops Automation for MQ can automate IBM MQ instrumentation events from any message queue in a z/OS queue manager. These z/OS queue managers must be running on the same z/OS image as BMC AMI Ops Automation for MQ.

To enable BMC AMI OpsA to issue commands to the local queue manager, you must ensure that the command server is started. For information about the command server and starting it, see the IBM documentation MQ Event Monitoring.

Setting up distributed queue manager connectivity

BMC AMI Ops Automation for MQ can automate events from distributed queue managers. To do this, you need to send the distributed event messages to a local queue automated by BMC AMI Ops Automation for MQ.

Event data is sent to the local instrumentation queues on the z/OS IBM MQ queue manager by defining the system event queues on the distributed operating system as remote queues. IBM MQ automatically transmits the messages from the distributed queue manager to the z/OS queue manager. BMC AMI Ops Automation for MQ, monitoring the local queues on the z/OS queue manager, receives from the distributed queue manager, the system event messages and performs whatever automation has been defined.

This section contains the following topics:


 

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