PowerCenter 8.

x New Features

Education Services
Version PC8_NFD_20060116



‡ Architecture and Framework ‡ New Licensing Options ‡ Administration Console ‡ Developer New Features


Architecture and Framework



‡ Service-Oriented Architecture ‡ Domain, Nodes & Services ‡ Services
‡ Core Services ‡ Application Services


Service-Oriented Architecture


Service-Oriented Architecture (SOA)
‡ SOA: An application architecture in which all functions, or services, invoke software interfaces that perform business processes. ‡ Service: A task performed by a service provider to achieve desired end results for a service consumer. Both provider and consumer are roles played by software agents on behalf of their owners.

Service Consumer



Service Provider


SOA (cont.)
‡ For example, in PowerCenter:
‡ PowerCenter Server has become a service, the Integration Service ‡ No more Repository Server, but PowerCenter includes a Repository Service

‡ Client applications are the same, but work on top of the new services framework


Same Clients, New Framework
Integration Service


Repository Service Repository Service Process

Administration Console

PowerCenter Client



Domains, Nodes and Services


Domains, Nodes, and Services
Node 1 (machine)
Service Manager Core Services

Node 2 (machine)
Service Manager Core Services

Node 3 (machine)
Service Manager Core Services

Application Services
Integration Service Repository Service SAP BW Service Web Services Hub

Application Services
Integration Service Repository Service SAP BW Service Web Services Hub

Application Services
Integration Service Repository Service SAP BW Service Web Services Hub


PowerCenter Domain
‡ Domain can be a single PowerCenter installation
‡ e.g. single Integration Service, Repository Service


PowerCenter Domain (cont.)
‡ Or it can be multiple PowerCenter installations


Human Resources



‡ A collection of nodes and services ‡ Primary unit of administration


Configuring Domains
‡ Domains and components are managed in the Administration Console ‡ Centralizes configuration and administration


‡ The logical representation of a machine in a domain ‡ Each node runs a Service Manager
‡ Lightweight service

‡ One node in domain is a gateway node


Gateway Node
‡ Routes service requests from PowerCenter Client to available nodes ‡ One node in domain serves as a gateway for domain ‡ All core services run on gateway node ‡ If gateway node is unavailable, domain cannot accept service requests


Service Manager
‡ Controls PowerCenter services running on the node ‡ Primary point of control for PowerCenter services ‡ Service on Windows, daemon on UNIX ‡ If Service Manager is not running, node is unavailable


‡ All PowerCenter processes run as services on a node ‡ All services installed by default.
‡ Define which services run by configuring the node and services.

‡ Two types:
‡ Application ‡ Core


Services (cont.)
Node 1
Service Manager Core Services

Node 2
Service Manager

Application Services
Integration Service Repository Service SAP BW Service Web Services Hub

Service installed and configured to run Service installed, but not configured to run

Core Services

Application Services
Integration Service Repository Service SAP BW Service Web Services Hub


Core Services in a Domain
Node 1
Service Manager

Node 2 (Gateway)
Service Manager

Node 3
Service Manager

Core Services ‡Configuration Service ‡Log Service ‡Service Process Controller

Core Services ‡Configuration Service ‡Log Service ‡Domain Service ‡Gateway Service ‡Authentication Service ‡Admin Service ‡Service Process Controller
Application Services

Core Services ‡Configuration Service ‡Service Process Controller

Application Services

Application Services


Core Services
‡ Built in to the domain ‡ Support the domain and application services ‡ Service Manager manages services


Core Services
‡ Gateway Service ‡ Log Service ‡ Configuration Service ‡ Domain Service ‡ Service Process Controller ‡ Licensing Service ‡ Authentication Service ‡ Admin Service

Licensing Service
‡ Manages PowerCenter licenses
‡ Master Gateway Node

‡ Assigns linceses and validates application services when they start ‡ Licenses keys are
‡ Encrypted in a binary file ‡ Original keys ‡ Incremental keys (upgrade)


License Tasks
‡ Create and remove ‡ Assign and unassign ‡ Update to add license keys ‡ View license details ‡ Configure user permissions on license


Log Service
‡ Collects all PowerCenter log events ‡ Processes log events for core and application services, workflows, and sessions ‡ Runs on gateway node by default ‡ When Log Service becomes unavailable:
‡ Core and application services write log events to temporary files

