Table of Contents

Search

  1. Preface
  2. Workflows
  3. Workflow Variables
  4. Workflow Parameters
  5. Cluster Tasks
  6. Command Task
  7. Human Task
  8. Mapping Task
  9. Notification Task
  10. Gateways
  11. Workflow Recovery
  12. Workflow Administration

Developer Workflow Guide

Developer Workflow Guide

Gateways Overview

Gateways Overview

A gateway splits a sequence flow into multiple sequence flows or it merges multiple sequence flows into a single sequence flow. The Data Integration Service evaluates the sequence flows at run time and runs the objects on the sequence flows that meet the conditions that you specify.
Add gateways to a workflow in pairs. The first gateway splits the sequence flow from an upstream workflow object and connects to multiple objects that you select. The second gateway merges the sequence flows so that you can connect a single sequence flow to the next object in the workflow. The first gateway is the outgoing gateway. The second gateway is the incoming gateway. A gateway must connect to at least two sequence flows.
Each sequence flow represents a branch that the workflow data can follow. You can connect multiple objects consecutively on a branch. Connect the final sequence flow on each branch to the incoming gateway.
The branches that you create on an outgoing gateway must merge into an incoming gateway of the same type. You can connect multiple workflow objects on each branch before the branches merge into the incoming gateway.
You can add Exclusive gateways and Inclusive gateways to a workflow. Add Exclusive gateways to run the objects on a single branch between the gateways. Add Inclusive gateways to run the objects on multiple branches in parallel. For example, you might use Exclusive gateways to determine that a workflow follows one branch if a mapping runs successfully and follows another branch if the mapping fails. You might use Inclusive gateways run a series of mappings in parallel from a single application.
You can add Exclusive gateways and Inclusive gateways to a branch between two gateways. When you add gateways to a branch between two gateways, add the gateways in pairs. For example, add an outgoing Inclusive gateway and an incoming Inclusive gateway to a branch between two gateways. Or, add an outgoing Exclusive gateway and an incoming Exclusive gateway to the branch. The gateways that you add to the branch are called nested gateways.
The branches that you create on an outgoing gateway must merge into an incoming gateway of the same type. For example, the branches from an outgoing Exclusive gateway must merge into an incoming Exclusive gateway. You can connect multiple workflow objects on each branch before the branches merge into the incoming gateway.
You define conditions on the sequence flows that you create on an outgoing gateway. When the Data Integration Service evaluates the conditions on an outgoing Exclusive gateway, the Data Integration Service runs the first sequence flow with a condition that evaluates to true. When the Data Integration Service evaluates the conditions on an outgoing Inclusive gateway, the Data Integration Service runs every sequence flow with a condition that evaluates to true. The Data Integration Service runs the sequence flows on the Inclusive gateway concurrently.
You must select a default sequence flow on each outgoing gateway. The default sequence flow ensures that data can flow from the outgoing gateway to the incoming gateway if all of the sequence flow conditions evaluate to false. The Data Integration Service runs the default sequence flow on an Exclusive gateway if the conditions on the other sequence flows evaluate to false. The Data Integration Service always runs the default sequence flow on an Inclusive gateway. You do not need to define a condition on the default sequence flow.

0 COMMENTS

We’d like to hear from you!