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.

Chapter 2: <strong>ESB</strong> Containers<br />

interceptor <strong>and</strong> forwards statistical information to an instance of the Looking Glass Server<br />

(also available separately).<br />

The Actional Agent can analyze Web service <strong>and</strong> JMS traffic on the Enterprise Service<br />

Bus. When you enable Actional’s interceptor technology on existing <strong>ESB</strong> infrastructures,<br />

the Analyzer lets you gather data from this interceptor <strong>and</strong> communicate with an instance<br />

of Actional Server.<br />

The Actional <strong>ESB</strong> Interceptor is included in an <strong>ESB</strong> installation; however, it is not<br />

enabled by default. To use the Actional Agent to manage <strong>ESB</strong> services <strong>and</strong> processes,<br />

connect the <strong>Sonic</strong> <strong>Management</strong> Console to a <strong>Sonic</strong> domain you want to instrument, <strong>and</strong><br />

then select the option to Enable Actional Instrumentation on each <strong>ESB</strong> Container you<br />

want to enable, as shown:<br />

To activate an enabled interceptor requires that the Actional Agent is installed <strong>and</strong><br />

running, <strong>and</strong> that the Agent node is under management by an Actional Server.<br />

If the Actional Agent is not running before the instrumented <strong>Sonic</strong> <strong>ESB</strong> Containers are<br />

started, you must restart the enabled <strong>Sonic</strong> <strong>ESB</strong> Containers to activate the Actional<br />

visualization feature.<br />

Important If the Actional Agent is installed with a non-default \link directory (the directory where<br />

the Actional Agent creates Uplink.cfg), you must specify the path to the link directory<br />

as a Java system property on the Environment tab of each management container’s<br />

properties with the Variable name com.actional.lg.interceptor.config <strong>and</strong>, for the<br />

Value, the complete path, such as usr1/aUser/Actional/ActionalAgent/LG.Interceptor.<br />

Note When using Actional to view an <strong>ESB</strong> process that makes a SOAP web service call, the<br />

display might not be correct if that web service is running on a machine which is under<br />

Actional management. The process <strong>and</strong> the remote web service might appear to be<br />

disconnected. To view these interactions properly, remove the web service from<br />

management through the Actional Server administration interface. Web services that are<br />

running on unmanaged Actional nodes are not affected by this <strong>and</strong> render correctly.<br />

See www.progress.com/actional for more information. The “Instrumenting <strong>Sonic</strong> <strong>ESB</strong>”<br />

chapter in the Actional Interceptor <strong>Guide</strong> in the Actional Agent documentation set<br />

provides details <strong>and</strong> illustrations of this feature.<br />

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

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

Saved successfully!

Ooh no, something went wrong!