Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Migrating Processes from BPEL4WS 1.1 to WS-BPEL 2.0

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. From the Project Explorer, double-click a BPEL file to open it in the Process Editor.
  2. Select
    File > Save As
    .
  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. 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:
  • 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.
The old syntax is:
<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>
The new syntax is:
<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.


Updated March 30, 2020