Progress Sonic ESB Configuration and Management Guide

License Container Commands
merge (standard form)
merge -storeType storeParams -storeType storeParams [-out outFile.xml] [-v]
where:
● The first -storeType storeParams identifies the source artifact store, and
the next -storeType storeParams identifies the target artifact store.
● storeType is { xar | fs | ds }.
● storeParams are:
■ When storeType is xar, the archive location on a file system
■ When storeType is fs, the root of the hierarchy on a file system
■ When storeType is ds, the management connection to a domain in the form:
domain url [username password] [managementNode]
● The out parameter lets you specify the preferred location of the .xml file that reports
on the analysis. If you do not specify an output file, a default file (Sonic_Merge.xml)
is created in the ESB Container’s working directory
● -v requests verbose reporting
For example, to merge an archive into a Directory Service store:
merge -xar sourceStore.xar -ds Domain1 myHost:2506 aUser aPwd -out c:\out.xml
merge (compound form)
A variation in the syntax of the merge command enables the merger of two source stores
into a target store. As a result, the target store is acted on but the two source stores are
unmodified. The source and target stores can be XAR files, file systems, or Directory
Service stores.
The syntax of the advanced merge command in the Sonic ESB Admin Tool is:
merge -sourceStore1Type sourceStore1Params
-sourceStore2Type sourceStore2Params
-targetStoreType targetStoreParams
[-out outFile.xml]
[-v]
where the variation from a standard merge is that sourceStore1 and sourceStore2 are two
distinct source types with their respective parameters that will be sequentially merged into
the target store.
For example, to merge a XAR and a file system into a target file system:
merge -xar source.xar -fs C:/sourceDir/ESB -fs C:/targetDir/ESB -out c:\out.xml
Progress Sonic ESB Configuration and Management Guide 8.5 52