working with power center 8 workflow

8/3/2019 Working With Power Center 8 Workflow

1/33

INFORMATICAINFORMATICAPOWERCENTER 8.1.0POWERCENTER 8.1.0

WORKFLOW


2/33

2integration * intelligence * insight

ContentContent

WORKING WITH POWERCENTER 8

WORKFLOW MANAGER

WORKING WITH POWERCENTER 8

WORKFLOW MONITOR


3/33


Workflow ManagerWorkflow Manager

Workflow Manager

In the Workflow Manager, we can define a set of instructions to execute tasks, such assessions, emails, and shell commands. This set of instructions is called a workflow. Ithas 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. Aworklet is an object that groups a set of tasks.Worklet is similar to a workflow, but withoutscheduling information. We can nest worklets inside

a workflow.

Workflow Designer

It creates a workflow by connecting tasks with linksin the Workflow Designer. We can also create tasksin the Workflow Designer as we develop the

workflow.

Workflow Manager Windows


4/33


Workflow Manager ToolsWorkflow Manager Tools

Workflow Designer

Maps the execution order anddependencies of Sessions, Tasks andWorklets, 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


5/33


Workflow StructureWorkflow Structure

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

Session

Task

Start

Task

Link


6/33


Working With LinksWorking With Links

Use the links to connect each workflow

task. We can specify conditions with linksto create branches in the workflow. TheWorkflow Manager does not allow us touse links to create loops in the workflow.Each link in the workflow can run onlyonce and Workflow Manager does notallow us to create a workflow thatcontains a loop.

By using the following procedure we canlink tasks in the Workflow Designer or theWorklet Designer. To link two tasks.

In the Tasks toolbar, click the LinkTasks button.

In the workspace, click the first taskyou want to connect and drag it to the

second task. A link appears between the two

tasks.

If we want to link multiple tasksconcurrently, we may not want to connecteach link manually.


7/33


Working With LinksWorking With Links

To link tasks concurrently

In the workspace, click the first task you want toconnect.

Ctrl-click all other tasks you want to connect.

Note: Do not use Ctrl+A or Edit > Select All to choosetasks.

Click Tasks > Link Concurrent.

A link appears between the first task you selected andeach task you added. The first task you selected linksto each task concurrently.

If we have a number of tasks that we want to linksequentially, we may not wish to connect each linkmanually

To link tasks sequentially

In the workspace, click the first task you want toconnect.

Ctrl-click the next task you want to connect. Continueto add tasks in the order you want them to run.

Click Tasks > Link Sequential.

Links appear in sequential order between the first task

and each subsequent task you added.


8/33


Workflow TasksWorkflow Tasks

Workflow tasks

Workflow tasks are instructions the Integration Service executes when running a

workflow. Workflow tasks perform functions supplementary to extracting, transforming,and loading data. Workflow tasks include commands, decisions, timers, and emailnotification.

We can create the following types of tasks in the Workflow Manager: Assignment

Assigns a value to a workflow variable. Command

Specifies a shell command to run during the workflow. Control

Stops or aborts the workflow. Decision

Specifies a condition to evaluate. Email

Sends email during the workflow.

Event-RaiseNotifies the Event-Wait task that an event has occurred.

Event-Wait

Waits for an event to occur before executing the next task. Session

Runs a mapping we create in the Designer. Timer

Waits for a timed event to trigger.


9/33


Task DeveloperTask Developer

We can create the following three types of tasks in the Task Developer.

Command

Session

Email


10/33


Creating a Task in the Task DeveloperCreating a Task in the Task Developer

In the Task Developer, click Tasks >

Create.

The Create Task dialog box appears.

Select the task type we want to create,Command, Session, or Email.

Enter a name for the task.

For session tasks, select the mapping wewant to associate with the session.

Click Create.

The Task Developer creates the workflowtask.

Click Done to close the Create Task dialogbox.


11/33


Session TaskSession Task

Server instructions to runs the logic of ONE specific Mapping

e.g. - source and target data location specifications, memory allocation, optional Mappingoverrides, scheduling, processing and load instructions

Becomes a component of a Workflow (orWorklet)

If configured in the Task Developer, the

Session Task is reusable (optional)

Session Task (continued)

Double click on the Session object

Valid Mappings are displayed in the dialog box.

Session Task tabs

General

Properties

Config Object

Mapping

Components

Metadata Extensions


12/33



Session Task-General

Session Task-Properties

Session Task-Config Object


13/33



Session Task Properties

Enable Test Load With a test load, the Integration Servicereads and transforms data without writing to targets.

