Preface
Welcome to Informatica Process Developer
- About Informatica Process Developer
- Working in the Eclipse Environment
- Migrating from Earlier Versions
- Saving From One Editing Style to Another (BPMN and Classic)
- Converting Legacy Deployments to Contributions
Using Guide Developer for the First Time
- Launching Process Developer
- Using the Workspace to Store Projects
- Creating an Orchestration Project
  - Changing the Default Location of a Workspace Project
  - Orchestration Project Templates
- Adding or Removing a Project Orchestration Nature
- About Project Orchestration and Validation Builders
- Using Project References
- Creating a New Process
  - Beginning a New Process
  - Selecting the BPMN-Centric or BPEL-Centric Palette
- Importing an Existing BPEL Process
- Importing a Visio XML Drawing File
- Begin Your First Project with Process Developer Assistance
- Setting Up the Embedded Process Server
- Process Developer Orchestration File Resources
Getting Started with Informatica Process Developer
- Using Source Control Systems
- Navigating Through Process Developer
- Windows Perspectives Views and Editors
- Process Developer Perspective
- Guide Developer Debug Perspective
- BPMN-Centric and BPEL-Centric Edit Styles
- Using the Process Developer Process Editor
- Customizing the Process Developer Perspective
- Process Developer Menus and Toolbars
- Process Developer Preferences
- Accessing Process Developer Help
About Interfaces Service References and Local WSDL
- Importing a Local WSDL
- Importing a Service Reference
- Creating a New Interface
- Creating a Java Interface
- Using the Interfaces View to Create Activities
- Creating a WSDL File with Extensions for BPEL
- Using Sample Data for WSDL Messages
- Finding Where a WSDL Component is Used
- Using Process Search
Planning Your BPEL Process
- Using Top-Down or Bottom-Up Process Design
- Using WSDL References for Efficient Design
  - Creating WSDL Extensions for BPEL
  - Starting a Process by Dropping an Operation onto the Process Editor
- Importing WSDL Schema and Other Resources
- Declaring Extensions
  - Using the Process Developer Create XPath Extension
  - Using the Process Developer Disable Selection Failure Fault Extension
- Declaring Extension Elements and Attributes
- Understanding BPEL Process Structure and Properties
- Understanding BPEL Process Lifecycle
- Creating an Executable vs. an Abstract Process
  - Creating an Abstract Process
  - Tips for Working with Abstract Processes
- Creating a BPEL Process as a Service for Another BPEL Process
- Message Exchange Declaration
Participants
- What are Participants
- What are Partner Link Types and Partner Links
- Partner Link Type
- Partner Link
- Using Scoped Partner Links
- Partner Links and Endpoint References
Implementing a BPMN Task or Event in BPEL
- BPMN-to-BPEL Implementation of Tasks and Events
- Overview of BPEL Activities
- Defining an Activity and Its Properties
  - Selecting Values for Activity Properties
  - Selecting Activity Labels
  - Standard Properties for Activities
  - Adding a Background Color to a Task Scope People Activity and Handlers
- Understanding and Using Activity Sequences and Flows
- Receive
- Reply
- Throw
- Rethrow
- Signal
- Exit
- Wait
- Compensate
- Compensate Scope
- Break
- Continue
- Start End None
- Invoke
  - From Part to Variable
  - From Variable to Part
  - Input Variable
  - Output Variable
- Assign
  - Tips for Copy Operations
  - Copy Operation Query and Expression Examples
  - Copy Operation Literal Contents Examples
  - Copy Operation Dynamic Endpoint Reference Example
  - Element to Element Copy Operation with Keep Source Element Name Attribute
  - Copy Operation with Ignore Missing From Data Attribute
- Empty
- Suspend
- Validate
- Opaque
- Creating a Custom Activity
- Creating an Activity by Starting with a WSDL Interface
Implementing a BPMN Gateway or Control Flow
- BPMN-to-BPEL Implementation of Gateways and Control Flow
- Different Ways of Structuring Activities
  - Overview of Control Flow Items
  - Ungrouping Selected Structured Activities
