Deploying to Multiple Environments with Different Configuration Values

If you are using 10.1.3.1 as I am, there is good news on customizing deployment tasks.  If you go to the 19th chapter of the  Oracle BPEL Developers guide, you will find the following paragraph.  The guide also provides a working example of how to implement different configurations.

19.1.3 Deploying to Multiple Environments with Different Configuration Values

When the testing and development phase of a BPEL process has completed, you are ready to deploy the process to a production environment. The configuration properties for the production environment are typically different from those for the development environment. For example, the partner link Web service URL for the production environment is typically different from the one used in the testing environment.

In previous releases, you resolved this conflict by modifying the bpel.xml deployment descriptor file or providing separate bpel.xml files for the development and production environments. This was a big effort if the bpel.xml file required many modifications or if you had multiple versions of bpel.xml that required modifications.

Beginning with this release, a customize ant task is provided that enables you to specify the property value for development and production environments in a single build file location. The customize task captures the changes between different versions of bpel.xml using the build file. This task can be used as a subtask of bpelc or as a standalone ant task. The bpelc subtask can contain multiple customize tasks. The customize task can contain multiple subtasks.

I believe it's time to create an example process to test and get familiar with the customize deployment tasks feature.