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

More documents

Recommendations

Info

Chapter 3: Mapping ESB Artifacts to Target Domains Building ESB Elements into a Domain A build strategy is viable in a static domain where the physical installations are retained, but the Directory Service is discarded and a ‘clean’ base-level Directory Service is restored, as shown in the following illustration: BUILD scripts Target Domain Directory Service Flush and Restore with 'Clean' DS The base level Directory Service structure is the foundation for the next build. The build strategy is useful only when the underlying domain manager is static, a situation that exists only on Sonic Workbenches and its deployment analog, the Developer Integration Test (DIT) environment. Because the DIT domain manager is narrowly defined and rarely reconfigured, a basic setup of the domain manager can be created, ESB-enabled, and then backed up and stored offline. The build scripts start by deleting the existing DIT Directory Service and then restoring the Directory Service from its backup. As a result, the imported ESB elements will encounter no file matches and there are no orphaned files to delete. This build technique propagates the selected branch of the source control repository into the target domain. You can use these methodologies in different ways at different deployment levels. For example, the techniques for deployment from development to integration testing might be a build process, while advanced staging uses incremental changes. 84 Progress Sonic ESB Deployment Guide 8.5
Incrementally Updating or Building Domains Deciding on Export or Promotion Through Stages The flow or deployment sets from development to production can: ● Enter a stage, and then be redeployed to move to the next stage. ● Enter a stage, and then determine whether the original deployment set should enter the next stage. Many deployments build the initial stages and use incremental change in the later stages. Exporting Through Stages Using this technique, satisfactory completion of a stage is characterized by exporting the changes that will be applied in the next stage, as illustrated: Sonic Workbenches Development Licenses Eclipse Project Workspace Checkout / Checkin Update View Source Control Repository Read source files and artifacts in branch This illustration shows: Runtime Deployments Deployment Licenses Staging and Test Environments Developer Integration 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— refresh the base level Directory Service, tailor the incoming archives, then apply import (at this stage, you might ignore nothing and overwrite everything unless you have a series of archives). Progress Sonic ESB Deployment Guide 8.5 85 Export Directory Service Import Rules - Overwrite - Ignore UAT Mapped Archive UAT Mapping Rules UPDATE scripts Export Directory Service Import Import Import Promoted to UAT Released to Production Import Rules - Overwrite - Ignore LIVE Mapped Archive LIVE Mapping Rules UPDATE scripts
Page 1 and 2:
® ® PROGRESS® SONIC® Sonic ESB
Page 3 and 4:
the redistribution, if any, must in
Page 5 and 6:
the relevant code modules. All Righ
Page 7 and 8:
OF USE, DATA, OR PROFITS; OR BUSINE
Page 9:
products derived from this software
Page 12 and 13:
Contents Using the Deployment Expor
Page 14 and 15:
Contents Chapter 7: Updating a Revi
Page 16 and 17:
Preface About This Guide This guide
Page 18 and 19:
Preface Progress Sonic Documentatio
Page 20 and 21:
Preface 20 Progress Sonic ESB Deplo
Page 22 and 23:
Chapter 1: Introduction Roles in Re
Page 24 and 25:
Chapter 1: Introduction Developing
Page 26 and 27:
Chapter 1: Introduction ESB Artifac
Page 28 and 29:
Chapter 1: Introduction Different P
Page 30 and 31:
Chapter 1: Introduction 30 Progress
Page 32 and 33:
Chapter 2: Exporting ESB Artifacts
Page 34 and 35: Chapter 2: Exporting ESB Artifacts
Page 60 and 61: Chapter 3: Mapping ESB Artifacts to
Page 96 and 97: Chapter 4: Analyzing ESB Artifacts
Page 106 and 107: Chapter 5: Importing Deployment Art
Page 122 and 123: Chapter 6: Adapting Imported Servic
Page 134 and 135:
Chapter 6: Adapting Imported Servic
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Chapter 7: Updating a Revised Deplo
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Chapter 8: Distributed Deployment a
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Index ESBWS WSDL files external to
Page 164:
Index 164 Progress Sonic ESB Deploy
show all

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

Create successful ePaper yourself

Delete template?

Save as template?