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 an Executable vs. an Abstract Process

Creating an Executable vs. an Abstract Process

In Process Developer, you can build two kinds of business processes:
  • An
    executable process
    contains all the actual message data, operations, and partner information required for a running process. It uses the full power of data assignment and selection. Process Developer creates executable processes by default. You can simulate, deploy, remote debug, and execute an executable process.
  • An
    executable process
    contains all the actual message data, operations, and partner information required for a running process. It uses the full power of data assignment and selection. Process Developer creates executable processes by default. You can simulate, deploy, and execute an executable process.
  • An
    abstract process
    is a business protocol description document that tells your business partners what a process will look like when it runs. It outlines the steps of a process without actually filling in all the actions and data required for a running process.
An abstract process lets you share information with your partners without exposing how you intend to use data from your service. It gives your partners a way to understand how to create their WSDL files to work in your process and to tell them what information you plan to send them when the process runs. An abstract process outlines the type of data to be exchanged, as well as activities, time limits, error handling, and other meaningful pieces of information for the process.
You cannot simulate, deploy, remote debug, or execute an abstract process.
You cannot simulate, deploy, or execute an abstract process.
See also
Creating an Abstract Process
and
Tips for Working with Abstract Processes
.


Updated March 30, 2020