PC 102 GettingStarted en
PC 102 GettingStarted en
PC 102 GettingStarted en
10.2
Getting Started
Informatica PowerCenter Getting Started
10.2
September 2017
© Copyright Informatica LLC 1998, 2020
This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be
reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC.
Informatica, the Informatica logo, and PowerCenter are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout
the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company and product names may be
trade names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights
reserved. Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta
Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated.
All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights
reserved. Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved.
Copyright © Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright
© Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo
Communications, Inc. All rights reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH. All
rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © International Business Machines Corporation. All rights reserved. Copyright ©
yWorks GmbH. All rights reserved. Copyright © Lucent Technologies. All rights reserved. Copyright © University of Toronto. All rights reserved. Copyright © Daniel
Veillard. All rights reserved. Copyright © Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved.
Copyright © PassMark Software Pty Ltd. All rights reserved. Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All rights reserved.
Copyright © Red Hat, Inc. All rights reserved. Copyright © The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright © EMC
Corporation. All rights reserved. Copyright © Flexera Software. All rights reserved. Copyright © Jinfonet Software. All rights reserved. Copyright © Apple Inc. All rights
reserved. Copyright © Telerik Inc. All rights reserved. Copyright © BEA Systems. All rights reserved. Copyright © PDFlib GmbH. All rights reserved. Copyright ©
Orientation in Objects GmbH. All rights reserved. Copyright © Tanuki Software, Ltd. All rights reserved. Copyright © Ricebridge. All rights reserved. Copyright © Sencha,
Inc. All rights reserved. Copyright © Scalable Systems, Inc. All rights reserved. Copyright © jQWidgets. All rights reserved. Copyright © Tableau Software, Inc. All rights
reserved. Copyright© MaxMind, Inc. All Rights Reserved. Copyright © TMate Software s.r.o. All rights reserved. Copyright © MapR Technologies Inc. All rights reserved.
Copyright © Amazon Corporate LLC. All rights reserved. Copyright © Highsoft. All rights reserved. Copyright © Python Software Foundation. All rights reserved.
Copyright © BeOpen.com. All rights reserved. Copyright © CNRI. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various
versions of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or
agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.
This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software
copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License
Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any
kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California,
Irvine, and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and
redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.
This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or
without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http://www.dom4j.org/ license.html.
This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at
http:// www.gnu.org/software/ kawa/Software-License.html.
This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & Wireless
Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software
are subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.
This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at
http:// www.pcre.org/license.txt.
This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php.
This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://
www.stlport.org/doc/ license.html, http://asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://
httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/
release/license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/
license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/
licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt; http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/
Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/
license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/
software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/
iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/
index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt;
http://www.schneier.com/blowfish.html; http://www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/CreateJS/
EaselJS/blob/master/src/easeljs/display/Bitmap.js; http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://
jdbc.postgresql.org/license.html; http://protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/
LICENSE; http://web.mit.edu/Kerberos/krb5-current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; https://github.com/lyokato/libgeohash/blob/
master/LICENSE; https://github.com/hjiang/jsonxx/blob/master/LICENSE; https://code.google.com/p/lz4/; https://github.com/jedisct1/libsodium/blob/master/
LICENSE; http://one-jar.sourceforge.net/index.php?page=documents&file=license; https://github.com/EsotericSoftware/kryo/blob/master/license.txt; http://www.scala-
lang.org/license.html; https://github.com/tinkerpop/blueprints/blob/master/LICENSE.txt; http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/
intro.html; https://aws.amazon.com/asl/; https://github.com/twbs/bootstrap/blob/master/LICENSE; https://sourceforge.net/p/xmlunit/code/HEAD/tree/trunk/
LICENSE.txt; https://github.com/documentcloud/underscore-contrib/blob/master/LICENSE, and https://github.com/apache/hbase/blob/master/LICENSE.txt.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and
Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary
Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://
opensource.org/licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/
licenses/artistic-license-1.0) and the Initial Developer’s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).
This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this
software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab.
For further information please visit http://www.extreme.indiana.edu/.
This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject
to terms of the MIT license.
DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied
warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC does not warrant that this software or documentation is error free. The
information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation
is subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software
Corporation ("DataDirect") which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES
OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH
OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
The information in this documentation is subject to change without notice. If you find any problems in this documentation, please report them to us in writing at
Informatica LLC 2100 Seaport Blvd. Redwood City, CA 94063.
Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE
INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.
4 Table of Contents
Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
PowerCenter Repository and User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
PowerCenter Source and Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table of Contents 5
Creating an Aggregator Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Creating an Expression Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Creating a Lookup Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Connecting the Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Designer Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Using the Overview Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Arranging Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating a Session and Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating the Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating the Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Running the Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Viewing the Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6 Table of Contents
Appendix B: Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Table of Contents 7
Preface
PowerCenter® Getting Started is written for the developers and software engineers who are responsible for
implementing a data warehouse. It provides a tutorial to help first-time users learn how to use PowerCenter.
PowerCenter Getting Started assumes you have knowledge of your operating systems, relational database
concepts, and the database engines, flat files, or mainframe systems in your environment. The guide also
assumes you are familiar with the interface requirements for your supporting applications.
Informatica Resources
Informatica Network
Informatica Network hosts Informatica Global Customer Support, the Informatica Knowledge Base, and other
product resources. To access Informatica Network, visit https://network.informatica.com.
To access the Knowledge Base, visit https://kb.informatica.com. If you have questions, comments, or ideas
about the Knowledge Base, contact the Informatica Knowledge Base team at
KB_Feedback@informatica.com.
Informatica Documentation
To get the latest documentation for your product, browse the Informatica Knowledge Base at
https://kb.informatica.com/_layouts/ProductDocumentation/Page/ProductDocumentSearch.aspx.
If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation
team through email at infa_documentation@informatica.com.
8
Informatica Product Availability Matrixes
Product Availability Matrixes (PAMs) indicate the versions of operating systems, databases, and other types
of data sources and targets that a product release supports. If you are an Informatica Network member, you
can access PAMs at
https://network.informatica.com/community/informatica-network/product-availability-matrices.
Informatica Velocity
Informatica Velocity is a collection of tips and best practices developed by Informatica Professional
Services. Developed from the real-world experience of hundreds of data management projects, Informatica
Velocity represents the collective knowledge of our consultants who have worked with organizations from
around the world to plan, develop, deploy, and maintain successful data management solutions.
If you are an Informatica Network member, you can access Informatica Velocity resources at
http://velocity.informatica.com.
If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional
Services at ips@informatica.com.
Informatica Marketplace
The Informatica Marketplace is a forum where you can find solutions that augment, extend, or enhance your
Informatica implementations. By leveraging any of the hundreds of solutions from Informatica developers
and partners, you can improve your productivity and speed up time to implementation on your projects. You
can access Informatica Marketplace at https://marketplace.informatica.com.
To find your local Informatica Global Customer Support telephone number, visit the Informatica website at
the following link:
http://www.informatica.com/us/services-and-training/support-services/global-support-centers.
If you are an Informatica Network member, you can use Online Support at http://network.informatica.com.
Preface 9
Chapter 1
Product Overview
This chapter includes the following topics:
• Introduction, 10
• Informatica Domain, 13
• PowerCenter Repository, 15
• Informatica Administrator, 15
• Domain Configuration, 16
• PowerCenter Client, 17
• PowerCenter Repository Service, 22
• PowerCenter Integration Service, 23
• Web Services Hub, 23
• Metadata Manager, 24
Introduction
PowerCenter provides an environment that allows you to load data into a centralized location, such as a data
warehouse or operational data store (ODS). You can extract data from multiple sources, transform the data
according to business logic you build in the client application, and load the transformed data into file and
relational targets.
PowerCenter also provides the ability to view and analyze business information and browse and analyze
metadata from disparate metadata repositories.
• Informatica domain. The Informatica domain is the primary unit for management and administration
within PowerCenter. The Service Manager runs on an Informatica domain. The Service Manager supports
the domain and the application services. Application services represent server-based functionality. The
domain supports PowerCenter and Informatica application services. PowerCenter application services
include the PowerCenter Repository Service, PowerCenter Integration Service, Web Services Hub, and SAP
BW Service. Informatica Services include the Data Integration Service, Model Repository Service, and the
Analyst Service.
• PowerCenter repository. The PowerCenter repository resides in a relational database. The repository
database tables contain the instructions required to extract, transform, and load data.
• Informatica Administrator. Informatica Administrator is a web application that you use to administer the
Informatica domain and PowerCenter security.
10
• Domain configuration. The domain configuration is a set of relational database tables that stores the
configuration information for the domain. The Service Manager on the master gateway node manages the
domain configuration. The domain configuration is accessible to all gateway nodes in the domain.
• PowerCenter Client. The PowerCenter Client is an application used to define sources and targets, build
mappings and mapplets with the transformation logic, and create workflows to run the mapping logic. The
PowerCenter Client connects to the repository through the PowerCenter Repository Service to modify
repository metadata. It connects to the Integration Service to start workflows.
• PowerCenter Repository Service. The PowerCenter Repository Service accepts requests from the
PowerCenter Client to create and modify repository metadata and accepts requests from the Integration
Service for metadata when a workflow runs.
• PowerCenter Integration Service. The PowerCenter Integration Service extracts data from sources and
loads data to targets.
• Web Services Hub. Web Services Hub is a gateway that exposes PowerCenter functionality to external
clients through web services.
• SAP BW Service. The SAP BW Service extracts data from and loads data to SAP NetWeaver BI. If you use
PowerExchange® for SAP NetWeaver BI, you must create and enable an SAP BW Service in the
Informatica domain.
• Metadata Manager Service. The Metadata Manager Service runs the Metadata Manager web application.
You can use Metadata Manager to browse and analyze metadata from disparate metadata repositories.
Metadata Manager helps you understand and manage how information and processes are derived, how
they are related, and how they are used. Metadata Manager stores information about the metadata to be
analyzed in the Metadata Manager repository.
Introduction 11
The following illustration shows PowerCenter components:
Sources
PowerCenter accesses the following sources:
• Relational. Oracle, Sybase ASE, Informix, IBM DB2, Microsoft SQL Server, SAP HANA, and Teradata.
• File. Fixed and delimited flat file, COBOL file, XML file, and web log.
• Application. You can purchase additional PowerExchange products to access business sources such as
Hyperion Essbase, WebSphere MQ, IBM DB2 OLAP Server, JMS, Microsoft Message Queue, PeopleSoft,
SAP NetWeaver, SAS, Siebel, TIBCO, and webMethods.
• Mainframe. You can purchase PowerExchange to access source data from mainframe databases such as
Adabas, Datacom, IBM DB2 OS/390, IBM DB2 OS/400, IDMS, IDMS‑X, IMS, and VSAM.
• Other. Microsoft Excel, Microsoft Access, and external web services.
• Relational. Oracle, Sybase ASE, Sybase IQ, Informix, IBM DB2, Microsoft SQL Server, SAP HANA, and
Teradata.
• File. Fixed and delimited flat file and XML.
• Application. You can purchase additional PowerExchange products to load data into business sources
such as Hyperion Essbase, WebSphere MQ, IBM DB2 OLAP Server, JMS, Microsoft Message Queue,
PeopleSoft EPM, SAP NetWeaver, SAP NetWeaver BI, SAS, Siebel, TIBCO, and webMethods.
• Mainframe. You can purchase PowerExchange to load data into mainframe databases such as IBM DB2
for z/OS, IMS, and VSAM.
• Other. Microsoft Excel, Microsoft Access, and external web services.
You can load data into targets using ODBC or native drivers, FTP, or external loaders.
Informatica Domain
PowerCenter has a service-oriented architecture that provides the ability to scale services and share
resources across multiple machines. The Informatica domain supports the administration of the
PowerCenter and Informatica services. A domain is the primary unit for management and administration of
services in PowerCenter.
• One or more nodes. A node is the logical representation of a machine in a domain. A domain may contain
more than one node. The node that hosts the domain is the master gateway for the domain. You can add
other machines as nodes in the domain and configure the nodes to run application services such as the
Integration Service or Repository Service. All service requests from other nodes in the domain go through
the master gateway.
A node runs service processes, which are the runtime representation of the application services running
on a node.
• Service Manager. The Service Manager is built into the domain to support the domain and the application
services. The Service Manager runs on each node in the domain. The Service Manager starts and runs the
application services on a machine.
• Application services. A group of services that represent Informatica server-based functionality. The
application services that run on each node in the domain depend on the way you configure the node and
the application service.
You use Informatica Administrator to manage the domain.
If you have the high availability option, you can scale services and eliminate single points of failure for
services. The Service Manager and application services can continue running despite temporary network or
hardware failures. High availability includes resilience, failover, and recovery for services and tasks in a
domain.
Informatica Domain 13
The following image shows a Informatica domain with three nodes:
This domain has a master gateway on Node 1. Node 2 runs a PowerCenter Integration Service, and Node 3
runs the PowerCenter Repository Service.
Related Topics:
• “Informatica Administrator” on page 15
Service Manager
The Service Manager supports the domain and the application services. The Service Manager performs the
following functions:
Application Services
When you install Informatica, the installation program installs the following application services:
PowerCenter Repository
The PowerCenter repository resides in a relational database. The repository stores information required to
extract, transform, and load data. It also stores administrative information such as permissions and
privileges for users and groups that have access to the repository. PowerCenter applications access the
PowerCenter repository through the Repository Service.
You administer the repository through Informatica Administrator and command line programs.
• Global repository. The global repository is the hub of the repository domain. Use the global repository to
store common objects that multiple developers can use through shortcuts. These objects may include
operational or application source definitions, reusable transformations, mapplets, and mappings.
• Local repositories. A local repository is any repository within the domain that is not the global repository.
Use local repositories for development. From a local repository, you can create shortcuts to objects in
shared folders in the global repository. These objects include source definitions, common dimensions and
lookups, and enterprise standard transformations. You can also create copies of objects in non-shared
folders.
You can view repository metadata in the Repository Manager. Informatica Metadata Exchange (MX) provides
a set of relational views that allow easy SQL access to the PowerCenter metadata repository.
Informatica Administrator
Informatica Administrator is a web application that you use to administer the PowerCenter domain and
PowerCenter security. You can also administer application services for the Informatica Analyst and
Informatica Developer. Application services for Informatica Analyst and Informatica Developer include the
Analyst Service, the Model Repository Service, and the Data Integration Service.
Domain Page
Administer the Informatica domain on the Domain page of the Administrator tool. Domain objects include
services, nodes, and licenses.
• Manage application services. Manage all application services in the domain, such as the Integration
Service and Repository Service.
• Configure nodes. Configure node properties, such as the backup directory and resources. You can also
shut down and restart nodes.
• Manage domain objects. Create and manage objects such as services, nodes, licenses, and folders.
Folders allow you to organize domain objects and manage security by setting permissions for domain
objects.
PowerCenter Repository 15
• View and edit domain object properties. View and edit properties for all objects in the domain, including
the domain object.
• View log events. Use the Log Viewer to view domain, PowerCenter Integration Service, SAP BW Service,
Web Services Hub, and PowerCenter Repository Service log events.
• Generate and upload node diagnostics. You can generate and upload node diagnostics to the
Configuration Support Manager. In the Configuration Support Manager, you can diagnose issues in your
Informatica environment and maintain details of your configuration.
Other domain management tasks include applying licenses and managing grids and resources.
Security Tab
You administer PowerCenter security on the Security tab of Informatica Administrator. You manage users
and groups that can log in to the following PowerCenter applications:
• Administrator tool
• PowerCenter Client
• Metadata Manager
You can also manage users and groups for the Informatica Developer and Informatica Analyst.
• Manage native users and groups. Create, edit, and delete native users and groups.
• Configure LDAP authentication and import LDAP users and groups. Configure a connection to an LDAP
directory service. Import users and groups from the LDAP directory service.
• Manage roles. Create, edit, and delete roles. Roles are collections of privileges. Privileges determine the
actions that users can perform in PowerCenter applications.
• Assign roles and privileges to users and groups. Assign roles and privileges to users and groups for the
domain and services.
• Manage operating system profiles. Create, edit, and delete operating system profiles. An operating
system profile is a level of security that the Integration Services uses to run workflows. The operating
system profile contains the operating system user name, service process variables, and environment
variables. You can configure the Integration Service to use operating system profiles to run workflows.
Domain Configuration
The Service Manager maintains configuration information for an Informatica domain in relational database
tables. The configuration is accessible to all gateway nodes in the domain. The domain configuration
database stores the following types of information about the domain:
• Domain configuration. Domain metadata such as the host names and the port numbers of nodes in the
domain. The domain configuration database also stores information on the master gateway node and all
other nodes in the domain.
• Usage. Includes CPU usage for each application service and the number of Repository Services running in
the domain.
• Users and groups. Information on the native and LDAP users and the relationships between users and
groups.
• Privileges and roles. Information on the privileges and roles assigned to users and groups in the domain.
PowerCenter Client
The PowerCenter Client application consists of the tools to manage the repository and to design mappings,
mapplets, and sessions to load the data. The PowerCenter Client application has the following tools:
• Designer. Use the Designer to create mappings that contain transformation instructions for the
Integration Service.
• Mapping Architect for Visio. Use the Mapping Architect for Visio to create mapping templates that
generate multiple mappings.
• Repository Manager. Use the Repository Manager to assign permissions to users and groups and manage
folders.
• Workflow Manager. Use the Workflow Manager to create, schedule, and run workflows. A workflow is a
set of instructions that describes how and when to run tasks related to extracting, transforming, and
loading data.
• Workflow Monitor. Use the Workflow Monitor to monitor scheduled and running workflows for each
Integration Service.
Install the client application on a Microsoft Windows computer.
PowerCenter Designer
The Designer has the following tools that you use to analyze sources, design target schemas, and build
source-to-target mappings:
• Navigator. Connect to repositories and open folders within the Navigator. You can also copy objects and
create shortcuts within the Navigator.
• Workspace. Open different tools in this window to create and edit repository objects, such as sources,
targets, mapplets, transformations, and mappings.
• Output. View details about tasks you perform, such as saving your work or validating a mapping.
PowerCenter Client 17
The following figure shows the default Designer interface:
1. Navigator
2. Output
3. Workspace
• Informatica stencil. Displays shapes that represent PowerCenter mapping objects. Drag a shape from the
Informatica stencil to the drawing window to add a mapping object to a mapping template.
• Informatica toolbar. Displays buttons for tasks you can perform on a mapping template. Contains the
online help button.
• Drawing window. Work area for the mapping template. Drag shapes from the Informatica stencil to the
drawing window and set up links between the shapes. Set the properties for the mapping objects and the
rules for data movement and transformation.
1. Informatica Stencil
2. Informatica Toolbar
3. Drawing Window
Repository Manager
Use the Repository Manager to administer repositories. You can navigate through multiple folders and
repositories, and complete the following tasks:
• Manage user and group permissions. Assign and revoke folder and global object permissions.
• Perform folder functions. Create, edit, copy, and delete folders. Work you perform in the Designer and
Workflow Manager is stored in folders. If you want to share metadata, you can configure a folder to be
shared.
• View metadata. Analyze sources, targets, mappings, and shortcut dependencies, search by keyword, and
view the properties of repository objects.
The Repository Manager can display the following windows:
• Navigator. Displays all objects that you create in the Repository Manager, the Designer, and the Workflow
Manager. It is organized first by repository and by folder.
• Main. Provides properties of the object selected in the Navigator. The columns in this window change
depending on the object selected in the Navigator.
• Output. Provides the output of tasks executed within the Repository Manager.
PowerCenter Client 19
The following figure shows the Repository Manager interface:
1. Status bar
2. Navigator
3. Output
4. Main
Repository Objects
You create repository objects using the Designer and Workflow Manager client tools. You can view the
following objects in the Navigator window of the Repository Manager:
• Source definitions. Definitions of database objects such as tables, views, synonyms, or files that provide
source data.
• Target definitions. Definitions of database objects or files that contain the target data.
• Mappings. A set of source and target definitions along with transformations containing business logic
that you build into the transformation. These are the instructions that the Integration Service uses to
transform and move data.
• Reusable transformations. Transformations that you use in multiple mappings.
• Mapplets. A set of transformations that you use in multiple mappings.
• Sessions and workflows. Sessions and workflows store information about how and when the Integration
Service moves data. A workflow is a set of instructions that describes how and when to run tasks related
to extracting, transforming, and loading data. A session is a type of task that you can put in a workflow.
Each session corresponds to a single mapping.
Workflow Manager
In the Workflow Manager, you define a set of instructions to execute tasks such as sessions, emails, and
shell commands. This set of instructions is called a workflow.
You then connect tasks with links to specify the order of execution for the tasks you created. Use conditional
links and workflow variables to create branches in the workflow.
When the workflow start time arrives, the Integration Service retrieves the metadata from the repository to
execute the tasks in the workflow. You can monitor the workflow status in the Workflow Monitor.
1. Status bar
2. Navigator
3. Output
4. Main
Workflow Monitor
You can monitor workflows and tasks in the Workflow Monitor. You can view details about a workflow or task
in Gantt Chart view or Task view. You can run, stop, abort, and resume workflows from the Workflow Monitor.
You can view sessions and workflow log events in the Workflow Monitor Log Viewer.
PowerCenter Client 21
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.
• PowerCenter Client. Create and store mapping metadata and connection object information in the
repository with the PowerCenter Designer and Workflow Manager. Retrieve workflow run status
information and session logs with the Workflow Monitor. Create folders, organize and secure metadata,
and assign permissions to users and groups in the Repository Manager.
• Command line programs. Use command line programs to perform repository metadata administration
tasks and service-related functions.
• PowerCenter Integration Service. When you start the PowerCenter Integration Service, the service
connects to the repository to schedule workflows. When you run a workflow, the Integration Service
retrieves workflow task and mapping metadata from the repository. The Integration Service writes
workflow status to the repository.
• Web Services Hub. When you start the Web Services Hub, it connects to the repository to access web-
enabled workflows. The Web Services Hub retrieves workflow task and mapping metadata from the
repository and writes workflow status to the repository.
• SAP BW Service. Listens for RFC requests from SAP NetWeaver BI and initiates workflows to extract from
or load to SAP NetWeaver BI.
You install the Repository Service when you install PowerCenter Services. After you install the PowerCenter
Services, you can use Informatica Administrator to manage the Repository Service.
A workflow is a set of instructions that describes how and when to run tasks related to extracting,
transforming, and loading data. The Integration Service runs workflow tasks. A session is a type of workflow
task. A session is a set of instructions that describes how to move data from sources to targets using a
mapping.
A session extracts data from the mapping sources and stores the data in memory while it applies the
transformation rules that you configure in the mapping. The Integration Service loads the transformed data
into the mapping targets.
Other workflow tasks include commands, decisions, timers, pre-session SQL commands, post-session SQL
commands, and email notification.
The Integration Service can combine data from different platforms and source types. For example, you can
join data from a flat file and an Oracle source. The Integration Service can also load data to different
platforms and target types.
You install the PowerCenter Integration Service when you install PowerCenter Services. After you install the
PowerCenter Services, you can use Informatica Administrator to manage the Integration Service.
• Batch web services. Includes operations to run and monitor the sessions and workflows. Batch web
services also include operations that can access repository metadata. Batch web services install with
PowerCenter.
• Real-time web services. Workflows enabled as web services that can receive requests and generate
responses in SOAP message format. Create real-time web services when you enable PowerCenter
workflows as web services.
Use Informatica Administrator to configure and manage the Web Services Hub. Use the Web Services Hub
Console to view information about the web service and to download WSDL files to create web service clients.
Metadata Manager
Informatica Metadata Manager is a PowerCenter web application to browse, analyze, and manage metadata
from disparate metadata repositories. Metadata Manager helps you understand how information and
processes are derived, how they are related, and how they are used.
Metadata Manager extracts metadata from application, business intelligence, data integration, data
modeling, and relational metadata sources. Metadata Manager uses PowerCenter workflows to extract
metadata from metadata sources and load it into a centralized metadata warehouse called the Metadata
Manager warehouse.
You can use Metadata Manager to browse and search metadata objects, trace data lineage, analyze
metadata usage, and perform data profiling on the metadata in the Metadata Manager warehouse. You can
also create and manage business glossaries.
The Metadata Manager Service in the Informatica domain runs the Metadata Manager application. Create a
Metadata Manager Service in the Informatica Administrator to configure and run the Metadata Manager
application.
• Metadata Manager Service. An application service in an Informatica domain that runs the Metadata
Manager application and manages connections between the Metadata Manager components. You create
and configure the Metadata Manager Service in the Administrator tool.
• Metadata Manager application. Manages the metadata in the Metadata Manager warehouse. Create and
load resources in Metadata Manager. After you use Metadata Manager to load metadata for a resource,
you can use the Metadata Manager application to browse and analyze metadata for the resource. You can
also create custom models and manage security on the metadata in the Metadata Manager warehouse.
• Metadata Manager Agent. Runs within the Metadata Manager application or on a separate machine.
Metadata Exchanges uses the Metadata Manager Agent to extract metadata from metadata sources and
convert it to IME interface-based format.
• Metadata Manager repository. A centralized location in a relational database that stores metadata from
disparate metadata sources. The repository also stores Metadata Manager metadata and the packaged
and custom models for each metadata source type.
Metadata Manager 25
Chapter 2
This tutorial walks you through the process of creating a data warehouse. The tutorial teaches you how to
perform the following tasks:
For more information, case studies, and updates about using Informatica products, refer to Informatica
MySupport Portal at the following location: http://mysupport.informatica.com.
Getting Started
The administrator must install and configure the PowerCenter Services and Client. Verify that the
administrator has completed the following steps:
26
to write down the domain and repository information. Use the tables in “PowerCenter Source and Target” on
page 29 to write down the source and target connectivity information. Contact the administrator for the
necessary information.
Before you begin the lessons, read Chapter 1, “Product Overview” on page 10. The product overview explains
the different components that work together to extract, transform, and load data.
• Create a group with all privileges on a PowerCenter Repository Service. The privileges allow users to
design mappings and run workflows in the PowerCenter Client.
• Create a user account and assign it to the group. The user inherits the privileges of the group.
In this tutorial, you learn about the following applications and tools:
• PowerCenter Repository Manager. Create a folder in the Repository Manager to store the metadata you
create in the lessons.
• PowerCenter Designer. Create the source and the target definitions. Create mappings that contain
transformation instructions for the PowerCenter Integration Service. In this tutorial, you learn about the
following tools in the Designer:
- Source Analyzer. Import or create source definitions.
- Target Designer. Import or create target definitions. You also create tables in the target database based
on the target definitions.
- Mapping Designer. Create mappings that the PowerCenter Integration Service uses to extract,
transform, and load data.
• Workflow Manager. Create and run the workflows and the tasks in the Workflow Manager. A workflow is a
set of instructions that describes how and when to run tasks to extract, transform, and load data.
• Workflow Monitor. Monitor scheduled and running workflows for each Integration Service.
Domain
Use the tables in this section to record the domain connectivity and default administrator information. If
necessary, contact the Informatica administrator for the information.
Domain Name
Gateway Host
Gateway Port
Administrator
The following table can be used to record the information you need to connect to Informatica Administrator
as the default administrator:
Use the default administrator account for the lessons “Creating Users and Groups” on page 31. For all other
lessons, you use the user account that you create in lesson “Creating a User” on page 33 to log in to the
PowerCenter Client.
Note: The default administrator user name is Administrator. If you do not have the password for the default
administrator, ask the Informatica administrator to provide this information or set up a domain administrator
account that you can use. Record the user name and password of the domain administrator.
Repository Name
User Name
Password
Note: Ask the Informatica administrator to provide the name of a PowerCenter repository where you can
create the folder, mappings, and workflows in this tutorial. The user account you use to connect to the
repository is the user account you create in “Creating a User” on page 33.
You must have a relational database available and an ODBC data source to connect to the tables in the
relational database. You can use separate ODBC data sources to connect to the source tables and target
tables.
The following table can be used to record the information you need for the ODBC data sources:
Database Password
The following table can be used to record the information you need to create database connections in the
Workflow Manager:
Database Type
User Name
Password
Connect String
Code Page
Database Name
Server Name
Domain Name
Tutorial Lesson 1
This chapter includes the following topics:
When you install PowerCenter, the installer creates a default administrator user account. You can use the
default administrator account to initially log in to the Informatica domain and create PowerCenter services,
domain objects, and user accounts.
The privileges assigned to a user determine the task or set of tasks a user or group of users can perform in
PowerCenter applications. You can organize users into groups based on the tasks they are allowed to
perform in PowerCenter. Create a group and assign it a set of privileges. Then assign users who require the
same privileges to the group. All users who belong to the group can perform the tasks allowed by the group
privileges.
31
2. In the Address field, enter the following URL for the Informatica Administrator login page:
http://<host>:<port>/administrator
If you configure HTTPS for Informatica Administrator, the URL redirects to the HTTPS enabled site. If the
node is configured for HTTPS with a keystore that uses a self-signed certificate, a warning message
appears. To enter the site, accept the certificate. The Informatica Administrator login page appears.
3. Enter the default administrator user name and password.
Use the Administrator user name and password you recorded in “Administrator” on page 28.
4. If the security domain is configured for LDAP, select Native.
5. Click Login.
6. If the Administration Assistant appears, click Administrator.
Creating a Group
In the following steps, you create a group and assign privileges to the group.
Property Value
Name TUTORIAL
Creating a User
The final step is to create a user account and add the user to the TUTORIAL group. You use this account
throughout the rest of this tutorial.
Folders provide a way to organize and store all metadata in the repository, including mappings, schemas, and
sessions. Folders are designed to be flexible to help you organize the repository logically. Each folder has a
set of properties you can configure to define how users access the folder. For example, you can create a
folder that allows all users to see objects within the folder, but not to edit them.
Folder Permissions
Permissions allow users to perform tasks within a folder. With folder permissions, you can control user
access to the folder and the tasks you permit them to perform.
Folder permissions work closely with privileges. Privileges grant access to specific tasks, while permissions
grant access to specific folders with read, write, and execute access. Folders have the following types of
permissions:
• Read permission. You can view the folder and objects in the folder.
• Write permission. You can create or edit objects in the folder.
• Execute permission. You can run or schedule workflows in the folder.
When you create a folder, you are the owner of the folder. The folder owner has all permissions on the folder
which cannot be changed.
6. In the connection settings section, click Add to add the domain connection information.
The Add Domain dialog box appears.
7. Enter the domain name, gateway host, and gateway port number from “Domain” on page 27.
8. Click OK.
If a message indicates that the domain exists, click Yes to replace the existing domain.
9. In the Connect to Repository dialog box, enter the user and password for the tutorial user.
10. Select the Native security domain.
11. Click Connect.
Creating a Folder
For this tutorial, you create a folder where you will define the data sources and targets, build mappings, and
run workflows in later lessons.
When you run the SQL script, you create the following source tables:
• CUSTOMERS
• DEPARTMENT
• DISTRIBUTORS
• EMPLOYEES
• ITEMS
• ITEMS_IN_PROMOTIONS
• JOBS
• MANUFACTURERS
• ORDERS
• ORDER_ITEMS
• PROMOTIONS
• STORES
The Target Designer generates SQL based on the definitions in the workspace. Generally, you use the Target
Designer to create target tables in the target database. In this lesson, you use this feature to generate the
source tutorial tables from the tutorial SQL scripts that ship with the product. When you run the SQL script,
1. Launch the Designer, double-click the icon for the repository, and log in to the repository.
Use your user profile to open the connection.
2. Double-click the Tutorial_yourname folder.
3. Click Tools > Target Designer to open the Target Designer.
4. Click Targets > Create.
The Create Target Table dialog box apprears.
You must create a dummy target definition to access the Generate/Execute SQL option.
5. Enter any name for the target and select any database type.
6. Click Create.
An empty definition appears in the workspace.
7. Click Done.
8. Click Targets > Generate/Execute SQL.
The Database Object Generation dialog box gives you several options for creating tables.
9. Click the Connect button to connect to the source database.
10. Select the ODBC data source that you created in order to connect to the source database.
Use the information you entered in “PowerCenter Source and Target” on page 29.
11. Enter the database user name and password and click Connect.
You now have an open connection to the source database. When you are connected, the Disconnect
button appears and the ODBC name of the source database appears in the dialog box.
12. Make sure the Output window is open at the bottom of the Designer.
If it is not open, click View > Output.
13. Click the Browse button to find the SQL file.
The SQL file is installed in the following directory:
C:\PowerCenterClientInstallationDir\client\bin
14. Select the SQL file appropriate to the source database platform you are using. Click Open.
The following table describes the database platform name and the corresponding SQL file:
Platform File
Informix smpl_inf.sql
Oracle smpl_ora.sql
DB2 smpl_db2.sql
Teradata smpl_tera.sql
Alternatively, you can enter the path and file name of the SQL file.
15. Click Execute SQL File.
Tutorial Lesson 2
This chapter includes the following topics:
1. In the Designer, click Tools > Source Analyzer to open the Source Analyzer.
2. Double-click the tutorial folder to view its contents.
Every folder contains nodes for sources, targets, schemas, mappings, mapplets, cubes, dimensions,
user-defined functions, and transformations.
3. Click Sources > Import from Database.
4. From the ODBC data source button, select the ODBC data source that you created to access source
tables.
5. Enter the user name and password to connect to this database. Also, enter the name of the source table
owner, if necessary.
Use the database connection information you entered in “PowerCenter Source and Target” on page 29.
In Oracle, the owner name is the same as the user name. Make sure that the owner name is in all caps.
For example, JDOE.
6. Click Connect.
7. In the Select tables list, expand the database owner and the TABLES heading.
A list of all the tables you created by running the SQL script appears in addition to any tables already in
the database.
8. Select the following tables:
• CUSTOMERS
• DEPARTMENT
• DISTRIBUTORS
• EMPLOYEES
39
• ITEMS
• ITEMS_IN_PROMOTIONS
• JOBS
• MANUFACTURERS
• ORDERS
• ORDER_ITEMS
• PROMOTIONS
• STORES
Hold down the CTRL key to select multiple tables. Or, hold down the SHIFT key to select a block of
tables. You may need to scroll down the list of tables to select all tables.
Note: Database objects created in Informix databases have shorter names than those created in other
types of databases. For example, the name of the table ITEMS_IN_PROMOTIONS is shortened to
ITEMS_IN_PROMO.
9. Click OK to import the source definitions into the repository.
The Designer displays the newly imported sources in the workspace. You can click Layout > Scale To Fit
to arrange all definitions in the workplace.
The following image shows the Designer with the newly imported sources in the workspace:
A database definition (DBD) node appears under the Sources node in the tutorial folder. This entry has
the same name as the ODBC data source that you used to import sources. If you double-click the DBD
node, the list of all the imported sources appears.
1. Double-click the title bar of the source definition for the EMPLOYEES table to open the EMPLOYEES
source definition.
The Edit Tables dialog box appears and displays all the properties of this source definition. The Table
tab shows the name of the table, owner name, and the database type. You can add a comment in the
Description section. Business name is empty.
2. Click the Columns tab.
The Columns tab displays the column descriptions for the source table.
Note: The source definition must match the structure of the source table. Therefore, you must not
modify source column definitions after you import them.
The following image shows the Columns tab for EMPLOYEES source definition:
Target definitions define the structure of tables in the target database or the structure of file targets the
Integration Service creates when you run a session. If you add a relational target definition to the repository
that does not exist in a database, you need to create target table. You do this by generating and executing the
necessary SQL code within the Target Designer.
In the following steps, you copy the EMPLOYEES source definition into the Target Designer to create the
target definition. Then, you modify the target definition by deleting and adding columns to create the
definition you want.
1. In the Designer, click Tools > Target Designer to open the Target Designer.
2. Drag the EMPLOYEES source definition from the Navigator to the Target Designer workspace.
The Designer creates a target definition, EMPLOYEES, with the same column definitions as the
EMPLOYEES source definition and the same database type.
Next, modify the target column definitions.
3. Double-click the title bar of the EMPLOYEES target definition to open it.
4. Click Rename and name the target definition T_EMPLOYEES.
Note: If you need to change the database type for the target definition, you can select the correct
database type when you edit the target definition.
5. Click the Columns tab.
The target column definitions are the same as the EMPLOYEES source definition.
1. Add button
2. Delete button
6. Select the following columns and click the Delete button.
• JOB_ID
• ADDRESS1
• ADDRESS2
• CITY
• STATE
• POSTAL_CODE
• HOME_PHONE
• EMAIL
The EMPLOYEE_ID column is a primary key. The primary key cannot accept null values. The Designer
selects Not Null and enables the Not Null option. You now have a column ready to receive data from the
EMPLOYEE_ID column in the EMPLOYEES source table.
7. Click OK to save the changes and close the dialog box.
8. Click Repository > Save.
Note: When you use the Target Designer to generate SQL, you can choose to drop the table in the database
before you create it. To do this, select the Drop Table option. If the target database already contains tables,
make sure it does not contain a table with the same name as the table you plan to create. If the table exists
in the database, you lose the existing table and data.
Tutorial Lesson 3
This chapter includes the following topics:
The next step is to create a mapping to depict the flow of data between sources and targets. For this step,
you create a pass-through mapping. A pass-through mapping inserts all the source rows into the target.
To create and edit mappings, you use the Mapping Designer tool in the Designer. You add transformations to
a mapping that depict how the Integration Service extracts and transforms data before it loads a target.
The following figure shows a mapping between a source and a target with a Source Qualifier transformation:
1. Output port
2. Input/Output port
3. Input port
46
The source qualifier represents the rows that the Integration Service reads from the source when it runs a
session.
If you examine the mapping, you see that data flows from the source definition to the Source Qualifier
transformation to the target definition through a series of input and output ports.
The source provides information, so it contains only output ports, one for each column. Each output port is
connected to a corresponding input port in the Source Qualifier transformation. The Source Qualifier
transformation contains both input and output ports. The target contains input ports.
When you design mappings that contain different types of transformations, you can configure transformation
ports as inputs, outputs, or both. You can rename ports and change the datatypes.
Creating a Mapping
In the following steps, you create a mapping and link columns in the source EMPLOYEES table to a Source
Qualifier transformation.
3. Drag the EMPLOYEES source definition into the Mapping Designer workspace.
The Designer creates a new mapping and prompts you to provide a name.
4. In the Mapping Name dialog box, enter m_PhoneList, and click OK.
The recommended naming convention for mappings is m_Mappingname.
5. Expand the Targets node in the Navigator to open the list of all target definitions.
6. Drag the T_EMPLOYEES target definition into the workspace.
The target definition appears.
7. Click Layout > Arrange.
8. In the Select Targets dialog box, select T_EMPLOYEES target, and click OK.
The Designer rearranges the mapping.
The final step is to connect the Source Qualifier transformation to the target definition.
Connecting Transformations
The port names in the target definition are the same as some of the port names in the Source Qualifier
transformation. When you need to link ports between transformations that have the same name, the Designer
can link them based on name.
In the following steps, you use the autolink option to connect the Source Qualifier transformation to the
target definition.
A workflow is a set of instructions that tells the Integration Service how to execute tasks, such as sessions,
email notifications, and shell commands. You create a workflow for sessions that you want the Integration
Service to run. You can include multiple sessions in a workflow to run sessions in parallel or sequentially. The
Integration Service uses the instructions configured in the workflow to run sessions and other tasks.
The following figure shows a workflow with multiple branches and tasks:
1. Start task
2. Session task
3. Assignment task
4. Command task
You create and maintain tasks and workflows in the Workflow Manager.
In this lesson, you create a session and a workflow to run the session. Before you create a session in the
Workflow Manager, you need to configure database connections in the Workflow Manager.
1. In the Workflow Manager Navigator, double-click the tutorial folder to open it.
2. Click Tools > Task Developer to open the Task Developer.
3. Click Tasks > Create.
4. Select Session as the task type to create.
5. Enter s_PhoneList as the session name and click Create.
The Mappings dialog box appears.
The following image shows the Mappings dialog box:
1. Open button
10. In the Connections settings on the right, click the Open button in the Value column for the
SQ_EMPLOYEES - DB Connection.
The Relational Connection Browser appears.
11. Select TUTORIAL_SOURCE and click OK.
12. Select Targets in the Transformations pane.
13. In the Connections settings, click the Open button in the Value column for the T_EMPLOYEES - DB
Connection.
The Relational Connection Browser appears.
14. Select TUTORIAL_TARGET and click OK.
15. In the Properties settings, change the Target Load Type to Normal.
16. On the Properties tab, select a session sort order associated with the Integration Service code page.
For English data, use the Binary sort order.
Creating a Workflow
You create workflows in the Workflow Designer. When you create a workflow, you can include reusable tasks
that you create in the Task Developer. You can also include non-reusable tasks that you create in the
Workflow Designer.
In the following steps, you create a workflow that runs the session s_PhoneList.
1. Open button
4. Enter wf_PhoneList as the name for the workflow.
The recommended naming convention for workflows is wf_WorkflowName.
5. Click the Open button to choose an Integration Service to run the workflow.
The Integration Service Browser dialog box appears.
6. Select the appropriate Integration Service and click OK.
Note: Integration Services appear if they are running. If no Integration Service appears, contact an
Informatica administrator.
7. Click the Properties tab to edit the workflow properties.
8. Enter wf_PhoneList.log for the workflow log file name.
9. Click the Scheduler tab.
14. Click Repository > Save to save the workflow in the repository.
You can run and monitor the workflow.
You can also open the Workflow Monitor from the Workflow Manager Navigator or from the Windows Start
menu.
1. Navigator
2. Gantt Chart tab
3. Workflow
4. Session
3. Click the Gantt Chart tab at the bottom of the Time window to verify the Workflow Monitor is in the Gantt
Chart view.
4. In the Navigator, expand the node for the workflow.
All tasks in the workflow appear in the Navigator.
The following table shows the data session writes to the target:
4. In the ODBC data source field, select the data source name that you used to create the target table.
5. Enter the database username, owner name and password.
6. Enter the number of rows you want to preview.
7. Click Connect.
The Preview Data dialog box displays the data that you loaded to T_EMPLOYEES.
8. Click Close.
You can preview relational tables, fixed-width and delimited flat files, and XML files with the Preview
Data option.
Tutorial Lesson 4
This chapter includes the following topics:
• Using Transformations, 59
• Creating a Target Definition and Target, 60
• Creating a Mapping with Aggregate Values, 63
• Designer Tips, 70
• Creating a Session and Workflow, 71
Using Transformations
In this lesson, you create a mapping that contains a source, multiple transformations, and a target.
A transformation is a part of a mapping that generates or modifies data. Every mapping includes a Source
Qualifier transformation, representing all data read from a source and temporarily stored by the Integration
Service. In addition, you can add transformations that calculate a sum, look up a value, or generate a unique
ID before the source data reaches the target.
The following table lists some of the transformations that you can create:
Transformation Description
59
Transformation Description
Source Qualifier Represents the rows that the Integration Service reads from a relational or flat file
source when it runs a workflow.
1. Create a target definition to use in a mapping and create a target table based on the new target
definition.
2. Create a mapping using the target definition. Add the following transformations to the mapping:
• Lookup transformation. Finds the name of a manufacturer.
• Aggregator transformation. Calculates the maximum, minimum, and average price of items from
each manufacturer.
• Expression transformation. Calculates the average profit of items, based on the average price.
3. Learn some tips for using the Designer.
4. Create a session and workflow to run the mapping and monitor the workflow in the Workflow Monitor.
After you create the target definition, you create the table in the target database.
Note: You can also manually create a target definition, import the definition for an existing target from a
database, or create a relational target from a transformation in the Designer.
1. Open the Designer, connect to the repository, and open the tutorial folder.
2. Click Tools > Target Designer.
3. Drag the MANUFACTURERS source definition from the Navigator to the Target Designer workspace.
The Designer creates a target definition, MANUFACTURERS, with the same column definitions as the
MANUFACTURERS source definition and the same database type.
Next, you add target column definitions.
4. Double-click the MANUFACTURERS target definition to open it.
The Edit Tables dialog box appears.
11. Click the Indexes tab to add an index to the target table.
If the target database is Oracle, skip to the final step. You cannot add an index to a column that already
has the PRIMARY KEY constraint added to it.
1. Select the table T_ITEM_SUMMARY, and then click Targets > Generate/Execute SQL.
2. In the Database Object Generation dialog box, connect to the target database.
3. Click Generate from Selected tables, and select the Create Table, Primary Key, and Create Index
options.
Leave the other options unchanged.
4. Click Generate and execute.
The Designer notifies you that the file MKTABLES.SQL already exists.
5. Click OK to override the contents of the file and create the target table.
The Designer runs the SQL script to create the T_ITEM_SUMMARY table.
6. Click Close.
• Finds the most expensive and least expensive item in the inventory for each manufacturer. Use an
Aggregator transformation to perform these calculations.
• Calculates the average price and profitability of all items from a given manufacturer. Use an Aggregator
and an Expression transformation to perform these calculations.
You need to configure the mapping to perform both simple and aggregate calculations. For example, use the
MIN and MAX functions to find the most and least expensive items from each manufacturer.
Tip: You can select each port and click the Up and Down buttons to position the output ports after the
input ports in the list.
11. Click Apply to save the changes.
1. Click the Open button in the Expression column of the OUT_MAX_PRICE port to open the Expression
Editor.
The Formula section of the Expression Editor displays the expression as you develop it. Use other
sections of this dialog box to select the input ports to provide values for an expression, enter literals and
operators, and select functions to use in the expression.
3. Double-click the Aggregate heading in the Functions tab of the dialog box.
A list of all aggregate functions now appears.
4. Double-click the Max function on the list.
The MAX function appears in the window where you enter the expression. To perform the calculation,
you need to add a reference to an input port that provides data for the expression.
5. Move the cursor between the parentheses next to MAX.
6. Click the Ports tab.
This section of the Expression Editor displays all the ports from all transformations appearing in the
mapping.
7. Double-click the PRICE port appearing beneath AGG_PriceCalculations.
A reference to this port appears within the expression. The final step is to validate the expression.
The following image shows the Ports tab in the Expression Editor:
8. Click Validate.
The Designer displays a message indicating that the expression parsed successfully.
9. Click OK to close the message box from the parser, and then click OK again to close the Expression
Editor.
1. Enter and validate the expressions for the other output ports.
The following table describes the output ports and expressions:
Port Expression
OUT_MIN_PRICE MIN(PRICE)
OUT_AVG_PRICE AVG(PRICE)
Both MIN and AVG appear in the list of Aggregate functions, along with MAX.
The following image shows the ports configured for the Aggregator transformation:
To add this information to the target, you create an Expression transformation that takes the average price of
items from a manufacturer, performs the calculation, and then passes the result along to the target. As you
develop transformations, you connect transformations using the output of one transformation as an input for
others.
Note: Right-click on the source definition and source qualifier and select Iconize to iconize them.
3. Open the Expression transformation.
4. Add an input port, IN_AVG_PRICE, using the Decimal datatype with precision of 19 and scale of 2.
5. Add an output port, OUT_AVG_PROFIT, using the Decimal datatype with precision of 19 and scale of 2.
Clear the Input port.
Note: OUT_AVG_PROFIT is an output port, not an input/output port. You cannot enter expressions in
input/output ports.
6. Enter the following expression for OUT_AVG_PROFIT:
IN_AVG_PRICE * 0.2
7. To validate the expression, click Validate.
8. To reflect the latest changes from the expression condition in the test expression section in the right
pane, click Refresh.
10. Close the Expression Editor and then close the EXP_AvgProfit transformation.
11. Connect OUT_AVG_PRICE from the Aggregator to IN_AVG_PRICE input port.
The following mapping shows a link from the Aggregator transformation port OUT_AVG_PRICE to the
input port IN_AVG_PRICE:
12. Connect the OUT_AVG_PROFIT port in the Expression Transformation to the AVG_PROFIT port in the
T_ITEM_SUMMARY target definition.
13. Click Repository > Save.
MANUFACTURER_ID = IN_MANUFACTURER_ID
Note: If the datatypes, including precision and scale, of these two columns do not match, the Designer
displays a message and marks the mapping invalid.
9. View the Properties tab.
Do not change settings in this section of the dialog box.
10. Click OK.
You now have a Lookup transformation that reads values from the MANUFACTURERS table and
performs lookups using values passed through the IN_MANUFACTURER_ID input port. The final step is
to connect this Lookup transformation to the rest of the mapping.
11. Click Layout > Link Columns.
12. Connect the MANUFACTURER_ID output port from the Aggregator transformation to the
IN_MANUFACTURER_ID input port in the Lookup transformation.
13. Connect the MANUFACTURER_ID port in the LKP_MANUFACTURERS Lookup transformation object to
the MANUFACTURER_ID port in the T_ITEM_SUMMARY target defintion object.
14. Click Repository > Save.
1. Drag the output ports to the corresponding input ports in the target.
The following table describes the output ports that connect to the corresponding input ports:
Designer Tips
This section includes tips for using the Designer. You learn how to complete the following tasks:
• m_PhoneList. A pass-through mapping that reads employee names and phone numbers.
• m_ItemSummary. A more complex mapping that performs simple and aggregate calculations and
lookups.
You have a reusable session based on m_PhoneList. Next, you create a session for m_ItemSummary in the
Workflow Manager. You create a workflow that runs both sessions.
By default, when you link both sessions directly to the Start task, the Integration Service runs both
sessions at the same time when you run the workflow. If you want the Integration Service to run the
sessions one after the other, connect the Start task to one session, and connect that session to the other
session.
13. ClickRepository > Save to save the workflow in the repository.
You can now run and monitor the workflow.
1. Right-click the Start task in the workspace and select Start Workflow.
Tip: You can also right-click the workflow in the Navigator and select Start Workflow.
The Workflow Monitor opens and connects to the repository and opens the tutorial folder.
If the Workflow Monitor does not show the current workflow tasks, right-click the tutorial folder and
select Get Previous Runs.
2. Click the Gantt Chart tab at the bottom of the Time window to verify the Workflow Monitor is in Gantt
Chart view.
Note: You can also click the Task View tab at the bottom of the Time window to view the Workflow
Monitor in Task view. You can switch back and forth between views at any time.
3. In the Navigator, expand the node for the workflow.
All tasks in the workflow appear in the Navigator.
You can preview the results from the workflow by following the directions on “Previewing Data” on page
58.
The following table shows the results from running the session s_ItemSummary:
Log Files
When you created the workflow, the Workflow Manager assigned default workflow and session log names
and locations on the Properties tab. The Integration Service writes the log files to the locations specified in
the session properties.
Tutorial Lesson 5
This chapter includes the following topics:
• Stored Procedure. Call a stored procedure and capture its return values.
• Filter. Filter data that you do not need, such as discontinued items in the ITEMS table.
• Sequence Generator. Generate unique IDs before inserting rows into the target.
You create a mapping that outputs data to a fact table and its dimension tables.
The following figure shows the mapping you create in this lesson:
75
Creating Targets
Before you create a mapping, you need to create the target tables for the mapping. These instructions explain
how to create the following target tables:
1. Open the Designer, connect to the repository, and open the tutorial folder.
2. Click Tools > Target Designer.
To clear the workspace, right-click the workspace, and select Clear All.
3. Click Targets > Create.
4. In the Create Target Table dialog box, enter F_PROMO_ITEMS as the name of the target table, select the
database type, and click Create.
5. Repeat step 4 to create the other tables needed for this schema: D_ITEMS, D_PROMOTIONS, and
D_MANUFACTURERS. When you have created all these tables, click Done.
6. Open each target definition, and add the columns to the appropriate table.
The following table describes the columns for the table D_ITEMS:
ITEM_NAME Varchar 72 - -
PROMOTION_NAME Varchar 72 - -
The following table describes the columns for the table D_MANUFACTURERS:
MANUFACTURER_NAME Varchar 72 - -
NUMBER_ORDERED Integer - - -
7. Click View > Navigator to close the Navigator to allow extra space in the workspace.
8. Click Repository > Save.
The mapping contains a Filter transformation that limits rows queried from the ITEMS table to those items
that have not been discontinued.
1. Connect the ports ITEM_ID, ITEM_NAME, and PRICE to the corresponding columns in D_ITEMS.
In the new mapping, you add a Sequence Generator transformation to generate IDs for the fact table
F_PROMO_ITEMS. Every time the Integration Service inserts a new row into the target table, it generates a
unique ID for PROMO_ITEM_ID.
The following table shows the syntax for the stored procedure:
Database Syntax
-- Declare handler
DECLARE EXIT HANDLER FOR SQLEXCEPTION
SET SQLCODE_OUT = SQLCODE;
BEGIN
SELECT COUNT(*)
INTO: SP_RESULT
FROM ORDER_ITEMS
WHERE ITEM_ID =: ARG_ITEM_ID;
END;
In the mapping, add a Stored Procedure transformation to call this procedure. The Stored Procedure
transformation returns the number of orders containing an item to an output port.
8. Click OK.
9. Connect the ITEM_ID column from the Source Qualifier transformation to the ITEM_ID column in the
Stored Procedure transformation.
10. Connect the RETURN_VALUE column from the Stored Procedure transformation to the
NUMBER_ORDERED column in the target table F_PROMO_ITEMS.
11. Click Repository > Save.
1. Connect the columns from the Source Qualifier transformation to the targets.
The following table describes the Source Qualifier transformation columns, target table, and the column
name:
The following image shows the mapping you created in this lesson:
Creating a Workflow
In this part of the lesson, you complete the following steps:
1. Create a workflow.
2. Add a non-reusable session to the workflow.
3. Define a link condition before the Session task.
Creating a Workflow 83
Creating the Workflow
Open the Workflow Manager and connect to the repository.
If the link condition evaluates to True, the Integration Service runs the next task in the workflow. The
Integration Service does not run the next task in the workflow if the link condition evaluates to False. You can
also use pre-defined or user-defined workflow variables in the link condition.
You can view results of link evaluation during workflow runs in the workflow log.
In the following steps, you create a link condition before the Session task and use the built-in workflow
variable WORKFLOWSTARTTIME. You define the link condition so the Integration Service runs the session if
the workflow start time is before the date you specify.
1. Double-click the link from the Start task to the Session task.
The following image shows the Expression Editor that appears:
Creating a Workflow 85
Add a comment by typing the following text:
// Only run the session if the workflow starts before the date specified above.
The following image shows the contents of the PreDefined tab:
4. In the Properties window, click Session Statistics to view the workflow results.
If the Properties window is not open, click View > Properties View.
The results from running the s_PromoItems session are:
D_ITEMS Output Rows [13]
D_MANUFACTURERS Output Rows [11]
D_PROMOTIONS Output Rows [3]
F_PROMO_ITEMS Output Rows [36]
Creating a Workflow 87
Chapter 8
Tutorial Lesson 6
This chapter includes the following topics:
In this lesson, you have an XML schema file that contains data on the salary of employees in different
departments, and you have relational data that contains information about the different departments. You
want to find out the total salary for employees in two departments, and you want to write the data to a
separate XML target for each department.
In the XML schema file, employees can have three types of wages, which appear in the XML schema file as
three occurrences of salary. You pivot the occurrences of employee salaries into three columns:
BASESALARY, COMMISSION, and BONUS. Then you calculate the total salary in an Expression
transformation.
You use a Router transformation to test for the department ID. You use another Router transformation to get
the department name from the relational source. You send the salary data for the employees in the
Engineering department to one XML target and the salary data for the employees in the Sales department to
another XML target.
88
The following figure shows the mapping you create in this lesson:
1. Open the Designer, connect to the repository, and open the tutorial folder.
2. Click Tools > Source Analyzer.
3. Click Sources > Import XML Definition.
4. Click Advanced Options.
5. Select Override All Infinite Lengths with value and enter 50.
6. Configure the options and click OK to save the changes.
The following table describes the options and values:
Option Value
Ignore fixed elements and attributes whose content is a fixed value specified by a schema Yes
Generate names for the XML columns/Select Use the element or attribute name for an XML column Yes
7. In the Import XML Definition dialog box, navigate to the following directory:
c:\PowerCenterClientInstallationDir\client\bin
8. Select the Employees.xsd file. Click Open.
9. Verify that the name for the XML definition is Employees and click Next.
10. Select Do not generate XML views.
In this lesson, you use the XML Editor to pivot the three occurrences of SALARY into three columns in an XML
group. You do this because the multiple-occurring element SALARY represents three types of salary: a base
salary, a commission, and a bonus that appear in the XML file as three instances of the SALARY element.
1. Bonus
2. Commission
3. Base salary
To work with these three instances separately, you pivot them to create three separate columns in the XML
definition.
You create a custom XML view with columns from several groups. You then pivot the occurrence of SALARY
to create the columns, BASESALARY, COMMISSION, and BONUS.
1. Navigator
2. XPath Navigator
3. XML View
4. XML Workspace
1. Double-click the XML definition or right-click the XML definition and select Edit XML Definition to open
the XML Editor.
2. Click XMLViews > Create XML View to create an XML view.
3. From the EMPLOYEE group, select DEPTID and right-click it.
4. Choose Show XPath Navigator.
5. Expand the EMPLOYMENT group so that the SALARY column appears.
6. From the XPath Navigator, select the following elements and attributes and drag them into the view:
• DEPTID
• EMPID
• LASTNAME
9. Drag the SALARY column into the XML view two more times to create three pivoted columns.
Note: Although the columns appear in the column window, the view shows one instance of SALARY.
The wizard adds three columns in the column view and names them SALARY, SALARY0, and SALARY1.
The following image shows three columns SALARY, SALARY0, and SALARY1 in the columns view:
SALARY0 COMMISSION - 2
SALARY1 BONUS - 3
Note: To update the pivot occurrence, click the Xpath of the column you want to edit. The Specify query
predicate for Xpath window appears. Select the column name and change the pivot occurrence.
11. Click File > Apply Changes to save the changes to the view.
12. Click File > Exit to close the XML Editor.
The following image shows the source definition that appears in the Source Analyzer, with all of the
listed EMPLOYEE attributes and elements:
Note: The pivoted SALARY columns do not display the names you entered in the Columns window.
However, when you drag the ports to another transformation, the edited column names appear in the
transformation.
13. Click Repository > Save to save the changes to the XML definition.
• Each department has a separate target and the structure for each target is the same.
• Each target contains salary and department information for employees in the Sales or Engineering
department.
Because the structure for the target data is the same for the Engineering and Sales groups, use two instances
of the target definition in the mapping. In the following steps, you import the Sales_Salary schema file and
create a custom view based on the schema.
17. Click Repository > Save to save the XML target definition.
In the following steps, you add two Router transformations to the mapping, one for each department. In each
Router transformation you create two groups. One group returns True for rows where the DeptID column
contains ‘SLS’. The other group returns True where the DeptID column contains ‘ENG’. All rows that do not
meet either condition go into the default group.
The Designer adds a default group to the list of groups. All rows that do not meet the condition you
specify in the group filter condition are routed to the default group. If you do not connect the default
group, the Integration Service drops the rows.
5. Click OK to close the transformation.
6. In the workspace, expand the RTR_Salary Router transformation to see all groups and ports.
7. Click Repository > Save.
Next, you create another Router transformation to filter the Sales and Engineering department data from the
DEPARTMENT relational source.
1. Connect the ports from RTR_Salary groups to the ports in the XML target definitions.
The following table describes the ports in RTR_Salary groups and the ports in the XML target definitions:
2. Connect the ports from RTR_DeptName groups to the ports in the XML target definitions.
The following table describes the ports in RTR_DeptName and the ports in XML target definitions:
Note: Verify that the Integration Service that runs the workflow can access the source XML file. Copy the
Employees.xml file from the Tutorial folder to the $PMSourceFileDir directory for the Integration Service and
rename it data.xml. Usually, this is the SrcFiles directory in the Integration Service installation directory.
Naming Conventions
This appendix includes the following topic:
Naming Convention
The following table lists the recommended naming conventions for transformations:
Aggregator AGG_TransformationName
Custom CT_TransformationName
Expression EXP_TransformationName
Filter FIL_TransformationName
HTTP HTTP_TransformationName
Java JTX_TransformationName
Joiner JNR_TransformationName
Lookup LKP_TransformationName
Normalizer NRM_TransformationName
104
Transformation Naming Convention
Rank RNK_TransformationName
Router RTR_TransformationName
Sorter SRT_TransformationName
SQL SQL_TransformationName
Union UN_TransformationName
The following table lists recommended naming conventions for other objects:
Targets t_TargetName
Mappings m_MappingName
Mapplets mplt_MappletName
Sessions s_SessionName
Worklets wl_WorkletName
Glossary
active database
The database to which transformation logic is pushed during pushdown optimization.
active source
An active source is an active transformation the Integration Service uses to generate rows.
application service
A service that runs on one or more nodes in the Informatica domain. You create and manage application
services in Informatica Administrator or through the infacmd command program. Application services
include services that can have multiple instances in the domain and system services that can have a single
instance in the domain. Configure each application service based on your environment requirements.
A service that runs on the node in the Informatica domain. You manage application services in Informatica
Administrator or through the infacmd command program. Configure each application service based on your
environment requirements.
associated service
An application service that you associate with another application service. For example, you associate a
Repository Service with an Integration Service.
An application service that is associated with another application service. For example, the Model Repository
Service is associated with the Data Integration Service.
attachment view
View created in a web service source or target definition for a WSDL that contains a mime attachment. The
attachment view has an n:1 relationship with the envelope view.
available resource
Any PowerCenter resource that is configured to be available to a node.
backup node
Any node that is configured to run a service process, but is not configured as a primary node.
blocking
The suspension of the data flow into an input group of a multiple input group transformation.
blurring
A masking rule that limits the range of numeric output values to a fixed or percent variance from the value of
the source data. The Data Masking transformation returns numeric data that is close to the value of the
source data.
bounds
A masking rule that limits the range of numeric output to a range of values. The Data Masking transformation
returns numeric data between the minimum and maximum bounds.
buffer block
A block of memory that the Integration Services uses to move rows of data from the source to the target. The
number of rows in a block depends on the size of the row data, the configured buffer block size, and the
configured buffer memory size.
buffer memory
Buffer memory allocated to a session. The Integration Service uses buffer memory to move data from
sources to targets. The Integration Service divides buffer memory into buffer blocks.
cache partitioning
A caching process that the Integration Service uses to create a separate cache for each partition. Each
partition works with only the rows needed by that partition. The Integration Service can partition caches for
the Aggregator, Joiner, Lookup, and Rank transformations.
child dependency
A dependent relationship between two objects in which the child object is used by the parent object.
child object
A dependent object used by another object, the parent object.
cold start
A start mode that restarts a task or workflow without recovery.
commit source
An active source that generates commits for a target in a source-based commit session.
compatible version
An earlier version of a client application or a local repository that you can use to access the latest version
repository.
composite object
An object that contains a parent object and its child objects. For example, a mapping parent object contains
child objects including sources, targets, and transformations.
concurrent workflow
A workflow configured to run multiple instances at the same time. When the Integration Service runs a
concurrent workflow, you can view the instance in the Workflow Monitor by the workflow name, instance
name, or run ID.
coupled group
An input group and output group that share ports in a transformation.
CPU profile
An index that ranks the computing throughput of each CPU and bus architecture in a grid. In adaptive
dispatch mode, nodes with higher CPU profiles get precedence for dispatch.
custom role
A role that you can create, edit, and delete.
Custom transformation
A transformation that you bind to a procedure developed outside of the Designer interface to extend
PowerCenter functionality. You can create Custom transformations with multiple input and output groups.
108 Glossary
data masking
A process that creates realistic test data from production source data. The format of the original columns
and relationships between the rows are preserved in the masked data.
default permissions
The permissions that each user and group receives when added to the user list of a folder or global object.
Default permissions are controlled by the permissions of the default group, “Other.”
denormalized view
An XML view that contains more than one multiple-occurring element.
dependent object
An object used by another object. A dependent object is a child object.
dependent services
A service that depends on another service to run processes. For example, the Integration Service cannot run
workflows if the Repository Service is not running.
deployment group
A global object that contains references to other objects from multiple folders across the repository. You can
copy the objects referenced in a deployment group to multiple target folders in another repository. When you
copy objects in a deployment group, the target repository creates new versions of the objects. You can create
a static or dynamic deployment group.
deterministic output
Source or transformation output that does not change between session runs when the input data is
consistent between runs.
digested password
Password security option for protected web services. The password is the value generated from hashing the
password concatenated with a nonce value and a timestamp. The password must be hashed with the SHA-1
hash function and encoded to Base64.
dispatch mode
A mode used by the Load Balancer to dispatch tasks to nodes in a grid.
domain
A domain is the fundamental administrative unit for Informatica nodes and services.
A domain is the fundamental administrative unit for the Informatica node and services.
dynamic partitioning
The ability to scale the number of partitions without manually adding partitions in the session properties.
Based on the session configuration, the Integration Service determines the number of partitions when it runs
the session.
element view
A view created in a web service source or target definition for a multiple occurring element in the input or
output message. The element view has an n:1 relationship with the envelope view.
envelope view
A main view in a web service source or target definition that contains a primary key and the columns for the
input or output message.
exclusive mode
An operating mode for the Repository Service. When you run the Repository Service in exclusive mode, you
allow only one user to access the repository to perform administrative tasks that require a single user to
access the repository and update the configuration.
failover
The migration of a service or task to another node when the node running or service process become
unavailable.
110 Glossary
fault view
A view created in a web service target definition if a fault message is defined for the operation. The fault view
has an n:1 relationship with the envelope view.
flush latency
A session condition that determines how often the Integration Service flushes data from the source.
gateway node
Receives service requests from clients and routes them to the appropriate service and node. A gateway node
can run application services. In the Administrator tool, you can configure any node to serve as a gateway for
a PowerCenter domain. A domain can have multiple gateway nodes.
global object
An object that exists at repository level and contains properties you can apply to multiple objects in the
repository. Object queries, deployment groups, labels, and connection objects are global objects.
grid object
An alias assigned to a group of nodes to run sessions and workflows.
group
A set of ports that defines a row of incoming or outgoing data. A group is analogous to a table in a relational
source or target definition.
hashed password
Password security option for protected web services. The password must be hashed with the MD5 or SHA-1
hash function and encoded to Base64.
high availability
A PowerCenter option that eliminates a single point of failure in a domain and provides minimal service
interruption in the event of failure.
idle database
The database that does not process transformation logic during pushdown optimization.
impacted object
An object that has been marked as impacted by the PowerCenter Client. The PowerCenter Client marks
objects as impacted when a child object changes in such a way that the parent object may not be able to run.
incompatible object
An object that a compatible client application cannot access in the latest version repository.
Informatica domain
A collection of nodes and services that define the Informatica platform. You group nodes and services in a
domain based on administration ownership.
Informatica Services
The name of the service or daemon that runs on each node. When you start Informatica Services on a node,
you start the Service Manager on that node.
input group
A set of ports that defines a row of incoming data.
Integration Service
An application service that runs data integration workflows and loads metadata into the Metadata Manager
warehouse.
invalid object
An object that has been marked as invalid by the PowerCenter Client. When you validate or save a repository
object, the PowerCenter Client verifies that the data can flow from all sources in a target load order group to
the targets without the Integration Service blocking all sources.
key masking
A type of data masking that produces repeatable results for the same source data and masking rules. The
Data Masking transformation requires a seed value for the port when you configure it for key masking.
label
A user-defined object that you can associate with any versioned object or group of versioned objects in the
repository.
112 Glossary
latency
A period of time from when source data changes on a source to when a session writes the data to a target.
linked domain
A domain that you link to when you need to access the repository metadata in that domain.
Load Balancer
A component of the Integration Service that dispatches Session, Command, and predefined Event-Wait tasks
across nodes in a grid.
local domain
A PowerCenter domain that you create when you install PowerCenter. This is the domain you access when
you log in to the Administrator tool.
Log Agent
A Service Manager function that provides accumulated log events from session and workflows. You can view
session and workflow logs in the Workflow Monitor. The Log Agent runs on the nodes where the Integration
Service process runs.
Log Manager
A Service Manager function that provides accumulated log events from each service in the domain. You can
view logs in the Administrator tool. The Log Manager runs on the master gateway node.
mapping
A set of source and target definitions linked by transformation objects that define the rules for data
transformation.
mapplet
A mapplet is a set of transformations that you build in the Mapplet Designer. Create a mapplet when you
want to reuse the logic in multiple mappings.
metadata explosion
The expansion of referenced or multiple-occurring elements in an XML definition. The relationship model you
choose for an XML definition determines if metadata is limited or exploded to multiple areas within the
definition. Limited data explosion reduces data redundancy.
mixed-version domain
A PowerCenter domain that supports multiple versions of application services.
native authentication
One of the authentication methods used to authenticate users logging in to PowerCenter applications. In
native authentication, you create and manage users and groups in the Administrator tool. The Service
Manager stores group and user account information and performs authentication in the domain configuration
database.
The authentication method used to authenticate users logging in to PowerCenter Express applications. The
Service Manager stores group and user account information and performs authentication in the domain
configuration database.
node
A logical representation of a machine or a blade. Each node runs a Service Manager that performs domain
operations on that node.
114 Glossary
node diagnostics
Diagnostic information for a node that you generate in the Administrator tool and upload to Configuration
Support Manager. You can use this information to identify issues within your Informatica environment.
nonce
A random value that can be used only once. In PowerCenter web services, a nonce value is used to generate
a digested password. If the protected web service uses a digested password, the nonce value must be
included in the security header of the SOAP message request.
normalized view
An XML view that contains no more than one multiple-occurring element. Normalized XML views reduce data
redundancy.
normal mode
An operating mode for an Integration Service or Repository Service. Run the Integration Service in normal
mode during daily Integration Service operations. Run the Repository Service in normal mode to allow
multiple users to access the repository and update content.
object query
A user-defined object you use to search for versioned objects that meet specific conditions.
one-way mapping
A mapping that uses a web service client for the source. The Integration Service loads data to a target, often
triggered by a real-time event through a web service request.
open transaction
A set of rows that are not bound by commit or rollback rows.
operating mode
The mode for an Integration Service or Repository Service. An Integration Service runs in normal or safe
mode. A Repository Service runs in normal or exclusive mode.
output group
A set of ports that defines a row of outgoing data.
parent object
An object that uses a dependent object, the child object.
permission
The level of access a user has to an object. Even if a user has the privilege to perform certain actions, the
user may also require permission to perform the action on a particular object.
pipeline branch
A segment of a pipeline between any two mapping objects.
pipeline stage
The section of a pipeline executed between any two partition points.
pmdtm process
The Data Transformation Manager process.
pmserver process
The Integration Service process.
port dependency
The relationship between an output or input/output port and one or more input or input/output ports.
predefined resource
An available built-in resource. This can include the operating system or any resource installed by the
PowerCenter installation, such as a plug-in or a connection object.
primary node
A node that is configured as the default node to run a service process. By default, the Service Manager starts
the service process on the primary node and uses a backup node if the primary node fails.
privilege
An action that a user can perform in PowerCenter applications. You assign privileges to users and groups for
the domain and application services.
privilege group
An organization of privileges that defines common user actions.
116 Glossary
pushdown compatible connections
Connections with identical property values that allow the Integration Service to identify tables within the
same database management system. The required properties depend on the database management system
associated with the connection object.
pushdown group
A group of transformations containing transformation logic that is pushed to the database during a session
configured for pushdown optimization. The Integration Service creates one or more SQL statements based
on the number of partitions in the pipeline.
pushdown optimization
A session option that allows you to push transformation logic to the source or target database.
random masking
A type of masking that produces random, non-repeatable results.
real-time data
Data that originates from a real-time source. Real-time data includes messages and messages queues, web
services messages, and change data from a PowerExchange change data capture source.
real-time processing
On-demand processing of data from operational data sources, databases, and data warehouses. Real-time
processing reads, processes, and writes data to targets continuously.
real-time session
A session in which the Integration Service generates a real-time flush based on the flush latency
configuration and all transformations propagate the flush to the targets.
real-time source
The origin of real-time data. Real-time sources include JMS, WebSphere MQ, TIBCO, webMethods, MSMQ,
SAP, and web services.
recovery
The automatic or manual completion of tasks after a service is interrupted. Automatic recovery is available
for Integration Service and Repository Service tasks. You can also manually recover Integration Service
workflows.
reference file
A Microsoft Excel or flat file that contains reference data. Use the Reference Table Manager to import data
from reference files into reference tables.
repeatable data
A source or transformation output that is in the same order between session runs when the order of the input
data is consistent.
repository client
Any PowerCenter component that connects to the repository. This includes the PowerCenter Client,
Integration Service, pmcmd, pmrep, and MX SDK.
repository domain
A group of linked repositories consisting of one global repository and one or more local repositories.
Repository Service
An application service that manages the PowerCenter repository. It retrieves, inserts, and updates metadata
in the repository database tables.
request-response mapping
A mapping that uses a web service source and target. When you create a request-response mapping, you use
source and target definitions imported from the same WSDL file.
required resource
A PowerCenter resource that is required to run a task. A task fails if it cannot find any node where the
required resource is available.
resilience
The ability for PowerCenter services to tolerate transient network failures until either the resilience timeout
expires or the external system failure is fixed.
resilience timeout
The amount of time a client attempts to connect or reconnect to a service. A limit on resilience timeout can
override the resilience timeout.
118 Glossary
resource provision thresholds
Computing thresholds defined for a node that determine whether the Load Balancer can dispatch tasks to the
node. The Load Balancer checks different thresholds depending on the dispatch mode.
role
A collection of privileges that you assign to a user or group. You assign roles to users and groups for the
domain and application services.
safe mode
An operating mode for the Integration Service. When you run the Integration Service in safe mode, only users
with privilege to administer the Integration Service can run and get information about sessions and
workflows. A subset of the high availability features are available in safe mode.
SAP BW Service
An application service that listens for RFC requests from SAP NetWeaver BI and initiates workflows to extract
from or load to SAP NetWeaver BI.
security domain
A collection of user accounts and groups in a PowerCenter domain. Native authentication uses the Native
security domain which contains the users and groups created and managed in the Administrator tool. LDAP
authentication uses LDAP security domains which contain users and groups imported from the LDAP
directory service. You can define multiple security domains for LDAP authentication.
seed
A random number required by key masking to generate non-colliding repeatable masked output.
sequential merge
A merge type that allows the Integration Service to create one merge file for all target partitions from the
individual output files. The integration Service writes the merge file to the final target.
service level
A domain property that establishes priority among tasks that are waiting to be dispatched. When multiple
tasks are waiting in the dispatch queue, the Load Balancer checks the service level of the associated
workflow so that it dispatches high priority tasks before low priority tasks.
Service Manager
A service that manages all domain operations. It runs on all nodes in the domain to support the application
services and the domain. When you start Informatica Services, you start the Service Manager. If the Service
Manager is not running, the node is not available.
service process
A run-time representation of a service running on a node.
service version
The version of an application service running in the PowerCenter domain. In a mixed-version domain you can
create application services of multiple service versions.
service workflow
A workflow that contains exactly one web service input message source and at most one type of web service
output message target. Configure service properties in the service workflow.
session
A task in a workflow that tells the Integration Service how to move data from sources to targets. A session
corresponds to one mapping.
session recovery
The process that the Integration Service uses to complete failed sessions. When the Integration Service runs
a recovery session that writes to a relational target in normal mode, it resumes writing to the target database
table at the point at which the previous session failed. For other target types, the Integration Service
performs the entire writer run again.
single-version domains
A PowerCenter domain that supports one version of application services.
source pipeline
A source qualifier and all of the transformations and target instances that receive data from that source
qualifier.
state of operation
Workflow and session information the Integration Service stores in a shared location for recovery. The state
of operation includes task status, workflow variable values, and processing checkpoints.
system-defined role
A role that you cannot edit or delete. The Administrator role is a system-defined role.
120 Glossary
target connection group
A group of targets that the Integration Service uses to determine commits and loading. When the Integration
Service performs a database transaction such as a commit, it performs the transaction for all targets in a
target connection group.
task release
A process that the Workflow Monitor uses to remove older tasks from memory so you can monitor an
Integration Service in online mode without exceeding memory limits.
team-based development
The collaboration of team members on a development project. Collaboration includes functionality such as
versioning through checking out and checking in repository objects.
terminating condition
A condition that determines when the Integration Service stops reading messages from a real-time source
and ends the session.
transaction
A set of rows bound by commit or rollback rows.
transaction boundary
A row, such as a commit or rollback row, that defines the rows in a transaction. Transaction boundaries
originate from transaction control points.
transaction control
The ability to define commit and rollback points through an expression in the Transaction Control
transformation and session properties.
transformation
A repository object in a mapping that generates, modifies, or passes data. Each transformation performs a
different function.
type view
A view created in a web service source or target definition for a complex type element in the input or output
message. The type view has an n:1 relationship with the envelope view.
user credential
Web service security option that requires a client application to log in to the PowerCenter repository and get
a session ID. The Web Services Hub authenticates the client requests based on the session ID. This is the
security option used for batch web services.
user-defined commit
A commit strategy that the Integration Service uses to commit and roll back transactions defined in a
Transaction Control transformation or a Custom transformation configured to generate commits.
user-defined property
A user-defined property is metadata that you define, such as PowerCenter metadata extensions. You can
create user-defined properties in business intelligence, data modeling, or OLAP tools, such as IBM DB2 Cube
Views or PowerCenter, and exchange the metadata between tools using the Metadata Export Wizard and
Metadata Import Wizard.
user-defined resource
A PowerCenter resource that you define, such as a file directory or a shared library you want to make
available to services.
version
An incremental change of an object saved in the repository. The repository uses version numbers to
differentiate versions.
122 Glossary
versioned object
An object for which you can create multiple versions in a repository. The repository must be enabled for
version control.
view root
The element in an XML view that is a parent to all the other elements in the view.
view row
The column in an XML view that triggers the Integration Service to generate a row of data for the view in a
session.
worker node
Any node not configured to serve as a gateway. A worker node can run application services but cannot serve
as a master gateway node.
workflow
A set of instructions that tells the Integration Service how to run tasks such as sessions, email notifications,
and shell commands.
workflow instance
The representation of a workflow. You can choose to run one or more workflow instances associated with a
concurrent workflow. When you run a concurrent workflow, you can run one instance multiple times
concurrently, or you can run multiple instances concurrently.
workflow run ID
A number that identifies a workflow instance that has run.
Workflow Wizard
A wizard that creates a workflow with a Start task and sequential Session tasks based on the mappings you
choose.
worklet
A worklet is an object representing a set of tasks created to reuse a set of workflow logic in multiple
workflows.
XML view
A portion of any arbitrary hierarchy in an XML definition. An XML view contains columns that are references
to the elements and attributes in the hierarchy. In a web service definition, the XML view represents the
elements and attributes defined in the input and output messages.
124 Glossary
Index
A PowerCenter repository
overview 15
Administrator tool
Domain page 15
Security page 16
Administrator Tool
S
overview 15 Security tab
overview 16
sessions
D creating 50, 71
source
Domain page viewing definitions 41
overview 15 sources
supported 12
I T
Informatica domains
overview 13 targets
Informix supported 13
database platform 36 transformations
Integration Service definition 59
overview 23
Introduction
overview 10 W
Web Services Hub
M overview 23
Workflow Manager
Metadata Manager overview 20
overview 24 Workflow Monitor
overview 20, 21
workflows
P running 86
PowerCenter Client
overview 17
125