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

Chapter 3: Mapping ESB Artifacts to Target Domains
Revising and Extending String Replace Maps
The stringReplaceMaps section, by default, removes workspace from the sonicfs paths.
You can tune this line if, for example, you routinely want the deployed files from a
development workspace to map to a directory structure named com.myCorp, as follows:
Important Always replace the name workspace — While you can revise the string replacement of
sonicfs: path references from workspace to no name or any specified name, you should
never leave the name workspace in a deployment configuration as it might trigger
behaviors not intended for deployment environments.
You can extend the stringReplaceMaps section to include multiple steps. The added steps
must each have an order parameter set to an incrementing integer value. As shown in the
following code segment, the stringReplaceMap line where order=”1” is evaluated first,
then the result is recursed with the line where order=”2”. After the sequence has been
completed, the default stringReplaceMap applies, as shown:
If you use order steps you must have one instance of each sequential step, but the listing
of the steps need not be in order.
References within files — String mappings also apply to strings within files, even if they
are packaged within the XAR (such as a CSAR package). You need to be careful in raw
string replacements to qualify your search string, and to avoid mapping key words, fixed
namespaces, and related artifacts by string replacement. This feature is most useful for
replacing URLs and references. For example, the following line might be for mapping
references to targets used in the test environment:
68 Progress Sonic ESB Deployment Guide 8.5