- Gateway
- Pick
- Fork Join
- If
- While
- Repeat Until
- Scope
- For Each
- Sequence
- Flow
Using Variables
- Overview of Variables
- Adding a Variable
- Adding Variable Properties and Property Aliases
- Initializing a Variable
- Viewing Variables
- Deleting a Variable
- Using Sample Data in Process Variables View
- Using the XML Data Wizard
- Finding Where Variables are Used
- Using Variables in a Copy Operation
- Using Variables Based on WSDL Fault Messages
- Mapping WSDL Message Parts in Web Service Interaction Activities
- Validating Variables
- Working with Variable Attachments
Attachments
- Adding an Attachment
- Adding an Attachment for Simulation
- Remote Debugging with Variable Attachments
- Custom Functions for Manipulating Attachments
- Attachment Custom Function Examples
Using Links
- What is a Link
- Process Developer Extension for Links
- Adding a Link Between Activities
- Execution Rules for Links
- Designing With Links vs. Structured Activities
- Links and the Join Condition
- Link Properties
Data Manipulation
- Overview of Data Manipulation in BPEL
- Selecting XPath or XQuery for Expression Building
  - Example XQuery Expressions
  - Example XPath Expressions
- Using the Expression Builder
- Expected Expressions for Conditions Counters and Other Values
- Using the Query Builder
- Creating a Join Condition for an Incoming Link
- Deadline and Duration Expressions
Compensation
- Compensation Handlers and Compensate Activities
  - Default-Order Compensation Example
  - Specified Compensation Example
- Adding a Compensation Handler to a Scope
- Compensating an Invoke Activity
Correlation
What is Correlation
What is a Correlation Set
- Properties
- Property Aliases
- WSDL Syntax and Example for Property Names and Aliases
- Global and Local Correlation Sets
Creating Message Properties and Property Aliases
- Creating a Property Definition
- Creating a Property Alias
Adding a Correlation Set
- XML Syntax
- Example
- Correlation Sets: Required and Optional Properties
Deleting a Correlation Set
Adding Correlations to an Activity
Rules for Declaring and Using Correlation Sets
Correlation Sets and Engine-Managed Correlation
Event Handling
- What is Event Handling
- Adding Event Handlers
  - Adding an onEvent Event Handler
  - Adding an onAlarm Event Handler
- Processing Rules for Events
- Adding Boundary Events
  - Catch and Catch All Boundary Events and Compensate Compensate Scope and Rethrow
  - Using a Variable from a Catch or Interrupting OnEvent Boundary Event
Fault Handling
- What is BPEL Fault Handling
- Defining Catch and CatchAll Fault Handlers
- Fault Handling for Service Invocations
- Adding a Fault Handler
- Fault Handling Processing Rules
- Rules for Catching Faults in a Catch Activity
- Tips on Fault Handling
- Catching Undeclared and SOAP Faults
Simulating and Debugging
- What is the Process Developer Debug Perspective
  - Opening the Process Developer Debug Perspective
  - Switching Between Process Developer Perspectives
- Process Developer Debug Perspective Views and Menus
- Simulating Execution of a BPEL Process
- Supplying and Inspecting Sample Variable Data During Simulation
  - Setting up Sample Data Values for Input Output and Fault Messages
  - Inspecting Process Variables during Simulation
- Selecting Simulation Paths and Properties
- Inspecting Standard Faults During Simulation
- Simulation Preferences
- Setting Debug Preferences
- Debugging Remote Processes Running on the Server
- Correcting Retrying or Completing Activities
- Monitoring Client Message Traffic with TCP IP Monitor
Deploying Your Processes
- Preparing for Deployment
  - Preparing BPEL Files for Deployment
  - Selecting a Server Platform for Deployed Processes
- Endpoint Reference Addressing Considerations
- Overview of Process Deployment Steps
- Creating a Process Deployment Descriptor File
- Creating and Deploying a Business Process Archive Contribution
  - Deploying Project Dependencies and Viewing Excluded Dependencies
  - Deploying Additional Resources
- Managing Deployment Contributions
- Using a BPRD Script to Regenerate and Deploy a BPR Contribution
  - Running a BPRD Ant Script from within Process Developer
  - Running a BPRD Ant Script from the Command Line
