Resolving problems when you monitor message flows

Follow the advice for dealing with common problems that can arise when you are monitoring IBM® Integration Bus flows.

Procedure

You are not receiving monitoring events from IBM Integration Bus

Procedure

  • Scenario: You are not receiving monitoring events from IBM Integration Bus.
  • Explanation: You can configure IBM Integration Bus flows to emit event messages. These messages can be used to support transaction monitoring and business monitoring. The events that are published by IBM Integration Bus can be written to a transaction repository, creating an audit trail of the transactions that are processed by an integration node. You can also use IBM Business Monitor to monitor events. To receive monitoring events, you must configure and enable event sources, activate monitoring, and subscribe to the topic for the flow.
  • Solution: If you are not receiving monitoring events, check that the following resources are configured correctly.
    1. Check that event sources are configured on the flow by using monitoring properties or a monitoring profile. For more information, see Monitoring properties or monitoring profile.
    2. Check that event sources are enabled by setting the -i parameter on the mqsichangeflowmonitoring command. For more information, see Enabling and disabling event sources.
    3. Check that monitoring is activated for the flow by setting the -c parameter on the mqsichangeflowmonitoring command. For more information, see Activating monitoring.
    4. Check that publication of monitoring events is enabled, and the corresponding pub/sub broker is configured and running.
      Monitoring events are in the BusinessEvents group. For more information about configuring the pub/sub broker, and reporting if publication is enabled, see Event monitoring.
    5. Check that you have subscribed to the topic for the flow.
      For example, on an MQ pub/sub broker:
      $SYS/Broker/integrationNodeName/Monitoring/integrationServerName/flowName
      and on an MQTT pub/sub broker:
      IBM/IntegrationBus/integrationNodeName/Monitoring/integrationServerName/flowName
    6. If you are writing events to a transaction repository, complete the following extra checks.
      • Check that events are configured for your transactions.
      • Check that you have subscribed to the event topic and written events to a repository.

        For more information, see Monitoring scenarios.

    7. If you are using IBM Business Monitor to monitor events, complete the following extra checks.
      • Check that IBM Business Monitor is installed, and that a monitor server is created and started. For more information, see IBM Business Process Manager product documentation online.
      • Check that the monitoring model application and message-driven bean (MDB) are installed and configured.
  • To report monitoring settings, use the mqsireportflowmonitoring command.
    For more information, see mqsireportflowmonitoring command.

Statistics options are not visible in the web user interface

Procedure

  • Scenario: Your integration node is configured for statistics, but you cannot view or use statistics in the web user interface.
  • Explanation: The pubsub component was configured, and one of the requirements for statistics is unavailable or disabled. By default, the built-in MQTT broker is used for OperationalEvents, which includes statistics.
    For example, if the built-in MQTT broker is disabled and an alternative broker is not specified, statistics will be unavailable.
  • Solution: Check for one of the following scenarios by using the mqsireportproperties command with the -b parameter set to pubsub, and take the corrective action:
    1. MQTT is disabled for OperationalEvents. Enable OperationalEvents over MQTT on the pubsub component.
      For more information, see Configuring the publication of event messages.
    2. MQTT is enabled for OperationalEvents and uses the default policy. However, the built-in MQTT broker is not currently running. Start the MQTT broker.
      For more information, see Configuring the built-in MQTT pub/sub broker.
    3. MQTT is enabled for OperationalEvents, but was configured with an invalid policy URL. Either the syntax is invalid, or the specified policy document does not exist. Check that the URL is valid.
    4. MQTT is enabled for OperationalEvents and a valid policy URL was specified, but the policy document is invalid or contains an incorrect host or port for the MQTT server. Correct the policy document.
      For more information, see Configuring and attaching operational policies.
    5. MQTT is enabled for OperationalEvents and a valid policy URL was specified. The policy document is valid and refers to an MQTT server. However, the MQTT server is not running. Start the MQTT server.