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

Optimize Parameters

Optimize Parameters

The
Optimize Parameters
command makes changes to your process based on the following conditions:
  • The variable is only assigned within a single assign activity and possibly has an initialization expression.
  • The assign immediately precedes the main activity that uses the variable as input (either in a sequence or through a link).
  • The assign qualifies to be converted into an XQuery assignment type: There is only one copy expression, the copy has a from expression, which uses XQuery, and there is no initialization expression for the variable.
The assign qualifies to be converted into an XQuery assignment type if the from clause is: an expression using XPath, a literal, a variable with a property, a variable, optionally with a part or a query.
Changes made
The changes that can be made are as follows:
  • If the variable is an element type, it is changed to a message type, and all copies that set it get a new "part" attribute.
  • If the variable was an element type and had an initialization expression, the initialization expression is moved to become the first "copy" in the assign activity.
  • If the variable is the only thing assigned in the assign statement that sets it, move the entire assign to be in the implicit scope and move all the inbound and outbound links for the assign to the implicit scope (adding to the inbound or outbound links that are already there). Otherwise, move just the copies from the assign to a new assign activity inside the implicit scope.
The actions you can perform are:
  • Move the variable into the implicit scope and rename it (and all of its uses) to "parameters.".
  • Convert copy "from" constructs to use expressions (unless they are from a literal). from
    variable.part
    with
    query="/foo/bar"
    becomes
    $parameters.part/foo/bar
    , from variable with
    property="ns:foo"
    becomes
    abx.getVariableProperty('parameters','ns:foo')
    , copy from
    variable.part (query?)
    to copy from an expression.


Updated March 30, 2020