- Deployment Complete
- Starting the Server and Running a Process
- How a BPEL Process is Instantiated
- What is Process Versioning
BPEL Unit Testing
- What is BPEL Unit Testing
- Creating a BPEL Unit Test File
- Running a BPEL Unit Test in Process Developer
- Creating and Running a B-unit Ant Script
- Editing a B-unit File
- Debugging a B-unit Test
- Creating and Running BPEL Unit Test Suites
- Example B-unit File
Creating POJO and XQuery Custom Functions
- Custom Functions Overview
- Implementing the Function Context and Adding Annotations
- Sample Custom Function
- Adding Global Custom Functions to the Process Server
- Writing XQuery Functions
Custom Service Interactions
- Using a REST-based Service
- Using an OAuth REST-Based System Service
  - Creating an OAuth Service
  - Specifying Deployment Details for an OAuth Service Provider
- Using a Java Messaging Service Invoke Handler
Process Exception Management
- What is Process Exception Management
- Suspending a Process on Uncaught Faults
Creating Reports for Process Server and Central
- Creating the User Reports Orchestration Project
- Using the Process Developer Report Template
- Using the Process Developer Data Source
- Creating a Data Set from the Process Developer Data Source
- Understanding the Process Developer Data Model
- Deploying a Process Developer Report
- Updating or Deleting a Deployed Report
- Reporting Service
Business Event Processing
- Defining an Event in the Process Deployment Descriptor
- Using System-Defined Events
- Creating an Event-Action BPEL Process
- Activity States Event Properties Task States and Task Event Types
Process Central Forms and Configuration
- What is Process Central
- Creating a Process Central Process Form
- Testing and Debugging Process Central Forms
- Creating a Process Central Configuration File
- Configuring Task Role Filters
- Deploying Forms Reports and Configuration Files
- Adding Multilingual Support to Process Central
- Process Central Advanced Configuration
Building a Process with a System Service
- Using a BPEL Template for a System Service-Based Process
- Alert Service
- Data Access Service
- Email Service
- Identity Service
- Migration Service
- Monitoring Alert Service
- Retry-Policy Service
- Server Log Service
- Shell Command Invoke Service
Human Tasks
- Getting Started with Human Tasks
- Participants and Tasks
- Using the People Activity
- Simulating Debugging Deploying
- Providing Renderings for Task Clients
- Custom Functions
  - Human Tasks Custom Functions
  - WS-HT (Human Task) Custom Functions
- Using Customized Task Clients
  - What is the Informatica Business Process Manager WS-HumanTask API
  - Using the WS-HT and Identity Service SDK
- Creating Custom Task Properties
- Creating Custom Escalation Actions
BPEL Faults and Reports
- BPEL Standard Faults
- User Reports Sample

Designer

9.2.5
- 9.2.4.6

Back Next

For Each

BPMN Implementation: Multi-Instance control flow

The For Each activity contains a scope activity and executes it for a specified count. The execution iterations can occur in parallel or in sequence. The number of iterations to execute is determined by evaluating expressions for a start and final value. These values are inclusive, so a start of one and a final of 10 causes the enclosed scope to execute 10 times.

The expressions for the start and final values must evaluate to an

xs:unsignedint

. If it doesn't, a runtime exception of

bpel:forEachCounterError

occurs. If the final value is greater than the start value then the for each will not execute.

The counter name of the For Each is manifested as an implicit variable within the child scope. The initial value of the variable is set to the current value of the For Each's iteration, which ranges from the start value to the final value. This variable is accessible to all activities nested within the For Each's scope and appears as a variable within the child scope.

Using a Completion Condition for Processing N of M Branches

A For Each activity can include an optional Completion Condition Expression
property that can in turn include an optional Count Successful Branches Only
property.

The completion condition expression can be used to process at least N out of M branches. The expression evaluates to an

xs:unsignedint

value that is used to define condition of N out of M. It is evaluated once, when the for each begins its execution. If the

completionCondition

is not an

xs:unsignedint

, or it is determined that it cannot be met prior to executing, the For Each faults with a

bpel:invalidBranchCondition

. An example of this would be a

completionCondition

value of five when there are only three iterations of the for each.