‡ When Log Service becomes available again:
‡ Service Manager processes the temporary files and sends them to the Log Service


Log Event Types
‡ Domain ‡ Service ‡ Session ‡ Workflow ‡ Row error


Application Services
‡ Represent server-based functionality in PowerCenter ‡ Following types:
‡ ‡ ‡ ‡ Repository Service Integration Service SAP BW Service Web Services Hub

‡ You designate a node on which to run the service process


Service Processes
‡ The runtime instance of a service running on a node ‡ Service processes do all the work


New Licensing Features


‡ High Availability ‡ Grid ‡ Pushdown Optimization ‡ Team based Development Changes ‡ Data Profiling Changes ‡ Partitioning Changes


High Availability
Aut mati Fail v r R tart v ry R m t Fail r (HW/ W)

I t grati rvi

a rvi fig

R rvi

it ry


High Availability
‡ Refers to the availability of resources in a computer system when system components fail ‡ Failover ‡ Recovery ‡ Resilience


High Availability (cont.)
Application and Core Services Nodes Primary Nodes

Backup Nodes

Grid Option
Automati Failo er Restart Re o ery

4 4 3 1
Dynami Distribution Sessions on Grid (SonG)

ower enter Adapti e oad alan er

Dynami artitions 1,2,3,4

Heterogenous Hardware Grid


Grid Option Changes
‡ A grid is a group of nodes in a domain ‡ Can create heterogeneous grids ‡ Distributes to available nodes only ‡ Session on grid: Distributes session partitions to different nodes ‡ Workflow on grid: Distributes workflow tasks to different nodes


PowerCenter 8.x Grid vs. 7.x Grid
PowerCenter 7.x Essentially a server grid. A number of Informatica servers were added to form one Server grid. Only homogenous Informatica Servers can be a part of the grid. For forming a grid the requirements for the participating servers are : y Same OS y Same no. of CPU¶s y Same amount of memory space y Same directory structure Any server not fulfilling the above prerequisites cannot be a part of the grid One server in the grid acts as the Master Server to whom all the requests are be routed while other servers are be worker servers. The master server runs all the non-session tasks assigned to the grid. PowerCenter 8.x Nodes are grouped to form a grid.

Heterogeneous nodes can be grouped to form a grid. There is no restriction on the OS, no. of CPU¶s or memory space for the participating nodes. The only restriction is that all the nodes have a common shared directory structure.

Grid is a service just like the Integration Service. The Load Balancer is the component of the Integration Service that dispatches the different tasks to the nodes or the different threads to the DTM processes running on the nodes in the grid. The Load Balancer distributes tasks or threads based on node and resource availability.

Essentially acts as workflow on grid. Individual sessions are assigned to an Informatica Server.

Acts as session on grid whereby the different threads of a session like the reader, writer and transformation threads can be assigned to different nodes.


Grid Option²Resources
‡ Database connections, files, directories, node names, and OS types required by a task ‡ Predefined and user-defined ‡ Load Balancer matches available and required resources
Parameter File1

DB connection2 Parameter File1

DB connection1 Source File1 Node Name1

DB connection1 Source File1 Node Name2


Pushdown Optimization
‡ A session option that causes the Integration Service to push some transformation logic to the source and/or target database ‡ You can choose source-side or target-side optimization, or both ‡ $$PushdownConfig mapping parameter ‡ Benefits:
‡ Can increase session performance ‡ Maintain metadata and lineage in PowerCenter repository ‡ Reduces movement of data (when source and target are on the same database)

Use Cases 
Batch transformation and load²staging and target tables in the same target database  Transformation and load from real-time status table to data warehouse in the same database
Step 1 Step 2



Data Sources

Target Database


Partial Pushdown Optimization to Source 
± One or more transformations can be processed in source database 

Virtual source ± transformations pushed to source  Generated SQL:
± SELECT « FROM s « WHERE (filter/join condition)« GROUP BY«
SQL Extract Source DB Joiner Agg Router Load Target DB


Partial Pushdown Optimization to Target 
± One or more transformations can be processed in target database 

Virtual target ± transformations pushed to target  Generated SQL:
DSQ Extract Source Lookup Transform Expr Load Target DB

