Configuring the Message Broker monitoring extension for queue managers which require authentication

In IBM WebSphere MQ Version 8 and higher, individual queue managers can be configured to allow or require connecting applications to supply an explicit userid and password for Connection Authentication.

If a broker's local queue manager is to be monitored via a direct connection and hhas its CONNAUTH property set to the name of an AUTHINFO object, and has its CHCKLOCAL property set to REQUIRED or REQDADM, then you must configure the extensions as below in order for them to be able to connect to the queue manager. If the CONNAUTH property is set, and the CHCKLOCAL property is set to OPTIONAL, then you can configure the extensions as described below. If the queue manager CHCKLOCAL property is set to NONE, then do not configured the extensions to attempt authentication.

If a broker's remote queue manager to be monitored via an agentless connection hhas its CONNAUTH property set to the name of an AUTHINFO object, and has its CHCKCLNT property set to REQUIRED or REQDADM, then you must configure the extensions as below in order for them to be able to connect to the queue manager. If the CONNAUTH property is set, and the CHCKCLNT property is set to OPTIONAL, then you can configure the extensions as described below. If the queue manager CHCKCLNT property is set to NONE, then do not configured the extensions to attempt authentication.

Was this page helpful? Yes No Submitting... Thank you

Comments