WebSphere MQ applications

For WebSphere MQ applications, you need the:

• Host names where the WebSphere MQ BTM Extension runs.
• Queue manager names so that you can define a regular expression to target this activity implementation for those queue managers.
• Application names. On Windows and UNIX this would be the file path to the application and application name. The .exe suffix is not included for Windows. On z/OS it is the job name.
  • On Windows and UNIX, if you have deployed the TrueSight Middleware and Transaction Monitor runtime toolkit and installed the BTM WebSphere MQ API exit, you might have a log that begins with btm_QmgrName_ApplicationName from which you can derive the queue manager and application name for the activity implementation details.
  • When monitoring the WebSphere MQ channel, the application name is WMQ_CHANNEL which matches a number of WebSphere MQ process names.
• Name of any queues used in the WebSphere MQ API calls (for example, the name specified in MQOD of the MQOPEN call). The optimum specification is the name specified on the MQOD of the MQOPEN call or MQPUT1 call. This can be:
  • Local Queue
  • Model Queue
  • Alias Queue
  • Remote Queue
  • Transmission Queue
  • Shared Queue
  • Other allowed queues names are:
    • Resolved Queue Name: The name that is returned when the queue is opened and the name specified in the MQOD is resolved to another queue.
    • Remote Queue Name from the MQXQH (Transmission Queue Header): This only applies to channel senders (the WebSphere MQ process that reads messages from the queue and sends them to another queue manager). This is commonly used when the channel has traffic that is not being monitored and isolates the monitoring to the applications sending to a particular destination queue.
• Name of any topic names used in the WebSphere MQ API calls. This can include the wildcard characters allowed by WebSphere MQ. This can cause some confusion as this WebSphere MQ specification is not interpreted by the WebSphere MQ BTM extension, it simply matches the string configured to that specified on the API. The WebSphere MQ BTM extension specification allows for this string to contain a * at the end to define a prefix or by itself to match anything.
  • If there is a conflict between the WebSphere MQ BTM extension specification and the WebSphere MQ topic name, specify a * and add an activity filter on the topic technology data using an appropriate regular expression. The topic technology data is the actual topic name as determined when messages are actually received or published.