Full Pushdown Optimization 
± Source and target are in the same RDBMS ± All transformations can be processed in database 

Data not extracted outside of DB  Generated SQL:
SQL Extract Source DB Expr Agg Filter Load Target DB


Configuring Pushdown Optimization
‡ Configure in Performance settings on the Properties tab in the session properties


How Pushdown Optimization Works
‡ Integration Service executes SQL against the database instead of processing the transformation logic itself ‡ Integration Service analyzes the mapping and writes one or more SQL statements based on the mapping transformation logic ‡ Integration Service analyzes the mapping and session to determine the transformation logic it can push to the database ‡ Integration Service processes transformation logic that it cannot push down to the database

Pushdown Optimization (cont.)
‡ Integration Service converts the expression in the transformation by determining equivalent operators, variables, and functions in the database ‡ If there is no equivalent operator, variable, or function, the Integration Service processes the transformation logic ‡ You can preview which transformations are pushed to the database ‡ You can preview the revised SQL statement for the source or target, but you cannot modify it ‡ Neither the revised SQL statements nor mapping changes are saved to the repository

Pushdown Optimization Preview from Session²Mapping Tab

Transformations Pushed to Source or Target Database

Generated SQL Statement


Pushdown Optimization: Databases Supported
‡ Oracle 9.x and above ‡ IBM DB2 ‡ Teradata ‡ Microsoft SQL Server ‡ Sybase ASE ‡ Databases that use ODBC drivers


Pushdown Optimization : Supported Transformations
To Source 
Aggregator  Expression  Filter  Joiner  Lookup  Sorter  Union

To Target 
Expression  Lookup  Target definition

Guidelines and Restrictions for Pushdown Optimization
‡ No row-level error logging ‡ Database manages error handling ‡ Data results are dependent on database settings (sort order, case sensitivity, etc.) ‡ Some operators, PowerCenter variables, and functions do not get pushed down, or get pushed down to only some databases ‡ Some transformations that can be pushed down have restrictions ‡ Unconnected transformations do not get pushed down ‡ Some partitioning restrictions


Team Based Development Changes
‡ Versioning:
‡ Can explicitly check out objects²opening an object no longer checks it out automatically ‡ Can view older object versions in the workspace

‡ Deployment:
‡ Can assign owners and groups to folders and deployment groups ‡ Can generate deployment control file (XML) to deploy folders and deployment groups with pmrep


Data Profiling Changes
‡ Functional Dependencies Analysis function ‡ Inter-source Structure Inference function ‡ Candidate key and redundancy column analysis ‡ Column lookup domain ‡ Multiple join columns ‡ Can load source rows as part of verbose data and view in an integrated report


Partitioning Changes
‡ Database partitioning
‡ Works with Oracle in addition to DB2

‡ Dynamic partitioning
‡ Integration Service determines the number of partitions to create at run time ‡ Integration Service scales the number of session partitions based on factors such as source database partitions or the number of nodes in a grid ‡ Useful if volume of data increases over time, or you add more CPUs


Administrator Console


‡ Introduction ‡ Administration in PC 8.x vs. Older versions ‡ Configuring Domain ‡ Configuring Services ‡ Managing Folders, users and permissions ‡ Log Viewer


PowerCenter Administration Console
‡ Browser-based utility ‡ Use for administration tasks for the domain and all services
‡ E.g. adding domain users, deleting nodes, creating services

‡ Consolidates administrative tasks that used to be done with previous tools ‡ Need a domain user account to log in


Administration Console


Consolidating Administration Tasks
Repository Server Setup PowerCenter Server Setup Repository Server Administration Console Workflow Manager (register server)

PowerCenter Administration Console


Repository Server Setup Properties
‡ Repository port numbers ‡ Backup directory ‡ Logging severity level
Version 6/7

= N/A in PC 8 = moved to PC 8


PowerCenter Server Setup Properties
‡ Most properties in new Administration Console
Version 6/7

Use new property, Max Processes, instead


Workflow Manager Properties
‡ Specify code page for each node ‡ Server variables
‡ Integration Service variables ‡ Integration Service process variables

‡ No longer register the PowerCenter Server in Workflow Manager


