Professional Documents
Culture Documents
POWERCENTER 8.1.0
WORKFLOW
Content
Workflow Manager
In the Workflow Manager, we can define a set of instructions to execute tasks, such as
sessions, emails, and shell commands. This set of instructions is called a workflow. It
has the following tools to help we develop a workflow.
• Task Developer
It creates tasks that we want to accomplish in the
workflow.
• Worklet Designer
It creates a worklet in the Worklet Designer. A
worklet is an object that groups a set of tasks.
Worklet is similar to a workflow, but without
scheduling information. We can nest worklets inside
a workflow.
• Workflow Designer
It creates a workflow by connecting tasks with links
in the Workflow Designer. We can also create tasks
in the Workflow Designer as we develop the Workflow Manager Windows
workflow.
integration * intelligence * insight 3
Workflow Manager Tools
Workflow Designer
• Maps the execution order and
dependencies of Sessions, Tasks and
Worklets, for the Informatica Server
Task Developer
• Create Session, Shell Command and
Email tasks
• Tasks created in the Task Developer
are reusable
Worklet Designer
• Creates objects that represent a set of
tasks
• Worklet objects are reusable
A Workflow is set of instructions for the Informatica Server to perform data transformation
and load
Combines the logic of Session Tasks, other types of Tasks and Worklets
The simplest Workflow is composed of a Start Task, a Link and one other Task
Link
Start Session
Task Task
We can create the following three types of tasks in the Task Developer.
Command
Session
Email
Click Create.
Session Task-General
Session Task-Properties
Session Task-Mapping
Connection
Before the Integration Service can access a source or target database
in a session, we must configure the database connections in the
Workflow Manager. When we create or modify a session that reads
from or writes to a relational database, we can select configured source
and target database connections.
When we create a connection, we must have the following information
available:
• Database name
Name for the connection.
• Database type
Type of the source or target database.
• Database user name
Name of a user who has the appropriate database permissions to
read from and write to the database. To use an SQL override with
pushdown optimization, the user must also have
permission to create views on the source or
target database.
• Password
Database password (7-bit ASCII only).
• Connect string
Connect string used to communicate with the database.
• Database code page
Code page associated with the database.
integration * intelligence * insight 15
Session Task
Partition Points Partition points mark the boundaries between threads in a pipeline. The
Integration Service redistributes rows of data at partition points. We can add partition points
to increase the number of transformation threads and increase session performance
• Add Partition Point
Click to add a new partition point. When we add a partition point, the transformation
name appears under the Partition Points node.
• Delete Partition Point
Click to delete the selected partition point. We cannot delete certain partition points.
• Edit Partition Point
Click to edit the selected partition point. This opens the Edit Partition Point dialog box.
$$PushdownConfig Mapping
Depending on the database workload, we may want to use source-side,
target-side, or full pushdown optimization at different times. For example,
we might want to use partial pushdown optimization during the peak
hours of the day, but use full pushdown optimization from midnight until
2 a.m. when activity is low.
To use different pushdown optimization configurations at different times, use the $
$PushdownConfig mapping parameter. The parameter lets we run the same session using
the different types of pushdown optimization.
Complete the following steps to configure the mapping parameter:
Create $$PushdownConfig in the Mapping Designer.
When we add the $$PushdownConfig mapping parameter in the Mapping Designer, use the
following values:
Field Value Name $$PushdownConfig Type Parameter Datatype String Precision or Scale
10 Aggregation n/a Initial Value None Description Optional
When we configure the session, choose $$PushdownConfig for the Pushdown Optimization
attribute.
Define the parameter in the parameter file.
Enter one of the following values for $$PushdownConfig in the parameter file:
• None. The Integration Service processes all transformation logic for the session.
• Source. The Integration Service pushes part of the transformation logic to the source
database.
• Source with View. The Integration Service creates a view to represent the SQL
override value, and it runs an SQL statement against this view to push part of the
transformation logic to the source database.
• Target. The Integration Service pushes part of the transformation logic to the target
database.
• Full. The Integration Service pushes all transformation logic to the database.
• Full with View. The Integration Service creates a view to represent the SQL override
value, and it runs an SQL statement against this view to push part of the
transformation logic to the source database. The Integration Service pushes any
remaining transformation logic to the target database.
Session Task-Transformations
Session Task-Components
Pre-Session Command
Shell commands that the Integration
Service performs at the beginning of
a session.
Event-Raise task
Event-Wait task
We can send email during a workflow using the Email task on the Workflow Manager. We
can create reusable Email tasks in the Task Developer for any type of email. Or, we can
create non-reusable Email tasks in the Workflow and Worklet Designer.
Use Email tasks in any of the following locations
Session properties
We can configure the session to send email when the session completes or fails.
Workflow properties
We can configure the workflow to send email when the workflow is interrupted.
Workflows or worklets
We can include an Email task anywhere in the workflow or worklet to send email based
on a condition we define.
Sample Workflow
Developing Workflow
The Workflow Monitor displays workflows that have run at least once. The Workflow
Monitor continuously receives information from the Integration Service and Repository
Service. It also fetches information from the repository to display historic information.
The Workflow Monitor consists of the following windows.
• Navigator window
It displays monitored repositories, servers, and repositories
objects.
• Output window.
It displays messages from the Integration Service and
Repository Service.
• Time window
It displays progress of workflow runs.
• Task view
It displays details about workflow runs in a report format.
• Gantt Chart view
It displays details about workflow runs in chronological Workflow Monitor Windows
format. integration * intelligence * insight 30
Workflow Monitor
The Workflow Monitor displays Workflows that have been run at least once
we can monitor a Server in two modes: online or offline
Online mode
Workflow Monitor continuously receives information from the
Informatica Server and the Repository Server
Offline mode
Workflow Monitor displays historic information about past Workflow
runs by fetching information from the Repository
Monitoring Workflow
Perform the following operations in the Workflow Monitor
Restart -- restart a Task, Workflow or Worklet
Stop -- stop a Task, Workflow, or Worklet
Abort -- abort a Task, Workflow, or Worklet
Resume -- resume a suspended Workflow after a failed task is corrected
View Session and Workflow logs
Abort has a 60 second timeout
If the Server has not completed processing and committing data
during the timeout period, the threads and processes associated with
the Session are killed
Monitoring Workflow