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.
Chapter 2: Exporting <strong>ESB</strong> Artifacts for <strong>Deployment</strong><br />
Using the Export Archive Command<br />
The export archive command syntax creates an archive file based on the properties or<br />
action specified in the command line:<br />
<strong>ESB</strong>Admin> export archive target.xar [source.xar | export-prop.xml | all]<br />
where:<br />
■ target.xar is the path and name of the file (using the .xar extension) that is the<br />
<strong>deploy</strong>ment export package. If the archive file exists, it is overwritten.<br />
■ Use one of the following arguments:<br />
❑ source.xar — When an existing archive filename is specified, the export<br />
performs according to the export properties file located in that archive file,<br />
putting the results in the target archive file. If source and target are the same<br />
file, the archive is rebuilt.<br />
❑ export-prop.xml — If the argument is an .xml file with well-formed and<br />
valid export properties, the export performs according to that export<br />
properties file, putting the results in the target archive file. This is an<br />
advanced concept; typically, source.xar or all are used.<br />
❑ all — All elements in the Directory Service are packaged in the archive file.<br />
For example, you might periodically script a backup archive to check in to source control:<br />
<strong>ESB</strong>Admin> export archive backup_myProject.xar all<br />
52 <strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Deployment</strong> <strong>Guide</strong> <strong>8.5</strong>