Old Administration Console Tasks
‡ Connections ‡ Locks ‡ Restore and back up ‡ Plug-ins ‡ Upgrade ‡ No longer propagate repository domain connectivity information

Repository Configuration Properties
‡ Most properties in new Administration Console ‡ Timeout properties replace with new resilience properties


Navigating the Administration Console
‡ Domain tab
‡ Navigator ‡ Main window

‡ Logs tab ‡ Administration tab ‡ Manage Account tab


Domain Tab

Domain Objects

Navigator Main Window


Domain Tab Navigator
‡ Shows domain objects ‡ Create and delete objects ‡ Move objects to folders ‡ Upgrade PowerCenter Servers and Repository Agents


Main Window²Domain Properties
View user permissions. Domain Properties View available resources.

Service Status




Main Window²Domain Properties
‡ Shows which services are running on which nodes ‡ Can configure domain properties ‡ Can define user permissions


Main Window²Node Properties

Stop and start node. Edit node properties.

Node Properties


Main Window²Repository Service Properties
Stop and start service. Perform actions on the repository, such as backup. View log events. Define permissions. Register plug-ins. View object locks. View and end users and connections. Edit properties.

Main Window²Integration Service Properties
Stop and start service. Edit associated repository. View log events. Define permissions. Edit properties for the service process on each node.

Edit service properties.


Licensing Service - License Details
View on Domain tab.


Configuring the Log Service
‡ Configure Log Services on the Domain tab of Administrator Console ‡ Nodes that run the Log Service ‡ Shared directory path for log event files ‡ Can export log events ‡ Can purge log events
‡ Manually ‡ Automatically


Configuring the Log Service

Export or purge log events.

Automatic Purge Options

Managing Folders, Users, and Permissions


Logging In
‡ Enter administrator user name and password specified during installation ‡ You can only see objects on which you have permission


Domain Administrators
‡ Have permission on domain ‡ Each domain includes a primary domain administrator
‡ Can create additional domain administrators ‡ Cannot delete primary domain administrator

‡ Can create folders ‡ Can create, edit, and remove domain users


Domain Folders
Create folder Delete folder Move object to another folder Folder Sub-Folder Objects in Selected Folder


Domain Folders
‡ Create and remove folders on the Domain tab ‡ Can put nodes, services, grids, and other folders into a folder


Domain Folders
‡ Can use folders in the domain to organize objects ‡ Can assign users permission on a folder
‡ User inherits permissions on all objects in the folder, even when you add new objects

‡ You might want to use folders to:
‡ Group services by type ‡ Manage security for domain objects


Domain Users
‡ Manage users on the Administration tab ‡ All domain users can manage their own accounts on the Manage Account tab

Add domain users. Domain Users

Remove user.

Managing Your Account

Change password.

Personal Profile Edit profile. User Preferences Edit preferences.


Domain Permissions²Node

Inherited Permissions

Object Permissions

Edit permissions.


Domain Permissions²Repository Service


Administration Console Log Viewer


Viewing Log Events

Search log events. Display Options

Selected Log Event

Log Event Details


Working with Log Events
‡ Logs tab ‡ Can search for log events ‡ Can choose columns in Log Viewer


Searching Log Events
Choose log viewer columns. Goes to Domain tab to configure log service.

Search Options

Save log events.


Developer New Features


‡ Transformation Language Enhancements ‡ Transformation Enhancements ‡ File and ftp Enhancements ‡ Usability and Repository Enhancements ‡ XML Enhancements ‡ Command Line Programs ‡ Recover Changes ‡ Workflow Monitor Log Viewer

Transformation Language Enhancements


23 New Built-In Functions
‡ Regular expression ‡ Financial ‡ Encoding ‡ Compression ‡ And more


User-Defined Functions
‡ Can create user-defined functions to use in transformations and workflow tasks ‡ Build complex expressions and reuse them ‡ Available to other repository users ‡ Include the functions in expressions or other userdefined functions ‡ Include any valid function except aggregate functions


User-Defined Functions (cont.)
‡ Repository-level objects ‡ When you copy, export, or deploy an object that uses a user-defined function, the XML file also includes the function ‡ Can export user-defined functions to an XML file ‡ Two types:
‡ Public: Callable from any transformation expression ‡ Private: Only callable from another user-defined function


