Informatica Data Services Getting Started Guide

Informatica Data Services (Version 9.5.
1)
Getting Started Guide
Informatica Data Services Getting Started Guide
Version 9.5.1
December 2012
Copyright (c) 1998-2012 Informatica Data Services. All rights reserved.
This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. 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 Corporation. This Software may be protected by U.S. and/or international
Patents and other Patents Pending.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in
DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013
(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.
The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in
writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,
PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On
Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica
Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All 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
is International Business Machines Corporation. All rights reserved. Copyright
yWorks GmbH. All rights reserved. Copyright
Lucent Technologies. All rights reserved. Copyright (c) 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.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License,
Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations under the License.
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 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-2007, 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.
The product includes software copyright
2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http://dojotoolkit.org/license.
This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this
software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/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.
1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http://
www.pcre.org/license.txt.
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.
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://www.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://developer.apple.com/library/mac/#samplecode/HelpHook/Listings/HelpHook_java.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; and http://benalman.com/about/license/.
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 MIT License (http://www.opensource.org/licenses/mit-
license.php) and the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0).
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 Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;
6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110, 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;
7676516; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending.
DISCLAIMER: Informatica Corporation 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 Corporation 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.
Part Number: DS-GSG-951-001
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Chapter 1: Getting Started Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Informatica Data Services Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Informatica Developer Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Informatica Developer Welcome Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Cheat Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
The Tutorial Story. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Tutorial Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2: Lesson 1. Setting Up Informatica Developer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Setting Up Informatica Developer Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Task 1. Start Informatica Developer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Task 2. Add a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Task 3. Add a Model Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Task 4. Create a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Task 5. Create a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Task 6. Select a Default Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Setting Up Informatica Developer Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 3: Lesson 2. Importing Physical Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Importing Physical Data Objects Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Task 1. Import the Boston_Customers Flat File Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Task 2. Import the LA_Customers Flat File Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Importing Physical Data Objects Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 4: Lesson 3. Creating a Logical View of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Creating a Logical View of Data Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Task 1. Import a Logical Data Object Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Task 2. Create a Logical Data Object Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table of Contents i
Step 1. Create the Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Step 2. Add Sources to the Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Step 3. Add an Expression Transformation to the Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Step 4. Add a Union Transformation to the Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Task 3. Run the Logical Data Object Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Creating a Logical View of Data Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 5: Lesson 4. Creating a Virtual View of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Creating a Virtual View of Data Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Task 1. Create an SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Task 2. Run an SQL Query to Preview Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Task 3. Create an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Task 4. Deploy the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Creating a Virtual View of Data Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Chapter 6: Lesson 5. Creating a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Creating a Web Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Task 1. Create a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Task 2. View and Validate the Operation Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Task 3. Test the Operation Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Task 4. Create an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Task 5. Deploy the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Creating a Web Service Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 7: Lesson 6. Exporting a Mapping to PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . 26
Exporting a Mapping to PowerCenter Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Task 1. Export a Mapping to PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Exporting a Mapping to PowerCenter Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Appendix A: Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Informatica Developer Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Appendix B: Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
ii Table of Contents
Preface
The Data Services Getting Started Guide is written for data services developers. It provides a tutorial to help first-
time users learn how to use Informatica Developer for data services tasks. This guide assumes that you have an
understanding of flat file concepts, relational database concepts, web services concepts, and the database
engines in your environment.
Informatica Resources
Informatica Customer Portal
As an Informatica customer, you can access the Informatica Customer Portal site at
http://mysupport.informatica.com. The site contains product information, user group information, newsletters,
access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library,
the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Product
Documentation, and access to the Informatica user community.
Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have
questions, comments, or ideas about this documentation, contact the Informatica Documentation team through
email at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us
know if we can contact you regarding your comments.
The Documentation team updates documentation as needed. To get the latest documentation for your product,
navigate to Product Documentation from http://mysupport.informatica.com.
Informatica Web Site
You can access the Informatica corporate web site at http://www.informatica.com. The site contains information
about Informatica, its background, upcoming events, and sales offices. You will also find product and partner
information. The services area of the site includes important information about technical support, training and
education, and implementation services.
Informatica How-To Library
As an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com.
The How-To Library is a collection of resources to help you learn more about Informatica products and features. It
includes articles and interactive demonstrations that provide solutions to common problems, compare features and
behaviors, and guide you through performing specific real-world tasks.
iii
Informatica Knowledge Base
As an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com.
Use the Knowledge Base to search for documented solutions to known technical issues about Informatica
products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If
you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base
team through email at KB_Feedback@informatica.com.
Informatica Multimedia Knowledge Base
As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at
http://mysupport.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia files
that help you learn about common concepts and guide you through performing specific tasks. If you have
questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base
team through email at KB_Feedback@informatica.com.
Informatica Global Customer Support
You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires
a user name and password. You can request a user name and password at http://mysupport.informatica.com.
Use the following telephone numbers to contact Informatica Global Customer Support:
North America / South America Europe / Middle East / Africa Asia / Australia
Toll Free
Brazil: 0800 891 0202
Mexico: 001 888 209 8853
North America: +1 877 463 2435
Toll Free
France: 0805 804632
Germany: 0800 5891281
Italy: 800 915 985
Netherlands: 0800 2300001
Portugal: 800 208 360
Spain: 900 813 166
Switzerland: 0800 463 200
United Kingdom: 0800 023 4632

Standard Rate
Belgium: +31 30 6022 797
France: +33 1 4138 9226
Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511445
Toll Free
Australia: 1 800 151 830
New Zealand: 09 9 128 901

