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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 11: Using Actional with <strong>Sonic</strong> Components<br />

The hybrid visualization of the messages flowing through the endpoints on the brokers<br />

might look similar to the following for a st<strong>and</strong>alone service through a call to the dev.Run<br />

service:<br />

Figure 19. St<strong>and</strong>alone Service<br />

Specifying the Uplink <strong>Configuration</strong> Location in <strong>Sonic</strong><br />

You need to explicitly declare the location of the Actional Agent’s uplink.cfg file in the<br />

<strong>Sonic</strong> context. In <strong>Sonic</strong>, you do this by setting a Java System property in each<br />

management container configuration where Actional instrumentation is enabled.<br />

◆ To specify the location of the uplink.cfg file:<br />

1. In the <strong>Sonic</strong> <strong>Management</strong> Console, open (in turn) the Properties dialog box of each<br />

management container that hosts a messaging broker or <strong>ESB</strong> Container where you<br />

enabled Actional instrumentation.<br />

2. Choose the Environment tab.<br />

3. Click New.<br />

a. For the Variable, enter com.actional.lg.interceptor.config.<br />

b. For the Value enter a location for the file, usually a new folder within the Actional<br />

Agent directory.<br />

4. Click OK on the two dialog boxes<br />

283 <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!