esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...

Chapter 4: Analyzing ESB Artifacts in Archives, Stores, and File Systems
Reporting on Impact Analysis
An impact analysis report combines aspects of “Reporting Differences” and “Reporting
on SonicMQ Reverse Dependencies.” Together, these features define the impact on the
target store that would result from merging the source store into the target store.
Because this report provides impact, the following information is also included:
● If a binary file type is different, the impact analysis report indicates that the file in the
source store will overwrite the one in the target store.
● If a file exists in the source store but not in the target store, the impact analysis report
indicates that a new file will be added to the target store.
However, if a file exists in the target store but not in the source store, it is not reported,
as it is not impacted and will not be affected by any import actions.
● If a dependency indicates that SonicMQ configuration objects must be created, the
impact analysis report describes the requirement.
Conversely, if existing SonicMQ configuration objects are no longer required by
ESB, the impact analysis report notes that fact. (There might be non-ESB related
references to a SonicMQ configuration.)
The syntax of the impact command in the Sonic ESB Admin Tool is:
impact -storeType storeParameters -storeType storeParameters
[-out outputFile.xml] [-v]
where:
■ The first -storeType storeParameters identifies the source artifact store, and
the next -storeType storeParameters identifies the target artifact store.
■ storeType is { xar | fs | ds }.
■ storeParameters 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:
domainName hostname:port [user password]
■ outputfile is the preferred target XML file name and location for the analysis
report on the file system. When you do not specify this parameter, the output file
is created as Sonic_ImpactAnalysis.xml in the tool’s directory.
■ -v requests verbose reporting (otherwise, you get terse reporting).
Assessing impact on a Directory Service store requires a connect command to establish a
connection to the domain prior to running impact.
102 Progress Sonic ESB Deployment Guide 8.5