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

Process Element and Properties

Process Element and Properties

After you create a new BPEL file in Process Developer, add an activity to the Process Editor canvas, and save your file, Process Developer creates the underlying XML source file. The XML source begins with the
<process>
element.
The XML Syntax for an executable process element looks like this:
<process name="NCName" targetNamespace="anyURI" queryLanguage="anyURI"? expressionLanguage="anyURI"? suppressJoinFailure="yes|no"? exitOnStandardFault="yes|no"? xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable">
If you use Process Developer extensions, other namespaces and process attributes can be added, as described in
Declaring Extensions
.
Click on a blank part of the Process Editor canvas to put the process as a whole in focus. In the Properties view, set the Process properties as desired.
Property
Description
Default Value
Generate Prefixed Source
Specifies that BPEL XML source code elements are generated with the
<bpel:...>
prefix. Enabling this property ensures that the attribute
xmlns:bpel
will not be null.
yes
Write Port Type
Add port type attribute to activity definition for receives, replies, onEvents, onMessages, and invokes.
no
Abstract Process
Specifies whether the process is abstract or executable. For more information, see
Creating an Executable vs. an Abstract Process
. This setting can be specified as a preference for all new processes. See
Process Developer Preferences
.
no
Abstract Process Profile
List of default profiles referenced in the WS-BPEL 2.0 specification
http://docs.oasis-open.org/wsbpel/2.0/process/abstract/simple-template/2006/08
BPEL Namespace
Specifies the BPEL language namespace for an executable or abstract process. The default is for executable processes.
http://docs.oasis-open.org/wsbpel/2.0/process/executable
Comment
Optional property for adding an HTML-tagged annotation to the
<process>
element. You can also add a comment to any activity, link, or container.
none
Create XPath
This property is a Process Developer extension to WS-BPEL 2.0, described in
Declaring Extensions
.
yes
Disable Selection Failure
This property is a Process Developer extension to WS-BPEL 2.0, described in
Declaring Extensions
.
yes
Documentation
Optional property for adding annotation to the
<process>
element. You can also add documentation to any activity, link, or container. See
Adding Documentation to a Process
.
none
Exit on Standard Fault
If this property is set to
yes
, then the process exits immediately as if an exit activity has been reached, when a WS-BPEL standard fault other than
bpel:joinFailure
is encountered. If this property is set to no, the process can handle a standard fault using a fault handler.
Processes can be suspended on an uncaught fault. This behavior takes precedence over the Exit on Standard Fault setting.
no
Expression Language
Specifies the language used in building variable and other expressions. The default is XPath 1.0. There is also built in support for XQuery 1.0 and Javas-Script 1.5 Other languages can also be added.
urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0
Extensions
Indicates element and attribute extensions to the WS-BPEL 2.0 specification that are not understood by Process Developer exist in the process. Extensions can also exist in most other BPEL constructs, such as partner links and activities. For details, see
Declaring Extension Elements and Attributes
.
none
Links are Transitions
By default, allows links to completed activities. For details, see
Process Developer Extension for Links
.
yes
Message Exchanges
A process or scope property that can be selected as an attribute of a receive or onMessage and its matching replies
(none)
Process Level Compensation/Termination
This is a Process Developer extension to WS-BPEL 2.0. Specifies whether the process as a whole can be compensated and terminated by platform-specific means. The process instance can be compensated after normal completion. For details, see
Creating a BPEL Process as a Service for Another BPEL Process
.
If you set this to
yes
, the Process Editor displays new tabs. For details, see
Process Editor Compensation and Termination Handler Tabs
.
no
Process Name
You can specify a process name that differs from the BPEL file name. This is useful if you create different or updated versions of the same process. You can name the BPEL file with meaningful version information, but can use the same internal process name. The process name property, not the BPEL filename, is known to the server engine.
name of the BPEL file
Query Language
Specifies the XML query language. The default is XPath 1.0. Also available for future standards as they evolve.
urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0
Suppress Join Failure
A join condition is a property of all activity types and provides status about an incoming link. A join failure indicates that link execution failed. At the process level, this attribute specifies whether a join failure is suppressed for the whole process. Can be overridden at the activity level and can be specified as a preference for all new processes. See
Process Developer Preferences
.
yes
Target Namespace
The XML namespace that refers to the required WSDL information. This is a required property.
none
Image Generation
See
Generate Deployment Image
Automatic


Updated March 30, 2020