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

More documents

Recommendations

Info

Chapter 2: Exporting ESB Artifacts for Deployment ■ Add all ESB elements in the domain — Selects all the ESB element types, but does not include SonicFS data unless referenced as dependencies. ■ Choose ESB Containers — Lets you select one or more ESB Containers. The links evaluated are services, endpoints, processes, and connections, each of which is, in turn, evaluated for dependencies. ■ Choose ESB Processes — Lets you select one or more ESB processes. The links evaluated are endpoints, services, processes, and WSDL URLs (when referencing SonicFS). Also: ❑ For each step in an ESB process, the endpoint name at each endpoint step (the endpoint name, the process name of each ESB process step, and the service name of each service step.) ❑ For each runtime parameter, if the parameter is a URL reference to a SonicFS file, the referenced file is included. ❑ For each invocation step, the .esbws file, when that file is in SonicFS. ■ Choose ESB Services — Lets you select one or more ESB services. The links evaluated are endpoints, services, processes, WSDL URLs (when these reference SonicFS), and init parameters that are URL references to SonicFS files. Sonic BPEL Server services evaluate the related BPAR as a dependency. ■ Choose ESB Service Types — Lets you select one or more ESB service types. Choosing a service type includes its properties file as a dependency. ■ Choose ESB Endpoints — Lets you select one or more ESB Endpoints. The links that are evaluated are EndpointTypes and WSDL URLs in SonicFS. ■ Add all SonicFS — Since many elements in SonicFS might be dependencies of ESB elements, this option selects all of the files in the Sonic File System. ■ Choose SonicFS — Lets you select one or more folders and files from SonicFS: ❑ When you choose a folder, you get all of a specified folder structure including any files you imported into the SonicFS in the selected folder. ❑ When you choose a file in SonicFS as the root element, that file is evaluated to include its dependencies. These include xsl, xslt, xml, xsd, wsdl, esbws, esbdb, xaction, or cbr. For example, an esbws file references a wsdl file. You can choose a mixture of folders and files, a technique that lets choose a folder’s contents and also evaluate the dependencies of a file in the folder that you know will have dependencies; for example, an esbws file in a project folder. ■ Rebuild — Starts the archive rebuild process, described on page 37. 44 Progress Sonic ESB Deployment Guide 8.5
Defining and Exporting a Sonic Deployment Archive Using the Deployment Export Tool As an example, the following procedure shows how some ESB artifacts, folders, and files can be exported. The basis of this export example is the Sonic Workbench’s ESB sample for Remote Information Access, Sample.RIA. The sample was imported onto a Sonic Workbench and then uploaded into its domain. That domain is where the deployment tools will connect to perform the export functions. Note Prototypes — The Sample.RIA project demonstrates the use of the Prototype Service. As such, this export includes those prototypes. In a real application, prototypes should be replaced by actual services before moving the project into deployment. ◆ To export ESB Artifacts through the Deployment Export Tool: 1. Select the Actions menu. The menu lists the options you can choose as your first root element. For this example, select Choose ESB Processes, as shown:. 2. In the Choose ESB Processes dialog box, choose the Sample.RIA.processRequest: When you click OK, references from the Sample.RIA.processRequest to other elements are traversed. When the traversal is complete, you are presented with the results for review. Progress Sonic ESB Deployment Guide 8.5 45
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 94 and 95:
Chapter 3: Mapping ESB Artifacts to
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?