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

More documents

Recommendations

Info

Chapter 2: Exporting ESB Artifacts for Deployment SonicFS classpaths The following illustration provides a more detailed look at ESB elements and reveals recursive and secondary references that the dependency logic discovers in a full set of dependencies: Routing HTTP connections Bus connections Dependencies in BPEL Server Projects ESB Connection Types ESB Connections ESB Service Types ESB Endpoint Types ESB Container ESB Services ESB Endpoints if BPE if BPAR ESB Processes itinerary BPAR (BPEL Archive) tracking details WSDL To choose a Sonic BPEL Server project, build and upload its project, and then choose its service name (such as Sample.BPEL) or its BPAR file. The traversal of the .bpar file evaluates the .wsdl, .bpel, .xlst, and .xsd content of the BPAR file recursively to determine dependent endpoints, connections, processes, .wsdl files and Resources. 34 Progress Sonic ESB Deployment Guide 8.5 WSDL URL
About Roots About Sonic ESB Deployment Artifacts The procedure of creating a deployment export package specifies through a series of selections, each of which defines a root in the archive structure. Each root is a line item in the archive definition that defines: ● An ESB artifact from which dependencies are to be evaluated. The process of discovery attaches the artifact’s dependencies to that root element. ● A file in the Sonic File System whose dependencies are discovered and defined as attachments to that root element. A file name with the extension xsl, xslt, xml, xsd, wsdl, esbws, esbdb, xaction, or cbr is examined for further references to SonicFS. ● A folder in the Sonic File System, SonicFS. Specifying a sonicfs:// folder includes all subordinate folders and files as attachments to that root element. Choosing a folder in SonicFS that contains files that, selected individually, would be evaluated does not cause any such files to be evaluated—instead the entire folder hierarchy below the selected folder is attached to that archive root. The following screen shows the roots specified in the example in “Using the Deployment Export Tool” on page 42. There are two roots in this archive specification: one ESB process, and one text file. Editing ExportProperties.xml The roots are stored in the ExportProperties.xml file that is created by a new export, and then stored in the file store or archive. When an archive is rebuilt, its contents are discarded except for its defined roots. The roots are re-evaluated so that current dependencies and folder hierarchies are included. This file is edited by changes you make in the Deployment Export Tool. If you want to change an existing ExportProperties.xml file when rebuilding an ESB artifact package using ESB Admin Tool export command, this file must be edited in the file store or within the archive before you issue the command. Progress Sonic ESB Deployment Guide 8.5 35
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 84 and 85:
Chapter 3: Mapping ESB Artifacts to
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Chapter 4: Analyzing ESB Artifacts
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Chapter 5: Importing Deployment Art
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Chapter 6: Adapting Imported Servic
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
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?