Standard Rate
India: +91 80 4112 5738
iv Preface
C H A P T E R 1
Getting Started Overview
This chapter includes the following topics:
Informatica Data Services Overview, 1
Informatica Developer Overview, 2
The Tutorial Story, 4
Tutorial Prerequisites, 4
Informatica Data Services Overview
Informatica Data Services provides the ability to create a unified model of data and provides access to data across
the enterprise. A data service is a collection of reusable operations that you can run against sources to access,
transform, and deliver data.
Use Informatica Developer (the Developer tool) to accomplish the following data services tasks:
Define logical views of data. A logical view of data is a representation of data that resides in an enterprise. A
logical view of data includes a logical data model, logical data objects, and logical data object mappings.
Define logical data object models. A logical data object model describes the structure and use of data in an
enterprise. The model contains logical data objects and defines relationships between them. A logical data
object describes a logical entity in an enterprise. It has attributes, keys, and it describes relationships between
attributes. You can define a logical data object model to create a unified model of data in an enterprise.
Map logical models to data sources or targets. Create a mapping that links objects in a logical model to data
sources or targets. You can link data from multiple, disparate sources to have a single view of the data. You
can also load data that conforms to a model to multiple, disparate targets.
Create virtual views of data. A virtual view is a type of table that uses SQL logic to convert the format of retired
data. You can create virtual views to store retired data in a different format from data on the production
database.
Create an SQL data service. An SQL data service is a virtual database that end users can query. It contains
virtual schemas and the virtual tables or stored procedures that define the database structure. End users can
run SQL queries against the virtual tables without affecting the source data.
Create a web service. You can create and deploy a web service so that web service clients can access data
integration functionality through a web service interface.
Export mappings to PowerCenter. You can export mappings to PowerCenter to reuse the metadata for physical
data integration.
Create and deploy mappings that end users can query. You can create mappings and deploy them so that end
users can query the mapping results.
1
Profile data. If you use the profiling option, profile data to reveal the content and structure of your data.
Profiling is a key step in any data project, as it can identify strengths and weaknesses in your data and help
you define your project plan.
Informatica Developer Overview
The Developer tool is an application client that developers use to design and implement data quality and data
services solutions.
The following figure shows the Developer tool:
The Developer tool workbench displays the following views by default:
Object Explorer view
Displays projects, folders, and the objects within the projects and folders. Appears in the top left area of the
Developer tool.
Connection Explorer view
Displays connections to relational databases. Appears in the top right area of the Developer tool.
Outline view
Displays objects that are dependent on an object selected in the Object Explorer view. Appears in the
bottom left area of the Developer tool.
Properties view
Displays the properties for an object that is in focus in the editor. Appears in the bottom area of the Developer
tool.
You can hide views and move views to another location in the Developer tool workbench. Click Window > Show
View to select the views you want to display.
The Developer tool workbench also displays the following views:
2 Chapter 1: Getting Started Overview
Cheat Sheets view
Displays the cheat sheet that you open. To open a cheatsheet, click Help > Cheat Sheets and select a
cheatsheet.
Help view
Displays context-sensitive online help.
Progress view
Displays the progress of operations in the Developer tool, such as a mapping run.
Search view
Displays the search results. You can also launch the search options dialog box.
Tags view
Displays tags that define an object in the Model repository based on business usage.
Validation Log view
Displays object validation errors.
Informatica Developer Welcome Page
The first time you open the Developer tool, the Welcome page appears. Use the Welcome page to learn more
about the Developer tool, set up the Developer tool, and to start working in the Developer tool.
The Welcome page displays the following options:
Overview. Click the Overview button to get an overview of data quality and data services solutions.
First Steps. Click the First Steps button to learn more about setting up the Developer tool and accessing
Informatica Data Quality and Informatica Data Services lessons.
Tutorials. Click the Tutorials button to see tutorial lessons for data quality and data services solutions.
Web Resources. Click the Web Resources button for a link to mysupport.informatica.com. You can access the
Informatica How-To Library. The Informatica How-To Library contains articles about Informatica Data Quality,
Informatica Data Services, and other Informatica products.
Workbench. Click the Workbench button to start working in the Developer tool.
Cheat Sheets
The Developer tool includes cheat sheets as part of the online help. A cheat sheet is a step-by-step guide that
helps you complete one or more tasks in the Developer tool.
After you complete a cheat sheet, you complete the tasks and see the results. For example, after you complete a
cheat sheet to import and preview a relational data object, you have imported a relational database table and
previewed the data in the Developer tool.
To access cheat sheets, click Help > Cheat Sheets.
Informatica Developer Overview 3
The Tutorial Story
HypoStores Corporation is a national retail organization with headquarters in Boston and stores in several states.
It integrates operational data from stores nationwide with the data store at headquarters on regular basis. It
recently opened a store in Los Angeles.
The headquarters includes a central ICC team of administrators, developers, and architects responsible for
providing a common data services layer for all composite and BI applications. The BI applications include a CRM
system that contains the master customer data files used for billing and marketing.
HypoStores Corporation must perform the following tasks to integrate data from the Los Angeles operation with
data at the Boston headquarters:
Set up a single view of customer data from both locations.
Create a virtual database to enable access to the customer data from both offices. Or, create a web service to
enable access to the customer data from both offices.
Tutorial Prerequisites
Before you can begin the tutorial lessons, the Informatica domain must be running and connected to a Model
Repository Service and a Data Integration Service.
The installer includes tutorial files that you will use to complete the lessons. You can find all the files in both the
client and server installations:
You can find the tutorial files in the following location in the Developer tool installation path:
<Informatica Installation Directory>\clients\DeveloperClient\Tutorials
You can find the tutorial files in the following location in the services installation path:
<Informatica Installation Directory>\server\Tutorials
You need the following files for the tutorial lessons:
All_Customers.csv
Boston_Customers.csv
Customer_Order.xsd
LA_customers.csv
4 Chapter 1: Getting Started Overview
C H A P T E R 2
Lesson 1. Setting Up Informatica
Developer
Setting Up Informatica Developer Overview, 5
Task 1. Start Informatica Developer, 6
Task 2. Add a Domain, 6
Task 3. Add a Model Repository, 7
Task 4. Create a Project, 7
Task 5. Create a Folder, 7
Task 6. Select a Default Data Integration Service, 8
Setting Up Informatica Developer Summary, 8
Setting Up Informatica Developer Overview
In this lesson, you start and set up the Developer tool. To set up the Developer tool, you add a domain. You add a
Model repository, and you create a project and folder to store your work. You also select a default Data Integration
Service.
The Informatica domain is a collection of nodes and services that define the Informatica environment. Services in
the domain include the Model Repository Service and the Data Integration Service.
The Model Repository Service manages the Model repository. The Model repository is a relational database that
stores the metadata for projects that you create in the Developer tool. A project stores objects that you create in
the Developer tool. A project can also contain folders that store related objects, such as objects that are part of the
same business requirement.
The Data Integration Service performs data integration tasks in the Developer tool.
Objectives
In this lesson, you complete the following tasks:
Start the Developer tool and go to the Developer tool workbench.
Add a domain in the Developer tool.
Add a Model repository so that you can create a project.
Create a project to store the objects that you create in the Developer tool.
5
Create a folder in the project that can store related objects.
Select a default Data Integration Service to perform data integration tasks.
Prerequisites
Before you start this lesson, verify the following prerequisites:
You have installed the Developer tool.
You have a domain name, host name, and port number to connect to a domain. You can get this information
from a domain administrator.
A domain administrator has configured a Model Repository Service.
You have a user name and password to access the Model Repository Service. You can get this information
from a domain administrator.
A domain administrator has configured a Data Integration Service.
The Data Integration Service is running.
Timing
Set aside 5 to 10 minutes to complete the tasks in this lesson.
Task 1. Start Informatica Developer
Start the Developer tool to begin the tutorial.
1. Start the Developer tool.
The Welcome page of the Developer tool appears.
2. Click the Workbench button.
The Developer tool workbench appears.
Task 2. Add a Domain
In this task, you add a domain in the Developer tool to access a Model repository.
1. Click Window > Preferences.
The Preferences dialog box appears.
2. Select Informatica > Domains.
3. Click Add.
The New Domain dialog box appears.
4. Enter the domain name, host name, and port number.
5. Click Finish.
6. Click OK.
6 Chapter 2: Lesson 1. Setting Up Informatica Developer
Task 3. Add a Model Repository
In this task, you add the Model repository that you want to use to store projects and folders.
1. Click File > Connect to Repository.
The Connect to Repository dialog box appears.
2. Click Browse to select a Model Repository Service.
3. Click OK.
4. Click Next.
5. Enter your user name and password.
6. Select a namespace.
7. Click Finish.
The Model repository appears in the Object Explorer view.
Task 4. Create a Project
In this task, you create a project to store objects that you create in the Developer tool. You can create one project
for all tutorials in this guide.
1. In the Object Explorer view, select a Model Repository Service.
2. Click File > New > Project.
The New Project dialog box appears.
3. Enter your name prefixed by "Tutorial_" as the name of the project.
4. Click Finish.
The project appears under the Model Repository Service in the Object Explorer view.
Task 5. Create a Folder
In this task, you create a folder to store related objects. You can create one folder for all tutorials in this guide.
1. In the Object Explorer view, select the project that you want to add the folder to.
2. Click File > New > Folder.
3. Enter a name for the folder.
4. Click Finish.
The Developer tool adds the folder under the project in the Object Explorer view. Expand the project to see
the folder.
Task 3. Add a Model Repository 7
Task 6. Select a Default Data Integration Service
In this task, you select a default Data Integration Service to run mappings and preview data.
1. Click Window > Preferences.
The Preferences dialog box appears.
2. Select Informatica > Data Integration Services.
3. Expand the domain.
4. Select a Data Integration Service.
5. Click Set as Default.
6. Click OK.
Setting Up Informatica Developer Summary
In this lesson, you learned that the Informatica domain services include the Model Repository Service and Data
Integration Service. The Model Repository Service manages the Model repository. A Model repository contains
projects and folders. The Data Integration Service performs data integration tasks.
You started the Developer tool and set up the Developer tool. You added a domain to the Developer tool, added a
Model repository, and created a project and folder. You also selected a default Data Integration Service.
Now, you can use the Developer tool to complete other lessons in this tutorial.
8 Chapter 2: Lesson 1. Setting Up Informatica Developer
C H A P T E R 3
Lesson 2. Importing Physical Data
Objects
Importing Physical Data Objects Overview, 9
Task 1. Import the Boston_Customers Flat File Data Object, 10
Task 2. Import the LA_Customers Flat File Data Object, 10
Importing Physical Data Objects Summary, 11
Importing Physical Data Objects Overview
A physical data object is a representation of data based on a flat file or relational database table. You can import a
flat file or relational database table as a physical data object to use as a source or target in a mapping.
Story
HypoStores Corporation stores customer data from the Los Angeles office and Boston office in flat files.
HypoStores wants to work with this customer data in the Developer tool.
Objectives
In this lesson, you import flat files as physical data objects. You also set the source file directory so that the Data
Integration Service can read the source data from the correct directory.
Prerequisites
Before you start this lesson, verify the following prerequisite:
You have completed lesson 1 in this tutorial.
Timing
9
Task 1. Import the Boston_Customers Flat File Data
Object
In this task, you import a physical data object from a file that contains customer data from the Boston office.
1. In the Object Explorer view, select the tutorial project.
2. Click File > New > Data Object.
The New dialog box appears.
3. Select Physical Data Objects > Flat File Data Object and click Next.
The New Flat File Data Object dialog box appears.
4. Select Create from an existing flat file.
5. Click Browse and navigate to Boston_Customers.csv in the following directory: <Informatica Installation
Directory>\clients\DeveloperClient\Tutorials
6. Click Open.
The wizard names the data object "Boston_Customers."
7. Click Next.
8. Verify that the code page is MS Windows Latin 1 (ANSI), superset of Latin 1.
9. Verify that the format is delimited.
10. Click Next.
11. Verify that the delimiter is set to comma.
12. Select Import column names from first line.
13. Click Finish.
The Boston_Customers physical data object appears under Physical Data Objects in the tutorial project.
14. Click the Read view and select the Output transformation.
15. Click the Runtime tab on the Properties view.
16. Set Source file directory to the following directory on the Data Integration Service machine: <Informatica
Installation Directory>\server\Tutorials
17. Click the Data Viewer view.
18. Click Run.
The Data Integration Service reads the data from the Boston_Customers file and shows the results in the
Output window.
19. Click File > Save.
Task 2. Import the LA_Customers Flat File Data Object
In this task, you import a physical data object from a flat file that contains customer data from the Los Angeles
office.
2. Click File > New > Data Object.
10 Chapter 3: Lesson 2. Importing Physical Data Objects
3. Select Physical Data Objects > Flat File Data Object and click Next.
The New Flat File Data Object dialog box appears.
4. Select Create from an existing flat file.
5. Click Browse and navigate to LA_Customers.csv in the following directory: <Informatica Installation
Directory>\clients\DeveloperClient\Tutorials
6. Click Open.
The wizard names the data object "LA_Customers."
7. Click Next.
8. Verify that the code page is MS Windows Latin 1 (ANSI), superset of Latin 1.
9. Verify that the format is delimited.
10. Click Next.
11. Verify that the delimiter is set to comma.
12. Select Import column names from first line.
13. Click Finish.
The LA_Customers physical data object opens in the editor.
14. Click the Read view and select the Output transformation.
15. Click the Runtime tab on the Properties view.
16. Set the source file directory to the following directory on the Data Integration Service machine: <Informatica
Installation Directory>\server\Tutorials
18. Click Run.
The Data Integration Service reads the data from the LA_Customers file and shows the results in the Output
window.
Importing Physical Data Objects Summary
In this lesson, you learned that physical data objects are representations of data based on a flat file or a relational
database table.
You imported physical data objects from flat files. You also set the source file directory so that the Data Integration
Service can read the source data from the correct directory.
Importing Physical Data Objects Summary 11
C H A P T E R 4
Lesson 3. Creating a Logical View
of Data
Creating a Logical View of Data Overview, 12
Task 1. Import a Logical Data Object Model, 13
Task 2. Create a Logical Data Object Mapping, 14
Task 3. Run the Logical Data Object Mapping, 16
Creating a Logical View of Data Summary, 17
Creating a Logical View of Data Overview
A logical view of data is a data model in an enterprise. It provides a single view of physical data in an enterprise,
even if the data comes from various sources, such as different files or databases.
To develop a single view of data, you need to define a logical data object model. A logical data object model
describes the structure and use of data in an enterprise. A logical data object model also describes how different
types of data are related to each other. For example, a logical data object model can describe how customer data
and order data are formatted and structured and how they are related.
A logical data object model contains logical data objects. A logical data object defines a data entity in an
enterprise, such as a customer or an order. It describes the attributes of the entity, such as name and address in a
customer data object. It also describes key relationships of those attributes to attributes in other logical data
objects. For example, it can define a relationship between the order ID in an order logical data object and the
customer ID of a customer logical data object. Therefore, the model states that in an enterprise, each order ID
must be associated with a customer ID.
A logical data object mapping contains a logical data object as the mapping input or output. You can use a logical
data object read mapping to read data from multiple sources and apply the output to a logical data object. The
mapping can also contain transformation logic to transform the data.
12
The following figure shows a process to create a logical view of data:
Story
HypoStores Corporation wants a single view of customer data from the Los Angeles and Boston offices. The
enterprise data model requires that customer names use the same format regardless of the data source. The
customer data from the Los Angeles office uses a different format for customer names than the data from the
Boston office. The data from the Los Angeles office uses the correct format, so you need to reformat the customer
data from the Boston office to conform to the data model.
Objectives
1. Import a logical data object model that contains the Customer and Orders logical data objects.
2. Create a logical data object read mapping with the Customer logical data object as the mapping output. The
mapping transforms the Boston customer data and defines a single view of the data from the Los Angeles and
Boston offices.
3. Run the mapping to view the combined customer data.
Prerequisites
Complete lessons 1 and 2 in this tutorial.
Timing
Set aside 20 minutes to complete the tasks in this lesson.
Task 1. Import a Logical Data Object Model
In this task, you import a logical data object model that contains the Customer and Order logical data objects.
Task 1. Import a Logical Data Object Model 13
2. Click File > New > Logical Data Object Model.
3. Select Logical Data Object Model from Data Model and click Next.
The New Logical Data Object Model dialog box appears.
4. Select W3C XML Schema 1.0 (XSD) as the model type.
5. Enter Customer_Order as the logical data object model name.
6. Click Next.
7.
Click the Open button ( ) in the Value column to select an XSD file.
8. Navigate to Customer_Order.xsd in the following directory: <Informatica Installation Directory>\clients
\DeveloperClient\Tutorials
9. Click Open.
10. Select All for the Collapse Level property.
11. Clear the Generate IDs property
12. Click Next.
13. Click the Move all items button to add the Customer and Order logical data objects to the logical data object
model.
14. Click Finish.
The Customer and Order logical data objects appear in the editor.
Task 2. Create a Logical Data Object Mapping
In this task, you create a logical data object mapping that combines the first and last names of the customer data
for the Boston office. The mapping also combines the customer data for the Los Angeles and Boston offices.
To create the logical data object mapping, complete the following steps:
1. Create a mapping with the Customer data object as the mapping output.
2. Add the LA_Customers and Boston_Customers physical data objects as sources.
3. Add an Expression transformation to concatenate the FirstName and LastName columns of the Boston
customer data. Preview the transformation output.
4. Add a Union transformation to combine the Los Angeles and Boston customer data.
Step 1. Create the Mapping
Create a logical data object mapping with the Customer data object as the mapping output.
1. In the Object Explorer view, expand Logical Data Object Models in the tutorial project.
2. Select the Customer_Order logical data object model.
3. Click File > New > Other.
4. Select Informatica > Logical Data Objects > Logical Data Object Mapping and click Next.
5. Click Browse and select the Customer logical data object under the Customer_Order logical data object
model in the tutorial folder.
6. Select Read as the mapping type.
14 Chapter 4: Lesson 3. Creating a Logical View of Data
7. Click Finish.
The editor displays a mapping with the Customer logical data object as the mapping output.
Step 2. Add Sources to the Mapping
Add the LA_Customers and Boston_Customers data objects to the mapping as sources.
1. In the Object Explorer view, expand Physical Data Objects in the tutorial folder.
2. Select LA_Customers and drag it to the editor that contains the logical data object mapping.
3. Select Read and click OK.
LA_Customers appears in the editor as a source.
4. Select Boston_Customers and drag it to the editor.
5. Select Read and click OK.
Boston_Customers appears in the editor as a source.
Step 3. Add an Expression Transformation to the Mapping
Add an Expression transformation to concatenate the FirstName and LastName columns of the Boston customer
data. Preview the transformation output.
1. In the Transformation palette, select the Expression transformation and drag it to the editor.
An Expression transformation appears in the editor.
Tip: To find the Expression transformation, click the Customize the Transformation Palette button at the top
of the palette. Select Show Icons and Labels. Expand the palette from the right edge to see the labels.
2. Select all columns in the Boston_Customers source and drag them to the Expression transformation.
Tip: Hold down the Shift key to select multiple columns. You might need to scroll down the list of columns to
select all of them.
The columns appear as ports in the Expression transformation.
3. Select the Expression transformation and click the Ports tab in the Properties view.
4. Select Output Only and click the New (Insert) button.
A port appears.
5. Enter FullName as the port name and change the precision to 20.
6.
Click the Open button ( ) on the right of the Expression column to open the Expression editor.
7. Delete the text in the Expression window.
8. Enter the following expression: CONCAT( CONCAT( FIRSTNAME, ' ' ), LASTNAME )
9. Click Validate to validate the expression. Click OK.
10. Click OK to exit the Expression editor.
11. Select the Expression transformation in the editor.
12. Select the FullName port.
13. Click the Move Up button at the top of the transformation until you have moved the FullName port below the
Customer Tier port.
Task 2. Create a Logical Data Object Mapping 15
16. Click Run.
The Data Integration Service processes the data from the Boston_Customers source and the Expression
transformation. The Developer tool shows the results in the Output window. The results show that the Data
Integration Service has concatenated the FirstName and LastName columns from the source.
Step 4. Add a Union Transformation to the Mapping
Add a Union transformation to combine the source data.
1. In the Transformation palette, select the Union transformation and drag it to the editor.
A Union transformation appears in the editor.
2. Select all columns in the LA_Customers source and drag them to the Union transformation.
Tip: Hold down the Shift key to select multiple columns. You might need to scroll down the list of columns to
select all of them.
The columns appear as ports in an input group and an output group of the Union transformation.
3. Select the Union transformation and click the Groups tab in the Properties view.
4. Click the New (Insert) button to add a group.
5. Name the group Boston_Input.
The Union transformation includes the Boston_Input group with ports of the same name as the input group
and output group.
6. In the editor, scroll through the ports of the Union transformation until you see the Boston_Input group.
7. In the Expression transformation, select all of the ports except LastName and FirstName.
8. Scroll to the top of the transformation. Then, drag the ports to the Boston_Input group of the Union
transformation.
The Developer tool links the ports in the Expression transformation to the ports in the Boston_Input group of
the Union transformation.
9. Select the ports in the output group of the Union transformation, except Customer_Region, and drag them to
the Customer transformation.
The Developer tool links the ports in the Union transformation to the ports in the Customer transformation.
10. Right-click an empty area in the editor and click Validate.
The Developer tool displays a message stating that it found no validation errors.
11. Click OK.
Tip: Right-click an empty area in the editor and click Arrange All to arrange mapping objects.
Task 3. Run the Logical Data Object Mapping
In this task, you run the logical data object mapping to create a single view of customer data from the Los Angeles
and Boston offices.
u Right-click an empty area in the editor and click Run Data Viewer.
The Data Viewer view appears.
16 Chapter 4: Lesson 3. Creating a Logical View of Data
After the Data Integration Service runs the mapping, the Developer tool shows the data in the Output section of
the Data Viewer view. The output shows that you merged the FirstName and LastName columns of the
Boston_Customers source. It also shows that you combined the data from the LA_Customers source and
Boston_Customers source.
Creating a Logical View of Data Summary
In this lesson, you learned that a logical data object model describes the structure and use of data in an
enterprise. The model contains logical data objects that define a data entity in an enterprise, such as a customer
or an order. You also learned that you can create a mapping that reads data from multiple sources, transforms it,
and applies the output to a logical data object.
You created a logical data object model to provide a single view of customer data.
Use the logical data object mapping that you created in this lesson in the following lessons:
Chapter 5, Lesson 4. Creating a Virtual View of Data on page 18
Chapter 6, Lesson 5. Creating a Web Service on page 22
Chapter 7, Lesson 6. Exporting a Mapping to PowerCenter on page 26
Creating a Logical View of Data Summary 17
C H A P T E R 5
Lesson 4. Creating a Virtual View
of Data
Creating a Virtual View of Data Overview, 18
Task 1. Create an SQL Data Service, 19
Task 2. Run an SQL Query to Preview Data, 20
Task 3. Create an Application, 20
Task 4. Deploy the Application, 21
Creating a Virtual View of Data Summary, 21
Creating a Virtual View of Data Overview
A virtual view of data is a virtual database that you can query as if it were a physical database.
To create a virtual database, you define an SQL data service in the Developer tool. The SQL data service must
contain at least one virtual schema that defines the virtual database structure. The virtual schema must contain at
least one virtual table. A virtual table can have a virtual table mapping that links a virtual table to source data and
defines the data flow between the sources and the virtual table.
After you create an SQL data service, you create an application and add the SQL data service to the application.
An application is an object that contains one or more SQL data services and mappings. You can deploy the
application to a Data Integration Service to make the virtual database available for end users to query.
18
The following figure shows a process for creating a virtual view of data:
Story
HypoStores Corporation wants to create a report about customers for the Los Angeles and Boston offices.
However, the Los Angeles customer data is not in the central data warehouse. A developer in the IT department
has combined the data for the Los Angeles and Boston customer offices in a logical data object model. The
developer can make this data available to query in a virtual database. A business analyst can create a report
based on the virtual data.
Objectives
1. Create an SQL data service to define a virtual database that contains customer data.
2. Preview the virtual data.
3. Create an application that contains the SQL data service.
4. Deploy the application to a Data Integration Service.
Prerequisites
Complete lessons 1, 2, and 3 in this tutorial.
Timing
Task 1. Create an SQL Data Service
In this task, you create an SQL data service to create a virtual database that end users can query.
2. Click File > New > Data Service.
3. Select SQL Data Service and click Next.
The New SQL Data Service dialog box appears.
Task 1. Create an SQL Data Service 19
4. Enter HypoStores_Customers for the SQL data service name and click Next.
5. To create a virtual table, click the New button.
The Developer tool adds a virtual table to the list of virtual tables.
6. Enter Customers for the virtual table name.
7.
Click the Open button ( ) in the Data Object column.
The Select a Data Object dialog box appears.
8. In the tutorial folder, expand the Customer_Order logical data object model, and select the Customer logical
data object.
9. Click OK.
The Developer tool adds Customer as the virtual table source. It also specifies Logical Data Object as the
source type and the tutorial project as the location.
10. Enter Customer_Schema in the Virtual Schemas column and press Enter.
11. Click Finish.
The Developer tool creates the HypoStores_Customers SQL data service. The SQL data service contains the
Customers table and the Customers mapping.
Task 2. Run an SQL Query to Preview Data
In this task, you run an SQL query against the Customers virtual table to preview the data.
1. In the Object Explorer view, open the HypoStores_Customers SQL data service.
2. Select the Data Viewer view.
3. In the Input section, enter the following SQL statement: SELECT * from customers
4. Click Run.
The Output section displays the combined customer data from the Los Angeles and Boston offices.
Task 3. Create an Application
In this task, you create an application that contains the SQL data service.
2. Click File > New > Application.
The New Application dialog box appears.
3. Enter HypoStores_Customers_App for the application name and click Next.
4. Click Add.
The Add Objects dialog box appears.
5. Select HypoStores_Customers and click OK.
6. Click Finish.
The Developer tool creates an application that contains the HypoStores_Customers data service.
20 Chapter 5: Lesson 4. Creating a Virtual View of Data
Task 4. Deploy the Application
In this task, you deploy the application so end users can query virtual tables in the SQL data service through a
JDBC or ODBC client tool.
1. In the Object Explorer view, expand Applications in the tutorial project.
2. Right-click the HypoStores_Customers_App application and click Deploy.
The Deploy dialog box appears.
3. Click Browse next to the Domain option.
4. Select a domain and click OK.
5. Select the Data Integration Service that you want to deploy the application to.
6. Click Finish.
When the deployment succeeds, the Deploy Completed dialog box appears.
7. Click OK.
Creating a Virtual View of Data Summary
In this lesson, you learned that you can define an SQL data service that contains a virtual database. A virtual
database includes at least one schema and virtual table. You learned that you can associate the virtual table with
a data object. You also learned that you can make the virtual database available so that end users can query the
virtual data.
You created a virtual view of data and ran an SQL query to preview the virtual data. You also created an
application to contain the virtual data and deployed the application to a Data Integration Service.
Task 4. Deploy the Application 21
C H A P T E R 6
Lesson 5. Creating a Web Service
Creating a Web Service Overview, 22
Task 1. Create a Web Service, 23
Task 2. View and Validate the Operation Mapping, 24
Task 3. Test the Operation Mapping, 24
Task 4. Create an Application, 24
Task 5. Deploy the Application, 25
Creating a Web Service Summary, 25
Creating a Web Service Overview
A web service provides access to data integration functionality through a web service interface.
You create web services in the Developer tool. A web service can have one or more operations. Each operation
defines an action that the web service client can perform when the web service client connects to a web service. In
the Developer tool, each operation corresponds to an operation mapping.
After you create a web service, you create an application and add the web service to the application. An
application is an object that contains one or more web services, SQL data services, and mappings. Deploy the
application to a Data Integration Service to make the web service available for web service clients to connect to.
Story
Hypostores customer service representatives want to access customer data from the Los Angeles and Boston
offices over a network. The customer service representatives want to view customer information based on the
customer ID. A developer in the IT department has a logical data object for customer data. The developer has
combined the data for the Los Angeles and Boston customer offices in a logical data object mapping.
The developer can create a web service that accepts a customer ID, looks up customer data in the logical data
object, and returns the customer details. Then, the developer can deploy an application containing the web service
to a Data Integration Service. The administrator can provide customer service with the WSDL URL so that
customer service can connect to the web service.
Objectives
1. Create a web service that provides access to customer details.
2. View and validate the operation mapping.
22
3. Test the operation mapping.
4. Create an application that contains the web service.
5. Deploy the application to a Data Integration Service.
Prerequisites
Complete lessons 1, 2, and 3 in this tutorial.
Timing
Set aside 15 to 20 minutes to complete this lesson.
Task 1. Create a Web Service
In this task, you create a web service with an operation that returns customer details based on a customer ID. You
use a logical data object to create an operation.
2. Click File > New > Data Service.
3. Select Web Service and click Next.
The New Web Service dialog box appears.
4. Enter HypoStores_CustDetails for the web service name and click Next.
5. Click the arrow next to the New button and click Operation > Create from Reusable Object.
The Select Reusable Object dialog box appears.
6. Expand the tutorial project, browse to Logical Data Object Model > Data Object Model, and then select
Customer.
7. Enter getCustomerByID for the operation name.
The Developer tool uses the name you provide for the operation to define the names for the operation input
and the operation output.
8. Click getCustomerByID_Input to select fields from the logical data object.
The Developer tool uses the fields you select from the logical data object to define elements in the operation
input.
9. On the Operation Input tab, clear the customer field to clear all the selected fields. Then, select
CUSTOMER_ID.
You select CUSTOMER_ID because you want the operation input to include an element for the customer ID.
You want to return all the customer details available for the customer ID in the operation output. Therefore,
you do not need to select fields for the operation output because all fields are selected by default on the
Operation Output tab of getCustomerByID_Output.
10. To review the input of the operation mapping, select the Mapping Input tab.
11. To review the output of the operation mapping, select getCustomerByID_Output and then select the
Mapping Output tab.
12. Click Finish.
The Developer tool creates the Hypostores_CustDetails web service and an operation mapping for the operation.
The operation mapping contains an Input, Lookup, and Output transformation.
Task 1. Create a Web Service 23
Task 2. View and Validate the Operation Mapping
In this task, you view and validate the operation mapping.
1. In the Outline view, select the operation mapping.
The operation mapping appears in the editor.
2. Right-click an empty area of the editor and click Validate.
The Developer tool displays a message stating that it found no validation errors.
Task 3. Test the Operation Mapping
In this task, you test the operation mapping by providing a customer ID as input and previewing the customer
details in the output. In the Data Viewer view, you can enter a SOAP request in the Input window and view the
SOAP response in the Output window.
1. Click an empty area in the editor.
2. Select the Data Viewer view.
3. In the Input window, replace the question mark (?) with 10110147.
10110147 is a customer ID.
4. Click Run.
The Output window displays the SOAP response based on the customer ID you entered.
Task 4. Create an Application
In this task, you create an application that contains the web service.
1. Click File > New > Application.
The New Application dialog box appears.
2. Enter HypoStores_CustDetails for the application name and click Next.
3. Click Add.
The Add Objects dialog box appears.
4. Select HypoStores_CustDetails and click OK.
5. Click Finish.
The Developer tool creates an application that contains the HypoStores_CustDetails web service.
24 Chapter 6: Lesson 5. Creating a Web Service
Task 5. Deploy the Application
In this task, you deploy the application so that a web service client can connect to the web service.
1. In the Object Explorer view, expand Applications in the tutorial project.
2. Right-click the HypoStores_CustDetails application and click Deploy.
The Deploy dialog box appears.
3. Click Browse next to the Domain option.
4. Select a domain and click OK.
5. Select the Data Integration Service that you want to deploy the application to.
6. Click Finish.
When the deployment succeeds, the Deploy Completed dialog box appears.
7. Click OK.
After you deploy the application, you can view the WSDL URL in the Administrator tool.
Creating a Web Service Summary
In this lesson, you learned that you can define a web service operation from a logical data object. You learned that
you configure the operation input and operation output based on the data that a web service receives or sends to
a web service client. You also learned that you can make the web service available so that a web service client
can connect to the web service.
You created a web service, validated the operation mapping, and tested the operation mapping to preview the web
service response. You also created an application to contain the web service and deployed the application to a
Data Integration Service.
Task 5. Deploy the Application 25
C H A P T E R 7
Lesson 6. Exporting a Mapping to
PowerCenter
Exporting a Mapping to PowerCenter Overview, 26
Task 1. Export a Mapping to PowerCenter, 27
Exporting a Mapping to PowerCenter Summary, 27
Exporting a Mapping to PowerCenter Overview
You can export a mapping that you create in the Developer tool to a PowerCenter repository. Export mappings to
PowerCenter to reuse the metadata for physical data integration or to create web services.
Story
You have developed a mapping that provides a single view of Los Angeles and Boston customer data. You want to
export this mapping to PowerCenter so that you can apply version control and load the target data to the central
data warehouse.
Objectives
In this lesson, you export a Developer tool mapping to a PowerCenter repository.
Prerequisites
Before you start this lesson, verify the following prerequisites:
Complete lessons 1, 2, and 3.
You can connect to the PowerCenter repository that you want to export the Developer mapping to. To get the
repository login information, contact a domain administrator.
Timing
Set aside 5 to 10 minutes to complete this task.
26
Task 1. Export a Mapping to PowerCenter
In this task, you export a mapping that you created in the Developer tool to a PowerCenter repository.
2. Click File > Export.
The Export dialog box appears.
3. Select Informatica > PowerCenter.
4. Click Next.
The Export to PowerCenter dialog box appears.
5. Select PowerCenter 9.1.0 as the target release.
6. Select PowerCenter Repository as the export location.
7. Click Browse to connect to a PowerCenter repository.
The Connect to PowerCenter Repository dialog box appears.
8. Enter the connection information and click OK.
The Developer tool displays a message after it connects to the repository.
9. Click OK.
10. Select the repository folder that you want to export the mapping to.
If the repository contains a tutorial folder, select it.
11. Click Next.
The Developer tool prompts you to select the objects to export.
12. Select Customer_Orders and click Finish.
The Developer tool exports the objects to the location you selected.
Exporting a Mapping to PowerCenter Summary
In this lesson, you learned that you can export Developer tool mappings to PowerCenter. You export mappings to
PowerCenter to reuse the metadata for physical data integration or to create web services.
You also exported a mapping to a PowerCenter repository.
Task 1. Export a Mapping to PowerCenter 27
A P P E N D I X A
Frequently Asked Questions
This appendix includes the following topic:
Informatica Developer Frequently Asked Questions, 28
Informatica Developer Frequently Asked Questions
Review the frequently asked questions to answer questions you may have about Informatica Developer.
What is the difference between a source and target in PowerCenter and a physical data object in the Developer tool?
In PowerCenter, you create a source definition to include as a mapping source. You create a target definition
to include as a mapping target. In the Developer tool, you create a physical data object that you can use as a
mapping source or target.
What is the difference between a mapping in the Developer tool and a mapping in PowerCenter?
A PowerCenter mapping specifies how to move data between sources and targets. A Developer tool mapping
specifies how to move data between the mapping input and output.
A PowerCenter mapping must include one or more source definitions, source qualifiers, and target definitions.
A PowerCenter mapping can also include shortcuts, transformations, and mapplets.
A Developer tool mapping must include mapping input and output. A Developer tool mapping can also include
transformations and mapplets.
The Developer tool has the following types of mappings:
Mapping that moves data between sources and targets. This type of mapping differs from a PowerCenter
mapping only in that it cannot use shortcuts and does not use a source qualifier.
Logical data object mapping. A mapping in a logical data object model. A logical data object mapping can
contain a logical data object as the mapping input and a data object as the mapping output. Or, it can
contain one or more physical data objects as the mapping input and logical data object as the mapping
output.
Virtual table mapping. A mapping in an SQL data service. It contains a data object as the mapping input
and a virtual table as the mapping output.
Virtual stored procedure mapping. Defines a set of business logic in an SQL data service. It contains an
Input Parameter transformation or physical data object as the mapping input and an Output Parameter
transformation or physical data object as the mapping output.
What is the difference between a mapplet in PowerCenter and a mapplet in the Developer tool?
A mapplet in PowerCenter and in the Developer tool is a reusable object that contains a set of
transformations. You can reuse the transformation logic in multiple mappings.
28
A PowerCenter mapplet can contain source definitions or Input transformations as the mapplet input. It must
contain Output transformations as the mapplet output.
A Developer tool mapplet can contain data objects or Input transformations as the mapplet input. It can
contain data objects or Output transformations as the mapplet output. A mapping in the Developer tool also
includes the following features:
You can validate a mapplet as a rule. You use a rule in a profile.
A mapplet can contain other mapplets.
What is the difference between a mapplet and a rule?
You can validate a mapplet as a rule. A rule is business logic that defines conditions applied to source data
when you run a profile. You can validate a mapplet as a rule when the mapplet meets the following
requirements:
It contains an Input and Output transformation.
The mapplet does not contain active transformations.
It does not specify cardinality between input groups.
Informatica Developer Frequently Asked Questions 29
A P P E N D I X B
Glossary
A
application
A deployable object that can contain data objects, mappings, SQL data services, web services, and workflows.
C
cost-based optimization
Optimization method that reduces the run time for mappings that perform join operations. With cost-based
optimization, the Data Integration Service creates different plans to run a mapping and calculates a cost for each
plan. The Data Integration Service runs the plan with the smallest cost. The Data Integration Service calculates
cost based on database statistics, I/O, CPU, network, and memory.
customized data object
A physical data object that uses one or more related relational resources or relational data objects as sources.
You use a customized data object to perform tasks such as join data from related resources or filter rows.
Customized data object uses a single connection and SQL statement for the source tables.
D
Data Integration Service
An application service that performs data integration tasks for Informatica Analyst, Informatica Developer, and
external clients. Data integration tasks include previewing data and running mappings, profiles, SQL data services,
web services, and workflows.
data service
A collection of reusable operations that you can run to access and transform data. A data service provides a
unified model of data you can access through a web service or run an SQL query against.
deploy
To make objects within an application accessible to end users. Depending on the types of objects in the
application, end users can then run queries against the objects, access web services, run mappings, or run
workflows.
E
early projection optimization
Optimization method that reduces the amount of data that moves between transformations in the mapping. With
early projection optimization, the Data Integration Service identifies unused ports and removes the links between
the ports in a mapping.
early selection optimization
Optimization method that reduces the number of rows that pass through the mapping. With early selection
optimization, the Data Integration Service moves filters closer to the mapping source in the pipeline.
F
folder
A container for objects in the Model Repository. Use folders to organize objects in a project and create folders to
group objects based on business needs.
I
Informatica Administrator
Informatica Administrator (the Administrator tool) is an application that consolidates the administrative tasks for
domain objects such as services, nodes, licenses, and grids. You manage the domain and the security of the
domain through the Administrator tool.
Informatica Developer
Informatica Developer (the Developer tool) is an application that you use to design data integration solutions. The
Model repository stores the objects that you create in the Developer tool.
Informatica Monitoring Tool
Informatica Monitoring Tool (the Monitoring tool) is an application that provides a direct link to the Monitoring tab
of the Administrator tool. The Monitoring tab shows properties, run-time statistics, and run-time reports about the
integration objects that run on a Data Integration Service.
L
logical data object
An object in a logical data object model that describes a logical entity in an enterprise. It has attributes, keys, and
it describes relationships between attributes.
logical data object mapping
A mapping that links a logical data object to one or more physical data objects. It can include transformation logic.
logical data object model
A data model that contains logical data objects and defines relationships between them.
logical data object read mapping
A mapping that links a logical data object to physical data objects to provide a single view of data from multiple
sources without accessing the underlying data sources.
Appendix B: Glossary 31
logical data object write mapping
A mapping that provides a way to write data to targets using a logical data object as input.
M
mapping
A set of inputs and outputs linked by transformation objects that define the rules for data transformation.
mapplet
A reusable object that contains a set of transformations that you can use in multiple mappings or validate as a rule.
Model Repository Service
An application service in the Informatica domain that runs and manages the Model repository. The Model
repository stores metadata created by Informatica products in a relational database to enable collaboration among
the products.
N
node
A representation of a level in the hierarchy of a web service message.
O
operation mapping
A mapping that performs the web service operation for the web service client. An operation mapping can contain
an Input transformation, an Output transformation, and multiple Fault transformations.
P
physical data object
A physical representation of data that is used to read from, look up, or write to resources.
predicate expression
An expression that filters the data in a mapping. A predicate expression returns true or false.
predicate optimization
Optimization method that simplifies or rewrites the predicate expressions in a mapping. With predicate
optimization, the Data Integration Service attempts to apply predicate expressions as early as possible to increase
mapping performance.
project
The top-level container to store objects created in Informatica Analyst and Informatica Developer. Create projects
based on business goals or requirements. Projects appear in both Informatica Analyst and Informatica Developer.
32 Glossary
pushdown optimization
Optimization method that pushes transformation logic to a source or target database. With pushdown optimization,
the Data Integration Service translates the transformation logic into SQL queries and sends the SQL queries to the
database. The database runs the SQL queries to process the data.
R
result set caching
A cache that contains the results of each SQL data service query or web service request. With result set caching,
the Data Integration Service returns cached results when users run identical queries. Result set caching
decreases the run time for identical queries.
S
semi-join optimization
Optimization method that reduces the number of rows extracted from the source. With semi-join optimization, the
Data Integration Service modifies the join operations in a mapping. The Data Integration Service applies the semi-
join optimization method to a Joiner transformation when a larger input group has rows that do not match a smaller
input group in the join condition. The Data Integration Service reads the rows from the smaller group, finds the
matching rows in the larger group, and performs the join operation.
SQL data service
A virtual database that you can query. It contains virtual objects and provides a uniform view of data from
disparate, heterogeneous data sources.
SQL Service Module
The component service in the Data Integration Service that manages SQL queries sent to an SQL data service
from a third-party client tool.
T
transformation
A repository object in a mapping that generates, modifies, or passes data. Each transformation performs a
different function.
V
virtual data
The information obtained when you query virtual tables or run stored procedures in an SQL data service.
virtual database
An SQL data service that you can query. It contains virtual objects and provides a uniform view of data from
disparate, heterogeneous data sources.
virtual schema
A schema in a virtual database that defines the database structure.
Appendix B: Glossary 33
virtual stored procedure
A set of procedural or data flow instructions in an SQL data service.
virtual table
A table in a virtual database.
virtual table mapping
A mapping that contains a virtual table as a target.
virtual view of data
A virtual database defined by an SQL data service that you can query as if it were a physical database.
W
Web Service Module
A component in the Data Integration Service that manages web service operation requests sent to a web service
from a web service client.
web service transformation
A transformation that processes web service requests or web service responses. Examples of web service
transformations include an Input transformation, Output transformation, Fault transformation, and the Web Service
Consumer transformation.
34 Glossary

