Configuration plan in SOA Suite 11g

We create configuration plan when we try to migrate our SOA composite from one
environment to another.config plan replaces sections of your composite.xml and wsdl to match the different configurations of SOA Suite installations on different environments at deploy time.

A lot has been discussed already in the following section of oracle documentation

http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#CHDCAGEB

41.6.1.1 Introduction to Configuration Plans

Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 (11.1.1)
Part Number E10224-05

We will just take a simple sample and try to understand how does it work.

Let suppose you have a BPEL process A which is calling another BPEL process B.Then in the composite for A you will have the reference for the wsdl for Process B.

IT obviously will contain the server information too something like

http://test:7001/sample?WSDL

Now if you want to move your project A to some other environment then the Process A still will have the same reference for process B that is it will still call the process B in same URL and will cause a fault.

What we want is that when we migrate the process A to different environment process A wsdl should also migrate to that new environment.

For that purpose we create a configuration plan.


Choose your process and select the composite.xml right click and select generate config plan



Let the default name be there and say ok




As you can see we have several commented section over there,We need to uncomment them and provide the name of our current server in search option and name of another environment(server) where we are going to deploy the process.

Similary for port also we need to make the change.

Depending upon your business process you have to add tags and change config plan accordingly.

Once it is done save the config plan.

Now try to deploy this select process and say deploy



Say next and this time choose your configuration plan and then deploy it to the new environment.




You can find some good explanation on the following forum post

http://forums.oracle.com/forums/thread.jspa?threadID=1101123