Progress Sonic ESB Configuration and Management Guide

Chapter 2: ESB Containers
3. In the ESB Container Maintenance section, specify the following properties:
Property Description
Name The name of the ESB container.
Intra-container
Messaging
ESB (JMS)
Connection
HTTP Routing
Connection
Select to allow the container to bypass the overhead of sending and
receiving messages to and from endpoints when the services in that ESB
process reside in the same container.
Also used for all OUTBOX processing where dynamic routing is indicated
(when the target destination is a remote destination such as NodeA::T1).
For more information, see the Progress Sonic Workbench User Guide in the Eclipse help.
4. In the Actional Integration section, specify the following properties:
Property Description
Enable Actional
Instrumentation
Enable Payload
Capture
Specify the ESB connection used to call web services deployed on the
ESB (in contrast to those available at an external HTTP address.)
Specify the HTTP routing connection to the SonicMQ broker that is used
for web services with HTTP addresses.
Select this option to enable Actional Server visualization on this ESB
container. By default, the option is not selected (unchecked). See the
chapter on “Instrumenting Sonic ESB” in the Actional Interceptor
Guide.
When Actional instrumentation is enabled, declares whether the
instrumentation should include the message body.
Note Payloads are only reported when required by policy defined in Actional. When
Enable Payload Capture is not checked for a container, no payloads are reported
(regardless of policy in Actional). When payload is requested, all message parts are
reported to Actional.
The Actional Integration feature requires Progress Actional software products to
provide visibility, control, and enforcement of deployed assets. This Sonic release is
59 Progress Sonic ESB Configuration and Management Guide 8.5