Unable to see the Websphere MQ node in Introscope for a Tomcat application making client calls to Websphere MQ

Article Id: 20107
Status: Published
Updated On: 14-02-2018 08:17
Legacy Id: TEC597692
Products:
CA Application Performance Management Agent (APM / Wily / Introscope) , INTROSCOPE
Issue/Introduction:

Description:

Websphere MQ client calls

Solution:

To instrument the client side calls made from the Tomcat app to websphere MQ, follow these steps:

  1. Configure the MQ agent extension on the Tomcat agent:

    1. In <AppServer_Home>/wily/core/ext/ copy the MQNameFormatter.jar

  2. Add the required pbd files to the directives list:

    introscope.autoprobe.directivesFile=websphere-typical.pbl,hotdeploy,webspheremq.pbl


  • Make sure the following IBM client jars are added to the application class path or to the tomcat/common/lib folder:

    For WebSphere MQ v6.x, copy the following JAR files from <IBM WebSphere MQ installation directory>/java/lib to the classpath

    • com.ibm.mq.jar

  • com.ibm.mqjms.jar

  • connector.jar

  • dhbcore.jar

For WebSphere MQ v7.0, copy the following JAR files from <IBM WebSphere MQ installation directory>/java/lib to the classpath

  • com.ibm.mq.jar

  • com.ibm.mqjms.jar

  • connector.jar

  • dhbcore.jar

  • com.ibm.mq.commonservices.jar

  • com.ibm.mq.headers.jar

  • com.ibm.mq.jmqi.jar


Note: If you are monitoring the Queue Managers of both WebSphere MQ v6.x and WebSphere MQ v7.0, then use the WebSphere MQ v7.0 library files

  • Remove the above client jars from the tomcat/endorsed/lib folder. This is very important because any jar available in the tomcat/endorsed/lib will be loaded as part of the JVM bootstrap loader, and by default the Introscope Agent skips the instrumentation of the classes loaded by the bootstrap loader, thus preventing MQ Powerpack from monitoring the MQ calls.

Environment:

Release:
Component: APMISP