Progress Sonic ESB Configuration and Management Guide

Chapter 11: Using Actional with Sonic Components
Related SonicMQ brokers placed on different systems (and therefore different Actional
nodes) should have their Actional Agent instances managed on the same Actional
Management Server to visualize interbroker flows such as clusters, Dynamic Routing,
and Continuous Availability failover. Correspondingly, SonicMQ brokers registered in
different SonicMQ domains but colocated on the same managed node will record their
events on the same Actional Management Server.
◆ To enable SonicMQ instrumentation on a SonicMQ broker:
1. Start the Sonic Management Console, and connect to the Directory Service that
manages the broker.
2. On the configuration tab's left panel, locate the broker configuration you want to
instrument.
3. Right click on the broker name, and then choose Properties.
4. Select the Monitoring tab.
5. Check the Enable Actional Instrumentation checkbox, and, optionally, whether to
enable capturing of each message's payload. You can specify the payload capture as
NONE, HEADER, BODY, or ALL (both header and body). The result of enabling SonicMQ
broker instrumentation and choosing to capture payload headers is as follows:
Figure 9. Enabled SonicMQ Broker Instrumentation
The log of the management container that hosts the broker immediately indicates the
status of the instrumentation, as shown for this example:
Code Sample 3. Broker’s Container Log of Actional Instrumentation Information
[date-time] ID=Br1 (info) Actional instrumentation is enabled with payload capture disabled
[date-time] ID=Br1 (info) Successfully connected to Actional agent
6. On the management container that hosts the broker, specify the location of the
uplink.cfg file. For more information, see “Specifying the Uplink Configuration
Location in Sonic” .
271 Progress Sonic ESB Configuration and Management Guide 8.5