Informatica Data Integration Analyst - 9.5.1 - User Guide ... · information provided in this...

Informatica Data Integration Analyst (Version 9.5.1)

User Guide

Informatica Data Integration Analyst User Guide

Version 9.5.1August 2012

Copyright (c) 1998-2012 Informatica. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use anddisclosure 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 internationalPatents 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 inDFARS 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 inwriting.

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 OnDemand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and InformaticaMaster Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other companyand 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 rightsreserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rightsreserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © MetaIntegration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. Allrights 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 © InformationBuilders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rightsreserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH. All rights reserved. Copyright © JaspersoftCorporation. 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 Boardof 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 theLicense 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 notlimited 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 ofthis 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, <[email protected]>. All Rights Reserved. Permissions and limitations regarding thissoftware 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 withoutfee 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 availableat 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 termsavailable 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 thissoftware 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 & WirelessDeutschland. 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 subjectto 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 termsavailable 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 DistributionLicense (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code LicenseAgreement 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).

This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this softwareare subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For furtherinformation 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 impliedwarranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. Theinformation provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation issubject 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 SoftwareCorporation ("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 NOTLIMITED 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 OFTHE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACHOF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: DS-IUG-95100-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1: Introduction to Informatica Data Integration Analyst. . . . . . . . . . . . . . . . . . . . . 1Informatica Data Integration Analyst Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Informatica Analyst Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Informatica Analyst Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Contents View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Properties View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Security View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Logging In to Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2: Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Connections Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

DB2 Connection Properties in Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

SQL Server Connection Properties in Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

ODBC Connection Properties in Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Oracle Connection Properties in Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Searching for a Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Creating a Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Editing and Testing a Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Deleting a Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3: Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Projects Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Creating a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Duplicating a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Renaming a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Deleting a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Rules and Guidelines for Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table of Contents i

Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Creating a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Renaming a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Duplicating a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Moving a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Deleting a Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Viewing a Project or Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Object Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Viewing an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Duplicating an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Renaming an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Moving an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Deleting an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Metadata Bookmarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Creating a Metadata Bookmark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Opening a Metadata Bookmark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Creating and Assigning a Tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Viewing Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Search Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Search Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Search Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Performing a Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Importing Metadata Manager Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Searching Objects Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Project Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Rules and Guidelines for Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Job Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Monitoring Job Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Metadata Manager Business Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Managing Business Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 4: Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Data Objects Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Flat Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Flat File Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Flat File Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Datetime Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Adding a Delimited Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Adding a Fixed-width Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ii Table of Contents

Synchronizing a Flat File Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Rules and Guidelines for Flat Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Database Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Adding a Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Synchronizing a Relational Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Rules and Guidelines for Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Viewing Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Editing Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 5: Mapping Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Mapping Specification Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Analyst and Developer Collaboration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Mapping Specification Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Mapping Specification Development. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Mapping Specification Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Column Mapping View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Properties View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Data Preview View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

SQL Query View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Profile Summary View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 6: Mapping Specification Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Mapping Specification Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Creating a Mapping Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Editing a Mapping Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Map Source and Target Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Mapping Source and Target Columns by Name or Position. . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Mapping to Selected Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Finding Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Removing Column Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Mapping Specification Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Validation Errors During Mapping Specification Development. . . . . . . . . . . . . . . . . . . . . . . . . . 51

Validation Errors During Data Preview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Validation Errors During a Load Operation to the Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

SQL Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Adding an SQL Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Editing an SQL Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 7: Mapping Specification Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Mapping Specification Objects Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Mapping Specification Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Adding and Editing a Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Table of Contents iii

Mapping Specification Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Mapping Specification Target Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Edit Options for Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Editing the Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Mapping Specification Aggregators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Aggregator Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Adding and Editing a Simple Aggregator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Adding and Editing an Advanced Aggregator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Mapping Specification Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Applying a Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Creating a Mapping Specification Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Mapping Specification Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Adding and Editing a Simple Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Adding and Editing an Advanced Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Mapping Specification Lookups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Lookup Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Lookup Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Adding a Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Editing a Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Mapping Specification Joins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Adding and Editing a Simple Join. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Adding an Editing an Advanced Join. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 8: Mapping Specification Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Mapping Specification Profiles Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Running a Column Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Profile Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Column Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Column Patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Column Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Viewing Column Profile Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 9: Sharing Mapping Specification Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Sharing Mapping Specification Logic Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Mapping Specification Export to Microsoft Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Exporting a Mapping Specification to Microsoft Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Mapping Specifications in Microsoft Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Mapping Specification Export to PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

PowerCenter Repository Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Exporting a Mapping Specification to PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Mapping Specification Export as a Virtual Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Exporting a Mapping Specification as a Virtual Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Mapping Specification Export to a Table Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

iv Table of Contents

Exporting a Mapping Specification to a Table Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Loading Mapping Specification Results to a Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Loading the Results of a Mapping Specification to a Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Rules and Guidelines for Loading Mapping Specification Results to a Flat File. . . . . . . . . . . . . . . . . . 76

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Table of Contents v

PrefaceThe Informatica Data Integration Analyst User Guide is written for data integration analysts. It describes how touse Informatica Analyst. This guide assumes that you have an understanding of data integration concepts, flat fileand relational database concepts, and the database engines in your environment.

Informatica Resources

Informatica Customer PortalAs 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 ProductDocumentation, and access to the Informatica user community.

Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you havequestions, comments, or ideas about this documentation, contact the Informatica Documentation team throughemail at [email protected]. We will use your feedback to improve our documentation. Let usknow 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 SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains informationabout Informatica, its background, upcoming events, and sales offices. You will also find product and partnerinformation. The services area of the site includes important information about technical support, training andeducation, and implementation services.

Informatica How-To LibraryAs 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. Itincludes articles and interactive demonstrations that provide solutions to common problems, compare features andbehaviors, and guide you through performing specific real-world tasks.

vi

http://mysupport.informatica.com

mailto:[email protected]


http://www.informatica.com


Informatica Knowledge BaseAs 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 Informaticaproducts. You can also find answers to frequently asked questions, technical white papers, and technical tips. Ifyou have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Baseteam through email at [email protected].

Informatica Multimedia Knowledge BaseAs 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 filesthat help you learn about common concepts and guide you through performing specific tasks. If you havequestions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Baseteam through email at [email protected].

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support. Online Support requiresa 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 FreeBrazil: 0800 891 0202Mexico: 001 888 209 8853North America: +1 877 463 2435

Toll FreeFrance: 0805 804632Germany: 0800 5891281Italy: 800 915 985Netherlands: 0800 2300001Portugal: 800 208 360Spain: 900 813 166Switzerland: 0800 463 200United Kingdom: 0800 023 4632

Standard RateBelgium: +31 30 6022 797France: +33 1 4138 9226Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511445

Toll FreeAustralia: 1 800 151 830New Zealand: 09 9 128 901

Standard RateIndia: +91 80 4112 5738

Preface vii






C H A P T E R 1

Introduction to Informatica DataIntegration Analyst

This chapter includes the following topics:

¨ Informatica Data Integration Analyst Overview, 1

¨ Informatica Analyst, 1

¨ Logging In to Informatica Analyst, 4

Informatica Data Integration Analyst OverviewInformatica Analyst (the Analyst tool) is a web-based application client that analysts can use to perform dataintegration tasks in an enterprise. Use the Analyst tool to collaborate with data integration developers on dataintegration solutions.

The Analyst Service manages the Analyst tool. The Analyst tool uses projects to store folders and objects. TheAnalyst tool stores projects, folders, and objects in the Model repository. The Analyst tool connects to the Modelrepository database to create, update, and delete projects and objects in the Analyst tool.

You can import data objects such as tables and flat files into projects and folders. The Analyst Service managesthe connection to the directory that stores uploaded flat files that you use as flat file sources in the Analyst tool.The Analyst Service also manages the connection to a database that stores reference tables that you create orimport in the Analyst tool.

You can use the data objects to create mapping specifications to define business logic that transforms and movesdata from a source to a target.

Informatica AnalystThe Analyst tool has a web-based interface that you can use to perform data integration and data quality tasks.

The Analyst tool interface has tabs, headers, views, and a Navigator. Use the Navigator to browse projects andperform tasks on projects and folders.

When you log in to the Analyst tool, the Browse: Projects tab appears. The tab displays views and the Navigator.The tab also displays the icons and the Actions menus that you can use to perform tasks in the Navigator and inviews.

1

When you click the link for an object in a view, the object opens in a tab. After you perform a search, the Analysttool displays the search results in a tab. You can keep multiple tabs open in the Analyst tool interface. You cannavigate between tabs.

The Analyst tool has the following header items:

¨ Log Off. Log out of the Analyst tool.

¨ Manage. Set user preferences to open metadata bookmarks in the Analyst tool or Developer tool and to deletedatabase connections. Monitor the status of Analyst tool jobs for objects such as profiles, scorecards,reference tables, and mapping specifications. Manage Metadata Manager business terms.

¨ Help. Access help for the current tab.

¨ Search. Search for folders in projects. Search for objects in the Model repository and the Metadata Managerrepository.

Informatica Analyst NavigatorUse the Navigator to browse projects and folders and their contents. After you log in to the Analyst tool, theNavigator appears in the left pane.

When you select a project in the Navigator, you can select a view to view the project contents, descriptiveinformation about the project, and permissions on the project.

The Navigator displays the following types of objects:

¨ Projects. Highest object in the Navigator hierarchy. It is the top-level container for all projects that you create.

¨ Folders. Child object of a project. Organize domain objects within a project in folders.

Refresh the Navigator to get the latest version of all objects in the Navigator. Multiple users can add projects andfolders that appear in the Navigator.

The Navigator has an Actions menu that you can use to perform tasks on projects and folders. You can also right-click projects and folders to perform the same tasks.

Use the Navigator to perform the following tasks:

¨ Create projects and folders.

¨ Manage projects and folders.

¨ Refresh the projects and folders that appear in the Navigator.

Informatica Analyst ViewsThe Analyst tool has views for the projects and folders that you select in the Navigator. Objects that open in tabsalso have views. Use the Actions menu or right-click objects to perform tasks related to the view. You can alsoclick icons in the view panels to perform the common tasks related to the view.

The Contents View and the Properties View are the views for the top-level Projects container. The Projectscontainer contains the projects that you create in the Navigator.

After you select a project or folder, the Analyst tool interface displays the following views:

¨ Contents view. Displays project or folder contents and properties for selected objects.

¨ Properties view. Displays project or folder properties.

¨ Security view. Displays user permissions on the project.

2 Chapter 1: Introduction to Informatica Data Integration Analyst

Contents ViewUse the Contents view to view project and folder information. In the Contents view, you can create and add dataobjects and profiles to projects and folders. You can perform project and folder management tasks.

After you select a project or folder in the Navigator, click the Contents view to view project or folder contents.

The Contents view displays project or folder contents in the Contents panel. When you select an object in theContents panel, the Analyst tool displays the object properties in the Properties panel.

You can perform the following tasks in the Contents view:

¨ Open an object.

¨ Duplicate projects, folders, and objects.

¨ Rename projects, folders, and objects.

¨ Move folders and objects.

¨ Delete projects, folders, and objects.

¨ Add a flat file to a project or folder.

¨ Add a relational table to a project or folder.

¨ Create a custom profile.

¨ Create a reference table.

¨ Create bad record or duplicate record tables.

¨ Close all tabs.

Properties ViewUse the Properties view to view descriptive information about the project or folder.

After you select a project or folder in the Navigator, click the Properties view to view the project or folderproperties.

In the Properties view, you can view the project or folder name and description.

Security ViewUse the Security view to view and assign project-level permissions to users.

After you select a project in the Navigator, click the Security view to view user permissions on the project. In theSecurity view, you can assign the read, write, and grant permissions to users. You can also add users and assignpermissions to them.

The Security view displays the following information in the Project-level permissions panel:

¨ User. User name for the user who is assigned permissions on the project.

¨ Security domain. Name of the security domain that the user belongs to. Security domain can be LDAP orNative.

¨ Permission. Permissions assigned to the user. Permissions can include read, write, or grant permission.

Informatica Analyst 3

Logging In to Informatica AnalystUse the Analyst tool URL to log in to the Analyst tool interface. When you log in to the Analyst tool, you mustspecify the user name, password, and the native domain or the LDAP security domain.

1. Start a Microsoft Internet Explorer or Mozilla Firefox browser.

2. In the Address field, enter the URL for the Analyst tool:http[s]://<host name>:<port number>/AnalystTool

3. On the login page, enter your user name and password.

4. Select Native or the name of a specific security domain.

The Security Domain field appears when the Informatica domain contains an LDAP security domain. If you donot know the security domain that your user account belongs to, contact the Informatica domain administrator.

5. Click Login.

The welcome screen appears.

6. Click Close to exit the welcome screen and access the Analyst tool.

4 Chapter 1: Introduction to Informatica Data Integration Analyst

C H A P T E R 2

ConnectionsThis chapter includes the following topics:

¨ Connections Overview, 5

¨ DB2 Connection Properties in Informatica Analyst, 6

¨ SQL Server Connection Properties in Informatica Analyst, 6

¨ ODBC Connection Properties in Informatica Analyst, 8

¨ Oracle Connection Properties in Informatica Analyst, 8

¨ Searching for a Database Connection, 9

¨ Creating a Database Connection, 10

¨ Editing and Testing a Database Connection, 10

¨ Deleting a Database Connection, 11

Connections OverviewA connection is a repository object that defines a connection in the domain configuration repository.

Create a connection to import relational or nonrelational data objects, preview data, run a profile on data, and runmappings. The Analyst tool uses the connection when you import a data object. The Data Integration Service usesthe connection when you preview data, run a profile, or run mappings.

The Analyst tool stores connections in the domain configuration repository. Any connection that you create in theAnalyst tool is available in the Developer tool or the Administrator tool.

Create and manage connections in the Manage Connections dialog box.

You can create the following types of connections in the Analyst tool:

¨ IBM DB2

¨ Microsoft SQL Server

¨ ODBC

¨ Oracle

You can browse and import tables from IBM DB2/zOS connections. You must create IBM DB2/zOS connections inthe Administrator tool or the Developer tool.

5

DB2 Connection Properties in Informatica AnalystUse a DB2 connection to access tables in an IBM DB2 database.

The following table describes the DB2 connection properties:

Property Description

User name Database user name.

Password Password for the user name.

Pass-through security enabled When enabled, the Data Integration Service connects to an IBM DB2 source withthe client user credentials instead of the credentials from a connection object.

Connection String Connection string to import physical data objects. Use the following connectionstring: jdbc:informatica:db2://<host>:50000;databaseName=<dbname>

Data Access Connection String Connection string to preview data and run mappings. Enter dbname from the aliasconfigured in the IBM DB2 client.

Code Page Database code page.

Environment SQL Optional. Enter SQL commands to set the database environment when youconnect to the database. The Data Integration Service executes the connectionenvironment SQL each time it connects to the database.

Transaction SQL Optional. Enter SQL commands to set the database environment when youconnect to the database. The Data Integration Service executes the transactionenvironment SQL at the beginning of each transaction.

Retry Period Number of seconds the Data Integration Service attempts to reconnect to thedatabase if the connection fails. If the Data Integration Service cannot connect tothe database in the retry period, the session fails. Default is 0.

Tablespace Tablespace name of the IBM DB2 database.

SQL identifier character to use The type of character used to identify special characters and reserved SQLkeywords, such as WHERE. The Data Integration Service places the selectedcharacter around special characters and reserved SQL keywords. The DataIntegration Service also uses this character for the Support mixed caseidentifiers property.

Support mixed case identifiers When enabled, the Data Integration Service places identifier characters aroundtable, view, schema, synonym, and column names when generating andexecuting SQL against these objects in the connection. Use if the objects havemixed-case or lowercase names. By default, this option is selected.

SQL Server Connection Properties in InformaticaAnalyst

Use a SQL Server connection to access tables in a Microsoft SQL Server database.

6 Chapter 2: Connections

The following table describes the SQL Server connection properties:




Pass-through security enabled Optional. When enabled, the Data Integration Service connects to a MicrosoftSQL Server database with the client user credentials instead of the credentialsfrom a connection object. By default, this option is not selected.

Use Trusted Connection Optional. When enabled, the Data Integration Service uses Windowsauthentication to access the Microsoft SQL Server database. The user name thatstarts the Data Integration Service must be a valid Windows user with access tothe Microsoft SQL Server database. By default, this option is not selected.

Connection String Connection string to import physical data objects. Use the following connectionstring: jdbc:informatica:sqlserver://<host>:<port>;SelectMethod=cursor;databaseName=<dbname>.

Data Access Connection String Connection string to preview data and run mappings. Enter<ServerName>@<DBName>.





Domain Name Optional. Name of the domain where Microsoft SQL Server is running.

Packet Size Required. Optimize the ODBC connection to Microsoft SQL Server. Increase thepacket size to increase performance. Default is 0.

Owner Name The name of the owner of the schema.

Schema Name The name of the schema in the database. You must specify the schema namefor the Profiling Warehouse and staging database if the schema name isdifferent than the database user name.

SQL identifier character to use The type of character used to identify special characters and reserved SQLkeywords, such as WHERE. The Data Integration Service places the selectedcharacter around special characters and reserved SQL keywords. The DataIntegration Service also uses this character for the SSupport mixed-caseidentifiers property.

Support mixed case identifiers When enabled, the Data Integration Service places identifier characters aroundtable, view, schema, synonym, and column names when generating andexecuting SQL against these objects in the connection. Use if the objects havemixed-case or lowercase names. By default, this option is selected.

SQL Server Connection Properties in Informatica Analyst 7

ODBC Connection Properties in Informatica AnalystUse an ODBC connection to access tables in a database through ODBC.

The following table describes the ODBC connection properties:




Pass-through Security Enabled When enabled, the Data Integration Service connects to a database throughODBC with the client user credentials instead of the credentials from aconnection object. By default, this option is not selected.

Data Access Connection String Connection string to connect to the database.





SQL identifier character to use The type of character used to identify special characters and reserved SQLkeywords, such as WHERE. The Data Integration Service places the selectedcharacter around special characters and reserved SQL keywords. The DataIntegration Service also uses this character for the Support mixed caseidentifiers property.

Support mixed case identifiers When enabled, the Data Integration Service places identifier characters aroundtable, view, schema, synonym, and column names when generating andexecuting SQL against these objects in the connection. Use if the objects havemixed-case or lowercase names. By default, this option is not selected.

ODBC Provide Type of database that ODBC connects to. For pushdown optimization, specifythe database type to enable the Data Integration Service to generate nativedatabase SQL.

Oracle Connection Properties in Informatica AnalystUse an Oracle connection to access tables in an Oracle database.


The following table describes the Oracle connection properties:




Pass-through Security Enabled When enabled, the Data Integration Service connects to an Oracle database withthe client user credentials instead of the credentials from a connection object. Bydefault, this option is not selected.

Connection String Connection string to import physical data objects. Use the following connectionstring: jdbc:informatica:oracle://<host>:1521;SID=<sid>

Data Access Connection String Connection string to preview data and run mappings. Enter dbname.world fromthe TNSNAMES entry.




Connection Retry Period Number of seconds the Data Integration Service attempts to reconnect to thedatabase if the connection fails. If the Data Integration Service cannot connect tothe database in the retry period, the session fails. Default is 0.

Enable Parallel Mode Optional. Enables parallel processing when loading data into a table in bulkmode. Default is disabled.

SQL identifier character The type of character used to identify special characters and reserved SQLkeywords, such as WHERE. The Data Integration Service places the selectedcharacter around special characters and reserved SQL keywords. The DataIntegration Service also uses this character for the Support mixed-caseidentifiers property.

Support mixed-case identifiers When enabled, the Data Integration Service places identifier characters aroundtable, view, schema, synonym, and column names when generating andexecuting SQL against these objects in the connection. Use if the objects havemixed-case or lowercase names. By default, this option is selected.

Searching for a Database ConnectionYou can use a part of the connection name as a search string to find database connections. The Analyst toolhighlights the first database connection in the list that has the search string.

1. In the Informatica Analyst header, click Manage > Connections.

The Manage Connections dialog box appears.

Searching for a Database Connection 9

2. Click Find.

The Find text field appears above the connection list.

3. Type in part of the connection name.

The Analyst tool highlights the first connection name in the list that contains the search string.

4. Click Close.

Creating a Database ConnectionYou can create a database connection in the Analyst tool.

1. In the Analyst tool header, click Manage > Connections.


2. Click New to open the New Connection dialog box.

3. Enter the following information:

Option Description

Name Name of the connection. The name is not case sensitive and must be unique within the domain.It cannot exceed 128 characters, contain spaces, or contain the following special characters:~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /

ID String that the Data Integration Service uses to identify the connection. The ID is not casesensitive. It must be 255 characters or less and must be unique in the domain. You cannotchange this property after you create the connection. Default value is the connection name.

Description Optional description for the connection.

4. Select a database type such as DB2, SQL SERVER, and ORACLE.

Additional fields appear based on the database type you select.

5. Choose whether you need a Simple Connection or Advanced Connection.

If you choose an advanced connection, you need to fill in more connection information fields.

6. Specify the connection settings and click OK.

The Analyst tool tests the connection and displays the test status.

Editing and Testing a Database ConnectionAfter you make changes to the properties of a database connection, the Analyst tool tests whether the connectivityis successful. You cannot change the ID of a connection.

1. In the Analyst tool header, click Manage > Connections.


2. Select a connection and click Edit.


The Edit Connection dialog box appears.

3. Make the required changes and click OK.

Note: If you change a connection name, deployed applications and parameter files that use the connectionare no longer valid. Contact an administrator to redeploy applications in the Administrator tool or to updateparameter files.

The Analyst tool displays the connection status after testing.

4. Click OK and then click Close.

5. To test a connection without editing it, click the Test icon in the Manage Connections dialog box.

Deleting a Database ConnectionDelete database connections that become redundant. You must have the Write permission on the databaseconnection to delete the connection.

1. In the Informatica Analyst header, click Manage > Connections.


2. Select the connection and click Delete.

3. Click Close.

Deleting a Database Connection 11

C H A P T E R 3

ProjectsThis chapter includes the following topics:

¨ Projects Overview, 12

¨ Folders, 14

¨ Viewing a Project or Folder, 16

¨ Objects, 16

¨ Metadata Bookmarks, 20

¨ Tags, 21

¨ Search, 22

¨ Security, 25

¨ Job Status, 27

¨ Metadata Manager Business Terms, 29

Projects OverviewA project is the top-level container that you use to store folders and objects in the Analyst tool. Use projects toorganize and manage the objects that you want to analyze for data quality.

Create a project based on the structure of the data for which you want to analyze data quality. For example, ananalyst needs to assess data quality on multiple systems structured by region in a country. The analyst createsprojects named East and West to correspond with data for East and West regions. The analyst can import dataobjects such as relational tables and flat files in the East and West projects.

You must create or open a project before you can work in the Analyst tool. Use the Navigator to create a project inthe Analyst tool. When you create a project, the Analyst tool stores the project in the Model repository.

You can share a project to share the project contents and collaborate with other users on the project. When youshare a project in the Analyst tool, the project also appears in the Developer tool.

A project can contain folders and objects. You can organize objects in folders.

12

The following table describes the tasks you can perform on a project:

Task Description

Manage projects Manage and share project contents. You can create,duplicate, rename, and delete a project. You can view projectcontents.

Manage folders Organize project content in folders. You can create, duplicate,rename, move, and rename folders within projects.

Manage objects You can view object contents, duplicate, rename, move, anddelete objects in a project or in a folder within a project.

Search projects You can search for folders or objects in projects. You canview search results and select an object from the results toview its contents.

Assign permissions You can add users to a project. You can assign the read,write, and grant permissions to users on a project to restrict orprovide access to objects within the project.

Creating a ProjectCreate a project to store data objects and object types in the Analyst tool. You can create folders in projects. Useprojects to manage the folders and objects in the project.

1. In the Navigator, select Projects.

2. Click Actions > New Project.

The New Project window appears.

3. Enter a name for the project and an optional description.

4. Click Unshared if you do not want to share the project or Shared if you want to share the project with otherusers. Default is Unshared.

5. Click OK.

The project appears in the Navigator.

Duplicating a ProjectYou can duplicate project contents in another project that you create. Duplicate a project to use the same projectcontents to perform different project tasks. Duplicating a project does not duplicate the user permissions on theproject. The owner of the project gets all permissions by default on the duplicate project.

1. In the Navigator, select the project that you want to duplicate.

2. Click Actions > Duplicate.

The Duplicate window appears.

3. Enter the project name and an optional description.

4. Click OK.

The Analyst tool duplicates the project contents in the project.

Projects Overview 13

Renaming a ProjectYou can rename a project after you create it. Rename a project according to business usage and namingconvention. You may need to rename a project because the name is incorrect or the project has a different use.

1. In the Navigator, select the project that you want to rename.

2. Click Actions > Rename.

The Rename window appears.

3. Enter a name.

4. Click OK.

The Analyst tool renames the project in the Navigator.

Deleting a ProjectDelete a project when the project and its contents become redundant.

1. In the Navigator, select the project that you want to delete.

2. Click Actions > Delete.

3. In the Delete Project window, click Yes.

The Analyst tool deletes the project from the Navigator.

Rules and Guidelines for ProjectsThis section describes the rules and guidelines for working with projects.

Use the following rules and guidelines when you work with projects:

¨ You cannot move a project in the Navigator.

¨ You can move folders within a project but you cannot move a folder into one of its own child folders in a project.

¨ You cannot duplicate a project in another project with the same name.

¨ You cannot duplicate a folder within a project to another folder in a different project.

FoldersUse folders to organize project contents. You can create a folder to group objects for a particular task in a project.You can create a folder in a project or in another folder.

Create folders to group objects based on business needs. For example, a project requires data analysis for datastored in multiple relational databases across an organization. Each region has a relational database. You cancreate folders named East and West to store the project metadata for each region.

Folders appear under projects in the Navigator. A folder can contain other folders and objects.

You can perform the following tasks on a folder:

¨ Create a folder.

¨ View a folder.

¨ Rename a folder.

14 Chapter 3: Projects

¨ Duplicate a folder.

¨ Move a folder.

¨ Delete a folder.

Creating a FolderCreate a folder to store objects created in the Analyst tool.

1. In the Navigator, select the project or folder where you want to create a folder.

2. Click Actions > New Folder.

The New Folder window appears.

3. Enter the folder name and optional description.

4. Click OK.

The Analyst tool creates the folder in the Navigator.

Renaming a FolderYou can rename a folder after you create it. Rename a folder to change its name according to business usage ornaming convention.

1. In the Navigator, select the project and the folder in the project that you want to rename.


The Rename window appears.

3. Enter the folder name.

4. Click OK.

The Analyst tool renames the folder in the Navigator.

Duplicating a FolderYou can duplicate a folder within a project. Duplicate a folder to organize or enhance the contents of a folder or touse the contents of a folder to perform different tasks.

1. In the Navigator, select the project and the folder in the project that you want to duplicate.



3. Navigate to the location where you want to duplicate the folder.

Optionally, enter the location.

4. Enter the folder name.

5. Click OK.

The Analyst tool duplicates the folder in the project in the Navigator.

Moving a FolderYou can move a folder within a project. Move folders to organize project content into a hirearchy of folders.

Folders 15

1. In the Navigator, select the folder in the project you want to move.

2. Click Actions > Move.

The Move window appears.

3. Navigate to the location in the project where you want to move the folder.


4. Click OK.

The Analyst tool moves the folder in the project in the Navigator.

Deleting a FolderDelete a folder if the folder contents become redundant.

1. In the Navigator, select the folder in the project you want to delete.


The Delete Folder dialog box appears.

3. Click Yes to delete the folder.

The Analyst tool deletes the folder from the Navigator.

Viewing a Project or FolderYou can view objects in a project or folder. For each object, you can view the object name and object type on theContents view. You can view descriptive information such as project name and description about the project orfolder on the Properties view.

1. To view project or folder contents on the Contents view, select a project or folder in the Navigator and viewthe contents in the Contents panel.

The Analyst tool displays a list of all objects in the project or folder and displays the object name and objecttype for each object.

2. To view descriptive information about the project or folder on the Properties view, select a project or folderfrom the Navigator and view descriptive information in the Properties panel.

The Analyst tool displays the project name or folder name and description for the project or the folder.

ObjectsThe types of objects that you use in the Analyst tool depend on the structure of data for which you want to analyzedata quality. You can use data objects to structure the data and create object types to analyze data quality in aproject.

Data objects can include the relational tables and flat files that you import into the Analyst tool. Logical dataobjects created in Data Object Models in the Developer tool appear as logical data objects in projects shared bythe developer in the Analyst tool. These logical data object can appear as tables or flat files.


Object types include objects such as profiles, rules, scorecards, reference tables, bad record tables, and duplicaterecord tables that you create in the Analyst tool.

You can store objects in projects or folders. You can associate objects with tags. You can search for objects byname or by tag.

You can perform the following common tasks on object types and data objects:

¨ View an object.

¨ Duplicate an object.

¨ Rename an object.

¨ Move an object.

¨ Delete an object.

Note: You cannot duplicate, rename, move, or delete a logical data object.

Object PropertiesThe following table describes the objects that you can store in a project and the viewable object properties:

Object Data Object / Object Type Object Properties

Relational Tables Data Object - Name. Name of the table in themodel repository.

- Location. Location of the table in theproject or folder.

- Connection. Name of the databaserelational connection.

- Schema. Name of the databaseschema.

- Table Name. Name of the relationaltable source.

Flat Files Data Object - Location. Location of the flat file inthe project or folder.

- File Path. File path of the flat file ona network drive.

- Uploaded. File path of the uploadedflat file.

- File Name. Name of the flat file.

Logical data object Data Object - Name. Name of the table in themodel repository.


- Data Object Model. Name of theData Object Model from which thelogical data object was created.

- Logical Data Object Name. Logicaldata object table name.

Profiles Object Type - Location. Location of the profile inthe project or folder.

- Name. Name of the profile.

Rules Object Type - Location. Location of the rule in theproject or folder.

- Name. Name of the rule.

Objects 17

Object Data Object / Object Type Object Properties

Scorecards Object Type - Location. Location of the scorecardin the project or folder.

- Name. Name of the scorecard.

Reference Tables Object Type - Name. Name of the table in themodel repository.




- Table Name. Name of the referencetable.

Bad Record Tables Object Type - Name. Name of the table in themodel repository.




- Table Name. Name of the bad recordtable.

Duplicate Record Tables Object Type - Name. Name of the table in themodel repository.




- Table Name. Name of the duplicaterecord table.

Viewing an ObjectYou can view object properties for each object in a project or folder. You can open the object to preview data in atab. You can preview the contents of data objects and object types to view the structure of data and analyze dataquality results.

1. In the Navigator, select the project or folder that contains the object you want to view.

2. In the Contents panel, select the object you want to view.

The Analyst tool displays the name, type, and location of the object in the project or folder in the Propertiespanel. You can view connection name, Data Object Model name, table name, and schema name for tableobjects. Additionally, you can view the file path for flat file objects.

3. Click Actions > Open.

The Analyst tool opens the object contents for preview in a tab. You can preview column metadata for tablesand flat files and data quality results for other object types.


Duplicating an ObjectYou can duplicate objects within a project or within folders in a project to use objects for different tasks.

1. In the Navigator, select the project or folder that contains the object you want to duplicate.

2. In the Contents panel, select the object you want to duplicate.



4. Navigate to the location in the project where you want to duplicate the object.


5. Enter the name of the object.

6. Click OK.

The Analyst tool duplicates the object to the location in the project or folder.

Renaming an ObjectRename an object to change its name according to business usage and naming convention.

1. In the Navigator, select the project or folder that contains the object you want to copy.

2. In the Contents panel, select the object you want to rename.


The Renamewindow appears.

4. Enter the object name.

5. Click OK.

The Analyst tool renames the object with specified name.

Moving an ObjectMove an object within a project to another location in the project to organize project contents. You cannot move anobject to a target folder that is a child folder of the source folder.

1. In the Navigator, select the project that contains the object you want to move.

2. In the Contents panel, select the object you want to move.

3. Click Actions > Move.

The Move window appears.

4. Navigate to the location where you want to move the object to a folder.

Optionally, enter the location where you want to move the object to a folder.

5. Click OK.

The Analyst tool moves the object to specified location in the project or folder.

Deleting an ObjectDelete an object from a project or folder if the object becomes redundant.

1. In the Navigator, select the project or folder that contains the object you want to delete.

Objects 19

2. In the Contents panel, select the object you want to delete.


4. In the Delete Object dialog box, click Yes.

The Analyst tool deletes the object from the project or folder.

Metadata BookmarksA metadata bookmark is a link to an object in a Model repository. Use a metadata bookmark to share an objectwith other Analyst tool users.

Because the Analyst tool is a web-based tool, you can access objects through a link to the object in the theAnalyst tool. Each object you view in the Analyst tool has a unique URL. You can share an object with otherAnalyst tool users by sharing the URL for the object. You can create a metadata bookmark for any object that youcan open in the Analyst tool.

The following example shows a metadata bookmark for a relational table:

http://styx:8080/AnalystTool/com.informatica.at.AnalystTool/index.jsp#p=lewis&i=U:VeP2HpstEd66x8vkMFuKtQ&c=com.informatica.metadata.relational.datasource.RelationalDataSource

To share a metadata bookmark, open the object you want to share in the Analyst tool. Copy the link location in thelocation bar. You can then send the link in an email or add it to a document. You can also bookmark the link inyour browser to access it again.

To access a metadata bookmark, you can click the link or copy and paste the link into the location bar in abrowser. When you access a metadata bookmark, the Analyst tool prompts you to log in if you are not alreadylogged in, and then displays the object.

To access a metadata bookmark, you must have the following permissions:

¨ Permission to use the the Analyst tool.

¨ Permission to access the project that contains the object.

Creating a Metadata BookmarkCreate a metadata bookmark to share an object in Informatica Analyst with other users.

1. In the Analyst tool, open the object that you want to create a metadata bookmark for.

2. Copy the URL in the location bar of the browser.

You can then paste the bookmark into an email or a document and distribute the email or document to otherusers.

Opening a Metadata BookmarkOpen a metadata bookmark to access an object in the Analyst tool.

1. Click an active link for a metadata bookmark or copy and paste the link into the location bar in a browser.

If you are not already logged in, the Analyst tool displays the login page.

2. Log in to the Analyst tool.

The Analyst tool displays the object in a tab.


TagsA tag is metadata that defines an object in the Model repository based on business usage. Create tags to groupobjects according to their business usage.

After you create a tag, you can associate the tag with one or more objects. You can remove the associationbetween a tag and an object. You can use a tag to search for objects associated with the tag in the Modelrepository. The Analyst tool displays a glossary of all tags. You can delete redundant tags.

For example, an analyst creates a tag named XYZCorp_CustomerOrders and applies it to tables that containinformation for the customers orders from the XYZ Corporation. The analyst can search by theXYZ_CustomerOrders tag to identify the tables associated with the tag.

Note: Tags associated with an object in the Analyst tool appear as tags for the same objects in the Developer tool.

Creating and Assigning a TagCreate a tag to add metadata that defines an object based on business usage. Assign the tag to an object toassociate the object with this metadata definition.

1. Click Actions > Show Tags.

2. On the Tags panel, click New.

3. Enter a name and an optional descripton.

The Analyst tool adds the tag to the glossary.

4. To assign a tag to an object, select an object in the Navigator and select the tag and click Assign.

Viewing TagsThe Analyst tool displays a glossary of tags. You can view all tags or only those tags that are assigned to objects.

Perform the following actions to view tags:

Task Action

Display tags. Click Actions > Show Tags.The Analyst tool displays aglossary of tags on the Tags panel.

View tags in the glossary by a group. Select the groups of letters, #, or the Other group.

View tags that are assigned to objects. Select Applied Tags from the top drop down menu.

View all tags. Select All Tags from the top drop down menu.

View the description of a tag. Select a tag and view the description in the bottom panel.

Hide tags. Click Actions > Hide Tags.

Tags 21

SearchYou can search for objects and folders in the Analyst tool. Search folders to find objects for a particular task suchas profiling data or creating business rules.

You can search for data objects, object types, and folders by name in the Analyst tool. You cannot search forprojects by name.

The Model Repository Service uses a search engine to index the metadata in the Model repository. To correctlyindex the metadata, the search engine uses a search analyzer appropriate for the language of the metadata thatyou are indexing. The Analyst tool uses the search engine to perform searches on objects in the Model repository.

You can search for objects in the Model repository by object name or by a tag. If you have Metadata Manager, youcan search for objects in the Metadata Manager repository by object name or by a Metadata Manager businessterm. You can select a Metadata Manager object from the search results and import it into the Analyst tool.

You can create a search query and filter the search results. You can view search results and select an object fromthe search results and view its contents in another tab.

You can search in different languages. To search in a different language, an administrator must change the searchanalyzer and configure the Model repository to use the search analyzer. You can change the search analyzer inthe Model Repository Service. After you change the search analyzer, you must restart the Model RepositoryService and re-index the search index. For more information about changing the search analyzer, see theInformatica Administrator Guide.

Search SyntaxUse search syntax to create a search query and filter search results.

The following table describes the search syntax you can use in a search:

Search Syntax Description

Keywords Use an exact keyword match in the search.

Cases Use upper case and lower case text in the search.

Wildcards Use wildcard characters in the search.

Logical Operators Use logical operators in the search.

Keyword MatchesUse a keyword match to search for folders and objects that match the keyword.

Enclose a search query in quotation marks (" ") to search for an exact keyword match. The Analyst tool returnsobjects with the name that matches the keyword exactly.

Note: You cannot use wildcards or special characters in a search.


WildcardsUse wildcards to define one or more characters in a search. Use wildcards as a prefix, suffix, or infix in a search.

The following table describes the wildcards you can use in a search:

Wildcard Description

* Represents characters. For example when you search forcustomer*, the Analyst tool can return customer,customer_name, and CustomerID.

? Represents a single character. For example when you searchfor Customer?, the Analyst tool can return Customer1,Customer2, and CustomerA.

OperatorsUse boolean search operators to logically combine search terms. All boolean operators must be upper case.

The following table describes the search operators you can use in a search:

Operator Description

AND Includes both search terms. For example, sales data ANDdata sales.

OR Includes either one of the search terms. For example, salesdata OR sales.

NOT Excludes a search term. For example, sales data NOT datasales. The NOT operator requires two operands.

Search FiltersApply a filter to the search query to refine search results based on an object name, tag, or a Metadata Managerbusiness term.

When you select a filter and apply it to a search query, the Analyst tool returns search results based on the filter.You can perform an advanced search to further refine the search results.

When you search for objects by name or by a tag, the Analyst tool returns search results for objects in the Modelrepository. You can perform an advanced search to search by object name, tag, or object type.

When you search for objects by a Metadata Manager business term, the Analyst tool returns search results forobjects associated with the business term in the Metadata Manager repository. You can select a MetadataManager object from the search results and import the object into the Analyst tool. You can perform an advancedsearch to search by object name, business term, or object type. You must have Metadata Manager to search forobjects by a Metadata Manager business term.

Note: If the tag name is the same as a business term name, the Analyst tool returns search results for objectsassociated with the tag and the business term from the Model repository and the Metadata Manager repository.

Search 23

The following table describes the search filters that you can use to perform a search:

Search Filter Description

Search by Name Search for objects by name.

Search by Tag / Business Term Search for objects associated with a tag in the Modelrepository or objects associated with a business term in theMetadata Manager repository.

Advanced Search Search for objects in the Model repository by object name,tag, or object type. Search for objects in the MetadataManager repository by object name, business term, or objecttype.

Search ResultsView search results to get specific objects or folders in the Analyst tool or objects in the Metadata Managerrepository. You can import the Metadata Manager objects in the search results as data objects in the Analyst tool.

After you perform a search, the Analyst tool displays the search results on the Search Results tab. The Analysttool displays objects that appear in the Model repository on the Projects tab. The Analyst tool displays objectsthat appear in the Metadata Manager repository on the External Tables tab. If you do not have MetadataManager, the Analyst tool does not display any Metadata Manager objects.

Select an object from the search results to view the object properties. You can perform an advanced search tofurther refine the search results.

Performing a SearchPerform a search to search for folders in the Analyst tool or objects in the Model repository and Metadata Managerrepository.

1. In the Search header box, enter a keyword search or select a search filter.

The Analyst tool returns the results of the search in the Search Results tab.

2. To perform an advanced search, select the Projects tab or the External Tables tab.

3. In the Advanced Search panel, select a filter and select the object types.

Importing Metadata Manager TablesAfter you search for Metadata Manager objects by a business term, you can import the objects into the Modelrepository.

Before you perfom this task, verify the following prerequisite:

¨ License to access Metadata Manager.

¨ Perform a search by business term.

1. On the Search Results tab, select the External Tables tab.

2. Select a Metadata Manager table.

3. Right-click the table and select Add Import.

The New Tables window appears. Follow the steps to import the Metadata Manager table into the Analysttool.


Searching Objects ExampleAn analyst wants to search for customer financial data related to bank transactions across tables in the Modelrepository and the Metadata Manager Repository. The analyst uses the business term "finance" to search fortables that contain customer financial data. The analyst performs an advanced search to filter search results todisplay tables in the Metadata Manager repository associated with the business term finance.

1. In the Search box, select the Search by Tag / Business Term filter.

2. Enter the business term named "finance".

3. Select the External Tables tab.

4. In the Advanced Search panel, select Tables as the object type.

SecurityManage permissions on projects in the Analyst tool to control access to projects. You can add users to a projectand assign permissions for users on a project.

Even if a user has the privilege to perform certain actions, the user may also require permission to perform theaction on a particular object.

When you create a project, you are the owner of the project by default. The owner has all permissions, which youcannot change. The owner can assign permissions to users.

The following table describes the permissions you can assign for users on a project.

Permission Grants users the ability to

Read Read on project, view projects and objects in projects.

Write Modify projects, create, edit, and delete objects in projects.

Grant Grants users the ability to manage the read, write, and grant permissions on a project.

Project PermissionsAssign project permissions to users or groups. Project permissions determine whether a user or group can viewobjects, edit objects, or assign permissions to others.

You can assign the following permissions:

Read

The user or group can open, preview, export, validate, and deploy all objects in the project. The user or groupcan also view project details.

Write

The user or group has read permission on all objects in the project. Additionally, the user or group can edit allobjects in the project, edit project details, and delete all objects in the project.

Grant

The user or group has read permission on all objects in the project. Additionally, the user or group can assignpermissions to other users or groups.

Security 25

Users assigned the Administrator role for a Model Repository Service inherit all permissions on all projects in theModel Repository Service. Users assigned to a group inherit the group permissions.

Assigning Permissions on a ProjectYou can add users to a project and assign permissions on a project to restrict, provide access, or manage theobjects within the project.

1. In the Navigator, select a project, and click the Security tab.

2. In the Project-Level Permissions View on the Contents panel, Actions > Edit Permissions.

The Edit Permissions dialog box appears.

3. Select users, groups, or both from the Users and groups panel.

4. Optionally, Click Add Users and Groups icon to add users and groups to the project.

The Add Groups and Users dialog box appears.

5. To filter the list of users and groups, enter a name or string.

Optionally, use the wildcard characters in the filter.

6. Select Native and click the filter icon to show users and groups in the native security domain. Select All toshow all users and groups.

7. To filter by users or groups, select either User or Group and click the filter icon.

8. Select users, groups, or both that need to have access to the project.

9. Click Next.

10. Select or clear the Read, Write, and Grant permissions in the Permissions panel.

11. Click Save and then click OK.

Viewing Effective Permissions on a ProjectEffective permissions include both direct and inherited permissions on a project. Users can assign permissions toa project. Projects can also inherit permissions as a result of groups and users you add to the project.

1. In the Navigator, select a project, and click the Security tab.

2. In the Project-Level Permissions View on the Contents panel, Actions > View Effective Permissions.

The Effective Permissions dialog box appears.

3. Verify the effective permissions for users and groups. The permissions you see include both direct andinherited permissions.

4. To filter the list of users and groups, enter a name or string.

Optionally, use the wildcard characters in the filter.

5. Select Native and click the filter icon to show users and groups in the native security domain. Select All toshow all users and groups.

6. To filter by users or groups, select either User or Group and click the filter icon.

7. Click Close.


Rules and Guidelines for SecurityRules and guidelines for managing security.

Use the following rules and guidelines to manage security:

¨ A user can have the privilege to create a project but can view only those projects on which the user is assignedpermissions.

¨ A user with the privilege to create a project but not the permission to view a project can create a project with aname that already exists. The Analyst tool displays a message stating that the project already exists.

¨ When you assign the permission to view a project to a user, the user needs to refresh the Navigator to view theproject. An administrator can view all projects.

¨ A user with an active Analyst tool browser session can continue to browse projects after the Read and Writepermissions for the user on the project are removed in the Developer tool.

¨ An unauthorized user can bypass Analyst tool security by copying the Analyst tool URL from the Administratortool to gain full access to the Analyst tool.

Job StatusYou can monitor the status of Analyst tool jobs for objects such as profiles, scorecards, reference tables, andmapping specifications. You can monitor data preview for all objects and monitor drill down operations on profiles.

You can monitor the status of each Analyst tool job on the Job Status tab. After you select a job, you can viewerror or information messages and the general properties for the job on the bottom panel.

You can perform the following tasks to monitor jobs:

¨ Search for a job. Enter a job property as a search filter to search for a job.

¨ Clear search filters for a job.

¨ Refresh a job.

¨ Abort a job.

¨ View Analyst tool logs events for a job.

¨ View the context of a job. View other jobs that started around the same time as the selected job.

¨ Get notifications for new jobs.

The following table descibes the job status properties:


Job ID Identifier for the job.

Name Name of the job.

Type Job type. The Analyst tool displays the following job types:- Profile- Scorecard- Preview- Mapping- Reference Table process- Custom

Job Status 27


Select Custom to filter by multiple types.

State State of the job. The Analyst tool displays the following job states:- Running- Completed- Failed- Abborted- Unknown- CustomSelect Custom to filter by multiple states.

Started By Name of the user who starts the job.

Start Time Start time of the job. The Analyst tool displays the following start times:- Last 30 minutes- Last 4 hours- Last 1 day- Last 1 week- CustomSelect Custom to enter a date and time range.

Elapsed Time Time the Analyst tool runs the job before it completes. The Analyst tool displays the following option forelapsed time:- CustomSelect Custom to enter a date and time range.

End Time Time when the job ends.The Analyst tool displays the following options for end time:- Last 30 minutes- Last 4 hours- Last 1 day- Last 1 week- CustomSelect Custom to enter a date and time range.

User SecurityDomain

Security domain for the user name. Security domain can be Native or LDAP.

Monitoring Job StatusUse the Actions menu or the icons on the Job Status tab to monitor Analyst tool jobs.

1. On the Analyst tool header, click Manage > Monitor Job Status.

The Analyst tool opens monitoring in the Job Status tab.

2. To search for a job, enter a job status property in the search fields.

3. To view other jobs that started around the same time as the selected job, click Actions > View Context.

The Analyst tool displays nformation about the jobs in the Working view.

4. To refresh the job status, click Actions > Refresh.

5. To clear search filters, click Actions > Clear Search Filters.

6. To abort a job, select a job and click Actions > Abort Selected Job.

7. To view log events for a job in a text file, select the job and click Actions > View Logs for Selected Object.


8. To get the status of new jobs without having to refresh, select New Job Notifications.

Metadata Manager Business TermsYou can access Metadata Manager and the Metadata Manager Business Glossary from the Analyst tool. You canbrowse the Metadata Manager business glossary to view the business terms in a business glossary or viewbusiness terms grouped by category. You can edit Metadata Manager business terms.

You can search for Metadata Manager objects in the Metadata Manager repository by a Metadata Managerbusiness term. You can select Metadata Manager objects from the search results and import these as data objectsin the Analyst tool.

You can perform Metadata Manager tasks based on the license for Metadata Manager. You cannot add aMetadata Manager business term to the Metadata Manager business glossary.

Managing Business TermsYou can access the Metadata Manager Business Glossary from the Analyst tool to manage Metadata Managerbusiness terms.

1. On the Analyst tool header, click Manage > Manage Terms.

Metadata Manager and the Metadata Manager Business Glossary open in another tab. Metadata Managerbusiness terms appear on the Glossary view in Metadata Manager.

2. To choose a business glossary, select a glossary from the Show list.

3. To view business terms grouped by a category, click Actions > View > Categories.

4. To view all business terms in a business glossary in alphabetic order, click Actions > View > Alphabet.

5. To view all business terms that start with a specific letter, click the letter.

6. To edit a business term, select the business term and click Actions > Edit Properties.

Metadata Manager Business Terms 29

C H A P T E R 4

Data ObjectsThis chapter includes the following topics:

¨ Data Objects Overview, 30

¨ Flat Files, 31

¨ Tables, 36

¨ Viewing Data Objects, 39

¨ Editing Data Objects, 39

Data Objects OverviewData objects represent the metadata sources from which you want to extract metadata to analyze in an Analysttool project. You can import data objects such as tables and flat files to analyze the structure of the data in aproject.

Data objects appear when you select the project or folder that contains the object in the Analyst tool. Any table orflat file that you add to a project in the Analyst tool also appears in the Developer tool. A table appears under thename of the connection for the table. A flat file appears with the file object name.

Logical data objects created in Data Object Models in the Developer tool appear as logical data objects in projectsshared by the developer in the Analyst tool. These appear as Logical Data Objects in the Analyst tool. You cannotrename, move, or delete logical data objects. You can view logical data objects and create profiles and scorecardsfor logical data objects.

SAP and mainframe data objects imported in the Developer tool appear as SAP and mainframe tables in projectsshared by the developer in the Analyst tool. You can view SAP and mainframe tables and create profiles andscorecards for these tables.

A developer can add parameters to relational table or flat file data objects in the Developer tool. You can view theparameterized data objects in the Analyst tool after the developer shares these data objects with the Analyst tool.You can preview data in the parameterized data objects and profile data for these objects.

Use table and flat file objects to profile source data and perform data analysis tasks. You can add data objects byimporting them into the Analyst tool. You can store data objects in projects and folders in the Navigator.

Before you can import a data object you must access the metadata source to extract the metadata that youanalyze in the data object. The Analyst tool requires a connection to the source relational table to extract metadatafor the table data object. The Analyst tool requires the network path or browse location to locate the source flat fileto extract metadata for the flat file data object.

30

After you add tables and files, you can create a profile for the source data that the tables and files represent.When you run the profile, the Analyst tool connects to the database table or flat file.

You can perform the following tasks on data objects :

¨ Add data objects. Add tables and flat files by importing tables and flat files into projects and folders in theNavigator.

¨ View data objects. View object properties and column metadata for tables, flat files, and logical data objects.

¨ Duplicate data objects. Duplicate tables and flat files to use them for different tasks.

¨ Rename data objects. Rename tables and flat files according to their business usage and naming convention.

¨ Move data objects. Move tables and flat files in a project or folders in a project.

¨ Delete data objects. Delete tables and flat files when they become redundant.

Note: If you delete a data object that other object types reference, the Analyst tool displays a message thatlists the object types being referenced. Determine the impact of deleting the data object before you choose todelete it.

¨ Edit data objects. Edit tables and flat files to change the name or description while viewing tables and flat files.

Flat FilesA flat file data object contains the metadata for a flat file in the Analyst tool. Use flat files to profile source data.When you add a flat file, the Analyst tool connects to the network path location or the location where you uploadthe source flat file to extract metadata.

You can add flat files in the Analyst tool by importing the flat files into projects or folders. Before you import a flatfile, you can choose to browse a file from your local machine. The Analyst tool uploads a copy of the flat file to adirectory in the Informatica Services installation directory that the Analyst tool can access. Or, you can point theAnalyst tool to a network location. The Analyst tool uses the location you specify to access the source flat file.

You can specify the directory where you upload flat files in the flat file cache when you configure the AnalystService in the Administrator tool. For more information about specifying the flat file cache, see the InformaticaAdministrator Guide.

You can import parameterized flat files into the Analyst tool. A developer can add parameters to flat files in theDeveloper tool, or to flat files in the Analyst tool that are shared with the Developer tool. The developer cannot addparameters to uploaded flat files.

Use the Add Flat File Wizard to import flat files into the Analyst tool. To add a flat file in the Analyst tool, selectthe flat file, configure the file options, and configure the column data types. After you add the flat file, you canpreview the flat file properties and column metadata in the flat file.

After you import a flat file, the Analyst tool infers the Numeric or String datatypes for flat file columns based on thefirst 10,000 rows.

Flat File OptionsWhen you import a flat file, you can configure the flat file options for each column in Add Flat File wizard. Theoptions that you configure determine how the wizard reads the data from the source flat file.

Flat Files 31

The following table describes the flat file options that you configure the in the Add Flat File wizard:

Options Description

Delimiters Character used to separate columns of data. Use the Otherfield to enter a different delimiter. Delimiters must be printablecharacters and must be different from the escape characterand the quote character if selected. You cannot select non-printing multibyte characters as delimiters.

Text Qualifier Quote character that defines the boundaries of text strings.Choose No Quote, Single Quote, or Double Quotes. If youselect a quote character, the wizard ignores delimiters withinpairs of quotes.

Column Names Option to import column names from the first line. Select thisoption if column names appear in the first row. The wizarduses data in the first row in the preview for column names. Ifthe first row contains numeric characters, the wizard usesCOLUMNx as the default column name. If the first rowcontains special characters, the wizard converts the specialcharacters to underscore and uses the valid characters in thecolumn name. The wizard skips the following specialcharacters in a column name: ".+-=~`!%^&*()[]{}'\";:?,< >\\|\t\r\n. Default is not enabled.

Values Option to start value import from a line. Indicates the rownumber in the preview at which the wizard starts readingwhen it imports the file.

Flat File DatatypesWhen you import a flat file, you can configure the datatypes for the data in each column in the Add Flat Filewizard. The datatypes you configure determine how the wizard imports the data from the source flat file.

You can configure the following data types for the data in each column in the Add Flat File wizard:

¨ bigint. You can specify the format in the Numeric Format window. You can use the default or specify anothernumeric format and choose to make this the default numeric format.

¨ datetime. You can specify the format in the Datetime Format window. You can use the default or specifyanother datetime format and choose to make this the default datetime format.

¨ double. You can specify the format in the Numeric Format window. You can use the default or specify anothernumeric format and choose to make this the default numeric format.

¨ int. You can specify the format in the Numeric Format window. You can use the default or specify anothernumeric format and choose to make this the default numeric format.

¨ nstring. You cannot specify a format.

¨ number. You can specify the format in the Numeric Format window. You can use the default or specifyanother numeric format and choose to make this the default numeric format.

¨ string. You cannot specify a format.

Datetime DatatypesWhen you import a flat file, you can configure the datatypes for file columns in the Add Flat File wizard. When youconfigure the datetime dataype, you can specify the format in the Datetime Format window. You can use thedefault or specify another datetime format and choose to make this the default datetime format.

32 Chapter 4: Data Objects

The following table describes the datetime format strings to specify as part of the date:

Format String Description

AM, a.m., PM, p.m. Meridian indicator. Use any of these format strings to specifyAM and PM hours. AM and PM return the same values as doa.m. and p.m.

DAY Name of day, including up to nine characters (for example,Wednesday). The DAY format string is not case sensitive.

DD Day of month (1-31).

DDD Day of year (001-366, including leap years).

DY Abbreviated three-character name for a day (for example,Wed). The DY format string is not case sensitive.

HH, HH12 Hour of day (1-12).

HH24 Hour of day (0-23), where 0 is 12AM (midnight).

J Modified Julian Day.

MI Minutes (0-59).

MM Month (01-12).

MONTH Name of month, including up to nine characters (for example,August). Case does not matter.

MON Abbreviated three-character name for a month (for example,Aug). Case does not matter.

MS Milliseconds (0-999).

NS Nanoseconds (0-999999999).

RR Four-digit year (for example, 1998, 2034). Use when sourcestrings include two-digit years.

SS Seconds (0-59).

SSSSS Seconds since midnight.

US Microseconds (0-999999).

Y The current year with the last digit of the year replaced withthe string value.

YY The current year with the last two digits of the year replacedwith the string value.

Flat Files 33

Format String Description

YYY The current year with the last three digits of the year replacedwith the string value.

YYYY Four digits of a year. Do not use this format string if you arepassing two-digit years. Use the RR or YY format stringinstead.

Adding a Delimited Flat FileWhen you import a delimited flat file to a project or folder, you can configure the delimited format properties, suchas code page and delimiters. You can change column attributes to match the data preview.

1. In the Navigator, select the project or folder that you want to add the flat file to.

2. Click Actions > New > Flat File.

The Add Flat File wizard appears.

3. Specify a location to import the flat file.

¨ Select Browse and Upload and click Browse to select the flat file and click Upload to upload it to themachine on which Informatica Analyst runs.

¨ Select Enter a Network Path and configure the path and file name of the file.

4. Click Next.

If you chose to upload the file, Informatica Analyst uploads the flat file to an Informatica Services installationdirectory that Informatica Analyst can access. The Choose type of import panel displays Delimited andFixed-width options. The default option is Delimited.

5. Configure the flat file options, and preview the flat file data.

Note: Select a code page that matches the code page of the data in the file.

6. Optionally, click Show to preview changes to the flat file data.

7. Click Next.

8. Optionally, change the Column Attribute to a column name that describes the data in the source column.

9. Click Next.

10. Configure the name, description, and the location in the Folders panel where you want to add the flat file.

The Flat Files panel displays the flat files that exist in a folder.

11. Click Finish.

The Analyst tool adds the flat file to the project or folder in the Navigator.

Adding a Fixed-width Flat FileWhen you import a fixed-width flat file to a project or folder, you can configure the fixed-width properties such ascode page and column breaks.

1. In the Navigator, select the project or folder that you want to add the flat file to.

2. Click Actions > New > Flat File.

The Add Flat File wizard appears.

3. Specify a location to import the flat file.


¨ Select Browse and Upload and click Browse to select the flat file and click Upload to upload it to themachine on which Informatica Analyst runs.

¨ Select Enter a Network Path and configure the path and file name of the file.

4. Click Next.

If you chose to upload the file, Informatica Analyst uploads the flat file to an Informatica Services installationdirectory that Informatica Analyst can access. The Choose type of import panel displays Delimited andFixed-width options. The default option is Delimited.

5. Select Fixed-width.

6. Click Next.

The fixed-width properties page appears.

7. Configure the flat file properties.

8. Optionally, click Show to preview changes to the flat file data.

9. To set a column break, click within the Preview panel. To remove a column break, double-click the columnbreak. To move column breaks, drag them.

Optionally, click Edit Breaks and use the Edit Breaks dialog box to manage column breaks.

10. Click Next.

11. Optionally, change the Column Attribute to a column name that describes the data in the source column.

12. Click Next.

13. Configure the name, description, and the location in the Folders panel where you want to add the flat file.

The Flat Files panel displays the flat files that exist in a folder.

14. Click Finish.

The Analyst tool adds the flat file to the project or folder in the Navigator.

Synchronizing a Flat File Data ObjectYou can synchronize the changes to an external flat file data source with its data object in Informatica Analyst.Use the Synchronize Flat File wizard to synchronize the data objects.

1. In the Contents panel, select a flat file data object.

2. Click Actions > Synchronize.

The Synchronize Flat File dialog box appears in a new tab.

3. Verify the flat file path in the Browse and Upload field.

4. Click Next.

A synchronization status message appears.

5. When you see a Synchronization complete message, click OK.

The message displays a summary of the metadata changes made to the data object. To view the details ofthe metadata changes, use the Properties view.

Flat Files 35

Rules and Guidelines for Flat FilesUse the following rules and guidelines while working with flat files:

¨ Upload small files. Use the option to upload small files to an Informatica Services installation directory on themachine where the Analyst tool runs. The Analyst tool accesses this location to extract flat file metadata thatdoes not change frequently. When you use small files of sizes up to 10MB, the Analyst tool accesses a copy ofthe file in the Informatica Services installation directory. If you modify the original file, you need to upload thefile again.

¨ Upload large files. Use the option to enable the Analyst tool to connect to a network path location for largefiles. The Analyst tool accesses this location to extract flat file metadata that changes frequently. The networkpath location should be a shared directory or file system that the Analyst tool can access. When you use largefile sizes greater than 10MB, the Analyst tool can connect to the flat file in the network path. If you modify theoriginal flat file, you must refresh the flat file in the Analyst tool. Refreshing metadata for a large flat file cantake time.

¨ Blank data rows. The Analyst tool does not import the blank rows above the first data row, blank middle rows,and blank rows after the last data row when importing a flat file.

¨ Previewing data. After a preview, you can change the row number at which the Add Flat File wizard startsreading when it imports the file. This row number corresponds with the preview. If you choose to import columnnames from the first line, refresh the preview to update the row numbers for the preview data.

TablesA table object contains the metadata for a relational database source in the Analyst tool. Use tables to profilesource data. When you add a table, the Analyst tool uses a database connection to connect to the sourcedatabase to extract metadata.

You can add tables in the Analyst tool by importing the tables into projects or folders. Before you import a table,you select or create a database connection and select the database table that you want to add. You can addmultiple tables from a connection as data objects. You can also search for a table or table schema when youimport a table.

Use the Add Table wizard to add a table to the project or folder.

You can use the database connection that the staging database uses to select a table. You can create anotherdatabase connection to connect to the source table when you import a table. An administrator creates theconnection to the staging database that stores bad record or duplicate record tables for the Analyst tool beforeconfiguring the Analyst Service. For more information about configuring the staging database, see the InformaticaAdministrator Guide.

Database Connection PropertiesYou can use the database connection that the staging database uses to select a table. When you import a table,you can create another database connection to connect to the source relational table. You can delete redundantdatabase connections.


The following table describes the database connection properties that you can configure for a database connection:


Name Name of the connection. The name is not case sensitive and must be unique within the domain. It cannotexceed 128 characters, contain spaces, or contain the following special characters:~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /

ID String that the Data Integration Service uses to identify the connection. The ID is not case sensitive. Itmust be 255 characters or less and must be unique in the domain. You cannot change this property afteryou create the connection. Default value is the connection name.

Description Description of the connection.

Database Type Type of relational database. You can select an Oracle, Microsoft SQL Server, or IBM DB2 database.

User Name User name used for authentication when you connect to the relational database.

Password Password for the database user name.

Connection String Connection string used to access data from the database.IBM DB2: <database name>Microsoft SQL Server: <server name>@<database name>ODBC: <data source name>Oracle: <database name listed in TNSNAMES entry>

Data AccessConnection String

JDBC connection URL used to access metadata from the database.IBM DB2: jdbc:informatica:db2://<host name>:<port>;DatabaseName=<database name>ODBC: n/aOracle: jdbc:informatica:oracle://<host_name>:<port>;SID=<database name>Microsoft SQL Server: jdbc:informatica:sqlserver://<host name>:<port>;DatabaseName=<database name>

Code Page Code page use to read from a source database or write to a target database or file.

Adding a TableUse the Add Tables wizard to add a table to a project. Add the tables that you want to profile data for. To add atable, select or create a connection, select the schema and tables, and add the table.

1. In the Navigator, select the project or folder that you want to add the table to.

2. Click Actions > New > Table.

The Add Tables wizard appears.

3. Select a connection.

4. Optionally, click Manage Connections to create and configure a connection.

5. In the Manage Connections window, click the New Connection icon to configure a connection.

6. Configure the database connection properties.

7. Choose to create a simple or advanced connection.

8. Configure the additional database connection properties and click OK.

9. Click Close.

Tables 37

10. Optionally, unselect Show Default Schema Only to show all schemas associated with the selectedconnection.

11. Select the table that you want to add or enter a table name in the Tables search box and click Go to searchby table name. Click Clear to remove the search results and display all tables.

12. Optionally, enter a table schema name in the Schema search box and click Go to search by table schemaname. Click Clear to remove the search results and display all schemas.

13. Optionally, click the Properties View to view the properties and column metadata for the table. Or, click theData Preview View to view the columns and data for the table.

14. Click Next.

The wizard displays the table to add to your folder or project.

15. Click Finish.

Synchronizing a Relational Data ObjectYou can synchronize the changes to an external relational data source with its data object in Informatica Analyst.External data source changes include adding, changing, and removing columns and changes to rules.

1. In the Contents panel, select a relational data object.

2. Click Actions > Synchronize.

A message prompts you to confirm the action.

3. To complete the synchronization process, click OK. Click Cancel to cancel the process.

If you click OK, a synchronization status message appears.

4. When you see a Synchronization complete message, click OK.

The message displays a summary of the metadata changes made to the data object. To view the details ofthe metadata changes, use the Properties view.

Rules and Guidelines for TablesUse the following rules and guidelines while working with tables:

¨ The Analyst tool displays the first 100 rows by default when you preview the data for a table. The Analyst toolmay not display all the data columns in a wide table.

¨ The Analyst tool can import wide tables with more than 30 columns for profiling data. When you import a widetable, the Analyst tool does not display all the columns in the data preview. The Analyst tool displays the first30 columns in the data preview. However, you can include all the columns in the wide tables and flat files forprofiling.

¨ You can import tables and columns with lowercase and mixed-case characters.

¨ You can import tables that have special characters in the table or column name. When you import a table thathas special characters in the table or column name, the Analyst tool converts the special character to anunderscore character in the table or column name. You can use the following special characters in table orcolumn names:

" $ . + - = ~ ` ! % ^ & * ( ) [ ] { } ' \ " ; : / ? , < > \ \ | \ t \ r \ n¨ You can import tables and columns with Microsoft SQL92 or Microsoft SQL99 reserved words such as "concat"

into the Analyst tool.

¨ You can use an ODBC connection to import Micorsoft SQL Server, MySQL, Teradata, and Sybase tables in theAnalyst tool. The OBDC connection requires a user name and password.


¨ When you use a Microsoft SQL Server connection to access tables in a Microsoft SQL Server database, theAnalyst tool does not display the synonyms for the tables.

¨ When you preview relational table data from an Oracle, IBM DB2, IBM DB2 for zOS, IBM DB2/iOS, MicrosoftSQL Server, and ODBC database, the Analyst tool cannot display the preview if the table, view, schema,synonym, and column names contain mixed case or lower case characters. To preview data in tables thatreside in case sensitive databases, set the Support Mixed Case Identifiers attribute to true in the connectionsfor Oracle, IBM DB2, IBM DB2 for zOS, IBM DB2/iOS, Microsoft SQL Server, and ODBC databases in theDeveloper tool or Administrator tool.

¨ You can view comments for the source database table after you import the table into the Analyst tool. To viewsource table comments, use an additional parameter in the JDBC connection URL used to access metadatafrom the database. In the Metadata Access String option in the database connection properties, useCatalogOptions=1 or CatalogOptions=3. For example, use the following JDBC connection URL for an Oracledatabase connection:

Oracle: jdbc:informatica:oracle:// <host_name>:<port>;SID=<database name>;CatalogOptions=1

Viewing Data ObjectsView data objects to preview data object properties and column metadata.

1. In the Navigator, select the project or folder that contains the table or file data object.

2. Click Actions > Open to open the data object.

The data object appears in a new tab. The Analyst tool retrieves the first 100 rows for the data object anddisplays it on the Data Preview view.

3. Optionally, select Columns and select a column to include in the preview. Default includes all columns forpreview.

If you choose not to include a column, the Analyst tool refreshes the preview and does not include the columnin the preview.

4. Optionally, click the Properties view to view the table and file properties in the Properties panel.

The Analyst tool displays the table name, description, location, connection name, and database schema namefor the table data object. The Analyst tool displays the file name, location, upload file path, or network path forthe flat file data object.

5. Optionally, view the column metadata for each column in the Columns panel.

You can view column name and datatype for each column in the table or flat file. You can view if the column isnullable and the key for each column in the table. Nullable and key properties are relational databaseproperties.

6. Optionally, click the Refresh button to refresh the metadata for the data object.

Editing Data ObjectsYou can edit the name and description properties of tables and flat files while viewing the tables and flat files.

1. In the Navigator, select the project or folder that contains the table of flat file data object you want to edit.

Viewing Data Objects 39

2. Click Actions > Open to open the data object.

The data object opens in a new tab.

3. Click the Properties view to view the table or flat file properties in the Properties panel.

4. Click Actions > Edit to edit the data object.

The Edit window appears.

5. Enter a name and an optional description.

6. Click OK.


C H A P T E R 5

Mapping SpecificationsThis chapter includes the following topics:

¨ Mapping Specification Overview, 41

¨ Mapping Specification Example, 42

¨ Mapping Specification Types, 43

¨ Column Mapping View, 44

¨ Properties View, 44

¨ Data Preview View, 46

¨ SQL Query View, 46

¨ Profile Summary View, 47

Mapping Specification OverviewA mapping specification describes the movement and transformation of data from a source to a target. Use amapping specification to define business logic that populates a target with data. You can then leverage that targetto report on the data.

You can add aggregators, filters, joins, lookups, rules, and sources to a mapping specification. You can edit theaggregators, filters, joins, lookups, rules, and target in a mapping specification.

After you develop the mapping specification, you can perform the following tasks:

¨ Run a column profile on the mapping specification source and target to analyze the structure and quality ofdata.

¨ Run a SQL query against source or target columns in a mapping specification and view the query results in adata preview.

¨ Load the results of the mapping specification to a relational or flat file target.

¨ Export the mapping specification logic to Microsoft Excel to document and share the mapping specificationlogic with other analysts and developers.

¨ Export the mapping specification logic to PowerCenter to share the mapping specification logic with aPowerCenter developer.

¨ Export the mapping specification logic as a virtual table that analysts and developers can use to run SQLqueries against the data.

41

Analyst and Developer CollaborationAnalysts and developers can collaborate to develop the business logic for a mapping specification.

In the Developer tool, the developer views the mapping specification as a logical data object. The logical dataobject is read-only. The developer can edit a copy of the logical data object. If the developer deletes the logicaldata object in the Developer tool, the corresponding mapping specification is deleted from the Analyst tool.

The analyst can view the logical data object that the developer edits in the Analyst tool. The analyst can use thislogical data object as a source for a mapping specification.

The developer can create a mapping that uses the logical data object in the Developer tool to load the mappingspecification results to a target. Or, the analyst can use the mapping specification in the Analyst tool to load themapping specification results to a target.

In PowerCenter, a developer views the mapping specification as a mapplet or a mapping. The Analyst tool exportprocess creates a mapplet if the analyst does not select a target and a mapping if the analyst selects a target forthe mapping specification during export.

If the Analyst tool export process creates a mapplet in PowerCenter, the developer can use the mapplet as asource in a mapping. If the Analyst tool export process creates a mapping in a non-reusable session in a workflow,the developer can create connection objects and run the workflow.

In the Administrator tool, analysts and developers view the mapping specification as a virtual table after theanalyst exports the mapping specification logic as a virtual table. Analysts and developers can run SQL queriesagainst the data in the virtual table.

Mapping Specification ExampleAs an analyst, you can develop business logic that can populate a target table with the current balance for eachbranch in a financial organization. You can export this business logic to PowerCenter to share it with aPowerCenter developer. You can export this business logic to a virtual table to run SQL queries against the data inthe virtual table.

Use the following high-level steps to generate current balance data for active customer accounts for a set offinancial products in the target table:

1. You can create a mapping specification named Customer_Data.

2. You can select customer tables for accounts and products and perform a normal join to display customeraccounts that have purchased a financial product.

3. You want the target table in the mapping specification to have the same structure as the Current_Balancetable that is in the Model repository. You can select the Current_Balance table as the target for the mappingspecification when you create the mapping specification.

4. You want to view data for active accounts in the mapping specification. You can add a simple filter to themapping specification to hide the inactive accounts and display the active accounts. You can add thefollowing simple filter condition:

Customer_Accounts.Status = 'Active'5. You can preview the data in the mapping specification. The data contains active customer accounts for the

checking, savings, and money market product categories. You want to view data for the savings and moneymarket product categories. You can collaborate with a developer to create an advanced filter for the mappingspecification. The mapping specification appears as a logical data object in the Developer tool. The developer

42 Chapter 5: Mapping Specifications

copies the logical data object and edits it to add a filter condition that displays customer accounts for thesavings and money market product categories. The developer adds the following advanced filter condition:

Customer_Products.Category = 'Savings' OR Customer_Products.Category = 'Money_Market'6. You can view the logical data object that contains the advanced filter condition as a logical data object in the

Analyst tool. You can add it as a source to the mapping specification.

7. You can edit the Current_Balance target table to add a rule that sums the balances from the savings andmoney market product categories.

8. You can preview the data in the mapping specification and load the results of the mapping specification to atarget table that matches the structure of the Current_Balance target table in the mapping specification.

9. You can choose to export the mapping specification logic to PowerCenter. You can select a target in theModel repository to share the mapping specification logic with a PowerCenter developer.

10. You can choose to export the mapping specification logic as a virtual table that appears in a virtual databasein the Administrator tool. You can run SQL queries against the data in the virtual table.

Mapping Specification DevelopmentDevelop a mapping specification to define the business logic that transforms data from source to target. After youdevelop the mapping specification, you can load the results of the mapping specification to a target or export themapping specification results or logic to share with other analysts or developers.

Complete the following steps to develop a mapping specification:

1. Create a mapping specification.

2. Configure the mapping specification to add aggregators, filters, joins, lookups, rules, and sources and edit theaggregators, filters, joins, lookups, rules, and target.

3. Validate the mapping specification.

4. Preview the mapping specification results.

5. After you develop a mapping specification, you can complete the following steps:

¨ Share the mapping specification with a developer.

¨ Load the results of the mapping specification to a target.

¨ Export the mapping specification logic as documentation to Excel.

¨ Export the mapping specification logic to PowerCenter.

¨ Export the mapping specification logic as a virtual table.

Mapping Specification TypesYou can create different types of mapping specifications based on the business logic you want to develop.

You can create the following types of mapping specifications:Mapping specification with no target

You can create a mapping specification with a source or multiple sources and no target during the initialphase of mapping specification development. The mapping specification is not valid and you cannot preview itor load the results of the mapping specification to the target. However, you can edit the mapping specificationto configure the target and validate it.

Mapping Specification Types 43

Mapping specification with multiple sources

You can create a mapping specification with two or more sources and a target. When you use multiplesources you must specify a join condition for the sources.

Mapping specification with another mapping specification as a source

You can create a mapping specification that uses another mapping specification as a source. Duringincremental development of a mapping specification, you may need to configure complex filters and rules.You can create separate mapping specifications to break down the complex logic. You can add each mappingspecification as a source to develop the logical flow.

Column Mapping ViewWhen you select or create a mapping specification, it opens in another tab. Create and develop a mappingspecification on the Column Mapping view of the tab.

The following table describes the mapping specification properties that appear on the Column Mapping view:

Property Panel Description

Source Column Sources Lists source table name and column names.

Transformation Transformationsand TargetColumns

Lists which source column has a relationship with a target column. Listswhich source, rule, aggregator, lookup, and join column has a relationshipwith a target column.

TransformationDescription

Transformationsand TargetColumns

Description of a row in the target table.

Target Column Mapping Target column name.

Properties ViewView the properties for a mapping specification on the Properties view. The Properties view also appears as aview on the bottom panel of the Column Mapping view.

The following table describes the mapping specification properties that appear on the Properties panel:


Name Name of the mapping specification.

Type Object type. Displays Mapping Specification for a mapping specification.

Description Description of the mapping specification.

Location Location of the project or folder that contains the mapping specification.



Created on Date that the mapping specification was created.

Created by Name of the user who created the mapping specification.

Source columns Source tables used in the mapping specification.

Target columns copied from Data object used to create the target columns.

Last modified on Date that the mapping specification was last modified.

Last modified by Name of the user who last modified the mapping specification.

Job Status Displays the status of the load operation that loads the results of the mappingspecification to the target.

Last loaded to target Displays the date that the mapping specification results were last loaded to the target.

Last target loaded Displays the last target that the mapping specification results were loaded to.

PowerCenter folder Displays the folder in PowerCenter where the mapping specification was exported.

Target object Type of target that the data in the mapping specification was loaded to.

Tags Lists tags used in the mapping specification.

Virtual database Virtual database name for the mapping specification exported as a virtual table.

Virtual table Virtual table name for the mapping specification exported as a virtual table.

JDBC URL JDBC URL for the mapping specification exported as a virtual table.

Last Loaded Date the mapping specification logic was last exported as a virtual table.

The following table describes the mapping specification property that appears on the Where Used panel:


Where Used Lists where objects in the mapping specification are used in other projects. Lists themapping specification name that is used as a source.

The following table describes the mapping specification properties that appear on the Target Columns panel:


Target Name Target column name.

Datatype Target column datatype.

Precision Target column precision.

Scale Target column scale.

Properties View 45


Nullable Property for a relational database column that determines if the column can containnull values.

Key Key column in the target.

The following table describes the mapping specification properties that appear on the Rules panel:


Rules Rule column name. Displays input and output column names.

Column Rule column name.

Datatype Rule column datatype.

Precision Rule column precision.

Scale Rule column scale.

Data Preview ViewView the results of a mapping specification or the data in a mapping specification source or target on the DataPreview view.

The Data Preview view appears in the following locations in the Analyst tool interface:

¨ On the Column Mapping view in a mapping specification.

¨ On tabs for mapping specification objects in the Edit Mapping Specification window.

¨ On sources and target selections in the New Mapping Specification window.

You can preview the results for the business logic that you apply to a mapping specification during mappingspecification development.

When you edit a mapping specification, you can preview the data for the mapping specification objects that youadd or edit. The Analyst tool previews the data in the mapping specification target. After you preview the results ofthe mapping specification, you can load the results to a target.

When you create a mapping specification, you can preview the data in the sources and target you select. Whenyou select a transformation object and perform a data preview, the Analyst tool returns a data preview for thetransformation object and any transformation objects added before this object.

SQL Query ViewYou can preview the results of an SQL query on the SQL Query view.

You can view and edit existing SQL queries. You can add SQL queries to a mapping section. The SQL Queryview displays the results of an SQL query as a data preview.


You can click icons on the view to display the SQL query used in the mapping specification, edit the SQL query inan editor, and preview the data in the SQL query.

Profile Summary ViewYou can view the profile summary for profiled source or target, and the values, patterns, and statistics for eachprofiled column on the Profile Summary view.

Use the Profile Summary view to run a column profile on a mapping specification source or target.

The following table describes the tooltip and icons that appear on the Profile Summary view:

Icon Description

Profile Summary The profile summary describes the profile results such as the number of unique and null valuesexpressed as a number and percentage.

Sampling policy icon The Analyst tool sampling policy for the profiled object. The Analyst tool displays the samplingpolicy for the object when you mouse over the icon.

View details icon View the values, patterns, and statistics for each profile result.

Refresh icon Run the column profile again.

Profile Summary View 47

C H A P T E R 6

Mapping SpecificationConfiguration


¨ Mapping Specification Configuration, 48

¨ Creating a Mapping Specification, 49

¨ Editing a Mapping Specification, 49

¨ Map Source and Target Columns, 50

¨ Finding Columns, 50

¨ Removing Column Relationships, 51

¨ Mapping Specification Validation, 51

¨ SQL Query, 52

Mapping Specification ConfigurationAfter you create a mapping specification, you can configure the objects that you want to use in the mappingspecification.

After you add objects to the mapping specification, you can edit the objects in the mapping specification. You canadd sources, rules, filters, lookups, or joins to a mapping specification.

You can add a virtual target to a mapping specification. If you create a mapping specification without a target, theAnalyst tool creates an empty target. You can edit the target to configure the target fields. You can validate themapping specification to verify that the mapping specification has no errors.

After you add objects to a mapping specification, the Analyst tool maps a relationship from the object columns tothe target columns. You can remove the relationship between the columns.

You can also run an SQL query against source or target columns in a mapping specification to view the queryresults in a data preview.

48

Creating a Mapping SpecificationCreate a mapping specification as a container for the business logic that transforms and moves data from sourceto target.

Before you create a mapping specification, verify that the sources you want to use exist in a project.

1. In the Navigator, select a project to create the mapping specification.

2. Click Actions > New > Mapping Specification.

The New Mapping Specification window appears.

3. Enter a unique name and an optional description.

4. Select the folder where you want to create the mapping specification.

5. Click Next.

6. On the Sources panel, click the Add Source Object icon and click each checkbox to add one or moresources for the mapping specification.

The Add Source Object window appears.

7. On the Source Object panel, select a source or multiple sources.

8. Optionally, select a source and click Data Preview to preview the source data.

9. Optionally, select a source and click Properties to view the source properties.

10. Click OK, and then click Next.

11. If you selected multiple sources, click the New Join icon to create a join and select the edit options toconfigure the join.

12. Click OK, and then click Next.

13. Choose to use a virtual target or a target from the Target Object panel.

¨ Use a virtual target if you do not know the structure of the target data object.

¨ Use a target from the Target Object panel if you know the structure of the data object. If you load themapping specification results to a table, the structure of this target must match the structure of the targettable.

14. Optionally, select a target and click Data Preview to preview the target data.

15. Optionally, select a target and click Properties to view the target properties.

16. Click Finish.

Editing a Mapping SpecificationEdi the mapping specification to configure the mapping specification rules, filter, transformation objects, and target.

1. Click Actions > Edit > General.

The Edit Mapping Specification window appears.

2. Optionally, edit the name and description for the mapping specification.

3. Optionally, click the Sources, Joins, Lookups, Rules, Filter, Aggregator, or Target tabs and configure theedit options.

4. Click Save.

Creating a Mapping Specification 49

Map Source and Target ColumnsThe Analyst tool can map source and target columns based on column names and column positions. The Analysttool can also map columns based on advanced criteria that you enter for column names and column positions. Youcan also select each source and target column to map the columns.

Use the Advanced mode in the Automap window to enter the column mapping criteria.

When you map by column name, the Analyst tool ignore source and target prefixes and suffixes. For example,map ACCOUNTS_PAID to ACCOUNTS.

When you map by column position, the Analyst tool maps the first or last source column with the target column youselect. For example, map the first source column ACCOUNTS_PAID to the target column ACCOUNTS.

Mapping Source and Target Columns by Name or PositionAutomatically map source and target columns based on naming conventions and column positions.

1. On the Sources panel, click the Automap Columns icon.

The Automap window appears.

2. Choose to map columns in simple or advanced mode.

¨ To map columns in the simple mode, select Simple.

¨ To map columns in the advanced mode, select Advanced and choose to map columns by name or columnposition.

In the Simple mode, the Analyst tool maps columns with the same name or position. In the Advanced mode,the Analyst tool maps columns based on either name or position.

3. Optionally, on the Transformation and Target Columns panel, click Show to update the mappingspecification with mapped columns.

4. Click Save.

Mapping to Selected ColumnsYou can select each source column to map it to a target column in the mapping specification.

1. On the Sources panel, select a source column.

2. On the Transformations and Target Columns panel, select a target column.

3. Click the Map to Selected Columns icon between the Sources and the Transformations and TargetColumns panels.

Finding ColumnsSearch for columns in a mapping specification to find columns that you want to edit or add to objects.

50 Chapter 6: Mapping Specification Configuration

u On the Column Mapping view, click the Find icon to find objects. The following table describes the choicesfor objects that you can find:

Option Description

Source Columns On the Sources panel, enter a source column name.

Target Columns On the Transformations and Target Columns panel, enter a target column name.

Transformations Columns On the Transformations and Target Columns panel, enter a transformation columnname.

Transformations Descriptions On the Transformations and Target Columns panel, enter a description fortransformation objects.

Removing Column RelationshipsWhen you add objects to a mapping specification, the Analyst tool maps a relationship between the objectcolumns and the target columns. You can remove the relationships between these columns.

1. On the Transformations and Target Columns panel, select a column from the Transformations panel.

2. Click Actions > Clear Transformation to remove the relationship for the column.

Mapping Specification ValidationValidate the mapping specification to verify that the mapping specification has no errors. You can validate amapping specification during different stages of the mapping specification development cycle. You must load avalid mapping specification to a target.

You can validate a mapping specification at the following stages of development:

¨ During the mapping specification development cycle.

¨ When you preview the results of the mapping specification.

¨ When you load the results of the mapping specification to the target.

¨ When you export the mapping specification logic to PowerCenter.

¨ When you export the mapping specification logic as a virtual table.

When a validation error occurs, the mapping specification is not valid. The Analyst tool cannot load the results ofthe mapping specification to the target, or export the mapping specification logic as a virtual table or toPowerCenter .

Validation Errors During Mapping Specification DevelopmentValidation errors might occur during mapping specification development.

Removing Column Relationships 51

The following validation errors can occur during the mapping specification development cycle:

¨ The mapping specification does not contain a target.

¨ The mapping specification contains expressions, rules, aggregators, filters, lookups, or joins that are not valid.

¨ The mapping specification contains a source that was deleted or modified in the Model repository.

¨ The mapping specification contains source and target column relationships that are not valid because ofincompatible datatypes.

Validation Errors During Data PreviewValidation errors might occur when you preview the results of a mapping specification.

The following validation errors can occur when you preview the results of a mapping specification:


¨ The mapping specification contains source and target column relationships that are not valid.

Validation Errors During a Load Operation to the TargetValidation errors might occur when you load the results of a mapping specification to the target.

The following validation errors can occur when you load the results of a mapping specification to the target:


¨ The mapping specification contains source and target column relationships that are not valid because ofincompatible datatypes.

¨ The structure and properties of the mapping specification target does not match the structure and properties ofthe target data object.

¨ The target data object does not exist in the Model repository.

¨ The database connection for the target data object contains incorrect database connection properties.

¨ The database connection for the target data object is deleted.

¨ You do not have permission to use the database connection for the target data object.

¨ The Data Integration Service for the Analyst Service is disabled or becomes disabled during the load operation.

¨ The Model Repository Service is disabled or becomes disabled during the load operation.

¨ The Mapping Service module for the Data Integration Service is not available.

¨ The source data object in the mapping specification is the same as the target data object to which you want toload the mapping specification results.

¨ The mapping specification contains Developer tool sources that are not valid.

SQL QueryRun an SQL query against source or target columns in a mapping specification to view the query results in a datapreview.

If a source contains a large number of columns, analysts can run an SQL query against select source columns toview the query results as a subset of the source data. Analysts can run an SQL query against target columns tovalidate the mapping specification logic before exporting the mapping specification as a virtual table.

52 Chapter 6: Mapping Specification Configuration

The Analyst tool adds the following default query to select all columns from the mapping specification target:

SELECT * from [MAPPING SPECIFICATION NAME]

Adding an SQL QueryAdd an SQL query to query the source or target data in a mapping specification.

1. On the Column Mapping view, click Actions > SQL Query.

The SQL Query window appears.

2. On the Columns panel, select a source or target column and click the arrow icon to add it to the SQL Queryeditor.

3. Click the SQL Query editor to modify the query.

4. Optionally, click the Validate icon to validate the SQL query.

5. Click Run SQL Query to run the SQL query.

Editing an SQL QueryEdit an SQL query to modify the query statement or to query another source or target column.

1. On the SQL Query view, click the Edit icon.

The SQL Query window appears.

2. Modify the SQL query in the SQL Query editor.

3. Click Run SQL Query to run and save the SQL query.

SQL Query 53

C H A P T E R 7

Mapping Specification ObjectsThis chapter includes the following topics:

¨ Mapping Specification Objects Overview, 54

¨ Mapping Specification Sources, 54

¨ Mapping Specification Target, 55

¨ Mapping Specification Aggregators, 56

¨ Mapping Specification Rules, 58

¨ Mapping Specification Filters, 60

¨ Mapping Specification Lookups, 61

¨ Mapping Specification Joins, 63

Mapping Specification Objects OverviewAdd objects to a mapping specification to perform data transformation operations. You must edit the mappingspecification to add and modify objects.

Add and edit mapping specification objects on the Column Mapping view. You can add sources, target columns,filters, rules, and transformation objects such as aggregators, lookups, and joins to a mapping specification.

You can add the following objects to a mapping specification:

¨ Aggregators

¨ Filters

¨ Joins

¨ Lookups

¨ Rules

¨ Sources

¨ Target columns

Mapping Specification SourcesWhen you create a mapping specification, you must add one or more sources to it.

54

When you add multiple source to a mapping specification, you must specify a join between the sources.

You can use Metadata Manager tables that you import into the Model repository as sources. You can use tables,flat files, logical data objects, social media objects, and mapping specifications as sources.

If an external source changes, you can synchronize the changes with corresponding source objects in a mappingspecification. After you synchronize the changes, the Analyst tool updates the mapping specification to match thechanges in the data object. You must open the mapping specification again to view the updated source.

You can search for source columns in the mapping specification. You can add source columns to the target, rules,filters, or joins. You can also automatically map source columns to target columns based on naming conventionsand column positions. You can drag multiple source columns to the target to insert between existing targetcolumns.

You can remove a source from the mapping specification. When you remove a source that is referenced by otherobjects, the Analyst tool displays a lists of referenced objects. If you remove the source that has referencedobjects, the mapping specification will not be valid.

Adding and Editing a SourceUse the Edit Mapping Specification window to add or edit a source. You can add multiple sources to a mappingspecification. Add sources to use additional data objects in the mapping specification. You can remove a sourcefrom a mapping specification.

1. On the Column Mapping panel, click Actions > Edit > Sources.


2. On the Sources panel, click the Add Source Object icon.

The Add Source Object window appears.

3. On the Source Object panel, click each checkbox to select a source or sources from a project.

4. Optionally, select a source and click Data Preview to preview the source.

5. Optionally, select a source and click Properties to view the source properties.

6. Click OK.

7. Optionally, select a source and click the Remove from Mapping Specification icon to remove it from themapping specification.

8. Click Save.

Mapping Specification TargetUse a target in the mapping specification to define the structure of the target data object.

You must know the structure of the target data object if you use a target in the mapping specification. If you do notknow the target structure, you can choose a virtual target. The Analyst tool creates an empty target in the mappingspecification. You can edit the mapping specification to configure the target.

After you finalize the mapping specification, you can load the mapping specification results to a target data objectthat matches the structure of the target in the mapping specification.

Note: The structure of the target columns in the mapping specification must match the structure of the columns inthe target table data object.

Mapping Specification Target 55

Mapping Specification Target DatatypesIf the target contains incompatible datatypes, you cannot load the results of the mapping specification to a targetor export the mapping specification logic to PowerCenter.

The following datatypes are compatible with the mapping specification target:

¨ Integer

¨ Bigint

¨ String

¨ Text

¨ Binary

¨ Decimal

¨ Double

¨ Datetime

Edit Options for TargetsWhen you edit the target in a mapping specification, you can select an edit option to edit it.

You can edit the target from the Transformations and Target Columns panel and select an edit target option toperform an edit task. You can select the edit options for the target on the Target tab of the Edit MappingSpecification window. You can also drag multiple source columns from the Sources panel to add to the target inthe Transformations and Target Columns panel.

You can move, edit, and delete target columns

After you edit the target, you can preview the data on the Data Preview tab and view the target properties on theProperties tab.

Editing the TargetEdit the target in a mapping specification to add target columns or modify the properties of the target columns.

1. To edit the target column values, click Actions > Edit > Target.


2. Select an edit target option to perform an edit task.

3. Optionally, click the Data Preview tab to preview the target data.

4. Optionally, click the Properties tab to view the target properties.

Mapping Specification AggregatorsAdd an aggregator to a mapping specification to perform aggregate calculations on multiple rows of data. You canadd multiple aggregate functions to the aggregator.

When you add an aggregator, you can perform aggregate calculations on groups of columns or all columns. Whenyou group by columns, you can apply the aggregate conditions and rules to multiple columns. You can includefilters, rules, conditional clauses, and nested expressions in an aggregator. You can also add different aggregatorsto multiple columns.

56 Chapter 7: Mapping Specification Objects

You can add, edit, or delete an aggregator. You can also preview data in an aggregator.

You can add the following types of aggregators:Simple aggregator

Aggregates data by applying conditions and rules to multiple columns. You can add lookup, rule, and sourcecolumns to the conditions in a simple aggregator.

Advanced aggregator

Aggregates data by applying aggregate functions and expressions to multiple columns. You can add lookup,rule, and source columns to the expression in a condition in an advanced aggregator.

Aggregator PropertiesConfigure aggregator properties when you add or edit an aggregator.

The following table describes the aggregator properties that you can configure:

Aggregator Properties Description

Functions Configure the following properties for aggregator functions:- Function. Type of aggregate function.- Aggregate Source Name. Source, lookup, or rule name for

the column on which to apply the aggregate function.- Aggregate Column Name. Source, lookup, or rule column

name on which to apply the aggregate function.- Target Column Name. Column name in the mapping

specification target that returns the results of the aggregatefunction.

Conditions Use aggregator conditions to reduce the number of rows inthe aggregator. Configure the source, lookup, rule column,operator, and value for an aggregator condition.

Functions and Conditions Configure the following properties for functions and conditions:- Expression. Expression in the aggregator that contains the

aggregate functions and conditions.- Target Column Name. Name of the target column that

contains the results of the aggregator.

Adding and Editing a Simple AggregatorAdd a simple aggregator to apply conditions and rules to aggregate data on columns. Edit a simple aggregator tomodify the conditions, rules, and group by columns.

1. Click Actions > Edit > Aggregator.


2. Choose to add or edit an aggregator.

¨ To add an aggregator, click the New Aggregator icon.

¨ To edit an aggregator, click the Edit icon.

3. To add or edit a simple aggregator, click Simple.

4. On the Functions panel, click the Add Rule icon and select the Function, Aggregate Source Name,Aggregate Column Name, and Target Column Name columns.

5. On the Conditions panel, select a column, operator, and enter a value to create a condition.

Mapping Specification Aggregators 57

6. Click Next.

7. Optionally, on the Columns panel, select the columns you want to group together to perform aggregatecalculations on groups of columns.

To select multiple columns press the Shift or Ctrl key and click each column.

8. Click the arrow icon to add the columns to the Group by panel.

9. Optionally, on the Data Preview panel, click Show to preview the data that is grouped together based onmatching values in the group by columns.

10. Click Finish and then click Save.

Adding and Editing an Advanced AggregatorAdd an advanced aggregator to apply conditions and expressions to aggregate data on columns. Edit anadvanced aggregator to modify the conditions, expressions, and group by columns.

1. Click Actions > Edit > Aggregator.


2. Choose to add or edit an aggregator.

¨ To add an aggregator, click the New Aggregator icon.

¨ To edit an aggregator, click the Edit icon.

3. To add or edit an advanced editor, click Advanced.

4. On the Functions and Conditions panel, click the Add Condition icon.

5. Select a target column name.

6. On the Functions tab, select a function, click the arrow icon, and select a column to add the function to theExpression editor.

7. Optionally, on the Rules tab, select a column and datatype and click the arrow icon to add the rule column tothe Expression editor.

8. Optionally, on the Lookup tab, select a column and datatype and click the arrow icon to add the Lookupcolumn to the Expression editor.

9. Click OK and then click Next.

10. Optionally, on the Columns panel, select the columns you want to group together to perform aggregatecalculations on groups of columns.

To select multiple columns press the Shift or Ctrl key and click each column.

11. Click the arrow icon to add the columns to the Group by panel.

12. Optionally, on the Data Preview panel, click Show to preview the data that is grouped together based onmatching values in the group by columns.

13. Click Finish and then click Save.

Mapping Specification RulesCreate a rule that defines the business logic for target columns in a mapping specification. When you create arule, you can add expression functions to the rule. Apply a rule to a mapping specification to add existing rule logicto target columns.


You can create a rule for a mapping specification or apply a rule to a mapping specification. After you create a rulefor a mapping specification, you can make it reusable. You can preview the results of the rule.

When you apply a rule to a mapping specification, the Analyst tool maps a relationship between the columns in therule to the columns in the target. You can remove the relationship from the rule columns to the target columns.However, the rule columns remain in the mapping specification. You can delete a rule from the mappingspecification. The Analyst tool removes the relationship from the rule columns to the target columns and deletesthe rule column from the mapping specification.

Applying a RuleApply a reusable rule to a target column in the mapping specification to apply the rule logic to the column. The rulemust exist in the Model repository.

1. On the Column Mapping view, click Actions > Edit > Rules.


2. Select the New Rule icon.

The New Rule window appears.

3. Select Apply a Rule.

4. Click Next.

5. In the Rules panel, select a reusable rule from a project or folder.

The Inputs and Outputs panels display the properties for the input and output columns for the rule.

6. Click Next.

7. Enter a rule column name.

8. Optionally, enter a description.

9. On the Inputs panel, select the input column for the rule.

10. On the Outputs panel, select a target column in the mapping specification.

11. Optionally, edit the Output Column Name.

12. Click Finish.

13. Click Yes in the message that appears to replace transformation objects and then click Save.

Creating a Mapping Specification RuleCreate a rule for a target column in a mapping specification to develop business logic for the column. When youcreate a rule, you configure the edit options for the rule. You can also choose to make the rule reusable.

1. On the Column Mapping view, click Actions > Edit > Rules.


2. Select the New Rule icon.

The New Rule window appears.

3. Select Create a Rule.

4. Click Next.


6. Enter a rule name.

7. Select a target column name to apply the rule to.

Mapping Specification Rules 59

8. To make the rule reusable, select Save the rule and select a project to save the rule.

9. On the Functions tab, select a function, click the arrow icon, and select a column to add the function to theExpression editor.

10. Optionally, on the Columns tab. select a target column and click the arrow icon to add it to the Expressioneditor.

11. Optionally, on the Rules tab, select a column and datatype and click the arrow icon to add the rule column tothe Expression editor.

12. Optionally, on the Lookup tab, select a column and datatype and click the arrow icon to add the Lookupcolumn to the Expression editor.

13. Click Finish.

14. Click Yes to replace the transformation object and click Save.

Mapping Specification FiltersAdd filters to a mapping specification to limit the data that appears in the mapping specification results. When youadd a filter, you can specify the filter conditions to use in the filter.

You can add the following types of filters:

¨ Simple filter. Applies to multiple values and operators on source columns.

¨ Advanced filter. Applies to expressions, functions, and rules on source columns.

Adding and Editing a Simple FilterAdd a simple filter to filter data by a fixed value on a column. After you add a simple filter, you can edit it to modifythe filter values and target columns.

1. To add or edit a filter, click Actions > Edit > Filter.


2. Chose to add or edit a filter.

¨ To add a filter, click the New Filter icon.

¨ To edit a filter, click the Edit icon.

The New Filter or Edit Filter icon appears.

3. Select Simple filter.

4. On the Condition panel, select a column, operator, and enter a value.

5. Optionally, on the Data Preview panel, click the Refresh icon to preview the data.

6. Click OK.

The Filter Properties panel displays the filter condition.

7. Optionally, click the Edit icon or the Delete icon to edit or delete the filter.

8. Click Save.


Adding and Editing an Advanced FilterAdd an advanced filter to filter data by multiple values on columns. After you add an advanced filter, you can edit itto modify the filter values and target columns.

Open the mapping specification to display the Field Mapping view.

1. Click Actions > Add > Filter.

The Edit Filter window appears.

2. Select Advanced Filter.

3. On the Functions tab, select a function, click the arrow icon and select a column, and click OK to add thefunction to the Expression editor.

4. Optionally, in the Columns tab, select a column and click the add icon to add the column to the Expressioneditor.

5. Select one of the following optional choices to perform a filter task:

¨ Optionally, on the Rules tab, select a rule and click the add icon to add the rule column to the Expressioneditor.

¨ Optionally, enter an expression in the Expression editor.

¨ Optionally, click Validate to validate the expression.

¨ Optionally, click Show to preview the data.

6. Click OK and Save.

Mapping Specification LookupsUse a lookup in a mapping specification to look up data in a data object. The Analyst tool queries the lookupsource based on the lookup inputs and a lookup condition.

You can use multiple lookups in a mapping specification. After you add a lookup, you can edit it.

You can perform a lookup on the following sources:

¨ Flat file

¨ Relational table

¨ Logical data object

¨ Reference table

When you add a lookup to a mapping specification, the lookup returns the result of lookup to the target column.You can configure the lookup to return a single row or multiple rows. You can edit the lookups that you add to amapping specification to modify how lookups are used in the mapping specification.

You can perform the following tasks with a lookup:

¨ Get a related value. Retrieve a value from the lookup based on a value in the source. For example, you canlook up an employee ID and return the employee name.

¨ Get multiple values. Retrieve multiple rows from a lookup. For example, you can look up a department costcenter and return all the employees in a department.

¨ Perform a calculation. Retrieve a value from a lookup and use it in a calculation. For example, you can look upa sales tax percentage, calculate a tax, and return the tax to a target column.

Mapping Specification Lookups 61

Lookup ConditionsWhen you configure a lookup condition, you compare the value of one or more columns in the source data withvalues in the lookup.

For example, the source data contains an employee_number. The lookup source table contains employee_ID,first_name, and last_name. You configure the following lookup condition:

employee_ID = employee_number

For each employee_number, the Analyst tool returns the employee_ID, last_name, and first_name column fromthe lookup.

The Analyst tool can return multiple rows from the lookup that match the lookup condition. You configure thefollowing lookup condition:

employee_ID > employee_number

The Analyst tool returns rows for all employee_ID numbers greater than the source employee number.

Lookup PropertiesConfigure lookup properties when you add or edit a lookup.

The following table describes the lookup properties that you can configure:

Lookup Properties Description

Name Lookup name.

Description Description of the lookup.

On multiple matches Determines which rows to return when the lookup findsmultiple rows that match the lookup condition. Select one ofthe following options:- Return first row. Returns the first row that matches the

lookup condition.- Return last row. Returns the last row that matches the

lookup condition.- Return any row. Returns any row that matches the lookup

condition.- Return all rows. Returns all rows that match the lookup

condition.- Report error. The Analyst tool reports an error and does

not return a row.

Lookup Condition Configure the following properties in a lookup condition:- Source Column Name. Name of the source column to

compare values with a lookup column .- Operator. Comparison operators for the lookup condition.- Lookup Column Name. Name of the lookup column to look

up values.

Output Configure the following output properties:- Lookup Column Name. Name of the lookup column to look

up values.- Target Column Name. Name of the target column to output

the results of the lookup.


Adding a LookupAdd a lookup to a mapping specification to look up data in a data object.

Before you add a lookup to a mapping specification, verify that the data source exists in a project in the Analysttool.

1. Click Actions > Edit > Lookups.


2. Click the New Lookup icon.

The New Lookup window appears.


4. Click Next.

5. On the Lookup Source panel, select a lookup from a project.

6. Optionally, click Data Preview to preview the lookup data.

7. Optionally, click Properties to view the lookup properties.

8. Click Next.

9. Enter the lookup conditions and properties.

10. Click Finish.

Editing a LookupEdit the lookups that you add to a mapping specification to modify how lookups are used in the mappingspecification.

1. Click Actions > Edit > Lookups.


2. Select a lookup and click the Edit icon.

The Edit Lookup window appears.

3. Enter the lookup conditions and properties.

4. Click Finish.

Mapping Specification JoinsWhen you use more than one source in a mapping specification, you can select a join type between sources andspecify the join criteria. The Analyst tool recommends join conditions for a join between sources. You can alsoselect other join conditions.

After you create and name a join, you can use this join object to join between another join object. You can edit ajoin to modify the join condition that you specify for a join.

Add a join to add multiple sources to a mapping specification. Edit a join to modify the join condition between thesources.

You can add the following types of join conditions:Simple join

Uses a single operator in a join condition.

Mapping Specification Joins 63

Advanced join

Uses expression functions in the join condition.

When you join between sources, you join the columns from the detail table and the master table.

The following table describes the type of joins:

Join Type Description

Normal Discards all rows of data from the master and detail source that do not match, based onthe condition.

Master Outer Keeps all rows of data from the detail source and the matching rows from the mastersource. Discards the unmatched rows from the master source.

Detail Outer Keeps all rows of data from the master source and the matching rows from the detailsource. Discards the unmatched rows from the detail source.

Full Outer Keeps all rows of data from both the master and detail sources.

Note: When you create a join between two or more relational tables that have the same column or table names,the Analyst tool uses the table name and column name to create a unique name. For example:TableName.ColumnName.

Adding and Editing a Simple JoinAdd a simple join condition to use a single operator in a join condition. Edit a simple join to modify the joincondition between sources.

1. Click Actions > Edit > Joins.


2. On the Join panel, select one of the following choices:

¨ To add a join, click the New Join icon.

¨ To edit a join, select the join and click the Edit Join icon.

The New Join or Edit Join window appears.


4. Select a join type from the Join Type field.

5. Select a master data object from the Master field.

6. Select a detail data object from the Detail field.

7. Select Simple Join.

8. Choose to add edit a join condition on the Join Condition panel.

¨ To add a join condition, click the New Join Condition icon and select a Master Column Name, Operator,and Detail Column Name.

¨ To edit a join condition, modify the Master Column Name, Operator, and Detail Column Name.

9. Optionally, click the Validate icon to validate the join condition.

10. Optionally, click the Refresh icon to preview the data.

11. Click OK.


Adding an Editing an Advanced JoinAdd an advanced join to use expression functions in the join condition. Edit a simple join to modify the expressionin the Expression editor.

1. Click Actions > Edit > Joins.


2. On the Join panel, select one of the following choices:

¨ To add a join, click the New Join icon.

¨ To edit a join, select the join and click the Edit Join icon.

The New Join or Edit Join window appears.


4. Select a join type from the Join Type field.

5. Select a master data object from the Master field.

6. Select a detail data object from the Detail field.

7. Select Advanced Join.

8. On the Functions tab, select a function, click the arrow icon, select a column, and click OK to add thefunction to the Expression editor.

9. Optionally, on the Master Columns tab, select a column and click the arrow icon to add it as a mastercolumn to the Expression editor.

10. Optionally, on the Detail Columns tab, select a column and click the arrow icon to add it as a detail columnto the Expression editor.

11. Optionally, click the Validate icon to validate the expression.

12. Optionally, on the Data Preview panel, click the Refresh icon to preview the data.

13. Click OK.

Mapping Specification Joins 65

C H A P T E R 8

Mapping Specification ProfilesThis chapter includes the following topics:

¨ Mapping Specification Profiles Overview, 66

¨ Running a Column Profile, 66

¨ Profile Summary, 67

¨ Viewing Column Profile Results, 68

Mapping Specification Profiles OverviewRun a column profile on a mapping specification source to understand the structure and quality of the source data.Run a column profile on the mapping specification target to understand the data that the mapping specificationlogic generates.

Analysts can perform the following profiling tasks on a mapping specification:

¨ Run a column profile on a mapping specification source.

¨ Run a column profile on the mapping specification target.

¨ View a profile summary of a source or target in a mapping specification.

¨ View values, patterns, and statistics for each column in the profile summary.

Running a Column ProfileRun a column profile on a mapping specification source or target to analyze the structure and quality of the data.

1. Choose a source or target column to run a column profile on.

¨ To choose a source column, select a column on the Sources panel.

¨ To choose a target column, select a column from the Transformations and Target Columns panel.

2. Click the Profile Summary tab.

The Analyst tool displays the column profile results.

3. Optionally, click the refresh icon to run the column profile again.

66

Profile SummaryYou can view the summary for a profile run on the Profile Summary view. The profile summary describes theprofile results such as the number of unique and null values expressed as a number and percentage.

You can click each profile summary property to sort on values of the property. The following table describes theprofile summary properties:


Name Name of the column in the profile.

Unique Values Number of unique values for the column in the sampled data set based on thesampling policy.

Unique % Percentage of unique values for the column.

NULL Number of null values for the column.

NULL % Percentage of null values for the column.

Inferred Datatype Datatype derived from the values for the column. The Analyst tool can derive thefollowing datatypes from the datatypes of values in columns:- String- Varchar- Decimal- Integer- "-" for Nulls

Inferred % Percentage of values that match the data type inferred by the Analyst tool. Notdisplayed in the Developer tool.

Documented Datatypes Data type declared for the column in the profiled object.

Maximum Value Maximum value in the column.

Minimum Value Minimum value in the column.

Column ValuesAfter you run a column profile, you can select a column on the Profile Summary view and view the columnvalues. The column values include values for columns and the frequency in which the value appears for thecolumn.

The following table describes the properties for the column values:


Value Displays 200 values for the column in the profile.

Frequency Number of times a value appears for a column, expressed as a number.

Percent Percentage that a value appears for a column.

Chart Chart for the percentage.

Profile Summary 67

Note: You can sort the Frequency column by selecting the column.

Column PatternsAfter you run a column profile, you can select a column on the Profile Summary view and view the columnpatterns. The column patterns include the value patterns for the columns and the frequency in which the patternappears.

The following table describes the properties for the column patterns:


Pattern Pattern for the column in the profile.

Frequency Number of times a pattern appears for a column, expressed as a number.

Percentage Percentage that a pattern appears for a column.

Chart Chart for the percentage.

Column StatisticsAfter you run a column profile, you can select a column on the Profile Summary view and view the columnstatistics. The column statistics include statistics about the column values, such as length, and top and bottomvalues.

The following table describes the types of column statistics:

Statistic Description

Maximum Length Length of the longest value for the column.

Minimum Length Length of the shortest value for the column.

Bottom (5) Lowest values for the column.

Top (5) Highest values for the column.

Viewing Column Profile ResultsYou can view the values, patterns, and statistics for each profiled column on the Profile Summary tab.

1. On the Profile Summary tab, select a profiled column.

2. Click the View Details icon.

The Column Profiling Details window appears.

3. Click the Values, Patterns, or Statistics tabs to view the values, patterns, or statistics for the column.

68 Chapter 8: Mapping Specification Profiles

C H A P T E R 9

Sharing Mapping SpecificationLogic


¨ Sharing Mapping Specification Logic Overview, 69

¨ Mapping Specification Export to Microsoft Excel, 70

¨ Mapping Specification Export to PowerCenter, 71

¨ Mapping Specification Export as a Virtual Table, 73

¨ Mapping Specification Export to a Table Definition, 74

¨ Loading Mapping Specification Results to a Table, 74

¨ Loading the Results of a Mapping Specification to a Flat File, 75

¨ Rules and Guidelines for Loading Mapping Specification Results to a Flat File, 76

Sharing Mapping Specification Logic OverviewAfter you create a mapping specification and build the business logic for the mapping specification target, you canshare the logic or results of the mapping specification with other analysts and developers.

You can share the mapping specification logic and results in the following ways:

Export the mapping specification logic to Microsoft Excel.

Share the mapping specification to document and review the mapping specification with other analysts anddevelopers to modify the mapping specification with the review feedback.

Export the mapping specification logic to PowerCenter.

Share the mapping specification logic or share an XML file that contains the mapping specification logic with aPowerCenter developer to use in a mapplet or mapping.

During the export to PowerCenter process, an analyst who does not have permissions to export the mappingspecification to a PowerCenter repository can choose to export the mapping specification logic as an XML file.The analyst can download this file and provide it to a PowerCenter developer to import as a mapplet ormapping in the PowerCenter repository.

Export the mapping specification logic as a virtual table.

Share the mapping specification logic in a virtual table to run SQL queries against the data.

69

Export the mapping specification target as a table definition.

Share the mapping specification target as a table definition. The Analyst tool generates an SQL script thatcontains the table definition. The SQL script is based on the structure of the mapping specification target. Youcan provide the script to a developer to create the mapping specification target as a table in a database.

Load the mapping specification results to a table.

Share the mapping specification results with other analysts and developers in a relational table. The structureof the mapping specification target must match the structure of the relational target.

Load the mapping specification results to a flat file.

Share the mapping specification results with other analysts and developers in a flat file. When you load themapping specification results to a flat file, the Analyst tool generates a flat file that you can download locally.

Mapping Specification Export to Microsoft ExcelExport the mapping specification logic to Microsoft Excel to share the mapping specification logic with businessteams who do not have access to the Analyst tool.

After you export the mapping specification logic to Microsoft Excel, you can choose to open the file in MicrosoftExcel, or save the file to another location. Analysts can edit the file and upload it to a shared location for furtherreview. Analysts can then edit the mapping specification to incorporate the review comments.

Exporting a Mapping Specification to Microsoft ExcelExport the mapping specification logic to Microsoft Excel to document, share, and review the mappingspecification logic.

Before you export the mapping specification logic to Microsoft Excel, verify that the mapping specification displaysthe Column Mapping view.

1. Click Actions > Export.

The Export window appears.

2. Select Excel.

3. Click Next.

4. Enter a name for the Microsoft Excel file.

By default, the Analyst tool uses the mapping specification name to name the Microsoft Excel file.

5. Click Finish.

A browser pop-up enables you to open or save the file.

Mapping Specifications in Microsoft ExcelAfter you export the mapping specification logic to Microsoft Excel, you can view the mapping specificationobjects, properties, and relationships between objects in separate worksheets in an Excel workbook.

70 Chapter 9: Sharing Mapping Specification Logic

The following table describes the mapping specification logic that appears in the Microsoft Excel workbook:

Microsoft Excel Worksheet Description

Column Mapping Contains the following information that appears in theColumn Mapping view of the mapping specification:- Mapping specification name- Sources- Transformation and target columnsContains hyperlinks for any columns related to mappingspecification objects. Click a hyperlink to access the relatedobject in another worksheet.

Properties Contains the mapping specification properties.

Expressions Contains any expressions that appear in aggregators,lookups, and rules.

Filters Contains the expressions that appear in filters.

Joins Contains the following join information between sources:- Join Name. Name of the join.- Join type. The type of join.- Master. The master data object for the join.- Detail. The detail data object for the join.- Condition. Join condition for the join.

Mapping Specification Export to PowerCenterExport a mapping specification to PowerCenter to share the mapping specification logic with a PowerCenterdeveloper. When you export a mapping specification to PowerCenter you can take advantage of capabilities thatare exclusive to PowerCenter such as partitioning, web services, and recovery.

When you export a mapping specification to PowerCenter, you can choose to use the target in the mappingspecification or select a target that exists in the Model repository.

If you do not select a target in the mapping specification during export, the Analyst tool exports the mappingspecification as a mapplet to PowerCenter. The PowerCenter developer can use this mapplet as a source in amapping and select a target. The developer can create a session, workflow, and connection objects. Thedeveloper can run the workflow.

If you select a target in the Model repository during export, the Analyst tool exports the mapping specification as amapping to PowerCenter. The Analyst tool export process creates a non-reusable session for this mapping in aworkflow. Before the developer runs the workflow, the developer must create the connection objects for thesources and the target in the mapping.

When you export a mapping specification to PowerCenter, you can choose to the following export options:Export to a PowerCenter Repository

You must specify the PowerCenter repository connection properties and the folder in the PowerCenterrepository where you want to export the mapping specification. The connection information for sources andtarget are not exported.

Mapping Specification Export to PowerCenter 71

Export to an XML File

If you do not have permissions to export the mapping specification to a PowerCenter repository, you canchoose to export the mapping specification to an XML file. You can download the XML file and share it with aPowerCenter developer. The developer can import the XML file into the PowerCenter repository and use themapping specification logic as a mapplet or mapping.

In the PowerCenter Designer, the mapping specification objects appear in the appropriate node in the folder. Forexample, the mapping specification target appears in the Targets node.

PowerCenter developers can view descriptions about mapping specification objects after the mappingspecification logic is exported to PowerCenter. Viewing descriptions about mapping specification objects enablesPowerCenter developers to understand the logical flow of a mapping specification. In PowerCenter, thesedescriptions appear in the transformation properties or in the descriptions of the ports in a transformation.

PowerCenter Repository Connection PropertiesWhen you export the mapping specification logic to PowerCenter, you must specify connection properties toconnect to the PowerCenter repository.

The following table describes the PowerCenter repository connection properties:


Host Name PowerCenter domain gateway host name.

Port Number PowerCenter domain gateway port number.

User Name Repository user name.

Password Password for repository user name.

Security Domain LDAP security domain name, if one exists. Otherwise, enter"Native."

Repository Name PowerCenter repository name.

Code Page Repository code page.

PowerCenter Version Version of the PowerCenter repository.

Exporting a Mapping Specification to PowerCenterExport the mapping specification logic to a PowerCenter repository or an XML file if you do not have permissionson the PowerCenter repository.

Before you export the mapping specification logic to PowerCenter, verify that the mapping specification displaysthe Column Mapping view.



2. Select PowerCenter.

3. Click Next.

4. Choose to export the mapping specification as a mapplet or a mapping to PowerCenter.


¨ To export the mapping specification as a mapplet, select the option to use the target in the mappingspecification.

¨ To export the mapping specification as a mapping, select a target from the Target Objects panel.

5. Optionally, click Data Preview to preview the target data.

6. Optionally, click Properties to view the target properties.

7. Click Next.

8. Choose to export the mapping specification to an XML file or to a PowerCenter repository.

9. Click Next.

10. Optionally, enter another name for the mapping specification.

11. Optionally, enter a description.

12. If you chose to export the mapping specification to a PowerCenter repository, select a folder in thePowerCenter repository to export the mapping specification.

13. Click Finish.

The Export to PowerCenter process creates a mapplet or mapping based on the target selected during exportin the PowerCenter repository. If you choose to export to an XML file, you can download the file and provide itto a Powercenter developer.

Mapping Specification Export as a Virtual TableExport the mapping specification logic as a virtual table in a virtual database that analysts and developers can useto run SQL queries against the data.

A virtual table is a table in a virtual database. A virtual database defines uniform views of data and makes the dataavailable for end users to query. A virtual database contains the virtual schemas that contain the virtual tables thatdefine the database structure. End users can run SQL queries against the virtual tables as if they were physicaldatabase tables.

When you export the mapping specification logic as a virtual table, you can create a virtual database or select anexisting virtual database. The Analyst tool creates a virtual table in the virtual database and displays parameters touse as connection information for an ODBC or JDBC connection. You can use an ODBC or JDBC client tool toaccess the virtual table. You can view the virtual database as an application for the Data Integration Service in theAdministrator tool. You can use a JDBC client tool to run SQL queries against the virtual table. You must installthe Informatica JDBC driver on the machine that you connect to the virtual database from.

After you export the mapping specification logic as a virtual table, you can edit the mapping specification andexport the logic to the same virtual table in the same virtual database. The Analyst tool updates the existing virtualtable in the virtual database with the modified logic of the mapping specification.

Exporting a Mapping Specification as a Virtual TableExport the mapping specification logic as a virtual table that analysts and developers can query.

Before you export the mapping specification logic as a virtual table, verify that the mapping specification displaysthe Column Mapping view.



2. Select Virtual table.

Mapping Specification Export as a Virtual Table 73

3. Click Next.

4. Choose to select an existing virtual database or another virtual database.

¨ To choose an existing virtual database, select a virtual database.

¨ To choose another virtual database, click New virtual database and enter a name and an optionaldescription and click OK.

5. Optionally, click Properties to view the virtual database properties.

6. Click Next.

7. Enter the name and an optional description for the virtual table.

8. Click Finish.

9. Optionally, copy the connection parameters to your clipboard.

You can use these connection parameters to create an ODBC or JDBC connection to access the virtual table.

Mapping Specification Export to a Table DefinitionExport the mapping specification target as a table definition that developers can use to create a table in adatabase.

When you export the mapping specification target as a table definition, you can select the database type for thetable definition. The Analyst tool generates an SQL script that contains the table definition based on the structureof the mapping specification target.

You can download this SQL script and provide it to a developer who can run the script to create the table in adatabase. In PowerCenter, a developer can use the table to create a table definition in a mapping. In theDeveloper tool, a developer can import the table as a physical data object to use in a mapping.

Exporting a Mapping Specification to a Table DefinitionExport a mapping specification to a table definition that a developer can use to create a table in a database.

Before you export the mapping specification logic to a table definition, verify that the mapping specificationdisplays the Column Mapping view.



2. Select Table Definition.

3. Click Next.

4. Select a database type.

5. Click Finish.

The Analyst tool displays a pop up to open or save a SQL script file.

Loading Mapping Specification Results to a TableLoad the results of the mapping specification to a target table data object that exists in the Model repository.


Before you load the mapping specification results to a table, verify that the relational table exists in the Modelrepository and that the mapping specification displays the Column Mapping view.



2. Select the Table option.

3. Click Next.

4. Optionally, enter a name for the load operation.

5. Click Next.

6. Optionally, select the Truncate target data option to truncate data in the target.

7. In the Target Object panel, select a target.

8. Optionally, click Data Preview to preview the data in the target.

9. Optionally, click Properties to view the target properties.

10. Click Finish.

Loading the Results of a Mapping Specification to aFlat File

Select the .csv or .txt file format to load the results of a mapping specification. If you select .txt, the Analyst toolcreates a flat file with tab separated values.

Before you load the mapping specification results to a flat file, verify that the mapping specification displays theColumn Mapping view.



2. Select the Flat File option.

3. Click Next.

4. Optionally, enter a name.

5. Optionally, select Export to first line, to export the column names from the first line.

6. Select a file format to save the file.

7. Select a code page.

8. Click Finish.

Note: The Analyst tool may take some time to generate the flat file. Do not close the mapping specificationbefore the prompts to download the flat file appear. You can download this file.

Loading the Results of a Mapping Specification to a Flat File 75

Rules and Guidelines for Loading MappingSpecification Results to a Flat File

Due to differences in flat file formats, some mapping specification results may not be loaded to a flat file.

Use the following rules and guidelines when you load the mapping specification results to a flat file:

Verify that the load file name does not contain non-English characters.

If you select a file name that contains non-English characters during the load process, the generated .txtor .csv flat file displays incorrect file and column names and incorrect data. Specify a file name that containsEnglish characters.

Verify the number of rows in the mapping specification results.

If the results of a mapping specification contain a very large number of rows, the load operation may take awhile to complete. If the load operation hangs, contact an administrator to disable and recycle the AnalystService and cancel the load job from the Data Integration Service.


I N D E X

Aadding and editing an advanced filter

mapping specification configuration 61mapping specification filters 61

aggregator propertiesmapping specification aggregators 57

analyst and developer collaborationmapping specification 42

automatic source and target column mappingmapping specification configuration 50

CColumn Mapping view

Column Mapping view properties 44mapping specification 44

Column Mapping view propertiesColumn Mapping view 44

column patternsmapping specification profiles 68

column profilemapping specification 66

column statisticsmapping specification profiles 68

column valuesmapping specification profiles 67

connectionsDB2 properties 6

connections in Informatica AnalystODBC properties 8Oracle properties 9overview 5SQL Server properties 7

contents viewInformatica Analyst interface 3

Ddata objects

deleting an object 30editing data objects 39flat files 30renaming an object 30tables 30viewing an object 30viewing data objects 39

Data Preview viewmapping specification 46mapping specification results 46

database connectioncreating a database connection 10deleting a database connection 11editing and testing a database connection 10

searching for a database connection 9database connection properties

tables 37datetime datatypes

flat files 33

Fflat file options

flat files 32flat files

adding a fixed-width flat file 34adding a flat file 34data objects 30datetime datatypes 33editing data objects 39flat file datatypes 32flat file options 32loading mapping specification results to a flat file 75synchronizing a flat file data object 35viewing data objects 39

folderscreating a folder 15deleting a folder 16duplicating a folder 15moving a folder 16renaming a folder 15viewing folders contents 16

IInformatica Analyst

Informatica Analyst interface 1Navigator 2

Informatica Analyst interfacecontents view 3Informatica Analyst 1Informatica Analyst views 2log in 4properties view 3security view 3

Informatica Analyst viewsInformatica Analyst interface 2

Jjob status

monitoring job status 28projects 27

77

Llogical data object

mapping specification 41lookup conditions

mapping specification lookups 62lookup properties

mapping specification lookups 62lookups

adding a lookup 63

Mmapping selected columns

mapping specification configuration 50mapping specification

analyst and developer collaboration 42Column Mapping view 44column profile 66creating a mapping specification 49Data Preview view 46editing a mapping specification 49editing an SQL query 53lmapping specification example 42logical data object 41mapping specification configuration 48mapping specification development 43mapping specification objects 54mapping specification types 43mapping specification validation 51Profile Summary view 47Properties view 44SQL query 52SQL Query view 46view a mapping specification in Excel 71

mapping specification aggregatorsadding a simple aggregator 57adding an advanced aggregator 58aggregator properties 57editing a simple aggregator 57editing an advanced aggregator 58mapping specification objects 56

mapping specification configurationadding a lookup 63adding a source 55adding an SQL query 53adding and editing a rule 59adding and editing an advanced filter 61automatic source and target column mapping 50automatically map columns 50creating and editing a rule 59editing a lookup 63editing a source 55editing the target 56loading mapping specification results to a flat file 75loading mapping specification results to a table 75mapping selected columns 50mapping specification 48mapping specification export 69removing column relationships 51

mapping specification developmentmapping specification 43

mapping specification examplemapping specification 42

mapping specification exportexport mapping specification results as a virtual table 73export to a table definition 74

export to Excel 70export to PowerCenter 71exporting mapping specification logic as a virtual table 73exporting mapping specification logic to a table definition 74exporting mapping specification logic to Excel 70exporting mapping specification logic to PowerCenter 72mapping specification configuration 69PowerCenter repository connection properties 72

mapping specification filtersadding a simple filter 60adding an advanced filter 60adding and editing an advanced filter 61editing a filter 60mapping specification objects 60

mapping specification joinsadding and editing a simple join 64, 65mapping specification objects 63

mapping specification lookupslookup conditions 62lookup properties 62mapping specification objects 61

mapping specification objectsmapping specification 54mapping specification aggregators 56mapping specification filters 60mapping specification joins 63mapping specification lookups 61mapping specification rules 59mapping specification sources 55mapping specification target 55

mapping specification profilescolumn patterns 68column statistics 68column values 67profile summary 67running a column profile 66viewing column profile results 68

mapping specification resultsData Preview view 46Profile Summary view 47SQL Query view 46

mapping specification rulesadding and editing a rule 59creating and editing a rule 59mapping specification objects 59

mapping specification sourcesfinding columns 51mapping specification objects 55Metadata Manager sources 55

mapping specification targetedit options for targets 56editing the target 56finding columns 51mapping specification objects 55target datatypes 56

mapping specification typesmapping specification 43

mapping specification validationmapping specification 51validation errors during a load operation 52validation errors during data preview 52validation errors during mapping specification development 52

metadata bookmarkcreating a metadata bookmark 20opening a metadata bookmark 20

Metadata Manager business termmanaging business term 29projects 29

78 Index

Metadata Manager tablesimporting 24

NNavigator

Informatica Analyst 2

Oobjects

deleting an object 19duplicating an object 19moving an object 19previewing data 18renaming an object 19viewing object properties 18

PPowerCenter repository connection

PowerCenter repository connection properties 72profile summary

mapping specification profiles 67Profile Summary view

mapping specification 47mapping specification results 47

projectsassign permissions 12assigning permissions 26creating a Project 13deleting a project 14duplicating a project 13job status 27manage folders 12manage projects 12manage security 25Metadata Manager business term 29permissions 25renaming a project 14search projects 12viewing permissions 26viewing project contents 16

properties viewInformatica Analyst interface 3

Properties viewmapping specification 44rule properties 44target properties 44Where Used 44

Rrule properties

Properties view 44

Ssearch

performing a search 24search filters 23search results 24search syntax 22searching objects example 25

search resultsimporting Metadata Manager tables 24

security viewInformatica Analyst interface 3

SQL queryadding an SQL query 53editing an SQL query 53mapping specification 52

SQL Query viewmapping specification 46mapping specification results 46

Ttables

adding a table 37creating a database connection 10data objects 30database connection properties 37deleting a database connection 11editing and testing a database connection 10editing data objects 39loading mapping specification results to a table 75searching for a database connection 9synchronizing a relational data object 38viewing data objects 39

tagsassigning a tag 21creating a tag 21hiding tags 21tags overview 21viewing tags 21

tags overviewtags 21

target datatypesmapping specification targets 56

target propertiesProperties view 44

Vvalidation errors

during a load operation 52during data preview 52during mapping specification development 52

WWhere Used

Properties view 44

Index 79

Informatica Data Integration Analyst - 9.5.1 - User Guide ... · information provided in this...

Documents

Transcript of Informatica Data Integration Analyst - 9.5.1 - User Guide ... · information provided in this...