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

Defining Scripts to Automate Deployment
Defining Scripts to Automate Deployment
The preceding tasks created work files to enable scripting of the same process. The steps
in Table 1 show how the steps can be used in scripts once their files are defined.
Table 1. The Deployment Process Steps from Initial Deployment to Scripted Deployment
Step Initial Use Subsequent use
a Export archive X from
source domain
Define export roots from
domain into a Sonic Archive
(XAR) file.
b Adjust tailoring rules No action required, but adjust
as needed.
c Create map for
archive X
d Edit archive X map for
target domain Y
e Apply map to archive
X and create archive Y
f Create X-Y analysis
reports
createMap command,
referencing tailoring rules when
not using the default file
Adjust values of exposed
parameters and string
references.
applyMap command to exported
archive referencing the map file
and naming the mapped archive
Use interactively to discover
which types suit your
requirements.
g Review Y map log See if changes were applied as
expected.
h Define / review
Y import rules then
Import into Y domain
Select overwrites and deselect
features not to apply.
Import through GUI tool to
create import rules.
Connect to domain and then
rebuild using the predefined
roots.
No action required. -
You reuse maps after they are
edited so they are recreated
only when basic changes
occur.
Minor edits usually tune the
archive for changes in the
target.
applyMap command to
exported archive referencing
the map file and naming the
mapped archive
Define a set of analyses that
are tied closely to an export
script.
Could be generated to standard
output to document the
scripted process.
Stored import rules can be
accessed by scripts.
import command with import
rules or merge.
Used in
Scripts?
Progress Sonic ESB Deployment Guide 8.5 81
Yes
-
-
Yes
Yes
Yes
Yes