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

Backup the Directory Service
Implementing Domain Builds and Updates
Before starting incremental changes, you should stop the management container, and then
back up the Directory Service store before you perform archive imports. If imports and
regression testing do not succeed, you can revert gracefully to the prior configuration.
Important An import procedure that considers restoration of the Directory Service as a recovery
technique should lock out administrative changes to the Directory Service until the
import is complete and verified. When you start the domain manager after backup, you
could revise the password for administrative users until the import procedure is complete
and then change it back.
Another tactic is to install the administrator tools on the target domain manager system.
Then, when the import file is copied to that system, the domain manager can drop its
network connections until the local user completes the import procedure (or restores the
previous directory service.) That tactic can be quite effective when using fault tolerant
management components at a remote site. In that case, when you back up the primary
Directory Service and copy it to the backup location, set it to not accept updates. Then,
when you take the primary Directory Service offline the failover is to the current data set
as read-only. After the import session is complete, failback to the primary Directory
Service resumes as write-enabled.
Run a Scripted Update Sequence
If you use archives in the advanced stages, the flow of updates might result in more than
one archive loading to achieve the update. In that circumstance, you might want to script
the process so that any overwrites in the import properties are consistently applied in later
stages.
See “Defining Scripts to Automate Deployment” on page 81 for information on creating
and applying scripts.
Evaluate Target Overwrites
When deployment elements reach advanced staging and production, you must decide
whether or not to overwrite on a file match. In the absence of a timestamp, you cannot
choose to have “newer” overwrite “older.” Developer documentation and file
management techniques can make these decisions easier. For example:
● Use comments in XML files to record change history — When you add notes to
XML files (actually, any files), you continue the established programmer tradition of
maintaining change history.
Progress Sonic ESB Deployment Guide 8.5 91