Antonis Logothetis Blog

A configuration plan for a SOA composite is an XML file, which enables you to modify on depoyment time several environment-specific values, such as JDBC connection strings, hostnames of various servers, and so on. In order to create a configuration plan: 1. Open JDeveloper 2. In the application pane, find your SOA project and right click on the composite.xml 3. Click on Generate Config Plan. Now that you have created the configuration plan, it should appear under the Resources folder. 4. Deploy your project using the configuration plan by selecting it in the "Deploy Configuration" wizard. Practically, the configuration plan contains a set of search and replace rules, that help you edit hostnames, JNDI Names, composite properties etc, for services exposed and references consumed in your SOA composite. Below you will find a section that edit a service exposed:             <service name="servicename_ep"> ...

When deploying Oracle Service Bus projects to a new environment some values such as Web Services endpoints, DB JNDI Names, AQ JNDI Names, LDAP JNDI Names etc. In order to achieve automated changes to your resources, Oracle suggests using Configuration Files which apply customization rules to them. In OSB 11g, Configuration Files where called "Customization Files", apart from renaming the file in OSB 12c for homogenization purposes with SOA Configuration Plans, there are no other changes and everything in terms of functionality remains the same. In order to create a Configuration File first you should deploy your project with the initial implentation, which typically contains some proxy, pipelines and business services. Then, you log in to Service Bus console and:  navigate to the Admin tab select the Create Configuration File option (take note that there is an option Execute Configuration File that we will use later) select the project for which you need ...