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.
Using Scripted Builds to Export <strong>ESB</strong> Artifacts<br />
Extending Ant Scripts For Mapping and Import Functions<br />
When you use scripted builds to export <strong>ESB</strong> artifacts for <strong>deploy</strong>ment, you probably want<br />
to integrate the export script with the Java build process and the import process.<br />
You should also handle domain mapping functions (an archive-only process) and<br />
accessing <strong>ESB</strong> Admin commands from within the Ant script.<br />
As described in “Mapping <strong>ESB</strong> Artifacts to Target Domains” on page 59, mapping is an<br />
archive-only operation. You can manage that in your script by moving your <strong>ESB</strong> artifacts<br />
into a <strong>Sonic</strong> <strong>deploy</strong>ment archive form, doing the mapping from defined map definition<br />
files for the target domain, and then importing the mapped archive into the target domain.<br />
The following excerpted procedures outline these operations. The example uses these<br />
variables you might want to consider in your scripts:<br />
<br />
<br />
<br />
<br />
<br />
<br />
● Packaging a set of files into a XAR file:<br />
<br />
<br />
<br />
<br />
<br />
● Launching the <strong>ESB</strong> Admin Tool and then directing mapping scripts to run:<br />
The XQCommandline launches the <strong>ESB</strong> Admin Tool. The xarmapfile property specifies<br />
a script that is redirected into the <strong>ESB</strong> Admin Tool.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Deployment</strong> <strong>Guide</strong> <strong>8.5</strong> 57