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

More documents

Recommendations

Info

Chapter 3: Mapping ESB Artifacts to Target Domains Specify the Build Content The content of a build is typically determined by the release management team through their branch mechanisms in source control and their build scripts that build JARs and package ESB artifacts on the specified branch. Run the Build for the Test Domains When you want to do a build in developer integration testing, refresh the Directory Service, then import the archives. ◆ To run the build in integration testing: 1. Flush the existing structure by stopping the domain manager's container, and then deleting the Directory Service folder. 2. Recreate the Directory Service store from the base level Directory Service backup you created. 3. Use the Deployment Archive Import Tool to import the archives targeted for the build into the restored clean Directory Service store. Bind the ESB Elements to the Domain The components of the built domain must be bound to the domain infrastructure. ◆ To bind ESB elements to a domain: 1. Bind the connections and endpoints to the management node. If you did tailoring, these are key parameters of the mapping process, so you do not have to do them now. 2. Create management containers that connect to the management node. 3. Create ESB Containers for the imported services, then add the ESB Containers to appropriate management containers. Dump Endpoint Lists and Iterate Queue Creation Because queues are static objects, they must be explicitly created before they can be used. When a deployment contains many endpoints, you might want to programmatically set the queue endpoints on the appropriate messaging node. 88 Progress Sonic ESB Deployment Guide 8.5
◆ To dump endpoint lists and iterate queue creation: Implementing Domain Builds and Updates 1. In a dumped archive or file structure, create an iterator over the elements in ESB\Endpoints\. On each item, examine the file to see if type is QUEUE. For each queue item, output its destination value to a list. 2. Create an application based on the SonicMQ ConfigBean/CreateQueue sample that connects to the domain and then adds each listed item as a queue. Test the Build Run the services in the test domain. You might want to import the test plans into SonicFS. When the test run is complete, the Directory Service on the Developer Integration Testing system can be refreshed to the base level DS structure in preparation for the next build. After the developer tests are complete, archive export and import techniques are generally appropriate for advanced staging and production environments. Using the Update Strategy on Dynamic Target Domains The following procedure describes how to use the update strategy for complex, evolving domains such as User Acceptance Testing and the production environment. The dynamic nature of the configured SonicMQ objects in advanced staging or production makes it difficult to isolate a Directory Service that produces a base level, yet is cleared of all ESB elements. When you import into an existing logical structure, you risk file name conflicts that can cause new services or existing services to perform in unexpected ways. Further, incremental changes that are updates of existing deployments might no longer use some files that should be removed. The advantage of incremental deployments is that existing services are bound to management containers so only new elements must adapt to the new domain. ◆ To implement update techniques for a Domain, complete the following tasks: 1. “Build or Export the Set of Changes Moving into Deployment” on page 90 2. “Map Archives for the Target Domain” on page 90 3. “Review Developer Documentation on Setup and Cleanup” on page 90. 4. “Backup the Directory Service” on page 91 Progress Sonic ESB Deployment Guide 8.5 89
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:
Page 36 and 37:
Page 38 and 39: 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 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 ...

Create successful ePaper yourself

Delete template?

Save as template?