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.
<strong>Sonic</strong> Build and <strong>Deployment</strong> Tools<br />
Creating <strong>Deployment</strong> File Sets with Scripted Builds of Projects<br />
Source Control<br />
Repository<br />
Scripted builds evaluate the <strong>ESB</strong> artifacts in all projects in a storage location to provide<br />
fine-grained packaging. In a build script, you specify the source locations in a properties<br />
file, and the location of output <strong>ESB</strong> artifact file sets. Running a specialized Ant build’s<br />
instructions against the script exports the artifacts.<br />
1. Script defines projects to build<br />
As illustrated:<br />
2. Build emulates an upload<br />
4. Build Java sources for Projects into JARs<br />
3. Build exports <strong>ESB</strong> Artifacts into File System<br />
1. A properties script specifies the root locations of the source files, and the target<br />
location of the output files.<br />
2. The Ant build of the <strong>ESB</strong> artifacts evaluates the specified projects to determine the<br />
<strong>ESB</strong> artifacts and their dependencies<br />
3. The Ant build exports the <strong>ESB</strong> artifacts as a set of files in the file system.<br />
4. A separate procedure builds the Java source files into <strong>deploy</strong>ment JARs.<br />
Both builds could run as one to automate the complete build process.<br />
Export to<br />
File System<br />
Note Scripted builds do not export <strong>Sonic</strong> BPEL Server projects complete for <strong>deploy</strong>ment.<br />
<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Deployment</strong> <strong>Guide</strong> <strong>8.5</strong> 41