Enabling Agentless Service monitoring on WebSphere MQ

To enable agentless WebSphere MQ monitoring and configuration, you must install the Agentless Services (QPEA/QPMON/QPCFG) on a supported TrueSight Middleware and Transaction Monitor server platform. The Agentless Services can be installed and running on the TrueSight Middleware and Transaction Monitor server machine, but they can also be run on a separate server altogether subject to the supported platforms. You might select to do this if your TrueSight Middleware and Transaction Monitor server is already heavily loaded. 

Agentless Service monitoring can be applied as required to your agent installations, at any time.

  1. On the computer where you plan to install the Agentless Services, install the WebSphere MQ client.
    You need the Agentless Services and WebSphere MQ client libraries on the same computer so that the Agentless Services can load the WebSphere MQ client libraries. BMC recommends that you install the latest version of the IBM WebSphere MQ client. If you have special concerns about WebSphere MQ Client compatibility with your target platform or version of WebSphere MQ, consult the IBM documentation.
  2. Following installation of the WebSphere MQ client, install the Agentless Services on your TrueSight Middleware and Transaction Monitor server or your separate agentless servers.

    • See The Agent for instructions on installing QPEA on your TrueSight Middleware and Transaction Monitor server platform. 
    • For instructions on installing QPCFG and QPMON on your TrueSight Middleware and Transaction Monitor server, see the appropriate sections of Running WebSphere MQ Configuration and Monitoring Extensions.
  3. After installing the Agentless Services on your server, you must configure them by setting appropriate preferences using the agentpref utility for each remote queue manager. See Configuring WebSphere MQ agentless services for further information.

Note

WebSphere MQ 7.1 (and later) target queue managers have a new feature, Channel Authentication Records. These records act to permit or deny access to the queue manager via channels or to map channels to specific users for local access. By default, new queue managers created with WebSphere MQ 7.1 (and later) have this feature enabled, and administrative access to the queue manager via Client/SVRCONN channels by certain users (e.g.,mqmgroup members, Windows Administrators group members, or the Windows SYSTEM account) is denied. To enable agentless monitoring to work, you must configure your queue managers to allow administrative access via the SVRCONN channel that you specify in the agentless monitoring configuration. See the IBM WebSphere MQ documentation for details.
In IBM WebSphere MQ Version 8 and later, individual queue managers can be configured to allow or require connecting applications to supply an explicit userid and password for Connection Authentication. See Configuring the WebSphere MQ Extensions for queue managers which require authentication for configuration instructions if you are using this IBM MQ feature.
Was this page helpful? Yes No Submitting... Thank you

Comments