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

More documents

Recommendations

Info

Chapter 3: Mapping ESB Artifacts to Target Domains Using StringReplace and PropertyReplace Content Change Rules The content change rules, StringReplaceMaps and PropertyReplaceMaps, are closely related. The following sections contain information about using both types. Rule Processing When you apply a map, its content change rules are processed as follows: 1. PropertyReplaceMaps are processed before StringReplaceMaps and are checked for named rules and generic rules. ■ If both a named rule and a generic rule exist, and both affect the same property, the named rule takes precedence over the generic rule. Best practice is to make sure that a named property file contains only one instance of a named property, because multiple instances may cause unpredictable results. ■ If multiple generic rules exist, they are processed in a top-down manner. If multiple generic rules affect the same property, the last rule found in the map (that is, the rule nearest to the bottom) takes precedence. Best practice is to have only one generic rule. ■ Generic rules extend to all properties files in the XAR and any component packages. Best practice is to use only named properties files, unless you are comfortable with changing properties globally. 2. After all PropertyReplaceMaps are completed, StringReplaceMaps are processed. ■ StringReplaceMaps are checked to determine the order of rules (specified with the order attribute) and then processed in the specified order. Unordered rules are processed after ordered rules. ■ You can add an artifactName property to a StringReplaceMap to constrain its scope to the named file. But the rule is still processed in the stated order. ■ If there are multiple unordered StringReplaceMaps, they are processed in a topdown manner. Best practice is to use only ordered rules, because multiple rules with no specific order may cause indeterminate results. Creating Properties Files It is good practice to make additional copies of properties files in preparation for tailoring. For example, copying ESBToREST.properties to ESBToREST_test.properties and ESBToREST_production.properties in SonicFS makes tailoring a bit easier. The alternative would be to extract the properties file from the XAR, make a named copy, and then add them back in to the XAR. 72 Progress Sonic ESB Deployment Guide 8.5
Tailoring Rules Applying Tailoring Rules and Creating a Map File for an Archive Once the tailoring rules are complete, you can generate a map file from an archive. The tailoring rules will specify what is included in the map. Then you edit the map for the settings you want to adjust in the target domain. Then the edited map will ruin against the original archive to create a mapped archive. Creation of a map for an export archive is achieved by running an ESBAdmin command with the source archive and the output map file as parameters. The default tailoring rules are applied unless you specify a custom rules file. Note that file path names are fully enunciated. For this example, the export file RIA.xar created in the “Exporting ESB Artifacts for Deployment” chapter is used in the ongoing example. ◆ To create a map file from a source archive and use default tailoring rules: 1. Start the ESB Admin Tool. 2. Enter: ESBAdmin> createMap source_archive map_file For this example: ESBAdmin> createMap c:\RIA.xar c:\RIA_map.xml You can now edit the map you created to specify its parameters for the target domain. ◆ To create a map file from a source archive and apply modified tailoring rules: If you created custom tailoring rules, as described in “Adjusting Tailoring Rules to Apply When Creating Map Files” on page 67, reference the file you saved, as follows: 1. Start the ESB Admin Tool. 2. Enter: ESBAdmin> createMap source_archive map_file [rules_file] For this example: ESBAdmin> createMap c:\RIA.xar c:\RIA_map.xml c:\myTailorRules.xml You can now edit the map you created to specify its parameters for the target domain. Progress Sonic ESB Deployment Guide 8.5 73
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 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?