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

More documents

Recommendations

Info

Chapter 3: Mapping ESB Artifacts to Target Domains 5. “Run a Scripted Update Sequence” on page 91 6. “Evaluate Target Overwrites” on page 91 7. “Dump Endpoint Lists and Then Iterating Queue Creation” on page 93 8. “Manage Imports, Containers, and Installed Sonic Products” on page 93 9. “Evaluate Change Requirements in JavaScript, and ebXML Files” on page 93 10. “Test and Accept or Rollback” on page 93 The following sections detail each of these tasks. Note See “Importing Deployment Artifacts into a Domain” on page 105 for update techniques. Build or Export the Set of Changes Moving into Deployment Use the archive or file set methods described in Chapter 2, “Exporting ESB Artifacts for Deployment.” Map Archives for the Target Domain If you used the archive method, create and apply the map for the target domain. See “Applying Tailoring Rules and Creating a Map File for an Archive” on page 73 for more information. Review Developer Documentation on Setup and Cleanup Ideally, the development and QA teams add their test procedures and notes to the archive. For example, queues that are expected to see high traffic can be properly placed in highspeed clusters. Or, for updated deployments, any elements that are no longer in use can be deleted in the updated domain (a manual task). 90 Progress Sonic ESB Deployment Guide 8.5
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
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:
Page 40 and 41: 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 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?