Migrating from Earlier Versions

Required Reset for Process Developer Perspectives

• •Reset both of the Process Developer perspectives. From the Window menu, select Reset Perspective for the perspective in focus.
• •Delete the current server configuration and add a new server. The Process Developer embedded server runs from a plug-in that includes version details. Each time you upgrade to a new version, you must delete the old server configuration by navigating to Window > Preferences > Server > Runtime Environments and select Remove to delete Process Developer Embedded Server. Then select Add from this same dialog to install a new server runtime environment.

Migrating from Process Developer Versions Prior to 9.0

• •Existing BPEL processes have an associated visual layout file that includes all layout and annotation information (.vbpel files). New BPEL files contain this information, eliminating the vbpel file and making it easier to move BPEL files to another location without losing annotations. To delete the vbpel file for existing processes, open and save your older processes. This is not required. This feature does not apply to BPEL 1.1 processes or processes designed in the Classic style.
• •The Process Editor palette offers a choice of BPMN-Centric (the default) or the existing BPEL-Centric stylesheet. Existing processes can be opened with either stylesheet with the exact same results. To use the BPEL-Centric palette, change the Layout Preference.
• •You can add an XQuery nature to existing projects to take advantage of the XQuery editing and runtime tools. Right-mouse click on a project and select Add XQuery Nature.
• •POJO (and XQuery) custom functions can be listed in the Expression Builder and deployed in your deployment contribution. There is no longer any function context set up required for new POJO custom functions.
• •If you have existing XQuery functions, be sure to read the Release Notes (elsewher in this help) for possible changes you may need to make to your functions.
• •A newly generated B-unit ant script contains targets and parameters for code coverage. You can manually add these ant tasks to your existing B-unit ant scripts. You can also add XQuery modules as B-unit resources.
• •You can migrate running process instances to run against a new process version. As a first step, open your existing process, modify it slightly by moving an activity a bit (mark the process as dirty), and save the process without making any other changes. Update the PDD to enable the Migrate Version option. Then deploy the contribution that contains the unchanged process structure and updated PDD. After you have deployed the Version 9 contribution, you can then make structural changes to your process and migrate running process instances to the new version.
• •Version 9 uses a newer version of the Saxon XSL parser that does not support the undocumented and non-standard @value attribute for the <xsl:param> element. If your older B-unit tests or other XSL functions contained this attribute, they cannot be parsed by Saxon. To correct this problem, use an expression such as select= instead of value=.

Migrating from Process Developer Versions Prior to 8.0.x

• •Deployments from prior versions are shown as legacy contributions on the server. Although there is no change in how your processes run on the server, we highly recommend that you delete old BPRs and redeploy your processes and resources to take advantage of contribution features. See Converting Legacy Deployments to Contributions.
• •In the PDD, there are wording changes for Process Version details to match the new contribution states. Effective date is now Online date and Expiration date is now Offline date.
• •There is a new Swimlane annotation in the Process Editor's tool palette (BPMN style only). To view this new Palette item, be sure to create a new workspace or delete your current Palette customization file.
• •You can no longer import a WSDL declaration into your BPEL from the file system. You must import the WSDL into your project or set project references to include another project. Existing file system declarations are converted to URLs.
• •The .avcconfig file for Process Central has been updated, but older files are compatible with Process Central. The new file allows for custom columns in Process Central.

Opening and Using BPEL4WS 1.1 Processes

Migrating Processes from BPEL4WS 1.1 to WS-BPEL 2.0

1. 1. From the Project Explorer, double-click a BPEL file to open it in the Process Editor.
2. 2. Select File > Save As.
3. 3. 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.
4. 4. Select the checkbox next to Convert to WS-BPEL 2.0 format, as shown in the example, and select OK.

• •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.

Taking Advantage of SOAP 1.2 Port Binding Version 7.x