Establishing queue managers

This section provides a scenario of the types of queue managers that you might be working with in your BMC AMI Ops Monitor for MQ environment.

The following figure illustrates the three ways that BMC AMI Ops Monitor for MQ uses queue managers, and the information that follows the figure describes the steps that need to be taken to define object types.

Related topic

Using


Example of a BMC AMI Ops Monitor for MQ environment

image2022-3-23_13-42-24.png

Legend

MVS

In Example A, messages are sent between the BBISS1 subsystem and the CSQ2 local queue.

Proxy

In Example A, messages are sent between the BBISS1 subsystem and the queue manager on a non-MVS system by way of a local proxy queue manager (CSQ1).

Agent

In Example B, a TCP/IP connection is used to allow BBISS2 to exchange messages with PAYROLL.TEST.QM, which resides on a non-MVS system. A MainView Middleware Administrator agent must be installed and running on the non-MVS system.

Defining-queue-manager-targets-and-profiles-for-example-environment describes how to define queue manager targets and profiles for the environment that is shown in this topic. Review this procedure to become familiar with the process of adding and altering the different kinds of queue managers.




 

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