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

Creating a BPEL Process as a Service for Another BPEL Process

Creating a BPEL Process as a Service for Another BPEL Process

A BPEL process uses an invoke activity to call out to a Web service to perform a task. You can create a BPEL process for this purpose.
You can choose between two different invocations of a process:
  • Standard
    process
    that behaves like a normal endpoint reference
    When you create a process deployment descriptor, you can select any process as a static endpoint reference for a partner role. This avoids the overhead of the server composing a SOAP message for dispatch through the standard invocation layer. The message is sent directly to the engine instead.
  • Subprocess
    of the calling process that is eligible for process-level compensation and termination handling
    When you create a process deployment descriptor, you can select any process:subprocess as a static endpoint reference for a partner role. This lets the subprocess participate in process-level compensation and termination handling.
More about Subprocesses
A subprocess is subject to the fault and compensation handling rules of the enclosing scope of the parent process from which it is invoked. A subprocess is compensated whenever either the fault handler or the compensation handler for the scope enclosing the invoke activity is run. This work is performed implicitly. However, you can enable process-level compensation and termination for the subprocess to select what compensation and termination tasks to do. For a discussion of compensation, see
Compensation
.
The enclosing scope for the invoke activity does not complete until the subprocess completes. If the subprocess is compensatable when it completes, the enclosing scope compensates the subprocess during its compensation.
If the subprocess throws a fault, the invoke activity of the parent process faults.
Creating a Process as a Service
To create a BPEL process as a service, you must do the following:
  1. Add a WSDL file to Project Explorer for the BPEL process. There are many ways to create a WSDL file.
    See Interfaces, Service References, and Local WSDL
    .
  2. Create the BPEL process to be used as a service.
  3. If desired, set the process property Process Level Compensation/Termination to Yes. Two additional tabs are added to the Process Editor, and you can add compensation and termination activities to them. The following illustration shows the tabs that are added to Process Developer.
  4. In the Process Deployment Wizard, identify a service name for the My Role partner link, just as you would for any process.
  5. Create a business process archive (.BPR), as described in
    Deploying Your Processes
    .
  6. Deploy the process to the server.
  7. Create the main process that invokes the BPEL process using an invoke activity.
  8. In the Process Deployment Wizard for the main process, do the following for the Partner Role partner link:
    1. Select process or sub-process as the invoke handler.
    2. Select static as the endpoint reference.
    3. Select the
      Dialog
      button to fill in the sub-process information.
  9. Deploy the main process.
When the main BPEL process is running, and it invokes another BPEL process, the invoked process has the status of a subprocess, with its own state information. The main process awaits the completion of the subprocess before continuing its own execution. For more information on actively running processes, see the
Process Console Help
.


Updated March 30, 2020