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

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