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

More documents

Recommendations

Info

Chapter 3: Mapping ESB Artifacts to Target Domains For example, the following code sample is an end-to-end script that exports from a domain under defined roots, applies its defined map, produces several analysis reports, and then imports into a defined target domain using defined import rules: connect Domain1 releaseManager:2506 Administrator Administrator export archive c:\dev.xar c:\exportProperties.xml disconnect applyMap c:\dev.xar c:\2\map1.xml c:\2\mapped1.xar c:\2\mapped2_log.xml diff -xar c:\dev.xar -xar c:\1\mapped2.xar -out c:\2\vDiff_xar_xar2.xml -v diff -xar c:\dev.xar -xar c:\1\mapped2.xar -out c:\2\tDiff_xar_xar2.xml mqdepends -xar c:\2\mapped2.xar -out c:\2\mqDepends.xml mqrevdepends -xar c:\2\mapped2.xar -out c:\2\mqRevDepends.xml connect Domain2 StageTwo:2526 Administrator StageTwoPassword impact -xar c:\2\mapped2.xar -out c:\2\tImpact_XAR2_DS2.xml -ds Domain2 StageTwo:2526 Administrator StageTwoPassword impact -xar c:\2\mapped2.xar -out c:\2\vImpact_XAR2_DS2.xml -ds Domain2 StageTwo:2526 Administrator StageTwoPassword -v import archive c:\2\mapped2.xar c:\2\2_import.xml disconnect bye That series of commands in Sonic ESB Admin Tool syntax, when saved as a text file such as End2End.txt, lets you create a script file that pipes in the command sequence, such as: C:\Sonic\ESB8.5\bin\esbadmin < c:\2\End2End.txt Once defined, the sequence of steps in the illustration on page 61 can be scripted. The script overlaying the image in the following illustration shows an end-to-end development to deployment process that is reliable, consistent, and fully documented: Workbench Domain - ESB Artifacts - SonicFS files Directory Service Exported Deployment Archive Analysis of Directory Services, archives, and file stores Differences Impact analysis SonicMQ dependencies SonicMQ reverse dependencies Scripted Export Procedure, Mapping, and Import Deployment Domain Directory Service Import tailored archive - Connect to the Workbench Domain. - Export archive using the previously defined export properties Mapped Archive - Disconnect. Export D archive C E - Apply the map that was previously defined to map the exported archive for this deployment domain. Edit Map - Output the map log fileCreateMap A Parameters for Apply Map - Generate a report that for shows Archive the differences between thie exported archive and the mapped archive. Target Domain - Generate a report that shows the SonicMQ dependencies in the mapped archive. - Connect to the deployment domain Map File Edited Map File - Generate a report that shows Bthe impact of the mapped archive on this deployment domain. - Import into the deployment domain Tailoring using Rules the preeviously definred import rules. - Output the import log file. - Disconnect. - End the script. Tailoring and Map export archive Import Log File Map Log File 82 Progress Sonic ESB Deployment Guide 8.5 G H F
Incrementally Updating or Building Domains Incrementally Updating or Building Domains You can update the ESB elements in a domain or, for testing environments, initialize the domain so that only the packaged ESB elements populate the domain after import. Incrementally Updating a Domain When importing files into a target domain, the existing Directory Service is usually populated with existing ESB elements, as shown in the following illustration: UPDATE scripts Target Domain Directory Service POPULATED Import Rules - Overwrite - Ignore The changes you apply must reconcile the incoming files with existing files so that any potential file overwrites clearly determine whether the incoming files take precedence over (overwrite) the existing files or not (ignore). Update scripts must submit archives to the target domain in a specified sequence so that the decision to ignore or overwrite changes in multiple archives achieves the expected final result. The archive packaged after successful integration testing is imported into an advanced staging domain or production as an incremental update. In live stages, the more elaborate distributed resources and existing ESB elements are not easily decoupled, so their Directory Services are incremented by files selected in import properties files and matching files are resolved to determine which of the matched files is retained. Progress Sonic ESB Deployment Guide 8.5 83
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 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 132 and 133:
Chapter 6: Adapting Imported Servic
Page 134 and 135:
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?