Creating User-Defined Functions
Choose Tools > User-Defined Functions

Edit selected function. Create new function.


Creating User-Defined Functions
Function name Function type Argument in expression Expression


Using User-Defined Functions

User-Defined Function Prefix

User-Defined Functions


Custom Functions
‡ Function created outside of PowerCenter using the Custom Functions API (shipped with PowerCenter) ‡ API uses C programming language ‡ Share custom functions with others ‡ Add to a repository as a plug-in ‡ Use in mapping and workflow expressions like native functions


User-Defined v. Custom Functions
‡ Created in the Designer ‡ Repository object ‡ Use in mapping or workflow expressions ‡ Same name ‡ Available to all folders

‡ Created outside the Client ‡ Repository plug-in ‡ Use in mapping or workflow expressions ‡ Unique name ‡ Available to all folders


Custom Function v. Custom Transformations
Custom Functions Custom Transformations
‡ Used inside a PowerCenter ‡ Existing PowerCenter expression which calls a DLL transformation calls a DLL or or shared library shared library ‡ C ‡ Each input row returns one value ‡ Must create a repository plug-in ‡ Must copy files to PowerCenter Client and Integration Service machines, and register the plug-in in each repository ‡ C, C++, or Java ‡ Each input row can return zero or more values ‡ No repository plug-in needed ‡ Must copy DLL or shared library to all Integration Service nodes


Transformation Enhancements


Custom Transformation Enhancements
‡ Java and C++ API (in addition to C) ‡ Can include thread-specific operations in Custom transformation procedures
‡ Can configure the Custom transformation to process each partition using one thread

‡ Can configure a Custom transformation to be partitioned locally or across a grid


Java Transformation
‡ Native transformation that uses Java to transform data ‡ Example: You can define transformation logic to loop through input rows and generate multiple output rows based on a specific condition ‡ Active or passive ‡ Enter Java code snippets in the PowerCenter Client, no need to write all Java code ‡ Do not need an external development environment


Java Transformation (cont.)
‡ Can define, compile, and fix Java code on the Java Code tab of the transformation ‡ Can import third party Java APIs, built-in Java packages, or custom Java packages ‡ PowerCenter Client compiles the code snippets and generates the byte code ‡ Integration Service executes the byte code to process data


Java Transformation²Java Code Tab


Flat File and FTP Enhancements


Flat File Enhancements
‡ Options for merging target partitions:
‡ ‡ ‡ ‡ Not at all (creates one file for each partition, previous behavior) Sequentially (creates one file for all partitions) Concurrently (creates one file for all partitions) File List (creates a file list that references all target files)


Flat File Enhancements
Choose to merge files sequentially, concurrently, or not at all. Or, choose to create a file list. Append data to file. Choose to write header information. Header Command Footer Command


Flat File Enhancements (cont.)
‡ Can append data to existing target and reject files ‡ Can write header and footer information to files
‡ Use target port names (headers only) or commands that specify information

‡ Can use Integer or Double datatypes


Flat File Source and Target Commands
‡ Can specify an operating system command as a source or target in a session ‡ UNIX: Use any valid UNIX command or shell script ‡ Windows: Use any valid DOS command or batch file


Source Commands
‡ Use source commands to:
‡ Generate source data ‡ Transform source data ‡ Generate a source file list

‡ Command sends data to the flat file reader (pipe) ‡ Can improve performance by sending data directly to Integration Service without using a pre-session command ‡ Example that generates a file list:
‡ cd $PMSourceFileDir; ls -l sales-records-Sep-*-2005.dat


Source Commands

Choose File or Command Command Type Enter command


Target Commands
‡ Integration Service writes data to command instead of target flat file ‡ Command typically generates a file that contains target data ‡ Use a command to perform additional processing of flat file target data, such as sorting or compressing ‡ Can increase session performance by pushing some tasks to the target ‡ Example that compresses target data:
‡ compress -c - > $PMTargetFileDir/myCompressedFile.Z

Target Commands

Choose File or Command Enter command


FTP Sources and Targets
FTP Targets: ‡ Can use FTP with new flat file features except target commands
‡ For example, can merge files concurrently on the FTP host

FTP Sources: ‡ Can use FTP to access a source file list ‡ Can use FTP with new flat file features except source commands


