IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


Subscribing to event message topics

You can subscribe to topics that return messages about the configuration, state, or operational status of your integration server or message flows.

About this task

A subscriber can send a subscription request to the pub/sub broker that specifies the event messages that the subscriber wants to receive. To receive IBM® App Connect Enterprise event messages, use the following information to define the subscription requests.

The IBM App Connect Enterprise event messages are published with a reserved topic root:
  • For an MQTT pub/sub broker, the topic root is IBM/IntegrationBus. For example,
    IBM/IntegrationBus/integrationNodeName/Status/ExecutionGroup/integrationServerName
  • For an MQ pub/sub broker, the topic root is $SYS/Broker. For example,
    $SYS/Broker/integrationNodeName/Status/ExecutionGroup/integrationServerName
Note: You can use wildcards when you subscribe to statistics reports. For example, to receive message flow statistics reports for all integration nodes and all integration servers, subscribe to the following topic:
topicRoot/+/StatisticsAccounting/#
where topicRoot is IBM/IntegrationBus for an MQTT pub/sub broker and $SYS/Broker for an MQ pub/sub broker. For more information about how you can use wildcards, see Special characters in topics.

You can subscribe to IBM App Connect Enterprise messages in the following categories:

Message flow performance
If you enable message flow accounting and statistics collection for an integration node, the integration node publishes messages (JSON or XML publications) at an interval that you can control by setting the statsInterval property of the integration node. You can subscribe to these messages on the following topics:
  • For JSON publications:
    topicRoot/integrationNodeName/Statistics/JSON/recordType/integrationServerName/messageFlowName
  • For XML publications:
    topicRoot/integrationNodeName/StatisticsAccounting/recordType/integrationServerName/messageFlowName
where recordType specifies the type of record (SnapShot or Archive).
Note: For an MQ pub/sub broker, each message is a JMS TextMessage that contains the statistics report in XML format. If you want the message in a JMS BytesMessage format, use one of the following methods:
  • Set the environment variable MQSI_STATS_MQSTR=false.
  • Run the mqsichangeproperties command with the pubsub component to change the format. For example:
    mqsichangeproperties INODE -b pubsub -o OperationalEvents/MQ -n format -v none
    The pubsub component change overrides the use of environment variables.

Resource performance
If you enable resource statistics collection for one or more integration servers on an integration node, the integration node publishes messages (JSON or XML publications) at 20-second intervals. You can subscribe to these messages on the following topics:
  • For JSON publications:
    topicRoot/integrationNodeName/Statistics/JSON/Resource/integrationServerName
  • For XML publications:
    topicRoot/integrationNodeName/ResourceStatistics/integrationServerName
Note: For an MQ pub/sub broker, each message is a JMS TextMessage that contains the resource statistics report in XML format. If you want the message in a JMS BytesMessage format, use one of the following methods:
  • Set the environment variable MQSI_STATS_MQSTR=false.
  • Run the mqsichangeproperties command with the pubsub component to change the format.

For more information about how to interpret the resource statistics that are included in the publication, see Viewing resource statistics data.

Results

Subscribers receive statistics reports only from those integration servers that are enabled to produce statistics.


aq20080_.htm | Last updated 2018-11-02 14:46:02