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

More documents

Recommendations

Info

Chapter 2: Exporting ESB Artifacts for Deployment About Sonic ESB Deployment Artifacts A Sonic deployment is a unit of deployment, a set selected configuration files exported from a domain, either as a set of files or a Sonic archive file, a .xar file. Typically, the projects in a source control branch are uploaded and packaged as one deployment archive. Each export includes an export properties file that contains information about the source domain and the root elements selected for the export. The export properties file provides the template that the export tool uses to rebuild the set of exported configurations. The files exported from a domain can include containers, ESB processes, services, service types, endpoints, and resources in the Sonic File System, SonicFS. As you construct an export archive, selected items are evaluated so that configurations that are dependencies are included while standard references that are installed in target domains are explicitly excluded from the archive. Most archives can be assembled in two steps: 1. Choosing a process or service and letting it discover its dependencies 2. Choosing the branch that defines your storage area for the project in the Sonic File System. Important Additional elements — Some configuration elements are not readily discovered or exported. Some elements that you must recreate in the target domain are: ● Properties files for management and administrative tools. ● Management containers. They are created in the target domain’s Sonic Management Console to bind hosted ESB components and services to physical distributed systems. ● Classes (.jar files) that not imported into SonicFS or not referenced by the ESB Container through a classpath parameter. ● Files not stored in the SonicFS structure, perhaps used by services or GUI components of an application. See “Packaging Graphical Components” on page 37 for more information. Note Ignored Elements — Within the set of referenced elements, some basic elements are not included because they are expected to exist in a target domain. These standard types are established in target domains as you define the domain and install its components. 32 Progress Sonic ESB Deployment Guide 8.5
About Sonic Archive Files and File Sets About Sonic ESB Deployment Artifacts A Sonic archive file, a XAR file, is an archive of selected configuration files exported from a domain. Each archive file includes an export properties file that contains information about the source domain and the root elements selected for the archive. The export properties file provides the template that the export tool uses to rebuild the archive. The files exported from a domain can include containers, ESB processes, services, service types, endpoints, and resources in the Sonic File System, SonicFS. As you construct an export archive, selected items are evaluated so that configurations that are dependencies are included while standard references that are installed in target domains are explicitly excluded from the archive. About Dependencies Dependencies are explicit references to other elements. When you choose an ESB element to be evaluated, the dependency logic traverses the selected element’s references to determine the element’s explicit dependencies. The following illustration shows the hierarchy of the ESB element groups that have dependencies on elements in that group or subordinate groups: ESB Connection Types ESB Endpoint Types ESB Container ESB Services ESB Endpoints ESB Processes ESB Connections ESB Service Types Progress Sonic ESB Deployment Guide 8.5 33
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 34 and 35: Chapter 2: Exporting ESB Artifacts
Page 60 and 61: Chapter 3: Mapping ESB Artifacts to
Page 82 and 83:
Chapter 3: Mapping ESB Artifacts to
Page 84 and 85:
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?