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 from Process Developer Versions Prior to 9.0

Migrating from Process Developer Versions Prior to 9.0

There are a few changes to be aware of for new versions of Process Developer.
  • 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=
    .


Updated March 30, 2020