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

More documents

Recommendations

Info

Chapter 7: Updating a Revised Deployment Using Deployment Tools to Rebuild and Deploy a XAR The Deployment Export Tool contains an ExportProperties.xml file that you can edit interactively in the graphical tool. Then, use the Deployment Import Tool to bring the rebuilt archive’s contents in to the target domain. ◆ To rebuild an archive with the Deployment Export Tool: 1. Start the ESB Deployment Export Tool. 2. Connect to the source domain and open the archive you want to change. 3. Add or remove configurations, files, and roots. 4. Choose Rebuild. 5. Save the rebuilt archive. You can choose to save the archive under a different name. The export tool recreates the archive with any changes and a redefined ExportProperties.xml file. You might want to tune the import properties before importing the rebuilt archive into the target domain. See “Modifying the Import Rules for the Target Domain” on page 142 for more information. ◆ To import a rebuilt archive with the Deployment Import Tool: 1. Start the ESB Deployment Import Tool. 2. Open the rebuilt archive. 3. 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. In the previous example with exampleProcess, you would specify to overwrite everything except: ■ Endpoints ■ Connections 4. Connect to the target domain. 5. Complete the import. In the example exampleProcess, the procedure imports the three additional files. 140 Progress Sonic ESB Deployment Guide 8.5
Using the ESB Admin Tool to Rebuild a XAR or File Store Using the ESB Admin Tool to Rebuild a XAR or File Store When using the ESB Admin Tool commands, if you want to modify the export properties, you must edit the file before running an export command. Modifying ExportProperties.xml You can rebuild an ESB artifact package to regenerate the package with different or changed roots if the package contains ExportProperties.xml. That file is produced in most cases and is stored at the root level of export packages, specifically: ● In a XAR produced by either the Deployment Export Tool or the ESB Admin Tool command export xar ● In a file store produced by the ESB Admin Tool command export fs See “Editing ExportProperties.xml” on page 35 for more information. Adding Additional Configurations or Files You can add files that were not included in an export package. In the exampleProcess, the following files were referenced indirectly by files that were included in the archive: ● File: sonicfs://Resources/myHelperFiles.js ● File: sonicfs://Resources/soap-imports.xsl To obtain these files, go to the source domain, open the archive, and explicitly add these files. The packaging rules will then explicitly include three items—the ExampleProcess, plus the two files. Then see “Rebuilding the Export Package with the ESB Admin Tool” on page 142 and “Deploying a Rebuilt XAR or File Store with ESB Admin Tool” on page 143. Progress Sonic ESB Deployment Guide 8.5 141
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: 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 142 and 143: 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?