$Source Connection Value Enter the databaseconnection we want the Integration Service to use for the$Source variable. Select a relational or applicationdatabase connection. We can also choose a$DBConnection parameter. Use the $Source variable inLookup and Stored Procedure transformations to specifythe database location for the lookup table or stored

procedure. $Target Connection Value Enter the database

connection we want the Integration Service to use for the$Target variable. Select a relational or applicationdatabase connection. We can also choose a$DBConnection parameter. Use the $Target variable inLookup and Stored Procedure transformations to specifythe database location for the lookup table or stored

procedure. Treat Source Rows As If the mapping for the session

contains an Update Strategy transformation or a Customtransformation configured to set the update strategy, thedefault option is Data Driven.

Commit Interval In conjunction with the selected commitinterval type, indicates the number of rows. By default, theIntegration Service uses a commit interval of10,000 rows.This option is not available for user-defined commit.

Session Task-Properties


14/33




Line Sequential Buffer Length Affects the way theIntegration Service reads flat files. Increase this settingfrom the default of 1024 bytes per line only if sourceflat file records are larger than 1024 bytes.

On Stored Procedure ErrorRequired if the sessionuses pre- or post-session stored procedures.

If we select Stop Session, the Integration Service

stops the session on errors executing a pre-session or post-session stored procedure.

If we select Continue Session, the IntegrationService continues the session regardless of errorsexecuting pre-session or post-session storedprocedures.

On Pre-Post SQL ErrorRequired if the session usespre- or post-session SQL.

If we select Stop Session, the Integration Servicestops the session errors executing pre-session orpost-session SQL.

If we select Continue, the Integration Servicecontinues the session regardless of errors

executing pre-session or post-session SQL.



15/33



Session Task-Mapping

Connection

Before the Integration Service can access a source or targetdatabase in a session, we must configure the database connectionsin the Workflow Manager. When we create or modify a session thatreads from or writes to a relational database, we can selectconfigured source and target database connections.When we create a connection, we must have the followinginformation available:

Database nameName for the connection.

Database typeType of the source or target database.

Database user nameName of a user who has the appropriate database permissionsto read from and write to the database. To use an SQL overridewith 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.


16/33



Partition Points Partition points mark the boundaries between threads in a pipeline. TheIntegration 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 transformationname appears under the Partition Points node.

Delete Partition PointClick 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 peakhours 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 usingthe different types of pushdown optimization.

Complete the following steps to configure the mapping parameter: Create $$PushdownConfig in the Mapping Designer.


17/33



When we add the $$PushdownConfig mapping parameter in the Mapping Designer, use thefollowing values:

Field Value Name $$PushdownConfig Type Parameter Datatype String Precision or Scale10 Aggregation n/a Initial Value None Description Optional

When we configure the session, choose $$PushdownConfig for the Pushdown Optimizationattribute.

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 SQLoverride value, and it runs an SQL statement against this view to push part of thetransformation 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 overridevalue, and it runs an SQL statement against this view to push part of thetransformation logic to the source database. The Integration Service pushes anyremaining transformation logic to the target database.


18/33



Session Task-Transformations

Allows overrides of sometransformation properties Does notchange the properties in the Mapping

Session Task-Components

Pre-Session CommandShell commands that the IntegrationService performs at the beginning ofa session.

Post-Session Success Command

Shell commands that the Integration

Service performs after the sessioncompletes successfully

Post-Session Failure Command

Shell commands that the IntegrationService performs after the session ifthe session fails.


19/33


Event-TaskEvent-Task

Event-Raise task

The Event-Raise task represents the locationof a user-defined event. A user-defined eventis the sequence of tasks in the branch fromthe Start task to the Event-Raise task. Whenthe Integration Service runs the Event-Raisetask, the Event-Raise task triggers the user-defined event.

To use an Event-Raise task In the Workflow Designer workspace,

create an Event-Raise task and place it inthe workflow to represent the user-defined event we want to trigger.

A user-defined event is the sequence oftasks in the branch from the Start task tothe Event-Raise task.

Double-click the Event-Raise task to openit.

Click the Open button in the Value fieldon the Properties tab to open the EventsBrowser for user-defined events.

Choose an event in the Events Browser. Click OK twice to return to the workspace.


20/33


Event-TaskEvent-Task

Event-Wait task

The Event-Wait task waits for a predefinedevent or a user-defined event. A predefinedevent is a file-watch event. When we use theEvent-Wait task to wait for a predefinedevent, we specify an indicator file for theIntegration Service to watch. The IntegrationService waits for the indicator file to appear.Once the indicator file appears, the