The property Count Successful Branches Only
can be set to Yes or No. If set to Yes
, it means the Process Developer engine counts branches towards it completion condition that have completed normally (meaning the child scope of the for each iteration did not catch a fault and is eligible for compensation). The default value of No results in the For Each counting the completion of any child iteration towards its completion condition.

At the completion of each iteration, the For Each tests the number of completed scopes versus its completion condition (taking into account the Count Successful Branches Only setting as described above). If it there are not enough iterations remaining to fulfill its completion condition, the For Each faults with a

bpel:completionConditionFailure

and any remaining iterations do not execute, or are terminated in the case of the parallel for each.

A common use of the completion condition is to process only the minimum number of items necessary to complete a scope of work. For example, a BPEL process can call out to many partners in parallel, asking for approvals on an item. The process can require that only three approvals be needed to continue processing the item. Even though the process requested many approvals, it can break off the approval scope of work when only three approvals are received. It can then continue with further processing.

Parallel For Each

You can create a parallel or sequential For Each. In a parallel For Each, instances of the enclosed activity occur simultaneously. Each counter variable is initialized to one of the integer values in the count.

Use a parallel For Each for simultaneous processing of document parts. For example, you can process parts of a complex message variable, such as line items in a purchase order.

A default Message Exchange property that keeps together the correct pair of receive/replies or onMessage/replies, is automatically and implicitly declared in the scope. For details, see

Message Exchange Declaration

Sequential For Each

In a sequential For Each, instances of the enclosed activity execute one at a time.

Required Properties	Optional Properties
Counter Name	Name. See Selecting Activity Labels
Start Counter Value	Completion Condition Expression
Final Counter Value	Count Successful Branches Only
Parallel Execution Flag	Join Condition. See Creating a Join Condition for an Incoming Link
	Suppress Join Failure. See Process Properties
	Comment. See Adding Comments to a Process
	Documentation. See Adding Documentation to a Process
	See Setting Visual Properties and Using Your Own Library of Images
	Execution State. See Viewing the Execution State of an Activity or Link
	Extension Attributes and Extension Elements. See Declaring Extension Elements and Attributes .

To build a For Each

From the Control Flow
palette, drag a Multi-Instance
activity to the Process Editor canvas.

In the Properties view of the For Each, fill in the required properties:

Parallel Execution Flag. Enable this setting to execute all instances of the activity concurrently. Be sure to read the Parallel For Each discussion above to learn the requirements for this type of execution. Disable this setting to execute the scope's activities sequentially.

Add a Counter Name that identifies the enclosed scope's local variable. The default name is counter.

Start Counter Value. Add an unsigned integer for the value. Type in a value or select the

Dialog (...) Button

at the end of the row to open the Expression Builder. For details, see

Using the Expression Builder

Final Counter Value. See Start Counter Value above.

If desired, add values for the optional property Completion Condition
and enable Count Successful Branches to count only successful branches, as described above.

Fill in the properties for the Scope container.

Specify all the properties for each activity in the scope container. Be sure to set a message exchange property for matching receive/replies and

onMessage

/replies within the scope if parallel execution is enabled.

XML Syntax

<forEach counterName="NCName" parallel="yes|no">
   standard-attributes>
   standard-elements
      <startCounterValue expressionLanguage="anyURI">
      </startCounterValue>
      <finalCounterValue expressionLanguage="anyURI">
       </finalCounterValue>
       <completionCondition extension-attribute
        extension-element
        <branches expressionLanguage="URI"?
          countSuccessfulBranchesOnly="yes|no"?>
           an-integer-expression
        </branches>
       </completionCondition>
   activity
</forEach>

Example 1: 100 Executions, Executing if 10 Succeed

<forEach counterName="counter" parallel="no">
   <startCounterValue>1</startCounterValue>
    <finalCounterValue>100</finalCounterValue>
    <completionCondition>
      <branches countSuccessfulBranchesOnly="yes">
        10</branches>
    </completionCondition>
    <scope>...</scope>
</forEach>

Example 2: Serial For Each with Completion Condition

Example 3: Execution Thread of a Parallel For Each Activity

The following illustration shows the execution thread of a parallel For Each that has a counter value of 10. Notice that 10 instances of the enclosed scope are running in parallel.