Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

Middleware monitoring - XML MQ

In the XML MQ section you set parameters specific to monitoring XML MQ-based software services.


For any given NAM Probe, you can change global settings for all XML transactions over IBM MQ so that the settings are inherited by all user-defined software services for this protocol. If required, global settings can then be overridden by specific settings for a particular user-defined software service.

To configure global XML over IBM MQ monitoring settings for a NAM Probe:

  1. Choose the operation model. The possible values are:

    Mixed In the mixed model, operation analysis is attempted at the level of the protocol analyzer: the protocol analyzer attempts to assemble the operation from two hits. However, this may not be possible, because of the time difference between the two parts of the operation. Therefore, if an operation is not identified at the protocol analyzer level, analysis is passed for post processing, to the transaction level. Each MQ hit (request-response pair) without any content is recognized as an operation and MQ hits with content are assembled into operations.

    External In the external model, we identify operations exclusively at the transaction level. Each MQ hit (request-response pair) is recognized as an operation.

  2. Choose the correlation ID layer.
    This option defines which layer a correlation ID will be extracted from.
    The possible values are:

    MQ The correlation ID is extracted from the IBM MQ layer. You specify the actual value of the correlation ID when specifying global configuration settings for the IBM MQ protocol.

    XML The correlation ID is extracted from the XML layer. You specify the actual value of the correlation ID tag when specifying the details of the XML operation for the specific XML over IBM MQ software service.

  3. Select the operation name separator. Specify the character to be recognized as the operation name separator that is a separator between operation names from the MQ and XML layers. The slash (“/”) character is given as the default separator.

  4. Choose if to report the operation name. The Report on Operation Name option determines whether information extracted from the MQ layer should be included in the operation name.

  5. Fine-tune availability and failures reporting.


By configuring the availability, you can determine which attempt failures are included in the availability metric calculation.

You can configure XML over MQ availability globally or at the software service level.

For global configuration, open the NAM Probe configuration and go to Global > Middleware Monitoring > XML over MQ > Availability. For the software service level, select the Availability tab in the Edit Rule window.

Failures (transport)

For IBM WebSpehere MQ, you can determine whether the following errors, all disabled by default, should be included in the calculation of Failures (transport) metric.

  • No response
  • MQ client errors
  • MQ server errors
  • MQ security errors
  • MQ protocol errors

Note that all of them are configurable.

Failures (application)

You can decide whether each of five MQ application errors should be reported as failures (application).