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

More documents

Recommendations

Info

Chapter 5: Importing Deployment Artifacts into a Domain Importing an ESB Artifact Store Into a Domain After you establish (or open a saved) import properties file, the import process into a domain is a straightforward task that logs actions and anomalies. Note An ESB artifact store can be imported to more than one target domain. You can define an import properties file unique to each target domain. ◆ To import a deployment ESB artifact store into a domain: 1. Start the Deployment Import Tool, as described on page 107. 2. Open the ESB artifact store you want to import, as follows: ■ Open an archive file by choosing File > Open XAR. Select an exported Sonic archive file (*.xar) and click Open. ■ Open a file store by choosing File > Open File System. Select the root of an exported Sonic ESB artifact file store and click Open. 3. To overwrite or ignore any of the content, define import properties or open an existing import file, as described on page 108. 4. Choose Domain > Connect. In the Domain Connection dialog box, enter the connection information for the domain to which you want to import configurations. 5. Select Actions > Import. The files selected are imported into the domain. 112 Progress Sonic ESB Deployment Guide 8.5
Validating Imported Elements Using The Deployment Archive Import Tool You should confirm the imported elements, especially if you ignored some elements on the import. Another case for validation is when you are not sure if the export process ignored reported errors. See the example of error handling during export in Step a on page 46. A good technique to resolve missing elements is to initiate an export from the target domain of the elements that have dependencies to see if they indicate that any of their dependent elements are missing. Validation, however, is not a substitute for a test plan that exercises the features of the new and revised (or impacted) services together with a delineation of the expected results of each set of test parameters and actions. You can build your plan and any associated services or test applications and store them in SonicFS so they can travel in a deployment archive. You can create an additional project folder for test plans as they are relevant in both development and deployment domains. Progress Sonic ESB Deployment Guide 8.5 113
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: 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 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?