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.
◆ To dump endpoint lists and iterate queue creation:<br />
Implementing Domain Builds and Updates<br />
1. In a dumped archive or file structure, create an iterator over the elements in<br />
<strong>ESB</strong>\Endpoints\. On each item, examine the file to see if type is QUEUE. For each queue<br />
item, output its destination value to a list.<br />
2. Create an application based on the <strong>Sonic</strong>MQ ConfigBean/CreateQueue sample that<br />
connects to the domain and then adds each listed item as a queue.<br />
Test the Build<br />
Run the services in the test domain. You might want to import the test plans into <strong>Sonic</strong>FS.<br />
When the test run is complete, the Directory Service on the Developer Integration Testing<br />
system can be refreshed to the base level DS structure in preparation for the next build.<br />
After the developer tests are complete, archive export and import techniques are generally<br />
appropriate for advanced staging and production environments.<br />
Using the Update Strategy on Dynamic Target Domains<br />
The following procedure describes how to use the update strategy for complex, evolving<br />
domains such as User Acceptance Testing and the production environment. The dynamic<br />
nature of the configured <strong>Sonic</strong>MQ objects in advanced staging or production makes it<br />
difficult to isolate a Directory Service that produces a base level, yet is cleared of all <strong>ESB</strong><br />
elements.<br />
When you import into an existing logical structure, you risk file name conflicts that can<br />
cause new services or existing services to perform in unexpected ways. Further,<br />
incremental changes that are updates of existing <strong>deploy</strong>ments might no longer use some<br />
files that should be removed.<br />
The advantage of incremental <strong>deploy</strong>ments is that existing services are bound to<br />
management containers so only new elements must adapt to the new domain.<br />
◆ To implement update techniques for a Domain, complete the following tasks:<br />
1. “Build or Export the Set of Changes Moving into <strong>Deployment</strong>” on page 90<br />
2. “Map Archives for the Target Domain” on page 90<br />
3. “Review Developer Documentation on Setup and Cleanup” on page 90.<br />
4. “Backup the Directory Service” on page 91<br />
<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Deployment</strong> <strong>Guide</strong> <strong>8.5</strong> 89