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 ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 6: Adapting Imported Services to a Domain<br />
Enabling and Updating <strong>Sonic</strong> <strong>ESB</strong> Service Containers<br />
Once the messaging nodes are established for the connections and endpoints in the target<br />
domain, the distributed systems and containers can be implemented.<br />
Installing Distributed Systems with <strong>Deployment</strong> Software<br />
On the computer systems that will run the services being <strong>deploy</strong>ed, install the appropriate<br />
software for the services. For example, the software for <strong>ESB</strong> requires installing the<br />
<strong>Sonic</strong>MQ Container feature and then installing the <strong>Sonic</strong> <strong>ESB</strong> Container feature. See<br />
<strong>Progress</strong> <strong>Sonic</strong> Installation and Upgrade <strong>Guide</strong> for instructions on all <strong>deploy</strong>ment<br />
installations. The <strong>Sonic</strong> Installer requires that you use <strong>deploy</strong>ment licenses to install<br />
distributed components.<br />
Determine what <strong>ESB</strong> Containers need to be installed from the archive. When you create<br />
<strong>ESB</strong> Containers on distributed systems, the installation creates the named <strong>ESB</strong> Container<br />
and a similarly named management container. The remote installation registers the<br />
installation in the Directory Service and creates its boot file. It can run but has no assigned<br />
services.<br />
Then, when you import the archive, the <strong>ESB</strong> Container and any associated services and<br />
classpaths can overwrite the <strong>deploy</strong>ed <strong>ESB</strong> Container to complete the service<br />
configuration.<br />
Checking for Elements That Might Not Have Been Exported<br />
Chapter 1, “Introduction,” described how <strong>deploy</strong>ment archives can package all the files<br />
needed to transfer between development domains or move into <strong>deploy</strong>ment.<br />
Elements that need adjustment in the target domain are:<br />
● Classes External to <strong>Sonic</strong>FS — If you did not import additional classes or JAR files<br />
and include them in the <strong>deploy</strong>ment package, they must be moved to the <strong>deploy</strong>ment<br />
domain and relocated in the same relative position to the <strong>Sonic</strong> installation as they<br />
were in the source domain.<br />
● <strong>ESB</strong>DB Scripts and <strong>ESB</strong>WS WSDL Files External to <strong>Sonic</strong>FS — <strong>ESB</strong>DB scripts and<br />
<strong>ESB</strong>WS WSDL files can be stored on a file system outside the Directory Service.<br />
When that is the case, these files are not exported by the <strong>deploy</strong>ment tool. You can<br />
choose to add them into <strong>Sonic</strong>FS as runtime elements. You might need to relocate<br />
them in the target domain to the same relative location outside <strong>Sonic</strong>FS in the target<br />
domain after importing them.<br />
132 <strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Deployment</strong> <strong>Guide</strong> <strong>8.5</strong>