Informatica (Version 9.0.1 HotFix 1)

Release Guide

Informatica Release Guide

Version 9.0.1 HotFix 1September 2010

Copyright (c) 1998-2010 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 and InformaticaOn Demand are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and productnames 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 2007 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 © Rouge 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.

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.

This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <daniel@haxx.se>. 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:// svn.dojotoolkit.org/dojo/trunk/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, and http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3-license-agreement.

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) and the BSD License (http://www.opensource.org/licenses/bsd-license.php).

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,254,590; 7,281,001; 7,421,458; and 7,584,422, international Patents and otherPatents 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 non-infringement, 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: IN-REL-90100-HF1-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Part I: Version 9.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1: New Features and Enhancements (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . 2Informatica Data Quality and Informatica Data Explorer Advanced Edition. . . . . . . . . . . . . . . . . . . . . 2

Informatica Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

PowerExchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Adapters for Data Quality and Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: New Features and Enhancements (9.0.1 HotFixes). . . . . . . . . . . . . . . . . . 12HotFix 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Informatica Data Quality and Informatica Data Explorer Advanced Edition. . . . . . . . . . . . . . . 12

Informatica Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3: Informatica Data Quality and Informatica Data Explorer AdvancedEdition (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 4: Informatica Data Services (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Relational Physical Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Relational Physical Data Object Source and Target Transformations. . . . . . . . . . . . . . . . . . . . . . . . 16

Relational Physical Data Object Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Flat File Physical Data Object File Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 5: Informatica Domain (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178.6.1 Features in 9.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Table of Contents i

Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

IBM DB2 Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Connection Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Command Line Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

infacmd Changed Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

infacmd New Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

New Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Data Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Data Integration Service Privilege. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Maximum # of Concurrent Connections Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Maximum Execution Pool Size Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

User Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

View Log Events from the Previous Informatica Version. . . . . . . . . . . . . . . . . . . . . . . . . . 23

Maximum Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Node Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

User Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

License Management Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 6: PowerCenter (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Mapping Analyst for Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Excel Add-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Export Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Standard Mapping Specification Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Sources and Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 7: Metadata Manager (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27backupCmdLine Command Line Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Business Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Data Lineage for Custom Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Data Lineage for SQL Inline Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Impact Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

mmcmd Command Line Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Searching for PowerCenter Metadata Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Part II: Version 9.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 8: New Features and Enhancements (9.0). . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Informatica Data Quality and Informatica Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

ii Table of Contents

Data Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

PowerExchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Adapters for PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

PowerExchange for HP Neoview Transporter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

PowerExchange for Netezza. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

PowerExchange for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

PowerExchange for Teradata Parallel Transporter API. . . . . . . . . . . . . . . . . . . . . . . . . . . 44

PowerExchange for Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

PowerExchange for webMethods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 9: Informatica Domain (9.0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45PowerCenter Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

PowerCenter Domain Name Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Administration Console Name Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Informatica Administrator URL Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Object Name Length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Shared Object Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Domain Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Command Line Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

New Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

New Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Metadata Manager Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 10: PowerCenter (9.0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Reference Table Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 11: Metadata Manager (9.0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Business Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

mmcmd Command Line Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Data Lineage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Removed Resource Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Deprecated Metadata Source Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Linking Objects in Connected Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Table of Contents iii

Connection Assignments for Purged Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Automatic Connection Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

PowerCenter Source Increment Extract Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

PowerCenter Parameter Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Part III: Version 8.6.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 12: New Features and Enhancements (8.6.1). . . . . . . . . . . . . . . . . . . . . . . . . 59Version 8.6.1 HotFix 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Version 8.6.1 HotFix 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Data Masking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Version 8.6.1 HotFix 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

PowerExchange for MSMQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Version 8.6.1 HotFix 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

PowerExchange for JMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Version 8.6.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Administration Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Command Line Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Deployment Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Upgrade Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Data Masking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

PowerExchange for Netezza. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

PowerExchange for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

PowerExchange for Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 13: Integration Service (8.6.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Date Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Pushdown Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Pushdown Subquery Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Pushdown Support for Netezza. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Oracle Bulk Load Buffer Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

IBM DB2 Range Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

FastExport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

iv Table of Contents

Chapter 14: Command Line Programs (8.6.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68infasetup Changed Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

pmrep Changed Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

pmrep New Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

infacmd isp Changed Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Chapter 15: Web Services Provider (8.6.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Web Service Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Deprecated Web Service Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 16: Mapping Analyst for Excel (8.6.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Matching Criteria for Custom Metamaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Import Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Export Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Custom File Naming Conventions and Storage Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 17: Metadata Manager (8.6.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Terminology Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Data Lineage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Lookup Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Publishing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Expanding Metadata Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Metadata Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Viewing Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Metadata Catalog and Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Object Relationships Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Searches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Business Intelligence Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Business Objects Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Dropped Objects in an Oracle Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Teradata Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

ERwin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

URL API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Business Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Wildcards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 18: Data Analyzer (8.6.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Datasource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Table of Contents v

Chapter 19: Adapters for PowerCenter (8.6.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79PowerExchange for Netezza. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

PowerExchange for Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

PowerExchange for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

BAPI/RFC Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

BCI Metadata Connection Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

SAP/ALE IDoc Interpreter Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Part IV: Version 8.6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 20: New Features and Enhancements (8.6). . . . . . . . . . . . . . . . . . . . . . . . . . . 82PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Code Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Orchestration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Mapping Architect for Visio (Data Stencil). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Metadata Exchanges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

PowerChannel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Adapters for PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

PowerExchange for Netezza. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

PowerExchange for SAP NetWeaver BI (BW Option). . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

PowerExchange for SAP NetWeaver (mySAP Option). . . . . . . . . . . . . . . . . . . . . . . . . . . 86

PowerExchange for Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Chapter 21: PowerCenter (8.6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Code Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Real-time Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

XML Target File List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

LANG Environment Variable for Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Mapping Architect for Visio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Mapping Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Unstructured Data Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

vi Table of Contents

Name Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

New Transformation Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Writing to Multiple Output Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 22: Metadata Manager (8.6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Custom Metadata Configurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Connection String. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Relationships Between Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Metadata Manager Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Business Objects XConnect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Cognos SDK Library Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Oracle Service Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Searches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Data Lineage and Where-Used Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 23: Data Analyzer (8.6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Data Analyzer Context Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

JDBC Driver URL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Chapter 24: Adapters for PowerCenter (8.6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97PowerExchange for Netezza. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Editing Datatype and Precision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Update Else Insert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Unprojected Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Code Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Creating Source and Target Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

PowerExchange for JMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

PowerExchange for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

PowerExchange for SAP NetWeaver mySAP Option Renamed. . . . . . . . . . . . . . . . . . . . . . 98

Installing the SAP RFC SDK Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Processing BAPI/RFC Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

PowerExchange for SAP NetWeaver BI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

PowerExchange for SAP NetWeaver BW Option Renamed. . . . . . . . . . . . . . . . . . . . . . . . 99

Registering the PowerExchange for SAP NetWeaver BI Client. . . . . . . . . . . . . . . . . . . . . . 99

Installing the SAP RFC SDK Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

PowerExchange for Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Web Services Consumer Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

SOAP Response Timeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Table of Contents vii

Part V: Version 8.5.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter 25: New Features and Enhancements (8.5.1). . . . . . . . . . . . . . . . . . . . . . . . 102Code Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 26: PowerCenter (8.5.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103pmrep. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Part VI: Version 8.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 27: New Features and Enhancements (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . 106Command Line Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

infacmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

pmrep. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Data Analyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Data Profiling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Data Stencil. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Date Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

External Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Flat File Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Parameters and Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Pushdown Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Real-time Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Session Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Metadata Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Browse and Search Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Edit Metadata Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Custom Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Data Lineage and Where-Used Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Metadata Exchanges (XConnects). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

User Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Metadata Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

PowerCenter Repository Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

New Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

viii Table of Contents

Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Unified Security Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

HTTPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Transformation Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Web Services Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Web Services Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Source and Target Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Mappings and Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

PowerExchange (PowerCenter Connect). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

PowerExchange for WebSphere MQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

PowerExchange for JMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

PowerExchange for SAP NetWeaver BW Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

PowerExchange for SAP NetWeaver mySAP Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

PowerExchange for Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Chapter 28: PowerCenter Domain (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Application Service Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Domain and Service Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Domain Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 29: PowerCenter Security (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125User and Group Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Unified User and Group Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Domain User Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Default Users and Groups for a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Default Users and Groups for a Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Default Repository Administrator Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Logging In to PowerCenter Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Service Manager Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Domain Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Domain Privilege Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Domain Tasks Not Determined by Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

PowerCenter Repository Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Repository Service Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Repository Tasks Not Determined by Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Table of Contents ix

Use Repository Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Metadata Manager Privileges and Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Permissions on Domain Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Permissions on PowerCenter Repository Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Relational Connection Object Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Configuring Repository Folder and Global Object Permissions. . . . . . . . . . . . . . . . . . . . . 132

Copying Repository Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Locking and Unlocking Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Chapter 30: Repository and Repository Service (8.5). . . . . . . . . . . . . . . . . . . . . . . . 134Code Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Managing Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Connecting to a Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Creating a Repository Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Managing User Connections and Locks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Restoring a Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Managing a Repository Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Changing a Repository Code Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

MX Views and MX Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

REP_USERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

REP_USERS_GROUPS and REP_GROUPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Chapter 31: Integration Service (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Datatype Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Bigint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Datetime Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Character Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Character Mapping Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Substitution Values for Inconvertible Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Post-Session Email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Pushdown Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Allow Temporary View for Pushdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Pushdown Optimization Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Date Formats for TO_CHAR() and TO_DATE() Functions. . . . . . . . . . . . . . . . . . . . . . . . 143

$$PushdownConfig Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Pushdown Optimization for Slowly Changing Dimension Logic . . . . . . . . . . . . . . . . . . . . . 144

Pushdown Optimization for the Update Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Real-time Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Recovery Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

x Table of Contents

Recovery Table and Recovery File Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Recovery with Restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Stopping a Real-time Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Partitioning Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Changes to Restart and Recover Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Chapter 32: Functions (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Built-in Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Date Functions with Format String Arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

DATE_COMPARE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

GREATEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

LEAST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

MAKE_DATE_TIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

User-Defined Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

User-Defined Functions in the Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Managing User-Defined Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Validating User-Defined Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Renaming User-Defined Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Copying User-Defined Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Versioning User-Defined Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Analyzing Dependencies for User-Defined Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Querying User-Defined Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Chapter 33: Web Services Provider (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Changes to Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Web Service Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Web Service Sources and Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Chapter 34: Command Line Programs (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152infacmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

New infacmd Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Changed infacmd Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

infasetup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

pmcmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

pmrep. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

New pmrep Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Changed pmrep Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Ported pmrep Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Chapter 35: Transformations (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Complex Data Transformation (Unstructured Data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

External Procedure Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Java Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Table of Contents xi

Joiner Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Sequence Generator Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Chapter 36: Data Profiling (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Data Profiling Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Data Profiling Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Chapter 37: Data Analyzer (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164User Account Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Data Lineage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Weblogic and WebSphere Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Customization of Style Sheets and Color Schemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Change in jBoss Installation Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Managing Data Analyzer Repository Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Obsolete Utilities and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Changes to Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Change in Path for Tools and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Multi-Select on Dashboard Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Panscopic and RDL Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Unicode Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Fax and Mobile Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Access Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Chapter 38: PowerCenter Repository Reports (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . 171PowerCenter Repository Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Running Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Schema Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Chapter 39: Metadata Manager (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Terminology Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Configuring Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Metadata Manager Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Metadata Manager Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Running Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Report Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Removed Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Dashboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Schema Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Metadata Exchanges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Business Objects Metadata Exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Cognos Impromptu Metadata Exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

xii Table of Contents

Microstrategy Metadata Exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Creating and Configuring Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Importing and Exporting Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Loading Multiple Resources Simultaneously. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Agent URL Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

JDBC Connection URL and Source JDBC URL Properties . . . . . . . . . . . . . . . . . . . . . . . 181

Encoding Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Data Lineage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Lineage History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Field-Level Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Limits on Displayed Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Remote Access To Data Lineage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Data Lineage Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Metadata Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Importing and Exporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Object and Report Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Versioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Deleting (Purging) Metadata Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Searching Metadata Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Creating Metadata Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Chapter 40: PowerCenter Connect (8.5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185PowerCenter Connect Name Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

PowerExchange for JMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

PowerExchange for SAP NetWeaver BI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Loading Data to SAP BW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

BW OHS Source Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

BW Application Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Process Chains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Installing Transports to Read Data from SAP BW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

PowerExchange for WebSphere MQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Selecting a Code Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Processing Unicode Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

PowerExchange for SAP NetWeaver mySAP Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Processing BAPI/RFC Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Passing the Sender Partner Number to SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

LANG Datatype Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

saprfc.ini and sideinfo File Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Table of Contents xiii

Upgrading IDoc and DMI Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

xiv Table of Contents

PrefaceThe Informatica Release Guide is written for administrators who are responsible for installing and configuring theInformatica platform and developers and software engineers who implement Informatica. This guide assumes thatyou have knowledge of the features for which you are responsible. The Informatica Release Guide lists newfeatures and enhancements, behavior changes between versions, and tasks you might need to perform after youupgrade from a previous version.

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 infa_documentation@informatica.com. 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. It

xv

includes articles and interactive demonstrations that provide solutions to common problems, compare features andbehaviors, and guide you through performing specific real-world tasks.

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 KB_Feedback@informatica.com.

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 KB_Feedback@informatica.com.

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 Standard RateNorth America: +1 650 653 6332

Toll FreeFrance: 00800 4632 4357Germany: 00800 4632 4357Israel: 00800 4632 4357Italy: 800 915 985Netherlands: 00800 4632 4357Portugal: 800 208 360Spain: 900 813 166Switzerland: 00800 4632 4357 or 0800 463200United Kingdom: 00800 4632 4357 or 0800023 4632 Standard RateBelgium: +32 15 281 702France: 0805 804632Germany: +49 1805 702 702Netherlands: +31 306 022 797

Toll FreeAustralia: 1 800 151 830New Zealand: 1 800 151 830Singapore: 001 800 4632 4357 Standard RateIndia: +91 80 4112 5738

xvi Preface

Part I: Version 9.0.1This part contains the following chapters:

¨ New Features and Enhancements (9.0.1), 2

¨ New Features and Enhancements (9.0.1 HotFixes), 12

¨ Informatica Data Quality and Informatica Data Explorer Advanced Edition (9.0.1), 14

¨ Informatica Data Services (9.0.1), 15

¨ Informatica Domain (9.0.1), 17

¨ PowerCenter (9.0.1), 25

¨ Metadata Manager (9.0.1), 27

1

C H A P T E R 1

New Features and Enhancements(9.0.1)

This chapter includes the following topics:

¨ Informatica Data Quality and Informatica Data Explorer Advanced Edition, 2

¨ Informatica Data Services, 5

¨ Informatica Domain, 6

¨ Metadata Manager, 8

¨ PowerCenter, 9

¨ PowerExchange, 10

¨ Adapters for Data Quality and Data Services, 11

Informatica Data Quality and Informatica Data ExplorerAdvanced Edition

This section describes new features and enhancements to Informatica Data Quality and Informatica Data ExplorerAdvanced Edition.

Analyst Viewer PermissionsYou can create a user or group in the Administrator tool with read-only permissions on objects in the Analyst tool.Analyst Viewer users and groups can view a profile, scorecard, bad or duplicate record table, or reference datatable. They cannot create, edit, or run an object or export profile results to reference tables.

Informatica ContentYou can define an INFA_CONTENT environment variable on a PowerCenter Integration Service machine to setthe path PowerCenter uses to read reference data. Use this environment variable if you cannot install thereference data to the expected location on the PowerCenter machine.

Informatica Data Quality TransformationsAddress Validator transformation

You can configure the Address Validator transformation to generate Coding Accuracy Support System(CASS) reports for United States addresses and Software Evaluation and Recognition Program (SERP)reports for Canadian addresses. CASS and SERP reports verify that the address validation operationsperformed on the source address data meet standards set by the USPS and Canada Post.

2

Multi-strategy transformations

You can configure multiple strategies within a single transformation object for the following transformations:Case, Decision, Key Generator, Labeler, Match, Merge, Parser, and Standardizer. You can apply eachstrategy to a set of data ports in a mapplet or mapping.

Decision transformation

Use the Decision transformation to write business rules using IF-THEN-ELSE logic and regular expressionsand apply the rules to selected ports in a mapplet or mapping.

Note: You must have Informatica Data Quality to use the Data Quality transformations.

Mapping Export and ImportYou can use the Developer tool to import mappings, mapplets, transformations, and any reference table data usedby these objects to the Model repository in a single step.

Mapping Performance¨ You can tune the performance of mappings by updating the mapping optimizer level through the mapping

configuration or mapping deployment properties. The optimizer level determines which optimization methodsthat the Data Integration Service applies to the mapping at run time. You can choose no, minimal, normal, orfull optimization for mappings.

Parameters and Parameter Files¨ You can create parameters to define values that change between mapping runs. For example, create a

parameter to represent a connection so you can run one mapping with different relational source connections.Create a parameter file to define parameter values. The Data Integration Service applies the parameter valueswhen you run a mapping from the command line and specify the parameter file.

Physical Data ObjectsCustomized physical data objects

You can create customized physical data objects to perform the following tasks:

¨ Join source data that originates from the same source database.

¨ Select distinct values from the source.

¨ Filter rows when the Data Integration Service reads source data.

¨ Specify sorted ports.

¨ Specify an outer join instead of the default inner join.

¨ Create a custom query to issue a special SELECT statement for the Data Integration Service to readsource data.

¨ Add pre- and post-mapping SQL commands.

¨ Define parameters for the data object.

¨ Retain key relationships when you synchronize the object with the sources.

You can add customized physical data objects to mappings and mapplets as read, write, or lookup objects.

Create and import

¨ You can create physical data objects from flat file, nonrelational database, relational database, and SAPresources.

¨ You can create physical data objects from resources that contain Developer tool illegal characters orreserved words. For example, you can import a view named "CONCAT" or a table that contains a columnwith a period in the column name.

Informatica Data Quality and Informatica Data Explorer Advanced Edition 3

¨ You can import tables, synonyms, and views from databases that use mixed case metadata. For example,you can import tables "CUST" and "Cust" as separate physical data objects.

ProfilesProfile comments

You can choose to delete profile comments on a profile.

Profile results

¨ You can profile multilingual data from different data objects and view profile results based on the localesettings in the browser. The Analyst tool changes the Datetime, Numeric, and Decimal datatypes based onthe browser locale.

¨ You can sort on multilingual data. The Analyst tool displays the sort order based on the browser locale.

¨ After you run a profile, the Analyst tool purges the last profile run results from the profiling warehouse.

¨ The profiling warehouse stores 16,000 unique highest frequency values including NULL values for profileresults by default. If there is at least one NULL value in the profile results, the Analyst tool can displayNULL values as patterns

Running a profile

¨ After you add a rule to a profile that has previously run, you can select the rule and associated columnsand run the profile again. The Analyst tool displays the previous profile results and the recent rule andcolumns results. You can modify the rule and run the profile again to view changes to profile results for therule.

¨ When you run a profile, you can choose to discard the profile results for previously profiled columns anddisplay results for the columns and rules selected for the latest profile run.

Drilling down on columns

¨ You can choose to drill down on profile data for a column.

¨ You can select the drill-down columns without profiling all the source columns again after you run theprofile.

Repository¨ You can migrate objects from the Informatica Data Quality 8.6.2 repository to the 9.0.1 Model repository. You

can also migrate reference data files used by the objects.

Rules¨ You can choose to drill down on live data for a rule.

¨ You can select the rules for drill down without profiling all the source columns again after running the profile.

Scorecards¨ You can group related scores within a scorecard to view a set of scores for a particular business concept.

When you add a profile column to a scorecard, you can choose to add it to a group. You can add a score to agroup within a scorecard. You can move scores between groups within a scorecard and edit and removegroups from a scorecard.

¨ You can select columns in the scorecard before running a scorecard again. You can choose to drill down onlive data for columns in a score.

¨ You can view the total number of valid and not valid records and the refresh date for each score in thescorecard.

4 Chapter 1: New Features and Enhancements (9.0.1)

Informatica Data ServicesThis section describes new features and enhancements to Informatica Data Services.

Applications¨ Objects in the Application view are sorted by default.

¨ Projects in the Application view have a new icon. They do not use the folder icon anymore.

¨ You can rename an application in the Administrator tool.

¨ You can refresh the Application view to update newly deployed, undeployed, and restored applications.

¨ You can update an application to resolve the conflict when you use the Administrator tool to deploy anapplication with the same name as an existing application. Also, when you select the update or replace optionduring a conflict, you can select an option to stop the existing application if it is running.

Custom Data Transformation¨ You can configure a Custom Data transformation in a mapping. The Custom Data transformation processes

unstructured and semi-structured file formats, such as messaging formats, HTML pages, and PDF documents.The Custom Data transformation also processes structured formats such as ACORD, HL7, EDI-X-12,EDIFACT, and SWIFT. The Custom Data transformation calls a Data Transformation service to process thedata.

Data Object CacheYou can purge data object and virtual table cache for an application. You can purge the cache from theApplications view in the Administrator tool. You can also purge cache with the infacmd PurgeDataObjectCachecommand line program.

Mapping Performance¨ You can tune the performance of mappings by updating the mapping optimizer level through the mapping

configuration or mapping deployment properties. The optimizer level determines which optimization methodsthat the Data Integration Service applies to the mapping at run time. You can choose no, minimal, normal, orfull optimization for mappings.

Parameters and Parameter Files¨ You can create parameters to define values that change between mapping runs. For example, create a

parameter to represent a connection so you can run one mapping with different relational source connections.Create a parameter file to define parameter values. The Data Integration Service applies the parameter valueswhen you run a mapping from the command line and specify the parameter file.

Physical Data ObjectsCustomized physical data objects

You can create customized physical data objects to perform the following tasks:

¨ Join source data that originates from the same source database.

¨ Select distinct values from the source.

¨ Filter rows when the Data Integration Service reads source data.

¨ Specify sorted ports.

¨ Specify an outer join instead of the default inner join.

¨ Create a custom query to issue a special SELECT statement for the Data Integration Service to readsource data.

¨ Add pre- and post-mapping SQL commands.

Informatica Data Services 5

¨ Define parameters for the data object.

¨ Retain key relationships when you synchronize the object with the sources.

You can add customized physical data objects to mappings and mapplets as read, write, or lookup objects.

Create and import

¨ You can create physical data objects from flat file, nonrelational database, relational database, and SAPresources.

¨ You can create physical data objects from resources that contain Developer tool illegal characters orreserved words. For example, you can import a view named "CONCAT" or a table that contains a columnwith a period in the column name.

¨ You can import tables, synonyms, and views from databases that use mixed case metadata. For example,you can import tables "CUST" and "Cust" as separate physical data objects.

Staging Database¨ The staging database properties include the database connection name and the properties for an IBM DB2

EEE database or a Microsoft SQL Server database.

SQL Data Services¨ You can view the JDBC string for an SQL data service in the general properties of the SQL Data Service view

in the Administrator tool.

¨ You can rename an SQL data service in the Administrator tool.

Virtual DataData preview

When you preview virtual table data, you can view a graphical representation of the SQL query you enter. Youcan view the query plan for the original query and for the optimized query plan. Use the query plan totroubleshoot queries that end users run against a deployed SQL data service. You can also use the queryplan to troubleshoot your own queries and to understand the log messages.

Column level security

You can set permissions at the column level to deny queries against a column in a virtual table. You canrestrict user access to a column without denying the user access to the table. You can fail a query that selectsthe column or replace the column value with a default value in a query. Configure column-level security withinfacmd.

Informatica DomainThis section describes new features and enhancements to the Informatica Domain.

ConnectionsPass-through security

The Data Integration Service uses the client user name and the password for connection objects in an SQLdata service. The Data Integration Service connects to source objects with the client credentials instead of thedefault credentials from the connection object. Restrict users from the data in an SQL data service based onuser permissions on the physical data object.

6 Chapter 1: New Features and Enhancements (9.0.1)

Object names

The Data Integration Service can generate SQL against Oracle, DB2, Microsoft SQL Server, or ODBCconnections that have case-sensitive table and column names. You can use the Administrator tool orDeveloper tool to configure the connection. You can specify whether to include quotes around table andcolumn names in the connection.

Microsoft SQL Server

¨ You can use the Administrator tool to specify the owner name and schema name for a Microsoft SQLServer connection.

¨ You can use the Administrator tool or Developer tool to configure a Microsoft SQL Server connection as atrusted connection in the domain.

IBM DB2

You can use the Administrator tool to specify the tablespace name for an IBM DB2 connection.

Connection types

If you have PowerExchange, you can create the following connection types:

¨ DB2 for i5/OS

¨ IMS

¨ Sequential z/OS

¨ VSAM

If you have PowerExchange for SAP Netweaver, you can create the following connection type:

¨ SAP

Connection permissions

You can assign users the read, write, and execute permissions on the database connection. The executepermission grants other users the ability to preview data and run profiles and scorecards on data objectscreated with the connection.

Command Line Program Environment VariablesINFA_DEFAULT_PWX_OSEPASSWORD

Stores the encrypted password for the operating system. You can useINFA_DEFAULT_PWX_OSEPASSWORD to set an encrypted password or use the corresponding commandline -e option on infacmd pwx commands. You can set this password to access the operating sytem.

INFA_DEFAULT_PWX_OSPASSWORD

Stores the plain text password for the operating system. You can use INFA_DEFAULT_PWX_OSPASSWORDto set a plain text password or use the corresponding command line -p option on infacmd pwx commands.You can set this password to access the operating sytem.

INFA_PASSWORD

Stores the encrypted password for miscellaneous options when you set LDAP connectivity, define gatewaynodes, define worker nodes, create new users, reset user passwords, and update SMTP options. You can useINFA_ PASSWORD to set a password or use the corresponding command line option. You can set thispassword to access your Informatica user account, data source, LDAP services, and outbound mail server.

INFA_PC_REPOSITORY_PASSWORD

Stores the default password for the PowerCenter Repository. You can use INFA_PC_REPOSITORY_PASSWORD to set a password or use the corresponding command line option. You canset this password to create a PowerCenter Integration Service, an SAP BW Service, a Web Services Hub,and get log events for the most recent run of a session.

Informatica Domain 7

Domain Configuration¨ You can use infacmd to back up and restore the domain.

LDAP Users¨ You can choose to support case-sensitive distinguished name attributes for the LDAP security domain.

License Management Report¨ The License Management Report is enhanced to provide more statistics, such as user statistics and CPU

statistics for each host. The report contains information for all licenses assigned to the domain. Anadministrator can track the number of times a user logs in to the Analyst tool and how often the user runsprofiles and scorecards.

Service Upgrade¨ Use the Service Upgrade Wizard in the Administrator tool to upgrade multiple services at one time. You can

save the upgrade report to file.

Metadata ManagerThis section describes new features and enhancements to Metadata Manager.

Browse MetadataImpact summary

When you view a business term or any metadata object except PowerCenter objects on the Browse tab, youcan view impacted objects from the most relevant classes. The most relevant classes include businessintelligence reports, relational database tables, PowerCenter mappings, and business terms.

Business GlossaryEmail notifications

Metadata Manager sends an email notifying users about the following events:

¨ A data steward proposes a draft business term for review. Metadata Manager displays the email optionsso that the data steward can send an email to other users.

¨ A user adds a comment to a business term in any phase. Metadata Manager sends an email to the datasteward assigned to the term.

Data LineageSQL inline views for PowerCenter and relational resources

You can view data lineage on a database table, view, or synonym used in an SQL query with an inline view.The SQL query can exist in the following objects:

¨ SQL override in a PowerCenter Source Qualifier or Lookup transformation.

¨ Database views, stored procedures, functions, and triggers.

Custom objects

¨ When you run data lineage analysis on a custom object, the data lineage diagram includes the customobject and all child custom objects.

8 Chapter 1: New Features and Enhancements (9.0.1)

¨ You can view correct data lineage for relationships created between a custom metadata object or abusiness term to the following PowerCenter objects:

- Reusable transformation or session.

When you run data lineage analysis on the custom object or business term, the data lineage diagramdisplays the PowerCenter object and all instances of the object. When you run data lineage analysis onany instance of the PowerCenter object, the data lineage diagram displays the associated custommetadata object or business term.

- Instance of a transformation or session.

When you run data lineage analysis on the custom object or business term, the data lineage diagramdisplays the PowerCenter object instance within the context where the instance is used. For example, thediagram shows a transformation instance within its corresponding mapping and session context.

- Shortcut.

When you run data lineage analysis on the custom object or business term, the diagram displays theinstances of the original object and all instances of the shortcuts to the original object.

PowerCenterThis section describes new features and enhancements to PowerCenter.

Mapping Analyst for ExcelUser interface

Mapping Analyst for Excel includes the following user interface enhancements:

¨ Simple or advanced view of a worksheet by displaying the minimum or maximum columns available.

¨ Icons for the most common tasks.

¨ Annotation of cells with descriptions from other worksheets.

Domains and enumerations

You can configure domains and enumerations to define reference data within a mapping specification. Adomain is a reference table. An enumeration includes the reference table values.

Reusable rules

You can define reusable rules to use as expressions on the Mappings worksheet. You can use rules in amapping specification to perform simple data cleansing.

Validation

When you validate a mapping specification, Mapping Analyst for Excel provides more detailed error messages.

Multiple mappings

You can configure multiple mappings in a single mapping specification based on the Standard mappingspecification template.

Mapping ObjectsData Transformation source and target

You can configure a Data Transformation source or a Data Transformation target in a mapping. The DataTransformation source and the Data Transformation target process unstructured and semi-structured file

PowerCenter 9

formats, such as messages, HTML pages, and PDF documents. The source and target also transformstructured formats such as HIPAA, HL7, EDI-X12, and EDIFACT.

The Data Transformation source and Data Transformation target call a Data Transformation service. The DataTransformation service is the application that transforms the unstructured and semi-structured file formats.The Data Transformation service receives data from the PowerCenter Integration Service, transforms thedata, and returns it to the PowerCenter Integration Service.

Unstructured Data transformation

The Unstructured Data transformation accepts hierarchical groups of input ports. You can pass data thatrepresents relational tables. Groups are related by primary key-foreign key relationships. To increaseperformance you can flush sorted input data to the Unstructured Data transformation.

Identity Resolution transformation

The Identity Resolution transformation is an active transformation that you can use to search and match datain databases. The PowerCenter Integration Service uses the search definition that you specify in the IdentityResolution transformation to search and match data residing in the Informatica Identity Resolution (IIR)tables. The input and output views in the search definition determine the input and output ports of thetransformation. Configure match tolerance and search width parameters in the Identity Resolutiontransformation to determine the matching scheme and search level. The Identity Resolution transformationreturns the candidate records along with the search link port, respective scores, and the number of recordsfound for the search.

PowerExchangeThis section describes new features and enhancements to PowerExchange.

CDC Support for Oracle Materialized Views¨ If you use Oracle materialized views, PowerExchange can capture change data from the tables that underlie

those views. PowerExchange CDC supports any type of materialized view.

CDC Support for Oracle Transparent Data Encrytion¨ If you use Oracle Transparent Data Encryption (TDE) to encrypt data, PowerExchange can capture change

data without your having to perform any additional CDC configuration task.

Data Maps Caching¨ If you configure a cache size, PowerExchange caches NRDB data maps on the system where they are used by

a single PowerExchange Listener, or by multiple PowerExchange Listener, netport, and batch jobs.

DB2 for i5/OS and DB2 for z/OS Stored Procedures as a Source¨ If you use the PowerExchange Client for PowerCenter (PWXPC) in PowerCenter, you can now execute DB2 for

i5/OS and DB2 for z/OS database stored procedures as override SQL for a data source.

GetCurrentFileName Function¨ For a data map record defined for a nonrelational data source, the GetCurrentFileName function gets the name

of the source data file. Use this function to determine from which data file the data for a record was read.

10 Chapter 1: New Features and Enhancements (9.0.1)

infacmd pwx Commands to Manage PowerExchange Application Services¨ infacmd pwx commands to manage a PowerExchange Listener Service. With the infacmd pwx program, you

can issue the CloseListener, CloseForceListener, ListTaskListener, and StopTaskListener commands from thecommand line to manage a PowerExchange Listener Service.

¨ infacmd pwx commands to manage a PowerExchange Logger Service. With the infacmd pwx program, you canissue the CondenseLogger, DisplayAllLogger, DisplayCheckpointsLogger, DisplayCPULogger,DisplayEventsLogger, DisplayMemoryLogger, DisplayRecordsLogger, DisplayStatusLogger, FileSwitchLogger,and ShutDownLogger commands from the command line to manage a PowerExchange Logger Service.

To issue commands to a PowerExchange process that is not managed by a PowerExchange application service,you must use the pwxcmd program.

Writer Partitioning for Bulk Data Movement Sessions¨ You can use pass-through partitioning at writer partition points for bulk data movement sessions that have

VSAM or sequential file targets. The writer partitions process insert operations only. Because the partitionsprocess inserts concurrently, this feature can help improve session performance. If you enable offloadprocessing, offload processing also runs in the partitions concurrently.

Enhanced Timeout Processing¨ PowerExchange provides the following types of timeouts for unsuccessful connection attempts or failed

connections:

- Connection timeouts detect unsuccessful connection attempts.

- Heartbeat timeouts detect a failure of the PowerExchange client or PowerExchange Listener to send orreceive heartbeat data.

- Network operation timeouts detect network operations that exceed the timeout period.

Adapters for Data Quality and Data ServicesThis section describes new features for adapters that you can use with Informatica Data Quality and InformaticaData Services.

PowerExchange for SAP NetweaverYou can use the SAP table reader to import the SAP tables and views definitions into the Model repository. SAPtables include transparent, pool, and cluster tables. In addition, you can extract data from database views in SAP.

Adapters for Data Quality and Data Services 11

C H A P T E R 2

New Features and Enhancements(9.0.1 HotFixes)

This chapter includes the following topic:

¨ HotFix 1, 12

HotFix 1

Informatica Data Quality and Informatica Data Explorer AdvancedEdition

This section describes new features and enhancements to Informatica Data Quality and Informatica Data ExplorerAdvanced Edition.

Informatica Data Quality TransformationsAddress Validation transformation

The Address Validator transformation supports additional output port options from the Address Doctor 5.1.3engine.

Parser transformation

When you define a pattern-based parsing operation, you can use wild cards to search for multiple consecutiveinstances of the same token. For example, you can define WORD+ as a pattern to search a string for anynumber of consecutive words.

Match transformation

The Match transformation can accept data on its GroupKey input port in identity matching mode. Use theGroupKey port to reduce identity match and field match operation times.

ProfilingColumn Profile Results

Profile results report three new types of information: the inferred datatype, the minimum value, and themaximum value in the column.

Join Analysis Results

When you perform join analysis on data sources in the Developer tool, you can export the common andunique records from the Data Viewer to a flat file.

12

Pushdown Optimization¨ The Data Integration Service can push filter transformation logic to SAP sources.

¨ The Data Integration Service can push filter transformation logic to Sybase ASE sources when the DataIntegration Service uses an ODBC connection. When you configure the ODBC connection, configure Sybaseas the ODBC provider.

Repository MigrationThe process to migrate objects from the Informatica Data Quality 8.6.2 repository to the 9.0.1 Model repositoryprovides greater support for address validation operations defined in Data Quality 8.6.2.

Informatica Data ServicesThis section describes new features and enhancements to Informatica Data Services.

Pushdown Optimization¨ The Data Integration Service can push filter transformation logic to SAP sources.

¨ The Data Integration Service can push filter transformation logic to Sybase ASE sources when the DataIntegration Service uses an ODBC connection. When you configure the ODBC connection, configure Sybaseas the ODBC provider.

Metadata ManagerThis section describes new features and enhancements to Metadata Manager.

Microsoft SQL Server AuthenticationYou can authenticate the database user credentials using the Windows protocol and establish a trustedconnection to a Microsoft SQL Server repository when you complete the following tasks:

¨ Create the Metadata Manager Service and the Metadata Manager repository is on Microsoft SQL Server.

¨ Create a Microsoft SQL Server resource.

¨ Create a PowerCenter resource and the PowerCenter repository is on Microsoft SQL Server.

¨ Back up a Metadata Manager repository on Microsoft SQL Server.

¨ Restore a Metadata Manager repository on Microsoft SQL Server.

HotFix 1 13

C H A P T E R 3

Informatica Data Quality andInformatica Data ExplorerAdvanced Edition (9.0.1)

This chapter includes the following topic:

¨ Transformations, 14

Transformations¨ Effective in version 9.0.1, the configurable options for some transformations have new names.

For example, most transformations use the term Strategy to specify the data operations defined in thetransformation. Previously, transformations used different names for user-defined data operations.

¨ Effective in version 9.0.1, the configurable options for some transformations are redesigned.For example, the design of the Labeler transformation is simplified. Previously, you selected token labeler orcharacter labeler mode when you created a Labeler transformation. This distinction is removed.

14

C H A P T E R 4

Informatica Data Services (9.0.1)This chapter includes the following topics:

¨ Relational Physical Data Objects, 15

¨ Relational Physical Data Object Source and Target Transformations, 16

¨ Relational Physical Data Object Keys, 16

¨ Flat File Physical Data Object File Path, 16

Relational Physical Data ObjectsEffective in version 9.0.1, there are two types of relational physical data objects. Relational data objects arephysical data objects that use relational resources as sources. Customized data objects also use relationalresources as sources, but they allow you to perform tasks such as joining data from related resources and filteringrows.

When you upgrade to version 9.0.1 of the Developer tool, the relational physical data objects you created inversion 9.0 of the Developer tool are customized data objects. Therefore, you can configure the data objects toperform the following tasks:

¨ Join source data that originates from the same source database.

¨ Select distinct values from the source.

¨ Filter rows when the Data Integration Service reads source data.

¨ Specify sorted ports.

¨ Specify an outer join instead of the default inner join.

¨ Create a custom query to issue a special SELECT statement for the Data Integration Service to read sourcedata.

¨ Add pre- and post-mapping SQL commands.

¨ Define parameters for the data object.

¨ Retain key relationships when you synchronize the object with the sources.

Previously, you could not perform these tasks within a relational physical data object.

15

Relational Physical Data Object Source and TargetTransformations

When you view a customized data object, the Read and Write views contain source and target transformationsthat display the metadata of the native, relational resources. By default, these transformations have the samename as the relational resource.

When you upgrade a relational physical data object from version 9.0, it becomes a customized data object. Thesource transformation in the Read view has the name "Read" instead of the name of the relational resource.Similarly, the target transformation in the Write view has the name "Write" instead of the name of the relationalresource.

The names of the source and target transformations have no effect on the query that the Developer tool executesagainst the relational resource. If you want to, you can rename the source and target transformations.

Relational Physical Data Object KeysEffective in version 9.0.1, when you upgrade a relational physical data object, it becomes a customized dataobject. In customized data objects, a foreign key must be linked to a primary key in another resource or to aprimary key in the same resource. If you delete a primary key, and the primary key is referenced by a foreign key,the Developer tool also removes the foreign key.

Because foreign keys in a 9.0 relational physical data object do not reference any primary key, the upgradeprocess removes foreign keys from the relational physical data object.

To restore key relationships, synchronize the objects that contain the primary key and foreign key at the same time.

Flat File Physical Data Object File PathEffective in version 9.0.1, if you use the Developer tool to change a flat file data object that you uploaded inAnalyst tool version 9.0, the Analyst tool displays the file path instead of "Uploaded."

Previously, the Analyst tool displayed the file path as "Uploaded."

16 Chapter 4: Informatica Data Services (9.0.1)

C H A P T E R 5

Informatica Domain (9.0.1)This chapter includes the following topics:

¨ 8.6.1 Features in 9.0.1, 17

¨ Connections, 18

¨ Command Line Programs, 19

¨ Data Integration Service, 21

¨ LDAP, 22

¨ Logs, 23

¨ Maximum Heap Size, 23

¨ Node Diagnostics, 23

¨ Reports, 24

8.6.1 Features in 9.0.1This section describes features that exist in versions 8.6.1 and 9.0.1. These features do not exist in version 9.0.

Alerts¨ You can subscribe to domain and service alerts to receive them through email.

¨ You can use infacmd isp to configure alerts.

Domain ConfigurationYou can use the command line interface to back up and restore the domain.

PermissionsConnection permissions.

You can use the Administrator tool or command line interface to configure permissions on connections to limitusers that perform particular actions on the connection. In 9.0, you could not assign permissions onconnections. If you upgrade from 9.0 to 9.0.1, connections that were created in 9.0 remain withoutpermissions. Assign permissions on the 9.0 connections to restrict access to the connections.

Service and folder permissions.

Unless a specific permission is assigned, services and folders inherit permissions from the parent folder.

Domain administrator role permissions.

Domain administrators automatically inherit permissions for all services and folders, including new servicesand folders that are created after the user is assigned the Administrator role.

17

UsersCase-sensitive distinguished name attributes.

You can configure Informatica to support case-sensitive distinguished name attributes for LDAP securitydomains. If you upgrade from 9.0 to 9.0.1, distinguished name attributes that were created in 9.0 are still notcase-sensitive. You can configure 9.0 distinguished name attributes to be case-sensitive.

User preferences.

You can configure user preferences to subscribe to domain and service alerts and to show custom properties.If you upgrade from 8.x to 9.0.1, the following user preferences are no longer available: Show UpgradeOption, Show Tooltips in the Overview Dashboards and Properties, and Overview Grid Refresh Time. As aresult, the Administrator tool performs the following actions:

¨ Shows the Upgrade tab if you have privileges to upgrade PowerCenter.

¨ Shows tooltips in the Overview and Properties tabs of the Administration tool.

¨ Refreshes the grid in the Overview tab every 30 seconds.

License Management ReportYou can send the License Management Report in an email.

ConnectionsThis section describes changes to connections.

IBM DB2 ConnectionsEffective in version 9.0.1, you can configure the tablespace name parameter for IBM DB2 in the advancedproperties of the staging database connection for the Analyst Service. During upgrade, this parameter is removedfrom the staging database properties. You can no longer configure this from the Analyst Service.

After you upgrade to version 9.0.1, an administrator needs to add the tablespace name to all upgraded IBM DB2connections.

Connection PermissionsEffective in version 9.0.1, you can assign read, write, and execute permission on connections.

Previously, all users had all permissions on every connection. All users are upgraded with read, write, and executepermissions. To restrict access to connections, a domain administrator must reset permissions.

18 Chapter 5: Informatica Domain (9.0.1)

Command Line ProgramsThis section describes changes to the command line programs.

infacmd Changed CommandsThe following table lists the changed infacmd dis commands:

Commands Description Comments

UpdateServiceOptions Configures Data Integration serviceoptions.

You can now enter the following options- AllowCaching. Allows data object caching

when pass-through security is enabled.- ConnectionNames. Enter the connection

object name of each connection that allowspass-through security.

The following table lists the changed infacmd ms commands:

Commands Description Comments

RunMapping Runs a mapping from a deployedapplication.

You can now use a parameter file when yourun a mapping. The following option is added:- ParameterFile -pf

Enter the name of the parameter file.

The following table lists the changed infacmd sql commands:

Commands Description Comments

AddGroupPermission Adds a permission to a group. Renamed to AssignGroupPermission.

AddUserPermission Adds a permission for a user. Renamed to AddUserPermission.

ListSchemaPermissions Lists the permissions for a virtualschema.

Deprecated.

SetSchemaPermissions Sets group permissions or userpermissions for a virtual schema.

Deprecated.

infacmd New CommandsThe following table describes new infacmd isp commands:

Command Description

AddConnectionPermissions Assigns permissions for a user or group to a connection.

AssignGroupPermission Assignes a group permissions on an object.

AssignUserPermission Assigns a user permission on an object.

Command Line Programs 19

Command Description

CreateConnection Creates a new database connection.

ListConnections Lists existing connections.

ListConnectionOptions Lists available options for connections that you can use when you create a connection.

ListConnectionPermissions Lists permissions that a user or group has for a connection.

ListConnectionPermissionsByGroup

Lists all groups that have permission for a connection and the type of permissions theyhave.

ListConnectionPermissionsByUser.

Lists all users having permissions on the given connection, along with the type ofpermissions.

ListGroupPermissions Lists the domain objects that a group has permission on.

ListUserPermissions Lists the domain objects that a user has permission on.

RemoveConnection Removes a database connection.

RemoveConnectionPermissions Removes permissions for a specific user or group.

SyncSecurityDomains Synchronizes LDAP security domain.

UpdateConnection Updates an exisiting connection.

The following table describes new infacmd ms commands:

Command Description

ListMappingParams Lists the parameters for a mapping with the default values. You can use the output as aparameter file template.

The following table describes new infacmd pwx commands:

Command Description

CloseForceListener Cancels subtasks and stop.

CloseListener Stops after subtasks complete.

CondenseLogger Starts another logging cycle.

DisplayAllLogger Displays verbose status of a PowerExchange Logger service .

DisplayCheckpointsLogger Reports information about the latest checkpoint file.

DisplayCPULogger Displays the CPU time spent.

DisplayEventsLogger Displays events in wait status.

DisplayMemoryLogger Displays memory use.

20 Chapter 5: Informatica Domain (9.0.1)

Command Description

DisplayRecordsLogger Displays changed record counts.

DisplayStatusLogger Displays status of a PowerExchange Logger service.

FileSwitchLogger Switches to a new set of log files.

ListTaskListener Displays information about active tasks.

ShutDownLogger Shuts down a PowerExchange Logger service.

StopTaskListener Stops a task.

The following table describes new infacmd sql commands:

Command Description

ExecuteSQL Runs SQL queries against virtual tables in a SQL data service.

ListColumnPermissions Lists permissions for a column.

Set ColumnPermissions Sets the permissions for a column.

UpdateColumnOptions Sets column options in order to return a constant instead of failing the query when a userdoes not have permissions on the column.

New Environment VariablesThe following table lists new environment variables:

Command Description

INFA_CLI_CONNECTION_PASSWORD Database password to create connections with infacmd isp CreateConnection.

INFA_PASSWORD User password to create users or maintain LDAP credentials.

INFA_PC_REPOSITORY_PASSWORD PowerCenter repository password to create PowerCenter services or retrievelogs.

Data Integration ServiceThis section describes changes to the Data Integration Service.

Data Integration Service 21

Data Integration Service PrivilegeEffective in version 9.0.1, users must have the following privileges and permission to manage applications in theAdministrator tool:

¨ Manage Applications privilege for the Data Integration Service

¨ Manage Services privilege for the domain

¨ Permission on the Data Integration Service

To manage applications in the infacmd command line program, users must have the Manage Applications privilegefor the Data Integration Service.

Previously, users needed the Manage Services privilege for the domain and permission on the Data IntegrationService to manage applications. After you upgrade, you must assign users the Manage Applications privilege forthe Data Integration Service.

Maximum # of Concurrent Connections PropertyEffective in version 9.0.1, Maximum # of Concurrent Connections is on the Data Integration Service Processesview. In version 9.0, the Maximum # of Concurrent Connections was on the Data Integration Service Propertiesview.

When you upgrade from version 9.0 to 9.0.1, the property value reverts to the default value. The default value is100.

If you configured a value for this property in version 9.0, you must reconfigure the property in version 9.0.1.

Maximum Execution Pool Size PropertyEffective in version 9.0.1, Maximum Execution Pool Size is on the Data Integration Service Processes view. Inversion 9.0, the Max Execution Pool Size was on the Data Integration Service Properties view.

When you upgrade from version 9.0 to 9.0.1, the property value reverts to the default value. The default value is10.

If you configured a value for this property in version 9.0, you must reconfigure the property in version 9.0.1.

LDAPThis section describes changes to LDAP.

User ImportEffective in version 9.0.1, the default maximum size for user import is set to 1000.

Previously, the default value was set to 0, which indicated that there was no maximum value.

When you upgrade, all users are imported into the domain. However, all users over 1000 will be dropped inreverse alphabetic order the next time the Service Manager synchronizes with the LDAP service directory.

To avoid dropping users, reset the maximum size in the LDAP server configuration.

22 Chapter 5: Informatica Domain (9.0.1)

LogsThis section describes changes to logs.

View Log Events from the Previous Informatica VersionEffective in version 9.0.1, use infacmd isp ConvertLogFile command to view log files from PowerCenter 8.1.1,8.5.x and 8.6.x.

The infacmd isp ConvertLogFile command uses the following syntax:

ConvertLogFile

<-InputFile|-in> input_file_name

[<-Format|-fm> format_TEXT_XML]

[<-OutputFile|-lo> output_file_name]

Maximum Heap SizeEffective in version 9.0.1 HotFix 1, specify the units for the Maximum Heap Size property value. You canconfigure the Maximum Heap Size property for an Analyst Service process, Data Integration Service process,Model Repository Service, or Web Services Hub Service. Append one of the following letters to the property valueto specify the units:

¨ b for bytes.

¨ k for kilobytes.

¨ m for megabytes.

¨ g for gigabytes.

Previously, you specified the value in megabytes. When you upgrade, the Administrator tool appends "m" to thevalue.

Node DiagnosticsEffective in version 9.0.1, you do not need to import SSL certificates to generate node diagnostics on a securenode. The Configuration Support Manager web application runs on the same web application as the Administratortool.

Previously, the Configuration Support Manager ran on a separate web application. If you wanted to ensuresecurity when you connected to the Configuration Support Manager, you had to configure the nodes for security.

Logs 23

ReportsThis section describes changes to reports.

User Activity ReportEffective in version 9.0.1, the User Activity Report is obsolete. You can view user activity details in user activity logevents, which appear on the Log tab.

License Management ReportEffective in version 9.0.1, the License Management Report contains information for all licenses assigned to thedomain.

Previously, there was one report for each license key.

24 Chapter 5: Informatica Domain (9.0.1)

C H A P T E R 6

PowerCenter (9.0.1)This chapter includes the following topics:

¨ Mapping Analyst for Excel, 25

¨ Web Services Hub, 26

Mapping Analyst for ExcelThis section describes changes to Mapping Analyst for Excel.

Excel Add-inEffective in version 9.0.1, Mapping Analyst for Excel includes an Excel add-in that adds a Metadata menu orribbon to Microsoft Excel. Use the Metadata menu or ribbon to complete the following tasks:

¨ Show and hide columns on a worksheet.

¨ Annotate cells with descriptions from other worksheets.

¨ Format a worksheet to resize the columns to fit the text.

¨ Validate the mapping specification.

¨ Insert another worksheet of a specific type.

You can install the add-in for Microsoft Excel 2003 or 2007. However, use Microsoft Excel 2007 to use theimproved user interface.

Previously, Mapping Analyst for Excel did not provide a Metadata menu or ribbon. You used the Validate button oneach worksheet to validate data.

Export OptionEffective in version 9.0.1, you do not configure the Operation export option. Mapping Analyst for Excel determinesthe type of export operation to perform. To configure the Format export option, you select the Standard mappingspecification template.

Previously, you configured the Operation export option and typed the name of a template in the Format exportoption.

25

Standard Mapping Specification TemplateEffective in version 9.0.1, Mapping Analyst for Excel includes a single mapping specification template namedStandard-Blank.xlsx. A mapping specification based on the Standard template contains a single or multiplemappings configured on multiple Excel worksheets. Mapping specifications based on this template can containsource definitions, target definitions, rules, and filter, join, lookup, aggregate, and non-aggregate expressions.

Previously, you created a mapping specification based on one of the following mapping specification templates:

¨ Mapping template

¨ Source-Target-Matrix template

¨ Custom template

You can no longer import from or export to mapping specifications based on these templates. If you have existingmapping specifications, you must reconfigure the mapping metadata in a mapping specification based on theStandard template.

Web Services HubThis section describes changes to the Web Services Hub.

Sources and TargetsEffective in version 9.0.1, you can edit sources and targets in web service mappings created in PowerCenter 9.0.1.

You cannot edit web service sources and targets upgraded from previous versions of PowerCenter. To update aweb service source or target from previous versions of PowerCenter, re-create the source or target inPowerCenter 9.0.1.

26 Chapter 6: PowerCenter (9.0.1)

C H A P T E R 7

Metadata Manager (9.0.1)This chapter includes the following topics:

¨ backupCmdLine Command Line Program, 27

¨ Business Glossary, 27

¨ Data Lineage for Custom Objects, 28

¨ Data Lineage for SQL Inline Views, 28

¨ Email, 29

¨ Impact Summary, 29

¨ mmcmd Command Line Program, 29

¨ Searching for PowerCenter Metadata Extensions, 30

backupCmdLine Command Line ProgramEffective in version 9.0.1, backupCmdLine includes an optional commit interval argument for the Restorecommand. The commit interval specifies the number of rows to use as a basis for commits to the MetadataManager repository. The Restore command uses a batch commit each time it writes this number of rows. Defaultis 10,000.

Previously, you could not configure the commit interval. The Restore command committed all rows at the end ofthe restore operation.

Business GlossaryEffective in version 9.0.1, Metadata Manager sends an email notifying users about the following events:

¨ A data steward proposes a draft business term for review. Metadata Manager displays the email options so thatthe data steward can send an email to other users.

¨ A user adds a comment to a business term in any phase. Metadata Manager sends an email to the datasteward assigned to the term.

Previously, Metadata Manager did not send emails notifying users about these events.

27

Data Lineage for Custom ObjectsYou can create a relationship between a custom metadata object or a business term and the followingPowerCenter objects:

¨ Reusable transformation or session.

¨ Instance of a transformation or session.

¨ Shortcut.

Effective in version 9.0.1, a data lineage diagram displays these relationships in the following ways:

¨ Custom metadata object or business term related to a reusable transformation or session.

When you run data lineage analysis on the custom object or business term, the data lineage diagram displaysthe PowerCenter object and all instances of the object. When you run data lineage analysis on any instance ofthe PowerCenter object, the data lineage diagram displays the associated custom metadata object or businessterm.

¨ Custom metadata object or business term related to an instance of a transformation or session.

When you run data lineage analysis on the custom object or business term, the data lineage diagram displaysthe PowerCenter object instance within the context where the instance is used. For example, the diagramshows a transformation instance within its corresponding mapping and session context.

¨ Custom metadata object or business term related to a shortcut.

When you run data lineage analysis on the custom object or business term, the data lineage diagram displaysthe instances of the original object and all instances of the shortcuts to the original object.

Previously, data lineage diagrams did not display all instances of PowerCenter reusable objects and did notdisplay the context of a PowerCenter object instance for these relationships.

After you upgrade, complete one of the following tasks to view these relationships in data lineage diagrams:

¨ Reload the custom resource.

¨ Reload each PowerCenter resource that is related to the custom resource or to the business glossary.

Data Lineage for SQL Inline ViewsEffective in version 9.0.1, you can view data lineage on a database table, view, or synonym used in an SQL querywith an inline view. The SQL query can exist in the following objects:

¨ SQL override in a PowerCenter Source Qualifier or Lookup transformation.

¨ Database views, stored procedures, functions, and triggers.

After you upgrade, reload any relational database or PowerCenter resource that uses SQL inline views.

Previously, Metadata Manager did not correctly display data lineage for a database table, view, or synonym usedin an SQL query with an inline view.

28 Chapter 7: Metadata Manager (9.0.1)

EmailEffective in version 9.0.1, you use the Administrator tool to configure the host name and port number of theoutgoing mail server in the domain SMTP configuration settings. You must configure these properties beforeMetadata Manager can send email notifications.

In version 9.0, you configured the host name and port number of the outgoing mail server in the imm.propertiesfile. After you upgrade from version 9.0, use the Administrator tool to configure the email properties in the domainSMTP configuration settings.

In version 8.6.x, you configured the host name and port number of the outgoing mail server in the domain SMTPconfiguration settings.

Impact SummaryEffective in version 9.0.1, you can view an impact summary when you view the details of a business term or ametadata object in a packaged resource. You cannot view an impact summary for a PowerCenter metadata objector a custom metadata object.

The impact summary for a metadata object displays the following details:

¨ Impact Summary Downstream. Lists all downstream objects. Changes to the selected metadata object impactthese objects.

¨ Impact Summary Upstream. Lists all upstream objects. Changes to these objects impact the selected metadataobject.

The impact summary for a business term displays the following details:

¨ Impact Summary Downstream. Lists all objects that are downstream from the object related to the businessterm. Changes to the related object impact these objects.

¨ Impact Summary Upstream. Lists all objects that are upstream from the object related to the business term.Changes to these objects impact the related object.

After you upgrade, reload all PowerCenter resources to view the impact summary for business terms andmetadata objects.

Previously, Metadata Manager did not display an impact summary. You needed to run data lineage analysis todetermine the impact of metadata changes.

mmcmd Command Line ProgramEffective in version 9.0.1, the mmcmd importmodel command has changed. The -modelName option is optional. Ifyou do not include a model name, mmcmd imports all models in the XML file. Previously, the -modelName optionwas required.

Email 29

Searching for PowerCenter Metadata ExtensionsEffective in version 9.0.1, you cannot search for PowerCenter metadata extensions defined for PowerCentermetadata objects.

When you upgrade, Metadata Manager modifies saved searches that search for a PowerCenter metadataextension property to search on Any Property.

Previously, you could search for PowerCenter metadata extensions.

30 Chapter 7: Metadata Manager (9.0.1)

Part II: Version 9.0This part contains the following chapters:

¨ New Features and Enhancements (9.0), 32

¨ Informatica Domain (9.0), 45

¨ PowerCenter (9.0), 52

¨ Metadata Manager (9.0), 53

31

C H A P T E R 8

New Features and Enhancements(9.0)

This chapter includes the following topics:

¨ Informatica Data Quality and Informatica Data Services, 32

¨ Informatica Analyst, 35

¨ Informatica Domain, 36

¨ PowerCenter, 37

¨ Metadata Manager, 38

¨ PowerExchange, 40

¨ Adapters for PowerCenter, 42

Informatica Data Quality and Informatica Data ServicesUse Informatica Data Quality and Informatica Data Explorer Advanced Edition for data quality solutions. UseInformatica Data Services for data services solutions. You can also use the Profiling option with Informatica DataServices to profile data.

Components for Data Quality and Data Services include a repository, application clients, and application services.

RepositoryData Services and Data Quality both use a Model repository to store objects. If you have Data Services and DataQuality, you can use the same repository.

Application ClientsData Services and Data Quality both use the following application clients to create objects and preview results:

¨ Informatica Developer (Developer tool). Developers use this application to design and implement dataquality and data services solutions. The Developer tool includes an editor to edit the objects that you create.

¨ Informatica Analyst (Analyst tool). Analysts use this web-based application client to analyze, cleanse,standardize, profile, and score data in an enterprise.

32

Application ServicesData Services and Data Quality use the following application services to process the objects that you create in theclient applications:

¨ Data Integration Service. Performs data integration tasks for Informatica Analyst and Informatica Developerand stores metadata in a Model repository.

¨ Model Repository Service. Manages connections to the Model repository.

¨ Analyst Service. Runs Informatica Analyst.

Data QualityInformatica Data Quality is enhanced in version 9.0 with new desktop and web-based client applications.

Use the Developer tool to design and distribute data quality mappings and rules from your desktop. Use theAnalyst tool to analyze data quality and run rules from any Internet browser.

With Data Quality, you can perform the following tasks:

¨ Profile data. Create and run a profile to analyze the structure and content of enterprise data and to identifystrengths and weaknesses in the data. After you run a profile, you can selectively drill down to see theunderlying rows in the profile results. You can also add columns to scorecards and add column values toreference tables.

¨ Score data. Create scorecards to score the valid values for any column or the output of rules. Scorecardsdisplay the value frequency for columns in a profile as scores. Use scorecards to measure and visuallyrepresent data quality progress. You can also view trend charts to view the history of scores over time.

¨ Standardize data values. Standardize data to remove errors and inconsistencies that you find when you run aprofile. You can standardize variations in punctuation, formatting, and spelling.

¨ Parse records. Parse data records to improve record structure and derive additional information from yourdata. You can split a single field of freeform data into fields that contain different information types. You canalso add information to your records. For example, you can flag customer records as personal or businesscustomers.

¨ Validate postal addresses. Address validation evaluates and enhances the accuracy and deliverability of yourpostal address data. Address validation corrects errors in addresses and completes partial addresses bycomparing address records against reference data from national postal carriers. Address validation can alsoadd postal information that speeds mail delivery and reduces mail costs.

¨ Manage bad and duplicate records. Duplicate record analysis compares a set of records against each otherto find similar or matching values in selected data columns. You set the level of similarity that indicates a goodmatch between field values. You can also set the relative weight given to each column in match calculations.For example, you can prioritize surname information over forename information.

¨ Create and run data quality rules. Informatica provides pre-built rules that you can run or edit to meet yourproject objectives. Create and apply rules within profiles. A rule is reusable business logic that definesconditions applied to data when you run a profile. Use rules to further validate the data in a profile and tomeasure data quality progress.

¨ Collaborate with Informatica users. The rules and reference data tables you add to the Model repository areavailable to users in the Developer tool and the Analyst tool. Users can collaborate on projects, and differentusers can take ownership of objects at different stages of a project.

¨ Export mappings to PowerCenter. You can export mappings to PowerCenter to reuse the metadata for dataintegration tasks or to create web services.

Informatica Data Quality and Informatica Data Services 33

¨ Manage reference data. Create and update reference tables for use by analysts and developers to use in dataquality rules. Create, edit, and import data quality dictionary files as reference tables. Create reference tablesto establish relationships between source data and valid and standard values.

The following table lists the data quality tasks that you can perform in the Developer tool and the Analyst tool:

Informatica Developer Informatica Analyst

- Create and run mappings.- Create and run rules.- Perform profiling.- Score data.- Export mappings to PowerCenter.

- Perform profiling.- Score data.- Manage reference tables.- Create profiling rules.- Run rules in profiles.- Manage bad and duplicate records.

Note: Informatica Data Explorer Advanced Edition functionality is a subset of Informatica Data Quality functionality.

Data ServicesInformatica Data Services provides a way to find, understand, integrate, and manage data across an enterprise.

With Informatica Data Services, you can create data models that describe how to represent and access data in anenterprise. You can use the components of the data model for data integration and data quality projects. Reusethe components for multiple projects to eliminate redundant work.

You can also create a virtual database that allows all applications to consume data regardless of how theintegration logic is physically implemented. The virtual database also isolates applications and other dataconsumers from changes in underlying data sources.

With Data Services, you can perform the following tasks:

¨ Define logical views of data. A logical view of data describes the structure and use of data in an enterprise.You can create a logical data object model that shows what types of data your enterprise uses and how thatdata is structured.

¨ Map logical models to data sources or targets. Create a mapping that links objects in a logical model todata sources or targets. You can link data from multiple, disparate sources to have a single view of the data.You can also load data that conforms to a model to multiple, disparate targets.

¨ Create virtual views of data. You can deploy a logical model to a virtual federated database. End users canrun SQL queries against the virtual data without affecting the actual source data.

¨ Export mappings to PowerCenter. You can export mappings to PowerCenter to reuse the metadata forphysical data integration or to create web services.

¨ Create and deploy mappings that end users can query. You can create mappings and deploy them so thatend users can query the mapping results.

¨ Profile data. Create and run profiles to reveal the structure and content of your data. Profiling is a key step inany data project, as it can identify strengths and weaknesses in your data and help you define your projectplan. This is available if you have the profiling option.

¨ Create rules. Create rules with Data Services transformations. This is available if you have the profiling option.

¨ Manage reference data. Create and update reference tables for use by analysts and developers to use in dataquality standardization and validation rules. Create, edit, and import data quality dictionary files as referencetables. Create reference tables to establish relationships between source data and valid and standard values.Developers use reference tables in standardization and lookup transformations in Informatica Developer.

34 Chapter 8: New Features and Enhancements (9.0)

The following table lists the data services tasks that you can perform in the Developer tool and the Analyst tool:

Informatica Developer Informatica Analyst

- Create logical data object models.- Create and run mappings with Data Services transformations.- Create SQL data services.- Profile data.- Create rules.- Export objects to PowerCenter.

- Manage reference data.

Note: If you have the profiling option, you can perform profiling and also create rules with Data Servicestransformations.

Informatica AnalystInformatica Analyst is a new web-based application that analysts can use to analyze, cleanse, standardize, profile,and score data in an enterprise.

Business analysts and developers use Informatica Analyst for data-driven collaboration. You can perform columnand rule profiling, scorecarding, and bad record and duplicate record management. You can also manage andprovide reference data to developers in a data quality solution.

Use Informatica Analyst to accomplish the following tasks:

¨ Profile data. Create and run a profile to analyze the structure and content of enterprise data and identifystrengths and weaknesses. After you run a profile, you can selectively drill down to see the underlying rowsfrom the profile results. You can also add columns to scorecards and add column values to reference tables.

¨ Create rules in profiles. Create and apply rules within profiles. A rule is reusable business logic that definesconditions applied to data when you run a profile. Use rules to further validate the data in a profile and tomeasure data quality progress.

¨ Score data. Create scorecards to score the valid values for any column or the output of rules. Scorecardsdisplay the value frequency for columns in a profile as scores. Use scorecards to measure and visuallyrepresent data quality progress. You can also view trend charts to view the history of scores over time.

¨ Manage reference data. Create and modify reference tables for use by analysts and developers to utilize indata quality standardization and validation rules. Create, edit, and import data quality dictionary files asreference tables. Create reference tables to establish relationships between source data and valid andstandard values. Developers utilize reference tables in standardization and lookup transformations inInformatica Developer.

¨ Manage bad records and duplicate records. Fix bad records and consolidate duplicate records.

Informatica Analyst 35

Informatica DomainThe PowerCenter domain is renamed to Informatica domain. It is expanded include objects and services for theInformatica platform.

Command Line Interfaceinfacmd is expanded to allow management of all Informatica application services.

The Informatica Domain command line interface has the following infacmd programs:

¨ infacmd as. Manage Analyst Services.

¨ infacmd dis. Manage Data Integration Services.

¨ infacmd isp. Administer the domain, security, and PowerCenter application services. Previously, this was calledinfacmd.

¨ infacmd mcf. Export mappings from the Model repository to the PowerCenter repository.

¨ infacmd mrs. Manage Model Repository Services.

¨ infacmd oie. Export objects from the Model repository to an export file. Import objects to the Model repositoryfrom the file.

¨ infacmd ps. Manage the profiling warehouse contents, profiles, and scorecards.

¨ infacmd rtm. Manage the staging database for the Analyst tool.

¨ infacmd sql. Manage SQL data services that you deploy to the Data Integration Service.

ServicesThe Informatica domain includes services for PowerExchange, Informatica Analyst, and Informatica Developer.

Analyst ServiceApplication service that runs Informatica Analyst in the Informatica domain. Create and enable an Analyst Serviceon the Domain tab of Informatica Administrator. When you enable the Analyst Service, the Service Manager startsInformatica Analyst. You can open Informatica Analyst from Informatica Administrator.

Data Integration ServiceApplication service that processes requests from Informatica Analyst and Informatica Developer to preview or rundata profiles and mappings. It also generates data previews for SQL data services and runs SQL queries againstthe virtual views in an SQL data service. Create and enable a Data Integration Service on the Domain tab ofInformatica Administrator.

Model Repository ServiceApplication service that manages the Model repository. The Model repository is a relational database that storesthe metadata for projects created in Informatica Analyst and Informatica Designer. The Model repository alsostores run-time and configuration information for applications deployed to a Data Integration Service. Create andenable a Model Repository Service on the Domain tab of Informatica Administrator.

PowerExchange Listener ServiceManages the PowerExchange Listener for bulk data movement and change data capture. The PowerCenterIntegration Service connects to the PowerExchange Listener through the Listener Service.

36 Chapter 8: New Features and Enhancements (9.0)

PowerExchange Logger ServiceManages the PowerExchange Logger for Linux, UNIX, and Windows to capture change data and write it to thePowerExchange Logger Log files. Change data can originate from DB2 recovery logs, Oracle redo logs, aMicrosoft SQL Server distribution database, or data sources on an i5/OS or z/OS system.

ManagementThis section describes new features and enhancements to domain management.

Informatica AdministratorThe PowerCenter Administration Console is renamed to Informatica Administrator (Administrator tool). TheInformatica Administrator has a new interface. Some of the properties and configuration tasks from thePowerCenter Administration Console have been moved to different locations in Informatica Administrator.

Connection ManagementDatabase connections are centralized in the domain. You can create and view database connections inInformatica Administrator, Informatica Developer, or Informatica Analyst. Create, view, edit, and grant permissionson database connections in Informatica Administrator.

DeploymentYou can configure, deploy, and enable applications in the Developer tool. Deploy applications to one or more DataIntegration Services.

LicensingThe Informatica domain enforces the licensing restrictions on the number of CPUs and PowerCenter repositories.

MonitoringYou can monitor profile jobs, scorecard jobs, preview jobs, mapping jobs, and SQL data services for each DataIntegration Service. View the status of each monitored object on the Monitoring tab of the Administrator tool.

PowerCenterThis section describes new features and enhancements to PowerCenter.

Real-time Sessions¨ Session log file rollover. You can limit the size of session logs for real-time sessions. You can limit the size

by time or by file size. You can also limit the number of log files for a session.

Lookup Transformation¨ Cache updates. You can update the lookup cache based on the results of an expression. When an expression

is true, you can add to or update the lookup cache. You can update the dynamic lookup cache with the resultsof an expression.

¨ Database deadlock resilience. In previous releases, when the Integration Service encountered a databasedeadlock during a lookup, the session failed. Effective in 9.0, the session will not fail. When a deadlock occurs,the Integration Service attempts to run the last statement in a lookup. You can configure the number of retryattempts and time period between attempts.

PowerCenter 37

¨ Multiple rows return. You can configure the Lookup transformation to return all rows that match a lookupcondition. A Lookup transformation is an active transformation when it can return more than one row for anygiven input row.

¨ SQL overrides for uncached lookups. In previous versions you could create a SQL override for cachedlookups only. You can create an SQL override for uncached lookup. You can include lookup ports in the SQLquery.

SQL Transformation¨ Auto-commit for connections. You can enable auto-commit for each database connection. Each SQL

statement in a query defines a transaction. A commit occurs when the SQL statement completes or the nextstatement is executed, whichever comes first.

¨ Exactly-once processing. The Integration Service provides exactly-once delivery of real-time sourcemessages to the SQL transformation. If there is an interruption in processing, the Integration Service canrecover without requiring the message to be sent again. To perform exactly-once processing, the IntegrationService stores a set of operations for a checkpoint in the PM_REC_STATE table.

¨ Passive transformation. You can configure the SQL transformation to run in passive mode instead of activemode. When the SQL transformation runs in passive mode, the SQL transformation returns one output row foreach input row.

XML Transformation¨ XML Parser buffer validation. The XML Parser transformation can validate an XML document against a

schema. The XML Parser transformation routes invalid XML to an error port. When the XML is not valid, theXML Parser transformation routes the XML and the error messages to a separate output group that you canconnect to a target.

Mapping Architect for Visio¨ Shortcuts. You can configure a transformation to use a shortcut. You can create a mapping template from a

mapping that contains shortcuts to reusable transformations.

¨ Mapping template. You can include the following objects in a mapping template:

- Pipeline Normalizer transformation

- Custom transformation

- PowerExchange source definition

- PowerExchange target definition

Metadata ManagerThis section describes new features and enhancements to Metadata Manager.

Resources¨ Microsoft Analysis and Reporting Services resource. Metadata Manager added the Microsoft Analysis and

Reporting Services resource. Use this resource to extract reporting metadata from Microsoft ReportingServices and to extract an analysis schema from Microsoft Analysis Services.

¨ Test a connection to validate the configuration of a resource. When you create or edit a resource, clickTest Connection to test the connection to the source system, validate the Metadata Manager Agent URL, orvalidate the source file configuration.

38 Chapter 8: New Features and Enhancements (9.0)

¨ PowerCenter parameter file syntax. Metadata Manager supports additional forms of parameters inPowerCenter parameter files for a PowerCenter resource.

¨ Upload multiple PowerCenter parameter files. When you configure a PowerCenter resource, you can uploadmultiple PowerCenter parameter files at the same time.

¨ Abort loads. You can abort a load of any resource that requires the Metadata Manager Agent or any IBM DB2z/OS resource.

¨ Single log file. You can download a single log file in Microsoft Excel that includes load details, sessionstatistics, and summary details.

¨ Edit resources. Use a single dialog box to edit any property for a resource, including connection properties,connection assignments, resource parameters, and schedules.

Connection Assignments¨ Link objects in connected resources. If you change connection assignments for a resource, you do not need

to reload the resource to create the links between matching objects in connected resources. You can use theResource Link Administration window to direct Metadata Manager to create the links between matching objectsin the resources.

¨ Export missing link details. The Load Details tab contains summary information for links created betweenobjects in connected resources. You can export the details of objects that Metadata Manager could not link to aMicrosoft Excel file for further analysis.

¨ Automatic connection assignment. Metadata Manager can automatically configure connection assignmentsfor a data integration, business intelligence, or data modeling resource. Metadata Manager configures theconnection assignments during a resource load or link process. Use the Load Details tab to review theconnection assignments and make corrections as needed. Or, you can manually configure the connectionassignments.

¨ Purging resources keeps connection assignments. Metadata Manager keeps connection assignments for apurged resource. The connection assignment properties display the schema status as purged. If you reload theresource, Metadata Manager changes the status to active if the schema still exists in the source.

Business Glossary¨ Business Glossary approval workflow. You can use the business glossary to create and edit draft business

terms, propose the business terms for review by data stewards and then publish the terms. After publication,the business term is visible to all users.

¨ Migrate a business glossary. You can migrate business glossaries to and from XML. The XML file includes allcategories, business terms, and custom objects, and object comments, links, and relationships.

¨ Business glossary terms in data lineage diagram. When you launch data lineage, Metadata Managerdisplays the business terms associated with each object in a lineage diagram. Metadata Manager does notdisplay the both upstream and downstream connections between business terms in a data lineage diagramanymore.

¨ Link business glossary terms to reference tables. You can associate a business term with a reference tablename and a URL to the reference table. You can specify a URL to a reference table in Informatica Analyst, oryou can include any valid URL to a reference table. Previously you associated a business term with a referencetable in Reference Table Manager. Reference Table Manager no longer exists.

¨ Audit trail. View the history of changes to business glossary categories, business terms, and custom objects.The audit trail includes the old and new values of a property and the user who made the edits. You can alsosearch the audit trail.

Metadata Manager 39

Browse Metadata¨ Use the URL API to access Metadata Manager objects and features . You can use the URL API to access

Metadata Manager objects and features from external applications. For example, you can bookmark a link to aparticular catalog object, or you can access data lineage on a specific object from a business intelligence tool.

¨ Display one instance of an object in the lineage diagram. PowerCenter mappings and database tables,views, and synonyms are no longer split across multiple instances in different nodes in a lineage diagram. Youcan also configure additional classes whose objects are not split.

mmcmd CommandsThe mmcmd command line program includes commands in the following areas:

¨ Resource management. Added commands to create, update, delete, and purge resources. Added commandsto configure connection assignments, configure PowerCenter parameter files, and create links between objectsin connected resources. Added a command to cancel a resource load.

¨ Metadata Manager Service. Added commands to create and delete Metadata Manager repository content andto restore PowerCenter repository content.

Import/Export¨ Export and import in XML. You can export any custom resource, business glossary, or property added to a

packaged resource type to an XML file and import it into another Metadata Manager instance.

Audit Trail¨ Audit trail. View the history of changes to business glossary categories and terms, custom resources, and

properties added to packaged resource types. The audit trail includes the old and new values of a property andthe user who made the edits. You can also search the audit trail.

SearchSearching metadata in Metadata manager includes the following enhancements:

¨ Links. You can search for text in links for metadata objects, including link name, link description, link URL .

¨ Location property. By default, the location of an object appears in search results. You can click the link toopen the metadata object from the search results.

¨ Include audit trail in search results. You can choose to search the history of changes made to customresource objects, business glossary categories and terms, and properties added to packaged resource types.

User Interface Enhancements¨ Updated user interface pages. The Browse, Model, Load, and Security pages contain updates to the look and

feel, Action menu, context-sensitive menus, and toolbar buttons. The Search menu is more conveniently placedfor accessibility. The user interface is more consistent with other Informatica web-based tools.

PowerExchangeThis section describes new features and enhancements to PowerExchange.

¨ Asynchronous network communication. PowerExchange uses asynchronous network communication formost send and receive operations between a PowerExchange client and a PowerExchange Listener. Withasynchronous communication, PowerExchange uses separate threads for network processing and dataprocessing, so that network processing overlaps with data processing. PowerExchange sends and receivesheartbeat signals across the network that can be used for early detection of failure situations.

40 Chapter 8: New Features and Enhancements (9.0)

¨ Partitioning for bulk data movement sessions. PowerExchange 9.0 provides the following partitioningenhancements:

- You can use pass-through partitioning without SQL overrides for bulk data movement sessions that includeany of the following offloaded data sources: VSAM data sets, sequential data sets, and DB2 for z/OS unloaddata sets. PowerExchange opens a single connection to the data source and distributes the data across thepartitions.

- For all other nonrelational bulk data sources, you can use pass-through partitioning with disjoint SQLoverrides. If you do not provide overrides with these data sources, data is read into the first partition only.

¨ DB2 for z/OS Stored Procedure transformations. You can use Stored Procedure transformations for DB2 forz/OS stored procedures in a PowerCenter mapping. Use Stored Procedure transformations for read or writebulk data movement and change data capture (CDC) operations.

¨ DB2 for i5/OS multiple-row FETCH statements. To enhance the performance of DB2 for i5/OS bulk datamovement operations that use the DB2 access method, PowerExchange uses a DB2 multiple-row FETCHstatement to retrieve multiple rows of data at a time from a source table. In PowerCenter, you can configure thenumber of rows to be retrieved by setting the Array Size attribute on a PWX DB2i5OS relational connectionused by PWXPC.

¨ PowerExchange Logger for Linux, UNIX, and Windows performance. The following enhancements improvePowerExchange Logger for Linux, UNIX, and Windows processing and management:

- PowerExchange Logger configuration parameters. You can enter additional parameters in thePowerExchange Logger for Linux, UNIX and Windows configuration file to control how expired CDCT recordsare deleted, specify the maximum number of days to hold retention array items in memory, and controlwhether PowerExchange displays a user confirmation prompt for a cold start or for a warm start from aprevious position in the change stream.

- PowerExchange Logger cold starts. PowerExchange 9.0 provides a COLDSTART parameter that enablesyou to control whether the PowerExchange Logger for Linux, UNIX, and Windows cold starts or warm starts.

- DISPLAY commands. Additional DISPLAY commands are available for the PowerExchange Logger forLinux, UNIX, and Windows to help you monitor and manage PowerExchange Logger processing. You canissue these commands from the command line or by using the pwxcmd program.

- Checkpoint file. For more efficient checkpoint processing and smaller checkpoint files, PowerExchange 9.0changes the format of the PowerExchange Logger checkpoint files from CISAM files to sequential files withthe extension .ckp.

¨ PowerExchange Logger file management. Use the PWUCDCT utility to back up, restore, and regenerate thePowerExchange Logger for Linux, UNIX, and Windows CDCT file and to manage expired CDCT records andorphaned log files. Also use the utility to print reports on PowerExchange Logger files such as checkpoint filesand log files.

¨ pwxcmd command support for i5/OS and z/OS. You can issue use the pwxcmd program to issue commandsfrom a Linux, UNIX, or Windows system to a PowerExchange Listener or PowerExchange Condense processrunning on an i5/OS or z/OS system.

¨ Extraction of relative record numbers during DB2 for i5/OS CDC processing. When you create a captureregistration, you have the option to capture the relative record number of the change record.

¨ PowerExchange Listener Service. Use this application service to manage the local PowerExchange Listener.You can create, start, or stop a PowerExchange Listener service or view status information in the InformaticaAdministrator.

¨ PowerExchange Logger Service. Use this application service to manage the local PowerExchange Logger forLinux, UNIX, and Windows. You can create, start, or stop a PowerExchange Logger service or view statusinformation in the Informatica Administrator.

PowerExchange 41

Adapters for PowerCenterThis section describes new features and enhancements to the adapters for PowerCenter.

PowerExchange for HP Neoview Transporter¨ Support for the following platforms:

- SUN SPARC 64-bit

- Windows 2003 on EM64T

¨ You can import a Neoview source or target definition from Neoview. Previously, you connected to Neoviewthrough ODBC to create an Neoview source or target definition.

¨ You can generate and execute SQL for a Neoview target.

¨ You can preview source and target data.

¨ Support for all Neoview datatypes except Interval.

¨ Precision to the nanosecond for Neoview date and time datatypes.

¨ Multibyte character support.

¨ You can configure the following properties in the Source Qualifier:

- Number of sorted ports

- Select distinct

- Source filter

¨ You can override an SQL query in the Source Qualifier.

¨ You can use the following transformations in a Neoview mapping:

- Lookup

- SQL

- Stored Procedure

- Update Strategy

¨ Relational connection object. Use a relational connection object for the Integration Service to connect toNeoview. Select a relational or bulk reader for the connection when you configure the session properties.

¨ You can enter mapping variables and workflow variables in the connection object properties.

¨ You can configure parameters for a Neoview session.

¨ You can configure a Neoview session for recovery.

¨ You can enter pre-session and post-session SQL commands.

¨ You can override the source table name and source table name owner the in the session properties.

¨ You can configure the following session properties for a Neoview session:

- Commit type

- Enable high precision

- Error log type

- Error row handling

- Pipeline partitioning

- Session on grid

¨ If you use PowerExchange change data capture, you can load the changed data to Neoview as a target in thesame mapping.

42 Chapter 8: New Features and Enhancements (9.0)

PowerExchange for Netezza¨ Filtering metadata during source import. You can filter the metadata you want to appear when you create a

Netezza source definition.

¨ You can import a Netezza source or target definition from Netezza. Previously, you connected to Netezzathrough ODBC to create a Netezza source or target definition.

¨ You can generate and execute SQL for a Netezza target.

¨ You can preview source and target data.

¨ Support for all Netezza datatypes except Interval.

¨ Precision to the nanosecond for Netezza date and time datatypes.

¨ Multibyte character support.

¨ You can configure the following properties in the Source Qualifier:

- Number of sorted ports

- Select distinct

- Source filter

¨ You can override an SQL query in the Source Qualifier.

¨ You can use the following transformations in a Netezza mapping:

- Lookup

- SQL

- Update Strategy

¨ Relational connection object. Use a relational connection object for the Integration Service to connect toNetezza. Select a relational or bulk reader for the connection when you configure the session properties.

¨ You can enter mapping variables and workflow variables in the connection object properties.

¨ You can configure parameters for a Netezza session.

¨ You can configure a Netezza session for recovery.

¨ You can enter pre-session and post-session SQL commands.

¨ You can override the source table name and source table name owner the in the session properties.

¨ You can configure the following session properties for a Netezza session:

- Commit type

- Enable high precision

- Error log type

- Error row handling

- Pipeline partitioning

- Pushdown optimization

- Session on grid

¨ If you use PowerExchange change data capture, you can load the changed data to Netezza as a target in thesame mapping.

PowerExchange for SAP NetWeaver¨ Writing data to the IS-U Migration Workbench. You can import an IS-U transformation to generate files for an

SAP migration file. The Integration Service can write the data to the IS-U Migration Workbench.

Adapters for PowerCenter 43

PowerExchange for Teradata Parallel Transporter API¨ You can add partitions to a session that includes a Teradata PT API source.

PowerExchange for Web Services¨ Configuring a user name and password for authentication. When a web service is protected or secure, you can

include a user name and password in a web service target or Web Services Consumer transformation.

PowerExchange for webMethods¨ You can import documents with special characters as source definitions.

44 Chapter 8: New Features and Enhancements (9.0)

C H A P T E R 9

Informatica Domain (9.0)This chapter includes the following topics:

¨ PowerCenter Domain, 45

¨ Command Line Programs, 46

¨ Metadata Manager Privileges, 51

PowerCenter DomainThis section describes changes to the PowerCenter domain.

PowerCenter Domain Name ChangeEffective in version 9.0, the PowerCenter domain is renamed to Informatica domain.

Administration Console Name ChangeEffective in version 9.0, the PowerCenter Administration Console is renamed to Informatica Administrator.

Informatica Administrator URL ChangeEffective in version 9.0, the host and port in the Informatica Administrator URL represent the host name of themaster gateway node and the Informatica Administrator port number. You configure the Informatica Administratorport when you define the domain. You can define the domain during installation or using the infasetupDefineDomain command line program.

If the domain fails over to a different master gateway node, the host name in the Informatica Administrator URLwill be equal to the host name of the elected master gateway node.

Previously, the host and port in the Informatica Administrator URL represented the host name and port number ofany gateway node.

Object Name LengthEffective in version 9.0, domain object names, except folder names, can be up to 128 characters long.

Previously, domain object names could be up to 80 characters.

45

Shared Object NamesEffective in version 9.0, some objects within a domain can have the same name. The following table lists whetherdomain objects can have the same names:

Node Folder Grid License Service

Node No Yes Yes Yes Yes

Folder Yes Yes, if they arenot at the samelevel.

Yes Yes Yes

Grid Yes Yes No Yes Yes

License Yes Yes Yes No Yes

Service Yes Yes Yes Yes No

Previously, domain objects could not have the same name.

Domain ConfigurationEffective in version 9.0, the domain configuration metadata uses the same database structure as the Modelrepository database.

You should back up the domain configuration database on a regular basis. You can restore the domainconfiguration from a backup. If you migrate the domain configuration to another database or change the databaseconnection information, you must update the database connection on all gateway nodes.

You create a license object when you install PowerCenter. You can also create license objects in InformaticaAdministrator. You can view the license and all licensed options in Informatica Administrator.

Command Line ProgramsThis section describes changes to the command line programs.

New CommandsThe following table describes the new infacmd as commands:

Command Description

CreateAuditTables Creates audit tables.

CreateService Creates an Analyst Service.

DeleteAuditTables Deletes audit tables.

46 Chapter 9: Informatica Domain (9.0)

Command Description

ListServiceOptions Lists Analyst service properties that you can update.

ListServiceProcessOptions Lists Analyst service process options that you can update.

UpdateServiceOptions Updates Analyst service properties.

UpdateServiceProcessOptions Updates Analyst service process properties.

The following table describes the new infacmd dis commands:

Command Description

BackupApplication Backs up an application from a Data Integration Service.

CreateService Creates the Data Integration Service.

DeployApplication Deploys an application to a Data Integration Service.

ListApplicationOptions Lists tapplication properties that you can update.

ListDataObjectOptions Lists the data object properties that you can update.

ListServiceOptions Lists Data Integration Service properties that you canupdate.

ListServiceProcessOptions Lists Data Integration Service process properties that youcan update.

RestoreApplication Restores an application to a Data Integration Service.

StartApplication Starts an application.

UpdateApplication Updates a deployed application from an application file andmaintains existing properties.

UpdateApplicationOptions Updates application properties.

UpdateDataObjectOptions Updates data object properties.

UpdateServiceOptions Updates Data Integration Service properties.

UPdateServiceProcessOptions Updates Data Integration Service process properties.

CancelDataObjectCacheRefresh Stops a refresh of data object cache.

ListApplicationObjects Lists the paths of objects in an application.

ListApplications Lists deployed applications for a Data Integration Service.

PurgeDataObjectCache Purges data object cache.

RefreshDataObjectCache Refreshes data object cache.

Command Line Programs 47

Command Description

RenameApplication Renames a deployed application.

StopApplication Stops an application from running.

UndeployApplication Remove an application from a Data Integration Service.

The following table describes the new infacmd ipc commands:

Command Description

ExportToPC Exports an object in PowerCenter format.

The following table describes the new infacmd mrs commands:

Command Description

BackupContents Backs up Model repository contents.

CreateContents Creates Model repository contents.

CreateService Creates a Model repository service.

DeleteContents Deletes a Model repository service

ListBackupFiles Lists backup files

ListServiceOptions Lists service options

ListServiceProcessOptions Lists service process options

RestoreContents Restores Model repository contents

UpdateServiceOptions Updates Model repository service options

UpdateServiceProcessOptions Updates service process options

UpgradeContents Updates the Model repository

The following table describes the new infacmd ms commands:

Command Description

ListMappingParams Create a parameter file for a parameterized mapping.

ListMappings List deployed mappings.

RunMapping Runs a deployed mapping.

48 Chapter 9: Informatica Domain (9.0)

The following table describes the new infacmd ps comands:

Command Description

CreateWH Creates Profiling Warehouse contents.

DropWH Drops ProfilingWarehouse Contents.

Execute Executes a profile or scorecard.

List Lists profiles or scorecards.

Purge Purge profile or scorecard results from the warehouse.

The following table describes the new infacmd pwx command:

Description Command

CloseForceListener Cancels subtasks and stops the Listener.

CloseListener Stops the Listener after subtasks complete.

CreateListenerService Creates a PowerExchange Listener service.

ListTaskListener Displays information about active tasks.

StopTaskListener Stops a task.

UpdateListenerService Updates a PowerExchange Listener service.

CondenseLogger Starts another logging cycle.

CreateLoggerService Creates a PowerExchange Logger service.

DisplayAllLogger Displays verbose status of a PowerExchange Logger service.

DisplayCPULogger Displays the CPU time spent.

DisplayCheckpointsLogger Reports information about the latest checkpoint file.

DisplayEventsLogger Displays events being waited on.

DisplayMemoryLogger Displays memory use.

DisplayRecordsLogger Displays counts of change records.

DisplayStatusLogger Displays status of a PowerExchange Logger service.

FileSwitchLogger Switches to a new set of log files.

ShutDownLogger Shuts down a PowerExchange Logger service.

UpdateLoggerService Updates a PowerExchange Logger service.

Command Line Programs 49

The following table describes the new infacmd rtm commands:

Command Description

Deployimport Imports Content to Staging database.

Export Exports dictionary content.

Import Imports dictionary content.

The following table describes the new infacmd sql commands:

ListSQLDataServiceOptions Lists SQL Data Service options.

ListSQLDataServicePermissions Lists SQL Data Service permissions.

ListStoredProcedurePermissions Lists stored procedure permissions.

ListTableOptions Lists table options.

ListTablePermissions Lists table permissions.

SetSQLDataServicePermissions Sets permissions on a SQL data service.

SetStoredProcedurePermissions Sets permissions on a stored procedure.

SetTablePermissions Sets permissions on a table.

StartSQLDataService Starts a SQL data service.

UpdateSQLDataServiceOptions Updates SQL data service properties.

UpdateTableOptions Updates table properties.

ListSQLDataServices Lists all SQL data service names for a Data IntegrationService.

PurgeTableCache Purge virtual table cache.

RefreshTableCache Refresh virtual table cache.

RenameSQLDataService Rename a SQL Data Service.

StopSQLDataService Stop a SQL data service.

New Environment VariableThe following table describes the new environment variable:

Command Description

INFA_DEFAULT_SECURITY_DOMAIN Default security domain name that a user belongs to.

50 Chapter 9: Informatica Domain (9.0)

Metadata Manager PrivilegesEffective in version 9.0, Metadata Manager includes the new privilege Draft/Propose Business Terms in theCatalog privilege group. The Manage Glossary privilege includes the Draft/Propose Business Terms privilege.

When you upgrade, users assigned the Manage Glossary privilege are also assigned the Draft/Propose BusinessTerms privilege.

Metadata Manager Privileges 51

C H A P T E R 1 0

PowerCenter (9.0)This chapter includes the following topic:

¨ Reference Table Manager, 52

Reference Table ManagerThis section describes changes to the Reference Table Manager application.

Effective in version 9.0, the Analyst tool contains the Reference Table Manager functionality. You can create andimport reference tables into the Analyst tool.

Previously, PowerCenter had a web application named Reference Table Manager.

After you upgrade to 9.01, you must create the reference tables in the Analyst tool again. The Analyst tool storesreference tables in the staging database. The Reference Table Manager external connections and privileges arenot valid in the Analyst tool.

When you create reference tables in the Analyst tool, a developer can view these tables in the the Developer tool.A developer can open a reference table to view the contents of the reference table and use them in Lookup andStandardizer transformations. A developer can launch the Analyst tool from the Developer tool to edit thereference table.

52

C H A P T E R 1 1

Metadata Manager (9.0)This chapter includes the following topics:

¨ Business Glossary, 53

¨ mmcmd Command Line Program, 53

¨ Data Lineage, 54

¨ Logging, 54

¨ Resources, 55

Business GlossaryEffective in version 9.0, you create links between business terms and reference tables by associating a businessterm with a URL to a reference table. You can specify the following types of URLs:

¨ Informatic a Analyst URL. You can include a URL to a reference table in Informatica Analyst.

¨ Other URL. You can include any valid URL to a reference table.

Previously, you created a link from a business term in Metadata Manager to a reference table in Reference TableManager. Reference Table Manager does not exist in version 9.0.

mmcmd Command Line ProgramEffective in version 9.0, mmcmd includes new commands.

The following table describes the new mmcmd commands:

Command Description

assignConnection Configures connection assignments for a resource using the properties in the specified resourceconfiguration file.

assignParameterFile Assigns parameter files to PowerCenter workflows for a PowerCenter resource using theproperties in the specified resource configuration file.

cancel Cancels a resource load.

53

Command Description

createRepository Creates the Metadata Manager warehouse tables and import models for metadata sources inthe Metadata Manager repository.

createResource Creates a resource using the properties in the specified resource configuration file.

deleteRepository Deletes Metadata Manager repository content including all metadata and repository databasetables.

deleteResource Deletes the resource and all metadata for the resource from the Metadata Manager repository.

export Exports a custom resource or business glossary from the Metadata Manager repository to anXML file.

getResource Writes all properties for the specified resource to an XML resource configuration file.

import Imports a custom resource or business glossary from an XML file into the Metadata Managerrepository.

link Creates the links between resources that share a connection assignment to run data lineageanalysis across the metadata sources.

listResources Lists all resources in the Metadata Manager repository.

purgeMetadata Deletes metadata for a resource from the Metadata Manager repository.

restorePCRepository Restores a repository backup file packaged with PowerCenter to the PowerCenter repositorydatabase.

updateResource Updates a resource using the properties in the specified resource configuration file.

Data LineageEffective in version 9.0, a data lineage diagram displays the database schema name as the parent object of atable, view, or synonym.

Previously, a data lineage diagram did not display the database schema name. Instead, Metadata Managerdisplayed the schema name in the location of the object. You could view the object location in the Details paneland when you moved the pointer over the object.

LoggingEffective in version 9.0, the Load Monitor is renamed the Load Details tab. The Load Details tab contains thefollowing views:

¨ Log view. Contains resource load events. Metadata Manager updates the Log tab as it loads a resource.

¨ Objects view. Contains summary information for metadata objects.

¨ Errors view. Contains summary information for errors.

54 Chapter 11: Metadata Manager (9.0)

¨ Sessions view. Contains session statistics for each session in the PowerCenter workflows that MetadataManager uses to load metadata.

¨ Links view. Contains summary information for links created between objects in connected resources.

You can export all of the contents in the Load Details tab to a single Microsoft Excel file. The file contains aworksheet for each view. You can export the contents of the Links view separately to analyze the missing linkdetails.

Previously, the Load Monitor listed the object, link, and error information in the Summary tab. You saved each tabin the Load Monitor window to a separate PDF file.

After you upgrade, the Load Details tab for all resources displays "No items to show" until you reload theresources.

ResourcesThis section describes changes to resources.

Removed Resource TypesEffective in version 9.0, Metadata Manager removed the following resource types:

¨ Data Analyzer

¨ Hyperion Essbase

¨ IBM DB2 CubeViews

¨ Microsoft Visio Database ERX

You cannot create or load these resource types.

Deprecated Metadata Source VersionsEffective in version 9.0, extracting metadata from the following metadata source versions is deprecated and willbecome obsolete:

¨ Business Objects 5.x, 6.x, and 11.0

¨ Cognos 8.0 and 8.1

¨ Cognos Impromptu 7.0.x, 7.1.5, and 7.3.x

¨ Cognos ReportNet 1.x

¨ Embarcadero ERStudio 5.1 through 6.6

¨ ERwin 3.x and 4.x

¨ IBM DB2 for LUW 8.x

¨ IBM DB2 for z/OS 8.x

¨ IBM Rational Rose 4.0, 98(I) to 2000

¨ Microsoft SQL Server 2000

¨ Microstrategy 7.0, 7.5.2, and 8.0

¨ Oracle Designer 1.3.2, 2.1.2, 6.0, 6i, and 9i

¨ Sybase PowerDesigner 6.1.x, 7.5 to 12.0

Resources 55

¨ Teradata v2R6 and v2R6.1

Use the supported versions to load metadata from these sources. You can still create, edit, and load resourcesfrom these deprecated versions. However, Informatica cannot help you resolve an issue encountered on adeprecated version.

Linking Objects in Connected ResourcesEffective in version 9.0, if you change resource connection assignments, you do not need to reload the resource tocreate the links between matching objects for data lineage analysis. You can use the Resource Link Administrationwindow to direct Metadata Manager to create the links between matching objects in the connected resources.

After upgrading, you must reload the following resource types:

¨ Relational database resources that share a connection assignment to any data integration, businessintelligence, or data modeling resource

¨ Data integration resources

¨ Business intelligence resources

¨ Data modeling resources

Previously, you needed to reload resources after modifying the connection assignments.

Connection Assignments for Purged ResourcesEffective in version 9.0, Metadata Manager keeps connection assignments for a purged resource. The ConnectionAssignment properties display the schema status as purged. If you reload the resource, Metadata Managerchanges the status to active if the schema still exists in the source.

Previously, Metadata Manager deleted connection assignments for a purged resource.

Automatic Connection AssignmentEffective in version 9.0, Metadata Manager can automatically configure connection assignments for a dataintegration, business intelligence, or data modeling resource. Metadata Manager configures the connectionassignments during a resource load or link process. Use the Links view in the Load Details tab to review theautomatic connection assignments and change the assignments as needed. Or, you can manually configure theconnection assignments.

Upgraded resources do not have Auto Connection Assignment selected by default.

Previously, you needed to manually configure connection assignments after creating a resource.

PowerCenter Source Increment Extract WindowEffective in version 9.0, the maximum value of the Source Increment Extract Window parameter for a PowerCenterresource is 8,000 days.

Previously, the maximum value was 4,000 days. PowerCenter resources that are upgraded retain the previousvalue of the parameter. Change the parameter value to extract PowerCenter metadata for more than the past4,000 days.

56 Chapter 11: Metadata Manager (9.0)

PowerCenter Parameter FilesEffective in version 9.0, Metadata Manager can extract workflow parameters from PowerCenter parameter fileswhen you load a PowerCenter resource. When you configure a PowerCenter resource, you can upload multiplePowerCenter parameter files at the same time.

Previously, Metadata Manager ignored workflow parameters in PowerCenter parameter files.

Resources 57

Part III: Version 8.6.1This part contains the following chapters:

¨ New Features and Enhancements (8.6.1), 59

¨ Integration Service (8.6.1), 65

¨ Command Line Programs (8.6.1), 68

¨ Web Services Provider (8.6.1), 70

¨ Mapping Analyst for Excel (8.6.1), 71

¨ Metadata Manager (8.6.1), 74

¨ Data Analyzer (8.6.1), 78

¨ Adapters for PowerCenter (8.6.1), 79

58

C H A P T E R 1 2

New Features and Enhancements(8.6.1)

This chapter includes the following topics:

¨ Version 8.6.1 HotFix 8, 59

¨ Version 8.6.1 HotFix 3 , 59

¨ Version 8.6.1 HotFix 2 , 60

¨ Version 8.6.1 HotFix 1, 60

¨ Version 8.6.1, 61

Version 8.6.1 HotFix 8This section describes new features and enhancements in version 8.6.1 HotFix 8.

Metadata ManagerYou can configure the index and search properties in imm.properties to improve Metadata Manager performanceduring indexing and search operations.

Version 8.6.1 HotFix 3This section describes new features and enhancements in version 8.6.1 HotFix 3.

Data Masking¨ Substitution masking.You can configure substitution masking in the Data Masking transformation.

Substitution masking replaces a column of data with similar but unrelated data. When you configuresubstitution masking, define a relational table or flat file dictionary that contains the substitute values. The DataMasking transformation replaces source data with data from the diction

You can substitute data with repeatable or non-repeatable values. When you choose repeatable values, theData Masking transformation produces deterministic results for the same source data and seed value.

59

¨ Repeatable expression masking. You can configure repeatable expression masking in the Data Maskingtransformation. Use repeatable expression mapping when a source column occurs in more than one table andyou need to mask the column from each table with the same value.

When you configure repeatable expression masking, the Integration Service saves the results of an expressionin a storage table. If the column occurs in another source table, the Integration Service returns the maskedvalue from the storage table instead of from the expression.

Metadata ManagerYou can extract all universes from a Business Objects resource and all models from a Cognos ReportNet ContentManager resource when you load the resources into the Metadata Manager warehouse.

Version 8.6.1 HotFix 2This section describes new features and enhancements in version 8.6.1 HotFix 2.

PowerExchange for MSMQYou can define whether the MSMQ queue is transactional or not. Configure the Is Transactional connectionattribute to match the queue configuration.

Select Yes, No, or Auto. When you choose Auto, the Integration Service determines if the queue is transactionalor not. You can choose Auto for a local queue or a remote queue that is not private. When a session writes to aremote private queue, the Integration Service cannot determine whether the queue is transactional or not.

Version 8.6.1 HotFix 1This section describes new features and enhancements in version 8.6.1 HotFix 1.

PowerExchange for JMS¨ Static or Dynamic JMS Destination Name. You can configure a JMS target with a static or dynamic

destination name.

When you configure a JMS target with a static destination name, the Integration Service creates the JMS targetwith the destination name from the JMS application connection. The Integration Service sends all messages tothat destination.

When you configure a JMS target with a dynamic destination name, the JMS target receives the destinationname in the JMSDestination port at run time. The destination name is passed to the JMS target with other JMSheader data.

60 Chapter 12: New Features and Enhancements (8.6.1)

¨ Transacted Mode for JMS Sources. You can configure a JMS session to run in Transacted or Non-Transacted mode.

When you configure a JMS session to run in Transacted mode, the Integration Service receives and processesa group of messages as a transaction. The Integration Service acknowledges all the messages by committingthe transaction. If a transaction rolls back, the JMS provider redelivers all the messages to the IntegrationService.

When you configure a JMS session to run in Non-Transacted mode, the Integration Service uses theCLIENT_ACKNOWLEDGE method to acknowledge messages. When the Integration Service acknowledgesone message in the JMS session, then all the messages are acknowledged by default. PowerCenter JMSsessions run in Non-Transacted mode by default.

Web Services HubYou can specify the password for the keystore file when you create a Web Services Hub running in HTTPS mode.

When you create the Web Services Hub in the Administration Console, specify the password for the keystore filein the KeystorePass property. The value of the KeystorePass property must match the password of the keystorefile. If you change the password of the keystore file, change the value of the KeystorePass property in theAdministration Console.

When you apply 8.6.1 HotFix 1, the value of the KeystorePass property of existing Web Services Hubs is null. Inthe Administration Console, the null password displays ***. The existing secure Web Services Hubs use thedefault password changeit for the keystore files. If you change the password of the keystore file associated with anexisting secure Web Services Hub, change the value of the KeystorePass property to match the new password.

Version 8.6.1This section describes new features and enhancements in version 8.6.1.

Administration Console¨ Generate and upload node diagnostics. You can use the Administration Console generate node diagnostics

for a node and upload them to the Configuration Support Manager on http://mysupport.informatica.com. In theConfiguration Support Manager, you can diagnose issues in your Informatica environment and maintain detailsof your configuration.

Command Line Programs¨ New pmrep command. The pmrep command line program includes a new command, MassUpdate. Use

MassUpdate to update a set of sessions based on specified conditions.

Deployment Groups¨ Non-versioned repository. You can create and edit deployment groups and copy deployment groups to non-

versioned repositories. You can copy deployment groups between versioned and non-versioned repositories.When you copy a dynamic deployment group, the Repository Service converts it to a static deployment group.For a non-versioned repository, if the objects in the deployment group exist in the target repository, thedeployment operation deletes the existing objects and creates new objects.

Version 8.6.1 61

¨ Execute Deployment Groups privilege. The Execute Deployment Groups privilege enables you to copy adeployment group without the write permission on target folders. You still need read permission on the sourcefolders and execute permission on the deployment group to copy the deployment group.

¨ Post-deployment validation. Validate the target repository after you copy a deployment group to verify thatthe objects and dependent objects are valid.

Domains¨ License Management Report. Monitors the number of software options purchased for a license and the

number of times a license exceeds usage limits. The License Management Report displays the license usageinformation such as CPU and repository usage and the node configuration details.

Integration ServiceThis section describes new features and enhancements for the Integration Service.

External Loading¨ IBM DB2 EE external loader. The IBM DB2 EE external loader can invoke the db2load95 executable located

in the Integration Service installation directory. If the IBM DB2 client version 9.5 is installed on the machinewhere the Integration Service process runs, specify the db2load95 executable when you create the externalloader connection.

Partitioning¨ Oracle subpartition support. PowerCenter supports Oracle sources that use composite partitioning. If you

use dynamic partitioning based on the number of source partitions in a session with a subpartitioned Oraclesource, the Integration Service sets the number of partitions to the total number of subpartitions at the source.

Pushdown Optimization¨ Pushdown compatible connections. When a transformation processes data from multiple connections, the

Integration Service can push the transformation logic to the source or target database if the connections arepushdown compatible. Two connections are pushdown compatible if they connect to databases on the samedatabase management system and the Integration Service can unambiguously identify the database tables thatthe connections access.

Connection objects are always pushdown compatible with themselves. Additionally, some relationalconnections are pushdown compatible if they are of the same database type and have certain identicalconnection properties.

¨ Subquery support. The Integration Service can produce SQL statements that contain subqueries. This allowsit to push transformations in certain sequences in a mapping to the source or target when the session isconfigured for source-side or full pushdown optimization.

¨ Netezza support. You can push transformation logic to Netezza sources and targets that use ODBCconnections.

Real-time¨ JMS resiliency. Sessions that fail with JMS connection errors are now resilient if recovery is enabled. You can

update the pmjmsconnerr.properties file which contains a list of messages that define JMS connection errors.

62 Chapter 12: New Features and Enhancements (8.6.1)

¨ Streaming XML. You can configure the Integration Service to stream XML data between a JMS or WebSphereMQ source and the XML Parser transformation. When the Integration Service streams XML data, it splits thedata into multiple segments. You can configure a smaller input port in the XML Parser transformation andreduce the amount of memory that the XML Parser transformation requires to process large XML files.

¨ Synchronized dynamic cache. You can configure multiple real-time sessions to access the same lookupsource table. Each session has a Lookup transformation that shares the lookup source with the other sessions.When one session generates data and updates the lookup source, then each session can update its own cachewith the same information.

Metadata Manager¨ Business glossary. You can create business terms organized by category in a business glossary and add the

business terms to metadata objects in the Metadata Manager metadata catalog. Use a business glossary toadd business terms to the technical metadata in the metadata catalog. You can import and export businessglossaries using Microsoft Excel.

¨ User interface. The Browse page in Metadata Manager contains the Catalog, Business Glossary, andShortcuts views. Use the views to browse and view details about metadata objects, categories and businessterms, and shortcuts in Metadata Manager. In addition, the Details section contains a single view of allproperties for metadata objects and business terms.

¨ Resources. Metadata Manager added the following resources:

- ERwin. Extract logical models from ERwin.

- Oracle Business Intelligence Enterprise Edition. Extract metadata from OBIEE.

¨ Load Monitor. The Load Monitor updates the current status and load events and contains summaryinformation for objects, links, and errors as you load a resource. It also displays session statistics forPowerCenter workflows.

¨ Error messages. Metadata Manager includes improved error messages to display the cause of errors whenyou create and configure resources.

¨ Data lineage. You can publish a complete data lineage diagram to a Microsoft Excel file.

¨ Migrate custom resource templates. You can migrate custom resource templates between MetadataManager instances.

¨ Object Relationships Wizard. Use the Object Relationships Wizard to create relationships by matchingmetadata objects by any property. You can also use the Object Relationships Wizard to create relationshipsbetween categories and business terms to technical metadata in the metadata catalog.

Upgrade Services¨ Upgrade services to the latest version. You can use the Upgrade Services tab to upgrade the Repository

Service and its dependent services to the latest version.

Data Masking¨ Expression masking. You can create an expression in the Data Masking transformation to mask a column.

¨ Key masking. You can configure key masking for datetime values. When you configure key masking for adatetime column, the Data Masking transformation returns deterministic data.

¨ Parameterizing seed values. You can use a mapping parameter to define a seed value when you configurekey masking. If the parameter is not valid, the Integration Service uses a default seed value from thedefaultValue.xml file.

Version 8.6.1 63

¨ Masking Social Security numbers. You can mask a Social Security number in any format that includes ninedigits. You can configure repeatable masking for Social Security numbers.

¨ Company Names Sample Data. The Data Masking installation includes a flat file that contains companynames. You can configure a Lookup transformation to retrieve random company names from the file.

Web Services Hub¨ Web service security. The Web Services Hub security for protected web services is based on the OASIS web

service security standards. By default, WSDLs generated by the Web Services Hub for protected web servicescontain a security header with the UsernameToken element. The web service client request can use plain text,hashed password, or digested password security.

PowerExchange for Netezza¨ Parameters and variables. You can use parameters and variables for the Null Value, Escape Character, and

Delimiter session properties.

PowerExchange for SAP NetWeaver¨ Row-level processing. The Integration Service can process each row of an outbound IDoc according to the

IDoc metadata and pass it to a downstream transformation. Row-level processing can increase sessionperformance.

¨ Viewing ABAP program information. You can view ABAP program information for all mappings in therepository folder.

PowerExchange for Web Services¨ Importing WSDLs with orchestration. You can import a WSDL file generated by orchestration as a web

service source, target, or transformation.

64 Chapter 12: New Features and Enhancements (8.6.1)

C H A P T E R 1 3

Integration Service (8.6.1)This chapter includes the following topics:

¨ Performance, 65

¨ Partitioning, 67

¨ FastExport, 67

PerformanceThis section describes changes to Integration Service performance.

Date FormatsEffective in version 8.6.1 HotFix 4, the Pre 85 Timestamp Compatibility option enables pre-85 behavior ofpushdown optimization to Teradata when converting dates.

By default, the Pre 85 Timestamp Compatibility option is disabled. The session fails when the option is disabled,Teradata does not support the specified date format, and you push the one of the following date functions orconversions to Teradata:

¨ TO_CHAR or TO_DATE functions

¨ Date-to-string or string-to-date conversions

When you enable the option and specify the default date format for one of the date functions or conversions, theIntegration Service pushes the functions and conversions to Teradata.

When you enable the option and specify a non-default date format, the Integration Service processes thetransformation.

Between versions 8.5 and 8.6.1 HotFix 3, regardless of the Pre 85 Timestamp Compatibility option setting, thesession fails when you specify a date format that Teradata does not support. When you specify a supported dateformat, the Integration Service pushes the date function or conversion to Teradata.

For versions earlier than 8.5, the Integration Service pushes the date functions and conversions to Teradata whenyou use the default date format. When you specify a non-default format, the Integration Service processes thetransformation.

Pushdown CompatibilityEffective in version 8.6.1, when a transformation processes data from multiple connections, the Integration Servicecan push the transformation logic to the source or target database if the connections are pushdown compatible.

65

Two connections are pushdown compatible if they connect to databases on the same database managementsystem and the Integration Service can unambiguously identify the database tables that the connections access.

Each connection object is always pushdown compatible with itself. Additionally, IBM DB2, Microsoft SQL Server,Oracle, Sybase ASE, and Teradata connections are pushdown compatible if they are of the same database type,have the same database user name and password, and have certain identical properties. If the database usernames and passwords differ, you can configure the connections to be pushdown compatible in somecircumstances.

Previously, each connection was pushdown compatible only with itself.

Because pushdown compatibility in version 8.6.1 is less restrictive than in previous versions, the IntegrationService might push transformation logic to the database differently in sessions that contain different, butcompatible, connection objects.

The source and target are Teradata databases with the same database user name, password, code page, datasource name, and connection and transaction environment SQL, but different database names. The expressioncan be pushed to either the source or target.

In version 8.6.1, the source and target are pushdown compatible. Therefore, the Integration Service pushes thetransformation logic to the target. Previously, the source and target were not pushdown compatible because thedatabase names differ. Therefore, pushdown processing stopped at the target, and the Integration Service pushedthe transformation logic to the source.

Pushdown Subquery SupportEffective in version 8.6.1, the Integration Service can produce SQL statements that contain subqueries. Thisallows the Integration Service to push the following transformations to the source or target database when thesession is configured for source-side or full pushdown optimization:

¨ Aggregator transformations that are upstream from Aggregator, Joiner, or connected Lookup transformations

¨ Transformations downstream from a Union transformation

Previously, the Integration Service processed an Aggregator, Joiner, or Lookup transformation if it wasdownstream from an Aggregator transformation. It also processed any transformation downstream from a Uniontransformation.

Pushdown Support for NetezzaEffective in version 8.6.1, the Integration Service can push transformation logic to Netezza sources and targetsthat use ODBC connections. If you have sessions configured for full pushdown optimization that contain Netezzasources or targets, the Integration Service might push some transformation logic to the Netezza database.

For example, you have a mapping with an Oracle source and a Netezza target configured for full pushdownoptimization. In version 8.6.1, the Integration Service might push some transformation logic to the source andsome to the target. Previously, the Integration Service could push transformation logic to the source only.

Oracle Bulk Load Buffer SizeEffective in version 8.6.1, the minimum size of the OCI buffer that the Integration Service requests when it insertsdata into Oracle target tables in bulk mode is based on the default buffer block size. This allows the buffer to holdall of the rows in the input block. Increasing the buffer size reduces the number of bulk load transactions, whichimproves session performance.

Previously, the Integration Service set the minimum buffer size to the size of one row, which is usually lower thanthe OCI default minimum size of 64 KB.

66 Chapter 13: Integration Service (8.6.1)

PartitioningEffective in version 8.6.1, sessions that read data from subpartitioned Oracle sources and use dynamic partitioningset the number of source partitions to the maximum number of database subpartitions. For example, if a sessionconfigured for dynamic partitioning contains an Oracle source with three partitions and two subpartitions for eachpartition, the Integration Service sets the number of source partitions to six.

This change increases the number of processing threads. Therefore, this change can increase processingperformance if there is enough CPU bandwidth on the node. If there is not enough CPU bandwidth on the node,the node can be overloaded.

Previously, the Integration Service set the number of source partitions to the maximum number of databasepartitions.

IBM DB2 Range PartitioningEffective in version 8.6.1 HotFix 11, you can configure database partitioning for IBM DB2 sources and targets thatuse range partitioning.

FastExportEffective in version 8.6.1, FastExport maps the “MS Windows Latin 1 (ANSI), superset of Latin1” connection codepage to the Latin1252_0A Teradata character set. By default, the Latin1252_0A character set is not enabled onthe Teradata database. Teradata character sets must be enabled on the database before you can use them.

Previously, FastExport mapped the “MS Windows Latin 1 (ANSI), superset of Latin1” connection code page to theASCII Teradata character set. By default, the ASCII character set is enabled on the Teradata database. When youupgrade FastExport sessions using the “MS Windows Latin 1 (ANSI), superset of Latin1” connection code page,you must enable the Latin1252_0A character set on the Teradata database or the sessions fail.

Partitioning 67

C H A P T E R 1 4

Command Line Programs (8.6.1)This chapter includes the following topics:

¨ infasetup Changed Commands, 68

¨ pmrep Changed Commands, 69

¨ pmrep New Commands, 69

¨ infacmd isp Changed Commands, 69

infasetup Changed CommandsEffective in version 8.6.1, some infasetup commands can use the -PreviousInfaHome (-ph) option to specify aprevious installation directory. Set the previous PowerCenter installation directory to run multiple service versionson the node.

The following table lists the changed infasetup commands:

Command Description Comments

DefineGatewayNode Defines a gateway node on thecurrent machine.

-PreviousInfaHome (-ph) option added to specify a previousinstallation directory. Set the previous PowerCenterinstallation directory to run multiple service versions on thenode.

DefineWorkerNode Defines a worker node on thecurrent machine.

-PreviousInfaHome (-ph) option added to specify a previousinstallation directory. Set the previous PowerCenterinstallation directory to run multiple service versions on thenode.

UpdateGatewayNode Updates connectivityinformation for a gateway nodeon the current machine.

-PreviousInfaHome (-ph) option added to specify a previousinstallation directory. Set the previous PowerCenterinstallation directory to run multiple service versions on thenode.

UpdateWorkerNode Updates connectivityinformation for a worker nodeon the current machine.

-PreviousInfaHome (-ph) option added to specify a previousinstallation directory. Set the previous PowerCenterinstallation directory to run multiple service versions on thenode.

68

pmrep Changed CommandsEffective in version 8.6.1, pmrep commands have changed. The commands have new or modified options.

The following table lists the changed pmrep commands:

Command Description Comments

AddToDeploymentGroup Adds objects to a deployment group. Enabled for non-versioned repositories. To usethe command for a non-versioned repository, donot specify the “-v” option.

AssignPermission Assigns permissions on a global object. You can specify “Others” as the group name toassign permissions to the default group.

ClearDeploymentGroup Clears all objects from a deploymentgroup.

Enabled for non-versioned repositories.

CreateDeploymentGroup Creates a deployment group. Enabled for non-versioned repositories.

DeleteDeploymentGroup Deletes a deployment group. Enabled for non-versioned repositories.

DeployDeploymentGroup Copies a deployment group from asource repository to a target repository.

Enabled for non-versioned repositories.

pmrep New CommandsThe following table lists the new pmrep command:

Command Description Comments

MassUpdate Updates session properties across multiple sessions. New command.

infacmd isp Changed CommandsEffective in version 8.6.1, the UpdateServiceProcess command can use the -ProcessEnvironmentVariables (-ev)option to add or update custom environment variables for a service process. You can provide multiple environmentvariables at a time.

pmrep Changed Commands 69

C H A P T E R 1 5

Web Services Provider (8.6.1)This chapter includes the following topics:

¨ Web Service Security, 70

¨ Deprecated Web Service Operations, 70

Web Service SecurityEffective in version 8.6.1, the default security for protected web services uses the user name token. The webservice client request can use the following password security:

¨ Plain text

¨ Hashed password

¨ Digested password

Previously, the default security for protected web services was user credentials.

You can still use user credential security for protected web services in version 8.6.1. Client applications built onWSDLs generated in PowerCenter version 8.6 or earlier can log in and get a SessionID to run protected services.The Web Services Hub processes the SOAP request in the same way as in previous versions.

Deprecated Web Service OperationsEffective in version 8.6.1, the following operations are deprecated:

¨ startSessionLogFetch

¨ startWorkflowLogFetch

¨ getNextLogSegment

70

C H A P T E R 1 6

Mapping Analyst for Excel (8.6.1)This chapter includes the following topics:

¨ Matching Criteria for Custom Metamaps, 71

¨ Import Options, 72

¨ Export Options, 72

¨ Custom File Naming Conventions and Storage Location, 73

Matching Criteria for Custom MetamapsEffective in version 8.6.1 HotFix 3, the Overview worksheet in a metamap contains a Match Criteria section. Thissection contains references to several cells in the associated mapping specification template. When you import amapping specification or export a mapping, Mapping Analyst for Excel uses the Match Criteria section to detectthe associated metamap for the mapping specification.

When you create a custom metamap, you must edit the Match Criteria section to use matching criteria thatuniquely identifies the associated mapping specification template. You can use up to five matching criteria.

The Match Criteria section includes the following parameters:

Parameter Description

Spreadsheet Match Criteria Name of the matching criteria. For example, you can enter the name of the worksheet andidentifying cell in the mapping specification template.

Contents Contents of the identifying cell in the mapping specification template. Enter the name ofthe cell in the mapping specification template.

Link Contains the location of the identifying cell in the mapping specification template. Copyand paste the cell location from the mapping specification template.

Previously, a metamap Overview worksheet did not contain a Match Criteria section. When you imported amapping specification or exported a mapping, you selected the correct mapping specification template andassociated metamap.

After you apply 8.6.1 HotFix 3, add matching criteria to custom metamaps. Enter values for the parameters toidentify the associated mapping specification template.

71

Import OptionsEffective in version 8.6.1 HotFix 3, when you import a mapping specification, you select the mapping specificationfile to import. Mapping Analyst for Excel detects the associated metamap for the mapping specification.

Previously, when you imported a mapping specification, you selected the mapping specification file to import andthe XML version of the associated metamap.

Export OptionsEffective in version 8.6.1 HotFix 3, the following options are new in the Microsoft Office Excel Options page of theMetadata Export Wizard:

Microsoft Excel Option Description

Operation Type of export operation to perform. Select one of the following options:- Create. Exports all metadata to a new or an existing mapping specification.- Update Sources. Exports source metadata to an existing mapping specification.- Update Targets. Exports target metadata to an existing mapping specification.Default is Create.

Format Format name of the metamap associated with the mapping specification template you want touse. Enter one of the following metamap values:- MappingTemplate- MappingTemplate_NoValidation- source-target-matrix- <custom-metamap-format-name>. For example, if the metamap is named MyCustom-

MetaMap.xml, enter MyCustom.If you do not enter a format, Mapping Analyst for Excel uses the Default format that specifiesDefault-MetaMap.xml.

The new Format export option replaces the following deprecated options in the Microsoft Office Excel Optionspage of the Metadata Export Wizard:

Microsoft Excel Option Description

With metadata mappingspreadsheet

Metamap associated with the mapping specification template you want to use. Click the Valuefield to locate and select one of the following metamaps:- MappingTemplate-MetaMap.xml- source-target-matrix-metamap.xml- <custom-metamap>.xml

From base spreadsheet Mapping specification template. Click the Value field to locate and select one of the followingmapping specification templates:- MappingTemplate.xls- MappingTemplate_NoValidation.xls- source-target-matrix-mirrepeatingsheet.xls- <custom-template>.xls

72 Chapter 16: Mapping Analyst for Excel (8.6.1)

Custom File Naming Conventions and Storage LocationEffective in version 8.6.1 HotFix 3, custom Mapping Analyst for Excel files use the following naming conventions:

File 8.6.1 HotFix 3 Naming Convention Previous NamingConvention

Custom metamap <format-name>-MetaMap.xmlFor example, MyCustom-MetaMap.xml is a valid metamap name.<format-name> must match <format-name> of the associated blankversion of the custom mapping specification template.

none

Blank version ofcustom mappingspecification template

<format-name>-Blank.xlsFor example, MyCustom-Blank.xls is a valid name for the blank versionof a custom mapping specification template. <format-name> mustmatch <format-name> of the associated metamap.

none

Source-Target-Matrixrepeating sheet file

source-target-matrix-Blank.xls source-target-matrix-mirrepeatingsheet.xls

Effective in version 8.6.1 HotFix 3, these custom files are stored in the following location:

<PowerCenter Installation Directory>\client\bin\mimb\conf\MIRModelBridgeTemplate\

MIRMicrosoftExcel

Previously, these files were stored in the following location:

<PowerCenter Installation Directory>\client\bin\Sample Specifications

After you apply 8.6.1 HotFix 3, rename custom metamaps and create blank versions of custom mappingspecification templates using the naming conventions. Copy the custom files to the following location:

<PowerCenter Installation Directory>\client\bin\mimb\conf\MIRModelBridgeTemplate\

MIRMicrosoftExcel

Then, associate the custom metamap with the new name of the blank version of the mapping specificationtemplate to maintain the metamap links to the mapping specification template.

Custom File Naming Conventions and Storage Location 73

C H A P T E R 1 7

Metadata Manager (8.6.1)This chapter includes the following topics:

¨ Terminology Changes, 74

¨ Data Lineage, 74

¨ Logging, 75

¨ Metadata Objects, 75

¨ Resources, 76

¨ URL API, 77

Terminology ChangesEffective in version 8.6.1, Metadata Manager includes the following terminology changes:

Previous Term New Term

Annotation Comment

Supporting Document Link

Data LineageThis section describes changes to data lineage.

Lookup TransformationEffective in version 8.6.1, Metadata Manager does not display input ports that are not used in the lookup conditionfor lookups. As a result, the total number of objects displayed when you launch a data lineage diagram mayincrease and the total number of connections displayed between elements may decrease. This behavior appears ifyou reload a PowerCenter resource and view a data lineage diagram.

Previously, Metadata Manager displayed all input ports for a lookup in the data lineage diagram.

74

PublishingEffective in version 8.6.1, you can publish a data lineage diagram to a Microsoft Excel file.

Previously, you could only publish data lineage diagram to a PNG file.

Expanding Metadata ObjectsEffective in version 8.6.1, you can use the Full Expand command to expand a metadata object and all child objectsin a data lineage diagram.

Previously, the data lineage diagram required you to expand each metadata object separately.

LoggingEffective in version 8.6.1, the Load Monitor contains the following tabs:

¨ Log tab. Contains resource load events. Metadata Manager updates the Log tab as it loads a resource.

¨ Summary tab. Contains summary information for objects, links, and errors.

¨ Session Statistics tab. Contains session statistics for each session in the PowerCenter workflows thatMetadata Manager uses to load metadata.

Previously, the Load Monitor only displayed high-level events about a resource load and did not report statisticsabout the resource load.

Metadata ObjectsThis section describes changes to metadata objects.

Viewing DetailsEffective in version 8.6.1, the Definition tab in the Details section contains the following details about metadataobjects, depending on the object type:

¨ Properties

¨ Shortcut Properties

¨ Related Catalog Objects

¨ Links

¨ Comments

¨ Profile

Previously, Metadata Manager displayed the details in the following tabs that no longer appear:

¨ At-A-Glance

¨ Relationships

¨ Annotations

¨ Supporting Documents

Logging 75

¨ Profiling

Metadata Catalog and ShortcutsEffective in version 8.6.1, you can access the metadata catalog and shortcuts from the Catalog and Shortcutsviews.

Previously, the metadata catalog and shortcuts appeared in separate sections on the Browse page.

Object Relationships WizardEffective in version 8.6.1, you can configure the Object Relationships Wizard to match any object property when itsearches for objects to create relationships between.

Previously, the Object Relationships wizard only matched metadata objects by object name.

SearchesEffective in version 8.6.1, Metadata Manager indexes comments for metadata objects. You can use keyword oradvanced search to search for text in comments.

To access this change immediately, manually update the resource indexes. Metadata Manager also updates eachresource index when you import or update a resource. Previously, Metadata Manager did not index comments.

ResourcesThis section describes changes to resources.

Business Intelligence ResourcesEffective in 8.6.1 HotFix 10, the Connection Assignment tab for a business intelligence resource includes a UseSchema Prefix property. If you enable this option, Metadata Manager uses the schema name in the businessintelligence model to link objects in connected relational database resources. If you disable this option, MetadataManager does not use the business intelligence schema name to link objects. Metadata Manager can link objectsto any relational database schema that contains all of the tables used by the business intelligence model. Disablethis option if you did not extract the actual relational database schemas, but extracted other schemas that containthe same content.

Previously, Metadata Manager could not use the business intelligence schema name to link objects in connectedrelational database resources.

Business Objects Configuration PropertiesEffective in 8.6.1 HotFix 10, you do not need to configure the JAVA API Path configuration property. MetadataManager automatically detects the path. Previously, you needed to enter the JAVA API Path for Business Objectsresources.

Effective in 8.6.1 HotFix 10, use the System property to enter the name of the machine where Business Objects isinstalled and the Business Objects Central Management Server port number on that machine. Previously, youused the Repository Name property to enter the name of the Business Objects repository that you wanted toconnect to.

76 Chapter 17: Metadata Manager (8.6.1)

Dropped Objects in an Oracle SchemaEffective in 8.6.1 HotFix 10, Metadata Manager does not extract dropped tables, constraints, triggers, or indexesfrom an Oracle schema.

Previously, Metadata Manager did extract dropped tables, constraints, triggers, and indexes.

Teradata HierarchyEffective in 8.6.1 HotFix 10, Metadata Manager no longer extracts the Teradata hierarchy of databases and users.Teradata organizes databases and users under the DBC user. You do not need to export the entire hierarchy fromthe DBC user to the metadata that you want to view.

Previously, to browse metadata in a Teradata database catalog, you had to export the entire hierarchy from theDBC user to the metadata that you wanted to view.

ERwinEffective in version 8.6.1, the existing ERwin resource is deprecated and will become obsolete. You must use thenew ERwin resource to load metadata from ERwin.

URL APIThis section describes changes to the URL API.

Business GlossaryEffective in version 8.6.1, you can use the URL API to access categories and business terms in a businessglossary.

WildcardsEffective in version 8.6.1, you cannot use wildcards with the URL API. Include the full path of the object for whichyou want to view data lineage or object details.

URL API 77

C H A P T E R 1 8

Data Analyzer (8.6.1)This chapter includes the following topic:

¨ Datasource, 78

DatasourceEffective in version 8.6.1 HotFix 1, you can configure the Datasource edit mode. In advanced edit mode, you canedit Datasource and Dataconnector properties in the Data Analyzer instance. In basic edit mode, you can editDatasource properties in the Administration Console. After you enable the Reporting Service in advanced editmode, you cannot change it back to basic edit mode.

Previously, you could edit Datasource properties in the Data Analyzer instance and in the Administration Console.

78

C H A P T E R 1 9

Adapters for PowerCenter (8.6.1)This chapter includes the following topics:

¨ PowerExchange for Netezza, 79

¨ PowerExchange for Web Services, 79

¨ PowerExchange for SAP NetWeaver, 79

PowerExchange for NetezzaEffective in version 8.6.1, you no longer need to configure the Ignore Key Constraints property to run a Netezzasession with multiple partitions. If you run a partitioned session with key constraints, only one partition shows loadstatistics.

Previously, if you ran a session with multiple partitions, and you did not configure the Ignore Key Constraintsproperty, the session failed.

PowerExchange for Web ServicesEffective in version 8.6.1 HotFix 7, you can configure the SOAP Response Compression property on the Mappingtab in the session properties. You can configure SOAP response compression for web service sources and targetsand Web Service Consumer transformations.

Select one of the following values:

¨ All. The Integration Service enables HTTP response compression.

¨ None. The Integration Service uses no compression. If the Integration Service connects to an IIS web server,set SOAP Response Compression to None.

Default is All.

Previously, sessions running on an IIS web server failed because of incorrect compression in HTTP responseheaders.

PowerExchange for SAP NetWeaverThis section describes changes to PowerExchange for SAP Netweaver.

79

BAPI/RFC TransformationEffective in PowerCenter 8.6.1 HotFix 4, the BAPI/RFC transformation handles CURR, DEC, NUMC, and QUANdata up to the maximum precision of 28.

If a mapping includes CURR, DEC, NUMC, or QUAN data with a precision greater than 15 in a BAPI/RFCtransformation, you must recreate the transformation to display the correct precision and to process high-precisiondata correctly.

Previously, a BAPI/RFC transformation with CURR, DEC, NUMC, or QUAN data displayed a precision of 15 andhandled a maximum precision of 18. When a session that contained CURR, DEC, NUMC, or QUAN data wasconfigured for high-precision, the Integration Service rounded data with a precision over 18. When a session wasnot configured for high precision, the Integration Service rounded data with a precision over 15.

BCI Metadata Connection TypeEffective in PowerCenter 8.6.1 HotFix 6, PowerExchange for SAP NetWeaver provides an SAP_ALE_IDoc_Writerconnection type, BCI Metadata Connection. Use this connection type to run business content integrationprocessing workflows with segments longer than 1,000 characters.

To use the application connection type, complete the following steps:

1. Upgrade and register the pmsapplg.xml plug-in.

2. Create a Type A DEST entry in saprfc.ini.

3. Configure an SAP_ALE_IDoc_Writer application connection that uses the DEST value in the saprfc.ini file.

4. In a business content integration source session, configure the BCI Listener to use the BCI MetadataConnection.

SAP/ALE IDoc Interpreter TransformationEffective in PowerCenter 8.6.1 HotFix 3, the SAP/ALE IDoc Interpreter transformation handles CURR, DEC,NUMC, and QUAN data up to the maximum precision of 28.

To display the correct precision and process high-precision data correctly, regenerate Business ContentIntegration processing mappings that include CURR, DEC, NUMC, or QUAN data with a precision greater than 15in an SAP/ALE IDoc Interpreter transformation. To display the correct precision and process high-precision datacorrectly in other mappings, recreate the SAP/ALE IDoc Interpreter transformation.

Previously, an SAP/ALE IDoc Interpreter transformation with CURR, DEC, NUMC, or QUAN data displayed aprecision of 15 and handled a maximum precision of 18. When a session that contained CURR, DEC, NUMC orQUAN data was configured for high-precision, the Integration Service rounded data with a precision over 18.When a session was not configured for high precision, the Integration Service rounded data with a precision over15.

80 Chapter 19: Adapters for PowerCenter (8.6.1)

Part IV: Version 8.6This part contains the following chapters:

¨ New Features and Enhancements (8.6), 82

¨ PowerCenter (8.6), 87

¨ Metadata Manager (8.6), 93

¨ Data Analyzer (8.6), 96

¨ Adapters for PowerCenter (8.6), 97

81

C H A P T E R 2 0

New Features and Enhancements(8.6)

This chapter includes the following topics:

¨ PowerCenter, 82

¨ Metadata Manager, 85

¨ PowerChannel, 85

¨ Adapters for PowerCenter, 85

PowerCenterThis section describes new features and enhancements to PowerCenter.

Code Pages¨ Compatibility. PowerCenter, PowerExchange, and Complex Data Exchange support the same code pages.

Datatypes¨ Byte. PowerCenter imports the Informix Byte datatype as a Binary transformation datatype. The minimum

value of the Byte datatype is 1 byte. There is no maximum value.

¨ Uniqueidentifier. PowerCenter imports the Microsoft SQL Server uniqueidentifier datatype as a Microsoft SQLServer Varchar datatype of 38 characters.

Designer¨ Workflow Generation Wizard. You can use the Workflow Generation Wizard to create workflows and sessions

from a mapping.

Functions¨ INSTR function string comparisons. When the Integration Service runs in Unicode mode, you can use the

comparison_type argument to specify whether the INSTR function performs linguistic or binary stringcomparisons.

82

Integration ServiceThis section describes new features and enhancements for the Integration Service.

Logging¨ Access log files with the high availability option. If you run a session on a primary node that becomes

unavailable, the Log Manager on the backup node can access log files that are stored in a shared locationspecified by an absolute path.

Parameters and Variables¨ Get the workflow run ID. Use a built-in mapping variable, session parameter, or workflow variable to get the

workflow run ID.

Partitioning¨ Based on number of CPUs. You can configure dynamic partitioning to set the number of partitions equal to

the number of CPUs on the node that prepares the session. If the session is configured to run on a grid,dynamic partitioning sets the number of partitions equal to the number of CPUs on the node that prepares thesession multiplied by the number of nodes in the grid.

Performance¨ View percentage of time a thread spends in each transformation. The session log includes details about

the percentage of time the Integration Service took to process each transformation in a thread.

Real-time Recovery¨ Improved recovery. The Integration Service writes real-time session recovery information to a queue. The

queue helps maintain data integrity during recovery so no data is lost or duplicated.

When you enable recovery for a real-time session that reads from a JMS or WebSphere MQ source and writesto a JMS or WebSphere MQ target, the Integration Service writes recovery information to a recovery queue.The recovery queue stores the reader state, the commit number, and the message ID that the IntegrationService committed to the target. When you recover a session, the Integration Service uses the recoveryinformation to determine where it stopped processing.

The Integration Service also writes recovery information to a recovery ignore list for a failed JMS orWebSphere MQ session. The recovery ignore list stores message IDs that the Integration Service wrote to thetarget for the failed session. The Integration Service writes recovery information to the list if there is a chancethat the source did not receive an acknowledgement. When you recover a session, the Integration Service usesthe recovery ignore list to prevent data duplication.

¨ Partitioning. You can add partitions to a real-time session that includes a JMS or WebSphere MQ source andis enabled for recovery.

¨ Resilience. Resilience is available if you have the real-time option.

PowerCenter 83

Orchestration¨ PowerCenter Orchestration is an application that models business processes with standard Business Process

Modeling Notation (BPMN) and creates executable Business Process Executable Language (BPEL) workflows.You can create an executable workflow from a process diagram without writing BPEL code. The OrchestrationServer executes the workflow.You can create a business process model that includes human tasks.

PowerCenter Orchestration integrates with PowerCenter through web services interfaces. You can call real-time web services or PowerCenter batch web services.

Transformations¨ HTTP. You can let the Integration Service determine the authentication type of the HTTP server when the

HTTP server does not return an authentication type to the Integration Service. Or, you can specify theauthentication type for the Integration Service to use.

¨ Unstructured Data. The Complex Data transformation is renamed to Unstructured Data transformation.Complex Data Exchange is renamed to Data transformation. You can define additional ports and pass outputrows to relational targets from the Unstructured Data transformation. You can create ports by populating thetransformation from a Data Transformation service. You can pass a dynamic service name to the UnstructuredData transformation with source data.

Web Services Hub¨ Processing chunked messages. The Web Services Hub can process chunked messages from web service

clients.

Mapping Architect for Visio (Data Stencil)¨ Name change. Data Stencil is renamed Mapping Architect for Visio.

¨ Terminology changes. Data Integration stencil is renamed to Informatica stencil. Data Integration toolbar isrenamed to Informatica toolbar.

¨ New mapping objects. You can include a Stored Procedure transformation in a mapping template or you cancreate a mapping template from a mapping that contains a Stored Procedure transformation. You can create amapping template from a mapping that contains a mapplet. Or, you can import a mapplet and add the relatedmapping objects to the mapping template. Mapplet properties are read-only.

¨ Shortcuts. You can configure a source definition or a target definition to use a shortcut. You can create amapping template from a mapping that contains shortcuts to sources or targets.

¨ Reusable transformation. You can configure a transformation to be reusable. You can create a mappingtemplate from a mapping that contains a reusable transformation.

¨ Multiple pipeline generation. When you import a mapping template in the Designer, you can create amapping with more than one pipeline.

¨ Workflow Generation Wizard. You can launch the Workflow Generation Wizard from the Import MappingTemplate Wizard.

84 Chapter 20: New Features and Enhancements (8.6)

Metadata Manager¨ Business Name attribute. A metadata object attribute you can use to identify metadata objects according to

their business usage.

¨ Data lineage. You can configure the number of resources that appear when you launch a data lineage diagramand configure the number of resources that appear when you navigate the data lineage diagram.

¨ Export and import custom attributes. Export or import custom attributes and business name attributes forpackaged resource types. You can export custom attributes for metadata objects in a packaged resource typeto an Excel file, edit the attribute values in the Excel file, and import the attributes into the metadata catalog.

¨ Objects Relationship Wizard. Use the Objects Relationship Wizard to create relationships for multiple custommetadata objects in the metadata catalog.

Metadata Exchanges¨ IBM DB2 z/OS. Extract metadata from IBM DB2 z/OS.

¨ Netezza. Extract metadata from Netezza.

Metadata Manager Service¨ Oracle service name. You can specify an Oracle service name or SID for a Metadata Manager repository on

Oracle.

¨ Oracle RAC. You can configure Oracle RAC for a Metadata Manager repository.

PowerChannel¨ Windows EM64T support. You can run a PowerChannel Server on Windows EM64T (64-bit).

Adapters for PowerCenterThis section describes new features and enhancements to adapters for PowerCenter.

PowerExchange for Netezza¨ Linux x86 (64-bit) support. You can extract data from a Netezza source or load data to a Netezza target when

the Integration Service runs on Linux x86 (64-bit).

¨ Update as insert. You can configure a session to insert a row even if it exists in the target.

PowerExchange for SAP NetWeaver BI (BW Option)¨ Name change. PowerExchange for SAP NetWeaver BW Option is renamed PowerExchange for SAP

NetWeaver BI.

Metadata Manager 85

PowerExchange for SAP NetWeaver (mySAP Option)¨ Name change. PowerExchange for SAP NetWeaver mySAP Option is renamed PowerExchange for SAP

NetWeaver.

¨ Real-time sessions with BAPI/RFC transformations. You can run a real-time session when the mappingcontains a BAPI/RFC transformation.

¨ Real-time sessions with SAP/ALE IDoc Prepare transformations. You can run a real-time session when themapping contains an SAP/ALE IDoc Prepare transformation.

¨ Table type parameters. You can import BAPI/RFC transformations from BAPIs that contain table typeparameters.

PowerExchange for Web Services¨ Authentication type configuration. You can let the Integration Service determine the authentication type of

the web service provider when the web service provider does not return an authentication type to theIntegration Service. Or, you can specify the authentication type for the Integration Service to use.

86 Chapter 20: New Features and Enhancements (8.6)

C H A P T E R 2 1

PowerCenter (8.6)This chapter includes the following topics:

¨ Code Pages, 87

¨ Integration Service, 88

¨ LANG Environment Variable for Linux, 90

¨ Mapping Architect for Visio, 91

¨ Mapping Template, 91

¨ Unstructured Data Transformation, 91

Code PagesEffective in version 8.6, the location of the package.bin file has changed. If the package.bin file extension wasrenamed in your previous installation, rename the file in the new file location.

To use 0X15 as the value of the end of line character in the affected IBM EBCDIC code pages, rename thefollowing file in the server\bin\NLS directory and the client\bin\NLS directory of the PowerCenter installationdirectory:

¨ On UNIX, rename package.bin to package.dat.

¨ On Windows, rename package8.5.bin to package8.5.dat.

To apply changes, restart the Designer and Workflow Manager after you rename the file.

Previously, to use 0x15 instead of 0x25 as the value of the end of line character, you could rename the fileextension of the package.bin and package8.5.bin to .dat. Previously, the package.bin and package8.5.bin file waslocated in the server\bin directory and the client\bin directory.

87

Integration ServiceThis section describes changes to the Integration Service.

PerformanceEffective in version 8.6, you can view thread worktime details in the session log. The session log includes detailsabout the percentage of time the Integration Service took to process each transformation in a thread. Use thesestatistics to determine which transformation takes more time than the others.

Previously, to determine which transformation takes more time than the others, you needed to add pass-throughpartition points to all transformations in the mapping. When you added partition points, more transformationthreads appeared in the session log. The bottleneck was the transformation thread that took the most time.

RecoveryThis section describes changes to recovery.

Session RecoveryEffective in version 8.6, you cannot configure a session recovery strategy to resume from the last checkpoint if thesession uses mapping variables.

After you upgrade, the Integration Service terminates sessions that use mapping variables and that have a resumerecovery strategy. To run a terminated session, remove the mapping variables from the session or change thesession recovery strategy.

Transformation RecoveryEffective in version 8.6, the following transformations are updated:

Transformation Property Value (In previous version) Value (In 8.6)

Custom (Passive) Output is Deterministic Property is not editable. Property is editable.

HTTP Output is Deterministic Property is not editable. Property is editable.

HTTP Output is Repeatable Property is not editable. Property is editable.

Java (Active) Output is Repeatable Property is not editable. Property is editable.

Java (Passive)* Output is Deterministic Property is not editable. Property is editable.

SQL (Passive)* Output is Repeatable Property is not editable. Property is editable.

Unstructured Data * Output is Repeatable Property is not editable.Default is Never.

Property is editable. Default isBased on Input Order.

Web ServicesConsumer

Output is Repeatable Default is Always. Default is Based on Input Order.

88 Chapter 21: PowerCenter (8.6)

Transformation Property Value (In previous version) Value (In 8.6)

XML Parser Output is Repeatable Property is not editable.Default is Always.

Property is editable. Default isBased on Input Order.

* Effective in version 8.6, you can specify that the transformation uses repeatable data. Previously, you could not specify thatthe output was repeatable and deterministic. You can configure a session to resume from the last checkpoint whentransformations in the session produce the data that is repeatable and deterministic.

When you upgrade, default values for transformations in the repository will not change. To use new values fortransformations in the repository, update the transformation property.

Real-time ProcessingThis section describes changes to real-time processing.

Recovery Queue and Recovery TopicEffective in version 8.6, when you enable recovery for a real-time session that reads from a JMS or WebSphereMQ source and writes to a JMS or WebSphere MQ target, the Integration Service writes recovery information to arecovery queue or topic. The recovery queue or topic stores the reader state, the commit number, and themessage ID that the Integration Service committed to the target. The recovery queue or topic helps maintain dataintegrity during recovery so no data is lost or duplicated.

When you recover a session, the Integration Service uses the recovery information to determine where it stoppedprocessing messages. The Integration Service reads unprocessed messages from the source by using themessage ID in the recovery queue or topic.

To run upgraded or new sessions, create a recovery queue or topic. For sessions with JMS targets, enter therecovery queue or topic name in the JMS application connection properties. For sessions with WebSphere MQtargets, enter the recovery queue in the session configuration object, session properties, or Integration Serviceproperties.

Previously, when you ran a session, the Integration Service saved message IDs in a recovery file. If the sessionfailed, the Integration Service retrieved unprocessed messages from the source by using the message ID in therecovery file.

Partitioning with Real-time ProcessingEffective in version 8.6, you can create multiple partitions for a JMS or WebSphere MQ real-time session that isenabled for recovery. During recovery, messages are processed once, even if they meet more than one filtercriteria.

Previously the Integration Service failed a JMS or WebSphere MQ real-time session when you enabled recoveryand created multiple partitions.

XML Target File ListEffective in version 8.6, the Integration Service writes the absolute path of each XML target in an XML target filelist. The Integration Service creates an XML target file list (.lst file) when you configure the target to generate newXML documents on commit, or when the root group of the XML target receives multiple rows.

Previously, the Integration Service wrote the relative path of each XML target in the file list.

Integration Service 89

LANG Environment Variable for LinuxEffective in version 8.6, the following locale values have been renamed:

Language Territory / Region Previous Value 8.6 Value

Danish Denmark da.ISO8859-15 da_DK.iso885915

Dutch Dutch-Belgium nl_BE.ISO8859-15 nl_BE.iso885915

Dutch Netherlands nl.ISO8859-15 nl_NL.iso885915

English United Kingdom en_GB.ISO8859-15 en_GB.iso885915

Finnish Finland fi.ISO8859-15 fi_FI.iso885915

French French-Belgium fr_BE.ISO8859-15 fr_BE.iso8859.15

French France fr.ISO8859-15 fr_FR.iso885915

German Germany de_AT.ISO8859-15 de_AT.iso885915

Indonesian Indonesia in id_ID

Italian Italy it.ISO859-15 it_IT.iso885915

italian Italy it.UTF-8 it_IT.utf8

Japanese Japan ja_JP.UTF-8 ja_JP.utf8

Korean Korea ko ko_KR

Portuguese Portugal pt.ISO8859-15 pt_PT.iso885915

Russian Russia ru_RU.KOI8-R re_RU.koi8r

Simplified Chinese China zh zh_CN

Simplified Chinese China zh.GBK zh_CN.gbk

Swedish Sweden sv.ISO8859-15 sv_SE.iso885915

Spanish Spain es.UTF-8 es_ES.utf8

Traditional Chinese Taiwan zh_TW.Big5 zh_TW.big5

Effective in version 8.6, support for the following locale value has changed:

Language Territory / Region No Longer SupportedValue

8.6 Value

French France francias fr_FR.iso885915fr_FRfrench

90 Chapter 21: PowerCenter (8.6)

If the LANG environment variable on a Linux machine is set to a value that has been renamed or is no longersupported, update the LANG settings.

Mapping Architect for VisioEffective in version 8.6, you can create a mapping template from a PowerCenter mapping that contains thefollowing objects:

¨ Mapplet

¨ Stored Procedure transformation

¨ Reusable transformation

¨ Shortcut to a source or target definition

Previously, when you created a mapping template from a mapping that contained these objects, you received anerror.

Mapping TemplateEffective in version 8.6, you can create a mapping template from a PowerCenter mapping that contains thefollowing objects:

¨ Mapplet

¨ Stored Procedure transformation

¨ Reusable transformation

¨ Shortcut to a source or target definition

Previously, when you created a mapping template from a mapping that contained these objects, you received anerror.

Unstructured Data TransformationThis section describes changes to the Unstructured Data transformation.

Name ChangeThe Complex Data transformation is renamed to Unstructured Data transformation. Complex Data Exchange isrenamed to Data Transformation.

New Transformation AttributesEffective in 8.6 you can pass a dynamic service name to the Unstructured Data transformation. When youupgrade, Dynamic Service Name is not enabled.

Mapping Architect for Visio 91

You can set a chunk size for data that the Unstructured Data transformation passes to a Data Transformationstreamer. When you upgrade, the default chunk size is 256KB.

When you configure an Unstructured Data transformation to receive status tracing messages from a DataTransformation service, the Designer creates the UDT Status Code and the UDT Status Message ports in thetransformation. When you upgrade, the Status Tracing Level is None and the transformation does not contain theStatus Code and Status Message ports.

Writing to Multiple Output GroupsWhen you define a hierarchy of output groups and ports, the Unstructured Data transformation returns rows ofdata instead of XML. You can pass the data directly to relational tables instead of an XML Parser transformation.When you define output groups, you override the File or Buffer output type. The Unstructured Data transformationdoes not write to the OutputBuffer port.

92 Chapter 21: PowerCenter (8.6)

C H A P T E R 2 2

Metadata Manager (8.6)This chapter includes the following topics:

¨ Custom Metadata Configurator, 93

¨ Logging, 94

¨ Metadata Manager Service, 94

¨ Business Objects XConnect, 94

¨ Resources, 95

¨ Searches, 95

¨ Data Lineage and Where-Used Analysis, 95

Custom Metadata ConfiguratorThis section describes changes to the Custom Metadata Configurator.

Connection StringEffective in version 8.6, you must configure the Connection String option to connect to the Metadata Managerrepository. For a Metadata Manager repository on Oracle, you can configure the SID or the full service name in theconnection URL.

When you upgrade, you must configure the Connection String for all Metadata Manager repositories in the CustomMetadata Configurator.

Previously, you configured the database host name, port number, and service name when you configured aconnection to a Metadata Manager repository in the Custom Metadata Configurator.

Relationships Between ResourcesEffective in version 8.6, you can create relationships between custom resources and packaged resource types inthe Custom Metadata Configurator. Previously, you could not create relationships between custom resources andpackaged resources. You could configure the relationships in other versions of Metadata Manager.

93

LoggingEffective in version 8.6, Metadata Manager creates the following log files on the machine running MetadataManager:

¨ Metadata Manager Agent log file. Contains log events generated during the metadata extraction process inMetadata Manager. Includes log events about the calls to the Metadata Manager Agent from MetadataManager.

¨ Metadata Manager Service log file. Contains all events that occur when the Metadata Manager applicationruns. Includes more information about the Metadata Manager component that generates a log event.

Previously, the Metadata Manager Agent did not generate a log file on the Metadata Manager machine andMetadata Manager only wrote log events to the PowerCenter Log Manager.

Metadata Manager ServiceEffective in version 8.6, the Metadata Manager Services includes new properties.

The following table describes the new properties:

Metadata Manager ServiceProperty

Description

SID/Service Name Indicates whether the Database Name property contains an Oracle full service name or SID.

Additional JDBC Parameters Additional JDBC options. For example, you can use this option to specify the location of abackup server if you are using a database server that is highly available such as Oracle RAC.

Business Objects XConnectEffective in version 8.6, Business Objects XConnect does not extract document folders or categories that do notcontain documents or reports for certain versions of Business Objects.

The following table describes the objects not extracted for each version of Business Objects:

Version Objects Not Extracted

5, 6, XI Document folders that do not contain documents or reports

XI Categories that do not contain documents or reports

94 Chapter 22: Metadata Manager (8.6)

ResourcesThis section describes changes to resources.

Cognos SDK Library PathEffective in version 8.6, you can configure the path to the Cognos ReportNet SDK when you configure a CognosReportNet resource. You can use the Cognos ReportNet SDK to connect to Cognos ReportNet, instead of theMetadata Manager Agent.

Oracle Service NameEffective in version 8.6, you can configure a full service name for a connection to an Oracle database forPowerCenter, Data Analyzer, and Oracle resources.

When you upgrade, configure the full service name in the JDBC URL for PowerCenter, Data Analyzer, and Oracleresources.

Previously, you could only use the SID for Oracle databases.

SearchesEffective in version 8.6, Metadata Manager recognizes the underscore (_) in searches. It also saves underscoresin search indexes.

To access this change immediately, manually update the resource indexes. Metadata Manager also updates eachresource index when you import or update a resource. Previously, Metadata Manager did not index underscores.

Data Lineage and Where-Used AnalysisEffective in version 8.6, the Metadata Manager API URL allows you to access both data lineage and where-usedanalysis directly from a third-party application. The API URL also provides two new optional parameters to helpidentify and display specified metadata.

Previously, you could only access data lineage analysis.

Resources 95

C H A P T E R 2 3

Data Analyzer (8.6)This chapter includes the following topics:

¨ Data Analyzer Context Path, 96

¨ JDBC Driver URL, 96

Data Analyzer Context PathEffective in version 8.6, the name of the Reporting Service is the name of the Data Analyzer instance and thecontext path for the Data Analyzer URL. The Service Manager replaces any character in the Reporting Servicename other than a number, letter, hyphen (-), or underscore (_) with an underscore and the Unicode value of thecharacter.

Previously, the Service Manager added the prefix ias- to the Data Analyzer context path and directory names. Italso prefixed an underscore with another underscore and replaced any character in the Reporting Service nameother than a number, letter, hyphen, or underscore with an underscore and the Unicode value of the character.

JDBC Driver URLEffective in version 8.6, the JDBC URLs for the Data Analyzer repository and reporting data sources have thefollowing changes:

¨ Oracle JDBC URL. When you create a Reporting Service and select an Oracle repository, you can selectwhether to use the SID or service name to connect to the Oracle database instance.

Previously, the Oracle JDBC URL used the SID to connect to the Oracle database by default.

¨ Code page override. When you create a Reporting Service and set the data source to a PowerCenterrepository or Metadata Manager warehouse, the Service Manager adds the CODEPAGEOVERRIDE parameterto the URL. The parameter matches the code page of the Reporting Service with the code page of thePowerCenter Service or Metadata Manager Service.

Previously, you could not override the code page of the Reporting Service.

96

C H A P T E R 2 4

Adapters for PowerCenter (8.6)This chapter includes the following topics:

¨ PowerExchange for Netezza, 97

¨ PowerExchange for JMS, 98

¨ PowerExchange for SAP NetWeaver, 98

¨ PowerExchange for SAP NetWeaver BI, 99

¨ PowerExchange for Web Services, 99

PowerExchange for NetezzaThis section describes changes to PowerExchange for Netezza.

Editing Datatype and PrecisionEffective in version 8.6, you cannot change the datatype, precision, and scale for columns of the followingdatatype:

¨ BigInt

¨ ByteInt

¨ Date

¨ Integer

¨ Real

¨ SmallInt

¨ Time

¨ Timestamp

Previously, the datatype, precision, and scale were editable.

Update Else InsertEffective in version 8.6, when you configure the session to update else insert, the Integration Service updates arow if it exists in the target. Otherwise, it inserts the row.

Previously, the Integration Service deleted target rows that matched primary source primary key rows and theninserted rows into the target.

97

Unprojected ColumnsEffective in version 8.6, the ignores unconnected target columns when it generates SQL to load to Netezza. If adefault value is defined for an unconnected column, Netezza updates or populates the column with the defaultvalue.

Previously, the Integration Service updated all unprojected target columns with null values.

Code PagesEffective in version 8.6, you cannot select a code page when you configure a Netezza relational databaseconnection. When the Integration Service runs in Unicode mode, it encodes Netezza data of the Nchar(m) andNVarchar(m) datatypes in UTF-8. It encodes Netezza data of the Varchar and Char datatypes in Latin-9.

Previously, you could select a code page when you configured a Netezza relational database connection.

Creating Source and Target DefinitionsEffective in version 8.6, you cannot create tables from Netezza source and target definitions.

PowerExchange for JMSEffective in version 8.6, the Integration Service can delete the durable subscription when a JMS sessioncompletes successfully, or it can remain subscribed. If the Integration Service deletes the durable subscription, itcan no longer receive messages the JMS subscriber publishes on the topic when the session is not running. If theIntegration Service remains subscribed, it can receive messages the JMS subscriber publishes on the topic whenthe session is not running.

Previously, the Integration Service unsubscribed from the durable subscription after a JMS session ended.

PowerExchange for SAP NetWeaverThis section describes changes to PowerExchange for SAP NetWeaver.

PowerExchange for SAP NetWeaver mySAP Option RenamedEffective in version 8.6, PowerExchange for SAP NetWeaver mySAP Option is renamed PowerExchange for SAPNetWeaver.

Installing the SAP RFC SDK LibrariesEffective in version 8.6, when you install or upgrade PowerExchange for SAP NetWeaver, you need to downloadand install the SAP RFC SDK libraries for the operating system that hosts the Integration Service process.

Previously, the installer installed the SAP RFC SDK libraries for the operating system that hosted the IntegrationService process.

98 Chapter 24: Adapters for PowerCenter (8.6)

Processing BAPI/RFC DataThe Integration Service can process table type parameters in a BAPI/RFC transformation. The transformationincludes groups for table type input parameters and table type output parameters.

PowerExchange for SAP NetWeaver BIThis section describes changes to PowerExchange for SAP NetWeaver BI.

PowerExchange for SAP NetWeaver BW Option RenamedEffective in version 8.6, PowerExchange for SAP NetWeaver BW Option is renamed PowerExchange for SAPNetWeaver BI.

Registering the PowerExchange for SAP NetWeaver BI ClientEffective in version 8.6, when you install or upgrade PowerExchange for SAP NetWeaver BI, you need to registerthe PowerExchange for SAP NetWeaver Client. Previously, the installer registered the PowerExchange for SAPNetWeaver BI Client.

Installing the SAP RFC SDK LibrariesEffective in version 8.6, when you install or upgrade PowerExchange for SAP NetWeaver BI, you need todownload and install the SAP RFC SDK libraries for the operating system that hosts the Integration Serviceprocess.

Previously, the installer installed the SAP RFC SDK libraries for the operating system that hosted the IntegrationService process.

PowerExchange for Web ServicesThis section describes changes to PowerExchange for Web Services.

Web Services Consumer TransformationEffective in version 8.6, the following property is updated:

Property Value (In previous version) Value (In 8.6)

Output is Repeatable Default is Always. Default is Based on Input Order.

When you upgrade, default values for the Web Services Consumer transformation in the repository will notchange. To use new values for Web Services Consumer transformations in the repository, update thetransformation property.

PowerExchange for SAP NetWeaver BI 99

SOAP Response TimeoutEffective in version 8.6, the Integration Service fails the session if it does not receive a SOAP response from theweb service provider within the time-out period you specify in the Web Services Consumer connection properties.

Previously, the session would hang if the Integration Service did not receive a SOAP response from the webservice provider. The timeout period in the Web Services Consumer connection properties only applied to thenumber of seconds the Integration Service waited for a connection to the web service provider before closing theconnection and failing the session.

100 Chapter 24: Adapters for PowerCenter (8.6)

Part V: Version 8.5.1This part contains the following chapters:

¨ New Features and Enhancements (8.5.1), 102

¨ PowerCenter (8.5.1), 103

101

C H A P T E R 2 5

New Features and Enhancements(8.5.1)

This chapter includes the following topic:

¨ Code Pages, 102

Code PagesPowerCenter 8.5.1 supports the following code pages:

¨ IBM1159

¨ IBM13121

¨ IBM13124

¨ IBM4933

¨ IBM835

¨ IBM836

¨ IBM837

102

C H A P T E R 2 6

PowerCenter (8.5.1)This chapter includes the following topics:

¨ pmrep, 103

¨ Transformations, 103

¨ Integration Service, 104

pmrepEffective in version 8.5.1, pmrep no longer supports the following command:

Command Description Comments

ListGroupsForUser Lists all groups that a user belongs to. You can view the list in the Security page ofthe Administration Console instead.

TransformationsEffective in version 8.5.1, the default value of the Requires Single Thread per Partition property for the followingtransformations is disabled and read-only.

¨ HTTP transformation

¨ Java transformation

¨ SQL transformation

¨ Union transformation

¨ Complex Data transformation

¨ XML Generator transformation

¨ XML Parser transformation

Previously, this field was enabled and editable by default.

103

Integration ServiceEffective in version 8.5.1, when the Integration Service runs in Unicode data movement mode, the columnprecision that you specify for ODBC datatypes determines the number of characters the Integration Service readsand writes.

Previously, the precision that you specified for ODBC datatypes determined the number of bytes that theIntegration Service read and wrote.

104 Chapter 26: PowerCenter (8.5.1)

Part VI: Version 8.5This part contains the following chapters:

¨ New Features and Enhancements (8.5), 106

¨ PowerCenter Domain (8.5), 123

¨ PowerCenter Security (8.5), 125

¨ Repository and Repository Service (8.5), 134

¨ Integration Service (8.5), 137

¨ Functions (8.5), 147

¨ Web Services Provider (8.5), 150

¨ Command Line Programs (8.5), 152

¨ Transformations (8.5), 161

¨ Data Profiling (8.5), 163

¨ Data Analyzer (8.5), 164

¨ PowerCenter Repository Reports (8.5), 171

¨ Metadata Manager (8.5), 173

¨ PowerCenter Connect (8.5), 185

105

C H A P T E R 2 7

New Features and Enhancements(8.5)

This chapter includes the following topics:

¨ Command Line Programs, 106

¨ Data Analyzer, 107

¨ Data Profiling, 107

¨ Data Stencil, 108

¨ Datatypes, 108

¨ Domains, 108

¨ Integration Service, 108

¨ Metadata Manager , 112

¨ PowerCenter Repository Reports, 114

¨ Repository Service, 116

¨ Security, 116

¨ Transformations, 118

¨ Transformation Language, 118

¨ Web Services Provider, 119

¨ XML, 121

¨ PowerExchange (PowerCenter Connect), 121

Command Line ProgramsThis section describes new features and enhancements for command line programs.

infacmd¨ Operating system profiles. Added commands to create, list, remove, and update operating system profiles.

¨ User. Added commands to complete the following tasks:

- Create and remove roles.

- Add, list, and remove privileges for roles.

106

- Assign roles to a user or group.

- Add user permissions.

- List security domains.

¨ User Management. Added commands to import or export native users and groups, and to set LDAPconnectivity.

¨ Repository Service. Added commands to set up LDAP authentication when upgrading from PowerCenterversion 8.1.1 and earlier to PowerCenter 8.5.

¨ Reporting Service. Added commands to complete the following tasks:

- Create, delete, upgrade, back up, and restore contents in a Data Analyzer repository.

- Create and update a Reporting Service.

- Upgrade users and groups in a Data Analyzer repository.

¨ Metadata Manager Service. Added commands to create, update, and assign or unassign an IntegrationService.

pmrepEffective in version 8.5, the pmrep command line program includes new commands AssignPermission,ChangeOwner, and RollBackDeployment.

Data Analyzer¨ Reporting Service. The Reporting Service is an application service that runs the Data Analyzer application in

a PowerCenter domain. You create and enable a Reporting Service on the Domain page of the PowerCenterAdministration Console. When you enable the Reporting Service, the Administration Console starts DataAnalyzer.

You log in to Data Analyzer to create and run reports on data in a relational database or to run the followingPowerCenter reports: PowerCenter Repository Reports, Data Analyzer Data Profiling Reports, or MetadataManager Reports. You can launch Data Analyzer from the Administration Console, PowerCenter Client tools, orMetadata Manager, or by accessing the Data Analyzer URL from a browser.

¨ Multiple values for dashboard filters. You can select multiple attribute values for a dashboard filter.

Data ProfilingYou can use a warehouse utility to create, drop, or upgrade a Data Profiling warehouse. The warehouse utility alsocreates or upgrades a Data Profiling warehouse schema and view for Data Profiling reports. The warehouse utilityruns the appropriate script for the destination database based on the command and arguments you enter.

Data Analyzer 107

Data Stencil¨ Mapping Template Wizard. When you import a mapping template, you can also choose from pre-defined

templates. Pre-defined templates include slowly changing dimension mappings.

¨ Mapping parameters and variables. Configure additional attributes for parameters in a mapping template. Forexample, specify a label or default value for a parameter.

Datatypes¨ Bigint. The Integration Service processes 64-bit integer values. The Bigint transformation datatype has a

maximum value of 9,223,372,036,854,775,807 and a precision of 19. You can use the Bigint datatype forgenerated keys for Sequence Generator, Lookup, Normalizer, and XML Source Qualifier transformations.

Domains¨ Configuration. After you install PowerCenter, use the Configuration Assistant in the Administration Console to

configure services for PowerCenter and Metadata Manager.

¨ License reports. Generate a license report to monitor number of times you use a database type as a source ortarget. You can monitor license usage to determine if you need additional licenses for upcoming dataintegration projects.

Integration ServiceThis section describes new features and enhancements for the Integration Service.

Date Processing¨ Subseconds. The Integration Service can process milliseconds, microseconds, and nanoseconds.

¨ Datetime format. You can specify the default datetime format for Date functions and port-to-port conversion inthe session configuration object. In version 8.5, the default datetime format specifies precision to themicrosecond: MM/DD/YYYY HH24:MI:SS.US. For upgraded session configuration objects, the default datetimeformat specifies precision to the second.

¨ Oracle Timestamp support. The Integration Service reads and writes Oracle Timestamp values. TheIntegration Service converts Oracle Timestamp values to PowerCenter Date/Time values.

External Loading¨ IBM DB2 EE external loader. You can use the IBM DB2 EE external loader to load to an IBM DB2 EEE

database. The IBM DB2 EE external loader can load data to an IBM DB2 EEE server on a machine that isremote from the Integration Service.

108 Chapter 27: New Features and Enhancements (8.5)

Flat File Processing¨ Create target directory. You can enable the session to create the target directory if it does not exist.

Parameters and Variables¨ Expanded support for parameters and variables. You can enter parameters and variables in more input

fields in the Designer and Workflow Manager. For example, you can use parameters and variables in sourceand target table names, connection object user names and passwords, flat file reader and writer code pages,stored procedure database connection information, and web service host end point URLs.

¨ Email variables. You can use email variables to include more information about a session in post-sessionemail. The variables allow you to include the Integration Service name, repository user name, session runmode, workflow name, and workflow run instance name in the email body or subject.

¨ Mapping parameters and variables expansion. The Integration Service can expand mapping parameters andvariables within transformation expressions.

¨ Subsecond support. Date/Time mapping parameters, mapping variables, and workflow variables supportvalues with precision to the nanosecond.

¨ Get file names for sessions that use a file list. For sessions that read source data from a file list, you canconfigure the associated mappings to return the name of the file from which a row has been read.

¨ Override connection properties. You can override connection properties in a parameter file using built-insession parameters. You can override connection properties for application, external loader, FTP, queue, andrelational connection objects.

¨ Get run-time information. Use built-in mapping variables, session parameters, and workflow variables thatallow you to get the following run-time information:

Information MappingVariable

SessionParameter

WorkflowVariable

Folder name X X X

Integration Service name X X X

Mapping name X X

Repository Service name X X X

Repository user name X X X

Session name X X

Session run mode X X

Source and target number of affected rows X

Source and target number of applied rows X

Source and target number of rejected rows X

Source and target table name X X

Integration Service 109

Information MappingVariable

SessionParameter

WorkflowVariable

Workflow name X X X

Workflow run instance name X X X

¨ Parameterize session parameter file names. You can define the session parameter file name in a workflowparameter file. When you run multiple instances of a workflow concurrently, you can define different parameterand variable values for sessions in the workflow.

¨ Share information among sessions. Sessions within the same workflow or parent worklet can shareinformation using certain types of parameters and variables. Before you run a session, you can updatemapping parameters, mapping variables, and session parameters with the values of parent workflow or workletvariables. At the end of a session, you can update workflow and worklet variables with mapping parameter,mapping variable, and session parameter values. This allows one session to pass information to a subsequentsession in the same workflow or worklet.

¨ Share information among worklets. Worklets within the same workflow or parent worklet can shareinformation using workflow and worklet variables. Before a worklet runs, you can update worklet variables withthe values of parent workflow or worklet variables. After a worklet runs, you can update parent workflow andworklet variables with worklet variable values. This allows one worklet to pass information to a subsequentworklet in the same workflow or parent worklet.

Pushdown Optimization¨ Lookup transformation. You can push a Lookup transformation with a lookup filter to the database with

source-side, target-side, or full pushdown optimization.

¨ Router transformation. You can push a Router transformation to the database with source-side or fullpushdown optimization.

¨ Sequence Generator transformation. You can push a Sequence Generator transformation to an Oracle orIBM DB2 database with source-side or full pushdown optimization. The Integration Service creates a temporarysequence object in the database to push the transformation logic to the database.

¨ Update Strategy transformation. You can push an Update Strategy transformation to the database with fullpushdown optimization.

¨ Slowly changing dimension mappings. You can push Type 1 and Type 3 slowly changing dimensionmappings to an Oracle or IBM DB2 database.

¨ Functions. The Integration Service can push the following functions to the specified databases:

Function IBM DB2 MicrosoftSQL Server

Oracle Sybase Teradata ODBC

DECODE X X X* X X X

GREATEST() X

IN() X* X* X* X* X* X

LEAST() X

SYSTIMESTAMP() X X X X X

110 Chapter 27: New Features and Enhancements (8.5)

Function IBM DB2 MicrosoftSQL Server

Oracle Sybase Teradata ODBC

TO_BIGINT() X X X X X

* The Integration Service was able to push the function to this database in the previous release.

Real-time Recovery¨ Improved recovery. The Integration Service writes real-time session recovery information to a database table.

The table helps maintain data integrity during recovery so no data is lost or duplicated.

When you enable recovery for a real-time session that reads from a JMS or WebSphere MQ source and writesto a relational target, the Integration Service creates a recovery table on the target database. The recoverytable stores the commit number and the message ID that the Integration Service committed to the target. Whenyou recover a session, the Integration Service uses the recovery information to determine where it stoppedprocessing.

¨ Automatic recovery. You can restart a real-time session without losing data. If you restart a real-time sessionthat has recovery enabled with a JMS or WebSphere MQ source, the Integration Service recovers allunprocessed messages before it continues to process the session.

¨ Operating system flush. When you enable recovery for a real-time session that reads from a JMS orWebSphere MQ source and writes to a non-relational target, you can prevent data loss if the IntegrationService is not able to write the recovery information to the recovery file. The Integration Service may fail towrite recovery information in cases of an operating system error, hardware failure, or file system outage. Whenyou configure this property, the Integration Service flushes the messages that are in the operating systembuffer to the recovery file.

¨ Stopping real-time sessions. When you stop a real-time session with a JMS, WebSphere MQ, or changeddata source, the Integration Service stops reading from the source and continues to process all messages itread.

¨ Message order. For a session with JMS or WebSphere MQ sources, the Integration Service reads messagesin the same order as they exist in the source.

Recovery¨ Workflow and task recovery. You can start a failed workflow or task that has recovery enabled without

processing the recovery data. If you want to restart a workflow or task without recovery, start the workflow ortask in cold start mode. You may not want to recover data if you already cleaned up the target system.

¨ Session recovery. You can enable recovery for sessions that have Stored Procedure and External Proceduretransformations. In the transformation properties, you can configure the transformation to be recoverable.

Session Properties¨ Custom properties. You can override Integration Service custom properties in a Session task.

Integration Service 111

Workflows¨ Concurrent workflows. You can run multiple instances of a workflow concurrently. You can run multiple

instances of the same workflow name, or you can define multiple instance names. When you define multipleinstance names, you configure different workflow parameter files for each instance. You can define differentsources, targets, and variables in the parameter files. The Integration Service can persist separate workflowand worklet variables for each workflow instance.

When you run multiple instances of the same workflow name, the Integration Service defines each instance bythe run ID. You do not define separate parameters for each instance and the Integration Service does notpersist variables for them. You might run multiple instances of the same workflow when the workflow is a webservice workflow.

Metadata ManagerThis section describes new features and enhancements for Metadata Manager.

Architecture¨ Metadata Manager Service. Runs the Metadata Manager application in a PowerCenter domain and manages

access to metadata in the Metadata Manager warehouse. You must create and enable a Metadata ManagerService in the PowerCenter Administration Console to run Metadata Manager.

¨ User interface. The Metadata Manager interface is a browser-based application that includes the followingpages that you can use to perform tasks in Metadata Manager:

- Browse. Browse and search the metadata catalog, create and view shortcuts and shared folders, run datalineage and where-used analysis, and edit metadata objects and object attributes.

- Model. Create and edit custom models, add custom attributes to existing and custom models, and import andexport custom models.

- Load. Create and configure resources and load metadata into the Metadata Manager warehouse. Use theLoad page to monitor and schedule resource loads and purge metadata from the Metadata Managerwarehouse. You also use the Load page to manage the Metadata Manage search index.

- Security. Manage permissions on metadata objects in the Metadata Manager repository.

The Metadata Manager user interface replaces the functionality in the Metadata Manager Console andMetadata Manager application in previous Metadata Manager versions.

¨ Metadata Manager Agent. Required by some resources to load metadata from metadata sources. You mustinstall the Metadata Manager Agent on the source machines before you load metadata from Business Objects,Microstrategy, and Cognos Impromptu. You also use the Metadata Manager Agent to extract metadata frommetadata source files. You can download the Metadata Manager Agent from the Load page.

¨ Reporting Service. Metadata Manager does not embed Data Analyzer functionality. Create a ReportingService to run reports on the Metadata Manager warehouse.

Browse and Search Metadata¨ Metadata catalog. Shows resources and metadata objects in the Metadata Manager warehouse. Use the

metadata catalog to browse and edit metadata objects and run data lineage and where-used analysis.

You must load metadata for a resource into the Metadata Manager warehouse before you can browse themetadata objects in the catalog.

112 Chapter 27: New Features and Enhancements (8.5)

¨ Search. Includes basic and advanced keyword search in the Browse page. Use basic search to search allproperties for metadata objects. Use advanced search to limit the object properties and object types thatMetadata Manager searches. You can also save searches to access common searches.

¨ Shortcuts. You can create shortcuts to commonly accessed metadata objects in the metadata catalog.Shortcuts also include saved searches. In addition, you can also share folders in shortcuts with other MetadataManager users.

¨ Tabbed browsing. You can use tabbed browsing to view details about multiple where-used and data lineageanalyses at the same time.

¨ Profiling. You can view profiling information for metadata sources that include relational metadata. When youload a metadata for a metadata resource, you can include profiling data for the metadata source. After you loadthe metadata for a resource, view the profiling information for the metadata object on the Browse page.

Edit Metadata Objects¨ Annotations. Add comments to a metadata object in the metadata catalog. Use annotations to share

comments with other Metadata Manager users.

¨ Relationships. Relationships are associations between metadata objects in the metadata catalog. You canview existing object relationships between metadata objects or create relationships between metadata objectsin the metadata catalog.

¨ Supporting documents. Create links to documents on a company intranet, shared drive, or the internet. Usesupporting documents add external information to a metadata object in the metadata catalog.

¨ Edit attributes. Edit attributes for custom metadata objects and attributes you added to metadata objects forpackaged resources.

Custom ModelsYou can use the Model page to create custom models to add custom metadata into the Metadata Managerwarehouse. You can create or edit the following types of metadata:

¨ Custom models. Create or edit custom models in the Model page. You can create a custom model to includemetadata in the Metadata Manager warehouse for which Metadata Manager does not include a packagedresource type. You can create a model and add custom classes, relationships, and attributes to define themodel.

¨ Custom attributes. Add custom attributes to packaged models.

Data Lineage and Where-Used AnalysisYou run data lineage analysis and where-used analysis on the Browse page. After you run data lineage analysison an object, you can use the Flash-based viewer to view the lineage diagram. You can also view the diagram in aseparate browser window. You open multiple data lineage and where-used analyses simultaneously.

You can access data lineage and where-used analysis for a metadata object from a shortcut to the object, fromsaved search queries, from the metadata catalog, or from where-used analysis or data lineage.

Metadata Exchanges (XConnects)¨ SAP Metadata Exchange. Extracts metadata from SAP R/3.

¨ Microstrategy Metadata Exchange. Extracts reporting metadata.

Metadata Manager 113

User Preferences¨ Catalog. You can select the resources to display in the metadata catalog.

¨ Browse. You can select the metadata object properties appear when you view details about a metadata object.

Metadata ResourcesResources represent metadata sources in Metadata Manager. Use the Resource Creation Wizard to create aresource for a metadata source in the Load page and configure the resource and configuration properties,parameters, connection assignments, and schedule for a resource.

You must create a resource in the Load page before you can load metadata for a metadata source in the MetadataManager warehouse. You can edit the configuration for a resource after you run the Resource Wizard by selectingthe resource in the Load page and editing the resource configuration.

Resources also include the following features:

¨ Parallel resource loads. You load multiple resources simultaneously.

¨ mmcmd. Use mmcmd to load, resume, and get the status of a resource load from the command line or from ascript. For example, you can use mmcmd to run Metadata Exchanges using an external scheduler.

¨ mmwfrundetails. Use mmwfrundetails to get information about the PowerCenter workflow and sessions.

¨ Schedules. You can create schedules for resource loads and assign the schedules to resources. When youcreate a schedule, you configure the name, description, and the time and frequency. After you create theschedule, you can assign the schedule to individual metadata resources.

PowerCenter Repository ReportsThis section describes new features and enhancements for PowerCenter Repository Reports.

New ReportsThe PowerCenter Repository Reports include the following reports:

¨ Mapping Composite Report. This composite report consists of subreports that list the sources, targets, andtransformations in a mapping. To generate this report, right click on a mapping in the PowerCenter MappingDesigner and select View Mapping Report option.

The following table describes the subreports:

Subreport Description

Mapping Object-Level Connections Displays all transformations from source to target in a mapping and how they areconnected to each other.

Mapping Port-Level Connections Displays all transformations from source to target in a mapping and how they areconnected to each other through ports.

Mapping Source Field Details Displays column names for all sources by repository, folder, and mapping. It alsodisplays properties of these columns such as datatype, precision, and length.

114 Chapter 27: New Features and Enhancements (8.5)

Subreport Description

Mapping Target Field Details Displays column names for targets by repository, folder, and mapping. It alsodisplays properties of these columns such as datatype, length, and precision.

Mapping Transformation Port Details Displays ports in a transformation by repository, folder, and mapping. It alsodisplays properties of the ports.

Mapping Unconnected Ports Displays all unconnected transformation ports from source to target in a mapping.

¨ Mapplet Composite Report. This composite report consists of subreports that list the sources andtransformations in a mapplet. To generate this report, right click a mapplet in the PowerCenter MappletDesigner and select View Mapplet Report.

The following table describes the subreports:

Subreport Description

All Objects Used in a Mapplet Displays all transformations used in a mapplet by repository and folder.

Mapplet Mapping Dependency Displays all the mappings where a particular mapplet is used by repository andfolder.

Mapplet Port Details Displays all source ports available in each mapplet and port properties.

Mapplet Sources Displays sources in a mapplet by repository and folder.

Mapplet Source Field Details Displays column names for all sources by repository, folder, and mapplet. It alsodisplays properties for these columns such as datatype, length, and precision. Thisreport is the second node in a workflow associated with the Mapplet List primaryreport.

Mapplet Transformations Displays transformations used in a mapplet by repository and folder.

Mapplet Transformation Port Details Displays ports and port properties for the transformation used in a mapplet byrepository and folder. This report is the second node in a workflow associated withthe Mapplet List primary report.

Mapplet Transformation Properties Displays the default or user-defined properties for transformations in a particularmapplet by repository and folder. This report is the second node in a workflowassociated with the Mapplet List primary report.

Mapplet Lookup Transformations Displays all Lookup transformations used in a mapplet by folder and repository.

¨ Workflow Composite Report. This composite report consists of subreports that display workflow tasks,events, and variables. To generate this report, right click a workflow in the PowerCenter Workflow Designerand select View Workflow Report.

PowerCenter Repository Reports 115

The following table describes the subreports:

Subreport Description

Workflow Events Displays workflow events and its properties by repository by folder.

Workflow Task Instance LinkConditions

Displays how tasks are connected to each other in a workflow by repository byfolder.

Workflow Task Instance List Displays all tasks created in a workflow by repository by folder.

Workflow Variables Displays workflow variables and their properties by repository by folder.

Repository ServiceThe PowerCenter Repository Service includes the following new features and enhancements:

¨ Exchanging Metadata. You can use the Meta Integration Model Bridge from Meta Integration Technology, Inc.to exchange data with CA ERwin Data Modeler 7.x.

¨ Optimizing Repository Schema. For IBM DB2 and Microsoft SQL Server repositories, you can improveperformance by enabling the Repository Service to create tables using Varchar(2000) columns instead ofCLOB columns.

SecurityThis section describes new features and enhancements for security.

Unified Security AdministrationYou administer PowerCenter security on the Security page of the Administration Console. You manage users andgroups that can log in to the following PowerCenter applications:

¨ Administration Console

¨ PowerCenter Client

¨ Metadata Manager

¨ Data Analyzer

Privileges determine the actions that users can perform in PowerCenter applications. You assign privileges tousers and groups for the domain and for each of the following application services in the domain: RepositoryService, Metadata Manager Service, and Reporting Service.

Roles are collections of privileges. If groups of users perform similar tasks, you can create and assign roles togrant privileges to the users.

116 Chapter 27: New Features and Enhancements (8.5)

AuthenticationThe PowerCenter Service Manager uses the following authentication methods to authenticate users logging in toPowerCenter applications:

¨ Native. You create and manage users and groups on the Security page of the Administration Console. TheService Manager stores the users and groups in the domain configuration database.

¨ Lightweight Directory Access Protocol (LDAP). You configure a connection to an LDAP directory service onthe Security page of the Administration Console. You also manage the users and groups that can log in toPowerCenter applications, and manage the privileges and roles that determine the actions that users canperform. The Service Manager imports the users and groups set up in the LDAP directory service into thedomain configuration database.

For both authentication methods, users are located in a security domain. A security domain is a collection of useraccounts and groups in a PowerCenter domain. When users log in to PowerCenter applications, they select thesecurity domain for their user account.

Single Sign-OnAfter you log in to a PowerCenter application, you can launch another application or access multiple repositories inthe PowerCenter Client. You do not need to log in to the additional application or repository. For example, if youlaunch a Data Analyzer report from the PowerCenter Workflow Manager, you do not need to log in to DataAnalyzer.

HTTPS¨ Domain. When you install PowerCenter, you can create or specify a keystore file to configure HTTPS.

Configure an HTTPS port for the Administration Console when you install PowerCenter or use thedefineDomain, defineGatwayNode or defineWorkerNode commands.

Specify the HTTPS ports for Metadata Manager and Reporting Service when you create the services in theAdministration Console.

¨ Data Analyzer. When you install PowerCenter, you can create or specify a keystore file to configure HTTPS.When you create a Reporting Service in the PowerCenter Administration Console, you specify the HTTPS portfor Data Analyzer.

¨ Web Services Hub. You can send requests to a Web Services Hub through HTTP or HTTPS or both. You canset the HTTP and HTTPS port on the Administration Console.

Permissions¨ Domain. Assign permissions on domain objects to users and groups. When a group has permission on a

domain object, all users belonging to the group inherit permission on the domain object.

¨ Repository. You can add any user or group to the permissions list for a folder. You assign folder permissionsto each user or group you added. A folder or global object owner has full permissions on the folder or globalobject. You cannot edit an owner’s permissions.

¨ Metadata Manager. Edit the permissions for a metadata object in the Security page, including the users andgroups that have permissions on the object. Permissions include full control, read, write, and no access.

Security 117

Privileges¨ Domain. Assign privileges to users and groups to determine the actions that users can perform in the

Administration Console. You assign privileges to users and groups for the domain on the Security page of theAdministration Console.

¨ Repository. You can assign a new set of privileges to users and groups to determine the actions that userscan perform in PowerCenter Client applications. You assign privileges to users and groups for a RepositoryService on the Security page of the Administration Console.

Integration Service¨ Secure FTP. You can configure FTP connection objects to use SFTP when connecting to SFTP servers. By

default, SFTP is disabled.

¨ Operating system profiles. An operating system profile is a level of security that the Integration Services usesto run workflows. The operating system profile contains the operating system user name, service processvariables, and environment variables. The Integration Service runs the workflow with the system permissions ofthe operating system user and settings defined in the operating system profile. You can configure theIntegration Service to use operating system profiles if the Integration service runs on UNIX.

Transformations¨ Complex Data transformation. You can parse streaming data from EDI or HIPAA files with the Complex Data

transformation. The transformation outputs data in multiple rows.

¨ Lookup filter. You can configure the Lookup transformation to filter the rows returned from a lookup. You filterthe returned rows to increase lookup performance.

¨ Lookup cache shared across pipelines. If you configure a Lookup transformation to use a persistent lookupcache and named cache files, you can share the cache among multiple Lookup transformations. You canconfigure a Lookup transformation to cache the lookup table and then configure other Lookup transformationsto share the cache. The first Lookup transformation uses dynamic cache and the rest of the transformationsuse static cache. The Lookup transformations can be in different pipelines.

¨ Pipeline lookup. You can perform lookups on sources other than relational tables and flat files, such as JMSand MSMQ. When you create a mapping, you can connect a Lookup transformation to an unconnected SourceQualifier transformation that connects to a relational, flat file, JMS, or MSMQ source. The Integration Servicereads the source data coming through the Source Qualifier, caches it, and performs the lookup.

¨ Lookup and Stored Procedure subsecond precision. You can specify precision up to nanoseconds for Date/Time values in Lookup and Stored Procedure transformations.

¨ XML Parser transformation. The XML Parser transformation can accept multiple row input. You can parselarge XML files and streaming data from Informatica PowerExchange for Complex Data by configuring the XMLParser transformation to receive data from more than one input row. Each input row consists of a string thatcontains the XML data and an integer port that indicates whether the row is the end of the XML stream.

Transformation Language¨ REG_REPLACE. Use REG_REPLACE to replace a character pattern in a string with another character pattern.

118 Chapter 27: New Features and Enhancements (8.5)

¨ SYSTIMESTAMP. Use SYSTIMESTAMP to return the current date and time of the machine hosting theIntegration Service with precision to the nanosecond.

¨ TO_BIGINT. Use TO_BIGINT to convert a string or numeric value to a bigint value.

¨ User-defined functions. User-defined functions appear in the Navigator of the Repository Manager and theDesigner. You can version, view dependencies, and query user-defined functions in the repository. You canalso add user-defined functions to deployment groups.

Web Services ProviderThis section describes new features and enhancements for Web Services Provider.

Web Services Hub¨ Multiple Web Services Hubs associated with a repository. You can assign more than one Web Services

Hub to a repository. You can run a web service on more than one Web Services Hub. You can publish a webservice to all the Web Services Hubs associated with a repository or publish the web service to specific WebServices Hubs.

¨ Multiple web service instances on a Web Services Hub. The Web Services Hub can run more than oneinstance of a web service to process requests. You can set the threshold at which a new instance will bestarted.

¨ Web Services Hub security mode. You can run the Web Services Hub on HTTP or HTTPS or both. If you runthe Web Services Hub on HTTP and HTTPS, the Administration Console displays the URL for both modes.

¨ Support of a load balancer. You can use a third-party load balancer to manage multiple Web Services Hubsand set one logical hub address for all the Web Services Hubs managed by the load balancer. The logical hubaddress is published in the WSDL of the web services that run in the managed Web Services Hubs.

¨ Web Services Report. On the Administration Console, you can run a report on the activities of a Web ServicesHub and the web services running on the Web Services Hub. You can view statistics on the requests receivedby the Web Services Hub and the average time it took to process messages.

¨ Web Services Hub Console. The Web Services Hub console displays information about the web services andoperations available on the Web Services Hub in a new format. You can sort the list of web services andoperations and search for specific web services or operations.

¨ Try-It client application. You can use the Try-It application to test an operation in a web service published onthe Web Services Hub console. Provide the request as a SOAP message or as parameter values and then runthe web service. The Web Services Hub displays the response on the console.

¨ Real-time web services. Sample programs are available that demonstrate how to create a real-time webservice in PowerCenter.

Web Services Provider 119

¨ Batch web services operations. New operations are available in Batch web services to get information onexecuted tasks and failed tasks. The Data Integration web services provide the following new operations:

Operation Description

GetTaskDetailsEx The GetTaskDetailsEx operation is similar to the getTaskDetails operation, but returnsinformation about all instances of a task. Use this operation when multiple instances of aworkflow run concurrently.

GetWorkflowDetailsEx This operation is similar to GetWorkflowDetails operation, but returns information about allinstances of a workflow. Use this operation when multiple instances of a workflow runconcurrently.

StartWorkflowEx The StartWorkflowEx operation returns the run instance ID for of the workflow. Use theStartWorkflowEx operation instead of the startWorkflow operation if you need to know therun ID of the workflow started by the operation.

¨ New Properties. The Web Services Provider provides the following new properties for the Web Services HubService:

Property Name Description

SessionExpiryPeriod Number of seconds that a session can remain idle before the session times out and thesession ID becomes invalid. The Web Services Hub resets the start of the timeout periodevery time a client application sends a request with a valid session ID.

HubLogicalAddress URL for the third party load balancer that manages the Web Services Hub. This URL ispublished in the WSDL for all web services that run on a Web Services Hub managed bythe load balancer.

MaxStatsHistory Number of days that PowerCenter keeps statistical information in the history file. Thisproperty determines the number of days available for which you can display historicalstatistics in the Web Services Report page of the Administration Console.

Source and Target Definitions¨ Creating sources and targets. You can create web service source and target definitions without using a

WSDL. You can define the columns manually or get the definition of the columns from existing relational or flatfile sources and targets. You can also import a web service source or target from a WSDL without creatingXML views. You can edit the empty source or target definition in the WSDL workspace to manually add theXML views.

You can create web service source and target definitions in one process.

¨ Editing sources and targets. If you create a web service source or target definition from a WSDL, you canadd, edit, or delete the XML views of web service source or target definitions in the WSDL workspace. If youcreate a web service source or target definition without a WSDL, you can edit the XML views in the Designerworkspace.

¨ Consolidated target definition. All XML views in a web service target are contained in one definition,including fault views.

120 Chapter 27: New Features and Enhancements (8.5)

Mappings and Workflows¨ Creating web service mappings. You can create a web service mapping by defining the source and target

manually or basing the source and target definitions on existing relational or flat file sources and targets. Youcan also create a service mapping based on a reusable transformation or a mapplet.

¨ WSDL. If you create a mapping from a relational or flat file source or target, reusable transformation, ormapplet, you can configure the Web Services Hub to generate the WSDL for the mapping.

¨ New workflow properties. The Web Services Provider provides the following new properties for the webservice workflow:

Property Name Description

Service Time Threshold(Milliseconds)

Maximum amount of time the Web Services Hub can take to process requests before itstarts another instance to process the next request.

Web Services Hubs Web Services Hub Service to run the workflow. By default, all Web Services Hub Servicesassociated with the repository run the web service workflow.

Maximum Run Count PerHub

Maximum number of web service instances that can be started in a Web Services Hub. Allinstances of the web service workflow running on the Web Services Hub are included in thecount, whether the instance is started dynamically or manually. The Web Services Hubcannot start another web service instance once the maximum is reached.

XML¨ Convert anyType to string. You can convert an XML element of type anyType to string by dragging the

anyType element into a view. You create a string port in the datatype field of the XML Editor. You can definelength for the string port.

PowerExchange (PowerCenter Connect)This section describes new features and enhancements for PowerCenter Connect.

PowerCenter Connect products are renamed to PowerExchange.

PowerExchange for WebSphere MQ¨ Improved recovery. The Integration Service writes real-time session recovery information in a database table

to maintain data integrity. You can stop and restart a WebSphere MQ real-time session without losing data.When you enable recovery for a real-time session that reads from a WebSphere MQ source and writes to a non-relational target, you can prevent data loss if the Integration Service is not able to write the recoveryinformation to the file cache.

¨ WebSphere MQ Unicode systems. You can use a UCS-2 code page to process data from a WebSphere MQsystem.

XML 121

PowerExchange for JMS¨ Improved recovery. The Integration Service writes real-time session recovery information in a database table

to maintain data integrity. You can stop and restart a JMS real-time session without losing data. When youenable recovery for a real-time session that reads from a JMS source and writes to a non-relational target, youcan prevent data loss if the Integration Service is not able to write the recovery information to the file cache.

PowerExchange for SAP NetWeaver BW Option¨ BW OHS source definitions. You can import InfoSpokes as metadata for BW OHS source definitions for BW

data extraction.

¨ Starting process chain from PowerCenter or SAP. You can start a process chain from PowerCenter or SAPto extract data.

¨ Monitoring data extraction from PowerCenter or SAP. You can monitor the progress of data extraction fromPowerCenter or SAP.

PowerExchange for SAP NetWeaver mySAP OptionBAPI/RFC integration includes the following enhancements:

¨ BAPI/RFC transformation. You can import a BAPI/RFC transformation from BAPIs with input and outputparameters.

¨ TYPE type specifier. You can import BAPIs with parameters that use the TYPE type specifier as BAPI/RFCtransformations. The TYPE type specifier can use data elements, structures, or fields to declare the BAPIparameter.

¨ SAP unicode systems. You can use a UTF-8 code page to process BAPI/RFC data in a Unicode SAP system.

¨ Decimal and Binary data. Ports in BAPI/RFC transformations can be of the Decimal or Binary datatype.

¨ High precision. You can enable high precision for sessions with BAPI/RFC transformations.

¨ Generate BAPI/RFC data by transaction. You can generate a BAPI/RFC transaction based on the commitinterval. The number you enter for the commit interval is the number of BAPI/RFC in a transaction.

¨ Error output group. The Integration Service writes data for invalid RFC/BAPI calls or data conversion errors toan error output group in comma-delineated format.

¨ System variables for BAPI/RFC input data. If the mapping does not provide an input value for someparameters of a BAPI/RFC transformation, the Integration Service can use SAP system variables as inputvalues.

PowerExchange for Web Services¨ Compression. The Integration Service compresses SOAP requests and responses to increase the speed and

efficiency of sending and receiving messages over the network.

¨ Creating sources and targets. You can create web service source and target definitions without using aWSDL. You can define the columns manually or get the definition of the columns from existing relational or flatfile sources and targets.

¨ Editing sources and targets. You can add, edit, or delete the XML views of web service source or targetdefinitions in the WSDL workspace. If you create a web service source or target definition without a WSDL, youcan edit the XML views in the Designer workspace.

122 Chapter 27: New Features and Enhancements (8.5)

C H A P T E R 2 8

PowerCenter Domain (8.5)This chapter includes the following topics:

¨ Application Service Names, 123

¨ Domain and Service Alerts, 123

¨ Domain Reports, 123

Application Service NamesEffective in version 8.5, application services cannot have the same name as the PowerCenter domain.

Previously, application services could have the same name as the PowerCenter domain.

If a PowerCenter domain contains an application service that has the same name as the domain, the upgradeprocess disables the application service and does not allow you to enable it. If an Integration Service, SAP BWService, or Web Services Hub has the same name as the PowerCenter domain, create the application service witha different name before upgrading. If a Repository Service has the same name as the PowerCenter domain, backup and restore the repository to a Repository Service with a different name before upgrading.

Domain and Service AlertsEffective in version 8.5, you cannot enter your email address on the Manage Account tab. You subscribe todomain and service alerts by selecting Subscribe for Alerts on the Manage Account tab and verifying that thedomain administrator has entered a valid email address for your user account on the Security page.

Previously, you subscribed to domain and service alerts by selecting Subscribe for Alerts and entering your emailaddress on the Manage Account tab.

Domain ReportsEffective in version 8.5, you can run the following domain reports from the Reports tab:

¨ User Domain Audit Report

¨ License Report

123

¨ Web Services Report

Previously, the User Domain Audit Report was named the User Activity Monitoring report. The License Report wasnamed the Domain Activity Monitoring report. You ran these reports from the Administration tab.

124 Chapter 28: PowerCenter Domain (8.5)

C H A P T E R 2 9

PowerCenter Security (8.5)This chapter includes the following topics:

¨ User and Group Management, 125

¨ Service Manager Authentication, 126

¨ Domain Privileges, 127

¨ PowerCenter Repository Privileges, 128

¨ Metadata Manager Privileges and Roles, 131

¨ Permissions on Domain Objects, 131

¨ Permissions on PowerCenter Repository Objects, 132

User and Group ManagementThis section describes changes to user and group management.

Unified User and Group ManagementEffective in version 8.5, you manage PowerCenter domain users, groups, privileges, and roles on the Securitypage of the Administration Console. The Service Manager stores domain users and groups in the domainconfiguration database and periodically synchronizes them to the PowerCenter repository, Metadata Managerrepository, or Data Analyzer repository. Privileges and roles determine the actions that users can perform inPowerCenter applications. Domain users with the appropriate privileges can log in to the following PowerCenterapplications: Administration Console, PowerCenter Client, Metadata Manager, and Data Analyzer.

Previously, you managed users, groups, privileges, or roles within each of the following PowerCenter applications:

¨ Administration Console. You managed domain users on the Administration tab of the Administration Console.Domain users were stored in the domain configuration database.

¨ PowerCenter Client. You managed repository users, groups, and privileges in the Repository Manager.Repository users and groups were stored in the repository.

¨ Metadata Manager. You managed Metadata Manager users, groups, privileges, and roles in MetadataManager. Metadata Manager users and groups were stored in the Metadata Manager repository.

¨ Data Analyzer. You managed Data Analyzer users, groups, privileges, and roles in Data Analyzer. DataAnalyzer users and groups were stored in the Data Analyzer repository.

To log in to an application, you needed a user account within that application. For example, to log in to thePowerCenter Client and Metadata Manager, you needed a user account in the PowerCenter Repository Managerand another user account in Metadata Manager.

125

When you upgrade the users and groups in a PowerCenter, Metadata Manager, or Data Analyzer repository, theService Manager moves them to the PowerCenter domain configuration database.

Domain User NamesEffective in version 8.5, domain user names are not case sensitive.

Previously, domain user names were case sensitive. If you had domain users with the same name but differentcapitalization, the upgrade process drops the user that was added last to the domain.

Default Users and Groups for a DomainEffective in version 8.5, a default administrator and domain administrator are created during installation. The username for the default administrator is Administrator. No default groups are created.

Previously, you created a domain administrator during installation.

Default Users and Groups for a Repository ServiceEffective in version 8.5, no default users or groups are created when you create a Repository Service in aPowerCenter domain.

Previously, the following default users and groups were created when you created a Repository Service:

¨ User with the repository database user name and password

¨ User with the name Administrator

¨ Public and Administrators groups

Default Repository Administrator AccountEffective in version 8.5, the default repository administrator from the repository is merged with the existing defaultAdministrator user account in the PowerCenter domain when you upgrade users and groups for a repository. Thepassword for the default repository administrator is not merged. You can change the password for theAdministrator user account after you complete the user upgrade process.

Logging In to PowerCenter ApplicationsEffective in version 8.5, you enter a user name, password, and security domain to log in to PowerCenterapplications. The security domain is Native or the name of a specific LDAP security domain. The Security Domainfield appears when the PowerCenter domain contains an LDAP security domain.

Previously, you entered a user name and password to log in to PowerCenter applications.

Service Manager AuthenticationEffective in version 8.5, the Service Manager authenticates users who log in to the Administration Console,PowerCenter Client, Metadata Manager, and Data Analyzer. The Service Manager uses the following types ofauthentication:

¨ Native. When you log in to an application as a native user, the Service Manager authenticates your user nameand password against the user accounts in the domain configuration database.

126 Chapter 29: PowerCenter Security (8.5)

¨ Lightweight Directory Access Protocol (LDAP). When you log in to an application as an LDAP user, theService Manager passes your user name and password to the external LDAP directory service forauthentication.

By default, the PowerCenter domain uses native authentication. You can configure the PowerCenter domain touse LDAP authentication in addition to native authentication.

Previously, each of the following PowerCenter applications used different authentication methods:

¨ Administration Console. You did not set up authentication. The Service Manager authenticated users whologged in to the Administration Console. The Service Manager did not use LDAP authentication.

¨ PowerCenter Client. You set up LDAP authentication for each repository or Repository Service. The repositoryauthenticated users who logged in to the PowerCenter Client. A repository could use repository authenticationor LDAP authentication, but not both authentication methods.

¨ Metadata Manager. You configured Metadata Manager to use repository or LDAP authentication. MetadataManager could not use both authentication methods. Metadata Manager authenticated users who logged in toMetadata Manager.

¨ Data Analyzer. You configured Data Analyzer to use repository or LDAP authentication. Data Analyzer couldnot use both authentication methods. Data Analyzer authenticated users who logged in to Data Analyzer.

Domain PrivilegesThis section describes changes to domain privileges.

Domain Privilege ChangesEffective in version 8.5, you assign domain privileges to users and groups to determine the actions that users canperform in the Administration Console and the infacmd and pmrep command line programs. You assign privilegesto users and groups on the Security page of the Administration Console.

Previously, you assigned privileges to users to grant users full or read-only access to the objects on which theyhad permission.

Domain users retain the same object permissions and receive the appropriate domain privileges during upgrade.

The following table shows the domain privileges that users receive during upgrade:

8.1.1 Permission On... 8.1.1 Privilege 8.5 Permission On... 8.5 Domain Privileges

Domain Full Domain Administrator role for the domain

Any object except for thedomain

Full Same objects - Access Administration Console- Manage Service Execution- Manage Services- Manage Nodes and Grids- Manage Domain Folders

Any domain object Read-only Same objects Access Administration Console

Domain Privileges 127

Domain Tasks Not Determined by PrivilegesEffective in version 8.5, some Administration Console tasks are determined by the Administrator role, not byprivileges and permissions. A user assigned the Administrator role for the domain can complete the following tasks:

¨ Configure domain properties.

¨ Create operating system profiles.

¨ Create services using the Configuration Assistant.

¨ Delete operating system profiles.

¨ Grant permission on domain objects using the Permissions tab.

¨ Grant permission on the domain and operating system profiles.

¨ Purge and export domain log events.

¨ Receive domain alerts.

¨ Run the User Domain Audit Report and the License Report.

¨ Shut down the domain.

¨ Upgrade PowerCenter using the Upgrade Wizard.

¨ View the PowerCenter Administration Assistant.

If you assign a user all privileges for the domain and then grant the user permission on all domain objects, theuser cannot complete these tasks.

Previously, all Administration Console tasks were determined by permissions and privileges.

PowerCenter Repository PrivilegesThis section describes the following changes to PowerCenter repository privileges.

Repository Service PrivilegesEffective in version 8.5, you assign a new set of Repository Service privileges to users and groups to determinethe actions that users can perform in the PowerCenter Client and in the pmcmd and pmrep command lineprograms. You use the Security page of the Administration Console to assign privileges to users and groups foreach Repository Service in the domain.

Previously, you used the Repository Manager to assign a different set of repository privileges to users and groupsfor each repository.

Users and groups who had repository privileges receive the appropriate Repository Service privileges or domainprivileges and permissions during upgrade. Some repository privileges correspond to 8.5 domain privileges.Domain privileges determine the actions that users can perform in the Administration Console and the infacmd andpmrep command line programs.

128 Chapter 29: PowerCenter Security (8.5)

The following table shows the 8.1.1 repository privileges and the associated Repository Service privileges anddomain privileges and permissions users receive during upgrade:

8.1.1 Repository Privilege 8.5 Repository Service Privileges 8.5 Domain Privileges and Permissions

Browse Repository - Access Repository Manager- Copy Folders- Create Queries

n/a

Use Designer - Access Designer- Create, Edit, and Delete Design Objects- Create, Edit, and Delete Sources and

Targets- Manage Design Object Versions- Manage Source and Target Versions

n/a

Use Repository Manager - Access Repository Manager- Copy Folders- Manage Deployment Groups- Create Labels- Manage Design Object Versions- Manage Folder Versions- Manage Run-time Object Versions- Manage Source and Target Versions

n/a

Use Workflow Manager - Access Workflow Manager- Access Workflow Monitor- Create, Edit, and Delete Run-time Objects- Execute Run-time Objects- Manage Run-time Object Versions- Monitor Run-time Objects

n/a

Admin Repository - Access Repository Manager- Manage Design Object Versions- Manage Run-time Object Versions- Manage Source and Target Versions

- Access Administration Console- Grant Privileges and Roles- Manage Service Execution- Manage Services- Manage Users, Groups, and Roles- Permission on the Repository Service- Permission on all Integration Services in

the domain that are associated with theRepository Service

Admin Integration Service Administrator role for the Repository Service - Access Administration Console- Grant Privileges and Roles- Manage Service Execution- Manage Services- Manage Users, Groups, and Roles- Permission on the Repository Service- Permission on all Integration Services in

the domain that are associated with theRepository Service

Super User Administrator role for the Repository Service - Access Administration Console- Grant Privileges and Roles- Manage Service Execution- Manage Services- Manage Users, Groups, and Roles- Permission on the Repository Service- Permission on all Integration Services in

the domain that are associated with theRepository Service

PowerCenter Repository Privileges 129

8.1.1 Repository Privilege 8.5 Repository Service Privileges 8.5 Domain Privileges and Permissions

Workflow Operator - Access Workflow Monitor- Manage Execution of Run-time Objects- Monitor Run-time Objects

n/a

Manage Connection - Access Workflow Manager- Create Connections

n/a

Manage Label - Access Repository Manager- Create Labels

n/a

Manage Folder - Access Repository Manager- Create Folders- Manage Folder Versions

n/a

Deploy - Access Repository Manager- Copy Folders

n/a

Manage Deployment Group - Access Repository Manager- Manage Deployment Groups

n/a

Repository Tasks Not Determined by PrivilegesEffective in version 8.5, some PowerCenter Client tasks are determined by folder and global object ownership andby the Administrator role, not by privileges and permissions.

If you assign a user or group all privileges for the Repository Service and then grant the user or group fullpermission on all repository objects, the user or group cannot complete these tasks.

The following table lists the tasks that a folder owner, global object owner, or a user assigned the Administratorrole for the Repository Service can complete:

Task Folder Owner Global ObjectOwner

User withAdministrator Role

Assign operating system profiles to repository folders if theIntegration Service uses operating system profiles.

Yes No Yes

Change the owner of folders and global objects. Yes Yes Yes

Configure folder and global object permissions. Yes Yes Yes

Connect to the Integration Service from the PowerCenterClient when running the Integration Service in safe mode.

No No Yes

Delete folders and global objects. Yes Yes Yes

Designate folders to be shared. Yes No Yes

Edit the name and description of folders. Yes No Yes

Previously, all PowerCenter Client tasks were determined by permissions and privileges.

130 Chapter 29: PowerCenter Security (8.5)

Use Repository ManagerEffective in version 8.5, when you merge users and groups, an existing repository user with the Use RepositoryManager privilege gets Purge Versions and Manage Folders privileges in PowerCenter 8.5.

Previously, repository users with the Use Repository Manager privilege could not purge versions or modify foldersin a repository. You can modify the user privileges to remove the purge and manage folder privileges after youupgrade the users and groups for a repository.

Metadata Manager Privileges and RolesEffective in version 8.5, you assign a new set of Metadata Manager privileges and roles to users and groups todetermine the actions that users can perform in Metadata Manager and Metadata Manager command lineprograms. You use the Security page of the Administration Console to assign privileges to users and groups foreach Metadata Manager Service in the domain.

Previously, you used the Metadata Manager application to assign a privileges or roles to users and groups foreach Metadata Manager instance.

Users and groups who had privileges receive the appropriate Metadata Manager privileges during upgrade.

The following table shows the 8.1.1 Metadata Manager privileges and roles and the associated Metadata Managerprivileges and roles:

8.1.1 Metadata Manager Privilege / Role 8.5 Metadata Manager Privilege / Role

Manage Class and Object Configuration Manage Model

Manage Repository, Class, and Association Type Manage Model

Manage Object and Object Association Manage Object

Advanced Consumer Metadata Service Advanced User

Advanced Provider Metadata Service Advanced User

Basic Consumer Metadata Manager Basic User

Basic Provider Metadata Manager Basic User

Intermediate Consumer Metadata Manager Intermediate User

Read-only Consumer Metadata Manager Basic User

System Administrator Administrator

Permissions on Domain ObjectsEffective in version 8.5, you assign object permissions to users or groups when you edit a domain object on theDomain tab or when you edit user or group permissions on the Permissions tab of the Administration Console.

Metadata Manager Privileges and Roles 131

Previously, you assigned object permissions to users on the Domain tab or on the Administration tab of theAdministration Console.

Permissions on PowerCenter Repository ObjectsThis section describes changes to permissions on PowerCenter repository folders and global objects.

Relational Connection Object PermissionsEffective in version 8.5, you must have read permission on connection objects to view them in the ConnectionObject Browser.

Previously, you could view connection objects if you had execute permission without read permission. To allowusers to view connection objects in the browser, you must grant read permission on the object.

Configuring Repository Folder and Global Object PermissionsEffective in version 8.5, you use different rules to configure PowerCenter repository folder and global objectpermissions.

The following table compares the rules you use in version 8.5 with the rules you used in previous versions:

Rules in 8.5 Rules in Previous Versions

The folder or global object owner or a user assigned theAdministrator role for the Repository Service can grant folderand global object permissions.

Users with the appropriate repository privileges could grantfolder and global object permissions.

Permissions can be granted to users, groups, and all others inthe repository.

Permissions could be granted to the owner, owner’s group,and all others in the repository.

The folder or global object owner and a user assigned theAdministrator role for the Repository Service have allpermissions which you cannot change.

You could change the permissions for the folder or globalobject owner.

During upgrade, the folder or global object owner is granted all permissions. The owner’s group and all others inthe repository retain the same permissions.

Copying Repository FoldersEffective in version 8.5, when you copy or replace a PowerCenter repository folder, the Copy Wizard copies thepermissions for the folder owner to the target folder. The wizard does not copy permissions for users, groups, orall others in the repository to the target folder.

Previously, the Copy Wizard copied the permissions for the folder owner, owner’s group, and all users in therepository to the target folder.

Locking and Unlocking LabelsEffective in version 8.5, a user with read and write permission on a PowerCenter repository label can lock andunlock the label.

132 Chapter 29: PowerCenter Security (8.5)

Previously, the label owner or a user with the Super User privilege could lock and unlock a label.

Permissions on PowerCenter Repository Objects 133

C H A P T E R 3 0

Repository and Repository Service(8.5)

This chapter includes the following topics:

¨ Code Pages, 134

¨ Managing Repositories, 135

¨ MX Views and MX Data, 136

¨ Operating Mode, 136

Code PagesEffective in version 8.5, the following IBM EBCDIC code pages use 0x25 as the value of the end of line character:

¨ IBM037

¨ IBM1047

¨ IBM273

¨ IBM280

¨ IBM285

¨ IBM297

¨ IBM500

¨ IBM930

¨ IBM935

¨ IBM937

¨ IBM939

Previously, these code pages used 0x15 as the value of the end of line character.

If you upgrade flat file sources or targets that use these code pages and that use the end of line character as therow delimiter, the Integration Service incorrectly reads or writes the source or target data. You can use 0x15 asthe value of the end of line character in the IBM EBCDIC code pages by renaming the following file in the server\bin\NLS directory and the client\bin\NLS directory of the PowerCenter installation directory:

¨ On UNIX, rename package.bin to package.dat.

¨ On Windows, rename package8.5.bin to package8.5.dat.

To apply changes, restart the Designer and Workflow Manager after you rename the file.

134

Managing RepositoriesThis section describes changes to repository management.

Connecting to a RepositoryEffective in version 8.5, after you connect to a repository in the PowerCenter Client, you can connect to multiplerepositories in the client without having to log in to the additional repositories. If you want to connect to arepository using a different user account, you must disconnect from all repositories and then connect to arepository with the different user account.

Previously, you had to enter a user name and password to connect to each repository in the PowerCenter Client.

Creating a Repository ServiceEffective in version 8.5, if you create a Repository Service for a database with existing content and the databaseexisted in a different PowerCenter domain, verify that users and groups with privileges for the Repository Serviceexist in the current domain. The Service Manager periodically synchronizes the list of users and groups in therepository with the users and groups in the domain configuration database. During synchronization, users andgroups that do not exist in the current domain are deleted from the repository.

You can use infacmd to export users and groups from one domain and import them into another domain.

Previously, when you created a Repository Service for a database with existing content, all repository users andgroups were retained.

Managing User Connections and LocksEffective in version 8.5, you manage repository user connections and locks in the Administration Console.

Previously, you could manage repository user connections and locks in the Administration Console or theRepository Manager.

Restoring a RepositoryEffective in version 8.5, if you back up a repository and restore it in a different domain, verify that users andgroups with privileges for the source Repository Service exist in the target domain. The Service Managerperiodically synchronizes the list of users and groups in the repository with the users and groups in the domainconfiguration database. During synchronization, users and groups that do not exist in the target domain aredeleted from the repository. You can use infacmd to export users and groups from one domain and import theminto another domain.

Previously, all repository users and groups were restored.

Managing a Repository DomainEffective in version 8.5, a user who needs to connect to a global and local repository must have privileges for eachRepository Service. When the global and local repositories exist in different PowerCenter domains, the user musthave an identical user name, password, and security domain in each PowerCenter domain.

Previously, a user who needed to connect to a global and local repository needed an identical repository username and password in each repository.

Managing Repositories 135

Changing a Repository Code PageEffective in version 8.5, you cannot change a repository code page in the Repository Service properties. Tochange a repository code page after you create a Repository Service, back up the repository and restore it to anew Repository Service. When you create the new Repository Service, you can specify a compatible code page.

Previously, you could change a repository code page in the Repository Service properties.

MX Views and MX DataThis section describes changes to MX Views and MX Data.

REP_USERSEffective in version 8.5, the REP_USERS view removes some columns and includes the USER_ID,NAME_SPACE, USER_NAME, and STATUS columns. If you have reports that use the REP_USERS view, updatethem to access the modified REP_USERS view.

REP_USERS_GROUPS and REP_GROUPSEffective in version 8.5, PowerCenter removes the REP_USERS_GROUPS and REP_GROUPS views. If you havereports that use the REP_USERS_GROUPS and REP_GROUPS views, update them so that they no longeraccess these removed views.

Operating ModeEffective in version 8.5, when you change the operating mode from exclusive to normal, you must restart theRepository Service.

Previously, you had to restart the Repository Service only when you changed the operating mode from normal toexclusive.

136 Chapter 30: Repository and Repository Service (8.5)

C H A P T E R 3 1

Integration Service (8.5)This chapter includes the following topics:

¨ Datatype Processing, 137

¨ Character Conversion, 140

¨ Recovery, 142

¨ Post-Session Email, 142

¨ Pushdown Optimization, 142

¨ Performance, 143

¨ Real-time Processing, 145

Datatype ProcessingThis section describes changes to datatype processing.

BigintEffective in version 8.5, the Integration Service can process bigint, or 64-bit integer, data values. Thetransformation Bigint datatype has a precision of 19 and supports values between -9,223,372,036,854,775,808and 9,223,372,036,854,775,807.

Previous versions do not have a Bigint datatype.

Bigint Values in Generated KeysYou can use Bigint as datatype to increase the range of generated key values in transformations. You can usebigint values for the following generated key values:

Transformation Generated Keys

Lookup (dynamic) Sequence ID number

Normalizer Generated key sequence number

Sequence Generator NEXTVAL and CURRVAL

XML Source Qualifier Primary and foreign keys

137

When you create a Lookup, Normalizer, or Sequence Generator transformation, the Designer sets the maximumvalue for generated keys to 9,223,372,036,854,775,807. In previous versions, the maximum key value was2,147,483,647. When you upgrade to version 8.5, the upgrade process does not reset the range for generated keyvalues for existing transformations. For example, if you upgrade a mapping that contains a Sequence Generatortransformation, the upgrade process does not increase the sequence end value.

To increase the range of generated key values, edit the transformation as follows:

¨ Sequence Generator. To use large integer values in a Sequence Generator, increase the sequence end value.

¨ Lookup. To increase the maximum sequence ID number in a dynamic Lookup transformation, change thedatatype of the Lookup port from Integer to Bigint.

¨ Normalizer. To increase the maximum generated key sequence number in a Normalizer transformation,change the datatype of the generated key port from Integer to Bigint.

When you import an XML source, the Designer sets the maximum values for primary and foreign keys to9,223,372,036,854,775,807. In previous versions, the maximum key value was 2,147,483,647. When you upgradeto version 8.5, the upgrade process does not reset the range for primary and foreign key values in existing XMLSource Qualifiers. To increase the range of primary and foreign key values, reimport the XML source.

Using Bigint with SDK CodeYou can use Bigint as datatype with SDK code to create plug-ins for custom applications.

When you upgrade to PowerCenter 8.5, the upgrade does not change the datatype used in the SDK code toBigint. If you developed a plug-in for a custom application, you need to recompile the SDK code to use the Bigintdatatype.

Bigint Datatype Support for DatabasesYou can use the Bigint datatype in relational sources and targets. Bigint datatype support is added for thefollowing databases:

¨ Informix

¨ Teradata

When you upgrade to PowerCenter 8.5, the upgrade does not change the datatype of relational sources or targetsto Bigint.

Import the sources, lookups, and targets to use the Bigint datatype. The Integration Service converts thetransformation Bigint datatype to the datatype that supports bigint data for the following databases:

Database Datatype

Informix Int8

Teradata Bigint

Datetime ProcessingEffective in version 8.5, the Integration Service processes datetime data up to nanoseconds. The transformationDate/Time datatype has a precision of 29. Previously, the Integration Service processed datetime data up toseconds. The Date/Time datatype had a precision of 19.

138 Chapter 31: Integration Service (8.5)

Specifying the Default Date FormatYou can specify the default date format the Integration Service uses in Date functions and port-to-port conversionof text strings to datetime values. To specify the default date format, enter a date format in the DateTime FormatString attribute on the Config Object tab for a session configuration object. You can define date formats thatprocess values to the nanosecond.

For new session configuration objects, the default date format is MM/DD/YYYY HH24:MI:SS.US, which specifiesprecision to the microsecond. For upgraded session configuration objects, the default date format is MM/DD/YYYY HH24:MI:SS, which specifies precision to the second.

To support subsecond precision in the date format for upgraded sessions, you can perform any of the followingactions:

¨ Change the date format for the session.

¨ Change the date format for the session configuration object.

¨ Create a new session configuration object, and apply it to the upgraded sessions.

For new sessions, the default date format is the date format in the session configuration object.

Maintaining Backward CompatibilityBy default, the Integration Service does not process subseconds in upgraded sessions. When you upgrade toversion 8.5, the upgrade process enables the Pre 8.5 Timestamp Compatibility session attribute in all upgradedsessions and session configuration objects. The Pre 8.5 Timestamp Compatibility session attribute appears on theConfig Object tab in the session properties.

When this attribute is enabled, the Integration Service performs the following actions:

¨ Trims subseconds for all Timestamp values when reading from or writing to relational databases.

¨ Trims subseconds for all Timestamp values when writing to external loader intermediate target files.

¨ Maps Timestamp values to Oracle Date values when you override a non-Oracle database connection with anOracle connection in the session properties.

¨ Does not override any custom property you set to support subseconds in a previous version of PowerCenter.For more information about custom properties that support subseconds, visit the Informatica Knowledge Baseat http://mysupport.informatica.com.

To cause the Integration Service to process subseconds in an upgraded session, disable the Pre 8.5 TimestampCompatibility session attribute in the session or session configuration object, or create a new session configurationobject and apply it to the upgraded session.

You might also need to perform the following actions:

¨ If the session contains a flat file source or target, change the date format in the source or target to acceptsubseconds.

¨ If the session contains a Lookup or Stored Procedure transformation, change the subsecond precision from 0to any positive integer value up to 9.

¨ If the session contains an SQL override that uses a string value to specify a date, change the date format to theformat used in the source. For example, to convert the string value ‘01-Jan-2007’ for an Oracle source, use thefollowing Oracle function in the SQL override:

to_date (‘01-Jan-2007’, ‘mm/dd/yyyy’)

Using Subsecond Data with SDK CodeYou can use datetime data up to milliseconds in the SDK code to create plug-ins for custom applications.

Datatype Processing 139

When you upgrade to PowerCenter 8.5, the upgrade does not change the precision of the Date/Time datatype toprocess subseconds in the SDK code. If you developed a plug-in for a custom application, you need to recompilethe SDK code to process subsecond data.

IntegersEffective in version 8.5, when the Integration Service reads from a fixed-width flat file, the Integration Serviceparses integers with leading blank spaces and writes integer and small integer values to the target.

Previously, the Integration Service read integer and small integer data with a leading blank space as an invalidvalue. The Integration Service rejected the row and logged an error message in the session log.

Character ConversionThe Integration Service processes data internally using the Unicode UCS-2 character set. Effective in version 8.5,the Integration Service uses ICU to convert character data into Unicode to process data.

Previously, the Integration Service used GlobalC to convert character data into Unicode to process data.

Character Mapping ChangesEffective in version 8.5, the Integration Services may write a different hexadecimal value when it writes data to adatabase. ICU can have multiple hexadecimal values for the same character.

For example, when the Integration Service reads a character with value 0xED40 and the connection objects usethe MS932 code page, ICU converts 0xED40 to U+7E8A. Before the Integration Service writes data, ICUdetermines if it should convert U+7E8A to 0xED40 or 0xFA5C. The ICU character mapping for the MS932 codepage states that 0xED40 and 0xFA5C represent the same character. ICU converts U+7E8A to 0xFA5C instead ofusing the original value 0xED40. The Integration Service writes the hexadecimal value that the ICU conversionproduces to the database.

You may notice different output data if you determine the value of a character based on its hexadecimal value.

Previously, the hexadecimal value of a character did not change due to Unicode conversion.

Substitution Values for Inconvertible CharactersEffective in version 8.5, the replacement value for inconvertible characters has changed. Changes to thehexadecimal replacement value may increase the size of output data. You may need to allocate more space orcolumn length in targets.

Replacement values have changed for the following code pages:

Code Page Name Code Page ID Code Page Description 8.5HexadecimalReplacementValue

ISO-8859-2 5 ISO 8859-2 Eastern European 0x1A

ISO-8859-3 6 ISO 8859-3 Southeast European 0x1A

140 Chapter 31: Integration Service (8.5)

Code Page Name Code Page ID Code Page Description 8.5HexadecimalReplacementValue

ISO-8859-4 7 ISO 8859-4 Baltic 0x1A

ISO-8859-5 8 ISO 8859-5 Cyrillic 0x1A

ISO-8859-6 9 ISO 8859-6 Arabic 0x1A

ISO-8859-7 10 ISO 8859-7 Greek 0x1A

ISO-8859-8 11 ISO 8859-8 Hebrew 0x1A

ISO-8859-9 12 SO 8859-9 Latin 5 (Turkish) 0x1A

ISO-8859-10 13 ISO 8859-10 Latin 6 (Nordic) 0x1A

JapanEUC 18 Japanese Extended UNIX Code (incl. JIS X 0212) 0xF4 0xFE

ISO-8859-15 201 ISO 8859-15 Latin 9 (Western European) 0x1A

IBM930 930 IBM EBCDIC Japanese 0xFE 0xFE

IBM935 935 IBM EBCDIC Simplified Chinese 0xFE 0xFE

IBM937 937 IBM EBCDIC Traditional Chinese 0xFE 0xFE

IBM939 939 IBM EBCDIC Japanese CP939 0xFE 0xFE

MS932 2024 MS Windows Japanese, superset of Shift-JIS 0xFC 0xFC

MS1250 2250 MS Windows Latin 2 (Central Europe) 0x1A

MS1251 2251 MS Windows Cyrillic (Slavic) 0x1A

MS1252 2252 MS Windows Latin 1 (ANSI), superset of Latin1 0x1A

MS1253 2253 MS Windows Greek 0x1A

MS1255 2254 MS Windows Latin 5 (Turkish), superset of ISO 8859-9 0x1A

MS1258 2258 MS Windows Vietnamese 0x1A

JEF 9000 Japanese EBCDIC Fujitsu 0xFE 0xFE

KEIS 9001 HITACHI KEIS Japanese 0xFE 0xFE

JIPSE 9002 NEC ACOS JIPSE Japanese 0xFE 0xFE

UNISYS 9003 UNISYS Japanese 0xFE 0xFE

MELCOM 9004 MITSUBISHI MELCOM Japanese 0xFE 0xFE

JEF-K 9005 Japanese EBCDIC-Kana Fujitsu 0xFE 0xFE

Character Conversion 141

Code Page Name Code Page ID Code Page Description 8.5HexadecimalReplacementValue

KEIS-K 9006 HITACHI KEIS-Kana Japanese 0xFE 0xFE

JIPSE-K 9007 NEC ACOS JIPSE-Kana Japanese 0xFE 0xFE

UNISYS-K 9008 UNISYS-Kana Japanese 0xFE 0xFE

MELCOM-K 9009 MITSUBISHI MELCOM-Kana Japanese 0xFE 0xFE

JP-EBCDIC 9010 EBCDIC Japanese 0xFE 0xFE

JP-EBCDIK 9011 EBCDIK Japanese 0xFE 0xFE

Previously, the hexadecimal replacement value for these code pages was 0x3F.

RecoveryEffective in version 8.5, you can enable recovery for a session that has Stored Procedure and External Proceduretransformations. The transformations contain the Output is Repeatable and Output is Deterministic properties.Enable Output is Deterministic when the source output data will not change between sessions. Enable Output isRepeatable when the data will be in the same order between sessions. If you enable both properties, you canconfigure session recovery.

When you upgrade, the default value for Output is Repeatable is Based on Input Order. To recover, enable Outputis Deterministic and configure the session recovery strategy. When you create a transformation, the properties aredisabled for session recovery by default.

Previously, the Integration Service disabled session recovery if a session included these transformations.

Post-Session EmailEffective in version 8.5, you can attach a session log to a post-session email without configuring the session tocreate a text log file. The Integration Service includes the session log from the Log Manager and generates thesession log file to attach to the email.

Previously, you needed to configure the session to create a text log file to attach session logs to post-sessionemails.

Pushdown OptimizationThis section describes changes to pushdown optimization.

142 Chapter 31: Integration Service (8.5)

Allow Temporary View for PushdownEffective in version 8.5, the Allow Temporary View for Pushdown option replaces the view part of the To Sourcewith View value for the Pushdown Optimization option. Select this option to enable the Integration Service tocreate views in the source or target database while pushing transformation logic to the database. The IntegrationService must create temporary views in the database to push particular transformation logic to the database. TheIntegration Service stores the value for this option in the repository.

Previously, you could only create views in the source database and you had to use the To Source with View option.

Pushdown Optimization OptionEffective in version 8.5, the Pushdown Optimization option has updated values:

Value in previousversions

Value in version 8.5 Description of Change

Full Full No change.

None None No change.

To Source To Source No change.

To Source with View n/a This value is obsolete. The To Source with View value is now split intotwo separate options:- Pushdown Optimization. Select the To Source value to push the

transformation to the source database. You can also select To Targetto push the transformation to the target database.

- Allow Temporary View for Pushdown. Select to create a view in thedatabase. You can create views in the source or target database.

If a mapping has ‘To Source with View’ selected and you upgrade therepository, the upgrade program selects the ‘To Source’ value and selectsthe Allow Temporary View for Pushdown option for the mapping.

To Target To Target No change.

The Integration Service continues to store the value in the repository.

Previously, the To Source with View was a possible value for the Pushdown Optimization option.

PerformanceThis section describes changes to performance.

Date Formats for TO_CHAR() and TO_DATE() FunctionsEffective in version 8.5, you can push the TO_CHAR() and TO_DATE() functions to the database regardless of thedate string.

Previously, you could push the TO_CHAR() and TO_DATE() functions to a database if the default date string wasused.

Performance 143

$$PushdownConfig ParameterEffective in version 8.5, the $$PushdownConfig parameter has updated parameter values:

Parameter Value inprevious version)

Parameter Value inversion 8.5

Description of Change

Full Full No change.

n/a Seq This is a new parameter value. To create a sequence object on thedatabase, append “Seq” after the pushdown optimization type.

n/a View This is a new parameter value. To create a view on the database,append “View” after the pushdown optimization type.

None None No change.

To Source To Source No change.

To Source with View n/a This value is obsolete. The To Source with View value is now splitinto two separate options:- Pushdown Optimization. Select the To Source value to push the

transformation to the source database. You can also select ToTarget to push the transformation to the target database.

- Allow Temporary View for Pushdown. Select to create a view inthe database. You can create views in the source or targetdatabase.

If a mapping has ‘To Source with View’ selected and you upgradethe repository, the upgrade program selects the ‘To Source’ valueand selects the Allow Temporary View for Pushdown option for themapping.

To Target To Target No change.

Pushdown Optimization for Slowly Changing Dimension LogicEffective in version 8.5, you can push Type 1 and Type 3 slowly changing dimension logic to the database. If youconfigured slowly changing dimension logic using the Slowly Changing Dimensions Wizard from a previousrelease and want to push the transformations that comprise the slowly changing dimension logic to the database,you must recreate the slowly changing dimension logic using the latest Slowly Changing Dimensions Wizard.

Previously, the Integration Service could not push slowly changing dimension logic to the database.

If the slowly changing dimension logic contains a Lookup transformation that is configured to use any value, firstvalue, or last value when multiple matches are found and you want to enable pushdown optimization, you mustmodify the existing Lookup transformation.

To modify the Lookup transformation to enable pushdown optimization, set the lookup policy to Report on Error.

Pushdown Optimization for the Update OperationEffective in version 8.5, you can configure the Integration Service to push the update operation on a target to thedatabase.

Previously, you could push insert and delete operations on a target to the database, but not the update operation.

144 Chapter 31: Integration Service (8.5)

Real-time ProcessingThis section describes changes to real-time processing.

Recovery ProcessEffective in version 8.5, when you enable recovery for a real-time session that reads from a JMS or WebSphereMQ source, the Integration Service writes messages to the target and then sends an acknowledgement to thesource. The process and acknowledge model prevents data duplication during recovery.

Previously, the Integration Service sent an acknowledgement to the source before it wrote messages to the target.Data duplication was possible if the session failed before the Integration Service acknowledged the messages orcleared the recovery file.

Recovery Table and Recovery File StorageEffective in version 8.5, when you enable recovery for a real-time session that reads from a JMS or WebSphereMQ source and writes to a relational target, the Integration Service creates a recovery table in the target database.The recovery table stores the commit number and the message ID that the Integration Service committed to thetarget. The recovery table helps maintain data integrity during recovery so no data is lost or duplicated.

When you recover a session, the Integration Service uses the recovery information to determine where it stoppedprocessing messages. The Integration Service reads unprocessed messages from the source by using themessage ID in the recovery table.

Previously, when you ran a session, the Integration Service saved messages to a recovery file. If the sessionfailed, the Integration Service read unprocessed messages from the recovery file.

Effective in version 8.5, when you enable recovery for a real-time session that reads from a JMS or WebSphereMQ source and writes to a non-relational target, the Integration Service stores message IDs in a recovery file. If asession fails, the Integration Service retrieves unprocessed messages from the source by using the message ID inthe recovery file.

Previously, the Integration Service saved the entire message to the recovery file.

Recovery with RestartEffective in version 8.5, when you restart a failed real-time session with a JMS or WebSphere MQ source, theIntegration Service recovers unprocessed messages after it initializes the session. The failed session must beenabled for recovery. Recovery occurs when you start a workflow or task from the Workflow Manager or when yourestart a workflow or task from the Workflow Monitor.

Previously, if you restarted a real-time session using Start Workflow, Start Task, or Start Workflow from Task, theIntegration Service ran the session without recovery. The Integration Service cleared the recovery file and startedthe session. Unprocessed messages were possibly lost. To avoid data loss, you had to manually recover thesession and then restart it.

Stopping a Real-time SessionEffective in version 8.5, when you stop a real-time session, the Integration Service completes message processingfor the flush latency interval. When you stop a real-time session with a JMS source, WebSphere MQ source, orchanged source data from PowerExchange, the Integration Service stops reading messages from the source,continues to process messages in the pipeline, and writes messages to the target. If you stop a real-time sessionthat is recovering messages, the Integration Service stops reading from the source when it completes recovery.

Real-time Processing 145

Previously, if you stopped a real-time session or a real-time session that is recovering messages, the IntegrationService might not have processed all of the messages that were in the pipeline.

Partitioning ChangesEffective in version 8.5, the Integration Service fails a JMS or WebSphere MQ real-time session when you enablerecovery and create multiple partitions.

To run the upgraded sessions, delete the partitions or disable recovery.

Previously, the Integration Service ran the session according to the partitioning configuration. As a result, theIntegration Service sometimes processed duplicate messages during recovery.

Changes to Restart and Recover CommandsEffective in version 8.5, the restart and recover command behavior is changed for real-time sessions with a JMSsource, WebSphere MQ source, or changed source data from PowerExchange. The changed behavior affectssessions that are enabled for recovery.

The following table describes changes to these commands:

Command Behavior in 8.1.1 Behavior in 8.5

Restart The Integration Service restarts the session. The Integration Service recovers before it restartsthe session.

Recover The Integration Service recovers before it restartsthe session.

The Integration Service recovers the session.

146 Chapter 31: Integration Service (8.5)

C H A P T E R 3 2

Functions (8.5)This chapter includes the following topics:

¨ Built-in Functions, 147

¨ User-Defined Functions, 148

Built-in FunctionsThis section describes changes to built-in functions.

Date Functions with Format String ArgumentsEffective in version 8.5, the following functions can process datetime values up to nanoseconds:

¨ ADD_TO_DATE

¨ DATE_DIFF

¨ GET_DATE_PART

¨ IS_DATE

¨ ROUND (Dates)

¨ SET_DATE_PART

¨ TO_CHAR (Dates)

¨ TO_DATE

¨ TRUNC (Dates)

These functions take a format string as one of the arguments. If you want the function to process subseconds,specify a subsecond format string in the format argument. For example, to convert the string “4/15/200712:15:10.123456789” to a datetime value, use the following expression:

TO_DATE('4/15/2007 12:15:10.123456789', 'MM/DD/YYYY HH24:MI:SS.NS')

DATE_COMPAREEffective in version 8.5, the DATE_COMPARE function can compare dates that include subseconds. If you do notwant to include subseconds in a date comparison, use the TRUNC (Dates) function to truncate the subsecondportion of the date, and then compare the dates.

147

GREATESTEffective in version 8.5, the GREATEST function returns NULL if any argument is null. Previously, the GREATESTfunction returned NULL if all arguments were null.

LEASTEffective in version 8.5, the GREATEST function returns NULL if any argument is null. Previously, the GREATESTfunction returned NULL if all arguments were null.

MAKE_DATE_TIMEEffective in version 8.5, the MAKE_DATE_TIME function can return the date and time based on input values up tonanoseconds. Previously, MAKE_DATE_TIME returned the date and time based on input values up to seconds.

User-Defined FunctionsThis section describes changes to user-defined functions.

User-Defined Functions in the NavigatorEffective in version 8.5, user-defined functions appear in the Repository Navigator of the Repository Manager andthe Designer. They appear as a User-Defined Functions node in repository folders. You can right-click the User-Defined Function folder to create new user-defined functions. You can right-click a user-defined function in thefolder to manage the function.

Previously, you created, viewed, and managed user-defined functions in the User-Defined Function dialog box.User-defined functions you created in a previous version appear in the User-Defined Function folder in therepository folder in which you created the user-defined function.

Managing User-Defined FunctionsEffective in version 8.5, you can manage user-defined functions in one of the following ways:

¨ Click the User-Defined Functions option on the Tools menu in the Designer.

¨ Right-click the User-Defined Functions folder in a repository folder in the Designer.

¨ Right-click a user-defined function in a repository folder in the Designer.

Previously, you managed user-defined functions from the User-Defined Function Browser dialog box.

Validating User-Defined FunctionsEffective in version 8.5, you can validate a user-defined function from the following areas:

¨ Expression Editor when you create or edit a user-defined function

¨ Query Results window

¨ View History window

Previously, you could validate a user-defined from the Expression Editor when you created or edited a user-defined function.

148 Chapter 32: Functions (8.5)

Renaming User-Defined FunctionsEffective in version 8.5, if you change a user-defined function name, the Designer does not propagate the namechange to expressions that user the function. Mappings and workflows that use an expression with the user-defined function may be invalid.

Previously, if you changed a user-defined function name, any expressions that used the user-defined functionreflected the name change.

Copying User-Defined FunctionsEffective in version 8.5, you can add a user-defined function to deployment groups to copy the user-definedfunction to another folder or repository. Previously, if you wanted to copy a user-defined function to anotherrepository or repository folder, you needed to export the user-defined function to XML and import it.

Versioning User-Defined FunctionsEffective in version 8.5, user-defined functions are versioned. When you upgrade from a previous version, thePowerCenter Client considers each user-defined function to be the first version of the object.

Analyzing Dependencies for User-Defined FunctionsEffective in version 8.5, you can view dependencies for user-defined functions. Other user-defined functions,transformations, mappings, mapplets, workflows tasks, workflows, and worklets may be dependent on user-defined functions. Previously, you could not view dependencies for user-defined functions.

Querying User-Defined FunctionsEffective in version 8.5, you can query user-defined functions. Select User-Defined Function as the object type in aquery. Previously, you could not query user-defined functions.

User-Defined Functions 149

C H A P T E R 3 3

Web Services Provider (8.5)This chapter includes the following topics:

¨ Changes to Properties, 150

¨ Web Service Operations, 151

¨ Web Service Sources and Targets, 151

Changes to PropertiesEffective in version 8.5 the following changes were made to properties:

¨ You can associate the Web Services Hub with a Repository Service that runs on the same domain as the WebServices Hub. You cannot associate a Web Services Hub with a Repository Service in another domain.Previously, you could associate a Web Services Hub with a Repository Service in another domain.

¨ The Web Services Hub property MaxLMConnections has is renamed MaxISConnections. The functionality ofthe property remains the same. MaxISConnections is the maximum number of connections from the WebServices Hub to the Integration Service that can be open at one time.

¨ The following Web Services Provider reader properties are no longer available:

- Real-time Flush Latency

- Treat Real-time Flush as Milliseconds

The Integration Service no longer buffers messages for a specified amount of time. The Integration Servicesends messages to the Web Services Hub immediately.

¨ The default values for the following Web Services Provider reader properties have changed:

Property Name Default Value in8.1.1

Default Value in8.5

Description

Idle Time -1 180 Amount of time in seconds the Integration Service waits toreceive messages before it stops reading from the sourceand ends the session. The previous default value of -1indicates an infinite period of time. The new default valueof 180 indicates the Integration Service waits 180 secondsto receive messages before it shuts down.

Message Count 1 -1 The number of messages the Integration Service readsbefore it ends the session. The new default value of -1indicates an infinite number of messages.

150

Web Service OperationsEffective in version 8.5, the following changes were made to web service operations:

¨ The deinitializeDIServerConnection operation is deprecated. You no longer need to explicitly disconnect theclient application from the Integration Service.

¨ The batch Login and Logout operations are added to Data Integration web services. You no longer need theMetadata web services WSDL to create applications that call Data Integration web services operations thatrequire authentication.

¨ Parameters for the Batch web services operations have additional parameters for workflow instance names toidentify the instance of a web service workflow that is running.

Web Service Sources and TargetsEffective in version 8.5, the process of importing a web service source or target from a WSDL has changed in thefollowing ways:

¨ Default import mode. The default import mode for web services sources and targets is entity relationship.Previously, the default import mode was normalized hierarchical relationship.

¨ One target definition. When you create a web service target, one target definition is created. A fault responseis defined as an XML view, not a separate target definition. Previously, each fault response is a separate targetdefinition.

¨ XML views. The web service source or target definition do not contain message and header ports by default.Previously, the web service source or target definitions contain message and header ports in separate XMLviews. The message and header ports are no longer required. You can add the message and header ports forstaged mappings and backward compatibility.

¨ WSDL workspace. If you create a web service source or target definition from a WSDL, you can edit source ortarget definitions in the WSDL workspace. Previously, you could not edit source or target definitions in theWSDL workspace.

Web Service Operations 151

C H A P T E R 3 4

Command Line Programs (8.5)This chapter includes the following topics:

¨ infacmd , 152

¨ infasetup, 156

¨ pmcmd, 157

¨ pmrep, 158

infacmdThis section describes changes to infacmd.

New infacmd CommandsEffective in version 8.5, the following infacmd commands are new:

Command Description Comments

AddGroupPermission Assigns a group permission on an object. New command.

AddGroupPrivilege Assigns a privilege to a group in a PowerCenter domain. Ported from pmrep.

AddRolePrivilege Assigns a privilege to a role in a PowerCenter domain. New command.

AddUserPermission Assigns a user permission on an object. New command.

AddUserPrivilege Assigns a privilege to a user in a PowerCenter domain. Ported from pmrep.

AddUserToGroup Adds a native or LDAP user to a native group in a domain. Ported from pmrep.

AssignIStoMMService Assign an Integration Service to a Metadata ManagerService.

New command.

AssignRoleToGroup Assigns a role to a group for a domain or an applicationservice.

New command.

AssignRoleToUser Assigns a role to a user for a domain or an applicationservice.

New command.

152

Command Description Comments

BackupDARepositoryContents Backs up content for a Data Analyzer repository to a binaryfile.

New command.

CreateDARepositoryContents Creates content for a Data Analyzer repository. New command.

CreateGroup Creates a group in the native security domain. Ported from pmrep.

CreateMMService Creates a Metadata manager Service in a domain. New command.

CreateOSProfile Creates an operating system profile in a domain. New command.

CreateReportingService Creates a Reporting Service in a PowerCenter domain. New command.

CreateRole Creates a custom role in a domain. New command.

CreateUser Creates a user in the native security domain. Ported from pmrep.

DeleteDARepositoryContents Deletes repository content from a Data Analyzer repository. New command.

DisableUser Disables a user account in a domain. New command.

EditUser Edits the general properties for a user in a domain. Ported from pmrep.

EnableUser Enables a user account in a domain. New command.

ExportUsersAndGroups Exports native users and groups in a PowerCenter domainto a file.

New command.

ImportUsersAndGroups Imports native users and groups into a PowerCenter domain. New command.

ListAllGroups Lists all the groups in the native security domain. Ported from pmrep.

ListAllRoles Lists all the roles in a PowerCenter domain. New command.

ListAllUsers Lists all the users in a PowerCenter domain. Ported from pmrep.

ListGroupPrivileges Lists privileges for a group in a PowerCenter domain. Ported from pmrep.

ListLDAPConnectivity Lists the connection information for an LDAP server. New command.

ListOSProfiles Lists the operating system profiles in a domain. New command.

ListRepositoryLDAPConfiguration Lists the LDAP server configuration options for aPowerCenter domain.

New command.

ListRolePrivileges Lists privileges for a role in a PowerCenter domain. New command.

ListSecurityDomains Lists the LDAP and native security domains in a domain. New command.

ListServicePrivileges Lists all privileges for a domain or an application service. Ported from pmrep.

ListUserPrivileges Lists privileges for a user in a PowerCenter domain. Ported from pmrep.

RemoveGroup Removes a group from the native security domain. Ported from pmrep.

infacmd 153

Command Description Comments

RemoveGroupPrivilege Removes privileges from a group in a PowerCenter domain. Ported from pmrep.

RemoveOSProfile Removes an operating system profile from a domain. New command.

RemoveRole Removes a custom role from a domain. New command.

RemoveRolePrivilege Removes privileges from a role in a PowerCenter domain. New command.

RemoveUser Removes a user from the native security domain. Ported from pmrep.

RemoveUserFromGroup Removes a native or LDAP user from a native group in adomain.

Ported from pmrep.

RemoveUserPrivilege Removes privileges from a user in a PowerCenter domain. Ported from pmrep.

RestoreDARepositoryContents Restores content for a Data Analyzer repository from abinary file.

New command.

SetLDAPConnectivity Sets up the connection to an LDAP server. New command.

SetRepositoryLDAPonfiguration Lists the LDAP server configuration options for aPowerCenter domain.

New command.

UnassignISMMService Unassociates an Integration Service from a MetadataManager Service.

New command.

UnassignRoleFromGroup Removes a role from a group for a domain or an applicationservice.

New command.

UnassignRoleFromUser Removes a role from a user for a domain or an applicationservice.

New command.

UpdateMMService Updates the service options for a Metadata ManagerService.

New command.

UpdateOSProfile Updates properties for an operating system profile in adomain.

New command.

UpdateReportingService Updates the service and lineage options for the ReportingService.

New command.

UpgradeDARepositoryContents Upgrades content for an existing Data Analyzer repository. New command.

UpgradeDARepositoryUsers Upgrades users and groups in a Data Analyzer repository. New command.

Note: You may need to update your scripts to avoid errors.

Changed infacmd Commands

154 Chapter 34: Command Line Programs (8.5)

Effective in version 8.5, the following infacmd commands are changed:

Commands Description Comments

AssignRSToWSHubService Associates a repository with a WebServices Hub in a domain.

The following option is removed:- rd (-RepositoryDomain)

CreateIntegrationService Creates an Integration Service in a domain The following option is added:- ev (EnvironmentVariables)The following argument is added to the -so(-ServiceOptions) option:- FlushGMDWrite=value.The following option is removed:- rd (-RepositoryDomain)

CreateSAPBWService Creates an SAP BW Service in a domain. The following option is removed:- id (-IntegrationServiceDomain)

CreateWSHubService Creates a Web Services Hub in a domain. The following option is removed:- rd (-RepositoryDomain)The following options are now required:- rs (-RepositorService)- ru (-RepositoryUser)- rp (-RepositoryPassword)- ln (-LicenseName)

GetLog Fetches log events based on the criteriayou provide.

The following values can be specified withthe -st (-ServiceType) option:- DOMAIN (Domain)- MM (Metadata Manager Service)- RPS (Reporting Service)

GetSessionLog Fetches log events for the most recentrun of a session.

The following options are added to specifyconcurrent workflow:- in (RunInstance)- id (RunId)

GetWorkflowLog Fetches log events for the most recentrun of a workflow.

The following options are added to specifyconcurrent workflow:- in (RunInstance)- id (RunId)

ListServices Lists the services in a domain. The following options are removed:- un (UserName)- pd (Password)

UnAssignRSWSHubService Disassociates a repository from a WebServices Hub in a domain.

The following option is removed:- rd (-RepositoryDomain)

UpdateIntegrationService Updates the configuration properties forthe Integration Service.

The following option is removed:- rd (-RepositoryDomain)

UpdateWSHubService Updates a Web Services Hub in a domain. The following option is removed:- rd (-RepositoryDomain)

Note: You may need to update your scripts to avoid errors.

infacmd 155

infasetupEffective in version 8.5, infasetup commands can use -DatabaseConnectionString (-cs) option to specify theconnection string used to connect to the domain configuration database.

The following table lists the changed infasetup commands:

Command Description Comments

BackupDomain Backs up the configuration metadatafor the domain.

-DatabaseConnectionString (-cs) option added tospecify the connection string used to connect to thedomain configuration database.

DefineDomain Defines a domain on the currentmachine.

-DatabaseConnectionString (-cs) option added tospecify the connection string used to connect to thedomain configuration database.-HttpsPort (-hs), -KeystoreFile (-kf), and -KeystorePass(-kp) options added to configure HTTPS for a node.-ResourceFile (-rf) option is now required.

DefineGatewayNode Defines a gateway node on thecurrent machine.

-DatabaseConnectionString (-cs) option added tospecify the connection string used to connect to thedomain configuration database.-HttpsPort (-hs), -KeystoreFile (-kf), and -KeystorePass(-kp) options added to configure HTTPS for a node.

DefineWorkerNode Defines a worker node on the currentmachine.

-HttpsPort (-hs), -KeystoreFile (-kf), and -KeystorePass(-kp) options added to configure HTTPS for a node.

DeleteDomain Deletes domain metadata tables. -DatabaseConnectionString (-cs) option added tospecify the connection string used to connect to thedomain configuration database.

RestoreDomain Restores the configuration metadatafor the domain.

-DatabaseConnectionString (-cs) option added tospecify the connection string used to connect to thedomain configuration database.

UpdateGatewayNode Updates connectivity information for agateway node on the current machine.

-DatabaseConnectionString (-cs) option added tospecify the connection string used to connect to thedomain configuration database.-HttpsPort (-hs), -KeystoreFile (-kf), and -KeystorePass(-kp) options added to configure HTTPS for a node.

UpdateWorkerNode Updates connectivity information for aworker node on the current machine.

-HttpsPort (-hs), -KeystoreFile (-kf), and -KeystorePass(-kp) options added to configure HTTPS for a node.

Note: You may need to update your scripts to avoid errors.

156 Chapter 34: Command Line Programs (8.5)

pmcmdEffective in version 8.5, the following pmcmd commands have changed:

Command Description Comments

aborttask Aborts a task. -runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

abortworkflow Aborts a workflow. -runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

getsessionstatistics Displays session details including informationfor the folder, workflow, and task instance.Displays session status and statistics for eachtarget and source qualifier.

-runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

gettaskdetails Displays details for a task including folder andworkflow name. Also displays the task, status,and run mode.

-runinsname (-rin) option added to specifyconcurrent workflows.

getworkflowdetails Displays details for a workflow includingworkflow name, status, and run mode.

-runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

recoverworkflow Recovers a suspended workflow. -runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

startask Starts a task. -runinsname (-rin) option added to specifyconcurrent workflows.-norecovery option added to restart a sessionwithout recovery.

startworkflow Starts a workflow. -osprofile (-o) option added to specify operatingsystem profile assigned to a workflow.-runinsname (-rin) option added to specifyconcurrent workflows.-norecovery option added to restart a sessionwithout recovery.

stoptask Stops a task. -runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

stopworkflow Stops a workflow. -runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

waittask Instructs the Integration Service to wait for thecompletion of a running task before startinganother command.

-runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

waitworkflow Notifies you whether the workflow ransuccessfully or is not running.

-runinsname (-rin) and -wfrunid options added tospecify concurrent workflows.

Note: You may need to update your scripts to avoid errors.

pmcmd 157

pmrepThis section describes changes to pmrep.

New pmrep CommandsEffective in version 8.5, the following pmrep commands are new:

Command Description Comments

AssignPermission Assigns permissions on a global object. New command.

ChangeOwner Changes the owner name for a global object. New command.

RollbackDeployment Rolls back a deployment to purge a deployed version from the targetrepository or folder.

New command.

Note: You may need to update your scripts to avoid errors.

Changed pmrep CommandsEffective in version 8.5, pmrep commands have changed. The commands have new or modified options.

The following table lists the changed pmrep commands:

Command Description Comments

Connect Connects to a repository. -s option added to specify the security domainthat the user belongs to.

Create Creates the repository tables in the database. -s option added to specify the security domainthat the user belongs to.

CreateFolder Creates a new folder in the repository. -o option added to specify the security domainthat the owner belongs to.

DeleteObject Deletes an object. You can specify “User Defined Function” asobject type.

DeployDeploymentGroup

Deploys a deployment group. -s option added to specify the security domainthat the user belongs to.

DeployFolder Deploys a folder. -s option added to specify the security domainthat the user belongs to.

ListObjects Returns a list of objects in the repository. You can specify “User Defined Function” asobject type.

ModifyFolder Modifies folder properties. You can assign an operating system profile to afolder.-a option added to specify the security domainthat the owner belongs to.

158 Chapter 34: Command Line Programs (8.5)

Command Description Comments

Register Registers a local repository with a connectedglobal repository.

-s option added to specify the security domainthat the user belongs to.

Restore Restores a repository backup file to a database. The following option is added:-s. The security domain that the user belongs to.The following options are removed:- v. User name of the repository administrator or

another valid user defined in the externaldirectory service.

- x. Password for the user name as defined inthe external directory service.

- X. Password environment variable that storesthe password of the repository administrator asdefined in the external directory service.

- w. Removes user-name-login mapping.

Unregister Unregisters a local repository from a connectedglobal repository.

-s option added to specify the security domainthat the user belongs to.

Note: You may need to update your scripts to avoid errors.

Ported pmrep CommandsEffective in version 8.5, pmrep no longer supports several commands. The command line program infacmdincludes replacement commands. Commands ported from pmrep to infacmd require a new set of parameters.

The following table lists the ported pmrep commands:

Command infacmd ReplacementCommand

Description

AddPrivilege AddGroupPrivilegeAddUserPrivilege

Adds a privilege to a user or a group.

AddUserToGroup AddUserToGroup Adds a user to a group.

ChangePasswd ResetPassword Changes the password of the user currently connected to therepository.

CreateGroup CreateGroup Creates a group.

CreateUser CreateUser Creates a user.

EditUser EditUser Edits the profile of a user.

ListAllGroups ListAllGroups Lists all groups registered with the repository.

LsPrivileges ListGroupPrivilegesListRolePrivilegesListUserPrivileges

Lists the privileges granted to a user or group.

ListAllPrivileges ListServicePrivileges Lists all privileges that you can assign to a user or group.

ListAllUsers ListAllUsers Lists all users registered with the repository.

pmrep 159

Command infacmd ReplacementCommand

Description

RmGroup RemoveGroup Removes a group from the repository.

RmPrivilege RemoveGroupPrivilegeRemoveUserPrivilege

Removes a privilege from a user or a group.

RmUser RemoveUser Removes a user from the repository.

RmUserFromGroup RemoveUserFromGroup Removes a user from a group.

Note: You must update your scripts to avoid errors.

160 Chapter 34: Command Line Programs (8.5)

C H A P T E R 3 5

Transformations (8.5)This chapter includes the following topics:

¨ Complex Data Transformation (Unstructured Data), 161

¨ External Procedure Transformation, 161

¨ Java Transformation, 161

¨ Joiner Transformation, 162

¨ Sequence Generator Transformation, 162

Complex Data Transformation (Unstructured Data)Effective in version 8.5, the Unstructured Data transformation is renamed to the Complex Data transformation.

External Procedure TransformationEffective in version 8.5, the External Procedure transformation includes the Output is Repeatable and Output isDeterministic properties. The properties determine if the Integration Service can recover sessions that include thistransformation.

When you upgrade, the properties are configured for session recovery by default.

Java TransformationEffective in version 8.5, PowerCenter uses Java Development Kit (JDK) 1.5 to compile the Java code andgenerate byte code for the transformation. If the Java code in the Java Transformation is impacted by changes inJDK 1.5, update and recompile the Java code.

For example, the syntax for Map and HashMap was updated in JDK 1.5. You must update and recompile the Javacode if it contains the following line:

private static Map empMap = new HashMap();

Update the line of Java code to the following:

private static Map <Integer, String> empMap = new HashMap <Integer, String> ();

161

For more information about changes to JDK 1.5, see the Java 2 Platform Standard Edition 5.0 release notes: http://java.sun.com/j2se/1.5.0/docs/relnotes/features.html

Previously, PowerCenter used JDK 1.4 to compile the Java code and generate byte code for the transformation.

Joiner TransformationEffective in version 8.5, when you specify that the Joiner transformation uses sorted input you can configure thesort order of the master source data. By default, the master sort order is set to auto. Previously, the Joinertransformation properties did not have the option to specify the sort order.

Sequence Generator TransformationEffective in version 8.5, if you configure multiple partitions in a session on a grid that uses an uncached SequenceGenerator transformation, the numbers that the Integration Service generates for each partition are notconsecutive.

Previously, the numbers the Integration Service generated for each partition were consecutive. However,performance was slow, because the worker DTM and master DTM communicated for each block of data.

162 Chapter 35: Transformations (8.5)

C H A P T E R 3 6

Data Profiling (8.5)This chapter includes the following topics:

¨ Data Profiling Sessions, 163

¨ Data Profiling Reports, 163

Data Profiling SessionsEffective in version 8.5, you can run a profile session that uses partitioning with structure inference functions.

To use pipeline partitioning for existing profile sessions that contain these functions, regenerate the profilemapping from the Profile Manager.

Data Profiling ReportsEffective in version 8.5, you use the Reporting Service to run Data Analyzer reports on the Data Profilingwarehouse.

When you upgrade, create a Reporting Service. Use Data Profiling for the reporting source. By default, theReporting Service imports Data Analyzer Data Profiling Reports and sets up the data source and data connector inData Analyzer.

Previously, you installed Data Analyzer and the PowerCenter Reports. Then, you set up data sources and a dataconnector in Data Analyzer.

163

C H A P T E R 3 7

Data Analyzer (8.5)This chapter includes the following topics:

¨ User Account Policy, 164

¨ Authentication, 165

¨ Data Lineage, 165

¨ Weblogic and WebSphere Support, 165

¨ Customization of Style Sheets and Color Schemes, 165

¨ Change in jBoss Installation Path, 165

¨ Managing Data Analyzer Repository Content, 166

¨ Obsolete Utilities and Tools, 166

¨ Changes to Utilities, 167

¨ Change in Path for Tools and Utilities, 169

¨ Language Support, 169

¨ Multi-Select on Dashboard Filters, 170

¨ Panscopic and RDL Support, 170

¨ Unicode Support, 170

¨ Fax and Mobile Support, 170

¨ Access Management, 170

User Account PolicyEffective in version 8.5, if you have upgraded users from an earlier version of Data Analyzer, the account policy foruser accounts is no longer valid. Since you create and manage users in the PowerCenter Administration Console,Data Analyzer no longer supports the following options with respect to a user account:

¨ Cannot Change Password

¨ Password Never Expires

¨ User Must Change Password at Next Login

¨ Maximum Password Age

¨ Minimum Password Length

¨ Password Complexity

You can edit the passwords of Data Analyzer users in the PowerCenter native security domain, in the ManageAccount tab of Data Analyzer.

164

AuthenticationEffective in version 8.5, you use PowerCenter authentication methods to authenticate users logging in to DataAnalyzer. You log in to Data Analyzer in any of the following ways:

¨ From the Administration Console

¨ From PowerCenter Client tools

¨ From Metadata Manager

¨ Accessing the Data Analyzer URL from a browser

Data LineageEffective in version 8.5, you use the PowerCenter Administration Console to configure data lineage and set up theconnection to the Metadata Manager Service. You set up the lineage properties when you create a ReportingService. Use the Administration > System Management > Categories and Departments option in Data Analyzer toset up categories and departments for Data Lineage.

Weblogic and WebSphere SupportEffective in version 8.5, Data Analyzer does not support Weblogic and WebSphere application servers. DataAnalyzer runs only on jBoss application server.

Customization of Style Sheets and Color SchemesEffective in version 8.5, you cannot customize the style sheets or define color schemes. You cannot modify theData Analyzer style sheets to customize the Data Analyzer user interface. You cannot create new color schemesand use custom graphics, buttons, and logos to match the standard color scheme for the web applications in yourorganization.

Change in jBoss Installation PathEffective in version 8.5, the jBoss folder relative to the PowerCenter node installation folder is<PowerCenter_install folder>/server/tomcat/jboss. The ias.ear file under the ias subfolder is specific to everyReporting Service you create. For example, if you create a Reporting Service for PowerCenter Repository Reportsand call it PCRR_Reporting, the ias.ear file is ias-PCRR_Reporting.ear and is available under the following folder:

/server/tomcat/jboss/server/informatica/ias

Authentication 165

Managing Data Analyzer Repository ContentEffective in version 8.5, you can manage the contents of the Data Analyzer repository from the PowerCenterAdministration Console. You create the Reporting Service in the PowerCenter Administration Console and use theoptions in the Actions menu to complete the following tasks:

¨ Create contents in the repository.

¨ Backup contents of the repository.

¨ Restore contents to the repository.

¨ Delete contents from the repository.

¨ Upgrade contents of the repository.

¨ Upgrade users and groups in the repository.

Previously, you used the repository utilities or the command line interface in Data Analyzer to manage therepository contents.

Obsolete Utilities and ToolsEffective in version 8.5, some utilities are obsolete. You can use the PowerCenter Administration Console toperform some of the tasks included in the utilities.

The following table lists the obsolete utilities and tools in 8.5:

Utility Description

adminutil Contains the Update System Accounts utility. Data Analyzer uses this utility to modify the user nameand password for the Data Analyzer system administrator and system daemon.In version 8.5, this is merged with repositoryutils.

backuputil Contains the Repository Backup utility. Data Analyzer uses this utility to take a back up of theexisting Data Analyzer repository. You can now take a back up of the repository using the BackupContents option in the Actions menu of the Reporting Service in the PowerCenter AdministrationConsole.In version 8.5, this is merged with repositoryutils.

ear_repackagerutil Contains the EAR Repackager utility. Data Analyzer uses this utility to easily unpack the EAR file,modify the contents, and repackage the EAR file.In version 8.5, this is no longer available.

ldap_migration Contains the LDAPTool*.jsp. Data Analyzer uses this to synchronize the users between therepository and the LDAP directory service.In version 8.5, this is removed.

license Contains the License Update utility. Data Analyzer uses this utility to update the license for DataAnalyzer.In version 8.5, you use the PowerCenter Administration Console to update the license for DataAnalyzer.

notifyias Contains the PowerCenter Integration utility. Data Analyzer uses this utility to update reports in DataAnalyzer when a PowerCenter session completes.In version 8.5, PowerCenter generates the notifyias utility for every Reporting Service that you create.

166 Chapter 37: Data Analyzer (8.5)

Utility Description

upgradeutil Contains the Repository upgrade utility. Data Analyzer uses this utility to upgrade the repository froman existing version to the latest version.In version 8.5, this is merged with repositoryutils.

validationutil Contains the Repository validation utility. Data Analyzer uses this utility to check the repository tablesand ensure that these tables are valid.In version 8.5, this is merged with repositoryutils.

ProfilingReports Contains the objects for the Data Analyzer Data Profiling reports. Data Analyzer uses this to importthe objects to the Data Analyzer repository.In version 8.5, if you create a Reporting Service for the Data Profiling warehouse, PowerCenterimports the objects for the Data Profiling reports.

RepositoryReports Contains the objects for the PowerCenter Repository reports. Data Analyzer uses this to import theobjects to the Data Analyzer repository.In version 8.5, if you create a Reporting Service for the Repository Service, PowerCenter imports theobjects for the Repository reports.

Changes to UtilitiesEffective in version 8.5, the repositoryutil has changed. The repositoryutil contains the utilities to manage the DataAnalyzer repository. Data Analyzer does not support the GUI for repository utilities. You use the command lineinterface to access the repository utilities.

The following utilities have been merged with the repository utilities:

¨ adminutil

¨ backuputil

¨ upgradeutil

¨ validationutil

The following table lists the commands that you can use in the command line interface:

Command Description

backup Backs up the repository at the given location to the specified file. Overwrites the existing backupfile.

restore Restores the respository from the specified file. Overwrites the existing repository or creates anew schema if there is no repository.

create Creates and initializes a new repository

deleteContents Deletes the contents of the repository. You need to restore the repository after you delete theexisting contents.

deleteSchema Deleted the contents of the schema and removes it from the repository.

upgrade Upgrades the repository from an earlier version to the latest version.

Changes to Utilities 167

Command Description

validate Validates the repository against a set of rules.

renameGroup Renames the user groups in the repository as per the names specified in the rename file.

renameUser Renames the users in the repository as per the names specified in the rename file.

createJmsTables Creates tables for to store JMS-messages.

deleteJmsTables Deletes the tables that store JMS-messages.

uploadExcelTemplate Uploads a new default Excel template to the repository.

createMMViews Creates the views and tables that the MetadataManager requires, to perform data lineage.

deleteMMViews Deletes the views and tables that the Metadata Manager requires.

testUnicodeSupport Checks how the specified database handles Unicode support.

markUsersDeleted Marks the users that have not been migrated to the PowerCenter domain configuration database,for deletion.

In addition to the above commands, you need to specify the following options with each command:

Option Description

-dt The database type.The following values are supported:- mssql for Microsoft SQL Server, default port 1433- oracle for Oracle, default port 1521- db2 for IBM DB2, default port 50000- sybase for Sybase, default port 1433

-dh The hostname of the database server.

-dn The name of the database schema.

-du The name of the database user who has the required permissions on the database to make changes to thedatabase schema.

-dp The password of the user.

-dspace The tablespace name. This is required only for a DB2 database.

-f The name of the file. You use this only with the backup, restore, renameGroup, and renameUser commands.

-dport The TCP port of the database server. You use this option if you want to change the default port.

-dURL The URL of the JDBC connection. You use this option if you want to change the default JDBC connectionurl. If you specify the correct URL, the values that you specify in the -dt, -dh, -dport, and -dn are notconsidered.

The following examples describe the usage of the commands with the required options:

* java -jar ias-repositoryutils.jar create -dt mssql -dh localhost -dn da85 -du da85 -dp da85 * java -jar ias-repositoryutils.jar restore -dURL jdbc:informatica:oracle://oracleDB:1521;SID=da85Oracle -dn da85 -du da85 -f c:/backup.85.bkp

168 Chapter 37: Data Analyzer (8.5)

Change in Path for Tools and UtilitiesEffective in version 8.5, there is a change in the folder path for some tools and utilities. The following lists the toolsand utilities and the change in the folder path:

Utility/Tool Original Folder Path New Folder Path

repositoryutils <PowerCenter_install folder>/PowerCenter8.1.1/DataAnalyzer/repositoryutils

<PowerCenter_install folder>/DA-tools/repositoryutils

DAAdministrativeReports

<PowerCenter_install folder>/PowerCenter8.1.1/DataAnalyzer/AdministrativeReports

<PowerCenter_install folder>/DA-tools/AdministrativeReports

import-export util <PowerCenter_install folder>/PowerCenter8.1.1/DataAnalyzer/import-exportutil

<PowerCenter_install folder>/DA-tools/import-exportutil

maps <PowerCenter_install folder>/PowerCenter8.1.1/DataAnalyzer/maps

<PowerCenter_install folder>/DA-tools/maps

SDK <PowerCenter_install folder>/PowerCenter8.1.1/DataAnalyzer/SDK

<PowerCenter_install folder>/DA-tools/SDK

SQLServerJTA <PowerCenter_install folder>/PowerCenter8.1.1/DataAnalyzer/SQLServerJTA

<PowerCenter_install folder>/DA-tools/SQLServerJTA

GettingStarted <PowerCenter_install folder>/PowerCenter8.1.1/DataAnalyzer/GettingStarted

<PowerCenter_install folder>/DA-tools/GettingStarted.The sample data warehouse files are availablein the DataWarehouse.zip file in this folder.

Language SupportEffective in version 8.5, Data Analyzer no longer supports the following languages:

¨ Chinese (Simplified)

¨ French

¨ German

¨ Italian

¨ Portuguese (Portugal)

¨ Spanish

¨ Dutch

¨ Korean

Data Analyzer supports only English and Japanese.

Change in Path for Tools and Utilities 169

Multi-Select on Dashboard FiltersEffective in version 8.5, you can select multiple attribute values in the dashboard filters. You can also applymultiple filters to an indicator. Data Analyzer applies each filter in the order in which it appears on the dashboard.

Panscopic and RDL SupportEffective in version 8.5, Data Analyzer no longer supports Panscopic and RDL editing features. There is no viewsetup functionality in version 8.5. Previously, you set up report displays in the view tab with the Panscopic andRDL features.

Unicode SupportEffective in version 8.5, Data Analyzer supports Unicode to store user names.

Fax and Mobile SupportEffective in version 8.5, Data Analyzer no longer supports fax machines and mobile devices as alert deliverydevices.

Access ManagementEffective in version 8.5, you can create and manage users, groups, and roles in the PowerCenter Administrationconsole. You use Data Analyzer only to set the access permissions and data restrictions for the users and groups.

Previously, you managed users, groups, and roles in Data Analyzer.

When you upgrade, you must update the PowerCenter domain configuration database with the existing DataAnalyzer users.

To update the PowerCenter domain configuration database withe the existing Data Analyzer users, you can usethe Upgrade Users and Groups option in the Actions menu of the Reporting Service in the right pane of thePowerCenter Administration Console.

Note: You can no longer import or export XML files that contain users, groups and roles to the Data Analyzerrepository.

170 Chapter 37: Data Analyzer (8.5)

C H A P T E R 3 8

PowerCenter Repository Reports(8.5)

This chapter includes the following topics:

¨ PowerCenter Repository Reports, 171

¨ Running Reports, 171

¨ Schema Objects, 172

PowerCenter Repository ReportsEffective in version 8,5, the following PowerCenter Repository Reports have changed:

¨ Mapping Lookup Transformation. Does not display the attribute ID.

¨ Mapplet Lookup Transformation. Does not display the attribute ID.

The PowerCenter Repository Reports no longer includes the Users By Group report in the Public Folders >PowerCenter Repository Reports > Security folder.

Running ReportsEffective in version 8.5, you use the Reporting Service to run reports on the PowerCenter repository.

When you upgrade, create a Reporting Service. Use an enabled Repository Service for the reporting source. Bydefault, the Reporting Service imports PowerCenter Repository Reports and sets up the data source and dataconnector in Data Analyzer.

Previously, you installed Data Analyzer and the PowerCenter Reports. Then, you set up data sources and a dataconnector in Data Analyzer.

171

Schema ObjectsEffective in version 8.5, the following objects have been deleted from the PowerCenter Repository Reportsschema:

Object Type Object Name Folder Path

Metric User Count Metrics > Security Schema > Users

Attribute Contact Info Attributes > Security Schema > GroupsAttributes > Security Schema > Users

Attribute Description Attributes > Security Schema > Users

Attribute Group Description Attributes > Security Schema > Groups

Attribute Group ID Attributes > Security Schema > Groups

Attribute Group Name Attributes > Security Schema > Groups

Attribute User Description Attributes > Mapping Schema > UsersAttributes > Mapplet Schema > UsersAttributes > Session Schema > UsersAttributes > Source Schema > UsersAttributes > Target Schema > UsersAttributes > Transformation Schema > UsersAttributes > Version Schema > UsersAttributes > Workflow Schema > UsersAttributes > Worklet Schema > Users

Attribute User External ID Attributes > Security Schema > Users

Attribute User ID Attributes > Security Schema > Users

Attribute User Name Attributes > Security Schema > Users

Attribute Database Type Attributes > Security Schema > Repository

Attribute Database User Attributes > Security Schema > Repository

Attribute Host Name Attributes > Security Schema > Repository

Attribute Port Number Attributes > Security Schema > Repository

Attribute Repository Description Attributes > Security Schema > Repository

Attribute Repository Domain Name Attributes > Security Schema > Repository

Attribute Repository Name Attributes > Security Schema > Repository

Attribute Repository Type Attributes > Security Schema > Repository

172 Chapter 38: PowerCenter Repository Reports (8.5)

C H A P T E R 3 9

Metadata Manager (8.5)This chapter includes the following topics:

¨ Terminology Changes, 173

¨ Configuring Metadata Manager, 174

¨ Metadata Manager Console, 174

¨ Metadata Manager Reports, 174

¨ Metadata Exchanges, 178

¨ Models, 179

¨ Resources, 180

¨ Data Lineage, 182

¨ Metadata Objects, 182

Terminology ChangesEffective in version 8.5, Metadata Manager includes the following terminology changes:

Previous Term New Term

XConnect Metadata Exchange

Association Relationship

Metamodel Model

Metadata Tree Metadata Catalog

Source repository Resource

Object property Object attribute

173

Configuring Metadata ManagerEffective in version 8.5, you create and configure a Metadata Manager Service in the PowerCenter AdministrationConsole to run the Metadata Manager application. Metadata Manager runs as an application service in aPowerCenter domain. Use the Administration Console to configure the Metadata Manager application properties,application services, and repositories you want to use with Metadata Manager. You can also use the commandline program infacmd to create and configure the Metadata Manager Service.

Previously, Metadata Manager ran on an application server and was installed with PowerCenter. You configuredthe connections to the Integration Service and Repository Service in the Metadata Manager Console.

Metadata Manager ConsoleEffective in version 8.5, the Metadata Manager Console is obsolete. The functionality of the Metadata ManagerConsole is contained on the Load page of Metadata Manager. Metadata Manager uses the Metadata ManagerAgent to extract metadata from metadata sources.

Previously, the Metadata Manager Console extracted metadata from metadata sources.

Metadata Manager ReportsThis section describes changes to Metadata Manager Reports.

Running Reports Effective in version 8.5, you use a Reporting Service to run reports on the Metadata Manager repository.

When you upgrade, create a Reporting Service. Use a Metadata Manager repository for the reporting source. Bydefault, the Reporting Service imports Metadata Manager reports and sets up the data source and data connectorin Data Analyzer.

Previously, Metadata Manager reports were included in the PowerCenter installer.

Report Links Effective in version 8.5, you cannot create links to reports from metadata objects. If you want to report onmetadata objects in the metadata catalog, create a Reporting Service for the Metadata Manager repository andrun the reports in Data Analyzer.

Previously, you could create links to Metadata Manager reports for a metadata object.

Removed ReportsEffective in version 8.5, the following reports are removed:

¨ Reports in the PUBLIC > Data Integration > Operational & Administrative Reporting folder

¨ Reports in the PUBLIC > Business Intelligence > Operational & Administrative Reporting folder

¨ Data lineage and where-used analysis reports

174 Chapter 39: Metadata Manager (8.5)

Metadata Manager no longer loads operational metadata for data integration and business intelligence metadatasources.

DashboardsEffective in version 8.5, the following dashboards are removed:

¨ Quarter to Date BI Operational Activity

¨ Recent BI Operational Activity

¨ Recent Data Integration Activity and Performance

¨ Data Integration Historical Operations

Schema ObjectsThis section describes changes to schema objects.

Operational Schema ObjectsEffective in version 8.5, the following operational and administrative attributes and metrics have been deleted fromthe Metadata Manager Reports schema:

Object Type Location

Metric All metrics under the Metrics > Operational folder and subfolders.

Attribute All attributes under the Attributes > Operational Attributes folder and subfolders.

Note: Time Based Schedules have also been removed.

Other SchemaEffective in version 8.5, versioning tables and other unused Metadata Manager tables are removed. As a result,the following attributes and metrics have been deleted from the Metadata Manager Reports schema:

Object Type Object Name Folder Path

Metric Dummy Count Metrics > Impact Analysis > Element Associations

Attribute Association Eff From Dt Attributes > Element Association

Attribute Association Eff To Dt Attributes > Element Association

Attribute Association Id Attributes > Associations

Attribute Association Name Attributes > Associations

Attribute Association Sequence Attributes > Element Association

Attribute Attribute Eff From Dt Attributes > ODS Report Attributes > Level 1 > Element Attributes

Attribute Attribute Eff To Dt Attributes > ODS Report Attributes > Level 1 > Element Attributes

Metadata Manager Reports 175

Object Type Object Name Folder Path

Attribute Cal Day Dt Template Dimensions > Dates

Attribute Cal Day Flag Template Dimensions > Dates

Attribute Cal Month Flag Template Dimensions > Dates

Attribute Cal Qtr Flag Template Dimensions > Dates

Attribute Cal Week Flag Template Dimensions > Dates

Attribute Cal Year Flag Template Dimensions > Dates

Attribute Deleted Flag Attributes > From Elements

Attribute Deleted Flag Attributes > To Elements

Attribute Detail Text Template Dimensions > Status

Attribute Disabled Flag Attributes > ODS Report Attributes > Level 1 > Element

Attribute Disabled Flag Attributes > From Elements

Attribute Disabled Flag Attributes > To Elements

Attribute Eff From Dt Attributes > ODS Report Attributes > Level 1 > Element

Attribute Eff to Dt Attributes > ODS Report Attributes > Level 1 > Element

Attribute From Class Description Attributes > From Elements

Attribute From Class ID Attributes > From Elements

Attribute From Element Create Dt Attributes > From Elements

Attribute From Element Eff From Dt Attributes > From Elements

Attribute From Element Eff To Dt Attributes > From Elements

Attribute From Element Key Attributes > From Elements

Attribute From Element Name Attributes > From Elements

Attribute From Element Update Dt Attributes > From Elements

Attribute From Element Version Num Attributes > From Elements

Attribute From Repo Type Description Attributes > From Elements

Attribute From Repo Type Name Attributes > From Elements

Attribute From Repository Description Attributes > From Elements

Attribute From Repository Name Attributes > From Elements

176 Chapter 39: Metadata Manager (8.5)

Object Type Object Name Folder Path

Attribute Hh24miss Str Template Dimensions > Time Of Day

Attribute Last Record Flag Attributes > From Elements

Attribute Last Record Flag Attributes > To Elements

Attribute Level 0 - Level 1 Eff From Dt Attributes > ODS Report Attributes > Association

Attribute Level 0 - Level 1 Eff To Dt Attributes > ODS Report Attributes > Association

Attribute Level 1 - Level 2 Eff From Dt Attributes > ODS Report Attributes > Association

Attribute Level 1 - Level 2 Eff To Dt Attributes > ODS Report Attributes > Association

Attribute Level 2 - Level 3 Eff From Dt Attributes > ODS Report Attributes > Association

Attribute Level 2 - Level 3 Eff To Dt Attributes > ODS Report Attributes > Association

Attribute Repository Connection Attributes > Metamodel > Repositories

Attribute Repository Connection Insert Flag Attributes > Metamodel > Repositories

Attribute Repository Dbms Type Attributes > Metamodel > Repositories

Attribute Repository Host Name Attributes > Metamodel > Repositories

Attribute Repository Last Load Date Attributes > Metamodel > Repositories

Attribute Repository Last Load Status Attributes > Metamodel > Repositories

Attribute Repository User Name Attributes > Metamodel > Repositories

Attribute Repository Vendor Name Attributes > Metamodel > Repositories

Attribute Repository Version Num Attributes > Metamodel > Repositories

Attribute Status Code Template Dimensions > Status

Attribute Status Msg Template Dimensions > Status

Attribute Status Text Template Dimensions > Status

Attribute To Class Description Attributes > To Elements

Attribute To Class Id Attributes > To Elements

Attribute To Element Create Dt Attributes > To Elements

Attribute To Element Eff From Dt Attributes > To Elements

Attribute To Element Eff To Dt Attributes > To Elements

Attribute To Element Key Attributes > To Elements

Metadata Manager Reports 177

Object Type Object Name Folder Path

Attribute To Element Name Attributes > To Elements

Attribute To Element Update Dt Attributes > To Elements

Attribute To Element Version Num Attributes > To Elements

Attribute To Repo Type Description Attributes > To Elements

Attribute To Repo Type Name Attributes > To Elements

Attribute To Repository Description Attributes > To Elements

Attribute To Repository Name Attributes > To Elements

Attribute Valid Flag Attributes > From Elements

Attribute Valid Flag Attributes > To Elements

Attribute Valid Flag ODS Report Attributes > Level 1 > Element

Metadata ExchangesThis section describes changes to Metadata Exchanges.

Business Objects Metadata ExchangeEffective in version 8.5, you download and install the Metadata Manager Agent on the machine that hasconnectivity to the Business Objects source repository.

Previously, you installed and configured the Business Objects software on the machine hosting the MetadataManager Console in order to load metadata using a Business Objects Metadata Exchange.

Cognos Impromptu Metadata ExchangeEffective in version 8.5, you download and install the Metadata Manager Agent on the machine that has where theCognos Impromptu source files are located, instead of installing the Cognos Impromptu client software.

Previously, you installed and configured the Cognos Impromptu client software on the machine hosting theMetadata Manager Console in order to load metadata using a Cognos Impromptu Metadata Exchange.

Microstrategy Metadata ExchangeThis section describes changes to Microstrategy Metadata Exchange.

Installing Microstrategy Client SoftwareEffective in version 8.5, you download and install the Metadata Manager Agent on the machine that hasconnectivity to the Microstrategy source, instead of installing the Microstrategy client software.

178 Chapter 39: Metadata Manager (8.5)

Previously, you installed and configured the Microstrategy client tools on the machine hosting the MetadataManager Console in order to load metadata using a Microstrategy Metadata Exchange.

Reporting MetadataEffective in version 8.5, the Microstrategy Metadata Exchange extracts the following reporting metadata objecttypes:

¨ Consolidation

¨ Consolidation Element

¨ CustomGroup

¨ Document

¨ Report

¨ HTML Document

¨ Graph

¨ Grid

¨ Local Filter

¨ View Filter

¨ Report Field

¨ Report Object

¨ Report Object Detail

¨ Subtotal

Previously, Metadata Manager did not extract reporting metadata from Microstrategy.

ModelsThis section describes changes to Metadata Manager models.

Creating and Configuring ModelsEffective in version 8.5, you create and configure custom and packaged models on the Model page in MetadataManager. When you create or configure a custom model, you configure the following components for a model:

¨ Classes

¨ Attributes

¨ Relationships

You can also add custom attributes to packaged models.

The Model page includes a simplified interface to browse and create and configure models. You do not deriveclasses, relationships and attributes from Common Warehouse Model (CWM) format, or configure the followingmodel components:

¨ Originators

¨ Repository types

¨ Packages

¨ Repository type root classes

Models 179

When you upgrade Metadata Manager, the upgrade process converts any custom models in the previousMetadata Manager repository to custom models on the Model page in Metadata Manager. Metadata Manageradds any class in the custom model to the Other Classes folder for the model.

Importing and Exporting ModelsEffective in version 8.5, you can import and export custom models or custom attributes added to packagedmodels. You cannot export all classes, attributes, and relationships for a packaged model. For example, youexport a packaged model to which you added a custom attribute. Only the custom attribute is exported, and notthe complete model.

Previously, you could export both custom and complete packaged models.

ResourcesThis section describes changes to resources.

ConfigurationEffective in version 8.5, you create resources using the Resource Wizard on the Load page in Metadata Manager.After you create a resource, you configure the resource, including connection assignments, using the ResourceProperties section on the Load page. You also delete resources using the Load page.

Previously, you created, configured, and deleted resources and configured connection assignments using theRepository Management task area of the Metadata Manager application.

Loading Multiple Resources SimultaneouslyEffective in version 8.5, you can load multiple resources of the same resource type simultaneously. WhenMetadata Manager loads metadata for a resource, the Integration Service runs a PowerCenter workflow specific tothe resource type. The Integration Service can run the same workflow concurrently. Previously, you could onlyload one source repository type at a time.

Agent URL Property Effective in version 8.5, you must configure the Agent URL property for the following resource types when youcreate a resource or upgrade Metadata Manager:

¨ Business Objects

¨ Cognos Impromptu

¨ Cognos ReportNet Report Manager

¨ ERStudio

¨ ERwin

¨ Hyperion Essbase

¨ IBM DB2 CubeViews

¨ Rational Rose

¨ Microsoft Visio

¨ Microstrategy

180 Chapter 39: Metadata Manager (8.5)

¨ Oracle Designer

¨ Sybase PowerDesigner

You use the Metadata Manager Agent to extract metadata from metadata sources. The Metadata Managerapplication includes a Metadata Manager Agent, or you can download and install the Metadata Manager Agent ona Windows machine.

You must download and install the Metadata Manager Agent in the following situations:

¨ You want to extract metadata from Business Objects, Cognos Impromptu, or Microstrategy metadata sources.

¨ The Metadata Manager application runs on a UNIX machine.

You can also install the Metadata Manager Agent on the machine where metadata source files for resources arelocated.

Previously, Metadata Manager required the client applications installed on the Metadata Manager Consolemachine to extract the metadata for Business Objects, Cognos Impromptu, or Microstrategy.

JDBC Connection URL and Source JDBC URL PropertiesEffective in version 8.5, you must configure the JDBC Connection URL or Source JDBC URL property for thefollowing resource types:

¨ Database Management (IBM DB2, Informix, Oracle, Microsoft SQL Server, Sybase, Teradata)

¨ Data Analyzer

¨ PowerCenter

Metadata Manager requires the JDBC connection information to perform certain resource tasks. For example,Metadata Manager requires the JDBC connection information when it verifies connection information for aresource.

When you upgrade Metadata Manager, you must configure the JDBC connection information for any applicableresource.

Encoding Property Effective in version 8.5, you configure the encoding property for all resource types on the Load page in MetadataManager.

If you configured a different encoding for a resource and upgrade Metadata Manager, you must reconfigure theresource encoding.

Previously, you configured the encoding for a resource in SuperglueUmbrella.config.

SchedulingEffective in version 8.5, you can configure multiple properties for resource load schedules, including the date andtime the schedule starts and the frequency in which the resource loads repeats. You configure schedules on theLoad page in Metadata Manager. You can also use mmcmd to schedule resource loads using an externalscheduler.

When you upgrade Metadata Manager, the upgrade process removes any previously configured schedules. Youmust create and assign schedules to any resource you want to load on a schedule.

Previously, you could only create a daily schedule and you configured schedules in the Scheduling task area inthe Metadata Manager application.

Resources 181

Data LineageThis section describes changes to Data Lineage.

Lineage HistoryEffective in version 8.5, Metadata Manager does not display data lineage analysis history for metadata objects.Metadata Manager opens multiple tabs to display multiple data lineage analyses instead. Previously, MetadataManager displayed the lineage history for the last nine objects on which you ran data lineage and you could onlyrun one data lineage analysis at a time.

Field-Level DetailsEffective in version 8.5, Metadata Manager displays field level details for a metadata object as a tool tip in the datalineage diagram. Previously, Metadata Manager displayed field-level details in a separate area in the MetadataManager interface.

Limits on Displayed ObjectsEffective in version 8.5, the data lineage diagram displays all objects in the data flow. You can expand or collapsethe objects in the data lineage diagram instead of filtering by repository and object type.

Previously, if the number of objects for a specific data flow contained more than 600 objects, the lineage diagramonly displayed lineage at the repository level.

Remote Access To Data LineageEffective in version 8.5, you can configure access to Metadata Manager data lineage from third-party applicationsusing the enhanced URL API.

Previously, you configured source object type mappings and used the Data Analyzer software development kit(SDK) to configure access to Metadata Manager data lineage from third party applications.

Data Lineage InterfaceEffective in version 8.5, the data lineage interface uses a Flash-based interface. You can pan and zoom thediagram, and highlight, expand, and collapse objects in the diagram. By default, Metadata Manager shows allobjects collapsed. In addition, you can open multiple data lineage diagrams simultaneously.

Previously, Metadata Manager expanded all objects expanded by default and you could not pan or zoom thediagram, or collapse or expand objects. In addition, you could only view one lineage diagram at a time.

Metadata ObjectsThis section describes changes to metadata objects.

182 Chapter 39: Metadata Manager (8.5)

Importing and ExportingEffective in version 8.5, you can only export custom metadata objects you added using the metadata catalog orcustom attributes you added to packaged resource types. If you can use a resource to load any metadata objectinto the Metadata Manager warehouse, you cannot export or import it.

Previously, you could export any object in the Metadata Manager warehouse.

Object and Report LinksEffective in version 8.5, you cannot create links to from one metadata object to another metadata object in themetadata catalog or to a Metadata Manager report. To create a link between two objects, create a relationshipbetween the two objects.

Previously, you could create links between objects in the metadata catalog or create links to Metadata Managerreports.

VersioningEffective in version 8.5, Metadata Manager does not store multiple versions of objects in the Metadata Managerwarehouse when you make changes to metadata objects. For example, if you edit a metadata object attribute,Metadata Manager does not store the previous version of the metadata object. In addition, you cannot viewdeleted versions of objects.

Previously, Metadata Manager stored multiple versions of metadata objects in the Metadata Manager warehouseand you could view deleted objects.

Deleting (Purging) Metadata ObjectsEffective in version 8.5, you purge metadata objects from the Metadata Manager warehouse on the Load page inMetadata Manager. Metadata Manager purges all metadata, including profiling information for relational resources,for a resource. However, you can delete any custom metadata object you added using the metadata catalog onthe Browse page in Metadata Manager.

Previously, you configured a parameter file and ran the WF_DELETE PowerCenter workflow to delete metadatafrom the Metadata Manager warehouse.

RelationshipsEffective in version 8.5, you can create and delete relationships from custom metadata objects to metadataobjects for packaged resource types. You create relationships on the Browse page. You must create therelationship between the classes for the metadata objects on the Model page before you can create a relationship.

Previously, you could create a relationship between any two objects.

Searching Metadata ObjectsEffective in version 8.5, Metadata Manager creates index files for the metadata in the Metadata Managerwarehouse when you load a resource or modify the objects in the Shortcuts section on the Browse page. Whenyou search metadata, Metadata Manager queries the index files and not the Metadata Manager warehouse. Youconfigure the location of the index files when you create the Metadata Manager Service.

Previously, Metadata Manager searched the Metadata Manager warehouse directly.

Metadata Objects 183

Creating Metadata ObjectsEffective in version 8.5, you must create a model and class for metadata objects on the Model page in MetadataManager before you can add custom metadata objects in the metadata catalog. You cannot add objects toresources for packaged resource types. However, you can add attributes to metadata objects for packagedresource types.

Previously, you could add, edit, and delete metadata objects in the metadata catalog for both custom andpackaged source repository types.

184 Chapter 39: Metadata Manager (8.5)

C H A P T E R 4 0

PowerCenter Connect (8.5)This chapter includes the following topics:

¨ PowerCenter Connect Name Change, 185

¨ PowerExchange for JMS, 185

¨ PowerExchange for SAP NetWeaver BI, 185

¨ PowerExchange for WebSphere MQ, 186

¨ PowerExchange for SAP NetWeaver mySAP Option, 187

PowerCenter Connect Name ChangeEffective in version 8.5, all PowerCenter Connect products are renamed to PowerExchange. For example,PowerCenter Connect for JMS is renamed to PowerExchange for JMS.

PowerExchange for JMSEffective in version 8.5, when the Integration Service acknowledges messages to JMS, it acknowledges a batch ofmessages. The Integration Service sends this acknowledgement for real-time sessions that have recovery enabled.

Previously, the Integration Service sent an acknowledgement for each message.

PowerExchange for SAP NetWeaver BIThis section describes changes to PowerExchange for SAP NetWeaver BI.

Loading Data to SAP BWEffective in version 8.5, the Integration Service loads data to SAP BW based on the number of characters in a row.Previously, the Integration Service loaded data to SAP BW based on the number of bytes in a row.

185

BW OHS Source DefinitionsEffective in version 8.5, you can import an InfoSpoke from SAP as a BW OHS source definition. Previously, youimported an SAP transparent table or file created by the InfoSpoke as an SAP R/3 source definition.

BW Application ConnectionsThis section describes changes to BW application connections.

Connection String in SAP BW Application ConnectionEffective in version 8.5, you can optionally configure a connection string for an SAP BW application connection.The connection string value is a type A DEST entry in saprfc.ini. The Integration Service uses saprfc.ini to connectto the SAP BW system. If you do not enter a connection string, the Integration Service obtains the connectionparameters from the SAP BW Service. When you upgrade, the SAP BW application connections do not contain avalue for the connection string.

Previously, you could not enter a connection string.

SAP BW OHS Application ConnectionEffective in version 8.5, you configure an SAP BW OHS application connection to extract data from SAP BW.Previously, you used an SAP R/3 application connection.

Process ChainsEffective in version 8.5, you can configure and start a process chain in PowerCenter to extract data from SAP BW.You can run the following commands:

¨ pmsaputil setparams. Run to set third-party parameters for the InfoSpoke, which is part of the process chain.

¨ pmsaputil startchain. Run to start the process chain and to optionally set third-party parameters for theInfoSpoke, which is part of the process chain.

Previously, you could only start the process chain from SAP. You configured the third-party parameters using theBAPI RSB_API_OHS_DEST_SETPARAMS. You used the ZPMSENDSTATUS ABAP program to send the dataextraction status to the SAP BW Service.

Installing Transports to Read Data from SAP BWEffective in version 8.5, if you want to read data from SAP BW with mappings you created in a previous versionand the SAP BW system is separate from the SAP system, you need to complete the following tasks:

¨ Configure mySAP Option.

¨ Install the designated transports on the SAP BW system.

If you do not need to use mappings you created in a previous version to read data from SAP BW, you do not needto complete these steps.

PowerExchange for WebSphere MQThis section describes changes to PowerExchange for WebSphere MQ.

186 Chapter 40: PowerCenter Connect (8.5)

Selecting a Code PageEffective in version 8.5, you can select a code page for message data when you configure a queue connection fora WebSphere MQ source or target. Previously, the Integration Service selected a code page for the messagedata, which was the code page of the Integration Service. When you upgrade, the default code page is MSWindows Latin1 (MS1252).

Processing Unicode DataEffective in version 8.5, if the Integration Service runs the WebSphere MQ server library, it uses the codedcharacter set identifier (CCSID) of the message header to process Unicode message body data. If it cannotdetermine the CCSID of the message header, it uses the CCSID of the queue manager to process Unicodemessage body data.

If the Integration Service uses the WebSphere MQ client library, it uses the CCSID of the message header toprocess Unicode message body data. If it cannot determine the CCSID of the message header, it uses the codepage in the CCSID of the MQCCSID environment variable to process Unicode data. If there is no value for theMQCCSID environment variable, the Integration Service uses the default code page of the WebSphere MQ system.

The Integration Service uses the code page in the queue connection in the following cases:

¨ The Integration Service cannot retrieve the CCSID of the queue manager or MQCCSID environment variablewhen it uses the WebSphere MQ client library. You might not have authorization on WebSphere MQ to retrievethis information.

¨ The CCSID value of a WebSphere MQ message is invalid, or WebSphere MQ does not support the value, andthe Integration Service cannot use the CCSID of the queue manager.

Previously, the Integration Service used the global locale of the WebSphere MQ system to determine the codepage. Also, you could not select a code page in an MQ queue connection object.

PowerExchange for SAP NetWeaver mySAP OptionThis section describes changes to PowerExchange for SAP NetWeaver mySAP Option.

Processing BAPI/RFC DataThis section describes changes to processing BAPI/RFC data.

BAPI/RFC TransformationEffective in version 8.5, you import a BAPI/RFC transformation to process BAPI/RFC data. Previously, you createdan RFC/BAPI function mapping with the Generate RFC/BAPI Function Mapping Wizard.

Error HandlingEffective in version 8.5, you can configure a BAPI/RFC session to increase the error threshold when theIntegration Service encounters a non-fatal error. If a session is aborted, the Integration Service rolls back datafrom the target. Previously, the session failed when the Integration Service encountered an error. Also, theIntegration Service did not roll back data from the target if the session was aborted.

PowerExchange for SAP NetWeaver mySAP Option 187

Passing the Sender Partner Number to SAPEffective in version 8.5, SAP/ALE IDoc Prepare transformations you create include the port CONTROL_SNDPRNin the control input group. CONTROL_SNDPRN passes the sender partner number to SAP. If you do connect thisport to an upstream transformation, the Integration Service use the partner number value of SNDPRN on the IDocControl Record tab of the transformation, if any.

Previously, the SAP/ALE IDoc Prepare transformation did not contain the CONTROL_SNDPRN port. To pass thesender partner number to SAP, you needed to specify a value for SNDPRN on the IDoc Control Record tab of thetransformation.

If you want the Integration Service to pass the sender partner number to SAP without configuring the SAP/ALEIDoc Prepare transformation, recreate the transformation.

LANG Datatype ValidationEffective in version 8.5, if SAP does not provide Unicode libraries for the operating system of the IntegrationService, an error occurs if the Integration Service writes an invalid language code to a field of the datatype LANG.The error increments the error count.

If SAP provides Unicode libraries for the operating system of the Integration Service, the SAP system does notvalidate the language code the Integration Service passes to a field of the datatype LANG.

Previously, an error occurred on Unicode and non-Unicode SAP systems if the Integration Service wrote an invalidlanguage code to a field of the datatype LANG. The error incremented the error count.

saprfc.ini and sideinfo File InstallationEffective in version 8.5, the installer installs saprfc.ini and sideinfo in the following locations if the files do not exist:

Installation Platform sideinfo Location saprfc.ini Location

Client Windows 2000 \WINNT\system32\ \WINNT\system32\

Client Windows XP, 2003 \windows\system32\ \windows\system32\

Integration Service Windows 2000, 2003 server\bin in the PowerCenterServices installation directory

\WINNT\system32\ for Windows2000\windows\system32\ for Windows2003

Integration Service UNIX server/bin in the PowerCenterServices installation directory

server/bin in the PowerCenterServices installation directory

Previously, the installer installed saprfc.ini.infa_811 and sideinfo.infa_811. You needed to rename the files if youwanted to overwrite existing saprf.ini or sideinfo files.

Upgrading IDoc and DMI TransformationsIf the PowerCenter license you used in a previous version did not allow pipeline partitioning, complete thefollowing steps for each transformation you created in the previous version:

1. On the Properties tab of the transformation, clear the Requires Single Thread per Partition option.

2. In the session properties, delete partition points for the transformation.

188 Chapter 40: PowerCenter Connect (8.5)