Designer > Welcome to Informatica Process Developer > Migrating from Earlier Versions

Migrating from Earlier Versions

Required Reset for Process Developer Perspectives

If you maintain your existing Workspace when you upgrade Process Developer, we recommend the following best practices so that you can take advantage of new features:

Migrating from Process Developer Versions Prior to 9.0

There are a few changes to be aware of for new versions of Process Developer.

Migrating from Process Developer Versions Prior to 8.0.x

There are a few changes to be aware of for new versions of Process Developer.

Opening and Using BPEL4WS 1.1 Processes

If you have BPEL processes created in earlier versions of Process Developer, they conform to the BPEL4WS 1.1 specification. You can open and work with BPEL 1.1 processes. Process Developer recognizes the version of BPEL in a process and opens in the appropriate mode: BPEL4WS 1.1 or WS-BPEL 2.0.
In BPEL4WS 1.1 mode, Process Developer displays the palette and menu options that support the BPEL4WS 1.1 specification.
By default, Process Developer is set to launch in WS-BPEL 2.0 mode. You can set a preference to open Process Developer in BPEL4WS 1.1 mode, if desired. For details, see Process Developer Preferences.

Migrating Processes from BPEL4WS 1.1 to WS-BPEL 2.0

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:
  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.
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.
Conversion issues:
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.
The old syntax is:
<pickList xmlns="">
<pickHeader ...>
<pickItem pickDisplay="ncname"
hoverHelp="prefix|namespace:ncname Description:ncname"/>*
The new syntax is:
<pickList xmlns="
<pickHeader ...>
<pickItem pickDisplay="NCName"
hoverHelp="prefix|namespace:NCName Description: NCName"/>*
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.

Taking Advantage of SOAP 1.2 Port Binding Version 7.x

Process Developer Version 7 and later supports endpoint reference port bindings for SOAP 1.1 and SOAP 1.2. All processes prior to Version 7 supported only SOAP 1.1. If you want to take advantage of the SOAP specification upgrade, SOAP 1.2 clients should use the new SOAP 1.2 URL when addressing My Role endpoints, namely:
Partner role services can be invoked with SOAP 1.2 bindings too.