10.02.2013 Views

Progress Sonic 8.0 ESB Configuration and Management Guide

Progress Sonic 8.0 ESB Configuration and Management Guide

Progress Sonic 8.0 ESB Configuration and Management Guide

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 1: Using <strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Management</strong> Tools<br />

diff<br />

diff -storeType storeParams -storeType storeParams [-out outFile.xml] [-v]<br />

The diff comm<strong>and</strong> assesses the difference between two artifact stores. Unlike a generic<br />

differencing engine, the <strong>ESB</strong>Admin diff only assesses specific filetypes in certain store<br />

types. The stores can be <strong>Sonic</strong> archive files—XAR files—(-xar store type), file systems<br />

(-fs store type), or Directory Service stores (-ds store type).<br />

Differences include:<br />

● Artifacts that are in both stores yet do not have identical content. You can choose to<br />

identify only that the files are dissimilar or to expose the differences in detail.<br />

● Artifacts that are in the source store but not in the target store<br />

● Artifacts that are in the target store but not in the source store<br />

As an example, a comm<strong>and</strong> comparing a XAR file with a Directory Service store is:<br />

diff -xar sourceStore.xar -ds Domain1 myHost:2506 aUser aPassword<br />

mqdepends<br />

mqdepends -storeType storeParams -out outputFile.xml<br />

[-include artifact1 [artifact2 ...] | -includeFile artifactListFile]<br />

where the optional parameters include:<br />

● artifact1 artifact2 ...(a series of specific files in the store to analyze)<br />

● artifactListFile (a text file that provides a list of files in the store to analyze)<br />

The mqdepends comm<strong>and</strong> assesses a source artifact store to evaluate <strong>and</strong> report on the<br />

dependencies of <strong>ESB</strong> artifacts on <strong>Sonic</strong>MQ configuration objects. You can use this<br />

information to create or verify the existence of the specified dependencies in a target<br />

Directory Service store. The stores can be a <strong>Sonic</strong> archive file, file system, or a Directory<br />

Service store.<br />

<strong>Sonic</strong> <strong>ESB</strong> dependencies on <strong>Sonic</strong>MQ artifacts include:<br />

● Endpoints for their destination dependencies (topics, queues, or routing).<br />

● <strong>ESB</strong> connections for <strong>Sonic</strong>MQ connection parameters (<strong>and</strong>, therefore, the broker<br />

location <strong>and</strong> port where static destinations must be created.<br />

As an example, to produce a dependency report on specified files:<br />

mqdepends -fs C:/myinstalldir/<strong>ESB</strong> -include processA serviceA serviceB<br />

44 <strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Management</strong> <strong>Guide</strong> <strong>8.0</strong>

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

Saved successfully!

Ooh no, something went wrong!