You can migrate any BPEL process you created in earlier versions of Process Developer, or any BPEL4WS 1.1 process, to a WS-BPEL 2.0 process. Doing so gives you access to all the new and updated activities, data manipulation, and handlers supported.
You can migrate your BPEL 1.1 processes as follows:
From the Project Explorer, double-click a BPEL file to open it in the Process Editor.
In the
Save As
dialog, select another file location, if desired, and rename your BPEL 2.0 file if you do not want to overwrite the BPEL 1.1 file.
Select the checkbox next to Convert to WS-BPEL 2.0 format, as shown in the example, and select
OK
.
Your BPEL 2.0 process opens in the Process Editor, and Process Developer changes to WS-BPEL 2.0 mode.
All of your preference settings are preserved.
Fault variable. The variable used in a catch activity is accessible only in the catch activity. In BPEL 1.1 the variable was declared in the enclosing scope. It is no longer available anywhere except within the catch. If a 1.1 process was using the fault
var
outside of the catch, the static analysis will report an error.
OnEvent variable. Same issue as above. The variable is now declared within the
OnEvent
activity, not in the enclosing scope. The variable is accessible only to the
OnEvent
and not to the scope.
Queries in copy operations. The absolute path used in 1.1 processes is now a relative path. However, a query using an XPath expression beyond a simple path to data may not get converted. A query that cannot correctly convert is left in
get Variable Data()
syntax. Process Developer warns you that the expression is not WS-BPEL 2.0 compliant.
Custom Function Pick Lists
The XML format for custom function pick lists has changed for Process Developer, for all process versions. You must update expression builder pick list files as follows.
<pickList xmlns="http://active-endpoints.com/FunctionBuilderSchema">
<pickHeader ...>
<pickItem pickDisplay="ncname"
syntax="namespace:ncname"
caretOffset="colnum-expr"
hoverHelp="prefix|namespace:ncname Description:ncname"/>*
</pickHeader>
</pickList>
<pickList xmlns="http://schemas.active-endpoints.com/picklist/
2006/08/ExpressionBuilder_FunctionsPickList_Schema.xsd">
<pickHeader ...>
<pickItem pickDisplay="NCName"
syntax="${prefix}:NCName(${caret})"
hoverHelp="prefix|namespace:NCName Description: NCName"/>*
</pickHeader>
</pickList>
If your Process Developer installation uses an existing workspace, your already-loaded custom function picklist will continue to work. However, you can not reload it without receiving a validation error.