FTP Sources and Targets

Retry Period offers some resilience.


Usability and Repository Enhancements


Usability Enhancements
‡ Propagate port description
‡ In the Designer, you can edit a port description and propagate the description to other transformations in the mapping

‡ Autolink by name ports in the workspace
‡ You can autolink ports directly in the workspace by right-clicking ‡ Cannot use prefixes or suffixes when autolinking by name in workspace


Propagating Descriptions

Propagate descriptions.


Autolinking Ports in the Workspace

Right-click and choose your autolink options.

Autolink Options


Environment SQL Enhancements

Connection and Transaction Environment SQL


Environment SQL Enhancements (cont.)
‡ Can use environment SQL to execute an SQL statement at the beginning of each transaction ‡ Integration Service executes transaction environment SQL at the beginning of each transaction ‡ Can still use environment SQL to execute an SQL statement at each connection to the database ‡ Use SQL commands that depend on a transaction being open during the entire read or write process ‡ Example SQL that modifies how the session handles characters:


Unicode Repository
‡ Store metadata from multiple languages in the same repository ‡ Choose UTF-8 as the repository code page ‡ Repository database code page must be UTF-8


Unicode Repository (cont.)


Unicode Repository (cont.)
‡ Use the Microsoft Windows Input Method Editor to enter multibyte characters from any language ‡ No need to run different versions of Microsoft Windows specific to other languages ‡ Fewer code page compatibility restrictions: Client and Integration Service must be subset of repository, no longer two-way compatible


Code Page Compatibility (Version 7)
Lookup and Stored Procedure Database External Procedure and Custom Transformation Procedure Data


PowerCenter Server


PowerCenter Client

Repository Server Repository Agent

External Loader

Repository Database



Code Page Compatibility (Version 8)
Lookup and Stored Procedure Database Sources Targets

External Procedure and Custom Transformation Procedure Data PowerCenter Client Repository Database Integration Service Subset Superset


Repository Data Compression
‡ Repository data is compressed between the Repository Service, Integration Service, and PowerCenter Client ‡ Improves performance when you connect to repositories at remote locations or over slow local networks


Object Queries
‡ Run queries against non-versioned repositories ‡ Object queries search in the repository for reusable objects that meet specified conditions ‡ Run queries from the Designer, Workflow Manager, or Repository Manager ‡ You might want to:
‡ Find object relationships ‡ Find groups of invalidated objects to validate

‡ Create, edit, run, or delete object queries in the Query Browser


Query Browser
Access Query Browser from the Designer, Workflow Manager, or Repository Manager Choose Tools > Queries. Edit selected query (opens Query Editor). Create new query (opens Query Editor).


Query Editor
Query Type Run the query. Query Name AND Parameter Operator Value


Query Results


Query Results
‡ For non-versioned repositories, Query Results only show reusable objects ‡ In the Query Results window, you can:
‡ ‡ ‡ ‡ Export some or all objects to an XML file Save results to an HTML file View dependencies for an object Validate invalid objects

‡ For versioned repositories, you can also:
‡ Check in objects ‡ Compare versions ‡ And more«


XML Enhancements


‡ Filter data with query predicate ‡ Create a default namespace ‡ Import part of an XML schema ‡ Use anySimpleType


Command Line Programs


Command Line Programs
‡ infacmd
‡ New program to administer application services and service processes.

‡ pmrepagent
‡ Discontinued. Use replacement commands in pmrep.

‡ pmrep
‡ Includes former pmrepagent commands. Also includes new syntax to connect to a domain.

‡ pmcmd
‡ Updated to support new Integration Service functionality.


Example infacmd Commands
‡ AddLicense ‡ EnableService ‡ GetLog ‡ GetServiceStatus ‡ RemoveNode ‡ UpdateNode ‡ And more


pmcmd Changes
‡ pingservice instead of pingserver ‡ getservicedetails instead of getserverdetails, etc. ‡ Includes syntax to specify domain and Integration Service information instead of PowerCenter Server information
‡ ‡ ‡ ‡ ‡ aborttask connect gettaskdetails startworkflow And more


