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

Chapter 3: Mapping ESB Artifacts to Target Domains
● A single deployment archive is exported from DIT for incremental update in User
Acceptance Testing (UAT) where it is tailored and passed through import rules. There
might be conflicts. When conflicts are resolved, an archive is exported.
● The UAT export archive carries the changes into production where, after tailoring, the
issue resolutions discovered in UAT are similarly applied.
Promotion Through Stages
Using this technique, satisfactory completion of a stage is characterized by notifying the
managers of the next stage that the version that it tested is ready for access, mapping, and
import from the same source, as illustrated:
Sonic Workbenches
Development Licenses
Eclipse Project Workspace
Checkout / Checkin
Update View
Source
Control
Repository
This illustration shows:
Runtime Deployments
Deployment Licenses
Staging and Test Environments
Developer
Integration
Read source files and artifacts in branch
Directory
Service
User
Acceptance
DIT UAT LIVE
Flush and
Restore with
'Clean' DS
DIT Mapped Archive
DIT Mapping Rules
BUILD
scripts
Production Environment
● The build strategy used in the Developer Integration Testing (DIT) environment is the
same used in the promotion-through-stages strategy.
● Advanced staging and the production environment build from the same source files
and import the same ESB artifacts as the DIT stage. This strategy keeps the path from
the release management branch to the target stages consistent and easier to reconcile
when errors are observed.
86 Progress Sonic ESB Deployment Guide 8.5
Directory
Service
Import Rules
- Overwrite
- Ignore
UAT Mapped Archive
UAT Mapping Rules
UPDATE
scripts
Directory
Service
Import Import Import
Import Rules
- Overwrite
- Ignore
LIVE Mapped Archive
LIVE Mapping Rules
UPDATE
scripts