Integration Service continues running tasksafter the Event-Wait task.

To wait for a user-defined event

In the workflow, create an Event-Waittask and double-click the Event-Waittask to open it.

In the Events tab of the task, selectUser-Defined.

Click the Event button to open theEvents Browser dialog box.

Select a user-defined event for theIntegration Service to wait.

Click OK twice.


21/33


E-Mail TaskE-Mail Task

We can send email during a workflow using the Email task on the Workflow Manager. Wecan create reusable Email tasks in the Task Developer for any type of email. Or, we cancreate 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 emailbased on a condition we define.


22/33


E-Mail TaskE-Mail Task

We can create Email tasks in the Task Developer, WorkletDesigner, and Workflow Designer.

To create an Email task in the Task Developer: In the Task Developer, click Tasks > Create. The Create

Task dialog box appears. Select an Email task and enter a name for the task. Click

Create. The Workflow Manager creates an Email task in the workspace.

Click Done.

Double-click the Email task in the workspace. The EditTasks dialog box appears. Click Rename to enter a name for the task. Enter a description for the task in the Description field. Click the Properties tab. Enter the fully qualified email address of the mail recipient

in the Email User Name field. Enter the subject of the email in the Email Subject field. Or,

we can leave this field blank. Click the Open button in the Email Text field to open the

Email Editor. Enter the text of the email message in the Email Editor. We

can leave the Email Text field blank. Note: We canincorporate format tags and email variables in a post-session email. However, we cannot add them to an Emailtask outside the context of a session.

Click OK twice to save the changes.


23/33


WorkletWorklet

A worklet is an object that represents a set of tasks that wecreate in the Worklet Designer. Create a worklet when we

want to reuse a set of workflow logic in more than oneworkflow. To run a worklet, include the worklet in a workflow. The

workflow that contains the worklet is called the parentworkflow. When the Integration Service runs a worklet, itexpands the worklet to run tasks and evaluate links within theworklet. It writes information about worklet execution in theworkflow log.

To create a reusable worklet In the Worklet Designer, click Worklet > Create. The

Create Worklet dialog box appears. Enter a name for the worklet. Click OK. The Worklet Designer creates a Start task in the worklet.

To create a non-reusable worklet: In the Workflow Designer, open a workflow. Click Tasks > Create. For the Task type, select Worklet. Enter a name for the task. Click Create. The Workflow Designer creates the worklet

and adds it to the workspace.

Click Done.


24/33


Workflow SchedulerWorkflow Scheduler

Workflow Scheduler Objects

Setup reusable schedules toassociate with multiple Workflows-Used in Workflows and Session Tasks


25/33


Server ConnectionsServer Connections

Configure Server data access connections- Used in Session Tasks


26/33


Relational Connections (Native)Relational Connections (Native)

Creating a relational (database)

connection Instructions to the Server to

locate relational tables

Used in Session Tasks

Relational Connections Properties

Define native relational (database)connection


27/33


FTP ConnectionFTP Connection

Creating an FTP connection

Instructions to the Server to ftp flat files Used in Session Tasks


28/33


Workflows DesignWorkflows Design

Sample Workflow

Developing Workflow


29/33


Workflows DesignWorkflows Design

Building Workflow Components

Add Sessions and other Tasks tothe Workflow

Connect all Workflow componentswith Links

Save the Workflow

Start the Workflow

NOTE: Sessions in a workflow can

be executed independently


30/33


Workflow MonitorWorkflow Monitor

Workflow Monitor

We can monitor workflows and tasks in the Workflow Monitor. View details about a

workflow or task in Gantt Chart view or Task view. We can run, stop, abort, andresume workflows from the Workflow Monitor. We can view sessions and workflow logevents in the Workflow Monitor Log Viewer.

The Workflow Monitor displays workflows that have run at least once. The WorkflowMonitor continuously receives information from the Integration Service and RepositoryService. 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 repositoriesobjects.

Output window.

It displays messages from the Integration Service andRepository 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 chronologicalformat.

Workflow Monitor Windows


31/33



The Workflow Monitor displays Workflows that have been run at least oncewe can monitor a Server in two modes: online or offline

Online mode

Workflow Monitor continuously receives information from theInformatica Server and the Repository Server

Offline mode

Workflow Monitor displays historic information about past Workflow

runs by fetching information from theR

epository

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 dataduring the timeout period, the threads and processes associated withthe Session are killed


32/33



Monitoring Workflow

Monitoring Window Filtering

Task View provides filtering

Truncating Monitor Logs


33/33


The End

working with power center 8 workflow

Documents