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

More documents

Recommendations

Info

Chapter 7: Updating a Revised Deployment Changing a Root Element You can also make changes to the configuration used as a root element before rebuilding. In the example process, the ErrorEndpoint is removed as a step. It is replaced by an invocation step to an ErrorService. This is an ESB service called using sonicfs://Resources/ErrorService.esbws. When the archive is rebuilt it will have the following changes: ● Addition of sonicfs://Resources/ErrorService.esbws. ● The endpoint, ErrorEndpoint, is no longer included in the archive. Note Reimporting the rebuilt archive overwrites the ExampleProcess. However, it does not remove the ErrorEndpoint from the target domain. You must do this manually, Rebuilding the Export Package with the ESB Admin Tool When you have identified the XAR and, if necessary, edited the ExportProperties.xml file, you can recreate the package by either: ● “Using the Export Archive Command” on page 52 ● “Using the Export FS Command” on page 53 Modifying the Import Rules for the Target Domain In the target domain, you want to control importing a revised deployment so that it concentrates on the areas of change. The developer preparing the archive should generate a corresponding import properties template for the changes that includes: ● Overwritten Elements — When you are importing changes that you want to definitely replace a matching file at the same location, choose to overwrite in the import properties to ensure that the changes are accepted. ● Ignored Elements — Setting the ignore flag on branches and files that are dependencies and supporting files but are known to have not changed, minimizes the rebinding in the target domains. ● Leftover Elements — Elements that are no longer meaningful should be removed from the target domain. For example, if the original archive had services A, B, C, and D and the revised package uses only A and D, the developer should include an update note in the project folder that recommends deletion of services B and C in the updated domain. 142 Progress Sonic ESB Deployment Guide 8.5
Using the ESB Admin Tool to Rebuild a XAR or File Store ● Overrides — If you are only adding to the previous archive, change the import option to clear Override Existing Files (= ‘FALSE’) to prevent changing any of the endpoints/configurations previously modified. ● Roots — You could change the nature of an archive by deleting roots and adding new ones. When everything is being packaged for the first time, it is in effect a new archive. But if there are some parts of the archive that were packaged and imported in other domains, rebuilding the archive rebuilds it from scratch, not incrementally. Deploying a Rebuilt XAR or File Store with ESB Admin Tool The following procedure describes how to use the ESB Admin Tool to import a rebuilt archive or rebuilt file store into a target domain. When you have rebuilt the export package and tuned the import rules, you can recreate the package according to its type: ● For an archive, see “Using Import Properties” on page 116 ● For an file store, see “Using the Import FS Command” on page 117 Progress Sonic ESB Deployment Guide 8.5 143
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:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Chapter 3: Mapping ESB Artifacts to
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93: Chapter 3: Mapping ESB Artifacts to
Page 94 and 95: 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 144 and 145: Chapter 7: Updating a Revised Deplo
Page 146 and 147: Chapter 8: Distributed Deployment a
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?