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

More documents

Recommendations

Info

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
Implementing Domain Builds and Updates Implementing Domain Builds and Updates The next sections describe in detail the procedures for using the build and update strategies. Using the Build Strategy on a Static Target Domain The following steps describe how to use the build technique for a basic, static domain such as Developer Integration Testing. ◆ To implement build techniques for a Domain, complete the following tasks: 1. “Create a Base Level Directory Service Structure” on page 87 2. “Specify the Build Content” on page 88 3. “Run the Build for the Test Domains” on page 88 4. “Bind the ESB Elements to the Domain” on page 88 5. “Dump Endpoint Lists and Iterate Queue Creation” on page 88 6. “Test the Build” on page 89 The following sections detail each of these tasks. Create a Base Level Directory Service Structure A base level Directory Service is the foundation for many different deployment tests. Once you create it, you refresh the working Directory Service with the base level Directory Service to reset the domain, as detailed here: 1. On the system where you want to set up an integrated testing environment, use the Sonic Installer to install a Domain Manager with an MQ and an ESB license key. If you intend to deploy Sonic BPEL Server, enter its key as well. Start the Domain Manager’s container. 2. Connect to the domain through the Sonic Management Console to enhance the base: ■ Add some global services and endpoints to simplify initial bindings for mapped artifacts. See “Adjusting Dev Service and Dev Endpoint Maps” on page 69 for more about these mapping targets. ■ Set up management and ESB Containers that correspond to the development containers. For example, dit_Test and dit_Core. 3. Stop the Domain Manager. Archive this clean Directory Service store. 4. Save the backup archive file. You will use it routinely to refresh the build domain. Progress Sonic ESB Deployment Guide 8.5 87
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 36 and 37: 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 136 and 137:
Chapter 6: Adapting Imported Servic
Page 138 and 139:
Chapter 6: Adapting Imported Servic
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?