Kavin's SOA Blog

March 31, 2009

How to control Default BPEL revision

Filed under: Setup — Tags: , , , — Kavin @ 3:14 pm

By default in BPEL when we deploy new version of BPEL process then the new version becomes default one for that BPEL process. However, there are situations where we want to override this behavior like wanting to keep an working copy as default BPEL version and continue to deploy new  versions with modification.

To achieve desired objective use the property ‘processDeployAsDefault’ in the domain configuration, which  controls which revision will be the default revision.  If set to "true" the  most recently-deployed version of a process is always the default version. If  set to "false" This means that the most recently deployed version of a  process prior to setting this property to false remains the default version.

Please remember this is a”DOMAIN” level configuration so you have to do this exercise for every BPEL domain in question. All you have to do is to modify domain.xml file which is located at <ORACLE_HOME>\bpel\domains\<DOMAIN_NAME>\config\domain.xml and add below mentioned text anywhere within “bpel-domain-descriptor” element.

<property id="processDeployAsDefault">
<name>Process Version Logic </name>
<value>false</value>
<comment><![CDATA[
         If set to "true" This means that the most recently-deployed version
  of a process is always the default version
         If set to "false" This means that the most recently deployed version
  of a process prior to setting this property to false remains the default
  version
  <p/>
         The default value "true".
         <p/>
         ]]>
</comment>
</property>

image

Theme: Shocking Blue Green. Blog at WordPress.com.

Follow

Get every new post delivered to your Inbox.