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

More documents

Recommendations

Info

Chapter 3: Mapping ESB Artifacts to Target Domains Adding Parameters to Existing ServiceTypes The parameters of an ESB configuration element define its functionality and its bindings to a target domain’s requirements, service levels, and physical topology. While the functionality is intended to stay constant, the bindings must be adjusted when the ESB element is brought into another domain. While predefined service types expose the most common parameters for tailoring, you might want to add (or remove) some parameters that can be mapped. For example, the configuration file for the service SplitJoinForEach.xml has several init parameters, only two of which are stated as required in the default tailoring rules file. If you want to tailor the Boolean parameter Keep Original Part to toggle from its default value false to true in deployment, add its parameter in your tailoring rules file as follows: Adjusting EndpointRules For an endpoint, you need to be aware of required destination names, particularly for the type QUEUE as queues must be statically defined before they are referenced. These queues will need to exist in the target domain. Other endpoint parameters are generally accepted as they have been defined. You might also provide a preferred name or pattern for destinations. For example, you could redefine a destination name RIA.entry to be controlled by ACLs you define for com.myCorp.# by changing the destination name to com.myCorp.RIA.entry. Adjusting ConnectionRules For a connection, the parameters exposed provide the parameters for management connection in the target domain, as well as SSL parameters that specify locations on local systems. Or, if you do not use SSL for management connections, you could leave those parameters off the tailoring rules so that they are not exposed. 70 Progress Sonic ESB Deployment Guide 8.5
Tailoring Rules Adding Property Mapping Rules You can append a PropertyRules section at the end of the tailoring rules file to enable mapping the value of a specific property name to your preferred value. For example: ...
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 96 and 97: Chapter 4: Analyzing ESB Artifacts
Page 106 and 107: Chapter 5: Importing Deployment Art
Page 120 and 121:
Chapter 5: Importing Deployment Art
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?