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

Designer

Designer

Tips for Working with Abstract Processes

Tips for Working with Abstract Processes

As described in
Creating an Executable vs. an Abstract Process
, you can create a process not immediately intended for execution. When working with abstract processes, consider the following tips:
  • For an abstract process, the namespace is:
    http://docs.oasis-open.org/wsbpel/2.0/process/abstract
  • You can set an Abstract Process Profile in the process Properties view. The default profiles listed are referenced in the WS-BPEL 2.0 specification.
  • You can use an activity unique to abstract processes. For details, see
    Opaque
    .
  • You can use an
    opaque from-spec
    assignment in a copy operation. For details, see
    Assign
    .
  • You can make an abstract process into an executable one by changing the process's Abstract Process property from Yes to No. If your process contains an opaque activity, you are warned to replace it with a different activity.
  • If desired, you can follow the guidance in the WS-BPEL 2.0 specification for hiding syntactic elements in your process. See the examples below.
WS-BPEL XML Fragment Examples
Example 1 - Variable Declaration
<variable name="commonRequestVar" element="##opaque" />
Example 2 - Use of Invoke Activity
<invoke partnerLink="homeInfoVerifier" operation="##opaque" inputVariable="##opaque" ext:uniqueUserFriendlyName="request verification" />
Example 3 - Use of Opaque Activity
<opaqueActivity template:createInstance="yes"> <documentation>...</documentation> </opaqueActivity>

0 COMMENTS

We’d like to hear from you!