10.02.2013 Views

Progress Sonic ESB Configuration and Management Guide

Progress Sonic ESB Configuration and Management Guide

Progress Sonic ESB Configuration and Management Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Instrumenting <strong>Sonic</strong>MQ<br />

Instrumenting <strong>Sonic</strong>MQ<br />

<strong>Progress</strong> <strong>Sonic</strong>MQ broker installations include the actional-sdk.jar in the <strong>Sonic</strong>MQ<br />

library archives <strong>and</strong> the <strong>Sonic</strong>MQ interceptor in the broker.jar.<br />

When a <strong>Sonic</strong>MQ broker is enabled for Actional instrumentation, <strong>and</strong> both the broker <strong>and</strong><br />

agent are running, <strong>Sonic</strong>MQ interceptors are in the flow between the message producers<br />

<strong>and</strong> message consumers. They intercept all inbound <strong>and</strong> outbound messages <strong>and</strong> feed<br />

information about those interactions to the agent as asynchronous events. The <strong>Sonic</strong>MQ<br />

interceptor maps the messaging interactions on an instrumented broker to Actional levels<br />

as follows:<br />

Actional Level <strong>Sonic</strong><br />

1 Host Name<br />

2 <strong>Sonic</strong> Node Name :: Broker Name<br />

3 Destination Name<br />

4 -<br />

A <strong>Sonic</strong>MQ message flow from producer to consumer, when visualized in the Actional<br />

<strong>Management</strong> Server, might look similar to the following:<br />

Figure 8. <strong>Sonic</strong>MQ Message Flow<br />

where producer P1 published to topic T.1 on broker br3 (a member of <strong>Sonic</strong> cluster that is<br />

referenced as <strong>Sonic</strong> routing node A). Subscribers S1<strong>and</strong> S2 are active consumers on broker<br />

br3 with patterns that include the T.1 topic<br />

Enabling the <strong>Sonic</strong>MQ Interceptor<br />

The <strong>Sonic</strong>MQ Interceptor is installed whenever a <strong>Sonic</strong>MQ broker is installed on a<br />

system. The interceptor is not, by default, enabled. In order to use the Actional Agent to<br />

manage services <strong>and</strong> processes on a system, you must install <strong>and</strong> provision the Actional<br />

Agent on the system where the <strong>Sonic</strong>MQ broker runs, <strong>and</strong> then enable the interceptor by<br />

making configuration changes to the <strong>Sonic</strong>MQ broker, typically through the <strong>Sonic</strong><br />

<strong>Management</strong> Console. Actional integration is set on each broker running on a system.<br />

<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Management</strong> <strong>Guide</strong> 8.5 270

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!