Informatica Data Services Getting Started Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Informatica Data Services Getting Started Guide

Caricato da

Copyright:

Formati disponibili

Informatica Data Services (Version 9.5.

Sun Microsystems. All rights reserved. Copyright

RSA Security Inc. All Rights Reserved. Copyright

Ordinal Technology Corp. All rights

Intalio. All rights reserved. Copyright

Oracle. All rights reserved. Copyright

Adobe Systems Incorporated. All

DataArt, Inc. All rights reserved. Copyright

ComponentSource. All rights reserved. Copyright

Microsoft Corporation. All rights reserved.

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

International Organization for Standardization 1986. All rights reserved. Copyright

ej-technologies GmbH. All rights reserved. Copyright

is International Business Machines Corporation. All rights reserved. Copyright

yWorks GmbH. All rights reserved. Copyright

Daniel Veillard. All rights reserved. Copyright

MicroQuill Software Publishing, Inc. All rights reserved. Copyright

PassMark Software Pty Ltd. All rights reserved.

LogiXML, Inc. All rights reserved. Copyright

2003-2010 Lorenzi Davide, All rights reserved. Copyright

Red Hat, Inc. All rights reserved. Copyright

EMC Corporation. All rights reserved. Copyright

Flexera Software. All rights reserved.

) 1993-2006, all rights reserved.

2002 Ralf S. Engelschall, Copyright

2002 The OSSP Project Copyright

2002 Cable & Wireless

Potrebbero piacerti anche