10.02.2013 Views

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 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 4: Analyzing <strong>ESB</strong> Artifacts in Archives, Stores, and File Systems<br />

Overview<br />

The decoupling of <strong>Sonic</strong> <strong>ESB</strong> artifacts from the underlying messaging infrastructure<br />

means that you must tune the artifacts and their parameters when you import them into a<br />

new domain. To help evaluate the potential changes, <strong>Sonic</strong> provides a set of analysis<br />

reports that extract differences and dependencies into XML files. The analysis reports<br />

discover and document variations in <strong>ESB</strong> artifact files and their content, and reveals<br />

<strong>Sonic</strong>MQ configuration parameters required by <strong>ESB</strong> artifacts.<br />

The analysis commands assess the files in a file store, archive, or directory service in three<br />

categories: XML, text, or binary. In an analysis that offers the -v verbose switch, not<br />

enabling the option provides a Boolean response to differences. A file’s extension<br />

classifies it for analysis and appropriate verbose information, as shown in this table:<br />

File Type Extensions Differencing Verbose [-v]<br />

XML .amap<br />

.bp<br />

.cbr<br />

.<strong>esb</strong>ws<br />

.<strong>esb</strong>db<br />

.prj<br />

.wsdl<br />

.xaction<br />

.xcbr<br />

.xml<br />

.xsd<br />

.xsl<br />

.xslt<br />

Text .bat<br />

.css<br />

.html<br />

.js<br />

.properties<br />

.sh<br />

.txt<br />

.xquery<br />

Binary .bpv<br />

.gif<br />

.jar<br />

.jpg<br />

.xar<br />

any other<br />

extension<br />

Requires XML<br />

equivalence. The order<br />

of elements is not<br />

significant—a series of<br />

tags listed in a different<br />

sequence is treated as<br />

equivalent.<br />

Reports on differences in the<br />

content of XML elements.<br />

The content (payload) of an<br />

element is case sensitive.<br />

XML tag names are not case<br />

sensitive.<br />

Exact textual match. Reported as in a standard text<br />

difference.<br />

Case sensitive.<br />

Exact binary match. Offset into the document of the<br />

first byte difference<br />

96 <strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Deployment</strong> <strong>Guide</strong> <strong>8.5</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!