esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...
esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...
esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Binding <strong>ESB</strong> Services to Messaging Nodes<br />
Binding <strong>ESB</strong> Services to Messaging Nodes<br />
You can import configurations into a domain that consists of only an <strong>ESB</strong>-aware domain<br />
manager. However, a distributed <strong>deploy</strong>ment environment typically constrains the domain<br />
manager’s messaging traffic to management traffic. Distributed broker installations are<br />
assigned to handle message traffic.<br />
Setting Up Distributed Messaging Nodes<br />
One of the first steps required after importing a <strong>deploy</strong>ment archive is binding<br />
connections and endpoints defined in <strong>ESB</strong> services to the new domain’s messaging<br />
environment. Often new messaging brokers are defined and <strong>deploy</strong>ed to host the<br />
connections and endpoints, especially in the initial stages of a distributed rollout. After<br />
the brokers are set up and configured, you can bind the connections and endpoints to the<br />
domain.<br />
See “Installing <strong>Sonic</strong>MQ Messaging Nodes in the Domain” in the <strong>Progress</strong> <strong>Sonic</strong><br />
Installation and Upgrade <strong>Guide</strong> for basic instructions on installing a messaging node.<br />
The administrator of the domain can set up broker clusters, fault tolerant brokers, and<br />
establish location-specific encryption and activation mechanisms for the <strong>deploy</strong>ed<br />
messaging nodes. See <strong>Sonic</strong>MQ <strong>Deployment</strong> <strong>Guide</strong> for details on broker architectures and<br />
topologies.<br />
Binding Connections to Host Ports in the New Domain<br />
After the messaging nodes are installed, you can bind the <strong>ESB</strong> connections defined in<br />
<strong>Sonic</strong>MQ Endpoints to acceptors on messaging nodes in the new domain.<br />
Important When you initially <strong>deploy</strong> into a new domain, be sure that you bind to connections on<br />
brokers in the new domain instead of perpetuating connections to messaging nodes in the<br />
source domain.<br />
The <strong>ESB</strong> connections such as http_defaultConnection and jms_defaultConnection are<br />
defined once in a domain. If you are hosting <strong>ESB</strong> services in a domain for the first time,<br />
you need to revise the connection URLs of the default <strong>ESB</strong> connections to the protocol,<br />
host, and port for corresponding acceptors set up on the stated host.<br />
<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Deployment</strong> <strong>Guide</strong> <strong>8.5</strong> 125