pmrep Changes
‡ infacmd EnableService instead of pmrep EnableRepository ‡ infacmd DefineRepositoryService instead of pmrep AddRepository ‡ Includes syntax to specify domain and Repository Service information instead of Repository Server information
‡ ‡ ‡ ‡ ‡ Connect DeployFolder Notify Register And more

Ported pmrepagent Commands
‡ Ported commands use new syntax for domain information ‡ Backup ‡ Create ‡ Delete ‡ Registerplugin ‡ Restore ‡ Unregisterplugin ‡ Upgrade

Recovery Changes


Recovery in PowerCenter 8
‡ You recover interrupted workflows and the tasks in them²no longer recover only a session
‡ To recover a session, recover the workflow containing the session

‡ Interrupted workflow: A workflow that stops executing before it completes ‡ You can recover a workflow that is suspended, stopped, aborted, or terminated
‡ When a workflow fails or succeeds, you cannot recover it


Recovery in PowerCenter 8 (cont.)
‡ Integration Service saves the workflow state in a shared file system instead of in memory²all nodes in a grid can access the information ‡ You still manually recover workflows
‡ With high availability option, Domain Service can recover a workflow automatically after failover

‡ Performance improvement when recovering sessions ‡ Data still must be repeatable/ordered


Recover vs. Restart
‡ Recover workflow:
‡ Recovered workflow is a continuation of the original workflow run ‡ Integration Service appends log events to the same log ‡ Workflow Monitor shows the workflow as a single run

‡ Restart workflow:
‡ Restarted workflow is a new workflow run, separate from original ‡ Integration Service writes to a new log ‡ Workflow Monitor shows the workflow as a new run


Recovery Changes for pmcmd
‡ New command:
‡ recoverworkflow, to recover a workflow

‡ Discontinued commands:
‡ resumeworkflow ‡ resumeworklet ‡ -recovery parameter in startworkflow


Changes in Recovery Options
‡ Recover Workflow (Workflow Manager) and Recover (Workflow Monitor)
‡ Replaces the menu options Resume/Recover and Resume

‡ Treat Error as Interruption
‡ Replaces Suspend on Error

‡ Recovery Strategy
‡ Replaces the Enable Recovery property for Session and Command tasks


Recovery Menu Options

Recover Workflow in Workflow Manager

Recover in Workflow Monitor


Treat Error As Interruption Option

Treat Error as Interruption


Recovering Sessions
‡ New options affect whether the session is recoverable:
‡ ‡ ‡ ‡ ‡ Source is Static (relational Source Qualifier option) Lookup source is static (Lookup transformation) Output is deterministic (SDK sources) Output is ordered (SDK sources) Handle previous partial load in recovery (SDK targets)


Recovery Strategy Option

Recovery Strategy


Task Recovery Strategy
‡ Each task has a different recovery strategy ‡ When you recover a workflow, you recover each task according to its recovery strategy ‡ All tasks are recoverable by default, except Session and Command tasks ‡ You must set the recovery strategy for Session and Command tasks


Session Recovery Strategy Options
‡ Skip
‡ Session is not recoverable

‡ Resume
‡ Integration Service saves session recovery information and updates recovery tables for a target database ‡ If session interrupts, Integration Service uses saved recovery information to recover it

‡ Restart
‡ Integration Service does not save session recovery information ‡ If session interrupts, Integration Service reruns the session to recover it


Command Task Recovery Strategy
‡ Continue
‡ Command task is not recoverable

‡ Restart
‡ If Command task interrupts, Integration Service must rerun the Command task to recover it

‡ Note: Integration Service reruns all tasks except Session and Command when you recover a workflow


Workflow Monitor Log Viewer


Log Viewer
‡ Log service captures and stores all log events ‡ You can view workflow and Session log events in the Log Viewer in the Workflow Monitor ‡ Log events contain information about:
‡ Tasks the Integration Service performs ‡ Workflows and all sessions in the workflows

‡ Optionally, you can configure to write log events to log files (backward compatible)


Log Viewer
Save Log Events Sort By Columns Click to search messages. Selected Log Event Log Event Details


Log Viewer (cont.)
‡ Can search for key words in messages ‡ Can sort log events by severity, timestamp, node, thread ID, or message ‡ Can save log events to an XML file


Thank You!!!


Sign up to vote on this title
UsefulNot useful