Progress Sonic ESB Configuration and Management Guide

Multiple Brokers, Clusters, and Nodes
Evaluating Endpoint Requirements on JMS Destinations
The ability to access services over the underlying SonicMQ messaging layer is an
important consideration when a Progress Sonic ESB service calls out to other services and
expects a reply, or when a Progress Sonic ESB process connects many ESB services.
Sonic’s Dynamic Routing Architecture (DRA) is a robust, secure way to send messages
through a broker or cluster of brokers to a destination on another broker or cluster. (In
routing, each broker or cluster is a routing node. For more information on DRA, clusters,
and routing nodes, see the “Multiple Nodes and Dynamic Routing” and “Clustered
Brokers” chapters in the Progress SonicMQ Deployment Guide.)
In multi-node domains, Progress Sonic ESB uses DRA to make fewer direct connections
to remote nodes by using the ESB (JMS) connection and DRA routes to send to remote
nodes. (Every ESB Container has an ESB (JMS) connection. See “Creating ESB
Containers” on page 58 for information on specifying the ESB Container connection.)
When a message is sent to a node-qualified destination, the ESB (JMS) connection is used
to send the message to the broker associated with the ESB Container on the bus. You
configure an endpoint using a node-qualified queue or topic name to reference a queue or
topic on a remote node to which the client (ESB service) is not connected. For example,
you can configure the ESB (JMS) connection to NodeA (a routing node) and an endpoint
based on queue, NodeB::Q2. Messages travel over the DRA connection of NodeA to NodeB.
Progress recommends using this node-qualified syntax as a best practice, as it avoids
making new connections from an ESB Container to all the remote nodes. Progress
recommends using the node-qualified syntax even if you are not running over DRA—
doing so eases the transition if you decide to implement DRA in the future.
The bus connection broker must have DRA routes defined for each of the remote nodes
that can be sent to. If not, sent messages go to the broker’s dead message queue (DMQ).
Important If the DRA connection fails, the message goes to the DMQ rather than to the rejected
message endpoint (RME), provided the message is sent PERSISTENT and
JMS_SonicMQ_preserveUndelivered and JMS_SonicMQ_notifyUndelivered are set to true
(the Progress Sonic ESB QoS is AT_LEAST_ONCE or EXACTLY_ONCE on the process.) For
more information, see the Progress Sonic Workbench User Guide in the Eclipse help.
The only time the bus connection is not used is when the node is sonic.http, an HTTP
outbound routing node. In this case, the ESB Container’s HTTP connection is used, as in
outbound web service invocations. (For more information, see the Progress Sonic
Workbench User Guide in the Eclipse help.)
Progress Sonic ESB Configuration and Management Guide 8.5 102