Controlling The Lifecycle Status Of A Bpel Process On Deployment (Doc ID 412145.1)

Last updated on NOVEMBER 19, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.1.0
Information in this document applies to any platform.

Goal

If you deploy a process with a new revision in 10.1.3.1.0 the revision's lifecycle will be
automatically set to active and the process revision as default. Therefore, you cannot set the
process revision and the life cycle during deployment.

The behavior was different in 10.1.2.0.2. The default revision was always set to active during
deployment, but if you deployed a different revision, this did not automatically become default.

The expected behavior is to be able to set the process revision and lifecycle on deployment.
After deployment you can modify both by using the BPEL Console:

- Default revision 1.0 of process set to inactive.
- Set revision 1.1 of the process lifecycle inactive on deployment.
- Default revision 1.0 remains inactive.
- Make revision 1.1 default and set lifecycle to active using BPEL Console.


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms