Repository Guide

Informatica PowerCenter®
(Version 7.1.1)

Informatica PowerCenter Repository Guide Version 7.1.1 August 2004 Copyright (c) 1998–2004 Informatica Corporation. All rights reserved. Printed in the USA. This software and documentation contain proprietary information of Informatica Corporation, they are provided under a license agreement containing restrictions on use and disclosure and is 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. 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 as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(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 document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free. Informatica, PowerMart, PowerCenter, PowerChannel, PowerCenter Connect, MX, and SuperGlue are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software are copyrighted by DataDirect Technologies, 1999-2002. Informatica PowerCenter products contain ACE (TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved. Portions of this software contain copyrighted material from The JBoss Group, LLC. Your right to use such materials is set forth in the GNU Lesser General Public License Agreement, which may be found at http://www.opensource.org/licenses/lgpl-license.php. The JBoss materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Portions of this software contain copyrighted material from Meta Integration Technology, Inc. Meta Integration® is a registered trademark of Meta Integration Technology, Inc. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software is Copyright (c) 1999-2004 The Apache Software Foundation. All rights reserved. DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

Table of Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv PowerCenter 7.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv PowerCenter 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi PowerCenter 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvii Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvii Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . xxxviii Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix

Chapter 1: Understanding the Repository . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Repository Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Repository Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Repository Server Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Repository Manager . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Workflow Manager . . . . . . . . . . . . . . . . . . 7 Receiving Notifications in the Workflow Monitor . . . . . . . . . . . . . . . . . . 7 PowerCenter Server Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 User-Created Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Understanding Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Administering Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

i

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PowerCenter Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Building the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Reusing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Reusing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2: Using the Repository Manager . . . . . . . . . . . . . . . . . . . . . 19
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Displaying Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Navigator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Adding and Removing a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Adding a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Removing a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Working with Repository Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Connecting to a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Connecting to Multiple Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Exporting/Importing Repository Connection Information . . . . . . . . . . . 32 Searching for Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Performing Keyword Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Searching All Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Validating Multiple Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Comparing Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Truncating Workflow and Session Log Entries . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 3: Managing the Repository . . . . . . . . . . . . . . . . . . . . . . . . . 49
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Permissions and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Repository Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Navigating the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

ii

Table of Contents

Console Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Registering and Connecting to the Repository Server . . . . . . . . . . . . . . . . . . 58 Registering a Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Connecting to the Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Disconnecting from the Repository Server . . . . . . . . . . . . . . . . . . . . . . 59 Tuning Repository Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Updating Repository Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Increasing Repository Copy, Backup, and Restore Performance . . . . . . . 60 Copying a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Deleting a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Backing Up and Restoring a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Backing Up a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Restoring a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Starting and Stopping the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Enabling the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Starting the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Stopping the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Disabling the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Sending Repository Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Registering a PowerCenter Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Migrating the Repository to a Different Repository Server . . . . . . . . . . . . . . 77 Propagating Repository Domain Connection Information . . . . . . . . . . . . . . 78 Viewing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Viewing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Viewing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Closing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Closing Connections in the Repository Manager . . . . . . . . . . . . . . . . . . 83 Closing Connections in the Administration Console . . . . . . . . . . . . . . . 84 Registering and Unregistering Repository Plug-ins . . . . . . . . . . . . . . . . . . . 85 Registering a Repository Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Unregistering a Repository Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Registering and Unregistering LDAP Security Modules . . . . . . . . . . . . . . . . 88 Registering an LDAP Security Module . . . . . . . . . . . . . . . . . . . . . . . . . 88 Unregistering an LDAP Security Module . . . . . . . . . . . . . . . . . . . . . . . 95 Reading the Repository Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Log File Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Process Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table of Contents iii

Repository Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Repository Agent Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 4: Configuring the Repository . . . . . . . . . . . . . . . . . . . . . . 103
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Adding a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Editing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Removing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Exporting and Importing Repository Configurations . . . . . . . . . . . . . . . . . 115 Exporting a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . 115 Importing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . 115 Creating or Promoting a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Promoting a PowerCenter Repository . . . . . . . . . . . . . . . . . . . . . . . . . 117 Enabling Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Working with PowerCenter Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License Key Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License Key Repository Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Managing License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 5: Repository Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Default Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 User Groups and Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Creating a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Editing a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Deleting a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using Default Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using LDAP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Switching Between Default and External User Authentication . . . . . . . 133 Creating and Editing Repository Users . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Editing a User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Creating a Repository User Under an External Directory Service . . . . . 137

iv

Table of Contents

Editing a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Enabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Disabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Removing a Repository User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Default Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Extended Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Assigning and Revoking a Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Configuring Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Configuring Versioning Object Permissions . . . . . . . . . . . . . . . . . . . . 149 Managing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Viewing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Handling User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Creating an Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Repository Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Locking the Same Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Locking Within Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Locking with Cubes and Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 155 Locking Business Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Handling Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Viewing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Releasing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Chapter 6: Working with Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Repository Manager . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . 166 Organizing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Folder Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Folder Owner and Owner's Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Shared Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Configuring a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Table of Contents

v

Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Editing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Deleting a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Comparing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Compared Attributes and Object Differentiation . . . . . . . . . . . . . . . . . 174 One-Way and Two-Way Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . 176 Editing and Saving Results Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Steps for Comparing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 7: Local and Global Shortcuts . . . . . . . . . . . . . . . . . . . . . . 181
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Shortcuts Versus Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Understanding Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Default Shortcut Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Describing the Object and the Shortcut . . . . . . . . . . . . . . . . . . . . . . . 184 Locating the Referenced Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Creating a Local Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Creating a Global Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Configuring the Global Shortcut Environment . . . . . . . . . . . . . . . . . . 192 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Refreshing Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Copying a Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Renaming Source Qualifiers to Shortcut Sources . . . . . . . . . . . . . . . . . 196 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Chapter 8: Working with Versioned Objects . . . . . . . . . . . . . . . . . . 199
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Sample Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Viewing Results View Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Working with Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Viewing Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Labels Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Object Status Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Changing Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

vi

Table of Contents

Changing Folder Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Tracking Changes to Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Viewing Object History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Comparing Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Checking Out and Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Checking Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Viewing Checked Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Undoing a Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Deleting and Purging Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Deleting a Versioned Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Recovering a Deleted Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Purging a Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Chapter 9: Grouping Versioned Objects . . . . . . . . . . . . . . . . . . . . . 217
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Working with Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Creating and Editing Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Applying Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Working with Object Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Configuring Query Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Validating and Saving a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Running a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Viewing Query Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Sample Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Working with Deployment Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Creating and Editing a Deployment Group . . . . . . . . . . . . . . . . . . . . . 237 Viewing Deployment History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Rolling Back a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Working with Static Deployment Groups . . . . . . . . . . . . . . . . . . . . . . 239 Working with Dynamic Deployment Groups . . . . . . . . . . . . . . . . . . . 240

Chapter 10: Copying Folders and Deployment Groups . . . . . . . . . . 241
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 PowerCenter Server Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Using the Copy Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Copy Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Table of Contents

vii

Registered PowerCenter Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Copying Plug-in Application Information . . . . . . . . . . . . . . . . . . . . . . 247 Copying or Replacing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Copying Within a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Copying From Local Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Steps for Copying or Replacing a Folder . . . . . . . . . . . . . . . . . . . . . . . 250 Copying a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Copying Composite Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Copying Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Object Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Steps for Copying a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . 258

Chapter 11: Exporting and Importing Objects . . . . . . . . . . . . . . . . . 263
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Working with Objects and Object Types . . . . . . . . . . . . . . . . . . . . . . . 265 Working with Different Repository Versions . . . . . . . . . . . . . . . . . . . . 265 Permissions and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 The XML and DTD Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 CRCVALUE Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Exporting and Importing Multiple Objects and Object Types . . . . . . . . . . . 269 Working with Dependent Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Exporting and Importing Parent Objects . . . . . . . . . . . . . . . . . . . . . . . 271 Working with Object Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Shortcut Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Importing Shortcuts to Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Modifying an Exported XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Modifiable Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

viii

Table of Contents

Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Validating XML Files Against the DTD . . . . . . . . . . . . . . . . . . . . . . . 280 Validating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Resolving Object Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Steps for Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Steps for Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Chapter 12: Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Resolving Copy Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Steps for Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Copying Workflow Manager Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Workflows and Worklets . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Workflow Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Copying Designer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Copying Mapping and Mapplets Segments . . . . . . . . . . . . . . . . . . . . . 310

Chapter 13: Exchanging Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Steps for Exporting Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Steps for Importing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Chapter 14: Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Working with Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Creating Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Editing Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Deleting Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Chapter 15: Using Metadata Exchange (MX) Views . . . . . . . . . . . . . 333
Viewing the Repository Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 MX View Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Using PowerCenter Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . 335
Table of Contents ix

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 REP_ALL_SOURCE_FLDS . . . . . . . . . 368 REP_WIDGET_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 REP_ALL_TARGET_FIELDS . . . . . . . . 362 REP_MAPPING_PORT_CONN . . . . . . . . . . . . . . 353 REP_ALL_MAPPINGS . . . . . . . . . . . . . . Worklet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 REP_METADATA_EXTN_DEFINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 REP_TBL_MAPPING . . . . . . . . . . . . . . . 369 Workflow. . . . . . . . . . . . . . . . 357 REP_FLD_MAPPING . . . . . . . 363 Metadata Extension Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 REP_TARG_TBL_COLS . . . 355 REP_TARG_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Transformation Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 REP_ALL_TARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 REP_WIDGET_INST . . . . . . . 339 REP_ALL_SOURCES . . . . . . . . . . . . . . . . . . . . . . 358 REP_SRC_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . 338 Source Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 REP_SRC_FLD_MAP . . . . . . . . . . 360 REP_TARG_TBL_JOINS . . . . 364 REP_METADATA_EXTNS . . . . . 351 Mapping and Mapplet Views . . . . and Task Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 REP_SRC_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 REP_SRC_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 REP_SRC_FILE_FLDS and REP_SEG_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 REP_TARG_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 REP_WIDGET_DEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Database Definition View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .SQL Definition of Views . . . . . . . . . . . . . . . . . . . . 346 Target Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 REP_WIDGET_FIELD . . . . . . . . . . . . . . . 354 REP_ALL_MAPPLETS . . . . . . . . . . . . . . 371 x Table of Contents . . . . . . . . . . . . . 361 REP_MAPPING_UNCONN_PORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Integrating MX Views with Third-Party Software . . . . . . . . . . . . . . . . . 356 REP_TARG_FLD_MAP . . . . . . . . . 338 REP_DATABASE_DEFS . . . . . . 345 REP_SRC_TBL_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 REP_ALL_TRANSFORMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. 378 REP_WFLOW_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 REP_WORKFLOW_DEP . . . . . . . . . . . . . . . . . . . . 395 REP_REPOSIT_INFO . . . . . . . . 393 Repository View . . . . . . . . . . . . . . . 388 Security Views . . . . . 399 Table of Contents xi . . . . . . . . . . . . . . . . . . . . . . . . 375 REP_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 REP_SESS_PARTITION_DEF . . . . . . . . . . 382 REP_SESSION_INSTANCE_FILES . . . . . . . . . . . . . . . . . . . 381 REP_SESSION_INSTANCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 REP_SESS_LOG . 383 REP_SESS_WIDGET_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 REP_DEPLOY_GROUP . . . . . . . . 395 PowerCenter Server Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 REP_TASK_INST_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 REP_SESS_CONFIG_PARM . . 383 REP_COMPONENT . . . . . 385 REP_TASK_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 REP_DEPLOY_GROUP_DETAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 REP_TASK_INST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 REP_USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 REP_SESSION_FILES . . . . . . . . . . . . . . 374 REP_ALL_SCHEDULERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 REP_WFLOW_VAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 REP_CM_LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 REP_LOAD_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .REP_WORKFLOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 REP_SERVER_NET_REF . . . . . . . . . . . . . . . . . . . . 372 REP_ALL_TASKS . . . . . . . . 398 REP_VERSION_PROPS . . . . . 391 REP_GROUPS . . . . . . . . . . . . . . . 387 REP_SESS_TBL_LOG . . . . . . . . . . 390 REP_USER_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Deployment Views . . . . 380 REP_SESSION_CNXS . . . . . . . . . 396 REP_SERVER_NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 REP_SERVER_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 REP_CM_LABEL_REF . . . . . . . . . . . . . . . . . . . . . . . 397 Change Management Views . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 Connecting to a Repository (Connect) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Removing Repositories From the Cache (Removerepository) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Exiting pmrep (Exit) . . . . . . . . . . . . . . . . . . . . . . 429 Sending Notification Messages (Notify) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Using Native Connect Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Configuring Repository Passwords on Windows . . . . . . . . . 433 Registering Local Repositories (Register) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Importing Objects (ObjectImport) . . . . . 409 pmrep System Commands . . . . . 411 Cleaning up Persistent Resources (Cleanup) . 435 xii Table of Contents . . . . . . . . . . . . 414 Backing up a Repository (Backup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 REP_SUBJECT . . . . . . . . . . . . . 413 Adding Repository Configurations (Addrepository) . . . . . . . . . . . . . . . . . . . . . . . . . 417 Deleting a Connection (Deleteconnection) . . . . . . . . . . . 410 Getting Help (Help) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Running Commands in Interactive Mode . . . . . . . . . . . . . . . . 408 Configuring Repository Passwords on UNIX . . . . . . 421 Enabling a Repository (Enablerepository) . . . 423 Listing Tables by Session (Listtablesbysess) . . . . . . . . . . . . . . . . . . . . . 407 Using Password Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Listing Object Dependencies (ListObjectDependencies) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Running Commands in Command Line Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Specifying Options and Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Folder View . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 Chapter 16: Using pmrep and pmrepagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Running Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 pmrep Repository Commands . . . . . . . . . . . . . . 412 Adding a Server (Addserver) . . . . . . . . . . . . . . . . . . . . . 404 Using pmrepagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Listing Repository Objects (ListObjects) . . . . . . . . . . . . . . 421 Disabling a Repository (Disablerepository) . . . . . . . . . . . . 403 Overview . . 420 Deleting a Server (Deleteserver) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Creating a Relational Connection (CreateConnection) . 404 Using pmrep . . . . . . . 431 Exporting Objects (ObjectExport) . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . 456 Registering a User (Registeruser) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Creating a Group (Creategroup) . . . . . . . 460 Adding to a Deployment Group (AddToDeploymentGroup) . . . . . . . . . . . . . . . . . . . . 454 Listing All Groups (Listallgroups) . . . . . . . . . . . . . . . . . . . . . . 449 Adding a Privilege (Addprivilege) . . . . . . . . . . . . . . . . . 445 Updating Server Variables (Updatesrvvar) . . 457 Removing a Privilege (Rmprivilege) . . . . . . . . . . . . . . . . . . . 459 pmrep Change Management Commands . . . . . . . . . . . . 461 Labeling (ApplyLabel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Showing Connection Information (ShowConnectioninfo) . . . . . . 455 Listing All Privileges (Listallprivileges) . . . . . . . . . . . . . . . . . . . 447 Updating the Target Table Name Prefix (Updatetargprefix) . . . . . . 462 Checking In Objects (Checkin) . . . 450 Changing the Repository Password (Changepasswd) . . . . . . . . . . . . . . . . 437 Changing the Connection Name (SwitchConnection) . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Unregistering Local Repositories (Unregister) . . . . . . . . . . . . . . . . . . . . 465 Table of Contents xiii . . . . . . . . . . . . . . . . . . . . . . . . 447 pmrep Security Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 Creating a Deployment Group (CreateDeploymentGroup) . . . 438 Truncating Workflow and Session Logs (Truncatelog) . . . . . 455 Modify Folder Properties (ModifyFolder) . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Editing a User (Edituser) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Running Script Files (Run) . . . . . . . . . . 457 Removing a Group (Rmgroup) . . . . . . . . . . . . . . . . . . . . . . . . 437 Stopping a Repository (StopRepository) . . . . . . . . . 464 Clearing a Deployment Group (ClearDeploymentGroup) . . . . . . . . . . . . . . . . 458 Removing a User from a Group (Rmuserfromgroup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Updating the Notification Email Addresses (Updateemailaddr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Adding a User to a Group (Addusertogroup) . . . . . . 444 Updating the Source Table Owner Name (Updatesrcprefix) . . . . . . . . . . . 452 Deleting a Folder (DeleteFolder) . . . . . . 443 Updating Sequence Generator Transformations (Updateseqgenvals) . . . 455 Listing All Users (Listallusers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Creating a Folder (CreateFolder) . . 458 Removing a User (Rmuser) . . . . . . . . . . . . . . . . . . 442 Updating Server Details (Updateserver) . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Updating a Database Connection (UpdateConnection) . . . 452 Creating a User (Createuser) . 446 Updating Repository Statistics (UpdateStatistics) . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Object Import Control File Parameters . . . . . . . . . 509 Designer Tasks . . . 477 Restoring Teradata Repositories using Fastload (Bulkrestore) . . . . . . . . . . . . .Creating a Label (CreateLabel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Upgrading a Repository (Upgrade) . . . . 511 xiv Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Scripting pmrep and pmrepagent Commands . 510 Workflow Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Tips . . . . . . . . . . . . . . . . . . . . . . . . . 474 pmrepagent Commands . . . . . . . 480 Deleting a Repository (Delete) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 Appendix A: Working with pmrep Files . . . . 504 Deployment Control File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 Scripting pmrep and pmrepagent Commands . . . . . . . . . . . . . . . . . . . . . . 466 Deleting a Deployment Group (DeleteDeploymentGroup) Deleting a Label (DeleteLabel) . . . . . . . . . . . . . . . . . 477 Backing up a Repository (Backup) . 473 Validating Objects (Validate) . . . . . . . . 493 Using the Persistent Input File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Creating a Persistent Input File with pmrep . . . . 505 Example . . . . . . . . . . . . 495 Using the Object Import Control File . . . 466 . . . . . . . . . . 507 Appendix B: Permissions and Privileges by Task . 467 . 494 Creating a Persistent Input File Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 Unregistering Plug-ins (Unregisterplugin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 Example . . . . . . . . . . . . . . . . 467 Deploying a Deployment Group (DeployDeploymentGroup) Executing a Query (ExecuteQuery) Deploying a Folder (DeployFolder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Restoring a Repository (Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 Sample Import XML File . . . . . . 481 Registering a Plug-in (Registerplugin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 Listing Checked Out Items (FindCheckout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Undoing a Checkout (UndoCheckout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 Creating a Repository (Create) . . . 500 Using the Deployment Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 pmrep Tasks . . . . . . . . . . . . . . . . . . . 519 pmrepagent Tasks . . . . . . . . . . . 513 pmcmd Tasks . . . . . . . . 520 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 Table of Contents xv . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Workflow Monitor Tasks . . . . . . . . . . . . . . . 515 Repository Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xvi Table of Contents .

. . . . 39 .. . . . . . . . . . . . . . . . . . . . . . . . 4 . . . . . .. . . .. .. . . . . . . . . . . . . .. . . . .. . . .. . . . . . .. . . . . . . . . . . Query with Multiple Conditions .. . . . . . . Source Definition Object Properties . .. .. 8-4. . . . . . Referenced Shortcut Object . . . . . . . . . . . Administration Console . . .. One-Way and Two-Way Comparisons .. . . . . . 52 . 8-1.. . . . . . . . . . .. . . . .. . ... . . . . . 22 . . . . . . .. . . . . . . . ... .. . . Deployment Group Browser . . . . . . . . . . . . . . .. . .. . . . Activity Log Window . . . . . . . .. . . . . . .. .. . .. . . 2-2. .. . 11-1. .. . . . . . . 9-5. . . .... . .. . . . . . . . 9-2.. . . . .. . . . . PowerCenter Repository Connectivity . . .. . . . . .. . . 9-10. . 7-4. .... . . .. . . . . 43 . . .. . .. . . . . . . . . . . . . . . . . . 8-6. Repository User Names and External Login Names 6-1. . .. . 28 . .. . . . . . . .. . . . . .. . . . . . . . . 40 . . . . . . . .. . . . . . . . . . . . . . . . . 24 . . Repository Details . . . . . . . .. . . . .. . . .. . . . . . . . . . .. . . .. . . . . 2-6. . . . . .. . . . . . . . . .. . . . . ... . . . . . . . .. . Deployment Group History . ... . . . . . . ..... . . . . . .. .. .. . .. . . . . . . .. . . Sample Query Results .. . .. . .. . . . . . . .. . . . . .. . .. . . 2-5. . .. . . . . Dependency for Deployment Group Dialog Box . . .. Output Window .. . . . . . . . . .. . . . . . . 56 100 100 132 177 185 186 187 190 202 204 204 205 206 209 220 220 221 223 224 225 226 232 236 237 238 239 268 List of Figures xv . . . . . . .. . . . . .. . . . . . . .. . . . . . . . . . Label Editor Options . . . . .. . . . . . . . . . 3-5. . . . . ... .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version Properties . . 7-2. . . . . . . ... . CRCVALUE Code in an Exported XML File . . . . .. . . . . . . . . .. .. . . . .. 2-7. . .. . . 3-2. .. . . . . . . . . . . . . . . . . . .. . 2-1. . . . . . . . . .. . . . . 27 .. . . . . . . . . .. . ... . ... . .. . . . . . . . . . . . . . .. . . . Apply Label Dialog Box . . . .. .. . . . . . ... . . . .. . . . ... . 7-3. . ... 9-12. .. . . . . . . .. . .. 25 . . . . . . . . . . . .. ... .. .. . . ... . . . . . . .. . . .. . . .. . .. . Results View Windows List . . . . . . . . . . . . 9-7. . . . . . . . . .. . . . 41 . .. . . . . . . . . Apply Label Wizard . . .. . . . . . .. . . 2-9.. . . . . .. . . .. . ... 9-6. . . . . . . . . .. . .. . . . . . . . . .. .. . . Dependency Window .... . .. . Repository Manager Navigator . . Object and Shortcut Description . . . . . . . . . . .. . . . . . .. . . . .. . . ... . Object Properties . . . . . . . . . . . . . .. . . . . . . . ... . . 3-1. . .. .. . . . . . . . 3-4. .. . Object Dependencies Saved as HTML . .. . . . . . . .. . . . . .. . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3. . . . .. . . . . . . ... . .. ... . . . 9-11. . . . . . . . . . .. . . . . .. . . . .. .. . Object Status Properties . . .. . . . . ... . . . . . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . . . . . . . . . . Query Browser ... . . ... . 2-8. . . . .. . . 8-3. .. . . .. . .. . .. . . View Dependencies Window . Transformation Shortcut Icon . . . Validate Objects Results . . .. . .. . . .. . . .. . . . . . Repository Manager Components .. ... .. . . . . . . . . Labels Properties . ... 3-3. . . . . . . . . . . .. . . . . . 7-1. . . . . . . . . . . . . . .. . . . . . . . . . Application Log Message Detail . . . . . . . .. .... . . . . . . .. 9-9. .. . . .. . . . . . . . . . . . . . 9-8. . . . . . . . .. . . . . . . Query Editor . 9-4. . . . . 5-1. . . . . . . .. . . . . . . .. . . . . .. 9-3. . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . ... . .. . . . .. . . . . . . . . . . . ... . . ... . . . . . . .. .. . .. . .. . . .. . ... ... . . . . . . . . . . . . . . . Event Viewer Application Log Message . . . . . . . . .. . .. . ... . .List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 1-1. . . . . . . . . . . . . . . . . . . . . . . .. . .... . . . . .. . . . . . . 2-4. Deployment Group Editor . . 55 . . . . . . . ... . . . . . . .. . 8-5. . . . View History Window . Create a Global Shortcut .. . . . . Dependencies Dialog Box . . 8-2.. . 9-1. Label Browser . . . .. . . . . . . . . . . . . . . . . .

. ... .283 . .. . .. . . . . . . . .. .Resolve Specific Object Conflicts Conflict Resolution Wizard . . . .271 . ..303 xvi List of Figures . . . . . . .. . . . . . . . . .. .. . . . . . . . .298 .. .. .. . .. Import Wizard . . . .. . . . .. ... . . . . . .301 . .. . .. . . . .. . . .. . .Figure Figure Figure Figure Figure Figure Figure 11-2. Copy Wizard Resolutions . .. . . 11-3. . . .. . .. 12-2. . Copy Wizard Mapping Conflicts . . .. . . . . . . . . . .. . . . ... . . . . ... . . .. . . . . . .. 12-3. . .. . .282 . . .284 . .. The Copy Wizard .. . . . .. . . . . .. Export Options Dialog Box . .. .. . . . 12-1. . . . . . .. .. . . . . . . . . . . . . .. . .. .. . . . . . .. .. . . . . . . . . . . .Resolve General Object Conflicts Import Wizard . . . . . . . . .. . 11-4. . . . 11-5.

.. 37 . . . . . . . . . . .. 9-3. . . . . . . .. . . . . . . . . . . . Object Details Displayed in Repository Main Window . . . . ... . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Repository Privileges . . . . . . ... .. ... . . . 97 106 107 108 109 120 122 143 145 148 149 151 154 157 169 174 175 196 209 212 222 227 232 251 258 List of Tables xvii . . . . 6-2. . . . . . . . . . .. .. .. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 9-1. . . .. . . . . . . . .. . . . . . . . . . . . . Change In Object Status After Copying Deployment Group Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 . . . . . . .Network Tab . 39 .. . . . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . . LDAP Login Properties Options . . . . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . Repository Connection Properties . . . . . .. . . . . 43 . . . 3-10. . . .. . . . Repository Log Codes . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . . . 54 . . . . . . .List of Tables Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 2-1. . . . . . . . . . . . . . Repository User Connection Details . . . . . . . . . . . . . 93 . Repository Details . . . . 7-1. . . . . . . . .. . . . . . . . . . . . . . . . . . . . Copy Folder Wizard Prompts (Copying a Folder) . . . . . . . . . . . . . . . .. . . . . . . . .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5. 40 . . . . . . . . . . . . . . . . . . . .. . . . . . Versioning Object Security Levels . . . . . . Register Security Module Options. . . . . . . . . Compared Object Types and Attributes . . . 81 . . . . 55 . . . . . 6-3. . . . . . . . . . . . . . . . . . . . . . . . .Database Connection Tab ... . . . . . . . . . . . . . . 5-4. . . . . . . . . . . . . . . . .. . . . . Converting Special Characters in Repository License File Names . . . . . . . . . . . . . . . . 2-2. . . .. . . . . . ... . . .. . . . 3-9. . . . . . . . . . . . . . . . Copying Global or Local Shortcuts . . . . . . . . . . . New Repository . .. . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . 91 . 5-5. . . . 55 . . . . . Object Properties for View Dependencies Window . . . . . . . . . . . . . . . . . . . Validate Objects Properties. . . . . License File Compatibility Requirements . . . . .. . .. . . . . . . . Repository Locks . . . . . . 2-4. . . . . . . New Repository . . . . . . . . . . Folder Permissions . . . . . . . . . . . . . . . . . . 5-6. . . . . . . . . . . .. Repository Servers Node Details . . . . . . . . Compared Objects in Compare . . . . .. . . . . . . .. . . . . .. . . .. . . . . . . . . . . . . . 54 . . . . . . . 5-3. . . . . . . . Viewing Object Dependencies . . .. . .. . . . . Default Repository Privileges . . New Repository . . . . . . . .. . .. . . Tasks Available in View Checkouts Window . . . HTML Links for Performing Repository Tasks . . . . .. . . . . . . . . . 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5. . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . .. . Repositories Node Details . . . . . . . . .. . 3-6. . . . . 4-6. . .. . . . . . . . . . . . . . . Object Lock Properties . 10-2. . . . . LDAP Server Configuration Options . . . . . . . . . . . . .. . . . . . . . . . . 96 . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . 3-4. . . . . . . . . . . .. . . . 3-1. . . . . . . . . . . . . . . . . . Dependencies Options .. . . . . 2-5. . . . 10-1. New Repository . . . . . . . . . . . . . .. . . 3-2. . . . Query Parameters and Values . . . .. . . . . . . . . . . . . .. . . . . . .. . . Tasks Available in Query Results Window . Folder Object Security Levels . 6-1. . .. . .. . . . 8-1. . 4-4. . . . . . . . . . . . . . . . . . . . . . . .. . 26 . . . . . . . . . . . . . 94 . . . . . . . . . . . . . . . . . 5-2. . . . . . . . 3-3.Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LDAP Login Properties Options . . . . . . . 3-11. . .. . . . Object Lock Properties .. . . . . . . . . . . . . . . . . . . . . 8-2. . . . . . . . . . . . . . . .. . 4-3. 4-2. . . .General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3. . . . . . . . . ... . . . . . .. . . . . . . . . .. . . . 3-8. . . . . Label Options and Description .. . 5-1. . . .. 4-1. . . . . . . . . .. . . . . . . . . . . . . . . . 9-2. . . . . . . . . . . . . . . . . . . . . . Tasks Available in View History Window . . . . . . 5-7. . . . . .

. . .. . . . . . . . . . . .. . . . . 15-23... .. . REP_ALL_MAPPLETS MX View .. . . . . . .. . . . Copy Wizard Areas . .341 . . . REP_ALL_SOURCES MX View . 15-10.344 . . . . . . . . . . . 15-1. . . . . .. . .. . . . . . . . Metadata Import Wizard . . . . . .359 . . . .. . . .. . . . . . . .. . . .. . . . . . . . . Copy Wizard Resolutions . . . .. . . . . . . . . . . . . .. . .. . . . .. . . . . . . . . . . . . . . 15-6. Modifiable Repository Objects . . . . . . . . . . . . ... . . . . . . . .. . . . .. .. . . . 15-4. . . 11-5.. . . . REP_ALL_MAPPINGS MX View . . . . . . . . . . . . . . . . . . . . . REP_METADATA_EXTNS MX View .355 .. . .. . MX View Categories . . . . . 13-1. . . . Mapping and Mapplet Views .339 . . Dependent Objects Exported . . . . . . . . . . . .. . . . .361 . . . 14-1.. . . . . . ... . . .. . . 15-9. . . . . . . . .. . . . . .346 . . . . . . . . . .338 . . . .. . . .. . . . 15-7. . . . . . . . . . . . . . . . . . . . . . . .. .. .354 . . . . . . . . . . . . . . . SQL Script to Drop MX Views . . . . . ... ... . . . . .. . ..336 . . . . . . . . . . .. . . . . . . . . .Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 10-3. . . . . . .. .. 15-32. . REP_DATABASE_DEFS MX View . . . REP_SRC_MAPPING MX View .. . . . . . . . . Exporting and Importing Objects Permissions and Privileges 11-2..362 . . . 11-3. . . . Metadata Extension Views . . . Target Views . .345 . . 15-13. . 15-17. . . . . . ... . . . . . . . . . . . . . . . Mapping Source Fields . . . . . . . . . . . . . ... . .334 . . . . . .. . . .. . . . . 15-29. .. . . . . . . . . . ... . . . . .266 . .. 15-24. . . . . . . . . . . .339 . . . . . Transformation Views ... . . . 15-31. . . . . . . . . . . . . .. .. Options for Exporting and Importing Multiple Objects . . . . . . . ..300 . .. .. REP_TARG_TBL_JOINS MX View .. . . . . . . . REP_TBL_MAPPING MX View .. . . . . . . .278 . . . . . . .364 . . . . . . .. . .. . . . . .. . . . . .. .. .359 . . . . . . ... . . . . . . . . .. . . 15-15.. . . .. . . . .. . .. . . . . . . . . . .282 . .. . . Options for Exporting Objects . . . . . . . . . . . . .. .. .. . .. .299 . . . . . . . . .. . . .. . . .. .. . . . . . . . .. . .. . .. . . .. . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . .364 . . . . . . .. . . . . . . . . .. . .. . . . . . . . . . . . .. . .. . 12-2. . ... . . ... . . .. . . . ... . .. . . .358 . . REP_ALL_TARGETS MX View . . .269 . . . . . . 15-22. . .. .. . REP_TARG_MAPPING MX View .366 xviii List of Tables . . . . . . . . . . . . . . . . . . .259 . . . . . . . . .. . . . .. . . . . . .. .. . . . . . . . .. . . .. . . . . . . . . . . . . 15-28. . . . . .. . . . . . REP_SRC_TBLS MX View .351 . ... REP_MAPPING_PORT_CONN MX View . . . . . . REP_ALL_TARGET_FIELDS MX View . . . . . . . . 15-30. . . . . . Options for Creating Reusable Metadata Extensions . . . . . . . . . 15-25... . . . . REP_TARG_FLD_MAP MX View . .356 .349 .351 . . . . .. . . . . 15-3. . . . . . . . . 15-16. . . . .. . . . . . ..270 . . . . . SQL Script to Create MX Views . . . . .. .357 . . .271 . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . REP_SRC_TBL_FLDS MX Views . .. .. . . . . 15-5. . . . . . . . . . 15-8. 12-1. . . . . .. . . . . . . . . . . .. . . . . . . .347 .321 .. . . . . . . . . .. . .. . . . . . . . . . . . . . .. . . . . . . . . . . ... . . . .. . . REP_ALL_SOURCE_FLDS MX View . . . . .. . . . . . .. . .. . . . . . . .. .PowerCenter Options . . . . . . . . . . . . .. . . . . . . . . . . . 15-12. . . . . . . . . . . . .. Source Views . . . . . .. 11-6. . . . . . .. .. . . . . . 15-21. . . . . . . .. .. . . . . . . . . . . . . ... . . . 15-11. .336 . . . .360 . . ... . . . .363 . . . .. . . . . . . . .. . . . . REP_TARG_TBLS MX View . . 15-18. . . . . . . . . . .. . . . .343 . . . . .. . ..329 . . 15-19. . .. . . . . . . .. . . . . . . . . . . . . . . . . REP_FLD_MAPPING MX View . . . . . . REP_SRC_FILES MX View . . . . . .. . . . . .. . .. . . . . . . . 15-26. . . . . . . . . . REP_SRC_FILE_FLDS and REP_SEG_FLDS MX Views . .. . . . 11-4. . ... .. . . . . . REP_TARG_TBL_COLS MX View . . . . . . .. . . . . .. . REP_MAPPING_UNCONN_PORTS MX View . 11-1. . . Resolving General Conflicts During Import. . Copy Deployment Group Wizard Prompts . . . . . . .. . . . . .365 . . . . .353 . . . 15-20. REP_METADATA_EXTN_DEFINES MX View . . . . . . . . . . . . . . . . . . 15-2. . . . . . . . . . . 15-14. . . .. . . . . . .. 15-27. . . . . . . . . . . . . . .347 . . . . .. . ... . . . . . . . . . . . .

. ... . .. . . . . .. . . .. . . . . . . . . . . . .. REP_EVENT MX View . . . . . ... . .. . . . ... . . REP_EIDGET_ATTR MX View . 15-63. . .. REP_USERS MX View . .. . . . . . 15-52. . . ... .. . . . . . . REP_WORKFLOW_DEP MX View .. . . . .. . .. REP_WIDGET_DEP MX View . . . . REP_ALL_TASKS MX View . .. . . . . . ... . . .. ... .. . REP_CM_LABEL MX View . REP_SERVER_NET_REF MX View.. . . . .. REP_TASK_ATTR MX View . . . .. . .. .. . . 15-48. . .. ... REP_WIDGET_INST MX View . . . . 15-46. . .. . . . . . . . . .. . . .. . . .. . . . . . . . . .. . . .. ... . .. . . . . . REP_SESS_TBL_LOG MX View . . . .. . . . . . .. . . . . . . Change Management Views . . . . . . .. . . . . . ... . . . . . REP_VERSION_PROPS MX View ... . . .. . . .... . 15-65. . . . . . . . . . .. . .. . . . . REP_SERVER_NET MX View ... . .. . . . . ... . . . . REP_WFLOW_VAR MX View .. . . . . . . .... .. . REP_SESSION_CNXS MX View . . .. . . . . . 15-68. .. 15-61.. . . . . . .. . . . . .. . . .. .. . .. . . . . .. . . . . . . Deployment Views .. . . .. . . . . . . . . . . 15-39. . . . . . .. . . . . . . .. .. . . . .. .. . . . . .. . . . . . . . . . .. . . . .. . .. . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . 15-37. . . . 15-49.. .. .. .. .. . . . . . . . . . ... .. 15-69. REP_REPOSIT_INFO MX View . . . .. . . . . . . . ..... . . .. . . . REP_ALL_SCHEDULERS MX View .. . . . . . . . . .. . .. . . . .. . . . . . . .. . . . . . . . . . . REP_USER_GROUPS MX View . .. . . . . .. 15-35. . . 15-36. . .. .. ... . . ... . .. . . REP_SESSION_FILES MX View .. . .. . . . REP_DEPLOY_GROUP MX View . . .. .. .. . . . . .. . . . . . . . .... .. . . ... . . . . . . . . . .... ... . . 15-43. . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . REP_WFLOW_RUN MX View .. . . . . and Task Views . . . . . ..... REP_TASK_INST_RUN MX View . . . . .. . . . . . . . . . . . .. . . .Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 15-33. . . . . .... .. . . . . . .. .. . . . . . . . .... . . . . . 15-74. . ... . .. . . . . . . . . . .. . ... . . . . . . . . . . . . . .. . .... .. . . . . . . . . . .. . . REP_WIDGET_FIELD MX View . ... .. 15-41. . . . . .. . . . .. .. . . . . 15-62. . . . . . . . . . . . . . .... . . . . . . . . . . . 15-64.. . . . . .. 15-66. . .. . . . . . . . . .. . .. . .. .. .. . . . . .. . . . PowerCenter Server Views . . . . . . . . . 366 368 368 369 369 371 372 374 374 375 376 377 377 378 379 380 381 382 382 383 383 384 385 385 386 387 388 390 390 391 391 392 392 393 395 396 396 397 397 398 398 399 399 List of Tables xix . . . . . . . . . . . . .. . . . . .. . . . . . . . . 15-47. . . . . ... .. . . . .. . . . . . .. REP_TASK_INST MX View . . . . . 15-42. .. . . .. . . . 15-75. . . . . . .. .. . . . . . . .. . . . . . . . .. 15-34. . . .. . . . . . . . . . .. . . . . . 15-51. .. . . .. . . . . . . . . . . . ... . . . . . . REP_WORKFLOWS MX View .. . . . .. . . .. . . . . . . ... . .. . . . . . . .. . . . . REP_SESSION_INSTANCES MX View .. . . . . . . . . . . . .. . . .. . .. . . ... . .. .. . . . . .. . . . . 15-67. .. .. . Worklet. . . . . . . . . . . . . . . 15-71. . . .. . . . . . . . .. . . 15-54. .. REP_ALL_TRANSFORMS MX View . . .. . 15-56. . . . . . 15-57. 15-70. 15-60. . . . . . .. . . . .. ... . . . . 15-58. . . . . . . . . .. . . .. . 15-72... . . . . . . . .. . . . . .. . .. . . .. . . .. . ... . . . .. . .. . Workflow. . . . .. . .. . . . . .. . . . . . . . . .. . . . REP_LOAD_SESSIONS MX View . .. . . . . . . . . .. ... . . REP_SESS_PARTITION_DEF MX View . . . . ... ... .. . .. . . . . . . .. . Security Views . . . . . . . . . 15-50. . . . . .. . .. .. . . . . . ... . 15-40. 15-55. ... . . . . .. . 15-38. . . . REP_SESS_CONFIG_PARM MX View . . . . . .. 15-45. .. . . . . . . . . . . . . . . . . . .. . .. ... . .. . . REP_CM_LABEL_REF MX View .. . .. . . . . .. ... . . 15-44. . . . . . .. .. . . . . . .. . . . . . . ..... 15-73. ... .. . . . . ... . . . . .. 15-53. . . . . ... . . .. .. REP_DEPLOY_GROUP_DETAIL MX View . . . . . . . . . . 15-59. .. . ... . .. ... . . . . . . . . . REP_GROUPS MX View .. REP_COMPONENT MX View . .. . . . . REP_SERVER_INFO MX View . . . . . . . . .. REP_SESSION_INSTANCE_FILES MX View REP_SESS_WIDGET_CNXS MX View . . .. REP_SESS_LOG MX View . . .

. . .. . Native Connect String Syntax . . . . . . Addserver Options and Arguments (pmrep) . .436 . . .. .. . . . . . . .. . . . . . . . . .. . . . ... . . . Database Type Strings . . .. . .422 . . ..410 . . . . . . . . . . . . . . . . . . .448 . 16-6... . . 16-42.. . .. .. . .. ... . .. . . . .414 . . . . . . . . . . . .. . . 16-20. . . Backup Options and Arguments (pmrep) . . Truncatelog Options and Arguments (pmrep) . . .. ... . . . . . .415 . .. . 16-30.. . . . . . . . . . . .. . . . . . . . .. .443 . . . . .442 . . .. . .. . . .. .. . . . . .. . . . .. . 16-15. . . . .. Unregister Options and Arguments (pmrep) . .... . .447 . .. . . . . . . . . . 16-28... . . . . .438 .. .412 . . . . . . . . . . . . . . . . . . . . . . . . . . . .440 . . .. . 16-26... . 16-32. . . .. . .. . . . Updateemailaddr Options and Arguments (pmrep) . . . . ... . . . . . Run Options and Arguments (pmrep) . . . . .426 . . . . . . . . . .. Updatestatistics Options and Arguments (pmrep) .. . . .451 . . . . . . . . . . . . . . . CreateFolder Options and Arguments (pmrep) . . . . . 16-36. . . . . . . .. . ..439 . . Transformation and Task Types to Use with pmrep . . ... . 16-38. . . . . .. . Updatesrcprefix Options and Arguments (pmrep) . Updatetargprefix Options and Arguments (pmrep) . . . . 16-8. . .430 .. . . . . 16-19. . 16-41.. . . .. . . .410 .. . . . . . . Removerepository Options and Arguments (pmrep) . . .. . Enablerepository Options and Arguments (pmrep) . . . . Code Page ID by Name (pmrep) . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . .. .431 . . . . . .. . . . . Creategroup Options and Arguments (pmrep) . . 16-14. . .. . . . . pmrep System Commands . . . .. . . Disablerepository Options and Arguments (pmrep) . . .. . . .. . .. . 16-24.416 . . 16-13. . CreateConnection Options and Arguments (pmrep) . . . . . .. . . . . . . . . . . pmrep Security Commands . . .446 .421 .. UpdateConnection Options and Arguments (pmrep) . . . . .. . . . . . 16-33. .. . . . . . . . 16-39. . .. . . . . . . .. . . . . . . .. . . . . . . . . . . .. Updateserver Options and Arguments (pmrep) . . . . .. . . 16-25. 16-12. . . . . Addrepository Options and Arguments (pmrep) . . . . . . . .. . . . .433 . 16-34. .. . StopRepository Option and Argument (pmrep) . .443 . . . . . . .450 . Changepasswd Options and Arguments (pmrep) . . . . .. . . . . . . . . . .. .. . . . .418 . . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . 16-2. . .452 xx List of Tables . . . . .. .. . . . Addusertogroup Options and Arguments (pmrep) . . . .451 .. . . . . . . . . . . . .. . ObjectImport Options and Arguments (pmrep) . . . .. . . . . . . . . .422 . . . . . 16-4. 16-22. 16-40. . . .. . . . . 16-29.. .. . .. . . . . . . . . .. . . . . .. 16-10.. . .434 . . . . . . Updateseqgenvals Options and Arguments (pmrep) . .... . . . . . 16-23. . . .. . . . Notify Options and Arguments (pmrep) . . . . . .. . . . .449 . . . . . . . . . . . . . . . . . .. . . . . 16-16. . . .. . . . ... . . . . . pmrep Repository Commands . .. . . . . .. . . 16-37. . .. . . . . . .. . . Listtablesbysess Options and Arguments (pmrep) . 16-11. .. . . .421 . . .... . . 16-1. .. . . . . . . . . . . Connect Options and Arguments (pmrep) . . .. Addprivilege Options and Arguments (pmrep) . . . . . . . . . . . . .. . .. ... . . .. REP_SUBJECT MX View .. . . ..401 .. . . Updatesrvvar Options and Arguments (pmrep) .. .. . .. 16-35. . . . . . . 16-21. . . . . . 16-3. . 16-31. . . . . .. . . . Register Options and Arguments (pmrep) ..447 . .. . . ... . . 16-27. .444 . . . . . . . . . ListObjects Options and Arguments (pmrep) . 16-5. . . . . . .. .. . . .. .. . .. . . ... . . . . . . . . .. .. .. . . ... . . . . . . .. . . . 16-7. .417 . . . . . . . .. . . . . .. .. . . . . . . . . . . . . . . ObjectExport Options and Arguments (pmrep) . ListObjectDependencies Options and Arguments (pmrep) . .419 . . . . . ... ...405 . . . . .. . . . . . . . .. . . . . . . ... . . . . . . . . . .. 16-18. Deleteconnection Options and Arguments (pmrep) . . . . . . ..439 . SwitchConnection Options and Arguments (pmrep) . . . . . .450 . .Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 15-76. . .434 . . . . . .. . . . . .. . Deleteserver Options and Arguments (pmrep) . ..435 . . . . . . .. . . ... .. . . 16-9. . . ... . .. . .425 . . . . . . . . . . . . .428 . . ... . 16-17. . . . . . . . . . . .. . .. . . . . . . . .. . . .

. . .. . 16-61. . .. . . . Rmuserfromgroup Options and Arguments (pmrep) . . . Registeruser Option and Argument (pmrep) . .. . . . . ... . .. . . . Object Import Control File Elements and Attributes (pmrep) .. . . . . . . . . . . .. 16-51.. .. 16-49. . . .. Delete Options and Arguments (pmrepagent) . . . . .. . DeleteDeploymentGroup Options and Arguments (pmrep) .. .. . . .. .. . A-1. . Validate Options and Arguments (pmrep) . . . . . Rmprivilege Options and Arguments (pmrep) . . . . . . . . . . . . . .. . . . 16-74. Checkin Options and Arguments (pmrep) . ExecuteQuery Options and Arguments (pmrep) . . . . . Required Privileges and Permissions for Workflow Monitor Tasks . . . . . . . . . . . . B-1. .. . B-3. . . . . .. . . . . . . . . Registerplugin Options and Arguments (pmrepagent) . . . . . . . .. ... . . . . . . . . . A-2. . . . . . . . . . .. . . . . . . . .. . . . . . . ... . . . . . .. . . . . . . . .. .. . . .. . . . Required Permissions and Privileges for pmrep Tasks. . . . . . . . .. .. . . Rmgroup Option and Argument (pmrep). . . . . . . . . . . . . . . . Required Permissions and Privileges for Repository Manager Tasks B-6. . . . . 16-46. . . . . Required Privileges and Permissions for pmcmd Tasks . . . .. . . . . .. .. . .. . . . . DeployDeploymentGroup Options and Arguments (pmrep) .. . . . . . . . 16-66. .. 16-59.. .. . . .. . . . . . . . AddToDeploymentGroup Options and Arguments (pmrep) . . . . . .. . . Backup Options and Arguments (pmrepagent) . . .. . . . . . . . . . . . . .. .. . . . . ... . .. . . . . .. . . 16-71. . . .. . . . . . . . . . . . . . . UndoCheckout Options and Arguments (pmrep) .. . . . .. . . . . . . . . . . . . ... . 16-63.... 16-70. . DeleteFolder Options and Arguments (pmrep) . . .. . . . . . . . 16-44.. . . . . . . Edituser Options and Arguments (pmrep) . . . . . . . . . . . . . ApplyLabel Options and Arguments (pmrep) . . . .. . .. . . . . . . . . . . . DeployFolder Options and Arguments (pmrep) ... .. . .. . . Deployment Control File Elements and Attributes (pmrep) . . . . . .. . .. DeleteLabel Options and Arguments (pmrep) . 16-55. . . . . . . . . . . 16-58.. . . 16-75. . . . . Required Privileges and Permissions for Workflow Manager Tasks . . . . . . . . . .. . . . .. . . . ModifyFolder Option and Argument (pmrep) .. .. . . . . . . . . . . . . . . . 16-62. . . . . . . . .. . . . . . . .. .. .. . . . . . . . .. . . . . .. 16-56. . . . .. . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 16-47. . . . . . . . .. . 16-54.. . . . . . . . . . . .. . 16-57. . Upgrade Options and Arguments (pmrepagent) . . . . . . . 16-53. . . .. .. . . . .. .. pmrepagent Commands . . . . . . . . pmrep Change Management Commands . . Unregisterplugin Options and Arguments (pmrepagent) . . . . . . . . . . . 16-67. . . . . . . . . . ClearDeploymentGroup Options and Arguments (pmrep) . . . . . . . 16-48. . . . . CreateDeploymentGroup Options and Arguments (pmrep) . . . . .. B-4. . . . 16-68. . . . . . . . . .. . . B-2. . . . . . . Required Privileges and Permissions for Designer Tasks . . . . . . CreateLabel Options and Arguments (pmrep) . . . . .. . . . 16-50. . . Rmuser Option and Argument (pmrep) . . . . . . . . . . . .. . . ... . . ... . . . . . 16-65.. 16-45. .Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 16-43. . ... . . . . . . . . . . . 16-64... . 16-52. Restore Options and Arguments (pmrepagent) . .. . Create Options and Arguments (pmrepagent) . . . . . . . . . . . . . . . . . . . . . . . . . . 16-73. . 16-69. Bulkrestore Options and Arguments (pmrepagent) . .. . B-5. . . .. . ... . .. . . . . . . . . .. . . . . . 16-60.. . . . . . . . . . . . . 453 453 454 456 457 458 458 459 459 460 461 463 464 465 465 466 467 467 468 469 470 472 474 475 477 478 479 480 481 482 485 488 490 498 505 510 511 513 515 516 519 List of Tables xxi . .. . . . . . . . . . . . .. . . . . . .. .. ... . . . . . . . . . . 16-72. . Createuser Options and Arguments (pmrep) . . . .. .. . . . . . . . . . . . . . .. . . . .. . .. . . . .. . . . . . . FindCheckout Options and Arguments (pmrep) . . . . . . ... .

xxii List of Tables .

The PowerCenter metadata repository coordinates and drives a variety of core functions. scalable data integration solution addressing the complete life cycle for all data integration projects including data warehouses and data marts. and information hubs. The PowerCenter Server can extract large volumes of data from multiple platforms.Preface Welcome to PowerCenter. transforming. including extracting. data synchronization. handle complex transformations on the data. data migration. and managing data. xxiii . and efficient manner. and support high-speed loads. loading. Informatica’s software product that delivers an open. usable. PowerCenter combines the latest technology enhancements for reliably managing data repositories and delivering information resources in a timely. PowerCenter can simplify and accelerate the process of moving data warehouses from development to test to production.

xxiv Preface . Define mapping.0. the rows that meet the business rule. and workflow prefixes for the mappings. You can configure the Data Profiling Wizard to filter the Domain Inference function results. or the rows that do not meet the business rule. and workflows generated when you create a data profile. JEF-kana.1 This section describes new features and enhancements to PowerCenter 7.1.1. you can configure the session to create multiple threads to read the flat file source. You can determine unique rows for a source based on a selection of columns for the specified source. Session enhancement. Row Uniqueness function. The PowerCenter Server can write all rows. You can create a data profile for a sample of source data instead of the entire source. and 7. When you create multiple partitions for a flat file source session. Data Profiling ♦ Data sampling. You may want to narrow the scope of patterns returned to view only the primary domains.1. Verbose data enhancements. Flat file partitioning. pmcmd passes variables and values in the file to the PowerCenter Server.New Features and Enhancements This section describes new features and enhancements to PowerCenter 7. session. You can define default mapping. You can use parameter files that reside on a local machine with the Startworkflow command in the pmcmd program.1. a specified percentage of data. or for a specified number of rows starting with the first row. Profile mapping display in the Designer. such as JIPSEkana. pmcmd. You can view a profile from a random sample of data. ♦ ♦ ♦ ♦ ♦ ♦ PowerCenter Server ♦ ♦ ♦ Code page. You can save sessions that you create from the Profile Manager to the repository. Domain Inference function tuning. and MELCOM-kana. and workflow prefixes.1. You can specify the type of verbose data you want the PowerCenter Server to write to the Data Profiling warehouse.1. The Designer displays profile mappings under a profile mappings node in the Navigator. 7. or you may want to widen the scope of patterns returned to view exception data. sessions. session. When you use a local parameter file. You can configure a maximum number of patterns and a minimum pattern frequency. PowerCenter supports additional Japanese language code pages. PowerCenter 7.

You can export or import multiple objects at a time. and repositories using native drivers. Use ODBC drivers to access other sources and targets. If any source. Oracle. You can attach document types such as XML. targets. containing reserved words. You can exchange source and target metadata with other BI or data modeling tools.txt in the PowerCenter Server installation directory. Oracle. GIF. You can now use Oracle OS Authentication to authenticate database users. DB2. JPEG. When you import web service definitions with attachment groups. Preface xxv . PowerCenter uses Oracle OS Authentication when the user name for an Oracle connection is PmNullUser. The PowerCenter Server runs on SuSE Linux. Depending on the loader you use. and Sybase repositories. and Sybase sources. or PDF. On SuSE Linux. The document type you can attach is based on the mime content of the WSDL file. The Repository Server runs on SuSE Linux. ♦ ♦ Repository ♦ Exchange metadata with other tools. Repository Server ♦ pmrep. Update a connection attribute value when you update the connection.txt. If the file exists. Reserved word support. You do not need to know a database user name and password. or lookup table name or column name contains a database reserved word. you can create and maintain a file. and work table names by specifying different tables on the same or different Teradata database. When the PowerCenter Server initializes a session. reswords. You can use pmrep to perform the following functions: − − − Remove repositories from the Repository Server cache entry list. log. it searches for reswords. DB2. Security ♦ Oracle OS Authentication. When you export metadata. When you load to Teradata using an external loader. Oracle OS Authentication allows you to log on to an Oracle database if you have a logon to the operating system.♦ SuSE Linux support. you can now override the control file. ♦ SuSE Linux support. you can pass attachments through the requests or responses in a service session. you can connect to IBM. Teradata external loader. Enable enhanced security when you create a relational source or target connection in the repository. you can connect to IBM. On SuSE Linux. such as Business Objects Designer. you can also override the error. the PowerCenter Server places quotes around matching reserved words when it executes SQL against the database. Web Services Provider ♦ Attachment support. the PowerCenter Client creates a file format recognized by the target tool. target.

1. You store xxvi Preface . Informatica provides a set of prepackaged domains that you can include in a Domain Validation function in a data profile. You can now purge data from the Data Profiling warehouse. XML User Guide. Licensing Informatica provides licenses for each CPU and each repository rather than for each installation. and view verbose data for Distinct Value Count functions. connectivity. ♦ ♦ ♦ ♦ ♦ ♦ Documentation ♦ ♦ Web Services Provider Guide. The PowerCenter Server creates a connection to the Web Services Hub based on the number of sources.1 This section describes new features and enhancements to PowerCenter 7. Prepackaged domains. resize columns in a report. You can now pivot more than one multiple-occurring element in an XML view. Purging data from the Data Profiling warehouse. You can create multiple partitions in a session containing web service source and target definitions. PowerCenter 7. Auto profiles now include the Aggregator function. PowerCenter Data Profiling report enhancements. You can also pivot the view row. Support for verbose mode for source-level functions. and partitions in the session. You can now view data profiles by source definition in the Profile Manager. Informatica provides licenses for product. It also includes information from the version 7. You can now create data profiles with source-level functions and write data to the Data Profiling warehouse in verbose mode.♦ Pipeline partitioning. This book consolidates XML information previously documented in the Designer Guide. Aggregator function in auto profiles. You can now view PowerCenter Data Profiling reports in a separate browser window. and Transformation Guide. This is a new book that describes the functionality of Real-time Web Services. You can now select the columns or groups you want to include in an auto profile and enable verbose mode for the Distinct Value Count function. You can now create a data profile for VSAM sources. and options. XML ♦ Multi-level pivoting. Source View in the Profile Manager. Data Profiling ♦ ♦ Data Profiling for VSAM sources. Creating auto profile enhancements. Workflow Administration Guide.0 Web Services Hub Guide. targets.

You can export metadata to and import metadata from other business intelligence tools. the PowerCenter Server Setup. This improves performance when PowerCenter accesses the repository. You can now run 64-bit PowerCenter Servers on AIX and HP-UX (Itanium). REP_VERSION_PROPS allows you to see the version history of all objects in a PowerCenter repository. pmlic.the license keys in a license key file. delete repository details. You can increase repository performance by skipping information when you copy. modify. You can also use pmrep to create. You can now read and write CLOB/BLOB datatypes. Repository Server ♦ Updating repository statistics. You can compare objects in an XML file to objects in the target repository when you import objects. or enable a repository. truncate log files. workflow and session log history. MX views have been added to help you analyze metadata stored in the repository. such as Cognos Report Net and Business Objects. and restore repositories. You can choose to skip MX data. You can use pmrep to back up. PowerCenter Metadata Reporter PowerCenter Metadata Reporter modified some report names and uses the PowerCenter 7. If you have the Partitioning option. ♦ ♦ Preface xxvii . Increased repository performance. ♦ ♦ Repository ♦ Exchange metadata with business intelligence tools. upgrade. Object import and export enhancements. You can manage the license files using the Repository Server Administration Console. PowerCenter Server ♦ ♦ ♦ ♦ 64-bit support. and deploy group history. pmrep. you can define up to 64 partitions at any partition point in a pipeline that supports multiple partitions. PowerCenter now identifies and updates statistics for all repository tables and indexes when you copy. or restore a repository. PowerCenter Server processing enhancements. back up. and the command line program. disable. Partitioning enhancements. and run multiple pmrep commands sequentially. delete a relational connection from a repository. REP_SERVER_NET and REP_SERVER_NET_REF views allow you to see information about server grids. The PowerCenter Server now reads a block of rows at a time.1 MX views in its schema. MX views. CLOB/BLOB datatype support. and delete a folder. This improves processing performance for most sessions.

You can install the Web Services Hub on a JBoss application server. The Web Services Hub now hosts Real-time Web Services in addition to Metadata Web Services and Batch Web Services. You can now perform lookups on flat files. The Union transformation is similar to using the UNION ALL SQL statement to combine the results from two or more SQL statements. the PowerCenter Server can ignore some ports when it compares values in lookup and input ports before it updates a row in the cache. Use these functions to take advantage of the PowerCenter Server processing enhancements. the Designer invokes the Flat File Wizard.Transformations ♦ Flat file lookup. or a collection of all older versions of objects. The query can return local objects that are checked out. ♦ ♦ ♦ ♦ Usability ♦ ♦ Viewing active folders. The Designer and the Workflow Manager highlight the active folder in the Navigator. Also. The PowerCenter Server can perform parallel processing of both requestresponse and one-way services. the latest version of checked in objects. Custom transformation API enhancements. Midstream XML transformations. The Custom transformation API includes new array-based functions that allow you to create procedure code that receives and outputs a block of rows at a time. You can now create an XML Parser transformation or an XML Generator transformation to parse or generate XML inside a pipeline. Enhanced printing. such as TIBCO or IBM MQSeries. such as data stored in a CLOB column. ♦ xxviii Preface . Version Control You can run object queries that return shortcut objects. When you use a dynamic lookup cache. you can choose whether the PowerCenter Server outputs old or new values from the lookup/output ports when it updates a row. You can also run object queries based on the latest status of an object. Union transformation. Real-time Web Services allows you to create services using the Workflow Manager and make them available to web service clients through the Web Services Hub. Dynamic lookup cache enhancements. The XML transformations enable you to extract XML data stored in relational tables. When you create a Lookup transformation using a flat file as a lookup source. You can also use a lookup file parameter if you want to change the name or location of a lookup between session runs. Web Services Provider ♦ Real-time Web Services. The quality of printed workspace has improved. You might want to output old values from lookup/output ports when you use the Lookup transformation in a mapping that updates slowly changing dimension tables. Web Services Hub. You can use the Union transformation to merge multiple sources into a single pipeline. You can also extract data from messaging systems.

or schema files. You can create views. such as TIBCO or IBM MQSeries. the Designer creates separate entities for references and multiple-occurring elements. You can edit XML views and relationships between views in the workspace. You can use XML schemas that contain simple and complex datatypes. It displays folders alphabetically. For more informations. You can open multiple instances of the Workflow Monitor on one machine. You can remove the Navigator and Output window. In a view with hierarchy relationships. including relational sources or targets. You can synchronize one or more XML definition when the underlying schema changes. targets. You can choose to generate XML views using hierarchy or entity relationships. Midstream XML transformations. ♦ ♦ ♦ Preface xxix . and transformations to call web services hosted by other providers. XML workspace. The XML transformations enable you to extract XML data stored in relational tables.Note: PowerCenter Connect for Web Services allows you to create sources. You can simultaneously monitor multiple PowerCenter Servers registered to the same repository. You can synchronize an XML definition with any repository definition or file used to create the XML definition. and define relationships between views. You can also extract data from messaging systems. see PowerCenter Connect for Web Services User and Administrator Guide. the Designer expands each element and reference under its parent element. You can now create an XML Parser transformation or an XML Generator transformation to parse or generate XML inside a pipeline. XML files. DTD files. such as data stored in a CLOB column. Additional options for XML definitions. you no longer distinguish between online or offline mode. add or delete columns from views. The Workflow Monitor includes improved options for filtering tasks by start and end time. you can choose how you want the Designer to represent the metadata associated with the imported files. When you create views with entity relationships. The Workflow Monitor displays workflow runs in Task view chronologically with the most recent run at the top. Workflow Monitor The Workflow Monitor includes the following performance and usability enhancements: ♦ ♦ ♦ ♦ ♦ ♦ When you connect to the PowerCenter Server. When you import XML definitions. Synchronizing XML definitions. XML Support PowerCenter XML support now includes the following features: ♦ ♦ Enhanced datatype support.

and XML schemas that use circular definitions.0. and evaluate join criteria.0 This section describes new features and enhancements to PowerCenter 7. Documentation ♦ ♦ Glossary. Data Profiling If you have the Data Profiling option. You can create XML files of several gigabytes in a PowerCenter 7. The Installation and Configuration Guide now contains a chapter titled “Upgrading Repository Metadata. The connectivity information in the Installation and Configuration Guide is consolidated into two chapters. Increased performance for large XML targets. you can determine implicit data type. You can define commits to trigger flushes for XML target files. Data Integration Web Services is a web-enabled version of the PowerCenter Server functionality available through Load Manager and Metadata Exchange.1 XML session by using the following enhancements: − ♦ Spill to disk. For example.♦ Support for circular references. − − PowerCenter 7. It is comprised of two services for communication with the PowerCenter Server. The PowerCenter Client provides a Profile Manager and a Profile Wizard to complete these tasks. PowerCenter now supports XML files.” This chapter describes changes to repository ♦ xxx Preface . you can create profiling mappings and run sessions. User-defined commits. If the size of the tree exceeds the cache size.” Upgrading metadata. Installation and Configuration Guide. suggest candidate keys. You can also define the file names for XML output files in the mapping. Support for multiple XML output files. Data Integration Web Services You can use Data Integration Web Services to write applications to communicate with the PowerCenter Server. You can output XML data to multiple XML targets. The Installation and Configuration Guide contains a glossary of new PowerCenter terms. Load Manager and Metadata Exchange Web Services running on the Web Services Hub. Then you can view reports based on the profile data in the profiling warehouse. DTD files. you can profile source data to evaluate source data and detect patterns and exceptions. You can specify the size of the cache used to store the XML tree. This book now contains chapters titled “Connecting to Databases from Windows” and “Connecting to Databases from UNIX. detect data patterns. After you create a profiling warehouse. Circular references occur when an element is a direct or indirect child of itself. the XML data spills to disk in order to free up memory.

The change in functionality for existing objects depends on the version of the existing objects. source and target tables.0 metadata. including session load time. In a server grid. The Soundex function encodes a string value into a four-character string. Preface xxxi ♦ ♦ . It uses the first character of the input string as the first character in the return value and encodes the remaining three unique consonants as numbers. session errors. ♦ Installation ♦ Remote PowerCenter Client installation. Row error logging. PowerCenter Metadata Reporter includes the following features: ♦ Metadata browsing. you can group PowerCenter Servers registered to the same repository into a server grid. You can create a control file containing installation information. and distribute it to other users to install the PowerCenter Client. You can choose to log row errors in a central location to help understand the cause and source of errors. You can use PowerCenter Metadata Reporter to analyze operational metadata. METAPHONE encodes characters of the English language alphabet (A-Z). Distributed processing. mappings. Consult the upgrade information in this chapter for each upgraded object to determine whether the upgrade applies to your current version of PowerCenter.1. You access the Informatica installation CD from the command line to create the control file and install the product. External loading enhancements. and warehouse growth.objects impacted by the upgrade process. Metadata analysis. The Metaphone function encodes string values. ♦ PowerCenter Server ♦ ♦ DB2 bulk loading. PowerCenter Servers balance the workload among all the servers in the grid. It encodes both uppercase and lowercase letters in uppercase. such as workflows. you can now choose to load from staged files. If you purchase the Server Grid option. You can enable bulk loading when you load to IBM DB2 8. The session configuration object has new properties that allow you to define error logging. When using external loaders on UNIX. session completion status. PowerCenter Metadata Reporter PowerCenter Metadata Reporter replaces Runtime Metadata Reporter and Informatica Metadata Reporter. worklets. and transformations. You can specify the length of the string that you want to encode. You can use PowerCenter Metadata Reporter to browse PowerCenter 7. When using external loaders on Windows. Functions ♦ Soundex. server load. you can now choose to load from a named pipe. SOUNDEX works for characters in the English alphabet (A-Z). Metaphone.

When you select data driven loading. deploying. Additionally. The deployment and object import commands require you to use a control file to define options and resolve conflicts. or update. delete. You can now enable or disable users from accessing the repository by changing the status. You can export and import objects with or without their dependent objects. such as maintaining deployment groups and labels. You can now use real-time processing in sessions that also process active transformations. or delete data. groups. Trusted connections. and permissions through the Repository Server Administration Console. such as copy object. maintain labels. Mixed mode processing for Teradata external loaders. ♦ ♦ Security ♦ LDAP user authentication. such as the Aggregator transformation. You can now use default repository user authentication or Lightweight Directory Access Protocol (LDAP) to authenticate users. The control file uses these values to determine how to load data to the target. Teradata Warehouse Builder can simultaneously read from multiple sources and load data into one or more tables. You can track changes to repository users. The repository maintains a status for each user.♦ External loading using Teradata Warehouse Builder. importing. You can apply the transformation logic to rows defined by transaction boundaries. Real time processing enhancements. the PowerCenter Server flags rows for insert. ♦ ♦ ♦ Repository Server ♦ Object export and import enhancements. You can use Teradata Warehouse Builder to load to Teradata. Audit trail. The Use Repository Manager privilege allows you to perform tasks in the Repository Manager. You can now export and import objects using the Repository Manager and pmrep. You can now use data driven load mode with Teradata external loaders. the repository maintains an association between your repository user name and your external login name. You do not have to delete user names from the repository. pmrep commands. The PowerCenter Server now reads data concurrently from sources within a target load order group. Use Repository Manager privilege. privileges. You can use pmrep to perform change management tasks. You can also export objects from a query result or objects history. checking in. the security module passes your login name to the external directory for authentication. You can now use a Microsoft SQL Server trusted connection to connect to the repository. Concurrent processing. You can choose to insert. When you log in to the repository. upsert. You can also use pmrep to run queries. You can perform the same tasks in the Designer and Workflow Manager if you have the Use Designer and Use Workflow Manager privileges. It writes a column in the target file or named pipe to indicate the update strategy. You can export and import multiple objects and objects types. update. and change object status. The Repository Agent logs security changes to a log file stored in the Repository Server installation directory. This enables more efficient joins with minimal usage of memory and disk cache. exporting. and listing objects. The ♦ ♦ xxxii Preface . If you use LDAP.

This gives you greater control over the specific objects copied from one repository to another. the colors. Deployment. copying a deployment group allows you to copy a select number of objects from multiple folders in the source repository to multiple folders in the target repository. and check in the object when you are ready to create a new version of the object in the repository. The Repository Manager and Workflow Manager allow you to compare two repository objects of the same type to identify differences between them. and workflows in the Workflow Manager. Version Control The PowerCenter Client and repository introduce features that allow you to create and manage multiple versions of objects in the repository. distribute the template with the DLL or shared library you develop. ♦ ♦ ♦ ♦ Preface xxxiii . You can create Custom transformations with multiple input and output groups. If you want to permanently remove an object version. Version control allows you to maintain multiple versions of an object. Version control in PowerCenter includes the following features: ♦ Object versioning. The Custom transformation replaces the Advanced External Procedure transformation. Compare objects. track changes. The PowerCenter Client tools allow you to compare objects across open folders and repositories. sessions. and use deployment groups to copy specific groups of objects from one repository to another. Check out and check in versioned objects. Each version is a separate object with unique properties. You can compare Designer objects and Workflow Manager objects in the Repository Manager.audit trail log contains information. Custom transformations operate in conjunction with procedures you create outside of the Designer interface to extend PowerCenter functionality. ♦ Joiner transformation. You can specify the icons used for transformation. control development on the object. You can delete an object from view and continue to store it in the repository. You can recover or undelete deleted objects. you can purge it from the repository. You can use the Joiner transformation to join two data streams that originate from the same source. Unlike copying a folder. such as changes to folder properties. worklets. You can also compare different versions of the same object. Transformations ♦ Custom transformation. and adding or removing privileges. You can compare tasks. You can create templates that customize the appearance and available properties of a Custom transformation you develop. You can check out and reserve an object you want to edit. This allows you to store multiple copies of a given object during the development cycle. Delete or purge a version. and you can compile the procedure with any C compiler. Individual objects in the repository are now versioned. When you create a Custom transformation template. and the properties a mapping developer can modify. adding or removing a user or group.

Track changes to an object. You can compare workflows and tasks from the Workflow Manager. You can view a history that includes all versions of an object and compare any version of the object in the history to any other version. You can format the XML target file so that you can easily view the XML file in a text editor. and to different repositories. You can copy objects within folders. Within the Designer. use XPath to locate XML nodes. Comparing objects. XML schemas allow you to declare multiple namespaces so you can use prefixes for elements and attributes. Increased performance for large XML files. ♦ ♦ ♦ XML Support PowerCenter contains XML features that allow you to validate an XML file against an XML schema. This allows you to associate multiple objects in groups defined by the label. You can save queries for later use. you can set commits and periodically flush XML data to the target instead of writing all the output at the end of the session. You can create a deployment group that contains references to objects from multiple folders across the repository. XML target enhancements. You can use XPath to locate XML nodes. format your XML file output for increased readability. You can make a private query. XPath support. You can create a query that specifies conditions to search for objects in the repository. declare multiple namespaces. and parse or generate XML data from various sources. ♦ ♦ ♦ Usability ♦ Copying objects. to other folders. or create a dynamic deployment group that uses a query to populate the group. You can also compare all objects from within the Repository Manager. Queries. You can use an XML schema to validate an XML file and to generate source and target definitions. and organize groups of objects for deployment or export and import.♦ Deployment groups. You can use labels to track versioned objects during development. You can create a static deployment group that you manually add objects to. This allows you to see the changes made to an object over time. improve query results. The XML wizard allows you to view the structure of XML schema. When you process an XML file or stream. You can choose to append the data to the same target file or create a new target file after each flush. You can now copy objects from all the PowerCenter Client tools using the copy wizard to resolve conflicts. XML support in PowerCenter includes the following features: ♦ XML schema. ♦ xxxiv Preface . or you can share it with all users in the repository. You can also configure the PowerCenter Server to not output empty elements to the XML target. A label is an object that you can apply to versioned objects in the repository. increase performance for large XML files. you can also copy segments of mappings to a workspace in a new folder or repository. XML schemas also allow you to define some complex datatypes. Labels.

The PowerCenter Client writes messages in the Output window that describe why it invalidates a mapping or workflow when you modify a dependent object. the Workflow Manager accesses the repository to retrieve the last-saved version of the object. such as sources. you can refresh a session mapping. In the Workflow Manager. Enhanced validation messages. You can validate multiple objects in the repository without fetching them into the workspace. When you edit a port in a mapping. Refresh session mappings. Before you edit or delete versioned objects. The Session Wizard is enhanced to provide a graphical depiction of a mapping when you configure partitioning. mappings. you can choose to propagate changed attributes throughout the mapping. Revert to saved. ♦ ♦ ♦ ♦ ♦ ♦ Preface xxxv . Viewing dependencies help you modify objects and composite objects without breaking dependencies. When you do this. View dependencies. Enhanced partitioning interface. You can now revert to the last saved version of an object in the Workflow Manager. mapplets. The Designer propagates ports. and worklets. expressions. targets. and conditions based on the direction that you propagate and the attributes you choose to propagate. You can save and optionally check in objects that change from invalid to valid status as a result of the validation. You can validate sessions.♦ Change propagation. or workflows. You can view parent and child dependencies and global shortcuts across repositories. workflows. Validate multiple objects. you can view dependencies to see the impact on other objects. mappings.

Includes information on running sessions with XML data. Troubleshooting Guide. Provides information needed to use the Designer. such as creating and maintaining repositories. Also contains information on administering the PowerCenter Server and performance tuning. Repository Guide. Provides basic tutorials for getting started. Web Services Provider Guide. XML User Guide. and transformations. mapplets. Also includes details on using the midstream XML transformations to parse or generate XML data within a pipeline. Provides syntax descriptions and examples for each transformation function provided with PowerCenter. Getting Started. and Metadata Web Services. as well as monitor workflows in the Workflow Monitor. Provides information needed to administer the repository using the Repository Manager or the pmrep command line program. Workflow Administration Guide. Designer Guide. and load data into JMS messages. Provides information you need to install and configure the Web Services Hub. Provides information about how to profile PowerCenter sources to evaluate source data and detect patterns and exceptions. Provides information you need to create XML definitions from XML. and relational or other XML definitions. Each error message includes one or more possible causes and actions that you can take to correct the condition. Batch Web Services. Also includes a description of the transformation datatypes used to process and transform source data. Transformation Guide. including details on environment variables and database connections. groups. XSD. folders.About Informatica Documentation The complete set of documentation for PowerCenter includes the following books: ♦ ♦ Data Profiling Guide. Provides information to help you create and run workflows in the Workflow Manager. and permissions and privileges. Provides information on how to create and configure each type of transformation in the Designer. ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ xxxvi Preface . Includes information to help you create mappings. The Web Services Hub hosts Real-time Web Services. build mappings. users. Provides information needed to install and configure the PowerCenter tools. Provides information to install PowerCenter Connect for JMS. This guide also provides information about how to use the web services that the Web Services Hub hosts. PowerCenter Connect® for JMS® User and Administrator Guide. Lists error messages that you might encounter while using PowerCenter. Installation and Configuration Guide. or DTD files. Includes details on functionality available in the Repository Manager and Administration Console. extract data from JMS messages. Transformation Language Reference.

This is a code example. italicized text boldfaced text italicized monospaced text Note: Tip: Warning: monospaced text bold monospaced text Preface xxxvii . Document Conventions This guide uses the following formatting conventions: If you see… It means… The word or set of words are especially emphasized. The following paragraph notes situations where you can overwrite or corrupt data. This guide assumes you have knowledge of relational database concepts. unless you follow the specified procedure. This is an operating system command you enter from a prompt to run a task. or mainframe systems in your environment. and the database engines. For additional information on related database connectivity issues not covered by this guide. You should also be familiar with the interface requirements of your supporting applications. This is generic text that should be replaced with user-supplied values. The following paragraph provides suggested uses.About this Book The Repository Guide is written for the database administrator and developers who manage the repositories. The following paragraph provides additional facts. This is the variable name for a value you enter as part of an operating system command. flat files. refer to the documentation accompanying your database products. The material in this book is available for online use. Emphasized subjects.

detailed descriptions of specific features. the Informatica Knowledgebase. The Informatica Webzine is a password-protected site that you can access through the Customer Portal.informatica. Visiting the Informatica Web Site You can access Informatica’s corporate web site at http://www.com. as well as literature and partner information.informatica. upcoming events.com.informatica. go to http://my. You can access the Informatica Developer Network at the following URL: http://devnet.com xxxviii Preface . you can access the Informatica Customer Portal site at http:// my. If you have any questions. This journal provides solutions to common tasks.com. The Customer Portal has an online registration form for login accounts to its webzine and web support. and locating your closest sales office.com. access to the Informatica customer support case management system (ATLAS). and access to the Informatica user community. Visiting the Informatica Webzine The Informatica Documentation team delivers an online journal. The services area of the site includes important information on technical support. To register for an account.Other Informatica Resources In addition to the product manuals. the Informatica Webzine.informatica. please email webzine@informatica. user group information. You will also find product information. Informatica provides these other resources: ♦ ♦ ♦ ♦ ♦ Informatica Customer Portal Informatica Webzine Informatica web site Informatica Developer Network Informatica Technical Support Visiting Informatica Customer Portal As an Informatica customer. training and education. and tips and tricks to help you develop data warehouses. The site contains product information. Visiting the Informatica Developer Network The Informatica Developer Network is a web-based forum for third-party software developers. Informatica Webzine. newsletters. and implementation services. its background. The site contains information about Informatica.

CA 94063 Phone: 866. .m.m. You can call or email your nearest Technical Support Center listed below or you can use our WebSupport Service. Obtaining Technical Support There are many ways to access Informatica technical support. 6 Waltham Park Waltham Road.com.com Africa / Asia / Australia / Europe Informatica Software Ltd.m.563.5:30 p.5:30 p. .m.informatica. .m.m. (local time) Singapore Phone: +65 322 8589 Hours: 9 a.5 p. (GMT) email: support_eu@informatica. (local time) Germany Phone: +49 1805 702 702 Hours: 9 a. market. . . and support customer-oriented addon solutions based on Informatica’s interoperability interfaces.9489 Hours: 6 a.m.6332 or 650.5:30 p.5800 Fax: 650.5:30 p.m.5 p.6 p.m. (local time) Netherlands Phone: +31 306 082 089 Hours: 9 a.The site contains information on how to create.m.385.m. (local time) Switzerland Phone: +41 800 81 80 70 Hours: 8 a. .m. Redwood City. (local time) France Phone: +33 1 41 38 92 26 Hours: 9 a. .m.m. North America / South America Informatica Corporation 2100 Seaport Blvd.com Belgium Phone: +32 15 281 702 Hours: 9 a.m. Berkshire SL6 3TN Phone: 44 870 606 1525 Fax: +44 1628 511 411 Hours: 9 a.213.m. (PST/PDT) email: support@informatica. WebSupport requires a user name and password. You can request a user name and password at http://my. White Waltham Maidenhead. .5:30 p. (local time) Preface xxxix .

xl Preface .

Chapter 1 Understanding the Repository This chapter covers the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 9 Administering Repositories. 2 Repository Architecture. 3 Repository Connectivity. 6 Understanding Metadata. 13 Version Control. 4 Repository Server Notifications. 11 PowerCenter Domains. 16 1 .

that you can create or modify using the PowerCenter Client tools. You can connect multiple repositories in a domain. and load data. permissions. You can back up the repository to a binary file. The Repository Server uses native drivers to communicate with the repository database. Configure security. or metadata. labeling. Restore. Enabling version control also allows you to perform change management tasks such as version comparison. transform. You can delete all of the repository tables on the database. the Repository Server uses a process called the Repository Agent to access the database tables. The PowerCenter Server uses repository objects to extract. For each repository database it manages. change tracking. You can create user and group profiles and configure folder permissions. and deployment.Overview The PowerCenter repository is a relational database managed by the Repository Server that stores information. You can create folders in the repository to organize metadata. Sharing objects allows you to reuse metadata. passwords. Metadata describes different types of objects. 2 Chapter 1: Understanding the Repository . You can store multiple versions of objects in a versioned repository. Repository administration tasks include the following: ♦ ♦ ♦ ♦ ♦ ♦ Back up. The repository uses database tables to store metadata. the Repository Server connects the client application directly to the Repository Agent process. used by the PowerCenter Server and Client tools. You can restore the repository from a binary backup file. The Repository Server protects metadata in the repository by managing repository connections and using object locking to ensure object consistency. PowerCenter Client tools and the PowerCenter Server communicate with the Repository Server over TCP/IP. The Repository Server also notifies you when objects you are working with are modified or deleted by another user. Delete. The Repository Server uses multiple Repository Agent processes to manage multiple repositories on different machines on the network. If you purchase the Team-Based Development option with PowerCenter. When a client application connects to the repository. you can share the objects in the folder with other repositories in the domain. Create folders. All repository client applications access the repository database tables through the Repository Server. you can enable the repository for version control. Copy. and privileges. When you configure shared folders in a repository. You can copy the repository to another database. The repository also stores administrative information such as user names. such as mappings or transformations. querying. Administer the repository using the Repository Manager client tool or the pmrep and pmrepagent command line programs.

The Repository Server Administration Console allows you to manage the Repository Server and repositories. Repository client applications access the repository database tables through the Repository Server. it connects to the repository to schedule workflows. inserts. Use pmrepagent to perform repository functions such as restoring and deleting repositories. The repository database tables contain the instructions required to extract. and PowerCenter Server registration information in the repository. The Repository Server accepts client connections and requests from the following PowerCenter applications: ♦ The PowerCenter Client tools. the PowerCenter Server writes workflow status information to the repository. The Repository Agent uses object locking to ensure the consistency of metadata in the repository. When you run a workflow. and load data. ♦ ♦ ♦ Repository Architecture 3 . The PowerCenter Server. The Repository Server can manage multiple repositories on different machines on the network. and updates metadata in the repository database tables. Use the Repository Manager to organize and secure metadata by creating folders and creating users and groups. Use pmrep to perform repository administration tasks such as listing repository objects. You can use multiple Repository Servers to manage repositories in a domain. When you start the PowerCenter Server. Use the Workflow Manager to store workflow metadata. Use the Designer to create and store mapping metadata in the repository. connection object information. The Repository Server configures and manages a Repository Agent process for each registered repository database. The Repository Server manages repository connection requests from client applications. The Repository Agent is a multi-threaded process that fetches. the PowerCenter Server retrieves workflow task and mapping metadata from the repository. transform.Repository Architecture The PowerCenter repository resides on a relational database. Use the Workflow Monitor to retrieve workflow run status information and session logs written by the PowerCenter Server. and creating and editing users and groups. pmrep and pmrepagent. The Repository Server managing the local repository communicates as a client application with the Repository Server managing the global repository. Other Repository Servers. During the workflow run.

it requires only one connection. The Repository Server uses one Repository Agent process for each repository database. The Repository Agent creates new database connections only if all the current connections are in use. the Repository Agent opens ten connections. It reuses the same database connection for all the requests. PowerCenter Repository Connectivity 4 Chapter 1: Understanding the Repository . Figure 1-1 illustrates the connectivity between the Repository Server. If the ten clients send requests simultaneously. if ten clients send requests to the Repository Agent one at a time. repository database. For example. Configure the Repository Server TCP/IP port number when you install the Repository Server. and pmrepagent connect to the repository through the Repository Server. pmrep. These connections remain open. PowerCenter Server. PowerCenter applications communicate with the Repository Server through a specified port over a TCP/IP connection. The Repository Server stores the connectivity information required for the Repository Agent process to connect to the repository database. The Repository Agent process uses native drivers to communicate directly with the repository database. and repository client applications: Figure 1-1. The PowerCenter Server opens additional connections to the Repository Agent process for each Load Manager and DTM process. The Repository Agent process supports multiple connections from each client. The Repository Agent maintains a pool of database connections for client applications. and the Repository Agent re-uses them to service requests from client tools or the server.Repository Connectivity PowerCenter applications such as the PowerCenter Client. Each client tool opens a separate connection to the Repository Agent process. You can set the maximum number of open connections for a repository by setting the Database Pool Size parameter in the repository configuration file.

Slow disk access on the repository database can slow metadata transactions and repository performance. Have the system administrator evaluate the hard disk on the repository database machine. Decrease the number of network hops between the repository client application. or deleted. The Repository Server starts the Repository Agent process for the repository database. 4. Check the hard disk on the repository database machine. and notifies the client application when objects in the repository are created. The Repository Server monitors the repository. Have your system administrator determine if your network runs at an optimal speed. ♦ Repository Connectivity 5 . and the repository database. modified. 5. The Repository Server uses the Repository Agent process to communicate with the repository database server and perform repository metadata transactions for the client application. The Repository Server verifies connectivity information for the target repository.The following process describes how the Repository Server connects a repository client application to the repository: 1. The client application sends a repository connection request to the Repository Server. Slow network connections can increase transaction times for metadata and slow repository performance. 3. The Repository Server can manage a repository residing on a database on a different machine on the network. the Repository Server. Use the following guidelines when you configure your repository environment: ♦ Improve network speed. 2.

you can update the mapping with the version of the source definition saved in the repository. Another user opens and edits the properties of a source definition used in the mapping and save the changes to the repository. For details on configuring the Designer to receive Repository Server notifications. modified. you must configure the Designer to receive Repository Server notifications. To receive a modification or deletion notification. see “Using the Designer” in the Designer Guide. suppose you are working with a mapping in the Designer. The Repository Server notifies you of the change so that you know the source in your mapping is out of date. see “Mappings” in the Designer Guide. modified. or deleted: ♦ ♦ ♦ Folders Users Groups You must be connected to the repository to receive notifications about folders. In this case. and the folder containing the object must be open in the Navigator. 6 Chapter 1: Understanding the Repository . see “Repository Manager Tasks” on page 516. the object must be open in the workspace. or deleted: ♦ ♦ ♦ ♦ ♦ ♦ Mappings Mapplets Shortcuts Source definitions Target definitions Transformations To receive any type of notification message about an object. Receiving Notifications in the Repository Manager The Repository Manager receives notification messages from the Repository Server when the following objects are created. or delete repository objects. Receiving Notifications in the Designer The Designer receives notification messages from the Repository Server when the following objects are created. Repository Server notification messages keep you informed of ongoing changes to metadata you are working with. Each PowerCenter Client tool and the PowerCenter Server receive notification messages for different types of objects. For information on the privileges and permissions to receive user and group notifications. For more information. For example.Repository Server Notifications The Repository Server sends notification messages when users create. modify.

and you must be connected to the repository. Repository Server Notifications 7 . For details on configuring the Workflow Monitor to receive Repository Server notifications. you must open the object in the workspace. modified. and the folder containing the object must be open in the Navigator. To receive a modification or deletion notification. or deleted: ♦ ♦ ♦ ♦ Sessions Tasks Workflows Worklets To receive any type of notification message about an object. For details on configuring the Workflow Manager to receive Repository Server notifications. PowerCenter Server Notifications The PowerCenter Server receives notification messages from the Repository Server when the following objects are created. you must configure the Workflow Monitor to receive Repository Server notifications. see “Monitoring Workflows” in the Workflow Administration Guide. the PowerCenter Server removes workflows from the schedule when it receives the notification. Receiving Notifications in the Workflow Monitor The Workflow Monitor receives notification messages from the Repository Server when the following objects are created.Receiving Notifications in the Workflow Manager The Workflow Manager receives notification messages from the Repository Server when the following objects are created. or deleted: ♦ ♦ ♦ Workflows Schedulers Folders If you delete a folder. see “Configuring the Workflow Manager” in the Workflow Administration Guide. or deleted: ♦ ♦ Folders PowerCenter Servers To receive any type of notification message about an object. you must configure the Workflow Manager to receive Repository Server notifications. The PowerCenter Server reschedules all workflows in the folder when it receives the notification. modified. The Repository Server also sends the PowerCenter Server a notification message when it copies a folder into the repository. modified.

Use notification messages tell users to disconnect if you want to shut down the repository. For more information on creating and sending notification messages. or to users connected to all of the repositories managed by a Repository Server.User-Created Notifications You can create and send notification messages to all users connected to a single repository. 8 Chapter 1: Understanding the Repository . see “Sending Repository Notifications” on page 74.

Multi-dimensional metadata refers to the logical organization of data used for analysis in OLAP applications. or passes data through ports that you connect in a mapping or mapplet. or COBOL files that provide source data. Mapplets. you can make the transformation reusable. You can use shortcuts to repository objects in shared folders. Detailed descriptions of database objects (tables. you can create a mapplet containing the transformations. Mappings. or XML files to receive transformed data. and mapplets. or a domain. Detailed descriptions for database objects. You use different PowerCenter Client tools to develop each kind of object. and any constraints applied to these columns. For example. Use the Designer to create and edit the following repository objects: ♦ Source definitions. you add transformations and configure them to handle data according to your business purpose. and synonyms). Shortcuts to metadata in shared folders. Transformations describe how the PowerCenter Server transforms data. reusable transformations. Use the Designer to create shortcuts. Rather than recreate the same set of transformations each time. or a domain. Use the Mapplet Designer tool in the Designer to create mapplets. views. Use the Warehouse Designer tool to create dimensions and cubes. then add instances of the mapplet to individual mappings. modifies. Shortcuts. Multi-dimensional metadata. A mapping specifies how to move and transform data from sources to targets. Use the Transformation Developer tool in the Designer to create reusable transformations. Use the Warehouse Designer tool in the Designer to import or create target definitions. You can create local shortcuts to shared folders within the same repository and global shortcuts to shared folders in the global repository of the domain. flat files. and add instances of the transformation to individual mappings or mapplets. Use the Mapping Designer tool in the Designer to create mappings. A transformation generates. XML files. ♦ ♦ ♦ ♦ ♦ ♦ ♦ Understanding Metadata 9 . a repository.Understanding Metadata The repository stores metadata that describes how to extract. Mappings can also include shortcuts. Target definitions. When you build a mapping or mapplet. PowerCenter metadata describes several different kinds of repository objects. Rather than recreate the same transformation each time. You can design a mapplet to contain sets of transformation logic to be reused in multiple mappings within a folder. and load source and target data. a source definition might be the complete structure of the EMPLOYEES table. column names and datatypes. During a session. transform. the PowerCenter Server writes the transformed data to targets. Reusable transformations. Use the Source Analyzer tool in the Designer to import and create source definitions. Mappings include source and target definitions and transformations. a repository. including the table name. such as NOT NULL or PRIMARY KEY. Transformations. Dimensions and cubes are most often used by end users of OLAP applications. flat files. You can design a transformation that you can reuse in multiple mappings or mapplets within a folder.

User groups organize individual repository users. To run the session. you may wish to store the name of that person with the source definition. For details on using metadata extensions. Workflow tasks include commands.For details on using the Designer to work with repository objects. transform. Connection objects. and email notification. Repository users have a user name and password that allow access to the repository. You can also configure a repository user with privileges that allow the user to perform specific tasks in the repository. For details on version control and change management. Use the Workflow Designer in the Workflow Manager to create sessions. divided into tasks. when someone in your company creates a source definition. ♦ ♦ If you enable version control. timers. For example. 10 Chapter 1: Understanding the Repository . and nest worklets in other worklets. see “Metadata Extensions” on page 325. You can control access to a folder by configuring the folder permissions. PowerCenter allows you to store multiple versions of metadata objects in the repository. ♦ ♦ ♦ For details on working with repository objects using the Workflow Manager. You can run worklets in workflows. PowerCenter also allows you to extend the metadata stored in the repository by associating information with repository objects. You associate information with repository metadata using metadata extensions. Worklets. Each repository user belongs to at least one user group. You create connection objects in the repository when you define database. see “Version Control” on page 16. A workflow is a set of instructions. FTP. Individual users inherit all privileges assigned to the user group. Worklets are objects that represent a set of workflow tasks that allow you to reuse a set of workflow logic in several workflows. Folders organize and store metadata in the repository. You can also configure a folder to share stored metadata with other repository users. and load data. The PowerCenter Client and Server use database connections to connect to the source and target databases. decisions. the PowerCenter Server uses to extract. Workflows. transforming. and external loader connections in the Workflow Manager. see the Workflow Administration Guide. Sessions. Workflow tasks are instructions the PowerCenter Server executes when running a workflow. and loading data. Use the Workflow Manager to create and edit the following repository objects: ♦ ♦ ♦ Database connections. User groups. Users. You create a session for each mapping you want to run. You can assign privileges to a user group. Workflow tasks. Sessions are workflow tasks that contain information about how the PowerCenter Server moves data through mappings. Use the Repository Manager to create and edit the following repository objects: ♦ Folders. Workflow tasks perform functions supplementary to extracting. place it in a workflow. see the Designer Guide and the Transformation Guide.

Although you can view the repository tables. You can make shortcuts to the table in other folders in the same repository. Creating the Repository The Repository Manager connects to the repository database through the Repository Server. you designate a user as the owner of the folder. You can restore the entire repository from a binary file. set up users and user groups and determine the repository privileges you want them to have. and restore repositories. The Repository Server uses the Repository Agent process to create and update the repository tables. Informatica is not responsible for corrupted data that is caused by customer alteration of the repository tables or data within those tables. user groups. For details on working with repositories. When you create a folder. so its contents are available to all other folders in the same repository. you might put it in the shared folder. and object locking. back up.Administering Repositories You use the Repository Manager to create. If you are working in a domain. Repository administration tasks include repository creation. Folders let you organize repository objects. After you create a repository. Administering Repositories 11 . If you plan to use the same object in several projects. providing a way to separate different types of metadata or different projects into easily identifiable areas. see “Managing the Repository” on page 49 and “Configuring the Repository” on page 103. These tables store metadata in a specific format the PowerCenter Server and the PowerCenter Client tools use. folder permissions. you can also make shortcuts to the table in folders in local repositories registered to the repository. and maintain the repository. Security To secure data in your repository. the user’s group. You can configure a folder to be shared. the repository provides a system of users. Creating Folders After you create the repository. and then assign different folder permissions to that user. you should never manually edit them through other utilities. organize. For example. and others accessing the repository. You use the Repository Server Administration Console to copy. You can also copy all the repository tables to another database. and configuring permissions and privileges for users and groups. For details on working with folders. You can back up the repository to a binary file. Warning: The Informatica repository tables have an open architecture. repository privileges. see “Working with Folders” on page 165. folder creation and organization. you can put a definition of the CUSTOMERS table that provides data for a variety of purposes in a shared folder. you can add folders to it.

12 Chapter 1: Understanding the Repository . or backing up the repository. Permissions permit or restrict access to folders and objects in the repository. see “Repository Security” on page 125. running sessions. For details on configuring repository security.Privileges permit or restrict the ability for users to perform tasks such as creating mappings.

serves several purposes: ♦ Opening connections between repositories. you need to have all of the following: ♦ ♦ ♦ A licensed copy of PowerCenter. If you are connected to a local repository. A licensed copy of PowerCenter for each local repository you want to create. the global repository. ♦ PowerCenter allows you to share data and metadata between global and local repositories by copying individual repository objects and entire folders within and between repositories. You can also copy objects in shared folders. Local repositories can then use shortcuts to objects in the global repository shared folders. The hub of this system. If you are connected to a global repository. The Repository Server accesses the repository faster if it is installed on the machine on which the repository resides. Building the Domain Before building your domain. and manage the process of developing and maintaining multiple data warehouses. or create copies of objects in non-shared folders. You can also use the Designer to create shortcuts to reference objects in other repositories.PowerCenter Domains The domain allows you to organize. ♦ ♦ ♦ A database created and configured for each repository. A domain consists of a single global repository and any number of local repositories. the code page of the global repository must be a subset of each local repository code page in the domain. PowerCenter Domains 13 . simplify. You can use one Repository Server to manage all of the repositories in the domain. Network connections between the Repository Servers and PowerCenter Servers. You can save any metadata that you plan to share across repositories in the global repository. you can navigate to the global repository without connecting to it separately. To preserve system security and to simplify the task of connecting from one repository to another. the code pages of the local and global repository must be compatible. Compatible repository code pages. You can connect repositories together within the domain. Storing and reusing shared metadata. you can navigate to any local repository in the domain. To register a local repository. To copy objects from the local repository to the global repository. You can also use multiple Repository Servers to manage the repositories in the domain. A Repository Server installed and configured to manage the repositories. required to create the global repository. the global repository stores information needed to connect to each repository.

For details on creating and configure a repository. Create user profiles for users performing cross-repository work. see “Repository Security” on page 125. 2. building a sales strategy. Although the user name and password must remain the same. see “Registering a PowerCenter Repository” on page 75. Once the local repository is registered. see “Creating or Promoting a Repository” on page 116. The profitability calculation might appear in several mappings in the sales division repository. or making other decisions. Since profitability is important information when investing in product development. A user who needs to connect to multiple repositories must have an identical repository user name and password in each repository. For details on creating user profiles and configuring repository security. and accounting divisions also need to use the same calculation in many mappings in their repositories. The R&D. You create a global repository by promoting an existing local repository. Once you make a repository a global repository. you need everyone in all parts of the organization to use the same calculation.Connecting separate repositories into a domain is a three-step process: 1. the user can be a member of different user groups and can have a completely different set of privileges in each repository. For details on registering repositories. 14 Chapter 1: Understanding the Repository . you can be sure that everyone looks at the value of each product to the company in the same way. It also helps enforce standards for the design of transformations at the enterprise level. Register other repositories with the global repository. PowerCenter provides a mechanism for sharing metadata among multiple repositories. even in other repositories. you might want to reuse it in other mappings. Reusing Metadata In a domain you frequently need to share metadata across repositories. based on variables such as production costs and marketing expenses. you can connect to the global repository from the local repository. When you develop the component of a mapping that performs this calculation. If you can share the profitability calculation. This calculation is likely to be complex. For example. Sharing metadata can help you save time and reduce work by reusing metadata. and to the local repository from the global. you cannot demote it to a local repository. a sales division develops a standard calculation for the profitability of each product. Create a repository and configure it as a global repository. marketing. 3.

Shared Folders You can configure folders in global and local repositories to be shared. you can create shortcuts to objects in that folder. For example. each folder within a repository might represent a different development project. A central data store improves throughput at the level of the entire enterprise. Reusing Data The need to share data is just as pressing as the need to share metadata. A more efficient approach would be to read. For example. If each department reads. you can use shortcuts to that folder in any repository in the domain. you can filter employee data that should remain confidential. rather than reading all the product data each time you update the central data store. you can improve performance by capturing only the inserts. For example. PowerCenter Domains 15 . see “Working with Folders” on page 165. you cannot create shortcuts to objects in the folder. For example. deletes. each department may need to read the same product data from operational sources. Or you can display date and time values in a standard format. and updates that have occurred in the PRODUCTS table since the last time you updated the central data store. You can use shortcuts in any other folder in the repository. transform. However. transforms. you might want to capture incremental changes to sources. so you might put the source definition for the BUG_REPORTS table in a shared folder. To improve performance further. However. You can perform these and other data cleansing tasks when you move data into the central data store instead of performing them repeatedly. several departments in the same organization need the same information. If the shared folder is in a global repository. the throughput for the entire organization is lower than it could be. For details on folders. Once you designate a folder as shared. and write the data to one central data store shared by all users. perform the same profitability calculations. you can still create copies of objects in non-shared folders. If a folder is not shared. and format this information to make it easy to review. Shared folders are useful when you want to use the same repository objects in several projects within the same repository. and writes this product data separately. The central data store also allows you to format data in a standard fashion. every project in the repository needs to store bug reports in a consistent format. Often.

or undelete. This allows you to see the changes made to an object over time. During development. A versioned repository can store multiple copies. You can make a private query. You can check out and reserve an object you want to edit. Queries. Workflow Manager. Compare objects. You can also compare different versions of the same object. You can create a query that specifies conditions to search for objects in the repository. see “Grouping Versioned Objects” on page 217. You can also roll back a deployment operation. You can view an object history that includes all versions of the object. You can create a deployment group that contains references to objects from multiple folders across the repository. This allows you to associate multiple objects in groups defined by the label. Track changes to an object. You can create a static deployment group that you manually add objects to. Deployment groups. test. You can copy objects in a deployment group from one repository to another. ♦ ♦ ♦ For more information on working with versioned objects. The Repository Manager. copying a deployment group allows you to copy one or more objects from multiple folders in the source repository to multiple folders in the target repository. provided that the object is present in the target 16 Chapter 1: Understanding the Repository . Delete or purge a version. You can recover. You can save queries for later use. of an object. You can use the following features to group versioned objects: ♦ Labels. deleted objects. You can delete an object from view and continue to store it in the repository. Each version is a separate object with unique properties. ♦ ♦ For more information on grouping versioned objects. and check in the object when you are ready to create a new version of the object in the repository. or you can share it with all users in the repository. You can also compare any version of the object in the history to any other version. improve query results. If you want to permanently remove an object version. see “Working with Versioned Objects” on page 199. You can also choose to copy part of a composite object. A label is an object that you can apply to versioned objects in the repository. You can use labels to track versioned objects during development. and deploy metadata into production. or versions. The PowerCenter Client tools allow you to compare objects across open folders and repositories. and organize groups of objects for deployment or import and export. you can enable version control for the repository. Unlike copying a folder. mark development milestones. PowerCenter version control features allow you to efficiently develop. you can purge it from the repository. you can use the following change management features to create and manage multiple versions of objects in the repository: ♦ Check out and check in versioned objects.Version Control If you have the Team-Based Development option. or create a dynamic deployment group that uses a query to populate the group. and Designer allow you to compare two repository objects of the same type to identify differences between them.

This gives you greater control over the specific objects copied from one repository to another and allows you to update only those objects that were modified. you can automate the process for copying deployment groups.repository. You can also use pmrep to perform change management tasks. For more information on using pmrep for change management. For more information on copying objects in a deployment group. Version Control 17 . see “Using pmrep and pmrepagent” on page 403. For example. This allows you to use pmrep scripts and files to automate change management tasks. see “Copying Folders and Deployment Groups” on page 241.

18 Chapter 1: Understanding the Repository .

48 19 . 30 Searching for Repository Objects. 34 Viewing Object Dependencies.Chapter 2 Using the Repository Manager This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 42 Comparing Repository Objects. 20 Repository Manager Windows. 37 Validating Multiple Objects. 29 Working with Repository Connections. 45 Truncating Workflow and Session Log Entries. 22 Adding and Removing a Repository.

mappings. restoring. targets. Dependency. you can use a keyword to search for a target definition. When you configure the Repository Manager to display object dependencies. see “Working with Repository Connections” on page 30. and shortcuts. such as deleting a folder or unlocking an object. Search for repository objects or keywords. For more information. You can add or remove multiple repositories to the Navigator window and client registry. The Navigator window allows you to connect to a repository. and the Output window. navigate through the folders. For more information. and browse repository objects. the Dependency window displays the dependency details when you select an object in the Navigator window. see “Adding and Removing a Repository” on page 29. If you add keywords to target definitions. For more information. ♦ ♦ ♦ 20 Chapter 2: Using the Repository Manager . Work with repository connections. see “Viewing Object Dependencies” on page 37.Overview The Repository Manager allows you to navigate through multiple folders and repositories and perform basic repository tasks. Note: Since the status of the repository changes as users access it. View object dependencies. You can export repository connection information from the client registry to a file. You can search for repository objects containing specified text. the Main window. You can dock and undock the Navigator. Before you remove or change an object. and Output windows. When you select an object in a node. such as copying. You can connect to one repository or multiple repositories. refresh your view of the repository before performing tasks. You can view dependency information for sources. For more information. The Output window displays detailed information for complex repository operations. You can import the file on a different machine and add the repository connection information to the client registry. Dependency. and Output windows. The Navigator window organizes the repository objects of the same type in each folder in groups called nodes. you can view details for the object in the Main window. Repository Manager Windows The Repository Manager can display four main windows: the Navigator window. Repository Manager Tasks You can use the Repository Manager to perform the following tasks: ♦ Add or remove a repository. see “Searching for Repository Objects” on page 34. the Dependency window. or upgrading a repository. You can also hide and display the Navigator. you can view dependencies to see the impact on other objects. The Output window also displays Repository Server notification messages.

You can use the Repository Manager to release residual locks left by residual connections. see “Exchanging Metadata” on page 313. see “Releasing Locks” on page 158. Terminate user connections. Release locks. Truncate session and workflow log entries. You can use the Repository Manager to view and terminate residual user connections. Releasing a valid lock can result in repository inconsistencies. so only release a lock when you know that the locked object is not in use. You can truncate all logs. For details. The Repository Manager allows you to compare two repository objects of the same type to identify differences between the objects. ♦ ♦ ♦ ♦ Overview 21 .♦ Compare repository objects. For details. For more information. such as Cognos ReportNet Framework Manager. see “Managing User Connections” on page 151. For more information. Exchange metadata with other business intelligence tools. You can truncate the list of session and workflow logs that the PowerCenter Server writes to the repository. see “Comparing Repository Objects” on page 45. see “Truncating Workflow and Session Log Entries” on page 48. or truncate all logs older than a specified date. You can export metadata to and import metadata from other business intelligence tools. For more information.

Repository Manager Components Navigator Window Dependency Window Output Window Status Bar Main Window When the Repository Manager accesses the repository. The Repository Manager can display the following windows: ♦ ♦ ♦ ♦ Navigator Main Dependency Output Figure 2-1 shows the Repository Manager components: Figure 2-1.Repository Manager Windows The Repository Manager has a main window and a status bar for information on the operation you are performing. the Status Bar reflects the connection in progress with a progress indicator. Progress Indicator 22 Chapter 2: Using the Repository Manager .

and session logs. tasks. drag the title bar toward or away from the Main window. Folders can be shared or not shared. choose View. Nodes can include sessions. Then select the window you want to open. When you launch the Repository Manager. To display a window: 1. Nodes. targets. The Dependency window appears when you want to view dependencies. Double-click the title bar. depending on the task you perform. From the menu. sessions. Deployment groups. the Navigator and the Main windows appear. Deployment groups contain collections of objects for deployment to another repository in the domain. mappings. targets. To close a window: ♦ Click the small x in the upper right corner of the window. PowerCenter repositories can be standalone. mapplets. Repository objects displayed in the Navigator can include sources. transformations. tasks. mapplets. sources. Navigator Window Use the Navigator window to connect to a repository and navigate through the folders and objects in the repository. you can also configure the Repository Manager to hide or display any window. Folders. 2. The Navigator window displays the following objects when they exist in the repository: ♦ ♦ ♦ ♦ ♦ Repositories. Repository objects. The Repository Manager displays windows as necessary. or global. worklets. Or. and mappings. local. transformations. and the Output window appears when the Repository Manager displays status messages.Displaying Windows The Repository Manager allows you to dock and undock the following windows: ♦ ♦ ♦ Navigator Dependency Output To dock or undock a window: ♦ Double-click the title bar. worklets. Repository Manager Windows 23 . workflows. workflow logs. workflows. However.

Figure 2-2 shows the Navigator components: Figure 2-2. You can also right-click the object in the Navigator and select Properties from the shortcut menu. and then clicking the View Properties button in the toolbar. Note: If you enable versioning when you create the repository. Repository Manager Navigator Repositories Deployment Groups Shared Folder Mappings Nodes Workflows Viewing Properties You can view the properties of the objects in the Navigator by selecting the object. 24 Chapter 2: Using the Repository Manager . you can view all tabs on the Properties dialog box. For more information about object properties. see “Viewing Version Properties” on page 203.

Source Definition Object Properties Main Window The Main window of the Repository Manager displays details about the object selected in the Navigator. The Repository Manager displays the columns in the new order until you change the display. to view detailed information about a particular repository object. if you select a repository in the Navigator. such as whether the folder is shared or in use. to sort mappings by validity. drill down on a node and select the object. select a node in the Navigator. To do this. For example. You can also change the order in which the columns appear. Note: You can double-click an object in the Main window to view its properties. select the mappings node. Sorting and Organizing You can sort items in the Main window by each of the columns. on the left side of the Main window. the Main window displays all the folders in the repository along with additional folder information.Figure 2-3 shows the object properties for a source definition: Figure 2-3. Viewing Object Details To view information about repository objects. Repository Manager Windows 25 . Click the heading again to reverse the order in which the mappings are sorted. For example. drag the Valid column heading to the desired location. you might want the Valid column to appear first. then click the Valid column heading. Or. For example.

and transformation nodes that contain the sources. Displays the properties for each source within the selected node. targets. Tasks Node Sessions Node Worklets Node Workflows Node Workflow Logs Node Session Logs Node Source Connections Node Source File Connections Node Target Connections Node 26 Chapter 2: Using the Repository Manager . and other objects associated with the worklet. Displays the properties for each mapping in the node. Select a mapplet to view the Transformations node containing the mapplet. tasks. and transformations used in the mapping. Select a static deployment group to view details for deployment group objects. Select a mapping to view sources. Displays properties for each task in the selected node. Displays connection properties for each target connection associated with the session. The Source Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. Select a target definition to view details for each target definition port. Object Details Displayed in Repository Main Window Node Repository Node Deployment Groups Node Sources Node Targets Node Transformations Node Mapplets Node Mappings Node Information Displayed Displays properties for each folder in the selected repository. Displays the properties for each reusable transformation in the selected node. targets. Displays the properties for each target with the selected node.and post-session email and commands. The Sessions Logs node displays under each session in the Sessions node. Select a worklet to view the nodes for sessions. Displays properties for each deployment group in the selected repository. Select a task to view the task details. Displays properties for each source file associated with the session. Displays connection properties for each source connection associated with the session. Displays properties for each worklet in the folder. Select a source definition to view details for each port in the selected source definition. Displays session log information for the selected session. Select a target in a mapping to view details for each port in the selected target definition. The Main window also displays information about pre. The Target Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. Select a session to view session logs. Displays workflow log information for the selected workflow.Table 2-1 shows the object details displayed in the Repository Manager Main window: Table 2-1. source connections and target connections nodes for the selected session. Displays properties for each session in the folder. The Source File Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. Select a transformation to view details for the specified transformation ports. The Workflow Logs node displays under each workflow in the Workflows node. Displays the properties for each mapplet in the selected node. Select a workflow to view information for tasks and objects associated with the selected workflow. Displays properties for each workflow in the folder.

see “Viewing Object Dependencies” on page 37. the Dependency window lists all sources or targets related to the selected object. Dependency Window The Dependency window appears when you configure the Repository Manager to display dependencies. Mapping dependencies. When you view mapping dependencies. along with details about each source.Table 2-1. For example. Dependency Window Selected Object Dependencies The Dependency window can display the following types of dependencies: ♦ Source-target dependencies. and the dependency information appears in the right pane of the window. the Dependency window lists all shortcuts to the selected object and relevant details. Displays log details for each transformation in the session when you select the Transformation Logs node. For information on using the Dependency dialog box. such as the repository and ♦ ♦ Repository Manager Windows 27 . You can also view dependencies using the Dependency dialog box. you view all sources that provide data for that target. the left pane of the Dependency window lists the object for which you want dependency information. The Target File Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. as well as relevant information about those mappings. You can view dependencies by using the menu items or the dependency buttons on the toolbar. Object Details Displayed in Repository Main Window Node Target File Connections Node Transformation Logs Node Information Displayed Displays properties for each target file associated with the session. Shortcut dependencies. if you select a reusable transformation. the Dependency window lists all mappings containing the selected object. When viewing dependencies. When you view source-target dependencies. including relevant details about those sources or targets. When you view shortcut dependencies. if you select a target. For example. Figure 2-4 shows the Dependency window: Figure 2-4. you view all mappings using that transformation and details about each mapping.

You can also view mapping object dependencies in the Designer. see “Using the Designer” in the Designer Guide. With more complex operations. For example. the status bar displays the following message: Accessing the repository. The Designer allows you to view dependencies for sources. When you perform a more lengthy operation. however. 28 Chapter 2: Using the Repository Manager . When you edit an object referenced by shortcuts.. transformations. and shortcuts. Output Window When possible. Output Window You can change the font type and size displayed in the output window by right-clicking the window and selecting Change Font. the Repository Manager writes details about the operation into the Output window. you can use the Repository Manager to see which folders contain the shortcut. when you connect to a repository. the status bar displays the word Ready. Once connected to the repository. the Repository Manager displays detailed information in the Output window.. For details. the Repository Manager displays status messages in the status bar. such as copying a folder. mapplets. Figure 2-5 shows the Output window: Figure 2-5.folder in which the shortcut exists. targets. mappings. it displays dependencies for the object in the Navigator that you select. When you open the Dependency window.

2. Adding a Repository Add a repository when a repository already exists but does not appear in the Navigator of the PowerCenter Client. select the repository you want to remove. you can connect to it. For details on creating a repository. see “Connecting to a Repository” on page 30. In the Navigator of the Repository Manager. To add a repository: 1. you can reverse your action by adding it. In the Navigator of the Repository Manager. You add a repository when you want to access an existing repository from the PowerCenter Client. For details on connecting to a repository. Press Delete. 2. To remove a repository from the Navigator: 1. select the repository you want to remove. Choose Tools-Remove Repository. 4. The Repository Manager adds the repository to the Navigator. 3. but you can no longer access it. Removing a Repository When you remove a repository. After adding a repository. see “Creating or Promoting a Repository” on page 116. The repository remains intact. To remove a repository from the client registry: 1. In the Repository Manager. you remove it from the Navigator of the PowerCenter Client. After you remove a repository. you can also remove it from the PowerCenter Client registry. Adding a repository to the Navigator window does not create the repository. click OK to remove the repository. When a message box appears. you need to add the repository and reconfigure the connection information. To reverse this action. Select the repository you want to remove. After you remove a repository from the Navigator. You remove a repository when you want to remove access to an existing repository. Adding and Removing a Repository 29 . Enter the repository name and your repository user name.Adding and Removing a Repository You can add or remove a repository from the Repository Manager. choose Repository-Add Repository. 2. and click Delete.

Click the Connect button. 30 Chapter 2: Using the Repository Manager . You can also choose Repository-Connect. Enter the database user name and password used to create the repository. 4. To simplify the process of setting up client machines. see “Default Groups” on page 127. 2. To connect to a repository for the first time: 1. Verify the Repository Server is started. For more information on the default users in the Administrators group. the database user name used to create the repository and Administrator. Connecting to a Repository You can connect to a repository for the first time or connect to a repository you have previously accessed. Launch the PowerCenter Client tool and select the repository you want to connect to in the Navigator window. see “Installing and Configuring the Repository Server on Windows. The default password for Administrator is Administrator. the Repository Server creates two default users in the Administrators group. you can export that information and import it to a different client machine using the same operating system. The Connect to Repository dialog box appears. When you create a repository. You can connect to a repository for the first time or connect to a repository you have previously accessed.” or “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. you can connect to single or multiple repositories. 3.Working with Repository Connections From the Repository Manager. The Repository Manager also saves repository connection information in the registry. The repository administrator can connect to the repository as Administrator and change the default password. For details on starting and stopping the Repository Server.

you can select the repository icon and choose Repository-Connect. Select the icon for the repository and click the Connect button on the toolbar. Working with Repository Connections 31 . 7. Enter the host name of the machine the Repository Server is running on and the port number the Repository Server uses for connections. The Repository Server now opens a connection to the database. Existing folders in the repository now appear beneath the repository. Click Connect. select a repository and choose Repository-Connect. 6. To connect to a repository that you have accessed before: 1. Alternatively. 3. Click More. In the Navigator. Folders within the repository now appear underneath the icon for that repository. 2. and a new icon representing the repository appears in the Repository Manager. Connecting to Multiple Repositories The PowerCenter Client allows you to connect to multiple repositories and work in multiple folders at one time. 4. To make these connections. To create a global shortcut. Launch the PowerCenter Client tool. Enter your repository user name and password. The Connect to Repository dialog box expands.5. Click Connect. you can also connect from a local repository to a global repository and from a global repository to any local repository in a domain. The password must be in 7-bit ASCII. you must have identical logins in both repositories. To connect to multiple repositories separately: 1. When working in a domain. connect from the local repository to the global.

Connect to the global repository. 2. Connect to the local repository. choose Tools-Export Registry. informing you that the Repository Manager successfully exported the repository registry file. The contents of the local repository appear. A dialog box appears. see “Exporting and Importing Repository Configurations” on page 115. Click OK. and then import it to a different client machine. The section of the registry you can import and export contains the following repository connection information: ♦ ♦ ♦ Repository name Repository user name and 7-bit ASCII password Repository Server host name and port number The Repository Server uses repository configuration information separate from the connection information stored in the registry to manage repositories. you can access its contents. you can export that information. You now open a connection to the global repository. Double-click the icon for the global repository. In the Repository Manager. Enter the name of the export file.reg. Icons for all the local repositories in the domain appear beneath the global repository. Exporting/Importing Repository Connection Information The Repository Manager saves repository connection information in the registry. such as MySources. If the repository is part of a domain. 3. To connect from the global repository to a local repository: 1. To identify the file. 32 Chapter 2: Using the Repository Manager . To connect from a local repository to the global repository: 1.reg. By double-clicking a folder in either repository. 2. an icon for the global repository appears beneath the local repository icon. as well as folders in the local repository. Select another repository. use the extension . If you want to export or import repository configuration information for the Repository Server. To simplify the process of setting up client machines. choose Repository-Connect. Double-click the icon for the local repository you wish to access. 2. You see the folders within the global repository as well as those in the local repository.2. Both machines must use the same operating systems. To export the registry: 1.

In the Repository Manager. To import the registry: 1. A dialog box appears.You can now distribute this file for import on other client machines with the same operating systems. 2. 3. Working with Repository Connections 33 . Navigate to the directory containing the import file and select it. informing you that the Repository Manager successfully merged the repository connection information into your registry. choose Tools-Import Registry. Click Open.

The Search Target Tables For Keyword dialog box appears. or you can select one from the list of all keywords applied to target definitions in the repository. In the Repository Manager.Searching for Repository Objects In the Repository Manager. you can search for repository objects using the following methods: ♦ ♦ Keyword search Search text Perform a keyword search when you have associated a keyword with a target definition. 2. Use Search All when you want to search through text in object names. 34 Chapter 2: Using the Repository Manager . Choose Analyze-Search by Target Keyword. If you want to select a keyword. group names or owner names associated with the repository object. comments. click List Keywords. or Enter a keyword in the Keyword window. connect to a repository. select a keyword. Performing Keyword Searches Once you add keywords to target definitions. then click OK. You can enter a keyword. 3. To search for targets containing a keyword: 1. you can use them to perform searches in the Repository Manager.

4. displaying the list of matching keywords in the bottom window. and tasks. Ignore Case 5. If selected. In the Repository Manager. the search would return a keyword match for REPOSITORY. the Repository Manager looks for keywords that contain the keyword entered. The screen splits. the Repository Manager does not try to match the case of the keyword entered. You can search for text in the repository objects such as transformations. source and target fields. The Repository Manager now searches for matching keywords in all target definitions in the repository. To search for text in all repositor y objects: 1. the Repository Manager only looks for the entire keyword entered. Otherwise. Select the options you want to use in the search: Option Exact Match Description If selected. group name. or owner name associated with repository objects. connect to the repository. For example. comments. if you enter REPOS without selecting the Exact Match option. If not selected. Searching for Repository Objects 35 . Click OK. the keyword search is case-sensitive. Searching All Repository Objects Use Search All to search for text in the object name.

In the item list. The Repository Manager displays the first repository object matching the search text in the Main window. The Search All dialog box appears. Click Find Next. Choose Analyze-Search All. 36 Chapter 2: Using the Repository Manager . Click Find Next to find the next repository object matching the search text. 5. 6. select the repository objects in which you want to search for the text. Select the repository object attributes in which you want to search for the text. 3. The Repository Manager selects all attributes by default. 8. The Repository Manager selects all objects by default. Select Match Case if you want to perform a case-sensitive search.2. 4. 7. Click Close to close the Search All dialog box.

you can view dependencies when you review the results of the following tasks: ♦ ♦ ♦ View object history. Workflow Manager. You can view dependencies from the Query Results window when you search for object dependencies or run an object query. Workflow Manager. .Sources the mapping uses. . . In the Repository Manager. . Note: You can check in objects from the View Dependencies dialog box. . you can view dependencies to see the impact on other objects. .Transformations the mapping uses. and Designer tools.Targets the mapplet uses.Sources the mapplet uses. View checkouts.Global and local shortcuts to the mapping. . View query results. before you remove a session. . You can view dependencies from the View History window when you view the history of an object. but you cannot check in original objects for global shortcuts. and Designer.Global and local shortcuts to the mapplet.Sources within the same folder that reference the source through a foreign key relationship. For example. .Global and local shortcuts to the transformation.Viewing Object Dependencies Before you change or delete repository objects. you can find out which workflows use the session.Targets the mapping uses.Targets within the same folder that reference the target through a foreign key relationship.Global and local shortcuts to the target.Transformations the mapplet uses. Viewing Object Dependencies Parent Object Mappings Tool Mapping Designer Types of Child Objects Displayed . . You can view dependencies for repository objects in the Repository Manager. you can view dependencies from the tools in the Workflow Manager and Designer. and the objects that View Dependencies displays when you view dependencies: Table 2-2. Table 2-2 lists the Workflow Manager and Designer tools you can use to display dependencies. . . You can view dependencies from the View Checkouts window when you search for persistent checkouts.Global and local shortcuts to the source. In addition. Mapplets Mapping Designer Mapplet Designer Sources Mapplet Designer Mapping Designer Source Analyzer Mapping Designer Warehouse Designer Mapplet Designer Mapping Designer Transformation Developer Targets Transformations Viewing Object Dependencies 37 .

Table 2-2.Sources the workflow uses. and a list of dependent objects and their properties. .Session configuration the workflow uses.Sessions the workflow uses. .Sources the worklet uses. . .Targets the session uses. . . . . object type.Schedulers the worklet uses. .Sessions the worklet uses. 38 Chapter 2: Using the Repository Manager .Mappings the session uses. . . . . . . . . Workflows Workflow Designer Worklets Worklet Designer Workflow Designer Note: You can perform all searches in this table from the Repository Manager. .Mappings the worklet uses. . Viewing Object Dependencies Parent Object Sessions Tool Task Developer Worklet Designer Workflow Designer Types of Child Objects Displayed .Transformations the session uses. .Mapplets the workflow uses.Transformations the worklet uses. .Mapplets the worklet uses.Tasks the worklet uses.Tasks the workflow uses.Session configuration the session uses.Mappings the workflow uses.Targets the worklet uses.Session configuration the worklet uses.Mapping the session uses.Schedulers the workflow uses. . You can view object dependencies in the Workflow Manager and Designer when you work with objects in the workspace.Sources the session uses. You can view object dependencies when you open objects in the following tools: ♦ ♦ ♦ ♦ Mapping Designer Mapplet Designer Workflow Designer Worklet Designer The Dependencies dialog box displays the object name.Worklet the workflow uses.Mapplets the session uses. . .Tasks the session uses. .Transformations the workflow uses.Targets the workflow uses. .

Search for dependencies. When you search for dependencies. For example. View global shortcuts across repositories. Dependencies Options Option All Parents Description View the objects that use the selected object. the results might include a workflow or worklet. View the objects that the selected object uses. children. Filter by object type when you search for parent or child dependencies. You can select this option when you search for parents. Dependencies Dialog Box Select options. or primary key-foreign key dependencies. Viewing Object Dependencies 39 . Table 2-3 shows the options you can select when you search for dependencies: Table 2-3. the results window displays the properties for each dependent object. you can filter the results by selecting options and object types. if you search for the parent objects for a session. All Children PK/FK Dependencies Go Across Repositories When you search for dependencies.Figure 2-6 shows the Dependencies dialog box: Figure 2-6. the results might include sessions and worklets. View primary and source object dependencies where there is a primary key-foreign key relationship. For example. if you search for the child objects for a workflow.

Dependent objects can be any of the following types: . DB2.Workflows . or XML. Status of the object. The type of dependent object.Mapplets . the group type can be Oracle. View Dependencies Window Object Properties Output Window Comments Window Labels Window Table 2-4 describes the object properties that display in the View Dependencies window: Table 2-4.Figure 2-7 shows the View Dependencies window: Figure 2-7. For example. Object Properties for View Dependencies Window Properties Object Name Group Name Object Type Description The name of the dependent object.Target definition . Comments associated with the dependent object.Mappings .Source definition The version number of the dependent object. Time the object was created or saved.Foreign key dependency . DBD associated with the source of the object. Active or Deleted.Sessions .Worklets . Version Time Stamp Status Version Comments 40 Chapter 2: Using the Repository Manager .Shortcuts .

Object Dependencies Saved as HTML Viewing Object Dependencies 41 . The View Dependencies window also displays output. Status of object deletion. Yes or No. The Output window displays validation information. Persistent or Non-Persistent. choose File-Save to File. Object Properties for View Dependencies Window Properties Folder Name User Name Host Name Checkout Type Purged by User Is Reusable Is Deleted Repository Description The folder name where the dependent object resides. and label information associated with the object. Status of object as reusable.Table 2-4. Name of the user who purged the object. and the Comments window displays text entered during object check in or check out. To save the list of dependent objects as an HTML file. User who created the object. Type of checkout for object. The Labels window displays labels associated with the object and information associated with the label object. Yes or No. comments. Host name for the machine hosting the object. Repository hosting the object. Figure 2-8 shows an example of the HTML file saved from a View Dependencies window: Figure 2-8.

The Validate Objects dialog box displays. If you do not choose to save the objects in the repository. If you select objects from query results or a list view. or Workflow Manager. Select validation options from the Validate Objects dialog box: ♦ ♦ Save validated objects. Choose whether to check in validated objects. You can also select objects from query results or an object dependencies list. you can choose different types of objects to validate. To validate multiple objects: 1. You can automatically check in valid objects. the validation just provides a report. you can also choose Tools-Validate to initiate a validation. Initiate the validation. ♦ 42 Chapter 2: Using the Repository Manager .Validating Multiple Objects PowerCenter allows you to validate multiple objects in the repository without fetching them into the workspace. and you can select them from within the Repository Manager. If you select objects from query results or an object dependencies list. Designer. mapplets. If you are checking in validated objects you must enter check in comments. see the Designer Guide. You can only select this option if you have selected the Save Objects option and versioning is enabled in the repository. in the same folder. If you select objects from the Repository Manager navigator. For information about mapping validation. 3. You can select objects to validate from the Repository Manager navigator. you can only select objects of the same type. You can validate sessions. and worklets. Otherwise this option is disabled. You can save and optionally check in objects that change from invalid to valid status as a result of the validation. see the Workflow Administration Guide. mappings. workflows. Check in comments. If you are selecting objects from the Navigator. 2. For information on validating sessions and workflows. Select the objects you want to validate. you must right-click one of the selected objects and choose Validate.

If you cancel. Validate Objects Results Hyperlinks to view the objects in the group. You can cancel the validation from the progress dialog box. The total includes skipped objects. If you do not choose the Save Objects or Check In Objects options. Table 2-5 describes the information that displays in the Validate Objects window.4. such as a deleted mapping associated with a session being validated. . Table 2-5. Use the results box to determine how many objects were validated and saved. The results box displays when validation completes.Objects that do not require validation. Validate Objects Properties Properties Objects provided for validation Skipped objects Description The total number of objects that you selected to validate. The number of selected objects that are valid. click the hyperlink. you cancel the remaining operations in the validation. such as sources. The number of objects that require fixing or editing. Figure 2-9 shows the Validate Objects results box. this number is zero. To view the objects in each total. targets. Objects that were invalid before the validation Objects successfully validated Objects still invalid Saved/checked in objects Cannot save objects due to lock conflict Validating Multiple Objects 43 . The validation displays status in a progress dialog box. and shortcuts. The number of invalid objects provided for validation. Click Validate. transformations. The number of the following types of objects: . you do not cancel the current operation. The number of validated objects you cannot save because someone has them locked. The total number of objects saved.Objects that cannot be fetched. The output window of your current screen shows the status of each object being validated. Figure 2-9.

a dialog box displays each object in the results group you select.5. When you click the hyperlink. Click a hyperlink to view the objects in the results group. Validation results that have more than zero objects in them have hyperlinks to the object details. 44 Chapter 2: Using the Repository Manager .

You can also compare different versions of the same object. For example. ♦ You can compare instances of the same type in detail. You can compare objects across folders and repositories. When you compare two objects. Comparing Repository Objects 45 . For more information about versioned objects. select the object you want to compare. Workflow Manager objects. the Repository Manager displays their attributes. To compare repository objects: 1. you must have read permission on each folder that contains the objects you want to compare. you can compare two sessions to check for differences. and workflows. such as tasks. connect to the repository. For more information about comparing objects in the Designer. worklets. see the Workflow Administration Guide. You can compare a reusable object with a non-reusable object. Use the following procedure to compare objects. see the Designer Guide. sessions. if the workflows you compare contain worklet instances with the same name.Comparing Repository Objects The Repository Manager allows you to compare two repository objects of the same type to identify differences between the objects. You can compare schedulers and session configuration objects in the Repository Manager. you must have both the folders open. but not in the Workflow Manager. Tip: To compare the first two objects in a node. you can compare the instances to see if they differ. In the Navigator. To compare objects. For more information about comparing objects in the Workflow Manager. 2. You can compare instances of mappings and transformations in a session comparison. see “Comparing Versions” on page 210. For example. For example. In the Repository Manager. You can compare the following types of objects: ♦ Designer objects. Further. You can compare Designer objects. You can compare instances of sessions and tasks in a workflow or worklet comparison. you cannot compare a source definition with a target definition. You can compare Workflow Manager objects. mapplets and mappings. targets. select the node. You cannot compare objects of different types. you can compare instances of the same type within a mapping or mapplet comparison. To do this. transformations. such as sources.

A dialog box similar to the following one appears: 4. 46 Chapter 2: Using the Repository Manager . Choose Edit-Compare Objects. Click Compare. such as a source. the Sources window shows the result of comparing two sources: View object differences.3. If you choose a Designer object.

Displays the properties of the node you select.If you choose a Workflow Manager object. Differences between object properties are marked. such as a session. the Diff Tool window shows the result of comparing two sessions: Filter nodes that have same attribute values. Compare object instances. Differences between objects are highlighted and the nodes are flagged. Comparing Repository Objects 47 .

enter the date and time. the PowerCenter Server saves those logs in local directories. 2. The Truncate Workflow Log dialog box appears. If you move or delete a session log or workflow log from the workflow log directory or session log directory.Truncating Workflow and Session Log Entries When you configure a session or workflow to archive session logs or workflow logs. The repository also creates an entry for each saved workflow log and session log. Choose Edit-Truncate Log. Choose whether you want to delete all workflow and session log entries. or all workflow and session log entries with an end time older than a certain date. The Repository Server deletes the workflow and session log entries from the repository. 5. To truncate workflow and session log entries: 1. 4. The Repository Server truncates the workflow log list and the session log list at the same time. In the Repository Manager. Use the Repository Manager to truncate the list of workflow logs. Click OK. You can truncate all of the workflow logs entries in the list. you can remove the entries from the repository. select the workflow in the Navigator window or in the Main window. The repository always retains the most recent workflow log entry for each workflow. and it always retains the most recent session log entry for each session. 48 Chapter 2: Using the Repository Manager . 3. If you want to delete all entries older than a certain date. or you can truncate all workflow logs before a specified date.

62 Deleting a Repository. 52 Registering and Connecting to the Repository Server. 74 Registering a PowerCenter Repository. 88 Reading the Repository Log Files. 75 Migrating the Repository to a Different Repository Server. 77 Propagating Repository Domain Connection Information. 83 Registering and Unregistering Repository Plug-ins. 60 Copying a Repository. 79 Closing User Connections and Locks. 50 Navigating the Administration Console. 71 Sending Repository Notifications. 97 49 . 85 Registering and Unregistering LDAP Security Modules. 58 Tuning Repository Performance.Chapter 3 Managing the Repository This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 66 Starting and Stopping the Repository. 64 Backing Up and Restoring a Repository. 78 Viewing User Connections and Locks.

Register and unregister a repository. enable. Send repository notification messages. creating repositories. stop. Permissions and Privileges When you connect to a Repository Server in the Administration Console. For details on upgrading a repository. Copy a repository. Delete a repository from the database. Edit repository license files. Export and import repository configurations. Register and remove repository plug-ins. and remove repository configurations. Promote a local repository to a global repository. For details on repository architecture and connectivity. You can use the Administration Console to perform the following tasks: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Add. Propagate domain connection information for a repository. A Repository Server can manage multiple repositories. View repository connections and locks.Overview The PowerCenter repository is a collection of database tables containing metadata. see “Configuring the Repository” on page 103. you can perform all tasks in the Administration Console for repositories the Repository Server manages. you use the administrator password specified in the Repository Server setup. Start. edit. see “Repository Architecture” on page 3 and “Repository Connectivity” on page 4. Close repository connections. and licenses. Create a repository. promoting repositories. Back up and restore a repository. For details on working with repository configurations. When you connect to a Repository Server. 50 Chapter 3: Managing the Repository . The Repository Server manages repositories. The Repository Server performs all metadata transactions between the repository database and repository client applications. see “Upgrading a Repository” in the Installation and Configuration Guide. and disable repositories. Upgrade a repository. You use the Repository Server Administration Console to create and administer the repository through the Repository Server.

However. The PowerCenter Client and Server code pages must be compatible with the repository code page. Overview 51 . or restore a repository. When you create. For more information on code pages. Note: EBCDIC code pages appear in the list of possible repository code pages when they are compatible with the PowerCenter Client code page. copy. see “Globalization Overview” in the Installation and Configuration Guide. do not select an EBCDIC code page for the repository code page. you must choose a repository code page from a list of code pages that are compatible with the PowerCenter Client.Repository Code Pages Every repository has an associated code page. since you cannot create a repository on mainframes.

starting.Navigating the Administration Console Use the Administration Console to connect to the Repository Server and perform repository administration tasks. The Administration Console displays a different set of Action menu items depending on which 52 Chapter 3: Managing the Repository . You must start the Repository Server before you can perform repository administration tasks. Figure 3-1 shows the Administration Console: Figure 3-1. choose RepositoryManage Repository Server. The Administration Console is a snap-in for MMC. such as creating. see “Installing and Configuring the Repository Server on Windows” and “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. On Windows. For more information on using MMC. MMC is a console framework for server and network management applications called snapins. The Administration Console uses Microsoft Management Console (MMC) technology. On UNIX. start the Repository Server service from the Services control panel. You can also launch the Administration Console from the Windows Start menu. and backing up repositories. see the online help for MMC. To launch the Administration Console from the Repository Manager. The Administration Console allows you to navigate multiple Repository Servers and repositories and perform repository management tasks. For details on starting and stopping the Repository Server. Administration Console Main Window Console Tree Nodes Console Tree The Console Tree allows you to browse Repository Servers and managed repositories. start the Repository Server from the command line.

or you can list them with or without item details. In List view. and registering with a global repository. Activity Log. such as backing up. locks. Available Packages. Figure 3-1 on page 52 shows the Administration Console in List view. Select this node to view existing object locks in the repository. Expand this node to perform repository functions. Expand this node to connect to a Repository Server or to register a Repository Server. Select this node to view the latest activity performed on all repositories managed by the Repository Server. Repository Server name. Figure 3-2 on page 55 shows the Administration Console in HTML view. Choose ViewDetails to view detailed information for a node in List view. Repository name. The Administration Console only displays repositories in HTML view. you can arrange the items in different ways by choosing the View menu. if you select a repository in the Console Tree. such as copying or backing up a repository. Backups. ♦ ♦ ♦ ♦ ♦ ♦ Main Window The Main window displays details of the node you select in the Console Tree. Lists the managed repositories. the Main window displays the properties of the repository. such as the status and start time. Backups. Lists repository locks. Expand this node to add or import a repository configuration. Displays repository information as a dynamic HTML page. Select this node to restore a repository from a backup file. You can view items as large or small icons. Repositories. The Console Tree contains the following nodes: ♦ ♦ ♦ Repository Servers. You can also right-click a node to access the Action menu items. The hypertext links are shortcuts to some Action menu items. Activity Log. Lists the nodes under it: Repositories. For example. Displays a collection of items that includes an icon and a label.node you select in the Console Tree. HTML view includes hypertext links that allow you to perform actions on the selected node. HTML view. ♦ Navigating the Administration Console 53 . Connections. Lists recent Repository Server activity. Locks. upgrading. and Available Packages. Lists repository information. Lists user connection details. and user connections. Lists the plug-ins available to the Repository Server. Lists the repository backup files available in the Repository Server backup directory. Select this node to view user connection information and to manually close connections. Lists the registered Repository Servers. and to start or stop all repositories managed by the Repository Server. Select this node to register and remove plug-ins. The Main window displays results in the following views: ♦ List view.

Backups. Repositories Node Details When you select the Repositories node. 54 Chapter 3: Managing the Repository . or disabled. The port number used to access the Repository Server. and Available Packages. the Main window displays details about each repository managed by the Repository Server. the Main window displays each node under the Repository Server node: Repositories.Repository Servers Node Details When you select the Repository Servers node in the Console Tree. Repository Servers Node Details Column Name Host Name Port Number Status Description The name of the computer hosting the Repository Server. stopped. either running. The start time of the repository. the Main window displays details about the repository in HTML view. the Main window displays details about each registered Repository Server. either connected or not connected. Repositories Node Details Column Name Name Status Start Time Description The name of the repository. Activity Log. The Main window also displays HTML links that allow you perform some repository tasks. Table 3-2 list Repositories node details that display in the Administration Console: Table 3-2. Table 3-1 lists Repository Servers node details that display in the Administration Console: Table 3-1. The connection status of the repository. Repository Server Name Node Details When you select a Repository Server in the Console Tree. The status of the repository. Repository Name Node Details When you select a repository in the Console Tree.

If you shut down the Repository Server. use this number to identify which error messages apply to the Repository Agent. The date display format is MM/DD/YYYY 24 HH:MI:SS. For more information. The type of database where the repository resides. Database Type Table 3-4 lists the HTML links for performing some repository tasks: Table 3-4. The Windows or UNIX process identification number assigned to the Repository Agent. starting. either running. see “Stopping the Repository” on page 72. see “Backing Up a Repository” on page 66. Back up the repository to a binary file. For more information on the repository log file. Repository Details Attribute Status Start Time Number of Restarts Process ID Description The status of the repository. The total number of times the repository started since the Repository Server started. stopping. HTML Links for Performing Repository Tasks HTML Link Stop Backup Description Stop the repository. Repository Details HTML View Hypertext Link Table 3-3 lists repository details displayed in the Administration Console: Table 3-3. The date and time the repository last started. The Repository Server and Repository Agent append this number to entries in the Repository Server and Repository Agent log files. this property resets to 0. When you troubleshoot the repository. For more information.Figure 3-2 shows repository details: Figure 3-2. stopped. see “Reading the Repository Log Files” on page 97. or disabled. Navigating the Administration Console 55 .

you can save the activity information to a text file by choosing Action-Save As. Connections Node Details When you select the Connections node. see “Viewing Locks” on page 80. Activity Log Node Details When you select the Activity Log node. and server configuration parameters for the repository. Activity Log Window 56 Chapter 3: Managing the Repository . such as starting a repository. Locks Node Details When you select the Locks node. This information also displays in the Main window when you select the Activity Log node. View general. For details. the Main window displays details about the locks associated with the selected repository. This includes activities such as upgrading or starting a repository. see “Adding a Repository Configuration” on page 105. For more information. For more information see “Restoring a Repository” on page 67. the Main window displays user connections to the repository. the Administration Console shows the Activity Log in a popup window. see “Viewing User Connections” on page 79. database. the Main window displays all activity the Repository Server performed on all managed repositories since you launched the Administration Console and connected to the Repository Server. Upgrade the repository to the latest version. For more information. For details. When you perform some repository management tasks. Figure 3-3 shows the Activity Log window: Figure 3-3. When you select the Activity Log node. HTML Links for Performing Repository Tasks HTML Link Restore Upgrade Properties Description Recover metadata from a repository binary backup file. see “Upgrading a Repository” in the Installation and Configuration Guide. network.Table 3-4.

see “Reading the Repository Log Files” on page 97. Change the font of all text. For more information about Repository Server log files.When you right-click the Activity Log window. the Main window displays the plug-in files available to register in the Repository Server plug-in directory. The Administration Console does not display Repository Server log file messages. you can perform the following tasks: ♦ ♦ ♦ ♦ ♦ Select all text. Save the information to a text file. Clear all text. the Main window displays the repository backup files available in the backup directory specified in the Repository Server setup. Available Packages Node Details When you select the Available Packages node. Backups Node Details When you select the Backups node. Copy selected text. Navigating the Administration Console 57 .

you must connect to the Repository Server. the Administration Console maintains the connection until you disconnect from the Repository Server or close the Administration Console. You must register a Repository Server to connect to it. 58 Chapter 3: Managing the Repository . To connect to the Repository Server: 1. Choose Action-New Server Registration. Launch the Administration Console and select the Repository Servers node. Launch the Administration Console and expand the Repository Servers node in the Console Tree. 2. You can connect concurrently to multiple Repository Servers. For details on configuring the Repository Server. The Repository Server icon in the Console Tree changes depending on the connection state. enter the password you use to administer the Repository Server and the port number used to access the Repository Server. 3. Registering a Repository Server Use the following procedure to register a Repository Server. see “Installing and Configuring the Repository Server on Windows” or “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. When you connect to a Repository Server. 2. The Administration Console connects to the Repository Server and displays the managed repositories. and click OK. Click OK. Connecting to the Repository Server Use the following procedure to connect to the Repository Server. To register a Repository Server: 1. The Administration Console adds the Repository Server to the Console Tree. Right-click the Repository Server and choose Connect. 3. In the Connecting to Repository Server dialog box. Enter the Repository Server host name and port number.Registering and Connecting to the Repository Server To perform repository administration tasks.

expand the Repository Servers node. Right-click the Repository Server and choose Disconnect.Disconnecting from the Repository Server Use the following procedure to disconnect from the Repository Server. To disconnect from the Repository Server: 1. 2. In the Console Tree. Registering and Connecting to the Repository Server 59 .

restore. Over time. or restore a repository. You can update statistics and skip information when you copy. the impact of choosing a sub-optimal query plan can affect performance drastically. and restore dialog box contains an Advanced button that allows you to choose the information you want to skip. see “pmrepagent Commands” on page 477. For more details. you reduce the time it takes to copy. you can choose to skip the following types of information: ♦ ♦ ♦ Workflow and session logs Deploy group history MX data By skipping this information. Backup. or restore the repository. upgrade. see “Updating Repository Statistics (UpdateStatistics)” on page 447. You can also skip this information when you use the pmrepagent commands. For details. 60 Chapter 3: Managing the Repository . backup. back up. You can also update statistics using the pmrep command Updatestatistics. these statistics can become outdated very quickly and SQL query optimizers may not choose the best query plan. backup. Each copy.Tuning Repository Performance PowerCenter includes features that allow you improve the performance of the repository. the repository becomes slower and slower. You have the option of skipping the information that is not essential to the function of the repository. and almost all tables use at least one index to speed up queries. or copy a repository. Increasing Repository Copy. In frequently-used repositories. Most databases keep and use column distribution statistics to determine which index to use to execute SQL queries optimally. When you back up. Updating Repository Statistics The PowerCenter repository has more than 170 tables. In large repositories. Database servers do not update these statistics continuously. and restore repositories. PowerCenter identifies and updates the statistics of all repository tables and indexes when you copy. and Restore Performance Large repositories may contain a lot of log and history information that slows down repository performance.

If you are copying a repository. Note: You can optimize repository performance for repositories on IBM DB2 EEE. For more information. or restoring a repository: 1.To skip information when copying. Backup Repository dialog box. 4. 3. follow the steps to restore a repository in “Restoring a Repository” on page 67. follow the steps to copy a repository in “Copying a Repository” on page 62. If you are backing up repository. Select the data you want to skip. or Restore Repository dialog box. or restoring the repository. 2. and continue copying. backing up. backing up. Tuning Repository Performance 61 . Click OK. If you are restoring a repository. Click the Advanced button on the Copy From Another Repository dialog box. follow the steps to back up a repository in “Backing Up a Repository” on page 66. see “Creating a Repository” in the Installation and Configuration Guide.

If you want to copy a repository managed by the same Repository Server. The Copy From Another Repository dialog box appears. When you copy a repository. set allow nulls by default to TRUE at the database level. Setting this option changes the default null type of the column to null in compliance with the SQL standard. select the target repository configuration. you must add or import a repository configuration for the target repository. Copy a repository to preserve the original repository before upgrading. 62 Chapter 3: Managing the Repository . The Repository Server uses the connection information in this repository configuration to connect to the target database when it copies the source repository. To copy a repository. Note: If you want to copy a Sybase repository.Copying a Repository You can copy a repository from one database to another. 3. choose Managed By the Same Repository Server. you must select a code page for the target repository that is compatible with the original repository. see “Adding a Repository Configuration” on page 105 and “Importing a Repository Configuration” on page 115. In the Console Tree. 2. For details. the copy operation fails. To copy a repository: 1. If a repository exists in the target database. You can also copy a repository when you want to move a repository from development into a production environment. You must back up and delete the existing repository from the target database before copying the repository. and select a repository from the repository list. Choose Action-All Tasks-Copy From. Copying repositories provides a quick way to copy all metadata you want to use as a basis for a new repository.

Copying a Repository 63 . Backup. and enter the repository name. and Repository Server port number. 7. Enter the repository user name and password for the source repository. 6. see “Increasing Repository Copy. and MX data. 5. For more details. If you want to copy a repository managed by a different Repository Server. You can view the progress of the copy in the Activity Log. select Managed By a Different Repository Server. To skip workflow and session logs. and Restore Performance” on page 60. click the Advanced button.4. The Repository Server starts the repository when it finishes copying it. deploy history. Click OK. The Repository Server copies the repository from the source repository to the database specified in the destination repository configuration. Repository Server host name.

If the repository contains information that you might need. Unless you unregister all local repositories. 2. 4. select the repository you want to delete. Note: You can also use the pmrepagent Delete command to delete repositories. Delete the repository in the database. You must stop and disable the repository before you delete it. The Repository Server stops the repository. For more information. For more information on stopping and disabling the repository. see “Deleting a Repository (Delete)” on page 481. The Deleting a Repository dialog box appears. Choose Action-Delete. <global repository name>. and click OK. contains registered repositories (<local repository names>). To delete a repository: 1. 5. This option instructs the Repository Server to delete the repository metadata and tables from the database. You might delete a repository if metadata is obsolete. back up the repository before you delete it.Deleting a Repository Delete a repository when you want to delete all metadata and repository database tables in the repository. see “Stopping the Repository” on page 72 and “Disabling the Repository” on page 73. If the repository you want to delete is a global repository. you must choose to unregister all local repositories. The Administration Console displays the following message: This repository. the Repository Server does not delete the global repository. If the repository is running. Choose Action-Disable. Deleting a repository is an irreversible action. The Repository Server disables the repository so that other users cannot start it. There was an error deleting the repository. choose Action-Stop. 3. In the Console Tree. Select Delete the Repository. 64 Chapter 3: Managing the Repository .

7. If the repository is a global repository. When you click Yes. Click OK. 9. 8. The Repository Server deletes the repository. The Delete Repository Content dialog box appears. the Administration Console removes the repository from the Console Tree. When prompted to delete the repository. Enter your repository user name and password. click OK. After the Repository Server deletes the repository. you can choose to unregister all local repositories. When you click No. Click No to keep the repository configuration. and it keeps a backup of the repository configuration file in the Repository Server configuration directory. You can monitor the progress of the delete operation in the Activity Log. 10.6. the Administration Console keeps the repository in the Console Tree. you can choose to keep or remove the repository configuration. or click Yes to remove it. Deleting a Repository 65 .

If you need to recover the repository. Enter your repository user name. connection information. Tip: You can also click Backup in the Main window. Specify a name for the backup file. the Repository Server saves the repository in a binary file. including the repository objects. Specify the backup directory in the Repository Server setup. The Repository Server uses the extension . 2. Choose Action-All Tasks-Backup. select the repository you want to back up. Use an easily distinguishable name for the file. You can also enter a description for the backup file. In the Console Tree. and file name for the repository backup file. The Repository Server saves the backup file in the Repository Server backup directory.rep. you might name the file DEVELOPMENTMay7. password. if the name of the repository is DEVELOPMENT. For example. and code page information. 66 Chapter 3: Managing the Repository . The Backup Repository dialog box appears. To back up a repository: 1. When you back up a repository. 3.rep for all repository backups. and the backup occurs the first week of May. the Repository Server stores the file in the Repository Server backup directory. you can restore the contents of the repository from this binary file. Backing Up a Repository When you back up a repository.Backing Up and Restoring a Repository Regularly back up your repositories to prevent data loss due to hardware or software problems.

Backing Up and Restoring a Repository 67 . you must have a Team-Based Development option license key to restore a versioned repository. and connectivity license keys to the repository license file when you edit the repository configuration you use to restore the repository backup file. If you want to restore a repository. In the Administration Console. If a repository already exists at the target database location. Note: If you want to create. 5. restore. If you have a backup file from an earlier version of PowerCenter or PowerMart. When restoring a repository. For details on the minimum system resources required to create a repository. see “Increasing Repository Copy. you must have a database available for the repository. Restoring a Repository You can recover metadata from a repository binary backup file. deploy history. You can view the backup operation in the Activity Log. For more information on licenses. If you want to overwrite an existing repository backup file. the Repository Server does not back up the repository. Verify you add the product. You can restore the repository in a database that has a compatible code page with the original database. replace the existing file. You must delete the repository database before restoring a backup repository. and Restore Performance” on page 60. you must have at least the minimum system resources required to create a repository. 6. option. The Repository Server does not restore a repository if one already exists in the target database location. set allow nulls by default to TRUE at the database level.4. Click OK. PowerCenter can restore repositories from the current version only. The actual amount of disk space required to restore the repository depends on the size of the repository backup file. see “Restoring a Repository (Restore)” on page 485 and “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. and you do not choose to replace the existing file. or upgrade a Sybase repository. To skip workflow and session logs. For more information. you must delete it before restoring a repository backup file. If you specify a file name that already exists in the Repository Server backup directory. and MX data. You can also use the pmrepagent Restore command to restore repositories. Setting this option changes the default null type of the column to null in compliance with the SQL standard. Backup. see “Working with PowerCenter Licenses” on page 119. you can restore a repository from either the Backups node or a repository name node. or the Bulkrestore command to restore Teradata repositories. you must use the earlier version to restore the repository. For more details. see “Creating a Repository” on page 116. click Advanced. For example.

To restore a repository from the Backups node: 1. and choose ActionRestore. select the Backups node. 3. deploy history. 5. For details on creating a repository configuration. The Restore Repository dialog box appears. 2. Backup. Choose to create a repository configuration or to use an existing repository configuration. 4. The Administration Console allows you to create a repository configuration or use an existing repository configuration for the restored repository. see “Adding a Repository Configuration” on page 105. see “Increasing Repository Copy. and Restore Performance” on page 60. The Main window lists the available backup files in the Repository Server backup directory. Click OK. Use an existing repository configuration. To skip workflow and session logs. For details. In the Main window. 68 Chapter 3: Managing the Repository . In the Console Tree. and MX data. select the repository backup file to restore. Create a repository configuration. click Advanced.

If the repository uses a security module. 7. The Repository Server restores the repository. If you choose to unregister the security module. To restore a repository from a repository name node: 1. If the Restore Repository-Security Module dialog box displays. In the Console Tree. If you choose to keep the external module. you must choose whether to restore the repository with the external module or to unregister the security module when you restore. Choose Action-All Tasks-Restore. The Repository Agent does not assume that the same user authentication module is on the new system.” The other user names become disabled. Backing Up and Restoring a Repository 69 . The Repository Agent verifies that the password is valid for the user name on the target server. the Administrator account password becomes “Administrator. Click OK. You can view the restore process in the Activity Log. 2. the Restore Repository-Security Module dialog box displays. you must specify the repository administrator user name and password. 6. select a repository configuration under the Repositories node to use for the restored repository. so it verifies that the administrative user can connect to the repository if the restore completes.

3. you must specify the repository administrator user name and password. If you choose to keep the external module. Click OK. 5. The Administration Console lists backup files in the Repository Server backup directory. The Repository Server restores the repository. you must choose whether to restore the repository with the external module or to unregister the security module when you restore. the Restore Repository-Security Module dialog box displays. Click OK.” The other user names become disabled. and MX data. For details. If the Restore Repository-Security Module dialog box displays. 4. To skip workflow and session logs. the Administrator account password becomes “Administrator. You can view the restore process in the Activity Log. and Restore Performance” on page 60. so it verifies that the administrative user can connect to the repository if the restore completes. If you choose to unregister the security module. In the Restore Repository dialog box. 6. see “Increasing Repository Copy. select the backup file to restore. The Repository Agent does not assume that the same user authentication module is on the new system. The Repository Agent verifies that the password is valid for the user name on the target server. deploy history. If the repository uses an authentication module. click Advanced. 7. Backup. 70 Chapter 3: Managing the Repository .

The Enable option is available when the repository is disabled. or enable the repository. Choose Action-Enable. Disable the repository to prevent other users or applications from starting it. Use the following steps as a guideline when you perform these tasks: 1. You can also use the Start command to restart the repository if it stops unexpectedly. see “Editing a Repository Configuration” on page 113. enable the repository to allow other users or applications to start it. In the Console Tree. Perform the repository administration task or edit the repository configuration. Remove the repository configuration. The Repository Server starts the repository. 3. If you want to start the repository. After restoring or upgrading the repository. 3. Starting the Repository The Start command allows you to manually start the repository. 4.Starting and Stopping the Repository The Administration Console allows you to manually start. The Repository Server enables the repository. Stop the repository. disable. You must stop the repository to perform the following repository administration tasks: ♦ ♦ ♦ Upgrade the repository. 2. Delete the repository. Use these commands when you perform repository administration tasks that require you to stop the repository. 5. stop. Start the repository. You should also stop the repository when you edit repository configuration parameters that are not dynamically updated. Enabling the Repository Enable the repository to allow you or other users full access to start a disabled repository. choose Action-Start. You can use the Start command to ensure a repository with a new or edited configuration initializes properly. To enable the repository: 1. 2. select the repository you want to enable. For more information on dynamic updating. The Starting and Stopping the Repository 71 .

3. see “Working with PowerCenter Licenses” on page 119. Choose Action-Disable if you want to prevent other users or applications from restarting the repository. send a notification telling repository users to save work in progress and disconnect from the repository. You must stop the repository before upgrading or deleting it. You can view the progress of the stop operation in the Activity Log. select the repository you want to start. You can view the startup progress in the Activity Log. 2. If the repository is disabled.Repository Server starts an enabled repository for client applications requesting a connection to the repository. You can also use the Stop All command to stop all repositories managed by the Repository Server. see “Disabling the Repository” on page 73. Check for active user connections before you stop the repository. The repository closes all connections to repository client applications before stopping. Note: Before you start the repository. For details on disabling the repository. In the Console Tree. The Repository Server starts the repository. For more information on licenses. Choose Action-Stop. disable the repository. Stop all repositories if you need to shut down the Repository Server. 72 Chapter 3: Managing the Repository . For details on viewing user connections. 3. The Repository Server only starts a repository if the repository license file exists in the Repository Server installation directory and it contains a valid product license key. You can also disable the repository while it is running. To stop a single repository: 1. Note: To avoid loss of data. To start a single repository: 1. you must start the Repository Server. In the Console Tree. select the repository you want to stop. Choose Action-Start. choose Action-Enable. Stopping the Repository The Stop command allows you to manually stop the repository to perform administration tasks. To prevent other repository client applications from starting the repository after you stop it. 2. The Repository Server stops the repository. see “Viewing User Connections” on page 79. see “Installing and Configuring the Repository Server on Windows” and “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. For details on starting the Repository Server.

2. Choose Action-Disable. the repository status changes from running to disabled. Disabling the Repository When you disable the repository. The Repository Server stops all repositories it manages. the repository continues to run and the repository status indicates it is running. In the Console Tree. you prevent other users or repository client applications from starting it. When you stop a disabled repository. Starting and Stopping the Repository 73 . To disable the repository: 1. select the Repositories node. see “Enabling the Repository” on page 71. You must enable the repository to start it. Disable the repository when you need to restore or upgrade the repository. You should also disable the repository when you edit configuration parameters that the Repository Server does not dynamically update.To stop all repositories: 1. Choose Action-Stop All. In the Console Tree. The Repository Server disables the repository. If the repository is running. You can disable a repository while it is running. For details on enabling the repository. select the repository you want to disable. 2. the repository status changes to disabled when you stop the repository. You must enable the repository before starting it again. You can view the progress of the stop operation in the Activity Log. When you disable a running repository.

Sending Repository Notifications You can create and send repository notification messages to users connected to the repository. The Notification Message dialog box appears. Choose Action-All Tasks-Notify Users. You can view the message text on the Notifications tab of the PowerCenter Client Output window. In the Console Tree. 4. Choose whether you want to send the notification message to users connected to the selected repository or all repositories managed by the Repository Server. The Repository Server sends the notification message to all PowerCenter Client users connected to the repository. Enter the message you want to send. or to all users connected to all repositories managed by the Repository Server. 3. You can send a repository notification message to users connected to a single repository. 2. You might want to send a notification message to notify users of scheduled repository maintenance or other tasks that require you to stop the repository or Repository Server. select the repository you want to send the message to. A message box informs the user that the notification was received. and click OK. 74 Chapter 3: Managing the Repository . To send a repository notification message: 1.

When working in a domain. Choose Action-All Tasks-Register. the Repository Server reestablishes global shortcuts. the code pages of the local and global repository must be compatible. Promote metadata from a local repository to a global repository. For details on propagating repository domain registration information. see “Globalization Overview” and “Code Pages” in the Installation and Configuration Guide. When you register a local repository. making it accessible to all local repositories in the domain. A Repository Server running on the same machine on which the repository resides yields higher performance for repository transactions. Copy objects from or create shortcuts to metadata in the global repository. see “Propagating Repository Domain Connection Information” on page 78. Registering a PowerCenter Repository 75 . If you unregister a repository from the global repository and then register it again. To register a local repository: 1. Copy objects from the local repository to the global repository. you can register all local repositories with the copy of the global repository. propagate the domain connection information for the moved repository to other repositories in the domain. Tip: You can also click Register in the Main window. 2. When you move a registered local or global repository to a different Repository Server in the domain. You can register a local repository to the global repository managed by a different Repository Server. select the global repository. you can perform the following tasks: ♦ ♦ ♦ ♦ Navigate from local to global repositories without connecting to each repository separately. You might want to have the local and global repositories managed by different Repository Servers if the repositories reside on different machines.Registering a PowerCenter Repository You can register local repositories with a global repository to create a domain. For details on code page compatibility. This allows you to copy objects from the local repository to the global repository and to create shortcuts or copy objects from the global repository to the local repository. In the Console Tree. For example. if you create a copy of the global repository and delete the original. The Repository Server reestablishes all global shortcuts unless you delete objects from the copied repository.

Choose the global repository from the global repository list. 76 Chapter 3: Managing the Repository . 5. The Repository Server registers the local repository with the global repository. choose Managed By the Same Repository Server and select a repository from the local repository list. 4. choose Managed By a Different Repository Server and enter the name of the local repository. Click Close. If you want to register a local repository managed by the same Repository Server. and enter your repository user name and password. Click Register. If you want to register a local repository managed by a different Repository Server. 8. 7. and the port number the Repository Server uses for connections.The Register Repositories dialog box appears. Enter the repository user name and password for the local repository. the host name of the Repository Server. 6. 3.

The repository contacts other repositories in the domain and updates the domain connectivity information. and add a repository configuration. propagate domain connectivity information for the repository. see “Propagating Repository Domain Connection Information” on page 78. For details. 2. If the repository you are moving is in a domain. see “Exporting and Importing Repository Configurations” on page 115. see “Starting the Repository” on page 71. see “Propagating Repository Domain Connection Information” on page 78. For details. 4.Migrating the Repository to a Different Repository Server You can change the Repository Server that manages a repository. Connect to the target Repository Server. move and propagate each repository completely before moving another repository. you must propagate domain connectivity information for the repository. For details. Use the following steps to migrate a repository to a different Repository Server: 1. Remove the repository configuration from the existing Repository Server. Move the repository license file specified in the repository configuration from the previous the Repository Server installation directory to the new Repository Server installation directory. Migrating the Repository to a Different Repository Server 77 . If you want to move multiple repositories in a domain to different Repository Servers. Connect to the Repository Server hosting the repository. and import the configuration into the target Repository Server. see “Connecting to the Repository Server” on page 58 and “Stopping the Repository” on page 72. and stop the repository. see “Removing a Repository Configuration” on page 114. For details on propagating domain connectivity information. Select the repository configuration under the new Repository Server. 6. For details. For details. 5. 3. You can also export the repository configuration from the existing Repository Server. If you want to migrate a repository that is in a domain. and start the repository.

In the Console Tree. Migrate one or more repositories in a domain to another Repository Server. 78 Chapter 3: Managing the Repository . configure repository connectivity. and propagate the connection information for local and global repositories in a specific order. For details on migrating a repository. For details on upgrading a domain. upgrade. you must stop. select the repository for which you want to change the repository connection information. ♦ To update the connection information for a registered repository: 1. Use the Propagate command when you want to perform the following tasks: ♦ Upgrade a domain from a previous version of PowerCenter. 3. start. 2. The Repository Server contacts other registered repositories in the domain and updates the connectivity information for the repository. When you upgrade a domain. see “Upgrading a Repository” in the Installation and Configuration Guide. Enter your repository user name and password. If you want to change the Repository Server managing one or more repositories in a domain. If you want to change the Repository Server that manages a repository. Choose Action-All Tasks-Propagate. see “Migrating the Repository to a Different Repository Server” on page 77.Propagating Repository Domain Connection Information Each local and global repository in a domain contains connectivity information to connect to the other repositories in the domain. and propagate connection information for local and global repositories in a specific order. you must update the connection information for other repositories in the domain. you must configure repository connectivity. start. Click OK.

The port number the machine hosting the repository client application uses to communicate with the repository. Viewing User Connections and Locks 79 . Table 3-5 describes the repository user connection details: Table 3-5. Repository User Connection Details Property User Connection ID Application Hostname Host Address Login Time Last Active Time Remote Host Port Description The user name associated with the connection. The time of the last metadata transaction between the repository client application and the repository. The name of the machine running the application. The time the user connected to the repository. To view user connection details: 1.Viewing User Connections and Locks The Repository Manager and Administration Console allow you to view the connection details and locks details for users connected to a repository. The repository client application associated with the connection. Viewing User Connections You can use the Repository Manager or the Administration Console to view connection details for users and applications connected to the repository. Launch the Repository Manager and connect to the repository. The identification number assigned to the repository connection. Viewing Connection Details in the Repository Manager Use the following procedure to view connection details in the Repository Manager. The TCP/IP address of the machine associated with the connection.

click on the column name.2. select the repository containing the user connections you want to view. Choose Edit-Show User Connections. To sort the connections by column. To sort the connections by column. 80 Chapter 3: Managing the Repository . In the Console Tree. To view user connection details: 1. and select the Connections node. The Administration Console displays the repository user connection details in the Main window: 2. The Repository Connections dialog box appears. Viewing Connection Details in the Administration Console Use the following procedure to view connection details in the Administration Console. 3. click on the column name. Viewing Locks You can view locks and identify residual locks in the Repository Manager or in the Administration Console.

4. To view all locks in the repository. mapping.Table 3-6 describes the object lock information in both the Repository Manager and the Administration Console: Table 3-6. choose Edit-Show locks. The identification number assigned to the repository connection. To show all repository locks: 1. Type of object. In the Repository Manager. The Object Locks dialog box appears. or source. Viewing Locks in the Repository Manager Use the following procedure to view locks in the Repository Manager. Type of lock: in-use. or execute. Workflow Manager. Name of the locked object. To sort your view of the locks by column. write-intent. 3. Name of the machine locking the object. Application locking the object: Designer. To view updated lock information. Time the lock was created. click Refresh. click on the column name. 2. Viewing User Connections and Locks 81 . version. or Repository Manager. Folder in which the locked object is saved. connect to a repository. such as folder. Object Lock Properties Column Name User Connection ID Folder Object Type Object Name Lock Type Lock Time Hostname Application Description User name locking the object.

To sort your view of the locks by column. 82 Chapter 3: Managing the Repository . 2. click on the column name. To show all repository locks: 1. In the Console Tree. Select the Locks node under the repository. select the repository containing the locks you want to view.Viewing Locks in the Administration Console Use the following procedure to view locks in the Administration Console. The Administration Console displays the repository object lock details in the Main window: 3.

The repository has a residual connection when the repository client application or machine is shut down but the connection remains in the repository. select the connection you want to terminate. the Repository Agent detects the residual connection. You can also use the Repository Manager or Administration Console to manually close residual user connections and release residual locks in the repository. The PowerCenter Server opens additional connections to the repository for each Load Manager and DTM process. repository.Closing User Connections and Locks Sometimes. To manually close a connection in the Repository Manager: 1. 3. Warning: Closing an active connection may cause repository inconsistencies. or database machine shuts down improperly. This is called a residual lock. Launch the Repository Manager and connect to the repository. For information on the privileges and permissions to terminate other user connections and unlock objects. it also releases all repository locks associated with the connection. Closing Connections in the Repository Manager Use the following procedure to close connections in the Repository Manager. Close residual connections only. 2. the Repository Server also closes all other connections to the same PowerCenter Server. When the Repository Agent closes the connection. If an object or folder is locked when one of these events occurs. A PowerCenter Client. This can happen in the following situations: ♦ ♦ Network problems occur. the Repository Server does not immediately disconnect a user from the repository. see “Repository Manager Tasks” on page 516. the repository does not release the lock. Closing User Connections and Locks 83 . However. If you close a repository connection to a PowerCenter Server. Informatica recommends that you allow the Repository Agent to automatically detect and release residual locks. You do not need special privileges to terminate connections associated with your repository user name. The Repository Agent closes the residual connection after three times the number of seconds specified for KeepAliveTimeout in the repository configuration. If a system or network problem causes a repository client application to lose connectivity to the repository. In the Repository Connections dialog box. Choose Edit-Show User Connections. A residual repository connection also retains all repository locks associated with the connection. PowerCenter Server.

see “Viewing Locks in the Repository Manager” on page 81. Verify the user is not connected to the repository. The Repository Server closes the connection and releases all locks associated with the connection. 7. You can enter the user name and password associated with the connection. first view the repository object locks to identify the connection ID number associated with the locks you want to release. For more information. Click Close to return to the Repository Manager.4. and select the Connections node. To manually close a connection in the Administration Console: 1. Select the user connection and choose Action-End Connection. 6. To terminate a connection associated with a residual lock. see “Viewing Locks in the Administration Console” on page 82. To terminate a connection associated with a residual lock. 5. 5. 84 Chapter 3: Managing the Repository . or a user name and password with Super User privilege. For more information. select the repository containing the connection you want to release. 2. Click End Connection. 4. In the Console Tree. first view the repository object locks to identify the connection ID number associated with the locks you want to release. Closing Connections in the Administration Console Use the following procedure to close connections in the Administration Console. 3. The Repository Server closes the user connection and releases all locks associated with the connection. The Main window displays the connections details. Verify the user is not connected to the repository. Enter the repository user name and password.

the plug-in directory is \Plugin in the Repository Server installation directory. Stop and disable the repository if it is running. The Repository Server registers plug-ins from the plug-in directory specified in the Repository Server setup program. please consult the plug-in documentation. In the Console Tree. select the Available Packages node. Repository plugins are third-party or other Informatica applications that extend PowerCenter functionality by introducing new repository metadata. Registering a Repository Plug-in Register a repository plug-in to add its functionality to the repository. By default. The Repository Server lists the available plug-ins in the Repository Server plug-in directory. To register a plug-in: 1. You can also update an existing repository plug-in. For installation issues specific to your plug-in. see “Starting and Stopping the Repository” on page 71. Registering and Unregistering Repository Plug-ins 85 . 2. For details.Registering and Unregistering Repository Plug-ins Use the Administration Console to register and remove repository plug-ins.

the Repository Server stops and restarts the repository. Use the following procedure to remove a plug-in from the repository. drill down to the Registered Packages node in the Console Tree. You might choose to do this when you upgrade the plug-in to a new version. and connect to the Repository Server. Unregistering a Repository Plug-in When you unregister a repository plug-in. Verify that all users are disconnected from the repository before you unregister a plug-in. select the repository in which to register the plug-in. 2.3. You can choose to update a plug-in already registered in the repository. 3. 6. Enter your repository user name and password. Select the plug-in to register. For the repository with the registered package. With the Registered Packages node selected. Click OK. 4. To unregister a plug-in: 1. Open the Administration Console. 5. The Repository Server registers the plug-in with the repository. and choose Action-Register. 86 Chapter 3: Managing the Repository . In the Register Security Module dialog box. You can view the registration process in the Activity Log. right-click the package you want to unregister in the Main window.

Registering and Unregistering Repository Plug-ins 87 . 5. Click OK. Enter your repository user name and password. Choose Unregister. 6.4.

Registering and Unregistering LDAP Security Modules
You can register and unregister an LDAP security module by using the Repository Server Administration Console or the appropriate pmrepagent commands.

Registering an LDAP Security Module
If you are using an LDAP directory to maintain users and passwords for a repository, you must register and configure the authentication module with the repository. You can register the authentication module by using the Repository Server Administration Console, or by using the pmrepagent Registerplugin command. For information on the Registerplugin command, see “Registering a Plug-in (Registerplugin)” on page 482. You can configure the authentication module using the Administration Console, or you can update the configuration file with a text editor. When you install the Repository Server on Windows, the installation places an LDAP external module library file and an associated XML file in the Repository Server security folder.
C:\repserver\bin\security\ldapauthen.dll C:\repserver\bin\security\ldap_authen.xml

The ldap_authen.xml file displays in the Available Packages folder of the Repository Server Administration Console. This XML file specifies the security module. The following is a sample LDAP XML file:
<?xml version="1.0" encoding="us-ascii"?> <POWERMART> <REPOSITORY CODEPAGE ="us-ascii"> <PLUGIN ID ="3014" NAME ="LDAPAuthenPlugin" VERSION ="1.0.0" VENDORID ="1" VENDORNAME ="Informatica" DESCRIPTION ="LDAP Authentication Security module">

<TEMPLATE ID="400100" NAME="LDAP Authentication Module" TYPE="AUTHENTICATIONMODULE" DESCRIPTION="Authentication module implemented using LDAP" COMPONENTVERSION="1.0.0">

<LIBRARY NAME="ldapauthen.dll" OSTYPE="NT" TYPE="REPAGENT"/>

88

Chapter 3: Managing the Repository

</TEMPLATE> </PLUGIN> </REPOSITORY> </POWERMART>

The NAME attribute in the LIBRARY element specifies the .dll file that implements the authentication. The OSTYPE attribute specifies the operating system running the library file. The TYPE should be REPAGENT.
Note: If you back up and restore a repository to a machine with a different operating system,

the restore process might unregister the external security module if it cannot find the security library on the new platform. Change the NAME attribute and the OSTYPE in the XML file to use it on the new machine.

Registering the Authentication Module
Use the Repository Server Administration Console to select and register the LDAP authentication module for a repository server.
To register an LDAP security module using the Administration Console: 1. 2. 3.

Connect to the Repository Server. Stop and disable the repository if it is running. For details, see “Starting and Stopping the Repository” on page 71. Open the Available Packages node in the Console Tree.

Registering and Unregistering LDAP Security Modules

89

The Repository Server lists the available plug-ins.

4.

Select the Authentication Module, and choose Action-Register.

90

Chapter 3: Managing the Repository

The Register Security Module dialog box displays.

Table 3-7 describes the information to enter in the Register Security Module dialog box:.
Table 3-7. Register Security Module Options Field Repository Update Security Module Registration Username Password External Directory Login Password Enable CRC Description Select the repository in which to register the module. Check this box if you are updating an existing security module. Leave it blank if this is the first time you are registering this module. Enter a user name that has Repository administrator privileges. You must have administrator privileges to register the security module. Enter the password for the Repository administrator. Enter a valid external login name for the module to use to connect to the external directory service. Enter the correct password for the external login name. Select Enable CRC to enable a runtime check the integrity of the authentication module library. This option stores the CRC of the plug-in library in the Repository. When the Repository Agent loads the authentication module, it checks the library against the CRC.

5.

Click OK. The Repository Server registers the plug-in with the repository. The LDAP security module displays under the repository in the Console Tree.
Registering and Unregistering LDAP Security Modules 91

Configuring the LDAP Authentication Module
When you use the LDAP authentication module you must configure it for the repository by updating the ldap_config.txt configuration file. This file resides in the bin\security folder in the Repository Server install directory. You can manually update this file, or you can use the Administration Console to update it.
To update the configuration using the Administration Console: 1. 2.

Open the Repository Server Administration Console and connect to the Repository server. Double-click the Available Packages node in the Navigator. The Repository Server displays the available plug-ins.

3.

Right-click the ldap_authen.xml authentication module and choose Configure. The Configure LDAP Authentication Module dialog box displays. You need to update both tabs to set the configuration.

4.

Enter LDAP server options.

92

Chapter 3: Managing the Repository

Table 3-8 describes the LDAP server configuration file options:
Table 3-8. LDAP Server Configuration Options Field Server name Port Search Base Scope Description The name of the LDAP server. Port number to connect to the LDAP server. The port is usually 636 for SSL enabled servers, or 389 for non-SSL enabled servers. Distinguished name (DN) of the entry that serves as the starting point to search for user names. Scope of the user search. Options are: - base. Search the entry identified by SearchBase. - onelevel. Search all entries one level beneath the SearchBase entry. - subtree. Search the entire subtree at all levels beneath the SearchBase entry. Distinguished name (DN) for the principal user. Leave this blank for anonymous login. Password for the principal user. Leave this blank for anonymous login.

Principal User Name Principal User Password 5.

Click the Login Properties Tab to enter login properties and SSL information.

Registering and Unregistering LDAP Security Modules

93

Table 3-9 describes the Login Properties tab options:
Table 3-9. LDAP Login Properties Options Field Login Attribute Login Filter UseSSL Certificate Database Description The directory attribute that contains login names. Condition to filter results for user search. The filter can specify attribute types, assertion values, and matching criteria. Indicates if the LDAP server uses SSL. The path to the certificate database if you are using SSL. Click the browse button to find and select the certificate file.

Example
The following example shows ldap_config.txt options for a Microsoft Active Directory server running on server6. When a user connects to the repository, the authentication module binds as the principal user JSmith to the LDAP server server6. The LDAP server searches for users within the search base starting at the organizational unit TestUsers, and searches down the subtree. It checks objects in the “person” object class. The server searches for the object with the sAMAccountName equal to the user’s login name.
serverName=server6 port=389 principal=CN=JSmith credential=testpasswd searchBase=ou=TestUsers, dc=informatica, dc=com scope=subtree loginAttr=sAMAccountName loginFilter=(objectclass=person) useSSL=no certDB=

The following example shows ldap_config.txt options for a SunONE directory server running on port 503 on server mars. The principal user and credential options are blank, which indicates that the users access the LDAP server through anonymous login.
serverName=mars port=503 principal= credential= searchBase=ou=people, dc=informatica, dc=com scope=subtree loginAttr=uid

94

Chapter 3: Managing the Repository

loginFilter=(objectclass=person) useSSL=no certDB=

Unregistering an LDAP Security Module
You can unregister the LDAP authentication module by using the Repository Server Administration Console or by using the pmrepagent Unregisterplugin command. For information on the Unregisterplugin command, see “Unregistering Plug-ins (Unregisterplugin)” on page 487. If you unregister the external security module, PowerCenter switches to repository authentication mode. All user passwords reset to the values in the repository instead of the values in the external directory. When you unregister the security module you lose the mapping between the repository user names and the external security login names unless you specify to keep the user name/external login mapping. If you keep the mapping, you can reuse it later if you register a new security module.
Note: Although you can save the associations between external logins and repository user

names, the Repository Manager does not display the external logins while running under repository user authentication. You must specify a new password for the administrator when you unregister the security module. This ensures that you can access the repository once the external security directory is unregistered. You should unregister the LDAP package when no users are accessing the repository. When you unregister the package you have to restart the repository. All users are disconnected.
To unregister an LDAP package: 1. 2.

Open the Repository Server Administration Console and connect to the Repository Server. Double-click the Available Packages node in the Navigator. The Repository Server displays the available plug-ins.

3.

Right-click the ldap_authen.xml authentication module and choose Unregister.

Registering and Unregistering LDAP Security Modules

95

The Unregister Package dialog box displays.

4.

Enter the LDAP Login properties shown in Table 3-10:
Table 3-10. LDAP Login Properties Options Field Administrator Username Password New Administrator Password Confirm Password Keep Username/ External Login Mapping Description The external login name for the repository administrator. The external login password for the repository administrator. The new password for the administrator to use with repository security after unregistering the external security module. Confirms the new password for the administrator. Keeps the mapping between the external user names and the login names in the repository. You can reuse this mapping if you register another external security module.

96

Chapter 3: Managing the Repository

Reading the Repository Log Files
The Repository Server and Repository Agent write error and operation messages to separate log files. The Repository Server log file contains information about managing the Repository Agents for all of the repositories configured to run on the Repository Server. The Repository Agent log file contains information about the operation of the Repository Agent managing each repository. The Repository Server and Repository Agent use a common format to log messages. Each message contains a log file code and process identification number used for troubleshooting purposes. The Repository Server and Repository Agent continuously append error and information messages to the log files. Depending on the number of repository transactions and the message severity level configured for the repository, the log files can grow to contain a large number of messages. Informatica recommends periodically deleting the Repository Server and Repository Agent log files and writing only higher severity level messages to the log files for normal operations.

Log File Codes
You can use the Repository Server and Repository Agent log files to determine the cause of repository problems. To troubleshoot repository problems, locate the relevant log file codes and text prefixes in the repository log file. Table 3-11 describes the codes that can appear in the Repository Server and Repository Agent log files:
Table 3-11. Repository Log Codes Log Code CNX LKM OBJM REP RCORE SF Description Messages related to connections to repository client applications. Messages related to obtaining and releasing repository object locks. Messages related to fetching, inserting, or updating repository objects. Messages related to communication between the Repository Agent and Repository Server. Messages related to Repository Server internal functions. Messages related to Repository Server status and management operations.

Process Identification
The Repository Server and Repository Agent append Windows or UNIX process identification numbers to the prefix of each message it writes to the Repository Server or Repository Agent log file. The process identification number helps you identify messages from a specific Repository Server or Repository Agent if you configure multiple repositories to write log messages to the same file.
Reading the Repository Log Files 97

You can verify the process ID number for the Repository Agent by checking the repository status. The process identification is printed before the message text in the repository log. The following example illustrates a connection message from a Repository Agent using process ID number 2548:
INFO : CNX_53037 [Thu Jul 15 10:45:44 2004]: (476|2548) Thread closing connection to the client.

Repository Server Log
By default, the Repository Server writes messages to the file pmrepserver.log. You can specify a unique log file name by configuring the Output to File option in the Windows Repository Server setup program. You can also configure the Windows Repository Server to log messages in the Windows event log. To view Repository Server messages in the Windows event log, you must be a system administrator on the machine hosting the Repository Server. You can specify a unique log file name on UNIX by configuring the Repository Server LogFileName option.

Repository Server Message Severity Level
You can configure the Repository Server to write the following levels of messages in the Repository Server log:
♦ ♦

Error. Indicates the repository failed to perform an operation or respond to a request from a repository client application. Error messages have the highest severity level. Warning. Indicates the Repository Server is performing an operation that may cause an error. This can cause repository inconsistencies. Warning messages have the second highest severity level. Information. Indicates the Repository Server is performing an operation that does not indicate errors or problems. Information messages have the third lowest severity level. Tracing. Indicates Repository Server operations at a more specific level than Information. Tracing messages are generally record message sizes. Trace messages have the second lowest severity level. Debug. Indicates Repository Server operations at the thread level. Debug messages generally record the success or failure of individual internal Repository Server operations. Debug messages have the lowest severity level.

♦ ♦

When you configure the repository to write messages of a specific severity level to the Repository Server log file, the Repository Server also writes all messages of greater severity to the log file. For example, if you configure the Repository Server to write Warning severity level messages to the log file, the Repository Server also writes Error severity level messages to the log file.

98

Chapter 3: Managing the Repository

INFO : REP_51005 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized database connection information. you must view the text of the message. INFO : SF_34002 [Fri Jul 16 09:16:46 2004] : (1324|1452) Server starting up. INFO : REP_51003 [Fri Jul 16 09:37:33 2004] : (1396|1952) Copyright (c) Informatica Corporation 2000-2001 INFO : REP_51004 [Fri Jul 16 09:37:33 2004] : (1396|1952) Informatica Repository Agent starting up. the messages appear in the Application Log component of the Windows Event Viewer. INFO : REP_51006 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized configuration information. However. INFO : REP_51036 [Fri Jul 16 09:37:37 2004] : (1396|1952) Error logging enabled INFO : REP_51035 [Fri Jul 16 09:37:37 2004] : (1396|1952) Repository agent connected to repository PRODUCTION. Database User : admin1 INFO : REP_51009 [Fri Jul 16 09:37:37 2004] : (1396|1952) Informatica repository agent ready to receive request on port 5003. Sample Application Log If you configure the Repository Server to log messages in the event log. INFO : REP_51007 [Fri Jul 16 09:37:33 2004] : (1396|1952) Repository runtime manager initialized. INFO : SF_34003 [Fri Jul 16 09:16:47 2004] : (1324|1452) Server initialization completed.When you configure the Repository Server to write Trace or Debug severity level messages to the Repository Server log file. Repository Server Log File Sample The following sample is an excerpt from a Repository Server log file that illustrates log file codes: INFO : SF_34058 [Fri Jul 16 09:16:46 2004] : (1324|1452) Service started. INFO : REP_51008 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized request dispatcher. INFO : SF_34012 : (1324|1452) Opened Server Port [5001] to listen for client connections. Database : penguin@production. since some message codes are embedded within other codes. Informatica recommends setting the Severity Level option in the Repository Server configuration to Warning or Error unless you are troubleshooting a problem with the Repository Server. Reading the Repository Log Files 99 . the file can grow to contain a large number of entries. Messages sent from the Repository Server display PmRepServer in the Source column. to ensure you are viewing the true message code.

Application Log Message Detail Repository Agent Log File By default.Figure 3-4 shows a sample Windows Event Viewer: Figure 3-4.log. 100 Chapter 3: Managing the Repository . You can view the repository log file using a text editor program such as Windows Notepad. Event Viewer Application Log Message Figure 3-5 shows the text of the message when you double-click it: Figure 3-5. You can specify a unique log file name for individual repositories by configuring the LogFileName option when you create or edit a repository configuration. You can write repository log messages from multiple repositories to the same log file. the Repository Agent writes messages to the file pmrepagent.

Indicates repository operations at a more specific level than Information. Warning. Warning messages have the second highest severity level. Repository Agent Message Severity Level You can configure the repository to write the following levels of messages in the Repository Agent log: ♦ ♦ Error. INFO : REP_51008 [Fri Jul 16 10:46:16 2004] : (2280|2256) Initialized request dispatcher.You can also configure the Repository Agent to write messages of different severity levels to the log file depending on the value of the ErrorSeverityLevel configuration option when you create or edit a repository configuration. The Repository Agent also writes all messages of greater severity to the log file. This can cause repository inconsistencies or cause repository client applications to report errors. INFO : REP_51036 [Fri Jul 16 10:46:17 2004] : (2280|2256) Error logging enabled . When you configure the repository to write Information or Trace severity level messages to the repository log file. Trace messages have the lowest severity level. Indicates the repository is performing an operation that may cause an error in a repository client application. Reading the Repository Log Files 101 . INFO : REP_51006 [Fri Jul 16 10:46:16 2004] : (2280|2256) Initialized configuration information. Trace messages are generally record message sizes and locking operations for specific objects in the repository. the Repository Agent writes a warning message to the Repository Agent log if you stop the repository when it has active connections. if you configure the repository to write Warning severity level messages to the log file. Information. Indicates the repository failed to perform an operation or respond to a request from a repository client application. the file can grow to contain a large number of entries. ♦ ♦ When you configure the repository to write messages of a specific severity level to the log file. Information messages have the second lowest severity level. Trace. Informatica recommends setting the ErrorSeverityLevel option in the repository configuration to Warning or Error unless you are troubleshooting a problem with the repository. For example. Indicates the repository is performing an operation that does not indicate errors or problems with the repository. Repository Agent Log File Sample The following sample is an excerpt from a Repository Agent log file that illustrates log file codes and severity level messages: INFO : REP_51007 [Fri Jul 16 10:46:16 2004] : (2280|2256) Repository runtime manager initialized. Error messages have the highest severity level. the Repository Agent also writes Error severity level messages to the log file. For example.

. WARNING: CNX_53056 [Wed Jul 14 13:21:51 2004] : (2588|2608) Shutting down the repository server with 3 connection(s) active.173). ..1.informatica. TRACE : REP_51047 [Fri Jul 16 10:46:17 2004] : (2280|1980) Sending message of size 278 bytes. INFO : CNX_53039 [Fri Jul 16 10:46:17 2004] : (2280|1980) Received TCP connection from host p153894.72. .com (10. 102 Chapter 3: Managing the Repository . . ERROR : CNX_53021 [Wed Jul 14 13:20:54 2004] : (2588|2336) Received an invalid request. port 2706.

119 103 . 105 Editing a Repository Configuration. 114 Exporting and Importing Repository Configurations. 113 Removing a Repository Configuration. 116 Working with PowerCenter Licenses. 104 Adding a Repository Configuration.Chapter 4 Configuring the Repository This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 115 Creating or Promoting a Repository.

Use the Administration Console to perform the following tasks: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ 104 Chapter 4: Configuring the Repository . This includes repository configuration information. Import repository configurations. Remove repository configurations. When you connect to the repository. Network. Configuration. ♦ Licenses. Enable version control for a repository. This displays the license key information stored in the repository license file. such as refresh interval and maximum connections. the Repository Server starts the repository using the stored connection information. The Repository Server uses this information to connect to the repository database. Create a repository. Database connection. Edit repository license files. You configure this file on the following tabs of the New Repository dialog box: ♦ ♦ ♦ ♦ General. Export repository configurations. You can also update the license keys in the license file. such as repository name and version control. This includes information. Add repository configurations. Edit repository configurations.Overview Each repository managed by the Repository Server contains connection information saved in a configuration file. Promote a local repository to a global repository. This includes receive and send timeout limits.

Upgrade an existing repository from an earlier version of PowerCenter or PowerMart. For more information. In the Console Tree. you can perform the following tasks: ♦ ♦ ♦ ♦ Create a repository in a database. and adds the repository name to the Console Tree. Adding a Repository Configuration 105 . displaying the General tab. select the Repositories node and choose Action-New Repository. Change the Repository Server managing the repository. For more information. see “Upgrading a Repository” in the Installation and Configuration Guide. the Administration Console creates a configuration file in the Repository Server configuration directory. see “Restoring a Repository” on page 67. see “Migrating the Repository to a Different Repository Server” on page 77. When you add a repository configuration. Restore a repository from a backup file.Adding a Repository Configuration Use the Administration Console to add repository configurations to the Repository Server. For more information. The New Repository dialog box appears. For more information. When you add a repository configuration. see “Creating a Repository” on page 116. To add a repository configuration: 1.

Add the license key on the Licenses tab. Only enable this option if you are sure you want to create a global repository. 106 Chapter 4: Configuring the Repository . Creates a versioned repository. Global Data Repository Optional Enable Version Control Optional Creation Mode Required 3. Choose to create a new repository based on this repository configuration. You can promote an existing repository to a versioned repository later. you must have the Team-Based Development option license key in the repository license file. Creates a global repository. Table 4-1 describes the options available on the General tab: Table 4-1.2. Only enable this option if you are sure you want to create a versioned repository. To enable a repository for version control. Once created. or to add the repository configuration without creating a repository in the database. you cannot change a global repository to a local repository. Do not use the following characters when creating a repository name: \ / : * ? < > " | . Click the Database Connection tab. You can promote an existing local repository to a global repository later. Enter general information about the repository. New Repository .General Tab Option Name Required/ Optional Required Description The name of the repository.

servername@dbname for Microsoft SQL Server. Note that for most databases. You cannot use spaces in the tablespace name. ConnectString Required DBUser DBPassword Trusted Connection Required Required Optional TablespaceName Optional Adding a Repository Configuration 107 . For a list of connect string syntax. Must be in 7-bit ASCII. The native connect string the Repository Server uses to access the database containing the repository. the Repository Server uses Windows authentication to access the Microsoft SQL Server database. The user name that starts the Repository Server must be a valid Windows user with access to the Microsoft SQL Server database. but a native connect string (for example. The account for the database containing the repository. or dbname. New Repository . the Repository Server creates all repository tables in the same tablespace. If selected. To improve repository performance on IBM DB2 EEE repositories. Set up this account using the appropriate database client tools. The repository database password corresponding to the database user. The repository code page. this is not an ODBC data source name.world for Oracle).Table 4-2 describes the options available on the Database Connection tab: Table 4-2. The Repository Server uses the character set encoded in the repository code page when writing data to the repository. When you specify the tablespace name. use the ODBC data source name. specify a tablespace name with one node. For more information on using the tablespace names. For Teradata databases. see “Creating a Repository” in the Installation and Configuration Guide. see Table 16-1 on page 405.Database Connection Tab Option Database Type CodePage Required/ Optional Required Required Description The type of database storing the repository. The tablespace name for IBM DB2 repositories.

Table 4-3 describes the options available on the Network tab: Table 4-3. Default is 3. 108 Chapter 4: Configuring the Repository . New Repository .Network Tab Option MessageReceiveTimeout MessageSendTimeout Required/ Optional Required Required Description Number of seconds the Repository Server waits to receive a message from a client application before timing out. 5. Number of seconds the Repository Server waits while sending a message to a client application before timing out. Default is 3.4. Enter the network information. Click the Network tab.

New Repository . INFO. Click the Configuration tab. . Writes ERROR code messages to the log file.Trace.Information. .Configuration Tab Option MaximumConnections ErrorSeverityLevel Required/ Optional Required Required Description The maximum number of connections the repository accepts from repository client applications. Writes INFO. If the date display format is invalid. the Repository Server uses the PowerCenter default date display format. and ERROR code messages to the log file. Default is 200. Table 4-4 describes the options available on the Configuration tab: Table 4-4. Writes TRACE. . The Repository Server validates the date display format and uses it when writing entries to the repository log file. Informatica recommends using the Trace and Information logging levels for troubleshooting purposes only. The level of error messages written to the Repository Agent log file.Error. Enter the repository configuration information. 7. DateDisplayFormat Required Adding a Repository Configuration 109 .Warning. and ERROR code messages to the log file. WARNING. Specify one of the following message levels: .6. Writes WARNING and ERROR code messages to the log file. WARNING. The default date display format is DY MON DD HH 24:MI:SS YYYY.

the Repository Agent does not timeout or close connections.log file in the Repository Server installation/bin directory. The first time you click the Licenses tab when you create a repository configuration. The number of rows to fetch each time an array database operation. Default is 500. Default is 60. Click the Licenses tab. The path and name of the Repository Agent log file. The number of seconds the Repository Agent waits to establish a connection to the repository database before timing out. Default is 100. The number of seconds the Repository Agent waits for a response from a repository client application before closing the connection. Logged to pmsecaudit.log. Default is 10. and permissions. Minimum is 30. For more information. If you specify the same log file name for multiple repositories. The default is pmrepagent. Select to track changes made to users. is issued. If you set this option to 0. Minimum is 20. The maximum number of locks the repository places on metadata objects. The maximum number of connections to the repository database that the Repository Agent can establish.Configuration Tab Option DynamicConfig RefreshInterval ThreadWaitTimeout Required/ Optional Required Required Description The number of seconds the repository waits to poll for updates to its configuration. If the Repository Agent receives no response from the repository client application in three times the number of specified seconds. such as insert or fetch. Default is 30 seconds. groups.000. Default is 60. Requires users to add check in comments. the Administration Console displays a messaging informing you that the license file is empty. New Repository .<repository_name>. the Repository Agent writes messages for each repository to the same file. 110 Chapter 4: Configuring the Repository . The number of seconds the master thread running repository processes waits for process threads to stop before stopping. If the Repository Agent tries to establish more connections than specified for DatabasePoolSize. MaximumLocks LogFileName Required Required KeepAliveTimeout Required DatabasePoolSize Required DatabaseConnection Timeout CheckinCommentsRequired SecurityAuditTrail Required Optional Optional DatabaseArrayOperationSize Optional 8.Table 4-4. privileges. the Repository Agent closes the connection. it times out the connection attempt after the number of seconds specified for DatabaseConnectionTimeout. see “Repository Security” on page 125. Default is 50.

♦ ♦ When you enter a valid license key string. PowerCenter only adds option and connectivity license keys to a license file when the license file contains a valid product license key. The license file name is repository_name-es. If you have any option or connectivity license key. when you use special characters in the repository name.lic and is located in the Repository Server installation directory. However. For more information about how the Administration Console creates repository file names. enter the key in the License Key field. You can use the Licenses tab to update and view the repository license file. Displays the license key repository type. You can also add license keys at any time. the Administration Console informs you it updated the license file successfully. Displays the repository license file name. Displays the license keys and their properties in the license file. 11. Do this for every option and connectivity license key. of the other license keys in the license file. Add the product license key in the License Key field and click Update. either production or development. The file is located in the Repository Server installation directory.9. The Administration Console does not add invalid or expired license keys or license keys that already exist in the license file. either development or production. and click Update. see “Repository License Files” on page 120. the Administration Console converts them to an underscore and a letter. PowerCenter adds the product license key to the license file. Adding a Repository Configuration 111 . Click OK to close the message dialog box. Consider the following rules and guidelines when you add license keys: ♦ You must add the product license key to the license file before you enter any option or connectivity license key. 10. The option and connectivity license keys you add must match the repository type. Add a license key to the repository license file.

see “Working with PowerCenter Licenses” on page 119. you can specify any compatible code page.For more information on licenses. Click OK to save the configuration options. the Repository Server begins building the repository in the database. the repository appears in the Console Tree under the Repositories node. The Administration Console saves the repository configuration and adds it to the Repository Server configuration directory. 12. 112 Chapter 4: Configuring the Repository . Tip: To change the repository code page after you create the repository. you can back it up and restore it. When the Repository Server finishes creating the repository. When you restore a repository. If you select the Create all Database Tables for This Repository option on the General tab.

Edit and apply changes in the Properties dialog box. Disable the repository to prevent other users or applications from starting it. 2. Stop the repository. Note: You cannot change the tablespace name in the repository configuration after you enter it. Start the repository. the Repository Server updates changes to the configuration at an interval specified in the DynamicConfigRefreshInterval configuration option. select the repository in the Console Tree and choose Action-Properties. remove the repository configuration and create a new one with the correct tablespace name. Edit the repository configuration. see “Adding a Repository Configuration” on page 105. Editing a Repository Configuration 113 . The Repository Server can update the following configuration parameters while the repository is running: ♦ ♦ ♦ ♦ MaximumConnections MaximumLocks ErrorSeverityLevel DatabasePoolSize Changes to other repository configuration parameters take effect the next time you start the repository. If you edit the configuration while the repository is running. If you create a repository configuration with a wrong or an invalid tablespace name. Enable the repository to allow other users or applications to start it.Editing a Repository Configuration You can edit a repository configuration at any time. Use the following steps if you want changes to the repository configuration to take effect immediately: 1. 5. 4. 3. For details on the options in the Properties dialog box. To edit a repository configuration.

Note: If you select Delete the Repository. 114 Chapter 4: Configuring the Repository . For more information. 4. For details on deleting the repository from the database. see “Disabling the Repository” on page 73. the Administration Console removes the repository from the Console Tree. and choose Action-Delete. 2.Removing a Repository Configuration You can use the Administration Console to remove a repository configuration. In the Console Tree. This instructs the Repository Server to remove the repository configuration only. Choose to remove the repository from the server cache. You might want to remove a repository configuration if you migrate the repository to a different Repository Server and no longer want to use the old configuration to run the repository. It does not remove the repository license file. The tables and metadata remain in the database. Stop the repository. see “Deleting a Repository” on page 64. For details. The Repository Server removes the repository configuration. Click OK. To remove a repository configuration: 1. you remove the configuration only. see “Stopping the Repository” on page 72. the Repository Server deletes the repository from the database. and deletes the configuration file from the Repository Server configuration directory. Disable the repository to prevent other users or applications from starting it. For details. 3. select the repository. see “Deleting a Repository” on page 64. Remove the repository configuration. The Deleting a Repository dialog box appears. When you remove the repository configuration. When you remove the repository configuration. 5.

2.cfg file. You can export and import configurations when you want move the repository to a different Repository Server. and click OK. 3. Importing a Repository Configuration Use the following procedure to import a repository configuration from a file. the Administration Console saves the file in the Repository Server configuration directory. select the repository from which you want to export the configuration information. Exporting a Repository Configuration Use the following procedure to export a repository configuration to a file. it displays the imported repository configuration under the Repositories node in the Console Tree. By default. To export a repository configuration: 1. You can import a repository configuration from a . If you want to export and import the repository registry information stored in the client registry. When the Repository Server imports a configuration file. Choose Action-Import Repository Connection. The Repository Server imports the configuration information and creates a repository entry under the Repositories node in the Console Tree. Locate the repository configuration file you want to import. In the Console Tree. and choose Action-All Tasks-Export Connection. select the Repositories node. In the Console Tree. see “Exporting/Importing Repository Connection Information” on page 32. To import a repository configuration: 1.Exporting and Importing Repository Configurations You can export a repository configuration to a . The Export Repository Configuration to a File dialog box appears. 3.cfg file. Enter a name and location to store the export configuration file. 2. Exporting and Importing Repository Configurations 115 . Click OK.

Before you can create a repository. The machine running the repository database system must have a network connection to the machine running the Repository Server. the database administrator must define the database on a single node. see “Creating a Repository” in the Installation and Configuration Guide. the create operation fails. You can promote an existing repository to a global repository. The password must be in 7-bit ASCII. After promoting a repository. you must complete the following steps: 1. This login must have database permissions to create the repository. For more information. or upgrade a Sybase repository. you must have the following information available: ♦ 116 Chapter 4: Configuring the Repository . you can register local repositories to create a domain. In the new repository.Creating or Promoting a Repository You can create a repository in a database based on a repository configuration. You must add the Team-Based Development option license key to the repository license file before you can enable version control. Once you enable version control for a repository you cannot disable it. to protect your repository and improve performance. 2. consider keeping it separate from overloaded machines. verify the repository database system meets the following requirements: ♦ ♦ ♦ Windows or UNIX operating system 100-150 MB disk space 128 MB RAM Database user name and password. you cannot change it to a local or standalone repository. this login becomes a default user with full privileges in the repository. You must delete the existing repository in the target database before creating the new repository. Tip: You can optimize repository performance on IBM DB2 EEE databases when you store an Informatica repository in a single-node tablespace. However. Creating a Repository Before you create a repository. You can create the repository on any supported database system. When you create a repository. PowerCenter also allows you to enable version control for a new or existing repository. If you create a repository on a database with an existing repository. Setting this option changes the default null type of the column to null in compliance with the SQL standard. The repository database name must be unique. Create and configure the database to contain the repository. If you have the Team-Based Development option. When setting up an IBM DB2 EEE database. Note: If you want to create. restore. set allow nulls by default to TRUE at the database level. Once you promote a repository to a global repository. Add or import a repository configuration.

Tip: To change the repository code page after you create the repository. To promote a repository: 1. see “PowerCenter Domains” on page 13. For details on global and local repositories. Creating or Promoting a Repository 117 . To create a repository: 1. Contains the character set of the data in the repository. For more information on licenses. see “Adding a Repository Configuration” on page 105.♦ Code page. Promoting a PowerCenter Repository After you create a local repository. select a repository configuration under the Repositories node. select the repository you want to promote. You must delete the existing repository in the target database before creating the new repository. However. see “Globalization Overview” in the Installation and Configuration Guide. it starts the Repository Agent. Before promoting a repository to a global repository. the Repository Server does not create the repository. The repository code page must be compatible with the PowerCenter Server and Client code pages. you cannot change the code page. For more information. you can specify a compatible code page. When you restore a repository. see “Creating a Folder” on page 171. In the Console Tree. When registering local repositories with a global repository. once you create a global repository. the global and local repository code pages must be compatible. 2. License keys. Note: If a repository already exists in the database. 2. ♦ Note: You can create a repository after you add a repository configuration. You can see the progress in the Activity Log. Choose Action-Properties. The Administration Console allows you to select from a list of code pages compatible with the PowerCenter Client code page. The Repository Server begins building the repository. For more information. you can promote it to a global repository. see “Working with PowerCenter Licenses” on page 119. For details. Once specified. In the Console Tree. You must start the repository before you can promote it to a global repository. Verify the repository license file contains a valid product license key and any connectivity and option license key. Choose Action-Create. After creating a repository. you cannot change it to a local repository. you can back up and restore it. When the Repository Server finishes creating the repository. you must create at least one folder before you can create objects in the Designer or Workflow Manager. make sure the repository code page is compatible with each local repository you want to register.

queries. In the Console Tree. The Administrator Console displays the Login Information dialog box. 118 Chapter 4: Configuring the Repository . The Repository Server enables version control for the repository and stops and restarts the repository for the changes to take effect. Version control allows you to maintain multiple versions of an object. and deployment groups to associate and copy specific groups of objects from one repository to another. Enter your repository user name and password and click OK. and track changes. In the Properties dialog box. The Repository Server promotes the repository to a global repository. When you enable version control for a repository. For more information on working with versioned objects and versioned object properties. select the Supports Version Control option. Once you enable version control for a repository. To enable version control for a repository: 1. 2. 4. 3. the repository assigns all versioned objects version number 1 and each object has an active status. you cannot disable it. Note: To enable a repository for version control. see “Grouping Versioned Objects” on page 217. you must have the Team-Based Development option license key in the repository license file. select the Global Data Repository option. control development on the object. Choose Action-Properties. queries. 4. In the Properties dialog box. Enter your repository user name and password. select the repository for which you want to enable version control. you can enable it for version control. and deployment groups. and click OK. You can also use labels. For more information on using labels. The Administrator Console displays the Login Information dialog box. Enabling Version Control After you create a repository. see “Working with Versioned Objects” on page 199. You must start the repository before you can enable version control.3.

Partitioning. You must update the PowerCenter Server license file with option and connectivity license keys after you install the product. You enter a product license key when you install the PowerCenter Server and Repository Server. PowerCenter provides license keys based on the type of repository you have. Also. PowerCenter stores the license keys in a license file. A license file can contain multiple option license keys. Informatica gives you one license key string that contains information for multiple connectivity licenses. option. Connectivity. You must have this license key when you install the PowerCenter Server and Repository Server. For more information about updating a license file. such as PowerCenter Connect for SAP R/3. They also allow you to access PowerCenter Connect sources. When you create or upgrade a repository. This license key allows you to start the PowerCenter Server and the Repository Server and create repositories. Option. and Server Grid. License Key Types PowerCenter provides the following types of license keys: ♦ Product. The repository type applies to all license keys and license files. you must add the product. Informatica gives one product license key for each product you purchase. ♦ ♦ When you buy multiple connectivity license keys at the same time. A license file can contain multiple connectivity license keys. development or production. Informatica gives you one license key string that contains information for multiple connectivity licenses. These license keys allow you to access options. Note: You can update license files with option and connectivity license keys at any time. License Key Repository Types PowerCenter provides license keys based on the type of repository you have. and connectivity license keys to the license file. when you buy multiple option license keys at the same time.Working with PowerCenter Licenses Informatica provides license keys for each PowerCenter Server and each repository. such as Team-Based Development. PowerCenter provides different license key types. you can use the set of license keys for all repositories and PowerCenter Servers in your development environment. Working with PowerCenter Licenses 119 . When you purchase development license keys. However. see “Managing License Files” on page 122. These license keys allow you to access sources and targets. either a PowerCenter Server license file or a repository license file. development or production: ♦ Development. Use development license keys in a development environment. The installation program creates a license file in the PowerCenter Server installation directory to store the product license key you enter.

the Administration Console ignores all existing license keys and adds the product license key you specify. PowerCenter Server license file.♦ Production. such as the Designer. Informatica gives you a set of license keys for each repository you buy. You lose the ability to use those option and connectivity license keys. + = ~ ` Characters Used in Repository License File Name _0 _A _B _C _D _E _F 120 Chapter 4: Configuring the Repository . or restore a repository.lic. Repository License Files PowerCenter creates a repository license file for every repository configuration you create in the Administration Console. However. When you mix development and production license keys. Use production license keys in a production environment. the Administration Console converts them to an underscore and a letter. when you use special characters in the repository name. The license file necessary to create. You cannot change the repository license file name. copy. Note: You do not need a license file to start a PowerCenter Client tool. run. Use one set of license keys for one repository and one PowerCenter Server only. You cannot mix development and production license keys in a license file. do not update a license file containing development license keys with a production product license key. The license file is repository_name-es. When you purchase production license keys. For example. Note: Do not update a license file with a product key of a different repository type. the PowerCenter Server or repository fail to start. and it is located in the Repository Server installation directory. When you do this. License File Types PowerCenter uses the following types of license files: ♦ ♦ Repository license file. The license file necessary to run the PowerCenter Server. Table 4-5 describes how the Administration Console converts special characters in repository license file names: Table 4-5. Converting Special Characters in Repository License File Names Special Character in Repository Name _ .

see “Adding a Repository Configuration” on page 105. the Repository Server verifies that the license file exists in the Repository Server installation directory. When you start a repository. add them to the license file after you add the product license key. If you have option or connectivity license keys. it fails to start the repository. : / ? . Working with PowerCenter Licenses 121 . For more information on adding license keys to the repository license file. If the Repository Server cannot find the license file. Converting Special Characters in Repository License File Names Special Character in Repository Name ! % ^ & * ( ) [ ] { } ' " . < > \ | \t (tab) \r (carriage return) \n (new line) Characters Used in Repository License File Name _G _H _I _J _K _L _M _N _O _P _Q _R _S _T _U _V _W _X _Y _Z _a _b _c _d _e You must add a valid product license key to the repository license file when you create the repository configuration. or if the file contains an invalid or expired product license key.Table 4-5.

.lic. For example. The connectivity license key for the particular PowerCenter Connect product. Source or target definition using a relational database connection. It creates a license file. If they do not match. or if the file contains an invalid or expired product license key.. You can manage license files using the following PowerCenter tools: ♦ Administration Console. You include the session in a workflow and assign the workflow to a PowerCenter Server that does not have the Partitioning option license key.PowerCenter Server License Files When you install the PowerCenter Server. any file you specify must exist in the PowerCenter Server installation directory for the PowerCenter Server to start. Workflow configured to run on a server grid. see “Adding a Repository Configuration” on page 105. assign the workflow to a PowerCenter Server that has the Partitioning option license key. Application Source Qualifier transformation. the session fails. For more information about using the Administration Console to manage license files. A session configured to use multiple partitions. 122 Chapter 4: Configuring the Repository . License File Compatibility Requirements When a Workflow Contains this Repository Object. You cannot start the PowerCenter Server if the specified license file does not exist. pm. Parse or Address transformation available with the Data Cleansing option. When you run the workflow. Managing License Files You manage license files using different PowerCenter tools.. depending on the license file type and the operating system. the installation program prompts you for the product license key. Partitioning option license key. The license keys in the PowerCenter Server license file must match the license keys in the repository license file when the PowerCenter Server runs workflows in the repository. PowerCenter Connect for Web Services connectivity license key. the session or workflow might fail. Table 4-6 describes the compatibility requirements when a PowerCenter Server runs a workflow: Table 4-6. in the PowerCenter Server installation directory. The connectivity license key for that relational database. Source definition configured to extract data from web services. You can configure the PowerCenter Server to use a different license file. However.. You can update and view repository license files for repositories managed by Repository Servers on UNIX and Windows. you create multiple partitions in a session. The PowerCenter Server License File Must Contain. To verify the session completes. Data Cleansing option license key. Server grid option license key.

♦ pmlic. see “Installing and Configuring the PowerCenter Server on Windows” in the Installation and Configuration Guide. Do not modify license files manually. For information about using the PowerCenter Server Setup to manage PowerCenter Server license files. You can manage license files for a PowerCenter Server on Windows. you must use pmlic. That license file must exist in the PowerCenter Server installation directory for the PowerCenter Server to start. Use production license keys in a production environment. Then add option and connectivity license keys. Specify the PowerCenter Server license file name in the PowerCenter Server setup. see “PowerCenter Server License Files” on page 122. You can use a development license key for all PowerCenter Servers and repositories in your development environment. The repository license file specified in the repository configuration must exist in the Repository Server installation directory for the repository to start. For details. You must purchase a production license key for every repository and PowerCenter Server in your production environment. PowerCenter Server setup. Update PowerCenter Server license file with connectivity and option licenses after you install the PowerCenter Server. ♦ ♦ ♦ ♦ ♦ ♦ Working with PowerCenter Licenses 123 . Verify that the PowerCenter Server that runs workflows in a repository uses a license file with the same license keys that exist in the repository license file. Use development license keys in a development environment. either production or development. For more information about using pmlic. Use the PowerCenter tools to modify license files. Enter the product license key on the Licenses tab of the repository configuration when you create a new repository configuration. ♦ Note: Only use the PowerCenter tools to edit a license file. see “Installing and Configuring the PowerCenter Server on Windows” in the Installation and Configuration Guide. To manage a PowerCenter Server license file for a PowerCenter Server on UNIX. Do not edit them manually. All license keys in a license file must be of the same repository type. You can manage all license file types. Rules and Guidelines Use the following rules and guidelines when you work with PowerCenter license keys and license files: ♦ ♦ ♦ ♦ Enter the product license key when you install the PowerCenter Server or Repository Server.

124 Chapter 4: Configuring the Repository .

Chapter 5 Repository Security This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 160 Troubleshooting. 131 Creating and Editing Repository Users. 127 User Authentication. 134 Repository Privileges. 148 Managing User Connections. 142 Permissions. 163 125 . 154 Handling Locks. 151 Creating an Audit Trail. 157 Tips. 153 Repository Locks. 126 User Groups.

Repository users. you need to determine if the owner of the lock is using the object. a group to which the owner belongs. execute. write-intent. User connections. You can assign users to multiple groups. Folder permissions. Every user in a group receives the privileges for that group. and the rest of the repository users. The repository creates five kinds of locks depending on your task: in-use. but to avoid repository inconsistencies. fetch. You must assign each user to at least one user group. Most tasks also require the appropriate repository privileges. Even if you have the repository privilege to perform certain tasks in the repository. The ability to perform tasks within an individual folder. Each user must have a unique repository user name to use folder and object locking properly. you need to determine if the user has an active connection before closing the connection. deployment groups.Overview PowerCenter offers several layers of security that you can customize for your repository. The Repository Server locks and unlocks all objects in the repository. You can grant versioning object permissions to users and groups. Repository privileges. You assign repository privileges to users and groups. and queries. The ability to perform actions within the repository and to start and stop the PowerCenter Server. The ability to use versioning objects for change management. User name used to access the repository. The repository locks repository objects and folders by user. 126 Chapter 5: Repository Security . you may require permission to perform the task within a given folder. Versioning objects permissions. ♦ ♦ ♦ ♦ ♦ ♦ Informatica recommends taking time to plan your overall strategy so that you can implement appropriate security measures to protect your repository. To avoid repository inconsistencies. You can plan and implement security using these features: ♦ User groups. You can assign privileges to individual user names. You can also assign privileges to groups. You can manually release a lock on an object by ending the connection of the user holding the lock. You can perform some tasks with folder permissions only. Locking. and save. You can use the Repository Manager to monitor user connections to the repository. Versioning objects include labels. Repository groups for user names. You can use an external directory service to manage your user names and passwords. You can grant permissions on three levels: to the folder owner. You can end connections when necessary.

you revoke the privilege from each user in the group. These two groups exist so you can immediately create users and begin developing repository objects. you can also create custom groups and assign specific privileges and permissions to those groups. Default Groups When you create a repository. you must revoke the privilege individually to restrict that user. Note: When you revoke a privilege from a group. However. You can also assign users to multiple groups. For details. For information on the privileges and permissions to administer repository user groups see “Repository Manager Tasks” on page 516. Use the Repository Manager to create and edit repository user groups. When you assign a user to a group. There are two default repository user groups: ♦ ♦ Administrators Public You cannot delete these groups from the repository or change the default privileges. Each repository user must be assigned to at least one user group. the Repository Manager creates two repository user groups. This grants the user the privileges of each group. the user: ♦ ♦ ♦ Receives all group privileges. Loses and gains privileges if you change the user group membership. if a user has been granted the privilege individually (as with default privileges). you assign that group a set of privileges. see “Repository Privileges” on page 142. User Groups 127 . After creating a new user group.User Groups You create custom user groups to manage users and repository privileges efficiently. The Repository Manager creates two default users in the Administrators group: ♦ ♦ Administrator The database user name used to create the repository You cannot delete these users from the repository or remove them from the Administrators group. Inherits any change to group privileges. For a list of default privileges. see “Default Privileges” on page 143. However. The Repository Manager does not create any default user for the Public group.

Select the Groups tab. For example. you must choose one of those groups to receive Owner’s Group permissions. To create a user group: 1. If the owner belongs to more than one group. If you assign read and write folder permissions to Owner’s Group. you must select one of those listed groups to receive Owner’s Group permissions. the Production group receives read and write permissions on the folder. You can only grant Owner’s Group permissions to one of the groups to which the folder owner belongs. then every user in the Developer group has read and write permission for the folder. Developer. Choose Security-Manage Users and Privileges. 2. Creating a User Group Perform the following steps to create a user group. the Developer group receives Owner’s Group permissions on the folder. 128 Chapter 5: Repository Security . If the owner of the folder belongs to both the Developer group and the Production group.User Groups and Folder Permissions When you create or edit a folder. If you select the Production group. connect to a repository. you can define Owner’s Group permissions for the folder. In the Repository Manager. 3. if the owner of a folder belongs to only one group.

Only the first 256 characters display in the Manage Users and Privileges window. the Repository Manager reassigns those users to the Public group. 6. and click OK.4. Select the group in the Groups tab that you want to delete. Edit the description. 5. 4. Public and Administrators. User Groups 129 . However. you cannot edit the default groups. 5. Click Add. Public and Administrators. In the Repository Manager. Click OK. 2. Editing a User Group You can edit the description of an existing user group at any time. The new group now appears in the list of all groups defined for the repository. You can now assign privileges and users to the group. 2. connect to a repository. Deleting a User Group You can delete any user group in the repository except the default repository user groups. Note: If you delete a group that contains users. Choose Security-Manage Users and Privileges. Enter the name of the group. Select a group in the Groups tab and click Edit. 7. To delete a user group: 1. Click OK again to save your changes.000 characters. To edit a user group: 1. 3. In the Repository Manager. You can enter up to 2. Click OK to return to the Repository Manager. Choose Security-Manage Users and Privileges. 3. connect to a repository.

Click OK to save your changes. A message appears stating all users in the group will be assigned to the Public group. 6.4. 5. Click OK. Click Remove. 130 Chapter 5: Repository Security .

User Authentication Each repository user needs a user name and password to access the repository. The default password for Administrator is Administrator. When you create a new user. the repository creates two default users: ♦ ♦ Administrator. you User Authentication 131 . These users are in the Administrators user group. New users receive the enabled status. The user name is valid for accessing the repository. but does not maintain user passwords in the repository. When you create a repository. The repository administrator maintains the user name-login associations. with full privileges within the repository. Using LDAP Authentication If you use LDAP authentication for repository users. Using Default Authentication If you use default authentication. A user receives this status if the repository administrator disables the user. For more information see “Registering a Plug-in (Registerplugin)” on page 482. The security module verifies users against these user names and passwords. You cannot remove them from the Administrators group or delete them from the repository. If you use an external directory service. the repository maintains an association between repository user names and external login names. repository users can have one of the following statuses: ♦ ♦ Enabled. To accomplish this. PowerCenter uses a security module to verify user log in. Disabled. If you use LDAP to authenticate users. The database user name and password used when you created the repository. change the Administrator password immediately after creating the repository to protect your metadata. Tip: If you are using default authentication. For information on the privileges and permissions to administer repository users. the repository security module passes a user login to the external directory for authentication. you must ensure that the Administrator has a valid external login name when you register the authentication module with the repository. LDAP defines a network protocol for accessing a directory service. The security module supports the following types of user authentication: ♦ ♦ PowerCenter default authentication Lightweight Directory Access Protocol (LDAP) authentication PowerCenter default authentication enables you to create users and maintain passwords in the repository. the repository maintains an association between repository user names and external login names. The user cannot access the repository. see “Repository Manager Tasks” on page 516. Database user.

The user name is valid for accessing the repository. The repository user name is not linked to an external login name. The Repository Administrator must explicitly enable the user by linking the user name to the login name. you can use the pmrep Registeruser command to create the user name and associated login name. Explicitly disabled from accessing the repository by the Administrator. Figure 5-1 shows the repository user names and associated login names: Figure 5-1. This status occurs when you change from the default authentication to an external directory service. Disabled.can select the login name from the external directory. Repository User Names and External Login Names User Status Login Name Repository User Name The user status indicates if a user can access the repository. you can see the repository user names and the directory login names. 132 Chapter 5: Repository Security . For more information on associating a user name to a login name. see “Registering a User (Registeruser)” on page 457. Users can have one of the following statuses: ♦ ♦ ♦ Enabled. see “Enabling a User” on page 139. You must associate JSmith with the directory login JohnS in order for him to access the repository. For more information about Registeruser. you might deploy a repository to a new server. or if you know the directory login name. No login assigned. When you view users in the repository. The user cannot access the repository. For example. A repository user called JSmith might have a directory login of JohnS on the new server. When you add new users they receive the enabled status.

the status for the associated user name becomes “no login assigned. You do not see the associations in the Repository Manager. The status changes to “account removed. You must enable these users by associating their repository user names with valid external directory login names. the security module cannot find the login name. The login changes on the LDAP directory. The user authentication mode changes between LDAP and default authentication.” The Repository Administrator must explicitly enable you by linking your repository user name to a new login name in the external directory. The user name is in the repository. The system administrator enables or disables it. ♦ User status changes for the following reasons: ♦ ♦ ♦ Switching Between Default and External User Authentication If you switch from default authentication to external directory authentication. your existing repository users receive the “no login assigned” or “login suggested” status. The user name is no longer on the external directory. When you retain the repository user name-login associations you can reuse the associations if you register another external directory service for authentication. For example. if your login changes on the external directory. but is not linked to a login name (as above) in the external directory. If you switch from using external directory authentication to default authentication.” User Authentication 133 . and the user cannot access the repository. but user authentication does not use them. Account removed. If a login is not valid on the new external directory. you can retain the user name-login associations in the repository.♦ Login suggested. This status is similar to “no login assigned” except that the security module finds a possible matching login name that you can enable. However. the users you add under the external directory service have the disabled status.

Tip: Before creating repository users. see “Repository Manager Tasks” on page 516. Choose Security-Manage Users and Privileges. Each user belongs to at least one user group. create user groups. connect to a repository. you must first add the user to another group. see “User Groups” on page 127. The New User dialog box displays. then remove the user from the Public group. For information on the privileges and permissions to create a repository user. 2. you create a different user name for each user accessing the repository. you enter user names in the repository and assign a password for each user name you create. Click Add. Creating a User Under Default Authentication If you are using default user authentication. 3. In the Repository Manager. the Repository Manager assigns the user to the Public group. To change the group. To create a user under default authentication: 1. For details on groups. and assign the appropriate privileges to those groups. 134 Chapter 5: Repository Security . The Manage Users and Privileges dialog box displays. When you create a user.Creating and Editing Repository Users In the Repository Manager.

You can use the optional Description and Contact Info fields to further identify the user. Enter a user name and password between 1 and 75 characters long. and click Add. 5.4. select the group in the Not Member list. The group to which the user belongs appears in the Member Of list. Click Group Memberships. Creating and Editing Repository Users 135 . with no leading or trailing spaces. The remaining groups appear in the Not Member Of list. 6. To add the user to a group.

8. 2. Editing a User Password If you are using default authentication. Click OK. connect to the repository. To remove the user from a group. 3. Click OK to return to the Repository Manager. Enter the new password twice to confirm it. 136 Chapter 5: Repository Security .The group appears in the Member list. and click Remove. select the group in the Member list. you can edit your user password. Note: You cannot remove a user from a group when the user belongs to only one group. To edit a password: 1. In the Repository Manager. Choose Security-Change Current Password. 7. Enter the old password. 4. 5. For information on the privileges and permissions to edit your own password see “Repository Manager Tasks” on page 516.

you add repository users from a list of login names from the external directory. 4. The Add Users dialog box displays a list of names from the external directory service. 2. click Check Names. but it must match a valid login name in the directory. Select a login name from the external directory list and click Add. Creating and Editing Repository Users 137 . 3. connect to a repository.Creating a Repository User Under an External Directory Service If you are using an external directory service for maintaining repository users. To add users with an external directory service: 1. Click Add. In the Repository Manager. Choose Security-Manage Users and Privileges. You do not create repository user passwords. To check the spelling. Note: You can type a name at the bottom of the screen. the names display at the bottom separated by semi-colons. If you select more than one name. The login name displays at the bottom of the screen.

or editing a user description. You cannot change a user name. so the repository user name maps to a new login name. you can remove it from the repository. In the Repository Manager. Click OK on the Add Names dialog box to add your selections to the user name-login name association. If you use default authentication. If you use default authentication. You cannot change group memberships for the Administrator user. you can change a user password. Passwords must be in 7-bit ASCII only. Click OK. you must correct the name or remove it from your selections on the Invalid Name dialog box. 138 Chapter 5: Repository Security . To edit a user: 1. 6. To change the password. login name and enabled status. If you use an external directory service you can change the user name-login association. Choose Security-Manage Users and Privileges. The Edit User dialog box displays. Editing a User You can edit users to maintain their group memberships and change their login status. If any of the names you type in do not match a valid directory service login. Highlight a user and click Edit. You can edit users with the following exceptions: ♦ ♦ ♦ ♦ You cannot edit passwords if you use an external directory for security. Refer to the next section for information on adding a user to a group. you can change the password. If a user name becomes obsolete. 3.5. The password can be between 1 and 75 characters long. enter the new password twice. You cannot edit any property for the Database user except contact information. with no leading or trailing spaces. The Manage Users and Privileges screen displays the user name. 2. 4. connect to a repository.

and click Remove. select the group in the Not Member Of list. 3. Choose Security-Manage Users and Privileges. To enable a user: 1. The group appears in the Member Of list. enter up to 2.000 characters. 2. click OK. The selected group appears in the Not Member Of list. Click OK again to return to the Repository Manager. When you enable a user under default authentication. 9. or if you are enabling a user that has a suggested login name. To edit the description. click Group Memberships. 7. Creating and Editing Repository Users 139 . Select the users you want to enable. To remove the user from a group.5. and click Add. To save your changes. Enabling a User A user with a status other than enabled cannot access the repository. One of the following actions occurs for each selected user: ♦ ♦ The user status changes to enabled. This occurs if you use default authentication. The first 256 characters display in the Manage Users window. 8. You can select multiple users at a time. You must explicitly enable the user. This dialog box displays a list of valid login names from the external directory service. It displays if you are using an external directory service. If the user belongs to only one group. To add a group membership. The Select Login Name dialog box displays. select the group in the Member Of list. The Manage Users and Privileges dialog box displays. When you enable a user and you are using an external directory service. you link their repository user name with their directory login name. only the status changes. To edit group memberships. Click Enable. 10. 6. you must add the user to another group before removing the user from the original group.

When you disable a user. You can disable users when you use default security or external user authentication. Note: You can disable users from the command line. this dialog box displays again for the next user. To associate the user name with a different login name. you retain the user name in the repository. select a login name from the list and click OK. 3. Choose Security-Manage Users and Privileges. see “Editing a User (Edituser)” on page 454. 4. In the Repository Manager. so you can quickly enable the user at a later time. For more information. Disabling a User When you disable a repository user you change the user status from enabled to disabled. The Manage Users and Privileges dialog box displays the login name and the associated repository user name. you can disable and then enable the user. see “Editing a User (Edituser)” on page 454. If you enable more than one user. Click Disable. The user status changes to disabled. 2. 4. 140 Chapter 5: Repository Security . To disable a repository user: 1. The user status becomes enabled.If a user has a suggested login name. For more information about Edituser. You can select multiple users at a time. Select the users you want to disable. Disabled users cannot access the repository. You can also use the pmrep Edituser command. you enable the association immediately when you click Enable. If you use the Select Login Name dialog box. connect to a repository.

4. Choose Security-Manage Users and Privileges. Select a user and click Remove. If you use default authentication. To remove a repository user: 1. Creating and Editing Repository Users 141 .Removing a Repository User When you remove a user from the repository that is using an external directory service. 2. In the Repository Manager. you remove the user name in the user name login association. 3. you remove the user name from the repository. connect to a repository. Click Yes to confirm that you want to remove the user.

For example. A privilege granted to an individual user remains with the user until you remove it. however. and execute permissions. you grant privileges to groups. the user retains this privilege regardless of changes in group membership. The Use Repository Manager privilege enables you to use management functions such as mass validating or applying labels. if you grant the Administer Repository privilege to the user. grant the Super User privilege to an individual user. Users with only the Use Designer or Use Workflow Manager privilege can do many of the tasks that Use Repository Manager allows. if you move a user from a group that has the Administer Repository privilege into a group that does not. However. generally require one or more folder permissions in addition to the related repository privilege to perform the task. This limits the number of users with the Super User privilege. such as stopping the PowerCenter Server or creating user groups. write. Folder related tasks. You can perform some tasks in the repository with only repository privileges. For more information on versioning object permissions. You can add or remove privileges from any user or group except: ♦ ♦ Administrators and Public (the default read-only repository groups) Administrator and the database user who created the repository (the users automatically created in the Administrators group) Ordinarily. Versioning objects and connection objects have separate read. However. see “Configuring Versioning Object Permissions” on page 149. the user loses the Administer Repository privilege. but only within the Designer or Workflow Manager. For tighter security. For a list of common repository tasks and the permissions and privileges necessary to perform those tasks. 142 Chapter 5: Repository Security . and ensures that the user retains the privilege even if you remove the user from a group.Repository Privileges The Repository Manager grants a default set of privileges to each new user and group for working within the repository. see “Permissions and Privileges by Task” on page 509. not an entire group. you can also grant privileges to individual users.

Edit folder properties for folders you own.Import. . Default Repository Privileges Default Privilege Browse Repository Permission n/a Permission Object n/a Grants You the Ability to . .Copy objects into the folder. .Search by keywords. . . You must also have Administer Repository or Super User privilege in the target repository. .Copy objects from the folder. .Create shortcuts from shared folders. Read Folder Read/ Execute Read/Write Use Designer n/a Query Query n/a Read Folder Read/Write Folder Use Repository Manager* n/a Write n/a Deployment group Repository Privileges 143 .Freeze folders you own. . Table 5-1 lists the default repository privileges: Table 5-1.Create shortcuts to objects in the folder. . . .Create or edit query.Connect to the repository using the Designer. .Import objects. .Copy a folder.Run query.View objects in the folder.View dependencies.Perform Use Repository Manager tasks in the Designer. .Browse repository.Create or edit metadata. or remove the registry.Delete from deployment group. .Remove label references. . .Unlock objects and folders locked by your user name. . . . . .Export objects. . . export.Change your user password.Add and remove reports.Connect to the repository using the Repository Manager.Configure connection information. .Default Privileges The Repository Manager grants each new user and new group the default privileges.

Add to deployment group.Export objects.Restart workflow. . . .View tasks. Read Read Write Read Write Read Write/ Execute Use Workflow Manager n/a Folder Folder Deployment group Original folders Target folder Folder Label n/a .Run the Workflow Monitor. . .Mass validation (Needs write permission if options selected. .Export objects.Check in.Start workflows immediately. and external loader connections in the Workflow Manager. . .Import objects.Recover after delete. FTP.Perform Use Repository Manager tasks in the Workflow Manager.Resume workflow.Create database. .View session details and session performance details. .Stop workflow. .Table 5-1. . .Import objects.Change status of the object. . .Delete objects from folder. .Change object version comments if not the owner. .Connect to the repository using the Workflow Manager.Abort workflow. .Copy objects. Default Repository Privileges Default Privilege Permission Write Permission Object Folder Grants You the Ability to . Read/Write Execute Connection Folder Read Folder Read/ Execute Read/ Execute Read/Write Folder Connection Folder 144 Chapter 5: Repository Security .View sessions. . .Create and edit workflows and tasks.Edit database.) .View session log. . . FTP.View workflows. . . . and external loader connections in the Workflow Manager.Apply label.Check out/undo check-out. .Validate workflows and tasks. .Schedule or unschedule workflows. . .

and privileges.Table 5-1. groups. Table 5-2 lists the extended repository privileges: Table 5-2. upgrade.Administer label permissions. stop. . . the Repository Manager provides extended privileges that you can assign to users and groups. . Default Repository Privileges Default Privilege Permission Read/Write Read Permission Object Folder Connection Grants You the Ability to .Manage passwords. users.Copy a folder within the same repository. Repository Privileges 145 . Extended Privileges In addition to the default privileges listed above. .Manage connection object permissions. .Check in or undo check out for other users. delete. . The Repository Manager grants extended privileges to the Administrator group by default.Create label. .Edit folder properties. and restore the repository.Create.Freeze folder. .Copy a folder into the repository. . backup.Create deployment group.Start. .Create and edit sessions. enable. .Copy a folder into a different repository when you have Administer Repository privilege on the destination repository.Administer deployment group permissions. . . .Purge a version. . and check the status of the repository.Create and edit deployment group. disable. * The Use Designer and Use Workflow Manager privileges enable you to do many of the tasks that you can do in the Repository Manager with the Use Repository Manager privilege. .Copy deployment group. Extended Repository Privileges Extended Privilege Administer Repository Permission n/a Permission Object n/a Grants You the Ability to . Read Read n/a Connection Read/Write Read/Write Read/Write Read Read/ Execute Write Deployment group Folder Label Original folder Deployment group Folder .Edit label.

. . .Edit server variable directories.Use pmcmd to start workflows in folders for which you have execute permission. .Start the PowerCenter Server. .Manage versioning object permissions. . When you change privileges for a group.Stop the PowerCenter Server through the Workflow Manager. . .View session details and performance details.Table 5-2. Assigning and Revoking a Privilege You can assign and revoke repository privileges to a user or group. However. Note: You cannot change the privileges of the default user groups or the default repository users. For information on the privileges and permissions to assign or revoke privileges. . .Schedule and unschedule workflows. Informatica recommends that you reserve extended privileges for individual users and grant default privileges to groups. Super User n/a n/a Workflow Operator n/a Read n/a Folder Execute Folder Read Execute Execute Execute Folder Connection Folder Connection The default privileges allow you to perform basic tasks in the Designer.View the session log.Register PowerCenter Servers with the repository. The user entered in the PowerCenter Server setup must have this repository privilege. . 146 Chapter 5: Repository Security . . across all folders in the repository. Workflow Manager. and Workflow Monitor. .Start workflows immediately.Manage connection object permissions.Perform all tasks.Stop the PowerCenter Server using the pmcmd program. Repository Manager.Abort workflow. users retain individually granted privileges until you revoke them individually. . Extended Repository Privileges Extended Privilege Administer Server Permission n/a Permission Object n/a Grants You the Ability to . . see “Repository Manager Tasks” on page 516. .Stop workflow. .Restart workflow. .Mass updates.Resume workflow.Connect to the PowerCenter Server. Extended privileges allow you to perform more tasks and expand the access you have to repository objects. you change the privileges granted to every user in the group.

To revoke a privilege from a user or group: 1. In the Repository Manager. Note: If you assign Super User privileges to a user. 4. In the Repository Manager. connect to a repository.To assign a privilege to a user or group: 1. 2. you cannot change the other privileges for them. Repository Privileges 147 . Select the privileges you want to assign to each user or group. Super User privilege enables all privileges for that user. 4. 3. Click OK to save your changes. Clear the privileges you want to revoke. Click Privileges. 3. Choose Security-Manage Users and Privileges. 2. connect to a repository. 5. Click OK to save your changes. Choose Security-Manage Users and Privileges.

148 Chapter 5: Repository Security . Allows you to run or schedule a workflow in the folder. For example. Allows you to create or edit objects in a folder. including the owner. Folder Object Security Levels Level Owner Owner’s Group Includes The owner of the folder. Write permission. maintain queries or labels. or copy deployment groups. you might have the Use Designer privilege.Permissions You can maintain user and group permissions for access to folders and versioning objects. You can grant folder permissions on three levels of security. deployment groups. you must have both read and execute permission to start a workflow in a folder. see the Workflow Administration Guide. but you must also have folder read and write permission to open and edit a mapping in a folder. Allows you to view the folders and objects. To perform a task you must have the privilege to perform the task in the repository as well as the applicable permission. queries. If the owner belongs to more than one group. if you grant only read permission to a folder Owner. if you have the default Use Workflow Manager privilege. Each member of the group to which the owner belongs. add or delete objects from deployment groups. For example. and grant read and write permission to the Owner’s Group. This becomes the Owner’s Group. Table 5-3 lists folder security levels: Table 5-3. If you do not have both the privilege and permissions. which allows you to connect to the repository through the Designer. you do not require any permissions. Versioning objects are labels. For example. you can start a workflow if you have only read permission. you cannot open or edit mappings in that folder. and connections. as listed in the owner menu. All groups and users in the repository. the folder owner has both read and write permission on the folder. If you have the Workflow Operator privilege. For details on configuring connection object permissions. run queries. You can maintain the following permissions for each type of object: ♦ ♦ ♦ Read permission. you must select one of those groups in the folder dialog box. Execute permission. while the Super User privilege requires no folder permissions. apply labels. Repository Each permission level includes the members of the level above it. Configuring Folder Permissions Certain privileges require fewer folder permissions to perform a given task. If you have the Super User privilege.

connect to a repository. you do not have read permission for the folder. 3. Configuring Versioning Object Permissions To configure and manage permissions to versioning objects you must have the Super User privilege or be the owner of the versioning object. Each versioning object has a permissions list. You cannot assign permissions to a private query. 7. The permissions list contains users or groups and their permissions for the object. To enable others to use it. World users receive no permissions by default. 5. Users that belong to the Administrators group receive all permissions by default. Choose Folder-Edit. When you assign privileges to versioning objects you can assign them on two levels. When you configure versioning object permissions. 6. If necessary. Versioning Object Security Levels Level User Group User Includes Repository group of user names. Select the folder in the Navigator. For information on the privileges and permissions to edit folder properties. A repository user name for an individual. 4. To edit folder permissions and properties: 1. If the folder does not appear in the Navigator. Users with Super User privilege receive all permissions by default. select a new owner from the Owner menu. Table 5-4 lists versioning object security levels: Table 5-4. Every user in a group receives the privileges for that group. use the following rules and guidelines: ♦ ♦ ♦ ♦ The object owner receives all permissions by default. When you add users or groups. In the Repository Manager. Permissions 149 . select a group from the Group menu. 2. If the owner belongs to more than one group.You can edit folder permissions and properties at any time. see “Repository Manager Tasks” on page 516. You also can change the object owner. The object owner is the user who creates the object. you can assign them permissions. change the query type to public. Click OK to save your changes. Edit the folder permissions as necessary.

150 Chapter 5: Repository Security . and versioning object permissions. see “Repository Privileges” on page 142. folder permissions. Add a new group or user. Change group.For information on tasks you can perform with user privileges. Change owner. You cannot change permissions of users with Super User privilege and users belonging to the Administrators group. The Permissions dialog box displays. To configure permissions for versioning objects. select a versioning object in a versioning objects browser and click Permissions. Click to define permissions.

The time of the last metadata transaction between the repository client application and the repository. The Repository Connections dialog box appears. Managing User Connections 151 . The TCP/IP address of the machine associated with the connection. To view user connection details: 1. 2. Choose Edit-Show User Connections. The repository client application associated with the connection. Launch the Repository Manager and connect to the repository. Repository Connection Properties Property User Connection ID Application Hostname Host Address Login Time Last Active Time Description The user name of the user associated with the connection.Managing User Connections The Repository Manager allows you to view the connection details for users connected to the repository. Viewing User Connections Use the Show User Connections menu command in the Repository Manager to show connection details for users and applications connected to the repository. The name of the machine running the application. The identification number assigned to the repository connection. The Repository Manager also allows you to terminate user connections. Table 5-5 describes the properties in the Repository Connections dialog box: Table 5-5. 3. Click Close to return to the Repository Manager. The time the user connected to the repository.

Use the Repository Manager to terminate residual user connections and release residual locks in the repository. A residual repository connection also retains all repository locks associated with the connection. Choose Edit-Show User Connections. Terminate residual connections only. In the Repository Connections dialog box. 2. The Repository Server closes the user connection. 3. the Repository Server does not disconnect the user from the repository. Click Close to return to the Repository Manager. 4. 6. The repository has a residual connection if the connection remains in the User Connections dialog box when the repository client application or machine is actually shut down. Verify the user is no longer connected to the repository. 5. Click End Connection.Handling User Connections Sometimes. The PowerCenter Server opens additional connections to the repository for each Load Manager and DTM process. If you terminate a repository connection to a PowerCenter Server. the Repository Server also terminates all other connections to the same PowerCenter Server. select the connection you want to terminate. This can happen in the following situations: ♦ ♦ Network problems occur. To terminate a residual connection: 1. Launch the Repository Manager and connect to the repository. 152 Chapter 5: Repository Security . A PowerCenter Client or PowerCenter Server shuts down improperly. Warning: Terminating an active connection may cause repository inconsistencies.

log file in the Repository Server installation directory. Changing your own password. The audit trail does not log the following operations: ♦ ♦ ♦ ♦ Creating an Audit Trail 153 . Changing the password of another user. but after you delete the owner or owner’s group. For more information on configuring the Repository. owner’s group. Deleting the owner or owner’s group for a folder. privileges. or permissions for a folder. The audit trail logs the following operations: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Changing the owner. Adding or removing users from a group. This change does not create a log entry. and permissions by selecting the SecurityAuditTrail configuration option in the Repository Server Administration Console. the Repository Agent logs security changes to the pmsecaudit. Installing or removing an external security authorization module. If you check this option. Adding or removing user and group privileges.Creating an Audit Trail You can track changes to Repository users. Changing permissions of queries. the ownership defaults to Administrator owner or the Public group. see “Adding a Repository Configuration” on page 105. groups. Changing global object permissions. The delete operation causes a log entry. Adding or removing a group.<repositoryname>. Adding or removing a user.

This keeps you from starting a workflow that is already running. and one execute lock simultaneously on each repository object. allowing you to view the object. Maximum per Object Unlimited Write-intent 1 Execute 1 Locking the Same Object The repository permits multiple in-use locks.Starting. the repository displays a message box: The [object_type] [object_name] is already locked by [user name]. . edit. such as workflows and sessions. The Repository Server creates and releases locks on repository objects. the PowerCenter Server runs the version of the workflow existing in the 154 Chapter 5: Repository Security . . Write-intent lock. Repository Locks Repository Lock In-use Created When . If you attempt to modify an object that already has a write-intent lock. or execute them in a workflow: ♦ ♦ ♦ In-use lock. .Editing a repository object in a folder for which you have write permission. The Repository Server creates the following types of locks on repository objects when you view. which can cause the PowerCenter Server to load duplicate or inaccurate data. or resuming a workflow. Table 5-6 lists each repository lock and the conditions that create it: Table 5-6.Repository Locks The repository uses locks to prevent users from duplicating or overriding work. Placed on objects you want to modify. For example. This keeps multiple users from editing the object at one time. Placed on objects you want to view. The repository allows multiple users to obtain in-use locks on an object. one write-intent lock.Exporting an object. The repository allows only one execute lock per object. and another user can view the session properties at the same time. if you obtain a write-intent lock on a workflow before the PowerCenter Server starts the workflow. Locks objects you want to run or execute. restarting aborting.Viewing an object in a folder for which you have write permission. thus preventing repository inconsistencies. Execute lock.Viewing an object that is already write-locked.Importing an object. . This means that you can edit a session while the PowerCenter Server runs the session.Viewing an object in a folder for which you do not have write permission. . The repository allows only one write-intent lock per object. The repository then issues an in-use lock for the object. .

For details on validating the workflow. You can view an object (obtain an in-use lock) used by another object without affecting the other object. For information about validating objects. Locking Business Components To maintain the integrity of your repository data. If you try to edit the workflow or task when another user has a write-intent lock. If you save changes after the workflow starts. Locking Within Objects Some repository objects contain other repository objects. preventing you from copying or editing the business component. Before you can use invalidated objects. However. Any user who tries to edit a related dimension table receives an in-use lock on the table. If you save changes to the repository before the workflow starts. if that object is a part of a cube or dimension being edited. the Repository Server locks the business component tree while its contents are being edited. Locking with Cubes and Dimensions Editing or deleting cubes and dimensions can affect many objects in the repository. and marks the session and every other session using the mapping invalid. and save your changes. If you try to start the workflow. the PowerCenter Server runs the original workflow and the repository updates your changes after the workflow completes. you might notice an object is locked even when no one is working with it. the Repository Server creates a write-intent lock on all related objects until you save your changes or cancel your edit. see “Validating Multiple Objects” on page 42. For example. see “Working with Workflows” in the Workflow Administration Guide. you must validate them. When you edit a property of a cube or dimension. the PowerCenter Server runs the newly-edited workflow. the PowerCenter Server obtains an execute lock on the workflow and tasks in the workflow. For example. if you use the Dimension Editor to change a Level Property field. if you save changes to an object used by other objects. Repository Locks 155 . workflows contain sessions and tasks. sessions contain mappings. the Repository Server locks all related dimension tables until you save your changes. Therefore.repository when the workflow starts. The change might invalidate any workflow containing the session. When you save the mapping. For example. you open a mapping used by a session. the repository might mark the other objects invalid. When the workflow starts. delete a transformation. the repository displays a message stating the workflow is already running. you receive a in-use lock. and mappings contain at least one source and target definition. the repository notes the mapping has been changed.

with General Ledger and Accounts Receivable as subdirectories. see “Handling Locks” on page 157. 156 Chapter 5: Repository Security . You can use the Show Locks feature to see if the business component or objects it points to are locked. For details. the Repository Server locks the Finance directory while you make changes to the Accounts Receivable or General Ledger subdirectories. For example.Locking occurs at the root directory of the business component tree. if Finance is the root directory of your tree. The Repository Server releases a lock when you choose Repository-Save.

This can happen in the following situations: ♦ ♦ Network problems occur. Object Lock Properties Column Name User Connection ID Description User name locking the object. The Object Locks dialog box appears. Handling Locks 157 . To view all locks in the repository. For more details on user connections. If an object or folder is locked when one of these events occurs.Handling Locks Sometimes. 2. To release a residual lock. see “Managing User Connections” on page 151. PowerCenter Server. connect to a repository. In the Repository Manager. Use the Show Locks menu command to view all locks in the repository. repository. Table 5-7 describes the object lock information in the Object Locks dialog box: Table 5-7. you must identify the connection associated with the lock and close the connection. This is called a residual lock. the repository does not release the lock. A PowerCenter Client. To show all repository locks: 1. The identification number assigned to the repository connection. or database machine shuts down improperly. the repository does not release a lock. Repository locks are associated with user connections. choose Edit-Show Locks. Viewing Locks You can view existing locks in the repository in the Repository Manager.

Releasing Locks If a system or network problem causes the repository to retain residual locks. Object Lock Properties Column Name Folder Object Type Object Name Lock Type Lock Time Hostname Application 3. Application locking the object: Designer. Time the lock was created. choose Edit-Show User Connections. You do not need special privileges to terminate connections associated with your repository user name. Warning: Before unlocking any object. 4. Name of the locked object. click the Refresh button. Open the Repository Manager and connect to the repository. 3. Type of lock: in-use. mapping.Table 5-7. click on the column name. 5. To view updated lock information. In the User Connections dialog box. or execute. To sort your view of the locks by column. Name of the machine locking the object. note which user owns the lock. Type of object: such as folder. 2. 158 Chapter 5: Repository Security . or source. For information on the privileges and permissions to terminate other user connections and unlock objects see “Repository Manager Tasks” on page 516. You can unlock objects and folders by identifying the user connection associated with the lock and terminating the user connection. verify that the object is not being used and verify that the user is not connected to the repository. After you view the object locks. you may need to unlock an object before using it. View object locks and identify the connection identification number associated with the locks you want to release. Description Folder in which the locked object is saved. Verify the user is not connected to the repository. To unlock a folder or repository object: 1. 4. Workflow Manager. or Repository Manager. write-intent. match the connection identification number from the Object Locks dialog box with the connection identification number in the User Connections dialog box.

Click Close to return to the Repository Manager. The Repository Server closes the user connection and releases all locks associated with the connection. 7.6. Select the user connection and click End Connection. Handling Locks 159 .

The simplest way to prevent security breaches is to limit the number of users accessing the repository. The more distinct your user groups. keep it simple. determine how many types of users access the repository. answer the following questions: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ After you evaluate the needs of the repository users. you can create appropriate user groups. Using shared accounts negates the usefulness of the repository locking feature. and limit folder permissions. assign the appropriate privileges to those groups and design folder permissions to allow their access to particular folders. The repository creates locks on objects in use. Once you establish separate groups. limit privileges.Tips When setting up repository security. You have the tools to create a complex web of security. Do not use shared accounts. limit the ability of other repository users to perform unnecessary actions. Then create separate user groups for each type. across all folders? Before implementing security measures. Securing the environment involves the following basic principles: ♦ ♦ ♦ Limiting users Restricting privileges Defining permissions Who needs access to the repository? What do they need the ability to do? Where can I limit repository privileges by granting folder permissions instead? Who creates transformations and mappings? Do they need access to all folders? Who schedules workflows? Who needs to start workflows manually? Do they need to access all workflows in the repository? Who administers the repository? Who starts and stops the PowerCenter Server? Who needs the ability to perform all functions within the repository. To do this. 160 Chapter 5: Repository Security . Breaking a valid lock can cause repository and inconsistencies. but the simpler the configuration. the tighter your repository security. such as running sessions or administering the repository. Create groups with limited privileges. Then. To avoid repository inconsistencies: ♦ Do not use shared accounts. the easier it is to maintain.

Limit the Administer Repository privilege. you can add the Administer Server privilege to the individual user. When working in a multiple repository environment (PowerCenter only). Limit user and group access to multiple repositories. The Super User privilege permits you to perform any task despite folder-level restrictions. Restricting the number of crossover users limits the possibility of a user connecting to the wrong repository and editing objects in the wrong folder. The Repository Manager grants the Super User privilege automatically to the Administrators group. For details on locking. and unlocking other user's locks. see “Repository Locks” on page 154. but this user also administers the PowerCenter Server. Limit the Super User privilege. restrict the number of users who need this all-encompassing privilege. you should limit this privilege in production repositories. Users with either the Browse Repository or Administer Repository privilege can unlock any object or folder locked by their own user name. Tips 161 . limit the number of users and groups accessing more than one repository. Since this feature is often used to deploy folders into production.♦ ♦ Before unlocking an object or folder. and you need to keep the user in that group for the purpose of folder permissions. you must also limit the number of users you assign to the Administrators group. You can allow users a limited ability to run workflows by granting the Use Workflow Manager privilege with read and execute permission. see who owns the lock and make sure the owner is not using the object. The Administer Repository privilege permits a user to copy a folder from one repository to another. This becomes more important when repositories contain folders with the same or similar names. if you have a user working in the Developers group. you can add individual privileges to that user. Ask all users to exit the repository before unlocking multiple objects or closing user connections. This includes starting any workflow. To protect your repository and target data. You can allow users a limited ability to unlock locks by granting them the Browse Repository or Administer Repository privilege. If a single user requires more privileges than those assigned to the user's group. Customize user privileges. Therefore. For example.

if the user needs to use the Workflow Manager to start workflows. avoid granting the Workflow Operator privilege. you can assign the user the Use Workflow Manager privilege. you can use the Workflow Manager to start any workflow within the repository for which you have read permission.Restrict the Workflow Operator privilege. Misuse of the privilege can result in invalid data in your target. With the Workflow Operator privilege. If the user uses pmcmd to start workflows. Instead. the user needs only execute permission for the folder. and read and execute permission for the folders in which the user works. You can also use the pmcmd program to start any workflow in the repository. Where possible. 162 Chapter 5: Repository Security .

and granting different sets of privileges. You must. or you can inherit Browse Repository from a group. You can assign Browse Repository directly to a user login. I find that none of the repository users can perform certain tasks. know the exact name of the workflow and the folder in which it exists. After creating users and user groups. to remove the privilege from users in a group. Therefore. but I cannot edit any metadata. Troubleshooting 163 . you need to edit the database user to allow all privileges in the database. you do not need to view a folder before starting a workflow within the folder. and every user in the group. How does read permission affect the use of the pmcmd program? To use pmcmd. you do not need read permission to start workflows with pmcmd. you must remove the privilege from the group. Check the folder permissions to see if you belong to a group whose privileges are restricted by the folder owner. Therefore. even the Administrator. Repository privileges are limited by the database privileges granted to the database user who created the repository. you must also have the default privilege Browse Repository. Browse Repository is a default privilege granted to all new users and groups. You may be working in a folder with restrictive permissions. but I cannot access a repository using the Repository Manager. If the database user (one of the default users created in the Administrators group) does not have full database privileges in the repository database. you can start any workflow in the repository if you have the Workflow Operator privilege or execute permission on the folder. With pmcmd.Troubleshooting The solutions to the following situations might help you with repository security. I have the Administer Repository Privilege. however. My privileges indicate I should be able to edit objects in the repository. Why does every user in the group still have that privilege? Privileges granted to individual users take precedence over any group restrictions. I created a new group and removed the Browse Repository privilege from the group. To perform administration tasks in the Repository Manager with the Administer Repository privilege.

164 Chapter 5: Repository Security .

166 Folder Properties. 171 Comparing Folders. 168 Configuring a Folder. 174 165 .Chapter 6 Working with Folders This chapter contains information on the following topics: ♦ ♦ ♦ ♦ Overview.

If you work with multiple repositories. and sessions. providing the means to organize the repository in the most logical way. you can use any mapping in the folder. transformations. business components. mapplets. or stored in a shared folder and accessed through a shortcut. 166 Chapter 6: Working with Folders . you can create a folder that allows users to share objects within the folder. you use folders to store workflows. you can copy the entire folder. You can create shared and non-shared folders. Keep in mind that any mapping in a folder can use only those objects that are stored in the same folder. you can copy it into your working folder. dimensions. so if you want to use an object in a nonshared folder. Folders are designed to be flexible. You can copy objects from one folder to another. You can copy a session within a folder or to another folder. you can create a folder that allows all repository users to see objects within the folder. you use folders to store sources.Overview Folders provide a way to organize and store all metadata in the repository. targets. Each folder has a set of configurable properties that help you define how users access the folder. When you create a session in a folder. Use the Copy Wizard to copy individual workflows to other folders. Using Folders in the Designer In the Designer. you can use any object in the folder. including mappings. For example. tasks. schemas. but not to edit them. and you can create shortcuts to objects in shared folders. you can include any session or task in the folder. you can view the users accessing folders and the objects within each folder. you can also copy objects across repositories. When you create a mapping in a folder. and sessions. and mappings. To copy all workflows within a folder to a different location. Or. Using Folders in the Workflow Manager In the Workflow Manager. When you create a workflow. You can also copy and replace folders within the repository or across repositories. Using Folders in the Repository Manager You create and maintain folders in the Repository Manager. to help you logically organize the repository. Organizing Folders Folders are designed to be flexible. Note: You must create a folder in a repository before you can connect to the repository using the Designer or Workflow Manager. cubes. In the Repository Manager.

designed to store work for that user only. If users work on separate projects. this technique avoids any problems that might occur if two people attempt to edit the same piece of metadata at the same time. For example: ♦ You might create a single folder for each type of data. subject area. you might create folders for each development project. For example. schemas. you should understand the security measures associated with folders so you can best protect repository objects. mappings. You can create a folder for each repository user. and reusable transformations) that you create through the Designer. target definitions. you might create one folder for accounts payable and another for accounts receivable. or type of metadata. Overview 167 . if you want to organize accounting data. user.In a repository. You might create a different folder for each type of metadata (source definitions. ♦ ♦ Before creating a system of folder organization.

Folders have the following permission types: ♦ ♦ ♦ Read permission.Folder Properties Each folder has several configurable properties on the folder property sheet. see “Permissions and Privileges by Task” on page 509. For list of permissions and privileges combinations allowing you to perform each task. Allows you to create or edit objects in the folder. Folder permissions work closely with repository privileges. and execute all tasks across all folders in the repository and can perform any task using the PowerCenter Client tools. Allows you to execute or schedule a workflow in the folder. For details on how folder permissions interact with repository privileges. You can use these properties to protect metadata saved in the folder. Execute permission. and the tasks you permit them to perform. and execute tasks within a specific folder. Allows you to view the folder as well as objects in the folder. write. For more information on changing the status of all objects in a folder. see “Working with Version Properties” on page 203. you can apply a status to all versioned objects in the folder. Folders have the following properties: ♦ ♦ ♦ ♦ Folder permissions Folder owner Owner’s group Allow shortcuts If folder is in a repository enabled for version control. you can control user access to the folder. Privileges grant access to specific tasks while permissions allow you to read. Write permission. With folder permissions. while permitting the appropriate users access to the folder. see “Repository Security” on page 125. 168 Chapter 6: Working with Folders . Permissions Permissions allow repository users to perform tasks within a folder. write. Note: Any user with the Super User privilege has read.

Shared Folders You can designate a folder to be shared. then grant the same permission to Repository. If you have an object that you want to use in several mappings or across multiple folders. Any other user must have Administer Repository and read permission. then grant all folder permissions to Owner and Owner’s Group. you make a user in the fullaccess group the owner of the folder. the Owner and Owner’s Group retain the permission.Permission Levels You can grant three levels of security on folder permissions. Each permission level includes the members in the level above it. If the owner belongs to only one group. restricting Repository permission limits that group’s folder permissions. as desired. When you create a folder. Folder Owner and Owner's Group Because you grant permissions to Owner and Owner’s Group. In the Designer. If you restrict a permission from the Owner or Owner’s Group. Table 6-1 lists the users included in each permission level: Table 6-1. Note: All users in the Administrators group or with the Super User privilege have full access to all folders in the repository. If the folder owner belongs to more than one repository group. All users and groups in the repository. Folder Permissions Permission Level Owner Owner’s Group Repository Includes Owner of the folder. The owner of the folder has an additional ability to edit the folders properties as long as the owner has the Browse Repository privilege and read permission on the folder. that group automatically becomes the Owner’s Group. or the Super User privilege to edit folder properties. As long as a group does not have the Super User privilege. Then restrict Repository permissions. For example. like an Expression transformation that calculates sales Folder Properties 169 . Each user in the owner’s repository user group. your choices for these settings affect how repository users access objects within the folder. you can also choose a repository group as the Owner’s Group. If the owner belongs to more than one group. To do this. shared folders allow users to create shortcuts to objects in the folder. You want a folder allowing full access to one group while limiting access to the other. you must select one group for the Owner’s Group. you can select any user in the repository to be the folder owner. the repository contains users in two user groups.

you can place the object in a shared folder. As with local shared folders. you can connect to the global repository. For example. Note: Once you make a folder shared. the repository updates all shortcuts in the domain to reflect those changes. you cannot reverse it. Shortcuts inherit changes to their shared object. you can change the Expression transformation in the shared folder. for example. if you are working in a folder in a local repository. Then all shortcuts to the Expression transformation inherit the changes. if changes are made to the original object. 170 Chapter 6: Working with Folders . Shared Folders in Global Repositories Shared folders in global repositories can be used by any folder in the domain. you can copy the existing object. You can then access the object from other folders by creating a shortcut to the object. you change the way your company calculates sales commissions. and create a shortcut to a shared folder for the official sales commission Expression transformation. So if.commissions. If you want to use an object in a shared folder without inheriting any future changes.

connect to the repository. Creating a Folder For information on the privileges and permissions to create a folder. Allows shortcuts. In the Repository Manager. Defines the ability of users and groups to access the folder. Folder owner. Owner’s group. You can then view these comments in the Repository Manager. To create a folder: 1. Configuring a Folder 171 . Folder status. and the ability to administer the folder. Each status defines the ability of users to check out and edit objects in the folder and whether copy deployment group operations can create new versions of objects in the folder. see “Repository Manager Tasks” on page 516. Determines whether the folder is shared. separate from general users.Configuring a Folder Each folder in the repository must have the following information configured in the folder properties dialog box: ♦ ♦ ♦ ♦ Folder name. The group selected can also have a different level of permissions in the folder. Folder permissions. The owner can have a different level of permissions within the folder. ♦ ♦ You can optionally enter a description of the folder. Specifies a status applied to all objects in the folder. The name of the folder in the repository.

makes the folder shared. If selected. 172 Chapter 6: Working with Folders . Description of the folder that appears in the Repository Manager. For more information on object status.2. If the folder is shared. Choose Folder-Create. The folder appears in the Navigator. Any user in the repository can be the folder owner. Only groups to which the owner belongs can be selected. the folder displays an open hand icon. For details. Owner of the folder. Click OK. Folder permissions for users in the repository. see “Permissions” on page 168. This option applies to versioned repositories only. Enter the following information: Folder Properties Name Description Owner Owner’s Group Allow Shortcut Status Required/ Optional Required Optional Required Required Optional Required Description Folder name. Repository user group to receive Owner’s Group permissions. 3. Permissions Required 4. see “Working with Version Properties” on page 203. The status applied to all objects in the folder.

Choose Folder-Edit. 2. Note: The Repository Server updates changes in folder properties immediately. In the Repository Manager. Enter the desired changes. For information on the privileges and permissions to delete a folder see “Repository Manager Tasks” on page 516. and click OK. you can delete that folder from the repository. 2. Deleting a Folder If a folder becomes obsolete. In the Repository Manager. click OK. make sure no users are accessing the folder when you edit the folder. To delete a folder: 1. To edit a folder: 1. connect to a repository and select a folder. 3. Choose Folder-Delete. connect to a repository and select a folder. To avoid repository inconsistencies due to changes in folder properties. 3.Editing a Folder For information on the privileges and permissions to edit a folder see “Repository Manager Tasks” on page 516. Configuring a Folder 173 . When asked if you really want to delete the folder.

You can specify either one-way or two-way comparisons. See Table 6-2 on page 174 for a list of compared attributes for object types. see “Comparing Objects” in the Designer Guide. Object types to compare. you might want to verify the contents of a folder or compare it with other folders. You must have read permission for each folder you want to compare. A directional comparison checks the contents of one folder against the contents of the other. Compare objects between two folders in different repositories. The wizard compares objects based on specific object attributes. You can specify the object types to compare and display between folders. Compared Attributes and Object Differentiation The Compare Folders Wizard compares objects based on specific object attributes. The Compare Folders Wizard allows you to perform the following comparisons: ♦ ♦ Compare objects between two folders in the same repository. the Repository Manager uses the latest checked in version of an object for comparison.Comparing Folders Before you copy or replace a folder in a repository. If you use a versioned repository. The Repository Manager lets you quickly and accurately compare the objects in different folders using the Compare Folders Wizard. Compared Object Types and Attributes Object Type Sources Targets Reusable transformations Compared Attribute Source name and database name Target name and database name Transformation name and type 174 Chapter 6: Working with Folders . Direction of comparison. You must also have privileges to access the repositories containing the folders. Similarities between objects Differences between objects Outdated objects Each comparison also allows you to specify the following comparison criteria: ♦ ♦ The wizard displays the following information: ♦ ♦ ♦ You can edit and save the result of the comparison. You can also compare two objects of the same type using Compare Objects. Table 6-2 lists the object types and attributes you can compare: Table 6-2. The wizard performs directional comparisons. For more information on Compare Objects.

regardless of whether you select the other objects to compare.Table 6-2. Compared Object Types and Attributes Object Type Mappings Mapplets Source fields Target fields Reusable transformation fields Sessions Session components Tasks Task instances Workflows Workflow events Workflow variables Worklets Shortcuts Transformation instances Mapping variables External procedure initialization properties Schedulers Configurations Compared Attribute Mapping name Mapplet name Column names Column names Port names Session name Component value Task name Task instance name Workflow name Workflow event name Workflow variable name Worklet name Shortcut name and object type Transformation instance name and type Mapping variable name Property name Scheduler name Configuration name Some objects you choose to compare also cause the wizard to compare other objects. Table 6-3 lists objects the wizard compares by default when you select certain objects to compare: Table 6-3. Compared Objects in Compare Selected Object Source field Target field Reusable transformation field Mapping variable External procedure initialization properties Session component Compared Object Source Target Reusable transformation Mapping Transformation instance Session Comparing Folders 175 .

Object name and type exist in one folder but not the other. Object modification date is older than objects with the same name. A one-way comparison does not note a difference if an object is present in the target folder but not in the source folder. ADS1 and ADS2. the source definition ORDER_ITEMS. the wizard does not note these as different. You can choose to compare based on the following criteria: ♦ ♦ ♦ Different objects. Two-way comparisons check objects in Folder1 against those in Folder2 and also check objects in Folder2 against those in Folder1. If you compare the folders using a one-way comparison. present in ADS2 176 Chapter 6: Working with Folders . Figure 6-1 shows two folders in the same repository. One-Way and Two-Way Comparisons Comparison results depend on the direction of the comparison. A two-way comparison can sometimes reveal information a one-way comparison cannot. type. Similar objects. such as precision or datatype. For example. One-way comparisons check the selected objects of Folder1 against the objects in Folder2. Outdated objects. Compared Objects in Compare Selected Object Task Instance Workflow event Workflow variable Compared Object Workflow and worklet Workflow and worklet Workflow and worklet The wizard compares the attribute of each object in the source folder with the attribute of each object in the target folder. Object name. if two folders have matching source names and column or port names but differing port or column attributes.Table 6-3. The wizard does not compare the field attributes of the objects in the folders when performing the comparison. and modification date are the same in both folders.

is not noted as a comparison. unmatched objects denoting a difference in red text. Steps for Comparing Folders Before comparing folders. Connect to the repositories containing the folders in the wizard. By default the results file is saved in the My Documents directory. similarities. choose Folder-Compare. Figure 6-1. even if you do not choose to display differences or similarities in the edit field. The Compare Folders Wizard always displays the total number of differences. In the Repository Manager. save it as an . 2. and outdated objects found during the comparison. To retain the color and font attributes of the result.but not in ADS1. Comparing Folders 177 . and outdated objects in blue text. A two-way comparison notes the absence of ORDER_ITEMS in ADS1 as a difference. Click Next. verify that you have Read permission for each folder you want to compare. Editing and Saving Results Files You can edit and save the result of a folder comparison. the absence of ORDER_ITEMS in ADS1 is noted as a difference. The Compare Folders wizard displays similar objects in green text. If you compare the folders using a two-way comparison. You can save the results of the comparison in the edit field to an .rtf or a .rtf file. One-Way and Two-Way Comparisons A one-way comparison does not note the presence of ORDER_ITEMS in ADS2 as a difference.txt file. To compare folders: 1.

Click Next. Select the object types you want to compare. 5. 6.3. 4. Click Next. 178 Chapter 6: Working with Folders . Connect to the repositories containing the folders you want to compare and select folders for comparison. Connect to repository.

name. 8. View the results of the comparison. specify the file type. 12. 11. Click Save. Click Finish. select Save results to file. 13. Save the compare results to a file. If you chose to save the results to a file. Comparing Folders 179 .7. and outdated objects. If you want to save the comparison results to a file. Click Next. similarities. Select display options. The wizard always displays the number of differences. and directory. 10. 9.

180 Chapter 6: Working with Folders .

190 Working with Shortcuts.Chapter 7 Local and Global Shortcuts This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 184 Creating a Local Shortcut. 197 Troubleshooting. 183 Understanding Shortcut Properties. 194 Tips. 182 Shortcuts Versus Copies. 198 181 . 187 Creating a Global Shortcut.

Overview Shortcuts allow you to use metadata across folders without making copies. you ensure each use of the shortcut matches the original object. Global shortcut. and you add a column to the definition. ensuring uniform metadata. A shortcut created in a local repository that references an object in a global repository. the shortcut inherits the additional column. For example. one in each folder. the Designer creates a copy of the object instead. You can create shortcuts to objects in shared folders. You can create the following types of shortcuts: ♦ ♦ 182 Chapter 7: Local and Global Shortcuts . For example. A shortcut inherits all properties of the object to which it points. Instead of creating 10 copies of the same source definition. if you have a shortcut to a target definition. When the object the shortcut references changes. a shortcut always inherits the properties of the latest version of the object that it references. By using a shortcut instead of a copy. You can create shortcuts to the following repository objects: ♦ ♦ ♦ ♦ ♦ ♦ Source definitions Reusable transformations Mapplets Mappings Target definitions Business components Local shortcut. you can create 10 shortcuts to the original source definition. the shortcut inherits those changes. Note: In a versioned repository. If you try to create a shortcut to a nonshared folder. you use a source definition in 10 mappings in 10 different folders. Shortcuts allow you to reuse an object without creating multiple objects in the repository. A shortcut created in the same repository as the original object. you can configure the shortcut name and description. Once you create a shortcut.

All shortcuts accessing the object inherit the changes. create a shortcut. If you need to edit the object. then reuse them easily in other folders. or reusable transformations. you can edit the original repository object. ♦ ♦ For details on exporting and importing objects to makes copies. if you want the object to inherit changes immediately. mapplets. and all sessions using those mappings. if you use a shortcut to a reusable transformation. You can restrict repository users to a set of predefined metadata by asking users to incorporate the shortcuts into their work instead of developing repository objects independently. then change a port datatype. you can invalidate all mappings with shortcuts to the transformation. You can save space in your repository by keeping a single repository object and using shortcuts to that object. Therefore. see “Exporting and Importing Objects” on page 263. if you have multiple copies of an object. However. If you need to change all instances of an object. For example. Shortcuts have the following advantages over copied repository objects: ♦ ♦ You can maintain a common repository object in a single location. Shortcuts Versus Copies 183 . In contrast. You can develop complex mappings. all shortcuts immediately inherit the changes you make. create a copy. or recopy the object. instead of creating copies of the object in multiple folders or multiple repositories. to obtain the same results. Otherwise. you need to edit each copy of the object. some changes can invalidate mappings and sessions.Shortcuts Versus Copies One of the primary advantages of using a shortcut is maintenance.

the Designer names the shortcut Shortcut_To_ObjectName. Describing the Object and the Shortcut Shortcuts inherit the description associated with the referenced object when you first create the shortcut. If you create a shortcut with this default. the Designer displays sources and targets by business names if they exist. the Designer displays all objects in the Navigator by name. By default. Default Shortcut Name The Designer names a shortcut after the object it references based on the object name as it appears in the Navigator when you create the shortcut: Shortcut_To_DisplayedName. However. including datatype. you can add object descriptions for each shortcut. Note: If the business name contains characters that are not allowed as in the object name. if the description of the referenced object subsequently changes.Understanding Shortcut Properties When you create a shortcut to a repository object. the Designer replaces the character with an underscore (_). you can enable the Designer tools option to display sources and targets by business name. and port description Object properties (such as tracing level) The shortcut also inherits a name and description which you can edit in the shortcut. Afterwards. the shortcut inherits the attributes of the object. precision. Since the description is unique to the shortcut. The shortcut inherits the following properties that cannot be edited in the shortcut object: ♦ ♦ ♦ Object business name and owner name Port attributes. the Designer names the shortcut Shortcut_To_BusinessName. scale. 184 Chapter 7: Local and Global Shortcuts . You can edit the default shortcut name at any time. If you create a shortcut to a source or target when this option is enabled. When you enable this option. default value. shortcuts do not inherit those changes.

Figure 7-1 shows the shortcut with a description inherited from the original transformation.For example. However. any shortcuts created after the change then contain the latest description. The shortcut object displays the following details about the referenced object: ♦ ♦ ♦ Repository name Folder name Table or transformation name Understanding Shortcut Properties 185 . Locating the Referenced Object Each shortcut tracks the location of the object it references and displays it in the transformation property sheet. as well as comments for the shortcut: Figure 7-1. Object and Shortcut Description Description from the original object Description added to the shortcut Shortcuts do not inherit edits to the description of the referenced object.

Referenced Shortcut Object Original Object Location Note: If you move or delete an object referenced by a shortcut. 186 Chapter 7: Local and Global Shortcuts . the shortcut becomes invalid.Figure 7-2 shows the transformation property sheet with the referenced shortcut objects: Figure 7-2.

When you drag the resulting shortcut into the workspace. the same shortcut icon appears. the shortcut.Creating a Local Shortcut You can reuse metadata within a single repository by creating a local shortcut. when you create a shortcut to the DetectChanges reusable Expression transformation. Shortcut_To_ObjectName. named Shortcut_To_DetectChanges appears in the Transformations node of the folder. Once you create a local shortcut. Figure 7-3 shows shortcut icons in the Navigator and Workspace windows: Figure 7-3. you can reuse it within the same folder. the shortcut icon indicates the transformation is a shortcut. If an object is in a nonshared folder. You can create a local shortcut in any folder in the repository. When you drag it into the workspace. Transformation Shortcut Icon Shared Folder Original Object Shortcut Icon Shortcut Creating a Local Shortcut 187 . The Designer names shortcuts after the original object by default. For example. it appears in the Navigator as an available repository object with the shortcut icon. You can create a local shortcut to objects in a shared folder in the same repository. After you create a shortcut. you can make a copy of the object.

you must have one of the following sets of privileges and permissions for the shared folder containing the original object: ♦ ♦ Use Designer privilege with read permission on the folder Super User privilege You must also have the one of the following sets of privileges and permissions on the destination folder: ♦ ♦ Use Designer privilege with read and write permission on the folder Super User privilege You can create a local shortcut in the Navigator or in the workspace. the folder in which you want the shortcut. 2. or click Cancel to cancel the operation. After you drop the object. to create a shortcut for a source. You can now use the shortcut in this folder. In the Navigator.Note: When you drag an object from a shared folder to a business component directory. click OK to create a shortcut. the folder in which you want the shortcut. Choose Repository-Save. the Designer displays the following message: Create a shortcut to <object type> <object name>? Note: If the object is not saved in the repository. To create a local shortcut. In the Navigator. For details. 2. choose the Source Analyzer or Mapping Designer tool. To create a local shortcut in the Navigator: 1. To create a shortcut. 5. Open the destination folder. Open the destination folder. save the object. expand the shared folder containing the object you want to use and drill down to locate the object. Select the appropriate Designer tool for the shortcut. cancel the operation. The shortcut now appears in the Navigator. Drag the object from the shared folder to the destination folder. expand the shared folder containing the object you want to use and drill down to locate the object. choose the Warehouse Designer or Mapping Designer tool. 4. 3. the Designer creates a shortcut if the object does not already exist in the destination folder. the Designer displays a message asking if you want to create a copy of the object. 3. see “Managing Business Components” in the Designer Guide. When prompted for confirmation. then create the shortcut. 188 Chapter 7: Local and Global Shortcuts . To create a shortcut for a target. For example. To create a local shortcut in the workspace: 1.

4.

Drag the object from the shared folder into the workspace. After you drop the object, the Designer displays the following message:
Create a shortcut to <object type> <object name>?

Note: If the object is not saved in the repository, the Designer displays a message asking if

you want to create a copy of the object. To create a shortcut, cancel the operation, save the object, then create the shortcut.
5.

When prompted for confirmation, click OK to create a shortcut, or click Cancel to cancel the operation. The shortcut now appears in the workspace and in the Navigator.

6.

Choose Repository-Save.

You can now use the shortcut in this folder. For details on working with shortcuts, see “Working with Shortcuts” on page 194.

Creating a Local Shortcut

189

Creating a Global Shortcut
You can reuse metadata between repositories by creating a global shortcut. A global shortcut is a shortcut in a local repository that references an object in a global repository. The local and global repository must be in the same domain. You can create a global shortcut in any folder in the local repository. Once you create the global shortcut in a folder, you can reuse it in the folder as you would any other repository object. You can create a global shortcut to any object in a shared folder in a global repository. If a folder is not shared, you can make a copy of these objects if the global and local repository have compatible code pages. For details on code page compatibility, see “Globalization Overview” in the Installation and Configuration Guide. To create a global shortcut, you must be able to connect to the global repository through the local repository. That is, if you connect to the local repository directly, the global repository must appear in the local repository. Similarly, if you connect to the global repository directly, the local repository must appear in the global repository. For example, Figure 7-4 shows the DEVELOPMENT repository as a local repository with the PRODUCTION global repository:
Figure 7-4. Create a Global Shortcut

To create a global shortcut: - Connect to the global repository through the local repository. OR - Connect to the local repository through the global repository.

You can use the Designer to connect to both the local and the global repositories individually. However, to create a global shortcut, you must connect to one repository through the other. You can connect to the PRODUCTION global repository first, then the DEVELOPMENT repository directly below PRODUCTION to create a global shortcut. You can also connect to the DEVELOPMENT repository then connect to the PRODUCTION repository appearing below it.

190

Chapter 7: Local and Global Shortcuts

To create a global shortcut, you must have one of the following sets of privileges and permissions in the global repository:
♦ ♦

Use Designer with read permission on the shared folder Super User privilege

To create a global shortcut, you must also have one of the following sets of privileges and permissions in the local repository:
♦ ♦

Use Designer with read and write permission on the folder Super User privilege

You can create a global shortcut in the Navigator or in the workspace.
To create a global shortcut in the Navigator: 1.

In the Designer, connect to the local repository and open the folder in which you want a shortcut. The global repository appears in the Navigator below the local repository. If it does not, the repository to which you are connected is not registered with the global repository.

2.

In the Navigator, connect to the global repository appearing below the local repository. The Designer expands the global repository, displaying folders for which you have read permission. If the Designer does not allow you to connect to the global repository, you might need to reconfigure aspects of your repository domain. For details, see “Configuring the Global Shortcut Environment” on page 192.

3. 4.

In the global repository, drill down through the shared folder until you locate the object you want to use. Drag the object into the destination folder in the local repository. After you drop the object, the Designer displays the following message:
Create a shortcut to <object type> <object name>?

Note: If the object is not saved in the repository, the Designer displays a message asking if

you want to create a copy of the object. To create a shortcut, cancel the operation, save the object, then create the shortcut.
5.

When prompted for confirmation, click OK to create a global shortcut, or click Cancel to cancel the operation. The shortcut now appears in the Navigator.

6.

Choose Repository-Save.

You can now use the shortcut in this folder.
To create a global shortcut in the workspace: 1.

In the Designer, connect to the local repository and open the folder in which you want a shortcut.
Creating a Global Shortcut 191

The global repository appears in the Navigator below the local repository. If it does not, the repository to which you are connected is not registered with the global repository.
2.

Select the appropriate Designer tool for the shortcut. For example, to create a shortcut for a source, choose the Source Analyzer or Mapping Designer tool. To create a shortcut for a target, choose the Warehouse Designer or Mapping Designer tool.

3.

In the Navigator, connect to the global repository appearing below the local repository. The Designer expands the global repository, displaying folders for which you have read permission. If the Designer does not allow you to connect to the global repository, you might need to reconfigure aspects of your repository domain. For details, see “Configuring the Global Shortcut Environment” on page 192.

4. 5.

In the global repository, drill down through the shared folder until you locate the object you want to use. Drag the object from the shared folder into the workspace. After you drop the object, the Designer displays the following message:
Create a shortcut to <object type> <object name>?

Note: If the object is not saved in the repository, the Designer displays a message asking if

you want to create a copy of the object. To create a shortcut, cancel the operation, save the object, then create the shortcut.
6.

When prompted for confirmation, click OK to create a global shortcut, or click Cancel to cancel the operation. The shortcut now appears in the workspace and in the Navigator.

7.

Choose Repository-Save.

You can now use the shortcut in this folder. For details on working with shortcuts, see “Working with Shortcuts” on page 194.

Configuring the Global Shortcut Environment
To create a global shortcut, configure the following:
♦ ♦ ♦

Repository code pages Repository user names and passwords for individual users Repository user name and password for the PowerCenter Server

Repository Code Pages
Before you can create a global shortcut in a repository, the repository must be registered with a global repository. To register a local repository with a global repository, the local repository code page must be a superset of the global repository code page. The Repository Manager
192 Chapter 7: Local and Global Shortcuts

validates code page compatibility when you register a repository. Once you register a local repository, you can create global shortcuts to the global repository. For details on code page compatibility between repositories, see “PowerCenter Domains” on page 13. For details on code page compatibility, see “Code Pages” in the Installation and Configuration Guide.

Repository User Name and Passwords for Individual Users
To create a global shortcut, you need to connect to the global repository through the local repository, or connect to the local repository through the global repository. To do this, you need to log into the first repository using a repository user name and password that is valid in the second repository. The second connection does not ask for a different user name/password combination. For example, you connect to the ERP repository using the user name/password, dev1/mouse. To create a global shortcut, you need to connect to the Development global repository that appears below the ERP repository. When you try to connect, the Designer verifies your user name/password exists in the Development global repository and checks your permissions and privileges. If your user name/password exists, and if you have the Use Designer repository privilege, the Designer opens the connection to the global repository.

Repository User Name and Password for the PowerCenter Server
To run a workflow with a session that uses a global shortcut, the PowerCenter Server must access both the repository in which the mapping is saved, and the global repository for the shortcut information. You enable this behavior by entering a repository user name and password in the server configuration parameter. This user name and password must exist in both of the following:
♦ ♦

The local repository with which the server is registered The global repository in the domain

To access the necessary information, this user name must have one of the following repository privileges in each repository:
♦ ♦ ♦

Use Workflow Manager with folder read and execute permissions Workflow Operator with folder read permission Super User privilege

Creating a Global Shortcut

193

Working with Shortcuts
Once you create a shortcut, you can reuse it in the folder as often as necessary. When you edit an object referenced by a shortcut, the Designer does not automatically validate mappings using shortcuts to the object. Some changes might invalidate mappings, such as deleting a port or changing the port datatype, precision, or scale. When a mapping is invalid, the PowerCenter Server cannot run the session. When editing a referenced object, use the View Dependencies features in the Repository Manager to determine which mappings contain shortcuts to the object. To ensure mappings are valid, open and validate the mapping. When validating a mapping, make sure you have the most recent version of the mapping. For details on viewing dependencies in the Repository Manager, see “Viewing Object Dependencies” on page 37. You can also view object dependencies in the Designer. For details on viewing dependencies in the Designer, see “Using the Designer” in the Designer Guide.

Refreshing Shortcut Properties
When working with shortcuts, it is critical to ensure you have the most recent version of the local or global shortcut in your workspace. If you launch the Designer, then drag a shortcut, or a mapping or mapplet using a shortcut, into the workspace, you view the current version of the object the shortcut references. However, if another user then edits and saves changes to the referenced object, the shortcut displayed in your workspace is no longer an accurate description of the referenced object. Therefore, when working in this type of environment, be sure to update your view of local and global shortcuts. The PowerCenter Server always uses the latest version of a referenced object. When the PowerCenter Server starts a session containing a shortcut, it accesses the repository to retrieve the mapping. If the mapping contains a shortcut, the PowerCenter Server accesses the repository for details about the original object.

Updating Views of Global and Local Shortcuts
The Designer updates properties for a global or local shortcut when it retrieves object information from the repository. If you think the original object referenced by a global or local shortcut has changed, you can refresh your view of the shortcut by performing one of the following:

Open metadata. When you drag an object into the Designer workspace, the Designer retrieves the object from the repository. If the object is a shortcut or contains a shortcut, the Designer retrieves and displays the most recent version of the shortcut. For example, if you open a folder to view a shortcut to a source or a mapping using that shortcut, the Designer displays the most recent version of the source.

194

Chapter 7: Local and Global Shortcuts

Note: When possible, the Designer uses information in memory. If the mapping was open

on your client machine, the Designer might display the version in memory rather than accessing the repository for the latest version. To ensure you have the most recent version, perform one of the following in addition to opening metadata.

Revert to saved. When you use the Designer menu command, Edit-Revert To Saved, the Designer accesses the repository to retrieve the last-saved version of the object. If you select a shortcut or a mapping using a shortcut, then choose Edit-Revert To Saved, the Designer displays the last-saved version of the object in the workspace. Close the folder or close all tools. To ensure you have correct shortcut information, you can clear the Designer memory by closing the folder or closing all tools (Repository-Close All Tools) then reopening the folder or tool.

For example, a mapping includes a shortcut named Shortcut_To_FIL_InsertChanged. This shortcut points to a reusable transformation named FIL_InsertChanged. Another user edits the filter condition in the original transformation, FIL_InsertChanged, and saves changes to the repository. When you open the mapping in the Designer, it retrieves the mapping from the repository. It also retrieves information for Shortcut_To_FIL_InsertChanged (and any other shortcuts used in the mapping). To validate the mapping, choose Mappings-Validate. However, if the mapping is already in memory, the Designer uses the version in memory. To ensure you have the correct version, choose Edit-Revert to Saved. Designer displays the mapping with the latest shortcut properties. To validate the mapping, choose MappingsValidate.

Copying a Shortcut
You can copy a shortcut to other folders. When the Designer copies a shortcut, it creates another shortcut in the new folder. The new shortcut points to the original object used by the original shortcut. The Designer cannot copy a shortcut (resulting in another shortcut), when it cannot find the object the shortcut references. This might occur if, for example, you copy a local shortcut from one repository to an unrelated repository. When the Designer cannot successfully copy a shortcut, it creates a copy of the shortcut object. The copy of the shortcut object is identical to the original object the shortcut references. Unlike an actual shortcut, the copy will not inherit any changes to the original object. You can use the copy of the shortcut as you would the original object. However, if the object is a source definition, you might need to rename the source definition.

Working with Shortcuts

195

Table 7-1 lists the results of copying global and local shortcuts to different repositories:
Table 7-1. Copying Global or Local Shortcuts Shortcut Type Local shortcut Local shortcut Local shortcut Global shortcut Global shortcut Local shortcut Local shortcut Shortcut Location Standalone repository Local repository Local repository Local repository Local repository Global repository Global repository Copied to Another folder, same repository Another folder, same repository Different local repository, same domain* Different local repository, same domain* Different repository, different domain* Local repository, same domain Different repository, different domain* Designer Creates Local shortcut to original object Local shortcut to original object Copy of the shortcut object Global shortcut to original object Copy of the shortcut object Global shortcut to original object Copy of the shortcut object

* To avoid losing metadata during the copy, the code pages of both repositories must be compatible.

For example, if you copy a shortcut named Shortcut_to_Employees from one standalone repository to another, the Designer creates a new source definition in the destination folder named Shortcut_to_Employees. This source definition is a copy of the original shortcut, but is not a shortcut. When you use the source definition in a mapping, the default SQL used to extract data from the source defines the source as Shortcut_to_Employees. If the source table is named Employees in the source database, you must rename the source definition (Employees) or enter a SQL override for the source qualifier connected to the source definition (renaming the source table Employees) for the PowerCenter Server to extract source data. For example, the fourth row of the table indicates when you copy a global shortcut (a shortcut to an object in a global repository) from one local repository to another local repository in the same domain, the Designer creates a global shortcut to the object in the global repository.

Renaming Source Qualifiers to Shortcut Sources
By default, shortcuts are named after their original object, Shortcut_To_ObjectName. If you create a shortcut to a source, and you have enabled the Mapping Designer option to automatically create source qualifiers, the Mapping Designer creates a source qualifier based on the source name. Therefore, if you do not change the name of the source shortcut, the resulting source qualifier is named SQ/ESQ/NRM_Shortcut_To_SourceName. Despite the name, however, the source qualifier is not a shortcut.
Tip: If names of source qualifiers automatically created for shortcut sources cause confusion,

you might want to rename those source qualifiers.
196 Chapter 7: Local and Global Shortcuts

Tips
The following suggestions can extend the capabilities of shortcuts. Keep shared objects in centralized folders. This keeps maintenance simple. This also simplifies the process of copying folders into a production repository. Only create shortcuts to finalized objects. Changes to an object referenced by shortcuts can invalidate the mappings or mapplets using the shortcut, as well as any sessions using these objects. To avoid invalidating repository objects, only create shortcuts objects in their finalized version. After editing a referenced object, make sure affected mappings are still valid. If you need to edit an object referenced by a shortcut, use the Analyze Dependencies feature in the Repository Manager to view affected mappings. After editing the object, see if your changes invalidate the listed mappings. To ensure a mapping is valid, open and validate it in the Designer. Refresh views of shortcuts when working in a multiuser environment. To refresh a shortcut in the workspace, choose Edit-Revert To Saved. You can also use Repository-Close All Tools in the destination folder then reopen the workspace.

Tips

197

Troubleshooting
The solutions to the following situations might help you with local and global shortcuts. The following message appears in the Designer status bar when I try to create a shortcut: “The selected folder is not open.” You are trying to create a shortcut from a shared folder to a folder that is not open. Open the destination folder (by opening at least one tool in the folder or by choosing Folder-Open) before creating the shortcut. When I try to create a shortcut, the Designer creates a copy instead. This can occur when one of the following is true:

The object is not saved in the repository. You can only create shortcuts to objects that are already in the repository. Save the object to the repository, then try creating the shortcut again. You are trying to create a shortcut for an object in a non-shared folder. You can only create shortcuts to objects in shared folders. You are holding down the Ctrl key when dragging the object. To create a shortcut, drag the object without holding down any additional keys. You are trying to create a shortcut between two local repositories, or between two repositories that are not in the same domain. You can only create a shortcut between repositories in the same domain. In addition, you can only create a shortcut in a local repository, referencing an object in a global repository. You cannot create a shortcut in a global repository that references an object in the local repository. You are dragging an object from a shared folder in the global repository to a folder in the local repository, but you are connecting to the repositories separately. To create a global shortcut, you must connect to one repository, then connect to the second repository through the first repository.

♦ ♦ ♦

I cannot connect to my global repository through my local repository to create a global shortcut (but I can connect to both separately). This can occur if you do not have the same user name and password in both repositories.

198

Chapter 7: Local and Global Shortcuts

Chapter 8

Working with Versioned Objects
This chapter includes the following topics:
♦ ♦ ♦ ♦ ♦

Overview, 200 Working with Version Properties, 203 Tracking Changes to Versioned Objects, 208 Checking Out and Checking In Objects, 211 Deleting and Purging Versioned Objects, 215

199

You can check out an object to reserve it while you edit the object. You can perform the following tasks when you work with a versioned object: ♦ ♦ ♦ ♦ 200 Chapter 8: Working with Versioned Objects .Overview If you have the team-based development license. Track changes to an object. A repository enabled for versioning can store multiple versions of the following objects: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Sources Targets Transformations Mappings Mapplets Sessions Tasks Workflows Worklets Session configurations Schedulers Cubes Dimensions View object version properties. You can delete an object from view and continue to store it in the repository. You can view a history that includes all versions of a given object. and prepare them for deployment to a production environment. you can configure the repository to store multiple versions of objects. the repository increments the version number by one and stores a new version of the object in the repository database. Each versioned object has a set of version properties and a status. This allows you to determine changes made to an object over time. track changes to those objects. Each time you check in an object. deleted objects. and compare any version of the object in the history to any other version. You can also configure the status of a folder to freeze all objects it contains or make them active for editing. the repository saves a new version of the object and allows you to add comments to the version. If you want to permanently remove an object version. or undelete. Object versioning allows you to store copies of previous versions of objects in development. Delete or purge the object version. Check the object version in and out. When you check in an object. or you can upgrade an existing repository to support versioned objects. you can purge it from the repository. You can also find objects checked out by yourself and other users. You can configure a repository for versioning when you create it. A versioned repository assigns multiple version numbers to versions of the same object. You can recover.

For more information on working with labels. Sample Scenario Suppose your environment includes a development repository and a production repository. and transformations. noting that it is the initial version of the mapping. it disappears from view in the Navigator window. Creating the Initial Version You use the Designer to create a mapping. retain older versions. and freeze the folder when you are finished with development to prevent further changes to the objects it contains. You purge all versions of the transformation. You do not need to use this transformation any more. and Workflow Manager.You can also apply labels to versioned objects. run queries to search for objects in the repository. and include versioned objects in deployment groups. you check it in to commit changes to a new version. Overview 201 . Each time you check in the mapping. While you are working with the mapping. When you delete the transformation. you check it in to the repository. target definition. You create and test metadata in the development repository. you want to exclusively edit objects. but the repository retains all versions of the transformation in the repository database. While working in the development repository. Other users are unable to edit the objects you have checked out. the repository assigns it version number one. Deleting and Purging an Object You want to remove a transformation instance from the mapping. When you finish editing the mapping. the repository creates a new version and increments the version number by one. Designer. You also include comments with the checked in version. You can perform these tasks in the Repository Manager. The first time you check in the object. Creating Successive Versions After creating a session and workflow and testing the initial version of the mapping. and then copy it to the production repository. including source definition. and deployment groups. permanently removing them from the repository and freeing up space in the repository database. When the mapping is ready to test. queries. the repository creates a new version of the object and assigns it a version number. you edit the mapping based on the results of your tests. see “Grouping Versioned Objects” on page 217. the repository locks the object for your use. When you check in the mapping.

You can view objects you and other users have checked out. Viewing Results View Windows You can query the repository for information about versioned objects. see “Working with Deployment Groups” on page 236. The deployment group specifies objects in the development repository you want to put into production. For more information about viewing checked out objects. View object dependencies to see the impact of changing or deleting an object. see “Tracking Changes to Versioned Objects” on page 208. Object queries. Object histories allow you to see the changes made to the object. Figure 8-1 shows the Results View Windows List: Figure 8-1. Freezing the folder prevents other users from checking out objects. For more information about viewing object queries. You can view results for the following types of versioned objects: ♦ Object dependencies. For more information about viewing object dependencies. You choose to freeze the folder and allow deployment of objects in the folder. see “Working with Object Queries” on page 224. ♦ ♦ ♦ To switch between open results view windows. see “Checking Out and Checking In Objects” on page 211. a query locates the object in the repository and includes it in a dynamic deployment group. Results View Windows List 202 Chapter 8: Working with Versioned Objects . For more information about viewing object histories. Object histories. Checked out objects. Later.Freezing a Folder After you finish developing and testing your metadata. An object query allows you to search for versioned objects in the repository that meet conditions you specify. you decide to freeze the folder. choose Window-Results View List. For more information about creating deployment groups. see “Viewing Object Dependencies” on page 37.

or Repository Manager to view the version properties of an object. To access the object properties. In a non-versioned repository. the Properties dialog box only displays the Object Status tab. Viewing Version Properties You can use the Designer. Workflow Manager. the Properties dialog box for a versioned object has the following tabs: Object.Working with Version Properties When you enable version control in a repository. Version. Working with Version Properties 203 . see “Purging a Version” on page 216. select the object in the Navigator and choose View-Properties. different versions of the same object may have different names. The repository assigns each copy. the repository creates a new version and increments the version number by one. the Navigator and workspace always display the latest version of an object. Or. You can view the version history of an object or create a query to search for previous versions of an object. Labels. and Object Status. Each time you check in an object. of the object a version number. To conserve space. By default. you can purge older versions you no longer need from the Repository Manager. For more information on purging objects. You can also view the current object version number and whether the object is checked out. right-click the object in the Main window or Navigator and choose Properties. you allow the repository to store multiple copies of the same object as you make changes and save it. Object Properties The Object tab of the Properties dialog box shows the object properties. labels applied to the version. and the status of the object in the Properties dialog box. Every version of an object takes up approximately the same amount of space in the repository database. or version. Object properties are associated with the object when you create it. You can view the version properties. If you rename an object during development. In a versioned repository.

Object Properties Version Properties On the Version tab. and any comments associated with the version.Figure 8-2 shows the Object tab in the Properties dialog box: Figure 8-2. This includes the version number. you can view properties that are specific to the latest version of the object. the user and host that created the version. Figure 8-3 shows the Version tab in the Properties dialog box: Figure 8-3. Version Properties 204 Chapter 8: Working with Versioned Objects .

You can also change the object status on this tab from the Repository Manager. For each label. and comments associated with the label. Figure 8-4 shows the Labels tab of the Properties dialog box: Figure 8-4. you can view the current status of the object. you can view all labels applied to the object. the time the label was applied. see “Working with Labels” on page 219.Labels Properties On the Labels tab. you can also view the name of the user who applied the label. Labels Properties For more information on creating and applying labels. Working with Version Properties 205 . Object Status Properties On the Object Status tab.

Each version of an object maintains its own status. deployment group contents. Changing Object Status You can change the status of individual repository objects from the Repository Manager. You can manually change the status of an object from the Repository Manager. Deleted. For more information on deleting objects and recovering deleted objects. You can recover a deleted object by changing its status from Deleted to Active. This is true even if you delete the object. You can change the status of an object when you view object history.Figure 8-5 shows the Object Status tab of the Properties dialog box: Figure 8-5. You can find a deleted object through a query. object dependencies. see “Deleting and Purging Versioned Objects” on page 215. The object is marked as deleted and is not visible in the Navigator. perform the following steps. You and other users can edit the object. To change object status. the repository removes the object from view. query results. No other objects can use or reference the deleted object. You must check in the object for other users to view changes to the object status. Object Status Properties The object status defines what actions you and other users can perform on the object. or checkouts. An object can have one of the following statuses: ♦ ♦ Active. 206 Chapter 8: Working with Versioned Objects . If you change the status of an object from Active to Deleted.

2. choose a status for the object. In the Properties dialog box. This status allows users to check out versioned objects in the folder. You can also change the status of folders in the repository. edit the folder in the Repository Manager. Allow Deploy to Replace. Click OK. You cannot deploy objects into this folder. Select the latest version of the object. The object properties appear. Each of the Frozen statuses allows the Repository Manager to add objects in the folder to a deployment group. you might change the status of a folder from Active to Frozen Allow Deploy to Replace to ensure that copy deployment group operations successfully complete. To change the folder status. For more information. 3. Note: Before you change the status of a folder. In the production repository.To change the status of an object: 1. Frozen. Deployment into the folder creates new versions of the objects. Working with Version Properties 207 . 4. you might change the status of a folder from Active to Frozen Do Not Allow Deploy to Replace in a code freeze scenario. This status does not allow users to check out objects in the folder. Suppose the environment contains a developing repository for creating and testing metadata and a production repository for running the workflows and sessions. you might want to verify that other users do not have objects in the folder checked out. right-click the object in the Navigator and choose Versioning-View History. The Frozen Allow Deploy to Replace status prevents other users from checking out objects in the folder. 6. In the development repository. but allows a copy deployment group operation to create new versions of objects. This prevents other users from checking out objects in the folder and creating new versions. see “Folder Properties” on page 168. Changing Folder Status Changing the folder status allows you to control what operations you can perform on all versioned objects that the folder contains. You can configure a folder with one of the following statuses: ♦ ♦ ♦ Active. 5. choose the Object Status tab. Do Not Allow Deploy to Replace. This status does not allow users to check out objects in the folder. In the Repository Manager. Frozen. and choose Tools-View Properties. The Frozen Do Not Allow Deploy to Replace status prevents other users and copy deployment group operations from creating new versions of the objects. You might change the status of a folder to serve different purposes depending on the configuration of your environment and your development processes. The View History window appears. Check in the object for other users to view changes to the status. From the Object Status list.

modify. You can view the history of a versioned object in the Designer. The object history allows you to view user changes to an object. To accomplish tasks like these. and check it in. 208 Chapter 8: Working with Versioned Objects . the View History window displays the object version history. If you or another user purges a version from the repository. the PowerCenter Client allows you to view a history of all of the versions of an object stored in the repository. going back to the initial version. you may want to view the object version history. Viewing Object History The history of an object is a record of all of the versions of an object stored in the repository. right-click the object in the Main window or the Navigator and choose Versioning-View History. Select the object in the workspace and choose Versioning-View History from the menu. Use the following methods to view the object version history in the Designer or Workflow Manager: ♦ ♦ ♦ Right-click the object in the Navigator and choose Versioning-View History. and comments associated with and labels applied to each version. the object history retains a record of the version in the object history and specifies the user who purged the version. It stores multiple versions of an object as you check out. When you choose View History. To view object version history in the Repository Manager. Troubleshoot changes in functionality between different versions of metadata. version number one. the date and time of changes. You can also compare two versions of an object displayed in the history. You may want to do this for the following reasons: ♦ ♦ Determine what versions are obsolete and no longer necessary to store in the repository. As the number of versions of an object grows. Right-click the object in the workspace and choose Versioning-View History. and Workflow Manager. Repository Manager.Tracking Changes to Versioned Objects A repository enabled for version control maintains an audit trail of version history.

To save the version history to an HTML file. See “Viewing Version Properties” on page 203. choose File-Save to File. View version properties. See “Viewing Object Dependencies” on page 37. Tracking Changes to Versioned Objects 209 . View History Window Table 8-1 lists additional tasks you can perform from the View History window: Table 8-1. Save object version history to a file. see “Exporting and Importing Objects” on page 263. Description See “Comparing Versions” on page 210. Undo check out or check in. View object dependencies. Export the version to an XML file. Export object version to an XML file. See “Deleting and Purging Versioned Objects” on page 215. Apply or remove a label.Figure 8-6 shows the View History window: Figure 8-6. See “Checking Out and Checking In Objects” on page 211. Tasks Available in View History Window Task Compare versions. For more information on exporting and importing objects. See “Working with Labels” on page 219. Purge a version. See “Working with Deployment Groups” on page 236. Add version to deployment group.

To compare two versions of an object. Or. select the versions that you want to compare in the object history and choose Tools-Compare-Selected Versions. 210 Chapter 8: Working with Versioned Objects . you can compare two selected versions of the object. When you compare two versions of an object. the PowerCenter Client displays the attributes of each object. select one version and choose Tools-Compare-Previous Version. The interface for comparing two versions of the same object is the same as the interface for comparing two different objects. This allows you to view all of the differences between the objects. see “Comparing Repository Objects” on page 45.Comparing Versions When you view the version history of an object. For information on comparing objects.

Checking Out and Checking In Objects When you work with versioned objects. Search for objects checked out by yourself. you check out an object each time you want to change it. You can check out and check in objects in the Designer and the Workflow Manager. the Repository Agent checks in the non-reusable Aggregator transformation implicitly. Workflow Manager. You can choose to narrow or broaden your search for checked out objects in the following ways: ♦ ♦ By folder. if you have a mapping that contains a non-reusable Aggregator transformation. see “Using the Designer” in the Designer Guide or “Using the Workflow Manager” in the Workflow Administration Guide. If you disconnect from the repository without saving a checkout. This allows you to reserve an object while you work on it. or if you need to check in all of the objects you have checked out. Use the following steps as a guideline when you search for checked out objects: To view checkouts: 1. You might want to view checkouts to see if an object is available for you to work with. and check it in when you want to commit your changes to the repository. No other repository users can edit the object while you have it checked out. When you work with composite objects. When you check in the parent mapping. choose Versioning-Find Checkouts. Viewing Checked Out Objects You can view objects you and other users have checked out. Checking Out and Checking In Objects 211 . You cannot check out objects from the Repository Manager. By user. or search for objects checked out by all users in the repository. For example. You must check out the object again when you reconnect. Checking Out Objects When you open an object in the workspace. you cannot check in the Aggregator transformation individually. the Repository Server releases the write-intent lock on the object and you lose the changes you made to the object. the Repository Agent treats non-reusable objects as part of the parent object. Search for checkouts in the selected folder. or search all folders in the repository. so you cannot check in or out individual non-reusable objects. the repository obtains a write-intent lock on the object for you if no other user has checked it out. or Repository Manager. Checking in an object adds a new version to the object history. For more information on performing check outs. The Repository Agent reverts back to last checked-in version of the object. In the Designer.

The View Checkouts window appears. For more information. 2. Select options to narrow or broaden your search. see “Comparing Versions” on page 210. see “Viewing Version Properties” on page 203. The results depend on the options you select for the search. For more information.The Find Checkouts dialog box appears. and click OK.. View version properties. Specify folders. Specify users. 212 Chapter 8: Working with Versioned Objects . Table 8-2 lists additional tasks you can perform from the View Checkouts window: Table 8-2. Compare the selected checkout with the previous checked in version. View the object and version properties of the checkout. For more information.. Tasks Available in View Checkouts Window Task Compare versions.

View checkouts. so you cannot check in or out individual non-reusable objects. View query results. the Repository Agent treats non-reusable objects as part of the parent object.Table 8-2. View object history. you must check it out. For example. To undo a check out. To save the version history to an HTML file. The most recently checked in version of the object becomes the latest version of the object. Tasks Available in View Checkouts Window Task View object dependencies. View dependencies for the selected checkout. Save object version history to a file. the Repository Agent checks in the non-reusable Aggregator transformation implicitly. For more information. You can undo a check out from the View Checkouts window. When you undo a checkout. if you have a mapping that contains a non-reusable Aggregator transformation. Check in or undo check out for the selected unmodified checkouts. For more information. If you want to modify the object again. such as a mapping. select the checkout object and choose Tools-Undo Checkout. You can undo a check out from the View History window.. Undoing a Checkout You can undo a checkout. If you want to check in all objects used in a mapping. Undo check out or check in. the repository creates a new version of the object and assigns it a version number. When you check in an object. For more information on exporting and importing objects. The Repository Agent does not check in reusable objects when you check in a composite parent object. Export the version to an XML file. When you check in the parent mapping. See “Undoing a Checkout” on page 213 and “Checking In Objects” on page 213. When you work with composite objects. the repository releases the write-intent lock on the object and removes the checkout version from the repository. View the object version history for the selected checkout. For more information.. Export object version to an XML file. you can check it in and commit the changes to the repository. see “Viewing Object History” on page 208. you cannot check in the Aggregator transformation individually. Checking Out and Checking In Objects 213 . You can undo a checkout from the Query Results window when you search for object dependencies or run an object query. you must check in reusable objects separately. Checking In Objects When you finish making changes to a checked out object. see “Viewing Object Dependencies” on page 37. choose File-Save to File. The repository increments the version number each time you check in an object. You can undo a check out when you review the results of the following tasks: ♦ ♦ ♦ View object history. see “Exporting and Importing Objects” on page 263.

You can check in objects from the Designer. or Repository Manager. For more information on performing a check in. 214 Chapter 8: Working with Versioned Objects . Workflow Manager.You must save an object before you can check it in. see “Using the Designer” in the Designer Guide or “Using the Workflow Manager” in the Workflow Administration Guide.

Change the status of the object you want to recover from Deleted to Active. Recovering a Deleted Object You can recover a deleted object by changing the object status to Active. You must use the Repository Manager to recover a deleted object. The repository retains the metadata information for all versions of a deleted object. the repository changes the object status to Deleted. This makes the object visible in the Navigator or the workspace. you must rename the object. that contains non-reusable objects. You must check in deleted objects for other users to view the changed status. Create and run a query to search for deleted objects in the repository. Deleting and Purging Versioned Objects 215 . see “Changing Object Status” on page 206. For more information on creating and running queries. the repository removes the object from view in the Navigator window or in the workspace. the Repository Server treats the non-reusable object as part of the parent object and deletes it. If you want to permanently remove a version of an object from the repository. Deleting a Versioned Object You can delete a versioned object in the Designer. Workflow Manager. or add conditions to narrow your search. the repository creates a new version of the object and changes the object status to Deleted. 2. you permanently remove the object from the repository. you must purge it from the Repository Manager.Deleting and Purging Versioned Objects When you delete an object in a versioned repository. You can recover a deleted object by changing its status to Active. and removes the object from view in the workspace and the Navigator. You can choose to search for all objects marked as deleted. If the recovered object has the same name as another object that you created after you deleted the recovered object. For information on changing the status of an object. but does not delete the object or any object version from the repository database. When you delete a versioned object. see “Working with Object Queries” on page 224. Use the following process as a guideline when you recover a deleted object: 1. If you want to permanently remove the object from the repository. You can use a query to search for deleted objects. When you delete a composite object. 3. You might want to purge a version if you no longer need to retain the version for development reasons and you want to reduce the size of the repository in the database. you must purge the version from the Repository Manager. If you purge all versions of an object. or Repository Manager. Instead. such as a mapping.

When you purge an object version. You can also purge multiple versions of an object from the repository at the same time. the name of the previous version changes to src_Records. Choose Tools-Purge Object Version. the repository does not maintain or keep a record of the purge. select it from the object version history in the Repository Manager. you must purge all versions. To purge a version. the prior version takes the name of purged version. You can purge a version from the View History window. If you purge the latest version. If you purge a version earlier than the latest version.Tip: To query the repository for deleted objects. you must purge it from the Repository Manager. If you purge the latest version. and the prior version has a different name. The latest version is named src_Records. If you purge the latest version. include the following condition in your query: Object Status Is Equal To Deleted Purging a Version To permanently remove an object version from the repository. the repository maintains a record of the purge in the object history. 216 Chapter 8: Working with Versioned Objects . you have the source src_Records. For example. To completely purge an object from the repository. the repository permanently removes it from the repository database. but the name of the previous version in the history is src_RecordsWeekly.

219 Working with Object Queries. 218 Working with Labels.Chapter 9 Grouping Versioned Objects This chapter includes the following topics: ♦ ♦ ♦ ♦ Overview. 224 Working with Deployment Groups. 236 217 .

and deployment groups to identify versioned objects that meet a certain criteria. see “Working with Labels” on page 219. Use labels to track versioned objects. Create deployment groups. see “Working with Object Queries” on page 224. For example. This populates the deployment group with a new set of objects each time you deploy the group. You want to deploy the objects that you test each day. and deployment groups to locate and group objects for deployment. You can apply a label to a group of objects across repositories in a domain. You can deploy objects when you move from test to production. For information about labels. Workflow Manager. you create a deployment group to identify objects for deployment to another repository. see “Working with Deployment Groups” on page 236. Finally. and then deploy it to the production repository. ♦ ♦ You can use labels. As you create objects. You use labels to associate groups of versioned objects in a repository. You create deployment groups to deploy objects to another repository within the domain. your environment includes a development repository and a production repository. You use queries to search for versioned objects in the repository. queries. Run queries. and Repository Manager. and deployment groups in the Repository Manager. You can create labels. For more information about deployment groups. While working in the development repository. You then create a query to locate all the objects that use the deployment label. For more information about queries. You create and test metadata in the development repository.Overview You can use labels. and you can group objects from the Designer. 218 Chapter 9: Grouping Versioned Objects . To do this. The query returns objects that reside in different folders in your development repository. you want to track the different versions of objects you create and deploy the latest versions of these objects to the production repository. You can group objects in the following ways: ♦ Apply labels. You might want to run a query to find objects to export or deploy. you create a dynamic deployment group that runs a query against the source database at deployment time. queries. or to compare versions. you assign a deployment label to those objects you have tested and are ready to deploy. queries.

you might want to apply a label to a group of objects to indicate that you tested the objects and are ready to deploy them. You can create and modify labels in the Label Browser. targets.Working with Labels A label is a versioning object that you can associate with any versioned object or group of versioned objects in a repository. For example. Or you can choose to apply the label to one object version when you need to limit the number of times users apply labels. Associate groups of objects for import and export. You can apply the label to multiple versions of an object. You lock a label to limit access to the label or ensure you apply a label only once. You can also choose to lock the label. Improve query results. mappings. you might apply a label to sources. Creating and Editing Labels When you create or edit a label. specify the number of times users can apply the label. choose Versioning-Labels from the Repository Manager to open the Label Browser. To create a label. and sessions associated with a workflow so that you can deploy the workflow to another repository without breaking any dependency. From the Repository Manager. Or you can specify that you can apply the label to one version of the object only. which prevents other users from editing or applying the label. Once you apply the label. For example. you can lock it to prevent users from editing the label or applying the label to other objects. choose Versioning-Labels to browse for a label. Associate groups of objects for deployment. You may want to apply labels to versioned objects to achieve the following results: ♦ ♦ ♦ ♦ Track versioned objects during development. You can choose to apply the label to multiple object versions when you do not need to limit label applications. you can specify the label name. Working with Labels 219 . and add comments.

or you can choose to lock the label to prevent other users from editing or applying the label. When you edit a label object.Figure 9-1 shows the Label Browser: Figure 9-1. Label Browser Note: Click a column heading to sort labels by that column. You can lock the label when you edit it. Label Editor Options Enter a name for the label object. Figure 9-2 shows the Label Editor options: Figure 9-2. 220 Chapter 9: Grouping Versioned Objects . Lock the label to prevent users from editing or applying the label. Select New to open the Label Editor. you can edit the name or the comments associated with it. Select from the options in the Label Editor to create a label object.

For example. Or. When you run an object query. Or. you can apply labels by selecting Versioning-Apply Labels in the Repository Manager. The Repository Server applies labels to sources. the Repository Server permanently deletes all instances of the label that have been applied to versioned objects. mappings. you can choose to label all children objects. or Repository Manager: ♦ ♦ View the history of an object. if you want to group dependencies for a workflow. When you view the history of an object. Figure 9-3 shows the Apply Label dialog box: Figure 9-3. Workflow Manager. In the Repository Manager. choose Tools-Labels-Apply Label from the Query Results window. Or. and tasks associated with the workflow. Create an object query. you can apply the label to dependent objects in a global repository from a local repository. you can apply the label to dependent objects in all registered local repositories in a global repository. which allows you to apply labels to groups of objects. if you deploy objects to multiple repositories. Apply Label Dialog Box Working with Labels 221 . You can select any label you have execute permissions for. targets.When you delete a label. you open the Label Wizard. Applying Labels You can apply one or more labels to any versioned object in the repository. choose ToolsLabels-Apply Label from the View History window. You can apply labels to objects when you complete one of the following tasks from the Designer. When you deploy labels to global shortcut dependencies. you can apply the label to global shortcut dependencies. You can also apply the label to selected dependent objects.

You can apply labels to the following groups of objects: ♦ ♦ ♦ One or more objects in a folder All objects in one or more folders All objects in one or more selected repositories 222 Chapter 9: Grouping Versioned Objects . such as Label all children. Select one of the previous options. Applies the label to the source object containing the primary key referenced by the foreign key in the selected source object. you can choose to move the label to the selected version of the object. You cannot apply labels to checked out objects. Label all Children Label all Parents Primary/Foreign Key Dependencies Global Shortcut Dependencies Preview When you apply a label to parent or child objects. Applies the label to all repository objects that the selected object uses. the Repository Agent applies the label to objects that are checked in to the repository.Table 9-1 describes the label options: Table 9-1. Label Options and Description Label Options Move Label Description Moves the label from a previous version of the object to the latest version of the object. Previews the group of objects that the Repository Agent applies the label to when you apply labels to dependent objects. the timestamp when the label was applied. To open the label wizard. Applies the label to all repository objects that use the selected object. view an object history. You can view the label owner. The Repository Agent applies the label to global shortcuts that meet the conditions you specify. you can use the Label Wizard to apply a label to groups of objects. or view object properties. Applying Labels to Groups of Objects In the Repository Manager. If the Repository Server detects the label is applied to another version of the same object. and select Global Shortcut dependencies. When you search for an object. choose Versioning-Apply Labels and click Next. Applies the label to global shortcut objects. and the comments you entered when applying the label to the object. you can view metadata for the labels applied to an object.

Working with Labels 223 . You can select Preview to view the objects the Repository Agent labels. For more information about label options. After you select objects to label. browse to select the label to apply and choose label options.Figure 9-4 shows the Apply Label Wizard: Figure 9-4. see Table 9-1 on page 222. Apply Label Wizard Select the folder or folders containing objects you want to label. Label selected objects. Label all objects in a selected repository.

Working with Object Queries
You use an object query to search for versioned objects in the repository that meet specified conditions. When you run a query, the repository returns results based on those conditions. You may want to create an object query to perform the following tasks:

Track objects during development. You can add Label, User, Last saved, or Comments parameters to queries to track objects during development. For more information, see “Query Parameters” on page 227. Associate a query with a deployment group. When you create a dynamic deployment group, you can associate an object query with it. For more information, see “Working with Deployment Groups” on page 236. Find deleted objects you want to recover. For more information about recovering deleted items, see “Recovering a Deleted Object” on page 215. Find groups of invalidated objects you want to validate. For more information about validating groups of objects, see “Validating Multiple Objects” on page 42.

♦ ♦

The Query Browser allows you to create, edit, run, or delete object queries. You can also view the list of available queries in the Query Browser. Choose Versioning-Queries to browse for a query. You can also configure permissions for the query from the Query Browser. For more information about configuring query permissions, see “Permissions” on page 148. Figure 9-5 shows the Query Browser:
Figure 9-5. Query Browser

Edit a query. Delete a query. Create a query. Configure permissions. Run a query.

Note: Click a column heading to sort queries by that column.

224

Chapter 9: Grouping Versioned Objects

In the Query Browser, select New or Edit to open the Query Editor. You can create, validate, and run a query in the Query Editor. Figure 9-6 shows the Query Editor:
Figure 9-6. Query Editor Save query. Validate query. Run query. Add a logical operator. Add a query condition.

Specify query conditions.

When you create a query, you can make it personal or shared. You can run personal object queries you own and any shared object query in the repository.

Configuring Query Conditions
Each query condition consists of a parameter, an operator, and a value. You can add, cut, copy, paste, and move query conditions. Each time you add a query parameter, you specify an operator and a value. You can view the valid operators and values for each parameter when you add the parameter to a query. You may need to configure multiple query conditions to effectively narrow your results. You can use the AND or OR logical operators to add multiple query conditions. For example, you might want to deploy a group of objects with the Deployment_2 label, but you also want to ensure that the objects were saved after a particular date.

Working with Object Queries

225

Figure 9-7 shows a query with multiple conditions:
Figure 9-7. Query with Multiple Conditions Add, edit or move query conditions and operators.

Add logical operators. Add multiple query conditions.

When the Repository Agent processes a parameter with multiple conditions, it processes them in the order you enter them. To receive expected results and improve performance, enter parameters in the order you want them to run. If you nest several parameters within a query, the Repository Agent resolves each inner parameter condition until it can resolve the outer parameter condition. For example, when you run the following query with nested conditions, the Repository Agent resolves the innermost conditions and the next outer conditions until it resolves all parameter conditions:
5 2 1

4

3

226

Chapter 9: Grouping Versioned Objects

Query Parameters
You build queries using query parameters. Each query parameter uses operators and accepts values. Table 9-2 describes the query parameters and the valid operators and values for each parameter:
Table 9-2. Query Parameters and Values Parameter AND Business Name Description Joins query conditions or groups of query conditions. Displays sources and targets based on their business names. For example, the query Business Name is equal to Informatica returns sources and targets that contain the Informatica business name, and filters out all other objects. The query Business Name is not equal to Informatica, filters out sources and targets with the Informatica business name and keeps all other objects. The Business Name query does not return shortcuts to objects that contain business names. Displays objects that are checked in at, before, or after a specified time or within a specified number of days. Valid Operator None Contains Does Not Contain Does Not End With Does Not Start With Ends With Is Equal To Is Not Equal To Is Not One Of Is One Of Starts With Accepted Values None String

Check-in time

Greater Than Is Between Less Than Is Not Between Within Last (days) Contains Does Not Contain Does Not End With Does Not Start With Ends With Is Equal To Is Not Equal To Is Not One Of Is One Of Starts With Greater Than Is Between Less Than Is Not Between Within Last (days) Greater Than Is Between Less Than Is Not Between Within Last (days)

Date/time Numeric

Comments

Displays comments associated with a source, target, mapping or workflow.

String

Deployment Dispatch History

Displays objects deployed to another folder or repository through deployment groups in a given time period.

Date/time Numeric

Deployment Receive History

Displays objects deployed from another folder or repository using deployment groups in a given time period.

Date/time Numeric

Working with Object Queries

227

Table 9-2. Query Parameters and Values Parameter Folder Description Displays objects in a specified folder. Valid Operator Is Equal To Is Not Equal To Is Not One Of Is One Of Where (Value 1) depends on (Value 2) Accepted Values Folder name

Include Children

Displays child dependent objects. For more information about object dependencies, see “Viewing Object Dependencies” on page 37.

Any Source Definition Target Definition Transformation Mapplet Mapping Cube Dimension Task Session Worklet Workflow Scheduler SessionConfig Any Source Definition Target Definition Transformation Mapplet Mapping Cube Dimension Task Session Worklet Workflow Scheduler SessionConfig Any Source Definition Target Definition Transformation Mapplet Mapping Cube Dimension Task Session Worklet Workflow Scheduler SessionConfig N/A

Include Children and Parents

Displays child and parent dependent objects. For more information about object dependencies, see “Viewing Object Dependencies” on page 37.

Where (Value 1) depends on (Value 2)

Include Parents

Displays parent dependent objects. For more information about object dependencies, see “Viewing Object Dependencies” on page 37.

Where (Value 1) depends on (Value 2)

Include Primary/ Foreign Key Dependencies

Displays primary key-foreign key dependencies.

N/A

228

Chapter 9: Grouping Versioned Objects

Table 9-2. Query Parameters and Values Parameter Invalidated Status Label Description Displays objects invalidated due to changes to a child dependent object. Displays objects associated with a label or group of labels. Valid Operator Is Equal To Is Equal To Is Not Equal To Is Not One Of Is One Of Greater Than Is Between Less Than Is Not Between Within Last (days) Is Equal To Is Not Equal To Is One Of Accepted Values Is invalidated Is not invalidated Labels for which you have execute permissions Date/time Numeric

Last Saved Time

Displays objects saved at a particular time or within a particular time range.

Latest Status

Displays objects based on the object history. The query can return local objects that are checked out, the latest version of checked-in objects, or a collection of all older versions of objects. For more information about restoring deleted objects, see “Recovering a Deleted Object” on page 215. For more information about purging older versions of objects, see “Purging a Version” on page 216. Displays objects based on an extension name or value pair. You can use this query parameter to find non-reusable metadata extensions. The query does not return user-defined reusable metadata extensions. Displays objects based on the object name.

Checked-out Latest checked-in Older

Metadata Extension

Is Equal To Is Not Equal To

User-defined metadata domain Any vendor-defined metadata extensions

Object Name

Contains Does Not Contain Does Not End With Does Not Start With Ends With Is Equal To Is Not Equal To Is Not One Of Is One Of Starts With

String

Working with Object Queries

229

Table 9-2. Query Parameters and Values Parameter Object Type Description Displays objects based on the object type. For example, you can find all workflows in a specified folder. Valid Operator Is Equal To Is Not Equal To Is Not One Of Is One Of Accepted Values Cube Dimension Mapping Mapplet Scheduler Session Session Config Source Definition Target Definition Task Transformation Workflow Worklet Unused Used

Object Used Status

Displays objects that are used by other objects. For example, you can find mappings that are not used in any session. If any version of an object is used by another object, the query returns the most recent version of the object. This occurs even when the most recent version of the object is unused. The query does not return workflows or cubes, as these objects cannot be used by other objects. For more information about dependencies, see “Viewing Object Dependencies” on page 37. Displays objects based on shortcut status. If you select this option, the query returns local and global shortcut objects. Shortcut objects are considered valid regardless of whether the objects they reference are valid. Displays reusable or non-reusable objects. Displays objects checked in or checked out by the specified user.

Is Equal To

Shortcut status

Is Equal To

Is Not Shortcut Is Shortcut

Reusable Status User

Is Equal To Is One of Is Equal To Is Not Equal To Is Not One Of Is One Of Is Equal To Is Equal To Is One of

Non-reusable Reusable Users in specified repository

Valid Status Version Status

Displays valid, invalid, and invalidated objects. Displays objects based on deleted or non-deleted status.

Invalid Valid Deleted Not deleted

Note: Valid operators and values depend upon the tool you use to create and view queries.

230

Chapter 9: Grouping Versioned Objects

Validating and Saving a Query
After you create the object query and specify the conditions, you validate it. Select Validate to run the query validation. The Validate Query window displays the validation results. If the validation returns an error, review the error message and validate the query again. Once you validate the query, you can save it for later use. For example, if you regularly run an object query on checkin histories, you might want to save the object query so that you can easily run it again.

Invalid Queries
The query parameters you can view and use in the Query Editor are determined by the tool you use to create queries. When you create a query in one PowerCenter Client tool, the query may appear invalid when you open it in another tool. For example, you can view query parameters such a workflows, worklets, and sessions in the Workflow Designer. If you open a query that uses Workflow Designer parameters in the Designer, the query may appear invalid. For example, you create a query in the Workflow Manager using the following parameters.
♦ ♦

Object Type is equal to Workflow. Valid Status is equal to Invalid.

When you open the query in the Designer, the query appears invalid:
Workflow query invalidated in the Designer.

Queries can be invalidated when you use logical operators with the wrong number or kind of query conditions. For example, an AND logical operator requires at least one parameter to be valid. The following example shows a query that is invalid because the AND operator has no parameters:
The query is invalid because the logical operator requires parameters.

Working with Object Queries

231

Running a Query
After you create and validate the object query, you can run it. The Repository Agent queries the repository and displays the results of the query in the Query Results window. Figure 9-8 shows sample query results from the object query shown in Figure 9-7 on page 226:
Figure 9-8. Sample Query Results

From the Query Results window, you can complete tasks by selecting the object and choosing Tools. Table 9-3 lists additional tasks you can perform from the Query Results window:
Table 9-3. Tasks Available in Query Results Window Task View history. Compare versions. Validate multiple objects. Check in. Undo check out. Export to an XML file. Apply or remove a label. View object dependencies. Task Information See “Viewing Object History” on page 208. See “Comparing Versions” on page 210. See “Validating Multiple Objects” on page 42. See “Checking Out and Checking In Objects” on page 211. See “Checking Out and Checking In Objects” on page 211. See “Exporting and Importing Objects” on page 263. See “Working with Labels” on page 219. See “Viewing Object Dependencies” on page 37.

232

Chapter 9: Grouping Versioned Objects

Table 9-3. Tasks Available in Query Results Window Task View version properties. Add version to deployment group. Change object status. Purge a version. Save object version history to a file. Open object in a workspace. Task Information See “Viewing Version Properties” on page 203. See “Working with Deployment Groups” on page 236. See “Changing Object Status” on page 206. See “Purging a Version” on page 216. To save the version history to an HTML file, choose File-Save to File. Select this option to open an object in the workspace when the object type is compatible with the tool in which you run the query. For example, you can open a workflow in the Workflow Manager using this option.

For more information on managing versioned objects, see “Working with Versioned Objects” on page 199.

Viewing Query Results
By default, when you run an object query, the Repository Agent returns objects that meet the following criteria:
♦ ♦ ♦

Objects are the latest version, either local checkout versions or checked-in versions. Objects are reusable. Objects that are not deleted.

If you want to view deleted or older objects, you must specify these values in the query parameter. You can search for deleted objects using the Deleted value in the Version Status parameter. You can search for older versions of objects when you specify the Older value in the Latest Status query parameter.
Note: If you run a query without specifying query conditions, the query returns reusable

objects in the repository.

Sample Queries
The following sample queries illustrate how to create query conditions with different parameters, operators, and values.

Finding Recently Deployed Objects
The following query returns the latest checked-in version of objects deployed within the last seven days and are reusable or non-reusable:

Working with Object Queries

233

Finding Invalidated Mappings
The following query returns the latest checked-in version of objects that are invalidated and whose object type is mapping. The Designer or Workflow Manager invalidates a parent object when you modify a child object in such a way that the parent object may not be able to run. The query returns invalidations for composite objects such as mapplets, mappings, sessions, worklets and workflows:

Note: You can use the invalidated object query to search for invalidated objects and run a

validation on multiple objects. For information about validating multiple objects, see “Validating Multiple Objects” on page 42.

Finding Invalid Mappings
The following query returns the latest checked-in version of objects in the repository that are invalid and whose object type is mapping. The Designer or Workflow Manager invalidates a parent object when you modify a child object in such a way that the parent object may not be able to run.

Finding The Used Status of Objects
The following query returns the latest checked-in version of objects that are mappings and that are not used by any session:

Finding Older Versions of Objects
The following query returns objects that are mappings and that are older and that are checked in by the Administrator:

234

Chapter 9: Grouping Versioned Objects

To include reusable and non-reusable dependencies.Finding Object Dependencies The following query returns sources and targets in the Vendors folder that are dependent on the mapping. Mapping_deploy. To search for parent and child dependencies. Select source definitions and target definitions for Value 1 and select mapping for Value 2. choose to include children and parent dependencies. select both reusable and non-reusable dependency in Value 3: Working with Object Queries 235 .

You can complete the following tasks: ♦ ♦ ♦ ♦ Create or edit a deployment group. choose Versioning-Deployment Groups from the Repository Manager. deployment date. Deployment Group Browser Preview the objects in a deployment group. For more information. Dynamic. Configure permissions for a deployment group. and user who ran the deployment. For more information see “Permissions” on page 148. You can view the history of a deployment group. You populate the deployment group by manually selecting objects. You can run a query to preview the objects that the Repository Agent will deploy. You can create the following types of deployment groups: ♦ ♦ Static. View the objects in a static or dynamic deployment group. To work with deployment groups. View the history of a deployment group. View the history of a deployment group. You use the result set from an object query to populate the deployment group. 236 Chapter 9: Grouping Versioned Objects . including the source and target repositories. For more information. see “Creating and Editing a Deployment Group” on page 237. Figure 9-9 shows the Deployment Group Browser: Figure 9-9. Note: Click a column heading to sort deployment groups by that column.Working with Deployment Groups A deployment group is a versioning object that allows you to group versioned objects for deployment to a different repository. see “Viewing Deployment History” on page 237.

you add objects to a static group or associate an object query with a dynamic group. The name of the deployment group. Figure 9-10 shows the Deployment Group Editor: Figure 9-10. Choose a static or dynamic group. The date and time you deployed the group. Target repository. Source repository. Deployment group name. The repository where you deployed the group. Working with Deployment Groups 237 . select a deployment group in the Deployment Group Browser and choose View History. Select a query to associate with a dynamic deployment group.Creating and Editing a Deployment Group To create or edit a deployment group. and configure the options in the Deployment Group Editor. You can view the following information about groups you deployed: ♦ ♦ ♦ ♦ ♦ Date/time. The repository you deployed the group from. Once you create the deployment group. Viewing Deployment History To view the history of a deployment group. choose New or Edit from the Deployment Group Browser. The user name of the person who deployed the group. Deployment Group Editor Enter a name for the deployment group. User name.

then the repository object is not the same as the object in the deployment. 238 Chapter 9: Grouping Versioned Objects . To roll back a deployment: 1. you roll back all the objects in a deployment group that you deployed at a specific date and time. When you roll back a deployment. the Repository Agent notifies you of the object that caused the failure. The Repository Agent checks the object versions in the deployment run against the objects in the target repository. The rollback fails. 2. The rollback results display at the end of processing. Rolling back a deployment purges the deployed versions from the target repository. and attempt to roll back the original deployment. The rollback ensures that the check-in time for the repository objects is the same as the deploy time. You can initiate a rollback on a deployment as long as you roll back only the latest versions of the objects. see “Copying Folders and Deployment Groups” on page 241. Select a deployment to roll back. Rolling Back a Deployment You can roll back a deployment. create a new object with the same name. If the check-in time is different. Select a deployment group in the Deployment Group Browser and choose View History. Figure 9-11 shows the Deployment Group History: Figure 9-11. You cannot roll back part of a deployment. If any of the checks fail. This might occur if you rename a deployed object.For more information about deploying objects to repositories. Click Rollback. 3. Deployment Group History Initiate a rollback. The rollback also fails if the rollback process causes you to create duplicate object names.

and choose Versioning-View History. select the group of objects in the Navigator and drag them into the deployment group. No dependencies. Select to skip deploying dependent objects. You cannot add checked out objects to a deployment group. Dependent objects can include dependent objects within a workflow or mapping as well as objects that shortcuts reference and primary key sources where there is a primary keyforeign key relationship. You can specify the following conditions for adding child dependencies: ♦ ♦ ♦ All dependencies. For example. you might group objects for deployment on a certain date and deploy all objects at once. Dependency for Deployment Group Dialog Box When you select All Dependencies. Figure 9-12 shows the Dependency for deployment group dialog box: Figure 9-12. you can also add child dependent objects to the deployment group. Select to deploy non-reusable dependent child objects. right-click an object in the Navigator or in a detail window. In the Repository Manager. see “Copying Folders and Deployment Groups” on page 241. To add objects from the Query Results or View History windows. Select to deploy all child dependencies. To add several objects to a deployment group. Working with Deployment Groups 239 . You manually add or delete objects from a static deployment group. choose Tools-Add to deployment group. In the View History window. For information on deploying groups to a repository. Non-reusable. You can add objects to a deployment group when you view the results of an object query or view the results of an object history query from the Repository Manager. When you add objects to a static deployment group. choose Tools-Add to deployment group.Working with Static Deployment Groups You might want to create a static deployment group if you do not expect the set of deployment objects to change. You can add checked in objects to a static deployment group from the Repository Manager. you add all dependent objects to the static deployment group.

you must create all mappings in the group with labels. If you want to find the latest versions of objects in a dynamic deployment group. see “Working with Versioned Objects” on page 199. Using Queries with Dynamic Deployment Groups When you associate an object query with the deployment group. If the dynamic deployment group contains a non-reusable object in an unlabeled mapping. 240 Chapter 9: Grouping Versioned Objects . You can run the dynamic deployment group query multiple times and add new objects to the group each time you run the query. you might use a dynamic deployment group if you develop multiple objects for deployment on different schedules. For example. the Repository Agent runs the query at the time of deployment.Working with Dynamic Deployment Groups You might want to create a dynamic deployment group if you expect the set of deployment objects to change frequently. The parent object and non-reusable child objects in a dynamic deployment group may not have the same label applied to them in the following circumstances: ♦ ♦ You changed the parent object. but did not apply a label to the latest version of the object. For more information on managing versioned objects. For more information on deploying groups of objects. You applied different labels to reusable or non-reusable objects when viewing the object history in the results view. see “Copying Folders and Deployment Groups” on page 241. the group will not deploy. You can associate an object query with a deployment group when you edit or create a deployment group.

248 Copying a Deployment Group. 244 Copying or Replacing a Folder.Chapter 10 Copying Folders and Deployment Groups This chapter contains information on the following topics: ♦ ♦ ♦ ♦ Overview. 242 Using the Copy Wizards. 254 241 .

After a week in production. the repository does not allow the PowerCenter Server to fetch objects from the target repository. When you complete initial development for the metadata in a new folder and you are ready to deploy the objects into production you copy the folder and all of its objects into the production repository. so you add the session to a deployment group. When the folder is ready for production.Overview You can use the Repository Manager to copy multiple objects from one repository to another. You can also effectively use different copy operations together. you have a development and production repository. you may use copy folder to copy an entire folder. You do not need to copy all of the metadata in the folder to production. or from a source repository into a target repository. When a PowerCenter 242 Chapter 10: Copying Folders and Deployment Groups . The contents of the replaced folder are overwritten. When it is ready for production. Copying a deployment group allows you to copy objects in a single copy operation from across multiple folders in the source repository into multiple folders in the target repository. For example. You can perform the following copy operations: ♦ ♦ Copy a folder. you copy the Sales folder into the production repository. When you copy the deployment group. You can copy a folder and all of its contents within a repository. PowerCenter Server Processing When you copy or replace a folder. If you want to update the metadata in a folder already in production. you have a folder called Sales in the development repository. You can copy a folder and all of its contents from a source repository and replace an existing folder of the same name in the target repository. you want to make minor changes. you can replace the folder. As development continues you make changes to a session in the folder. rather than the entire contents of a folder. Replacing the folder allows you to update the production repository without creating multiple copies of the folder. ♦ If you want to archive or share metadata or deploy metadata into production. resulting in two copies of the folder in production. You can copy the objects in a dynamic or static deployment group to multiple target folders in the target repository. Copying a deployment group also allows you to specify individual objects to copy. Replace a folder. You might use copy folder and copy deployment group together in your repository environment at different stages of the development process. or you can replace the existing Sales folder with the new one. you may also copy the objects in a deployment group from one repository to another. the Copy Deployment Group wizard creates a new version of the session in the target folder. For example. you can either copy the folder into the production repository. The deployment operation creates new versions of existing objects in the target folders. If the repository is enabled for versioning. You edit the Sales folder in the development repository and test the changes. or copy a deployment group. Copy a deployment group.

The PowerCenter Server fetches the repository object and completes the workflow. session. if the PowerCenter Server tried to fetch session information to run a session in a workflow. session. It cannot fetch objects in that repository during this time. or task while a repository is blocked. it displays the following message: The folder/object deployment has completed. For example. Overview 243 . The PowerCenter Server pauses until the repository completes the deploy. When the repository allows access again. the repository denies access and returns the following message: Access to the repository is blocked since a folder/object deployment is in progress. The error message appears in either the server log. or task. the message appears in the workflow log.Server tries to access the repository to run a workflow. depending on which operation the PowerCenter Server tried to perform. The current operation will resume. workflow log. The current operation will be suspended until the deployment is completed. or session log.

The wizard steps vary depending on the operation and the contents of the folder or deployment group you want to copy. Copy metadata extension values. The wizard might have to determine how the folders are related before establishing shortcuts. Copy persisted values. When you copy a folder or deployment group. For specific instructions on using the Copy Deployment Group Wizard to copy a deployment group. You can choose the shared folder to associate shortcuts.Using the Copy Wizards The Repository Manager provides a wizard to copy and replace folders and to copy deployment groups. you must choose from the following Copy Wizard modes: ♦ ♦ Typical. Copy the metadata extension values associated with repository objects. Use the PowerCenter Server to run all workflows in the folder if a matching server does not exist in the target repository. Copy database. Advanced. Retain the assigned server settings for workflows and session instances configured to run on specific PowerCenter Servers in a server grid. You can override the defaults for shortcuts to local and global shared folders. 244 Chapter 10: Copying Folders and Deployment Groups . Copy the saved persisted values for mapping variables used in a session and workflow variables used in a workflow. Copy Modes When you copy a folder or deployment group. The wizard uses the defaults for shortcuts to local and global shared folders. you must perform many of the same actions to ensure both the Copy Folder and Copy Deployment Group wizards allow you to perform the following actions: ♦ ♦ Choose a PowerCenter Server. see “Copying a Deployment Group” on page 254. FTP. Copy plug-in application component information that does not exist in the target repository. Copy plug-in application information. ♦ ♦ ♦ ♦ For specific instructions on using the Copy Folder Wizard to copy or replace a folder. and Application connection information if matching connection names do not exist in the target repository. Retain assigned PowerCenter Server settings. Copy connections. external loader. see “Copying or Replacing a Folder” on page 248.

the wizard does not copy PowerCenter Server connection information. ♦ ♦ ♦ Associating with Multiple PowerCenter Servers If the workflows in a folder are associated with multiple PowerCenter Servers in the originating repository.Registered PowerCenter Servers Each workflow is configured to run on an associated PowerCenter Server in the repository. You then select one of those Servers to run all unassociated workflows. you must register those servers before you copy the folder. If you associate another PowerCenter Server with a workflow when you copy a folder. it registers all unassociated workflows. If the connection already exists in the target repository. Instead. The wizard associates or prompts you to associate a copied session with a PowerCenter Server in the target repository under the following circumstances: ♦ If the target repository contains a PowerCenter Server name that matches the PowerCenter Server or servers configured to run the folder workflows. If there is only one PowerCenter Server in the target repository. you can associate them with multiple PowerCenter Servers in the target repository. ♦ Tip: If you want to use PowerCenter Servers with the same name. make sure that the directory structure for server variables and other directory paths in the session properties match. the Copy Wizard uses the existing connection. the wizard associates the workflow with the same PowerCenter Server in the target repository. when you register a PowerCenter Server with the repository. If the target repository does not contain a PowerCenter Server with the same name. If a PowerCenter Server with the same name does not exist in the target repository. Connections The Copy Wizard copies connections used by sessions in the folder or deployment group. the wizard lists all of the PowerCenter Servers in the target repository. The wizard does not overwrite connections in the target repository. Using the Copy Wizards 245 . the wizard registers those workflows with the existing PowerCenter Servers. you can choose a PowerCenter Server to run the workflow. If the target repository has no registered PowerCenter Servers. the Workflow Manager assigns all workflows to that first PowerCenter Server. The Copy Folder Wizard uses the following rules to associate servers: ♦ If the target repository contains a PowerCenter Server name that matches the PowerCenter Servers configured to run the folder workflows.

You have access to the object in the originating repository. Reusable metadata extensions that you create exist in the User Defined Metadata Extension domain. the copied extensions become reusable in the target repository. Reusable extensions that other applications create exist in the appropriate vendor domain. This depends on whether the extensions are non-reusable or reusable. A matching object with the same name exists in the target repository. The wizard copies the object. All sessions using this connection are invalidated. You have access to the object in the originating repository. the Copy Wizard copies the metadata extension values associated with those objects to the target repository. When you copy an object that contain user-defined. ♦ Metadata Extensions When you copy objects to another repository. You have access to the objects in both the originating and target repositories. If the metadata extension contains a value. A matching object with the same name exists in the target repository. When you copy an object that contains a non-reusable metadata extension. such as all workflows or all Expression transformations. No match exists in the target repository. the copied extensions become non-reusable. Non-Reusable Metadata Extensions Non-reusable metadata extensions apply to single objects such as one source definition or one session. the wizard retains the value of the metadata extension in the target repository. the wizard displays the following information about connections: ♦ ♦ ♦ No Match Found. The wizard copies the object and renames it by appending a number to the name. If the definition does not exist in the target repository. 246 Chapter 10: Copying Folders and Deployment Groups . Match Found. Match Found .When you copy a folder or deployment group. You can edit it. The extension becomes nonreusable in the target repository. the Copy Wizard copies the extensions to the target repository. You have no access to the object in the originating repository. will copy and rename to [new_name].Permission Denied. Permissions Denied. reusable metadata extensions. ♦ User-defined extensions. The metadata extension values may or may not be available in the target repository. If the definition exists in the target repository. delete it. or promote it to a reusable extension. You create non-reusable metadata extensions in the Designer or Workflow Manager. see “Working with Metadata Extensions” on page 327. but no access to the object in the target repository. For more information about non-reusable metadata extensions. the Copy Wizard copies the extension to the target repository with the object. Reusable Metadata Extensions Reusable metadata extensions apply to all repository objects of a certain type.

♦ Vendor-defined extensions. For more information about reusable metadata extensions and domains. The source folder uses plug-in application connections. you can copy plug-in application information. If you continue. the extensions are not available in the target repository. the Copy Wizard copies the extensions to the target repository and retains their values. see “Working with Metadata Extensions” on page 327. If the vendor domain does not exist in the target repository. the Copy Wizard allows you to cancel the copy or continue. Using the Copy Wizards 247 . The source folder or deployment group depends on a plug-in application in the following cases: ♦ ♦ ♦ The source folder contains metadata extension values from a vendor-defined metadata domain. When you install the vendor application. The source folder contains a source or target with a plug-in application database type. When you copy an object that contains vendor-defined metadata extensions. if the folder or deployment group depends on the plug-in application information. the metadata extensions become part of that domain in the target repository. Copying Plug-in Application Information When you copy a folder or deployment group. If the vendor domain exists in the target repository. the metadata extensions become available so you can view them and change their values. Therefore. you can view them or change the values as you do with the other metadata extensions in that domain.

you can rename the copy of the source folder created the Copy Folder Wizard creates in the target repository. When you copy a folder. the wizard deletes the existing folder. the folder replacement operation overwrites the objects in the target folder. You can choose to copy only the latest version of objects in the source folder. 248 Chapter 10: Copying Folders and Deployment Groups . If a folder in the target repository has the same name as the folder you are copying. Rename folders. Copy latest object versions or all object versions. Maintain shortcuts to objects in shared folders. the wizard makes you the owner of the copied folder. the wizard maintains properties of the replaced folder. If you cancel the copy before it completes. the wizard creates a new version of existing replaced objects in the target folder. When replacing a folder. When you replace folder. back up your repository before replacing a folder. Retain persisted values for workflow variables. You can choose to retain existing values. Instead of creating a second copy of the folder in the production repository. Retain persisted values for mapping variables. or replace them with values from the source folder. the wizard copies all of the metadata objects in the folder. or all versions. Note: When you copy a folder. you can copy a folder within the same repository. the wizard rolls back all changes. If you copy the latest object version in the source folder. If you copy all versions from the source folder. To ensure no metadata is lost. or replace them with workflow logs from the source folder. the Copy Folder Wizard allows you to perform the following actions: ♦ ♦ ♦ Reestablish shortcuts. Compare folders to determine how they are related. You can choose to retain existing workflow logs. When you replace a folder. you can replace the existing folder with the updated data. FTP. such as shortcuts. You can choose to retain existing values.Copying or Replacing a Folder In the Repository Manager. It does not overwrite previous versions in the target folder. the wizard allows you to perform the following additional actions: ♦ ♦ ♦ ♦ ♦ Retain current values for Sequence Generator and Normalizer transformations. Use the Copy Folder Wizard to perform the copy or replace operation. or replace them with values from the source folder. and external loader connection information. Compare folders. or replace them with values from the source folder. Copy latest object versions or all object versions. The wizard copies and replaces folders as a single transaction. Workflow logs. The Copy Folder Wizard allows you to perform all of the tasks listed in “Using the Copy Wizards” on page 244. You can choose to retain existing values. Each time you copy or replace a folder. You might replace a folder when you want to update a folder that is already in production. You can also copy a folder into a different repository within the same domain or to a different domain. ♦ You can also copy and replace a folder across repositories.

Naming When you copy a folder. If you do not copy the shared folders before copying the folder. If you are replacing a folder in a repository that is enabled for versioning. see “Viewing Checked Out Objects” on page 211. the wizard does not allow you to copy a folder when the folder. Copying or Replacing a Folder 249 . the wizard names the copy after the folder. the wizard asks you to copy it again. Shortcuts to the global repository are called global shortcuts. view object locks to verify that the folder is not in use. Shortcuts The folder or you want to copy might contain shortcuts to shared folders in the same repository or to shared folders in the global repository. If the folder name already exists in the repository. and yyyy=year). the wizard appends the date to the folder name. are being saved. Likewise. verify that no objects in the target folder are checked out. and you choose not to replace it. For more information on changing the status of an object. local shortcuts become global shortcuts. If you copy the folder from the global repository to a local repository in the same domain. If you a replacing a folder in a target repository enabled for versioning. dd=days. if you edit the original shared folder after you copy it to the target repository. as follows: <folder_name>_mm/dd/yyyy (where mm=months. Before you copy a folder. you must also verify that no objects in the target folder are checked out. the wizard verifies whether the copy is current. Therefore. Shortcuts to folders in the same repository are known as local shortcuts. In typical mode. you can compare the folders to see which folder is most recent. Locking and Checkouts To protect the integrity of the repository. you must copy shared folders before copying the folder. In the advanced mode. Therefore. to copy shortcuts correctly. For more information on searching for checkouts in the repository. For details on locking. see “Working with Version Properties” on page 203. If shared folders exist in the target repository. you cannot save objects in a folder as the wizard copies the folder. you can keep shortcuts intact by copying the necessary local shared folders to the target repository before copying the folder. see “Repository Security” on page 125. Local Shortcuts The wizard can reestablish local shortcuts to shared folders if you have a current copy of the shared folders in the target repository. the wizard deletes all shortcuts and marks all affected mappings invalid. The wizard does not establish shortcuts to an outdated shared folder. or objects in the folder.

using a naming convention that clearly defines the existing folder. the wizard recreates global shortcuts to the global repository. When you copy a folder from a global repository to a local repository within the domain. You might want to rename existing shared folders before performing the copy. you want to copy a shared folder and a non-shared folder with shortcuts from a global repository to a local repository. Global Shortcuts The wizard can reestablish global shortcuts if you copy the folder or deployment group to another repository in the same domain in the following situations: ♦ ♦ ♦ When you copy a folder from one local repository to another within the domain. the wizard uses the folder name for the copied folder. you must copy those shared folders into the target repository before copying the folder. If it does not. copy any shared folders from the local and global repositories in the source domain to either the local or global repository in the target domain. you establish global shortcuts to the shared folder in the global repository. If you have edited objects in any local shared folders used by the folder. If it does. If you copy a folder that contains global shortcuts between domains. The wizard reestablishes all shortcuts. use the Repository Manager to verify no users are accessing objects in the folder. The Copy Wizard will either reestablish global shortcuts as a local shortcuts. Steps for Copying or Replacing a Folder Before you copy a folder. If you copy the folder in advanced mode. If you choose to copy the folder in typical mode. you can also choose to establish local shortcuts to the shared folder in the local repository. you might want to rename the existing folder in the target repository. it asks you to rename the folder.For example. Copying Within a Repository When you copy a folder within the same repository. local shortcuts become global shortcuts. or establish the copied shortcuts as global shortcuts. First copy the shared folder into the local repository. When you copy a folder from a local repository to its global repository. the wizard verifies whether a folder of the same name exists in the target repository. the wizard asks you to rename the folder. copy dependent 250 Chapter 10: Copying Folders and Deployment Groups . the global shortcuts become local shortcuts. Copying From Local Repositories When you copy a folder from a local repository to another repository. You might want to ask all users to exit the repository Also. If you want to copy the folder again. and the copied folder continues to use the same connection and server information. Then copy the non-shared folder.

To copy or replace a folder: 1. Table 10-1 lists the dialog boxes and prompts that you may see when you copy a folder: Table 10-1. The wizard might have to determine how the folders are related before establishing shortcuts. or all versions. Replace Folder Folder Modified Compare Folders Typical/Advanced Typical/Advanced Typical/Advanced Sequence Generators and Normalizers Mapping Variables Typical/Advanced Typical/Advanced Copying or Replacing a Folder 251 . 2. click Cancel. To stop the replacement. The Copy Folder Wizard appears. The Copy Wizard prompts you for more information based on the content of the folders and the copy mode you selected. 4. The wizard uses the defaults for shortcuts to local and global shared folders. In the Navigator. Click Next.shared folders to the target repository before copying a folder. List existing copies of the folder or all folders in the repository Specify if objects in the source folder have been created or modified since the last copy. 3. Choose Edit-Copy. displaying the folder name and target repository name. If you are replacing a folder. select the target repository. connect to the source repository and select the folder you want to copy. If copying to a different repository. You can override the defaults for shortcuts to local and global shared folders. If you specified that the source folder contains new or modified objects. compare the folders to determine the similarities and differences between the folders. copying the latest version adds a new version to the existing objects in the target folder. For information on the privileges and permissions to copy a folder. You can choose the shared folder to associate shortcuts. verify no users are accessing objects in the target repository. and choose Edit-Paste. Tip: You can also drag and drop the folder into the target repository after connecting to the repository. The wizard rolls back all changes. If you are replacing a folder. Choose to retain current values for Sequence Generator and Normalizer transformations. connect to the target repository. Advanced. 5. 6. see “Repository Manager Tasks” on page 516. Copy Folder Wizard Prompts (Copying a Folder) Copy Folder Wizard Dialog Box Latest Version Only Mode Typical/Advanced Prompt Choose to copy the latest version of objects in the folder. In the Repository Manager. The Copy Folder dialog box prompts you to select a mode: ♦ ♦ Typical. Copy persisted values for mapping variables if they exist.

Choose to retain existing workflow logs in the target folder if you choose not to copy workflow logs from the source folder. Lists all external loader connections in the folder. indicating the connections for which you do not have read permission. If the target repository contains less than two PowerCenter Servers. Lists all database connections in the folder. Choose to retain the assigned PowerCenter Server information for workflows and sessions configured to run on specific PowerCenter Servers in a server grid. choose to retain persisted values for mapping variables. Copy dependency information for objects in mappings. Rename the target folder if a folder of the same name exists in the target repository. indicating the connections for which you do not have read permission. Lists plug-in application information upon which the source folder depends if the plug-in information does not exist in the target repository. Copy Folder Wizard Prompts (Copying a Folder) Copy Folder Wizard Dialog Box Retain Mapping Variables Dependency Information Workflow Variables Retain Workflow Variable Persisted Values Copy Workflow Log Retain Workflow Logs Folder Exists Mode Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Prompt If you are replacing a folder. if it exists. Lists local shared folders in the target repository that you need to copy first. Lists all FTP connections in the folder. Choose to retain persisted values. click Cancel and copy all listed local shared folders before copying the folder. To preserve shortcuts and prevent invalid mappings. Retain Server Settings Typical/Advanced Database Connections MQ Connections FTP Connections External Loaders Application Connections Plug-in Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Servers Typical/Advanced Local Shared Folders Typical Global Shared Folders Typical 252 Chapter 10: Copying Folders and Deployment Groups . the wizard skips this step. it appends the date to the original folder name. Lists all application connections in the folder. Lists global shared folders in the target repository that you need to copy first. Lists all MQ connections in the folder. Allows you to select a PowerCenter Server to run all nonassociated workflows. Choose to copy workflow logs if they exist. indicating the connections for which you do not have read permission. Copy persisted values for workflow variables. indicating the connections for which you do not have read permission. Otherwise.Table 10-1. click Cancel and copy all listed local shared folders before copying the folder. To preserve shortcuts and prevent invalid mappings.

Displays objects that exist in the local shared folder but not in the global shared folder.Table 10-1. a message warns you that shortcuts to missing objects will be removed. Lists all dependent local and global shared folders. To preserve shortcuts and prevent invalid mappings. click Cancel and copy all listed local shared folders before copying the folder. The wizard takes you back to Select Shared Folders dialog box. Copy Folder Wizard Prompts (Copying a Folder) Copy Folder Wizard Dialog Box Outdated Shared Folders Mode Typical Prompt Lists outdated folders in the target repository that you need to copy first. Lists folders you can select to establish shortcuts if you choose to override the default folder selection in the Select Shared Folders dialog box. Lists the results from the folder compare. Also lists the folder that contains shortcuts and the folder to which you can establish shortcuts. Allows you to compare folders if the folders you choose in Override Shared Folder dialog box are different. Also displays objects that are older or newer than matching objects in the global shared folder. Select Shared Folders Advanced Override Shared Folder Advanced Compare Shared Folder Compare Results Advanced Advanced Copying or Replacing a Folder 253 . You can choose to accept or override the shared folder. If there are differences between the folders.

the wizard creates a new object in the target repository. If this naming conflict occurs. For more information. creating a new version of the object in the target repository. After it creates the new version. You copy local and global shortcuts. Object names in the target repository are different from or conflict with the deployment group object. see “Copying Composite Objects” on page 255. When you create a deployment group you can choose to copy all or part of composite objects. ♦ ♦ ♦ The status of the object in the target repository is different from the status of the object in the deployment group. Locking and Checkouts To protect the integrity of repository metadata. see “Object Naming” on page 257. The status of an object in a deployment group may change after the copy operation depending on the status of the copy of the object to be replaced. An object in the target repository may also have the same name as an object in the deployment group. For details on copying composite objects in a deployment group. you must ensure that the correct shared folders and necessary global shortcuts exist in the target repository. you must be aware of the relationships between objects in the deployment group and the target repository under the following circumstances: ♦ You copy part of a composite object. At the time of deployment. see “Object Status” on page 257. In this situation. the wizard checks in the object. but may not be a copy of the deployment group object. see “Copying Shortcuts” on page 256. but have a different name. For details on changes to object status when you copy a deployment group. For details on object naming.Copying a Deployment Group If the repository is enabled for versioning. the wizard identifies the previously copied object and replaces it. the wizard copies all objects included in a static deployment group. The next time you copy the object. the wizard allows you to reestablish local shortcuts to objects in shared folders. As a result. you must ensure that dependent objects exist in the target folder. the wizard replaces the copy of the object and create a new version of the object with the same name as the deployment group object. If you choose to deploy part of a composite object. When you copy a deployment group. An object in the target repository may be a copy of the object in the deployment group. you can also use the Copy Deployment Group Wizard to copy objects in a deployment group into multiple deployment folders in the target repository. If you are copying a dynamic deployment group. The wizard does not allow you to reestablish global shortcuts. the Copy Deployment Group Wizard does not allow you to copy a deployment group when objects targeted for replacement are checked 254 Chapter 10: Copying Folders and Deployment Groups . the wizard first runs the query associated with the deployment group and then copies the objects from the results of the query. The first time you copy an object in a deployment group to the target repository. the wizard cannot copy the deployment group object. As a result.

Copying a Deployment Group 255 . a mapping may use a reusable source. it fails the copy operation. For more information on viewing checked out objects in the repository. see “Checking Out and Checking In Objects” on page 211. You want to update the copy of the mapping currently stored in the production repository. If the wizard cannot locate necessary dependencies in the target repository. For more information on changing the status of an object. you can choose to include all dependencies. the Repository Agent rolls back changes. You must ensure that the dependent objects are also included in the deployment group or already exist in the target repository. View checkouts and manually check in the objects to complete the copy operation. Change the folder status to Frozen. and several non-reusable transformations. but the wizard can still copy and check in deployment group objects. the wizard uses existing copies of objects in the target repository for all child dependencies not included in the deployment group. The next time you deploy the group. For details on locking.out or locked. you must include all dependencies of the composite object. For example. If you choose to copy no dependencies or non-reusable dependencies for a composite object. You can freeze the target deployment folder to ensure that no target objects are checked out when you copy a deployment group. If this happens. the deployment group objects may be copied to the target repository. Each of these objects is a child dependency of the mapping. other users cannot check out objects in the folder. The first time you deploy a group. However. Note: If the repository stops unexpectedly during the copy operation. you edit a mapping variable in a mapping. Allow Deploy. but not checked in. You can copy the following composite objects to a deployment group: ♦ ♦ ♦ ♦ ♦ ♦ Local shortcuts Mappings Mapplets Sessions Worklets Workflows When you create a deployment group. You add the mapping to a deployment group with no dependencies because you do not want to update any non-reusable or reusable transformations in the mapping. When you copy the mapping to the production repository. When you freeze a folder. Before you copy a deployment group. Copying Composite Objects A composite object is one that uses other objects. see “Working with Version Properties” on page 203. For example. you can add all or some object dependencies to the deployment group. see “Repository Security” on page 125. search for checkouts in the target repository and verify that no deployment target objects are checked out. the objects will be stored in the repository as checked out objects. reusable target. nonreusable dependencies. or no dependencies for composite objects.

the wizard deletes all shortcuts and marks all affected mappings invalid. For example.the wizard replaces the current version of the mapping and associates all existing transformations with the new version. For details about the status of deployed objects. the wizard asks you to copy it again. To ensure that necessary dependencies exist in the target repository. You may want to add all dependencies the first time you copy an object to another repository. Design the query associated with the dynamic deployment group to find dependencies. When you compare folders. if the parent object is deleted. the Repository Agent treats associated non-reusable objects as deleted. If the referenced object already exist in the target repository. the Repository Agent treats the non-reusable objects in the composite object as part of the parent object. In advanced mode. You may want to further refine the query for a dynamic deployment group by specifying other parameters. see “Working with Deployment Groups” on page 236. You can keep these shortcuts intact by copying the necessary local shared folders to the target repository before you copy the deployment group or by including the object the shortcut references in the deployment group. Shortcuts to folders in the same repository are known as local shortcuts. you can compare the contents of the folders to see which contains the most recent copies of referenced objects. if you edit the original shared folder after you copy it to the target repository. The PowerCenter Client prompts you to do this when you manually add an object to a static deployment group. the wizard verifies that the copy is current. You can then use deployment groups to update individual objects over time. In typical mode. the wizard compares 256 Chapter 10: Copying Folders and Deployment Groups . You can also add dependencies to the deployment group. You can design the query to search for dependencies of a composite object. If you do not copy the shared folders before copying the deployment group. Local Shortcuts The wizard can reestablish local shortcuts to objects in shared folders if you have a current copy of the object in the target repository. you might want to copy the entire folder to the target repository the first time you copy the objects. ♦ For more information on creating static and dynamic deployment groups. Copying Shortcuts The deployment group you want to copy might contain shortcuts to shared folders in the same repository or to shared folders in the global repository. Use one of the following methods to ensure that you include dependencies in the deployment group: ♦ Manually add the dependencies to the static deployment group. see Table 10-2 on page 258. Shortcuts to the global repository are called global shortcuts. and then decide to cancel and copy the shared folder again or proceed with the copy operation. Note: When you deploy composite objects.

Object Status When you copy an object in a deployment group. including the shortcut. The latest version of the mapping in the production repository is now m_OrdersWeekly. the wizard detects the relationship between the two objects and replaces the copy in the target folder with the deployment group object. you change the name of the mapping in the development repository to m_OrdersWeekly. Object Naming Different versions of an object may have different names. For example. you have the mapping m_Orders in the development repository. If the global shortcut is part of a composite object you want to copy. the status of the source object may change if a copy of the object already exists in the target folder. exists in the target repository. The wizard deletes the shortcut and marks all affected mappings invalid. As you continue development. In this situation. the wizard cannot reestablish the shortcut. you have a mapping that uses relational source src_Records in the development repository. consider copying the entire folder. but is a different object. the naming conflict causes the copy operation to fail. Global Shortcuts If the deployment group contains global shortcuts. Also. the copy operation fails because the XML source src_Records has the same name. If you are copying the object for the first time. You add this new version of the mapping to a deployment group and copy it to the production repository. the copy operation fails. For example. the wizard does not reestablish them when you copy them to the target repository. the wizard completes the copy operation but does not copy the shortcut. The wizard determines that m_Orders is an older copy of m_OrdersWeekly. If you copy a global shortcut alone. Later. To ensure that global shortcuts are preserved when you copy a composite object.the version of the objects in the deployment group with the latest version of objects in the target folder. you delete src_Records from the production repository and create a new XML source. but is not a copy of the object. verify that a copy of the object. You might also have an object in the target repository that has the same name as a deployment group object. but the copy has a different name. Copying a Deployment Group 257 . You add it to a deployment group and copy it to the production repository. If you then use a deployment group to copy the relational source src_Records to the target repository. creating a new version. The object may be of a different type. and replaces it. you might add an object to a deployment group that has an existing copy in the target folder. You add the mapping to a deployment group and copy it to the production repository. As a result. also named src_Records. if you copy a local shortcut into the same folder that contains the object the shortcut references. You can then use a deployment group to copy subsequent versions of the object. If this happens.

Steps for Copying a Deployment Group Use the Copy Deployment Group Wizard to copy objects in a deployment group. copy dependent shared folders for shortcuts in the deployment group. Or. Change In Object Status After Copying Deployment Group Objects Status of Deployment Group Object Active Object Active Object Deleted Object Deleted Object Deployment Wizard Action Deploys the object Deploys the object Deploys the object Skips the object Status of Target Repository Object Deleted Active Active Deleted Status of Target Repository Object After Copying Active Active Deleted Deleted Note: Non-reusable objects derive status from their parent composite objects. you may want to apply a label to the source and target objects that specifies when the source object version was deployed and when the target object version was created. 258 Chapter 10: Copying Folders and Deployment Groups . depending on the status of the source and target objects: Table 10-2. For example. Before you copy a deployment group. associated non-reusable objects also have a deleted status. For details on viewing a deployment history. You can apply labels to the deployment group objects in the source and target repositories. For example. You can remove the copied objects from a static deployment group when you finish copying them into the target repository. see “Working with Deployment Groups” on page 236. You can move labels from version to version in source and target repositories. you might want to move a label from the last version to the latest version before you deploy an object.Table 10-2 describes the status an object may take after copying the deployment group. Clear the static deployment group when you finish copying. You can choose the specific folders in the target repository you want to deploy. The repository stores a deployment history for each deployment group. Also. you might want to deploy an earlier version of an object and apply the latest label to the object. ♦ ♦ You can copy a deployment group only if the source and target repositories are both enabled for version control. The Copy Deployment Group Wizard allows you to perform all of the tasks listed in “Using the Copy Wizards” on page 244. verify that existing objects in the target repository are not checked out or locked. It also allows you to perform the following tasks: ♦ ♦ Choose deployment folders. Apply labels to source and target objects. Move labels. If a parent composite object has a deleted status.

Advanced. Copy dependency information for objects in mappings. Click Next. Table 10-3 lists the dialog boxes and prompts that you may see when you copy a deployment group: Table 10-3. Override the default selections for deployment folders. Clear Source Deployment Group Sequence Generators and Normalizers Retain Mapping Variables Dependency Information Retain Workflow Variable Persisted Values Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Copying a Deployment Group 259 . The Copy Deployment Group Wizard appears. Choose to retain current values for Sequence Generator and Normalizer transformations. The Copy Deployment Group Wizard dialog box prompts you to select a mode: ♦ ♦ Typical. Choose to retain persisted values for mapping variables. To copy a deployment group: 1. The wizard rolls back all changes. Select the folders you want to compare. 4. Copy Deployment Group Wizard Prompts Copy Deployment Group Wizard Dialog Box Select Deployment Folders Override Deployment Folder Select Compare Folders Select Labels Mode Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Prompt Choose the folders you want to deploy objects to. 3. Select a label in the source repository to apply to the copied object versions. 2. Connect to the source and target repositories. Choose to retain persisted values. The Copy Wizard prompts you for more information based on the content of the folders and the copy mode you selected. You can override the defaults for shortcuts to local and global shared folders. displaying the folder name and target repository name. and select a label in the target repository to apply to the newly created object versions. You can choose the shared folders to associate shortcuts. Select the deployment group to copy. The wizard uses the defaults for shortcuts to local and global shared folders. if they exist. Choose to remove objects from the deployment group after the wizard completes the deployment operation. 5. click Cancel. To stop the replacement. The wizard might have to determine how the folders are related before establishing shortcuts.Use the following steps as a guideline when you copy a deployment group. Click and drag or paste the deployment group to the target repository.

Allows you to select a PowerCenter Server to run all nonassociated workflows. Database Connections MQ Connections FTP Connections External Loaders Application Connections Plug-in Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Typical/Advanced Servers Typical/Advanced Local Shared Folders Typical Outdated Shared Folders Typical Select Shared Folders Advanced Override Shared Folder Advanced 260 Chapter 10: Copying Folders and Deployment Groups . Choose to retain the assigned PowerCenter Server information for workflows and sessions configured to run on specific PowerCenter Servers in a server grid. Lists local shared folders in the target repository that you need to copy first. Lists all application connections in the folder. Lists all dependent local and global shared folders. Copy Deployment Group Wizard Prompts Copy Deployment Group Wizard Dialog Box Retain Workflow Logs Retain Server Settings Mode Typical/Advanced Typical/Advanced Prompt Choose to retain existing workflow logs in the target folder if you choose not to copy workflow logs from the source folder. indicating the connections for which you do not have read permission. To preserve shortcuts and prevent invalid mappings. click Cancel and copy all listed local shared folders before copying the folder. Lists all database connections in the folder.Table 10-3. Also lists the folder that contains shortcuts and the folder to which you can establish shortcuts. indicating the connections for which you do not have read permission. If the target repository contains less than two PowerCenter Servers. Lists plug-in application information upon which the source folder depends if the plug-in information does not exist in the target repository. indicating the connections for which you do not have read permission. You can choose to accept or override the shared folder. Lists all FTP connections in the folder. Lists outdated folders in the target repository that you need to copy first. the wizard skips this step. Lists all external loader connections in the folder. Lists folders you can select to establish shortcuts if you choose to override the default folder selection in the Select Shared Folders dialog box. indicating the connections for which you do not have read permission. To preserve shortcuts and prevent invalid mappings. Lists all MQ connections in the folder. click Cancel and copy all listed local shared folders before copying the folder.

Also displays objects that are older or newer than matching objects in the global shared folder. Copying a Deployment Group 261 . Lists the results from the folder compare. Copy Deployment Group Wizard Prompts Copy Deployment Group Wizard Dialog Box Compare Shared Folder Compare Results Mode Advanced Advanced Prompt Allows you to compare folders if the folders you choose in Override Shared Folder dialog box are different. If there are differences between the folders. The wizard takes you back to Select Shared Folders dialog box. a message warns you that shortcuts to missing objects will be removed.Table 10-3. Displays objects that exist in the local shared folder but not in the global shared folder.

262 Chapter 10: Copying Folders and Deployment Groups .

276 Importing Objects. 280 Steps for Exporting Objects. 273 Working with Shortcuts. 287 Troubleshooting.Chapter 11 Exporting and Importing Objects This chapter includes information on the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 269 Working with Dependent Objects. 296 263 . 267 Exporting and Importing Multiple Objects and Object Types. 285 Steps for Importing Objects. 264 The XML and DTD Files. 274 Exporting Objects. 270 Working with Object Versions.

You can use the following client applications to export and import repository objects: ♦ ♦ ♦ ♦ Repository Manager.Overview In the PowerCenter Client. You might export and import objects to incrementally deploy metadata by exporting and importing part of a composite object. You can copy objects between repositories that you cannot connect to from the same client. Share metadata. Archive metadata. you can export it to an XML file and then import it from the XML file into a production repository. Several other transformations call the lookup port through an expression. You can export the mapping to an XML file and open it in a text editor. see “Exporting Objects (ObjectExport)” on page 432 and “Importing Objects (ObjectImport)” on page 433. You can export and import both Designer and Workflow Manager objects. Export the object and transfer the XML file to the target machine. For example. After you test a mapping in a development repository. Search for the old port name and replace all references to it with the new port name. When you export an object from one repository and import the object into another repository. when you copy objects between folders or repositories. The third party can import the mapping from the XML file and analyze the metadata. Exporting and importing an object is similar to copying an object from one folder or repository to another. For example. Search and replace property names in an entire repository object. You can export and import only Designer objects. you can export repository objects to an XML file and then import repository objects from the XML file. but you do not want to disclose repository connection information for security reasons. you have a mapping with an unconnected Lookup transformation. Designer. You can share metadata with a third party. You want to change the name of a port in the unconnected Lookup transformation. Then import the mapping into the repository. Then import the object from the XML file into the target repository. Workflow Manager. so you want to make sure you change the port name in all other expressions. You can export and import only Workflow Manager objects. You can export and import both Designer and Workflow Manager objects. You can search for a property name and replace all occurrences of it with a different name. You can export the mapping to an XML file and edit the repository connection information before sending the XML file. when you copy an object between folders or export and import that object. you do not need to be connected to both repositories. You might use pmrep to automate exporting objects on a daily or weekly basis. For more information on using pmrep to export and import objects. you must be connected to both repositories. However. pmrep. You can export and import repository objects to accomplish the following tasks: ♦ Deploy metadata into production. For example. you can resolve object name conflicts. Copy metadata between repositories. you want to send a mapping to someone else for testing or analysis. ♦ ♦ ♦ ♦ 264 Chapter 11: Exporting and Importing Objects . You can export objects to an XML file that you no longer need before removing them from the repository.

Working with Objects and Object Types You can export and import the following repository objects: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Sources Targets Transformations Mapplets Mappings Tasks Sessions Schedulers Session configurations Worklets Workflows When you export and import repository objects. For more information. see “Exchanging Metadata” on page 313. you can do this when you access a query result from the Designer. You can export and import one or more object types. For more information. You can export and import one or more objects. you can choose to export and import the following types of objects: ♦ Multiple object types. Dependent objects. see “Exporting and Importing Multiple Objects and Object Types” on page 269. Also. ♦ ♦ ♦ Working with Different Repository Versions You can share objects with other repositories by exporting and importing objects between repositories with the same version. you can export and import objects from one or more folders in the same repository. The combination of object types you can export and import depends on the PowerCenter Client you use. Workflow Manager.You can also export and import relational sources and targets to share metadata with other business intelligence and data modeling tools. For more information on exchanging metadata. Objects from multiple folders. For more information. You can also import objects exported from a repository version PowerCenter supports upgrading. Multiple objects. Using the Repository Manager or pmrep. or Repository Manager. see “Exporting and Importing Multiple Objects and Object Types” on page 269. you can only import sessions exported from version 6. Overview 265 .0 and later. see “Working with Dependent Objects” on page 270. You can export and import an object with or without its dependent objects. However.

Permissions and Privileges To export and import repository objects.When you import an object exported from an earlier repository version. or Repository Manager. For example. The PowerCenter Client imports the transformation and changes it to a Custom transformation. see “Globalization Overview” and “Code Pages” in the Installation and Configuration Guide. Workflow Manager. you export an Advanced External Procedure transformation from an earlier repository version. you must have the proper folder permissions and user privileges. The permissions and privileges required to import and export objects change depending on whether you are using the Designer. For details on code page compatibility. Table 11-1 lists the permissions and privileges you need to export and import objects: Table 11-1. The code page of the originating repository must be a subset of the destination repository code page. 266 Chapter 11: Exporting and Importing Objects . the PowerCenter Client displays an error message and does not import any object. Exporting and Importing Objects Permissions and Privileges PowerCenter Client Designer Repository Privilege Use Designer Super User Workflow Manager Use Workflow Manager Super User Repository Manager Use Repository Manager Super User Folder Permission Read for exporting Read/Write for importing N/A Read for exporting Read/Write for importing N/A Read for exporting Read/Write for importing N/A Code Pages To ensure no data is lost when you import an object. You import the transformation in the current repository version. see “Upgrading Repository Metadata” in the Installation and Configuration Guide. For more information on changes the upgrade process makes on repository metadata. the repository updates the object metadata to conform with the current repository version. If the two repository code pages are not compatible. the PowerCenter Client only allows you to export and import objects between repositories with compatible code pages.

When you export or import an object.dtd.dtd states that an element must occur once in an XML file.w3. You also need to make sure the metadata in the XML file conforms to Designer and Workflow Manager rules. When you import repository objects.dtd is not in the client installation directory. an exported XML file is valid if it complies with the constraints expressed in powrmart. Although PowerCenter validates the XML file before importing repository objects from it. For example. The CRCVALUE code is another attribute in an element. for more information on XML. If you import into your repository an object that does not conform to Designer or Workflow Manager rules. if powrmart. when you define a shortcut to an object. For more information on reading DTD files. Therefore.org/. see the W3C specifications for XML at http:// www. you cannot import repository objects. When you export repository objects. the PowerCenter Client creates the XML file based on the structure specified in powrmart. If powrmart. When you install PowerCenter. Note: If you modify an exported XML file.dtd.dtd file. see “Modifying an Exported XML File” on page 277. it might not catch all invalid changes. so you can only The XML and DTD Files 267 . You can use this same file to import the repository objects into a repository. When you export a Designer object. define the folder in which the referenced object resides as a shared folder.dtd. the PowerCenter Client might include a CRCVALUE (Cyclic Redundancy Checking) code in one or more elements in the XML file. the PowerCenter Client looks for powrmart. The XML file has an associated Document Type Definition (DTD) file called powrmart. the XML file is invalid if the element occurs more than once or not at all. For example. the PowerCenter Client creates an XML file that contains the metadata of the exported repository objects.The XML and DTD Files When you export repository objects.dtd in the client installation directory. For information on modifying XML files. you might cause data inconsistencies in your repository. VSAM source objects always contain a CRCVALUE code. For example. When the PowerCenter Client includes a CRCVALUE code in the exported XML file. CRCVALUE Codes Informatica restricts which elements you can modify in the XML file. An XML file is valid if it complies with the constraints expressed in its associated DTD. you need to make sure that the XML file conforms to the structure of powrmart. Or. see “XML Concepts” in the XML User Guide.dtd.dtd. the installation program copies powrmart. Do not modify the powrmart.dtd into the client installation directory. you can only modify some attributes and elements before importing the object into a repository. the PowerCenter Client validates the XML file against powrmart.

CBL" IBMCOMP ="YES" CRCVALUE ="3108520154" OWNERNAME ="" DESCRIPTION ="" BUSINESSNAME ="" DATABASETYPE ="VSAM" . If you modify certain attributes in an element that contains a CRCVALUE code..> . 268 Chapter 11: Exporting and Importing Objects .. </SOURCE> CRCVALUE code The CRCVALUE attribute for the element SOURCE in Figure 11-1 is 3108520154. see “Modifying an Exported XML File” on page 277. Note: The PowerCenter Client only includes CRCVALUE codes in the XML file when you export Designer objects.. For example. CRCVALUE Code in an Exported XML File <SOURCE NAME ="SALES_FILE" DBDNAME ="SALES. Figure 11-1 shows part of the element for a source object with the CRCVALUE code: Figure 11-1.. you cannot import the source into the Designer. you cannot import the object. For details on which attributes and objects you can modify.modify some attributes in a VSAM source object. if you modify the OWNERNAME attribute in the source object in Figure 11-1.

However.Multiple object types from one folder For example. and Command tasks from one folder . You cannot export multiple object types.Multiple objects from one folder .Multiple objects from one folder . Exporting and Importing Multiple Objects and Object Types 269 .Multiple object types from multiple folders When you import objects from multiple folders. Options for Importing . . You cannot export multiple mappings or mapplets. . . Table 11-2 lists the multiple objects you can export and import: Table 11-2. . you can export multiple mappings to the same file.Multiple sources. Options for Exporting and Importing Multiple Objects PowerCenter Client Application Repository Manager Options for Exporting .Multiple objects from one folder . you can export reusable transformations and reusable worklets to the same file. or reusable transformations from one folder For example. . you can choose which folders to import into.Multiple reusable Email.Multiple workflows from one folder For example. Note: You can export different object types from all PowerCenter Client tools by exporting the results of an object query.Multiple objects from multiple folders . pmrep Designer Workflow Manager . you can choose which folders to import into using the control file. the combination of object types depends on the PowerCenter Client application you use. you can export a reusable Email task and a reusable Session task. Session.Exporting and Importing Multiple Objects and Object Types You can export and import multiple objects and multiple object types at the same time.Multiple object types from multiple folders For example. you cannot export both sources and targets from the Navigator.Multiple object types from one folder You can import Workflow Manager objects only. targets.Multiple worklets from one folder .Multiple objects from multiple folders .Multiple objects from multiple folders .Multiple object types from multiple folders When you import objects from multiple folders.Multiple object types from one folder You can import Designer objects only.

For information on exporting and importing shortcuts. For example. the PowerCenter Client imports the object without the metadata extension. and worklets. When you export and import objects. and worklets. Table 11-3 lists the dependent objects that the PowerCenter Client includes in the XML file by default: Table 11-3. The object the shortcut references.* Session configuration and reusable and non-reusable tasks when you export from any client application. For more information on registering plug-ins. If the plug-in is not registered. Parent object without dependent child objects. see your PowerCenter Connect documentation. Worklet Workflow *The PowerCenter Client always exports metadata extensions. sessions. Dependent Objects Exported Parent Object Mapping Mapplet Source with foreign key Target with foreign key Shortcut Any repository object Session Dependent Child Objects Exported Sources. sessions. you can export and import any of the following combination of objects: ♦ Parent object with dependent child objects. The PowerCenter Client exports the dependent child objects listed in Table 11-3 by default. see “Exporting and Importing Parent Objects” on page 271. see “Exporting and Importing Parent Objects” on page 271. The XML file contains metadata for parent and child objects. the PowerCenter Client exports certain dependent objects by default.Working with Dependent Objects When you export an object. see “Working with Shortcuts” on page 274. Scheduler and reusable and non-reusable tasks. Verify you register a plug-in in the destination repository before you import an object using a vendor-defined metadata extension associated with the plug-in. Source definition containing the primary key. Target definition containing the primary key. A dependent object is an object that is used by another object. Sources and reusable transformations. For more information. and mapplets. targets. The PowerCenter Client does not export all dependent objects. A dependent object is a child object to the parent object that uses the dependent object. Reusable and non-reusable tasks. For more information. a source definition referenced by a shortcut is a dependent object of that shortcut. The XML file contains metadata for the parent object. but not the child object. ♦ 270 Chapter 11: Exporting and Importing Objects . reusable and non-reusable transformations. Mapping used by the session when you export from the Repository Manager or pmrep. Any reusable or non-reusable metadata extension associated with the object.

Options for Exporting Objects Export Option Export primary key tables when exporting sources/targets with foreign keys. To access the Export Options dialog box. Working with Dependent Objects 271 . the PowerCenter Client exports the source or target containing the primary key. worklet. You might want to export and import an object without its dependent objects if you change a workflow property. When you export a mapping. the PowerCenter Client exports all non-reusable transformations for a mapping or mapplet. Figure 11-2 shows the export options for dependent objects: Figure 11-2. Export reusable objects used by objects being exported. worklet. For example. mapplet. mapplet. You can choose the export options in the Export Options dialog box.Exporting and Importing Parent Objects You can choose to export a parent object with or without its dependent child objects. Description When you export a source or target containing a foreign key. and all non-reusable tasks for a worklet or workflow. the PowerCenter Client exports all non-reusable objects used by the parent object. When you export an object with its dependent child objects. click the Advanced Options link in the Export dialog box when you export objects. or workflow. the PowerCenter Client exports all reusable objects used by the parent object. Export original object referred by the shortcut when exporting shortcuts. the PowerCenter Client exports the metadata for the object. targets. When you export a mapping. the PowerCenter Client exports the metadata for the parent object and the dependent objects. and reusable transformations when you export a mapping. When you export a shortcut. the PowerCenter Client exports all sources. the PowerCenter Client exports the actual object referenced by the shortcut. but you did not change any task in the workflow. For example. Export non-reusable objects used by objects being exported. Export Options Dialog Box Table 11-4 describes the options in the Export Options dialog box: Table 11-4. such as a workflow variable. or workflow. When you export an object without its dependent objects.

when you export a session from the Repository Manager. the associated mapping must exist in the target folder and be valid. the PowerCenter Client looks for an object in the destination folder with the same name. Then edit one of the XML files to include both objects. but not the associated mapping. the associated mapping must be valid. sessions. the PowerCenter Client imports all objects used by the mapping. 272 Chapter 11: Exporting and Importing Objects . When you import an object. the session does not need to be valid before you export it. sessions. it uses the object in the destination folder. You might want to export an invalid session to send to someone else to troubleshoot. However. For example. If the mapping does not exist or is invalid. the PowerCenter Client imports the workflow metadata only. If the PowerCenter Client finds an object with the same name. and tasks. such as the sources. You can also create an XML file that contains both the session and mapping objects by using pmrep or the query results accessed from the Repository Manager to select both objects and export them. When you import the workflow. it does not import the object. To import a session. the results differ depending on whether or not the dependent objects exist in the XML file: ♦ Dependent objects exist in XML file. the PowerCenter Client exports the session. the PowerCenter Client imports all dependent objects. When you import an object. you create a workflow with multiple worklets. When you import an object that uses dependent objects. ♦ Working with Sessions When you export a session. Dependent objects do not exist in XML file. and tasks that exist in the destination folder. If the PowerCenter Client does not find an object with the same name. However. the PowerCenter Client exports the session and the associated mapping. Export the workflow and do not export the reusable and non-reusable tasks. you can use the Designer to export the mapping and the Workflow Manager to export the session. you can import the session if the XML file contains the metadata for the associated mapping. When you export a session from the Workflow Manager. For example. However. However. When you import the mapping. the object you export still references the dependent objects even though they do not exist in the XML file. when you use the Repository Manager or pmrep. You change the link condition between two tasks.but does not export metadata for the dependent objects. the PowerCenter Client does not import the session. The PowerCenter Client uses the worklets. You want to update only the link condition when you import the workflow into a different folder. you export a mapping including its dependent objects. Or.

the PowerCenter Client changes the existing target definition to version four. For information on versioned objects. Working with Object Versions 273 . For example. When you export an object from the Navigator or workspace. the PowerCenter Client exports the latest version of the object. see “Running a Query” on page 232. your query results contain two mappings that use different versions of the same source. the target folder contains a target called WEEKLY_ORDERS and the latest version is three. or reusing the object. but the PowerCenter Client exports only the latest version selected for that object. see “Working with Versioned Objects” on page 199. If you export both mappings. see “Viewing Object History” on page 208. When you replace the target. If you want to export an earlier version of an object. you can select it from a query result or object history. For more information on viewing object history. select the objects to export and choose Tools-Export to XML File.Working with Object Versions You can export one version of an object at a time. In the View History or Query Results window. You can resolve an object conflict by replacing. When you import an object that exists in the target folder. the PowerCenter Client handles object versions differently depending on how you resolve the object conflict. the PowerCenter Client creates a new target definition and assigns it a version of one. renaming. Note: You cannot export deleted objects from a query result or object history. You import a target with the same name. When you reuse the target. For example. the PowerCenter Client does not change the version of the existing target definition. and does not change the version of the existing target definition. You can select multiple object versions to export. When you rename the target. For more information on running an object query. the PowerCenter Client exports only the latest version of the source.

274 Chapter 11: Exporting and Importing Objects . you can specify a folder from the global repository only. For more information on exporting the object a shortcut references. the PowerCenter Client creates a global shortcut. the PowerCenter Client creates a local shortcut. When the shortcut exists in a local repository. you can specify folders for the shortcut and the referenced object. The PowerCenter Client imports the shortcut object into the destination repository using the metadata in the XML file. When you import a shortcut into a global repository. The new shortcut points to the object in the folder you specify for the referenced object. whether or not you also import the referenced object into that folder. you can specify a folder from the local repository or the global repository in the domain. the import behavior is based on whether or not the PowerCenter Client finds the referenced object in the folder you specify: ♦ The PowerCenter Client finds the referenced object.Working with Shortcuts You can export and import local and global shortcuts. You might want to export the referenced object if it does not exist in the destination repository. When you import a shortcut. The type of shortcut the PowerCenter Client creates does not depend on the shortcut type specified in the XML file. The PowerCenter Client finds the referenced object in the folder because the object already existed in the folder. However. You can import the shortcut and the referenced object concurrently. When you export a shortcut. You always specify a folder for the referenced object. When both the shortcut and referenced object exist in the same repository. The PowerCenter Client writes a message notifying you it imported the actual object instead of the shortcut object. The PowerCenter Client creates a shortcut in the folder you specify. When the XML file does not contain the metadata for the referenced object. and the referenced object exists in a global repository in the same domain. ♦ When you import a shortcut into a local repository. see “Working with Dependent Objects” on page 270. The PowerCenter Client searches for the referenced object in the folder you specify to establish the shortcut. or because you imported it along with the shortcut. The PowerCenter Client does not find the referenced object. you can choose to export the object the shortcut references. it does not import the shortcut. the PowerCenter Client imports the actual object into the destination repository using the metadata in the XML file. Shortcut Types The type of shortcut the PowerCenter Client creates in the destination repository depends on the folders you specify for the shortcut and the referenced object. When the XML file contains the metadata for the referenced object.

The Designer creates a new source definition in the destination folder named Shortcut_To_Employees. Working with Shortcuts 275 . if the object is a source definition. However. you choose to import the shortcut. When you use the source definition in a mapping. so it imports the actual object instead. The XML file defines the metadata for the object. the default SQL used to extract data from the source defines the source as Shortcut_To_Employees. You use the Designer to import the shortcut into a different repository. The PowerCenter Client does not find an object with the same name in the folder you specified. You can use the imported object as you would the original object. This source definition is a copy of the original object. Also in the Import Wizard. you export a shortcut named Shortcut_To_Employees and you also export the referenced object. For example. and is not a shortcut. you might need to rename the source definition. but you do not import the referenced object. the folder does not contain an object with the same name as the referenced object specified in the XML file. you choose a folder in the destination repository to specify the location of an existing referenced object. you must rename the source definition (Employees) or enter a SQL override for the source qualifier connected to the source definition (renaming the source table Employees) for the PowerCenter Server to extract source data. In the Import Wizard.Importing Shortcuts to Sources When the PowerCenter Client imports the object instead of the shortcut. If the source table in the source database is named Employees. However. the imported object does not inherit any changes you make to the original object in the source repository.

For example. Workflow Manager. from the same folder that contains the referenced object.Exporting Objects When you export an object. the PowerCenter Client writes the definition of the object to an XML file. when you export shortcuts from the query results accessed from the Designer.dtd.Shortcut_to_Source1 from the Orders folder . including changes you made to them since you last saved the repository. The Designer exports the version of Source1 you have open in the Designer because you export an object. the PowerCenter Client exports the version of the object saved in the repository. Source1. When you export an object from the Repository Manager. The XML file complies with powrmart. the PowerCenter Client exports either the version of the object saved in the repository or the version of the object you have open in the Designer or Workflow Manager: ♦ Version saved in the repository. you run an object query from the Designer.Target1 from the Sales folder . When you export an object from the Designer. Version you have open in the Designer or Workflow Manager. pmrep. Therefore. Source1 in the Items folder Mapping1 in the Items folder Target1 in the Sales folder The Designer behavior depends on the other objects you export: Exported Objects .Mapping1 from the Items folder Designer Export Behavior The Designer exports the saved version of Source1 because you do not export any object from the same folder that contains the referenced object. the Designer exports either the version of the referenced object you have open in the Designer or the version of referenced object saved in the repository. Source1.Shortcut_to_Source1 from the Orders folder . or query results accessed from the Designer or Workflow Manager. After you export objects. ♦ However. the PowerCenter Client exports the latest version of the object. depending on the other objects you export. Mapping1. The shortcut references Source1 in the Items folder. When you export the latest version of an object. or the query results accessed from the Repository Manager. see “Modifying an Exported XML File” on page 277. For more information. 276 Chapter 11: Exporting and Importing Objects . the Designer exports the latest versions of all objects in the Items folder. including any change you made to it since you last saved it to the repository. you can modify the XML file. The query result contains the following objects: ♦ ♦ ♦ ♦ Shortcut_to_Source1 in the Orders folder.

and then import the mapping with the new values. do not associate a Source Qualifier transformation with a VSAM source. if powrmart. For example.dtd. The Modifiable Attributes column lists the attributes Exporting Objects 277 . Do not modify powrmart. suppose you have inconsistent column names across a mapping. You want to globally search and replace Cust_ID and Customers_ID with Customer_ID. For example. Modifying an XML file is an easy way to change the metadata for a repository object. You cannot modify attributes in an element containing a CRCVALUE unless the attribute is listed in Table 11-5 on page 278. However. You cannot modify attributes in an element if its parent element contains a CRCVALUE code.dtd says that an element must include a specified child element. unless the attributes are listed in Table 11-5 on page 278. make sure you include the child element. modify the values in the XML file. For example. regardless of CRCVALUE codes. Table 11-5 on page 278 lists the repository objects you can modify.dtd. Informatica restricts the elements and attributes you can modify in the XML file. Make sure the structure of the XML file complies with the constraints in powrmart. You can modify all attributes listed in Table 11-5 on page 278. Use the following rules when you modify XML files: ♦ Make sure you define metadata that you could create in the Designer or Workflow Manager. You can export the mapping into an XML file. ♦ ♦ ♦ ♦ ♦ ♦ Modifiable Objects You can modify some attributes and elements in an XML file. you can modify the XML attributes before importing the object into a repository.Modifying an Exported XML File After exporting an object. You can modify the BUSINESSNAME and DESCRIPTION attributes in any element.

Table 11-5. Modifiable Repository Objects Repository Object Source Type Relational Flat File VSAM MQ XML PeopleSoft Siebel SAP table SAP ALE IDoc TIBCO Null source Target Relational SAP BW XML MQ TIBCO Null target Reusable Transformation Mapping All Relational Flat File VSAM MQ XML PeopleSoft Siebel SAP table SAP ALE IDoc TIBCO Modifiable Attributes All All BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION All All All All BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION All All All All All All All All BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION All All Create New Yes Yes No No No No No No Yes Yes Yes Yes No No No Yes Yes Yes Yes Yes No No No No No No Yes Yes 278 Chapter 11: Exporting and Importing Objects .you can modify for an exported object and then import. The Create New column indicates which objects you can define directly in the XML file and then import.

Modifiable Repository Objects Repository Object Mapplet Type Relational Flat File PeopleSoft Siebel SAP table SAP ALE IDoc TIBCO Session Task Worklet Workflow Reusable Non-reusable Reusable Non-reusable Reusable Non-reusable N/A Modifiable Attributes All All BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION BUSINESSNAME DESCRIPTION All All All All All All All All All Create New Yes Yes No No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Exporting Objects 279 .Table 11-5.

4. is located in the PowerCenter Client directory. see “Importing Objects (ObjectImport)” on page 433. see “Resolving Object Conflicts” on page 281. the Import Wizard only shows Designer objects when you use the Designer. Resolve object conflicts. You can enter check in comments in the Import Wizard. 2. you use a control file to specify the same import options in the Import Wizard. The DTD file. ♦ ♦ ♦ Validating XML Files Against the DTD You can only import objects from a valid XML file. or Repository Manager. You can import all object types using the Repository Manager. The Import Wizard allows you to perform the following actions: ♦ ♦ Choose the XML file. For details. The XML file must comply with powrmart. For information on using pmrep to import objects. 3. 280 Chapter 11: Exporting and Importing Objects . Validates the objects in the XML file. Check in the objects and apply a label. For more information on resolving object conflicts.dtd. Match folders. see “The XML and DTD Files” on page 267. replace. you can apply a label to them.Importing Objects You can import objects from a valid XML file. When you import an object into a folder that contains an object with the same name. The PowerCenter Client validates the XML file against the DTD and parses the XML file before importing. you can check in the objects after you import them. the PowerCenter Client performs the following tasks: 1. the PowerCenter Client displays an error message and does not import the objects. powrmart. When you import an object. or reuse the object. When you import using pmrep. Parses the XML file. you can choose to rename. Choose an existing label or create a new one.dtd. You can choose all or some objects listed in the XML file. and only Workflow Manager objects when you use the Workflow Manager. When you use the Repository Manager to import objects into a versioned repository. you can match folders listed in the XML file with folders in the destination repository. Creates the objects in the repository. When you use the Repository Manager to import. If the XML file is not valid. When you import an object in the Designer.dtd. If you check in the objects. Workflow Manager. You can import objects that you exported from the same repository or a different repository. Choose which objects to import. If the XML file contains both Designer and Workflow Manager objects. Validates the XML file against powrmart. the Import Wizard appears.

When you create an object resolution rule. Resolving General Object Conflicts You can resolve some object conflicts by creating rules that apply to a set of objects. Importing Objects 281 . sometimes an object in the XML file has the same name as an object in the destination folder. For example. Resolve specific object conflicts. see “The XML and DTD Files” on page 267. Create rules on the Specify Rules for Conflict Resolutions page of the Import Wizard. For details on CRCVALUE codes. The CRCVALUE code determines whether or not you can modify certain elements and attributes. The PowerCenter Client does not import objects with CRCVALUE codes that have been modified nor objects that do not conform to PowerCenter specifications. You can choose to resolve object conflicts in the following ways: ♦ ♦ Create general object resolution rules. see “Steps for Importing Objects” on page 287. Resolving Object Conflicts When you import objects. the PowerCenter Client validates objects with CRCVALUE codes to ensure that certain elements and attributes of Designer objects in the XML file have not been modified. the PowerCenter Client resolves object conflicts for objects to which the rule applies. In addition. For more information on the Import Wizard. The PowerCenter Client validates each object in the XML file to ensure that it conforms to the PowerCenter specifications for that object. a mapplet cannot contain a target definition.Validating Objects You can only import valid objects into the repository.

Resolving General Conflicts During Import Column Select Criteria Description Choose the set of objects the rule applies to.All objects. Applies to objects of the type you choose. 282 Chapter 11: Exporting and Importing Objects . Applies to all objects with the label you choose. You can create multiple rules. Applies to all objects you import. You can select this option when you import objects into a versioned repository. .Objects of type. If multiple rules apply to one object.Figure 11-3 shows where you can resolve general object conflicts in the Import Wizard: Figure 11-3. . The PowerCenter Client applies the rules to objects in order.Resolve General Object Conflicts Apply rule to these objects. You can choose the following sets of objects: . the PowerCenter Client applies the uppermost rule only. Table 11-6 describes the different columns you define for each rule: Table 11-6.Objects in query. Applies to all objects that result from the object query you choose. You can select this option when you import objects into a versioned repository. Import Wizard . Use the buttons in the Import Wizard to move the rules up and down. .Objects with label. Choose how to resolve object conflicts.

Choose how to resolve the object conflicts. For example. You can resolve conflicts using the following methods: . you can specify a different name in the Conflict Resolution Wizard. choose the label name in this column. .Replace.Rename. Creates a new object in the destination folder with a new name. you can define the specific conflict resolutions in the Conflict Resolution Wizard. Replaces the existing object in the destination folder. Allows you to choose a resolution on an object by object basis. Figure 11-4 shows where you can resolve specific object conflicts in the Import Wizard: Figure 11-4.Prompt User.Table 11-6. When you choose Prompt User. After you create general object resolution rules. For more information on the Conflict Resolution Wizard. see “Resolving Specific Object Conflicts” on page 283.Resolve Specific Object Conflicts Importing Objects 283 . you can resolve specific object conflicts using the Import Wizard. Import Wizard . Uses the existing object in the destination folder. if you select Objects with label in the first column. . You can resolve specific object conflicts in the Import Wizard. Resolving General Conflicts During Import Column Select Value Select Resolution Description Choose a value that modifies the first column. Resolving Specific Object Conflicts Some object conflicts may still exist after you define rules to resolve conflicts. see “Resolving Specific Object Conflicts” on page 283. For more information on the Conflict Resolution Wizard. . When you choose Rename.Reuse.

Resolved. it opens the Conflict Resolution Wizard. ♦ When the Import Wizard detects unresolved conflicts for objects in a folder. After you resolve object conflicts in the Conflict Resolution Wizard. For information on resolving conflicts in the Copy Wizard. you can view or edit the object conflict resolutions by clicking View/Edit. It also displays the object resolution status for objects in each folder: ♦ Unresolved. The user interface is similar and you resolve the same type of object conflicts in both. The Import Wizard is ready to import these objects. Click Resolve to resolve the object conflicts. you return to the Import Wizard. Some objects in this folder conflict with objects in the target folder. see “Copying Objects” on page 297. No object in this folder conflicts with objects in the target folder. However.The Import Wizard displays all folders listed in the XML file. Figure 11-5 shows the Conflict Resolution Wizard: Figure 11-5. Conflict Resolution Wizard The Conflict Resolution Wizard is similar to the Copy Wizard. 284 Chapter 11: Exporting and Importing Objects . You must resolve all object conflicts before you can import objects.

Steps for Exporting Objects You can export objects from the repository using the Designer. 4. Repository Manager. click Advanced Options. For more information. Enter a name for the XML file and click Save. 2. In the Export Options dialog box. Workflow Manager. choose which dependent objects to export and click OK. see “Exporting Objects (ObjectExport)” on page 432. Choose Repository-Export Objects. To export objects from the query result or object history. query result. In the Navigator or workspace. select the objects to export and choose Tools-Export to XML File. select the objects to export. navigate to the directory where you want to save the XML file. For information on using pmrep to export objects. 5. 6. To export an object from the Designer. or object history. Choose which dependent objects to export. To choose which dependent objects to export. or Repository Manager: 1. 3. Workflow Manager. Open the folder that contains the objects you want to export. see “Working with Dependent Objects” on page 270. Steps for Exporting Objects 285 . In the Export dialog box.

286 Chapter 11: Exporting and Importing Objects . You can click View File to view the XML file the PowerCenter Client creates. Click Close in the Exported Objects dialog box. and displays export status in the Exported Objects dialog box: View the XML file the PowerCenter Client creates.The PowerCenter Client exports the objects to an XML file. 7.

For information on using pmrep to import objects. The Import Wizard opens to guide you through the process of importing the objects into the target folder. Open the folder into which you want to import an object. 2. Steps for Importing Objects 287 . Navigate to the directory where the XML file is located. To import an object: 1. You can compare objects when importing objects with the Import Wizard. see “Importing Objects (ObjectImport)” on page 433. or Repository Manager. In the Import Wizard. 3. Workflow Manager. Select the XML file and click OK. Choose Repository-Import Objects.Steps for Importing Objects You can import objects into the repository using the Designer. click Browse to locate the XML file.

288 Chapter 11: Exporting and Importing Objects . when you select Sources and click Add. When you import objects using the Repository Manager. you can select objects from one folder. For example. when you click a particular database definition node. To remove an object from the Objects to Import pane. Select a folder or repository in the Folders field. Click Next. 5. You can filter which objects to view in the Objects in File pane. you can select objects from multiple folders from one repository. After you add an object to the list of objects to import. the Import Wizard adds all objects listed under that node. When you select a node in the Objects in File pane and click Add. Note: When you import objects using the Designer or Workflow Manager. select the object and click Remove. Select the objects to import and click Add. You can right-click an object and choose Properties to view the properties associated with an object. the Import Wizard displays a check mark on the icon for objects in the Objects in File pane.4. the Import Wizard imports all sources listed under that database definition node. the Import Wizard adds all sources for that folder. Or.

Specify the folder properties in the Create Folder dialog box. 8. Click the Open button for a folder listed in the Import Wizard. or when you import a shortcut object in the Designer. You must select a different folder for each folder listed in the Import Wizard. Steps for Importing Objects 289 .6. You can match folders listed in the XML file to folders in the destination repository. Select a folder in the destination repository and click OK. Open Button This step of the Import Wizard appears when you import objects using the Repository Manager. The Folder Selection dialog box appears. Tip: You can create a new folder in the destination repository by clicking Create Folder. Click Next. 7.

To apply a label to all objects you import. In the Label Browser dialog box. select Check In and enter comments in the comment field. choose the label and click OK. You can check in the objects and apply labels to the them after importing. 10. 290 Chapter 11: Exporting and Importing Objects . You can only apply a label to the objects if you choose to check them in. Click Next. This step of the Import Wizard appears when you use the Repository Manager to import objects into a versioned repository.9. To check in all objects after importing them. 11. select Apply Label and click Select Label.

This step of the Import Wizard appears when you import objects using the Repository Manager. or all objects. 14. You can create rules to resolve general object conflicts. 13. Click Next. Choose to which objects to apply the rule and select a resolution. Click Next. You can apply rules to objects with a certain label. Steps for Importing Objects 291 . To create a new rule.12. objects listed in an object query. see “Resolving Object Conflicts” on page 281. objects of the same type. For more information on resolving object conflicts. click New Rule.

292 Chapter 11: Exporting and Importing Objects . You can save the comparison as a text or HTML file.The Import Wizard opens the Conflict Resolution Wizard for objects in one of the folders listed in the XML file. Click Compare Conflict to compare conflicting objects in the XML file and target repository. The Diff Tool window appears. see “Copying Objects” on page 297. The Conflict Resolution Wizard is similar to the Copy Wizard. 15. For information on resolving conflicts in the Copy Wizard. Use the Conflict Resolution Wizard to resolve specific object conflicts.

If the objects in the XML file exist in the target repository. the Targets window appears instead of the Diff Tool window. Steps for Importing Objects 293 . 16. Click Next to proceed through the Conflict Resolution Wizard. 17. Click Close when you resolve all the conflicts for this folder. Resolve object conflicts as they appear in the Conflict Resolution Wizard.

the Import Wizard proceeds with the import process. 294 Chapter 11: Exporting and Importing Objects .The Import Wizard opens the Conflict Resolution Wizard for objects in any other folder listed in the XML file. Click Resolve in the Action column for that folder to open the Conflict Resolution Wizard and resolve the object conflicts. You can click View/Edit to view or edit the object conflicts for the objects in that folder. When you resolve conflicts for all objects in all folders. Note: If you cancel the Conflict Resolution Wizard for a folder. the Import Wizard displays the status of that folder as unresolved.

The Output window displays the results of the import process. and displays the progress of the import process. Click Done. The PowerCenter Client imports the objects into the destination repository. Steps for Importing Objects 295 . 19. Errors and warnings are designated by colored text. Click Import in the Import Wizard to import the objects into the repository.18.

Troubleshooting The solutions to the following situations might help you with exporting and importing objects. the Designer must be able to connect to the source repository to re-establish the shortcut. Make sure that the metadata you define in the XML file is valid. make sure the source is not a VSAM source. 296 Chapter 11: Exporting and Importing Objects . For example. the Designer imported the actual object instead of the shortcut. The Designer marks mapplets with VSAM sources as invalid. I imported a mapping from an XML file I modified. When it cannot connect to the source repository. When I tried to import a shortcut to an object. You must be able to create the object you define in the Designer or Workflow Manager. if you edit the metadata for a mapplet. To import a shortcut to an object into a repository. it imports the object the shortcut references using the metadata in the XML file. but the Designer marked it invalid.

300 Steps for Copying Objects. 298 Resolving Copy Conflicts.Chapter 12 Copying Objects This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ Overview. 310 297 . 302 Viewing Object Dependencies. 305 Copying Workflow Manager Objects. 306 Copying Designer Objects.

Figure 12-1 shows the Copy Wizard: Figure 12-1. targets. sources.Overview The Workflow Manager. Compare Conflict Link Apply resolution to other conflicts. Next Conflict/ Option View Object Dependencies Overview Area 298 Chapter 12: Copying Objects . you must first open the target folder. and transformations. Designer. The Copy Wizard displays possible resolutions in the Resolution area of the screen. to a different folder. a description of the conflict displays in the Conflict Message section of the screen. You can copy objects within the same folder. If you want to copy an object to another folder. You can also copy segments of workflows or mappings. or skip copying the object. sessions. For a duplicate object you can rename. reuse. The Copy Wizard Copy From/ Copy To Conflict Message Edit name. The Copy Wizard checks for conflicts in the target folder and provides choices to resolve the conflicts. You can copy repository objects such as workflows. For example. and Repository Manager provide a Copy Wizard that allows you to copy repository objects. or to a different repository. mapplets. tasks. mappings. if an item exists in the target folder. worklets. replace.

Next Conflict/Option displays only with session or workflow conflicts that you resolve by renaming or replacing the target. see “Comparing Repository Objects” on page 45.It displays a red icon next to each object with a conflict. original instance name. Overview 299 . Displays the items to copy. For more information.Table 12-1 describes the areas of the Copy Wizard: Table 12-1. For more information. Displays object dependencies for the current object. and action taken to resolve the conflict. such as applying default connections or retaining server connections during the copy. depending on the conflict. Applies the resolution to all unresolved conflicts or just the conflicts for the same object type. and a green icon next to each object without a conflict. Choices might be different. the message describes the resolution. if any. Compares duplicate objects in the target folder to the objects you are copying. see “Viewing Object Dependencies” on page 305. target instance name. Copy Wizard Areas Area Copy From/Copy To Overview Area Description Displays the original repository and folder name and the target repository and folder name. Allows you to choose additional options for session and workflow resolutions. After you choose a resolution. existing conflicts. Displays the elected resolution or a list of choices for resolution. Enables you to edit the object name if you choose to rename the object. Identifies the current conflict and the name of the object with the conflict. Conflict Message Resolution Edit ApplyThisResolution to Other Conflicts Compare Conflict Next Conflict/Option View Object Dependencies You can configure display settings and functions of the Copy Wizard by choosing ToolsOptions in the Designer or Workflow Manager.

When an object with the same name exists in the target folder. When copying to another folder in the same repository or another folder in a different repository and an object with the same name exists in the target folder. When the Copy Wizard cannot find a server. The Copy Wizard provides you with the resolutions depending on the type of conflict. Click Browse to choose a server. it prompts you to resolve the conflict before continuing the copy process. You must select a valid object in the target folder for the copy process to succeed. Replace the existing object in the target folder. connection. Copy Wizard Resolutions Resolution Name Copy Browse Description Copy a connection object. or mapping in the target folder it displays the Browse button. Change the object name when copying it to the target folder. connection. Availability When the Copy Wizard cannot find a connection object in the target repository. When a reusable object exists in the target folder. When an object with the same name exists in the target folder. see “Comparing Repository Objects” on page 45. If the target folder has duplicate objects. you can compare them to the objects you are copying to determine the differences. Skips copying the object. or mapping. Click the Compare Conflict link on the Copy Wizard to display source and target views of the objects. Table 12-2 describes the Copy Wizard resolutions: Table 12-2. For more information about comparing repository objects. 300 Chapter 12: Copying Objects . Rename Replace Reuse Skip Use the existing object in the target folder.Resolving Copy Conflicts When the Copy Wizard encounters a conflict.

click Apply This Resolution To and choose either All Conflicts or conflicts for just the specified object type. Optionally. To apply the resolution to more objects. Resolving Copy Conflicts 301 . Copy Wizard Resolutions The wizard prompts you to select a resolution for each unresolved object in your copy.Figure 12-2 shows the conflict that occurs when you try to copy an object to a folder that already contains an object of the same name. or to all conflicts in your copy. you can apply the resolution to all unresolved objects of the same type. Figure 12-2. The selected resolution reuses the object.

The 302 Chapter 12: Copying Objects . To copy an object using the Copy Wizard: 1. Open the target folder. 2. For example. select the object you want to copy. It displays conflicts one object type at a time. 5. the sessions display under the Sessions node. click the Cancel button or press the Esc key. The Copy Wizard displays a red icon on objects with conflicts. 4. If you encounter a conflict. The Copy Wizard appears.Steps for Copying Objects Use the following procedure to copy an object using the Copy Wizard. For example. Figure 12-3 shows the first of two unresolved mapping conflicts to resolve. Click Yes on the Copy Confirmation prompt. In the Navigator. choose a resolution from the Resolution options. The Copy Wizard displays objects by type. and mappings display under the Mappings node. To cancel the copy operation. Click Next if you do not encounter a conflict. 3. Drag or copy the object into the target folder.

use Next Conflict/Option if you want to apply default connections in the target during the copy. Next Conflict/Option displays when you have session and workflow conflicts. Steps for Copying Objects 303 .resolution option requires you to browse for an appropriate mapping. Figure 12-1 on page 298 shows the Next Conflict/Option button. Click Next to view the next conflict. Figure 12-3. If you work with session or workflow conflicts. Copy Wizard Mapping Conflicts Copy Conflict 6. For example. 7. Repeat steps 5-6 until you resolve all conflicts. Click Browse to select a mapping. you can click Next Conflict/Option to configure additional options for sessions or workflows with conflicts. and you choose to Rename or Replace the target objects.

The Copy Summary information displays: 8. 304 Chapter 12: Copying Objects . Click Finish to complete the copy process.

Select the object from the Overview area of the Copy Wizard. The objects display upward in a hierarchy. For example. you might want to view the objects or instances that depend on the object you are copying.Viewing Object Dependencies When you copy an object. you can select the connection object in the Copy Wizard and see which sessions in the workflow use the connection. the Copy Wizard copies all dependent objects. Object You Selected In the Overview Area Dependent Objects Viewing Object Dependencies 305 . While you set up a copy. If there are no object dependencies. The Dependency dialog box displays the objects that use a selected object. Click the View Object Dependencies button. if you view the object dependencies of a connection object when you copy a workflow. the View Object Dependencies dialog box displays the following message: <<No dependencies found for this object. if you are going to copy a session and an associated connection object in a workflow. the Dependency dialog box shows the session that uses the source object and the workflow that uses the session.>> To view dependencies for an object: 1. For example. 2. The Dependency dialog box appears.

If you rename or replace the session you can use default mappings and connections. The Import Wizard also provides options to resolve conflicts. For details on resolving conflicts. ♦ Copying Sessions When you copy a Session task. To copy these objects. A session with the same name exists in the target folder. If the target folder has no mappings. you must resolve all conflicts that occur in the target folder. Cannot find server connection. ♦ 306 Chapter 12: Copying Objects . When you copy a workflow or worklet. the Copy Wizard looks for the database connections and associated mappings in the target folder. You can also use the Copy Wizard to copy segments of a workflow. see “Importing Objects” on page 280. worklets.Copying Workflow Manager Objects The Workflow Manager allows you to copy workflows. see “Resolving Copy Conflicts” on page 300. see “Workflow Manager Tasks” on page 511. A workflow. This includes the associated mapping and the database connection. If the mapping or connection does not exist. you can select a new mapping or connection. You can rename the existing session. Note: The Workflow Manager provides an Import Wizard that allows you to import objects from an XML file. If a server connection does not exist. you may need to choose the connections and mappings after you copy the session. worklet. Session conflicts. you must first copy a mapping to the target folder in the Designer before you can copy the session. When you copy a session. and sessions using the Copy Wizard. workflow segments. Cannot find server connection. For information on the privileges and permissions to copy Workflow Manager objects. you might encounter the following copy conflicts: ♦ ♦ Duplicate name. The server connection for this session does not exist in the target. For more information about the Import Wizard. sessions. and tasks included in the original workflow or worklet. When you copy a workflow. You cannot copy server connections. Copying Workflows and Worklets When you copy a workflow or a worklet. Server connections from the original workflow do not exist for the target. Otherwise. reuse the session in the target folder or replace it. or workflow component with the same name exists in the target folder. you can select a connection or skip the conflict and choose a server connection after you copy the workflow. the Copy Wizard checks session components for possible conflicts. the Copy Wizard copies all of the worklets. you might encounter the following copy conflicts: ♦ Duplicate name.

You must cancel the copy process to create a mapping. the Copy Wizard prompts you to create one: There are no mappings in this folder.♦ Cannot find mapping. If the mapping does not exist. Copy the connection to the target repository. the Copy Wizard either copies the variables to the target folder or retains the saved variable values already in the folder. The associated mapping is not in the target folder. Database Connection Conflicts When you copy a session to a different repository. Mapping Variables When you copy a session that uses mapping variable values. To avoid this problem you can copy the mapping to the target folder in the Designer before copying the session. Skip the connection conflict. the Copy Wizard does not copy any object. If a connection of the same name does not exist in the target. Note: You cannot copy server connections when you copy workflows. A database connection object does not exist in the target repository. If you replace a mapping with an invalid mapping. the Copy Wizard prompts you to either copy the connection information or choose another connection. To find available mappings in the target folder. click Browse. you must verify that the lookup or stored procedure database connection exists in the target folder to validate the session. After you copy the session. you can choose a different mapping from the target folder. the associated sessions become invalid. Cannot find database connections. even if the connection does not exist in the target folder. the Copy Wizard verifies that the associated mapping exists in the target folder. you can do one of the following: ♦ ♦ ♦ Select any connection of the same type in the target folder. Otherwise it uses the connection name in the session properties. If you have no mappings in the target. you must cancel the session copy. Copying Workflow Manager Objects 307 . Select connections from the target repository. ♦ Mapping Conflicts When you copy a session. Please create a mapping in the Mapping Designer. the session uses the same database connection name and type as it has in the source folder. If the target folder does not have any mapping in it. You can select an available mapping in the target folder. If you override the lookup or stored procedure database connection in the session properties. When you cancel.

When you overwrite the segment. you might encounter the following copy conflicts: ♦ Duplicate name. you cannot overwrite the original task with the copied task. Cannot find database connection. For example. You must select a new mapping. You can copy segments into workflows and worklets within the same folder. You paste a segment into another workflow or worklet containing a task instance with the same name as the one you are copying. The replaced session in the target folder does not have saved variable values. To avoid overwriting an object instance in a target workflow or worklet. or within a folder in a different repository. the Copy Wizard overwrites the task instance in the target workspace. the links between the tasks. If the target folder does not contain a mapping. it creates a new copy of the object you are pasting and renames it so that it does not overwrite any objects. You can copy reusable and non-reusable objects in segments. select any ♦ 308 Chapter 12: Copying Objects . but the target folder does not contain the associated database connection. You can also paste segments of workflows or worklets into an empty Workflow or Worklet Designer workspace. You copy a session into a folder to replace an existing session. The Workflow Manager retains the saved variable values in the target folder if you replace a session that already has saved variable values. You paste a segment to another folder without the associated mappings in the target folder. and any condition in the links. within another folder. The Copy Wizard creates a copy of the task and assigns it a new name. the conditions in the copied link overwrite the link conditions in the target workflow or worklet. A segment consists of one or more tasks. if you copy a segment from Workflow_A containing s_Session1 into Workflow_B containing a session named s_Session1. If you replace the task instance. If you copy to a folder in a different repository. You paste a segment to another folder. For reusable objects. you can resolve this conflict by replacing the task instance or renaming the task instance with a unique name. choose to create a copy of the instance instead of replace it. Note: You can copy individual non-reusable tasks by selecting the task and following the instructions for copying segments. you must copy a mapping to the target folder before you can copy the segment. When you copy a segment.The Workflow Manager copies the variable values to the target folder under the following conditions: ♦ ♦ You copy a session into a folder to create a new session. ♦ Cannot find mapping. and a connection of the same name does not exist. Copying Workflow Segments You can copy segments of workflows and worklets when you want to reuse a portion of workflow logic. If you copy and paste a task within the same workflow or worklet. The new session contains a mapping that has an associated mapping variable from the copied session. Each time the Copy Wizard locates a duplicate instance in the target workflow or worklet.

Select a segment by highlighting each task you want to copy. 3. Copying Workflow Manager Objects 309 . The Copy Wizard opens and notifies you if it finds copy conflicts. 2. or skip the connection conflict. Choose Edit-Paste or press Ctrl+V. If you paste a segment containing a user-defined workflow or worklet variable. You can also select segments by dragging the pointer in a rectangle around objects in the workspace. Copy the segment to the clipboard. To copy a segment from a workflow or worklet: 1. You can also copy the object into the Workflow or Worklet Designer workspace. 4. You can select multiple reusable or non-reusable objects. copy the connection to the target repository. Open the workflow or worklet into which you want to paste the segment. User-defined workflow variables are only valid in the workflow or worklet in which they were created. 5. expressions using the variable become invalid. Open the workflow or worklet.connection of the same type in the target folder. ♦ Segment contains user-defined workflow variable.

Copy SAP Program information. When copying a Normalizer transformation.Copying Designer Objects You can copy Designer objects within the same folder. or shortcut. Choose the Copy SAP Program Information checkbox. select this option to retain the current value of the generated key sequence. For more information about ABAP programs see the PowerCenter Connect for SAP R/3 documentation. select the Sequence Generator and Normalizer Current Value to retain the current value of the sequence number. For more information on resolving conflicts. If you copy Sequence Generator transformations. When you copy objects you might have duplicate objects in the target folder. target. mappings. You can copy segments across folders or repositories. When you copy Designer objects. If you copy an SAP R/3 mapping. You might have some duplicate components in the target folder. transformations. ♦ ♦ ♦ Copying Mapping and Mapplets Segments You can copy segments of mappings and mapplets when you want to reuse a portion of the mapping logic. To copy mapping segments. A segment can include a source. and dimensions. 310 Chapter 12: Copying Objects . targets. You can copy any of the Designer objects such as sources. You can resolve these conflicts individually. select and copy the segments from the Mapping Designer and paste them into a target mapping or an empty mapping or mapplet workspace. Retain current values in reusable Sequence Generator or Normalizer transformations. see “Resolving Copy Conflicts” on page 300. A segment consists of one or more objects in a mapping or mapplet. you might have the following copy conflicts or options: ♦ Duplicate item name. see “Designer Tasks” on page 510. When you copy a mapping or mapplet. transformation. Copy a source included in a primary key-foreign key relationship that is not included in the mapping. or you select resolutions all at once. mapplets. the Copy Wizard asks you if you want to copy the referenced object. or to a different repository. you must resolve all conflicts that occur in the target folder. To copy these objects. This option displays when you copy an SAP R/3 mapping across repositories. see “Resolving Copy Conflicts” on page 300. you can choose to copy the associated installed ABAP program. the wizard attempts to copy all the components of the mapping to the target. For information on the privileges and permissions to copy designer objects. This option displays only when you copy Sequence Generator or Normalizer transformations. For details on resolving conflicts. mapplet. You must open the target folder before you can copy to it. When you copy a mapping with a source object that has a primary keyforeign key relationship with another object not included in the mapping. to a different folder.

You can select multiple objects. Choose Edit-Paste or press Ctrl+V. Select a segment by highlighting each object you want to copy. Open a target mapping or mapplet. 2. 3. You can also paste the segment into an empty workspace. Open a mapping or mapplet. the Designer assigns a unique name to the new object. You can also select segments by dragging the pointer in a rectangle around objects in the workplace. If you are creating duplicate objects in a folder.To copy a segment of a mapping or mapplet: 1. 4. 5. Copying Designer Objects 311 . Copy the segment to the clipboard by pressing Ctrl+C or choosing Edit-Copy.

312 Chapter 12: Copying Objects .

319 313 . 316 Steps for Importing Metadata.Chapter 13 Exchanging Metadata This chapter includes the following topics: ♦ ♦ ♦ Overview. 314 Steps for Exporting Metadata.

For more information on exporting and importing objects. see “Exporting and Importing Objects” on page 263. To exchange metadata between PowerCenter and another tool. The Repository Manager uses a wizard to guide you through the export or import process. see “Steps for Importing Metadata” on page 319. you can use one of the follow methods: ♦ Use PowerCenter as the source tool. In PowerCenter. For more information on importing metadata. For more information on exporting metadata. You do not need a PowerCenter Metadata Exchange option license key. To exchange metadata you export the metadata from the source tool and import the metadata into the target tool.Overview You can use the Repository Manager to share source and target metadata with other business intelligence (BI) and data modeling tools. see “Steps for Exporting Metadata” on page 316. export metadata to a file recognized by the source tool. In the source BI or data modeling tool. For information on resolving conflicts in the Copy Wizard. 314 Chapter 13: Exchanging Metadata . such as Business Objects Designer. MIMB uses the specifications in powrmart. but you must be able to export or import XML files that conform to powrmart. When the Metadata Import Wizard detects object conflicts during import. The wizard prompts you for different options. The Conflict Resolution Wizard is similar to the Copy Wizard.dtd to exchange metadata with PowerCenter. see “Copying Objects” on page 297. export metadata to a file recognized by the target tool. Inc. select an object and choose Repository-Export Metadata. and then use PowerCenter to import metadata from the file. Use the BI or data modeling tool as the source tool. You can export to and import from the following BI and data modeling tools: ♦ ♦ ♦ ♦ ♦ ♦ Business Objects Designer Cognos ReportNet Framework Manager IBM DB2 Cube Views IBM Rational Rose Microsoft Visio Database Oracle Warehouse Builder Cognos Impromptu You can import from the following BI tool: ♦ Note: You can also exchange metadata with BI and data modeling tools by using the Export Objects and Import Objects menu commands. it opens the Conflict Resolution Wizard. select a folder and choose Repository-Import Metadata. To import metadata. PowerCenter uses the Meta Integration® Model Bridge (MIMB) from Meta Integration Technology. and then use the target BI or data modeling tool to import metadata from the file. PowerCenter can be the source or target tool. to exchange metadata with other BI and data modeling tools.dtd. ♦ To export metadata. depending on the BI or data modeling tool.

you can export targets to some tools as dimensions. Overview 315 . see “Working with PowerCenter Licenses” on page 119. When you export a source or target with a foreign key. You cannot export shortcuts. the Repository Agent also exports the source or target containing the corresponding primary key.Rules and Guidelines Consider the following rules and guidelines when you exchange metadata with BI or data modeling tools: ♦ ♦ ♦ ♦ ♦ ♦ ♦ You can export and import relational source and target definitions. However. You cannot export cubes and dimensions. You can export multiple source definitions or multiple target definitions at a time. For more information on licenses. You must have a Metadata Exchange option license key to exchange metadata for a specific tool. You can import multiple source and target definitions at a time. You cannot export source and target definitions at the same time.

Choose a path and file name. and choose Repository-Export Metadata. You can click More Info to read about the tool requirements. The Metadata Export Wizard appears.Steps for Exporting Metadata Use the following procedure to export metadata from PowerCenter to a file recognized by the target BI or data modeling tool. In the Repository Manager Navigator. To export metadata: 1. 2. select the object or objects you want to export. 316 Chapter 13: Exchanging Metadata . Choose the target tool you want to export the object to.

Choose a path and file name for the target file.3. 5. The Metadata Export Wizard displays options specific to the tool you select. Steps for Exporting Metadata 317 . and click Next. Click Next. Enter the options specific for the tool to which you are exporting. 6. The consistency check verifies the object meets the metadata requirements for the target tool. Choose the level of consistency checking you want MIMB to perform. 4.

318 Chapter 13: Exchanging Metadata . 8. Click Finish to close the wizard. You can click Show Details to view detailed messages about the metadata conversion. You can click Save Log to save the message log to a text file. Click Export.7.

The wizard uses the file name as the source database name for each object you import. Choose the target tool from which you want to import the object. You can click More Info to read about the tool requirements. Steps for Importing Metadata 319 . The Metadata Import Wizard appears.Steps for Importing Metadata Use the following procedure to import metadata from a file created by another BI or data modeling tool. 2. To import metadata: 1. select the folder into which you want to import metadata. and choose Repository-Import Metadata. In the Repository Manager.

The PowerCenter Options page of the wizard appears. 5. Enter the options specific for the tool from which you are importing.3. 320 Chapter 13: Exchanging Metadata . 6. Click Next. 4. Click the Browse button to navigate to the file that contains the metadata. such as IBM DB2 Cube Views. Enter the PowerCenter options. The Metadata Import Wizard displays options specific to the tool you select. and click Next.

or you can override the database type by choosing a database type here. The code page of the repository you import the metadata into. The number of spaces used to indent the file you import. Steps for Importing Metadata 321 . Default is source. If you do not specify a DBD. Indicates whether or not to retain the column properties when you replace an existing object. The Metadata Import Wizard converts the metadata in the file to a format recognized by PowerCenter.Table 13-1 describes the PowerCenter options you define in the Metadata Import Wizard: Table 13-1. You can create source or target definitions. Default is auto detect. Click Next. Default is MS1252. Default is False. Default is no indentation.PowerCenter Options Option Table Type Database Type Require/ Optional Required Required Description The type of repository objects to create. Database Name Optional Codepage Indentation Retain Physical Properties Required Optional Optional 7. Metadata Import Wizard . Choose the database type for the source or target definitions the wizard creates. The DBD under which you want to group the repository objects in the Navigator. the Metadata Import Wizard groups all objects under a DBD based on the source or target database. The wizard can define the object definition database type based on the metadata defined in the file.

the Metadata Import Wizard opens the Conflict Resolution Wizard. In the Object Selection page.You can click Save Log to save the message log to a text file. The Conflict Resolution Wizard is similar to the Copy Wizard. Use the Conflict Resolution Wizard to resolve specific object conflicts. see “Copying Objects” on page 297. Click Next. 8. For information on resolving conflicts in the Copy Wizard. select which objects to import into the repository. If the folder contains objects with the same name as those you import. 9. You can click Show Details to view detailed messages about the metadata conversion. 322 Chapter 13: Exchanging Metadata . The Metadata Import Wizard adds the objects to the folder in the repository. and click Finish.

11. Click Compare Conflict to compare conflicting objects in the import file and target repository. 12. Steps for Importing Metadata 323 . Click Close when you resolve all conflicts. The Metadata Import Wizard imports all objects.10. Click Next to proceed through the Conflict Resolution Wizard. For more information on comparing sources or targets. Resolve object conflicts as they appear in the Conflict Resolution Wizard. see “Comparing Objects” in the Designer Guide.

324 Chapter 13: Exchanging Metadata .

332 325 . 328 Editing Reusable Metadata Extensions. 327 Creating Reusable Metadata Extensions. 331 Deleting Reusable Metadata Extensions. 326 Working with Metadata Extensions.Chapter 14 Metadata Extensions This chapter covers the following topics: ♦ ♦ ♦ ♦ ♦ Overview.

and view user-defined metadata extensions. when you create a mapping. you add them to this domain. but you cannot create. User-defined metadata extensions exist within the User Defined Metadata Domain. you may see domains such as Ariba or PowerCenter Connect for Siebel. PowerCenter Client applications can contain the following types of metadata extensions: ♦ Vendor-defined. delete. You can create. If you are using third-party applications or other Informatica products. delete. User-defined. Vendor-defined metadata extensions exist within a particular vendor domain. For example. edit. ♦ All metadata extensions exist within a domain.Overview Informatica allows end users and partners to extend the metadata stored in the repository by associating information with individual objects in the repository. You cannot edit vendordefined domains or change the metadata extensions in them. or view metadata extensions. you can store your contact information with the mapping. When you create metadata extensions for repository objects. You can also change the values of user-defined extensions. Third-party application vendors create vendor-defined metadata extensions. You create user-defined metadata extensions using PowerCenter. edit. You can view and change the values of vendor-defined metadata extensions. You associate information with repository metadata using metadata extensions. Both vendor and user-defined metadata extensions can exist for the following repository objects: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Source definitions Target definitions Transformations Mappings Mapplets Sessions Tasks Workflows Worklets 326 Chapter 14: Metadata Extensions . You see the domains when you create. or redefine them.

♦ ♦ To create. You associate reusable metadata extensions with all repository objects of a certain type. and delete non-reusable metadata extensions for sources. that extension is available only for the target you edit. and delete non-reusable metadata extensions for sessions. edit. You can promote a non-reusable metadata extension to reusable. and delete reusable user-defined metadata extensions. and delete reusable metadata extensions for all types of repository objects. it is available for all mappings. targets. but you cannot change a reusable metadata extension to non-reusable. and worklets. Create. For details. you must have one of the following privileges: ♦ ♦ Administer Repository Super User Working with Metadata Extensions 327 . You can also promote non-reusable metadata extensions to reusable extensions. edit. Therefore. It is not available for other targets. Workflow Manager.Working with Metadata Extensions You can create reusable or non-reusable metadata extensions. For details. If you want to create. and delete metadata extensions for multiple objects at one time. see “Using the Workflow Manager” in the Workflow Administration Guide. if you edit a target and create a non-reusable extension for it. transformations. Create. Non-reusable extensions are associated with a single repository object. and delete user-defined metadata extensions using the following tools: ♦ Designer. mappings. edit. So. use the Repository Manager. when you create a reusable extension for a mapping. and mapplets. Create. edit. edit. workflows. see “Using the Designer” in the Designer Guide. You can create. Repository Manager. edit. You can also promote non-reusable metadata extensions to reusable extensions. Vendor-defined metadata extensions are always reusable.

To create a reusable metadata extension: 1. The Edit Metadata Extensions dialog box opens. they appear in their own domains. If vendor-defined metadata extensions exist. the SourceCreator extension appears on the Metadata Extensions tab. 2. User-Defined Metadata Extensions This dialog box lists the existing user-defined and vendor-defined metadata extensions. Click Add. Open the User Defined Metadata Domain. the metadata extension becomes part of the properties of that type of object. Choose Edit-Metadata Extensions. For example. User-defined metadata extensions appear in the User Defined Metadata Domain. 4. 328 Chapter 14: Metadata Extensions . When you create a reusable metadata extension for any type of repository object. 3. suppose you create a reusable metadata extension for source definitions called SourceCreator. Anyone who creates or edits a source can enter the name of the person that created the source into this field. When you create or edit any source definition in the Designer. In the Repository Manager.Creating Reusable Metadata Extensions You can create reusable metadata extensions for repository objects using the Repository Manager. connect to the appropriate repository.

you can enter a default value of more than one line. Table 14-1 describes the options available in the Add Metadata Extension dialog box: Table 14-1. Object Type Required Database Type Required for source and target definition objects Required Optional Datatype Default Value Creating Reusable Metadata Extensions 329 .147. An optional default value. For a string metadata extension. string. 5. if you create a metadata extension for Expression transformations. The database type. or boolean.647 and 2.483. This can be a source definition. You can select a single database type or all database types. You associate metadata extensions with specific types of transformations. target definition. mapplet. For a numeric metadata extension. or all of these objects. For a boolean metadata extension. For example.647. workflow.The Add Metadata Extensions dialog box opens.147. Metadata extension names cannot contain any special character except underscore. transformation. up to 2. it is available only for Expression transformations. Enter the metadata extension information.483. choose true or false.483. session.147.647 bytes. mapping. Metadata extension names must be unique for each type of object in a domain. the value must be an integer between -2. worklet. Options for Creating Reusable Metadata Extensions Field Extension Name Required/ Optional Required Description Name of the metadata extension. The datatype: numeric (integer). and they cannot begin with a number. The type of repository object to which the metadata extension is associated. The database type is required for source and target definition objects.

the Repository Manager grants Share Read permission as well. Specifies whether the value of the metadata extension is editable in PowerCenter. The Repository Manager enables this option when third-party application vendors create vendor-defined metadata extensions only. Options for Creating Reusable Metadata Extensions Field Maximum Length Client Visible Client Editable Required/ Optional Required for string objects Optional Optional Description The maximum length for string metadata extensions. Optional Click Create. Specifies whether the metadata extension is visible in PowerCenter.Table 14-1. 330 Chapter 14: Metadata Extensions . Click Done. 7. the Repository Manager grants Client Visible permission as well. Optional description of the metadata extension. If you enable Share Write permission. If you select this option. Specifies whether the metadata extension is visible in vendor domains. Specifies whether the metadata extension is private to the domain in which it is created. Specifies whether the value of the metadata extension is editable across vendor domains. Share Read Share Write Optional Optional Private Optional Description 6.

You can modify the following fields: ♦ ♦ ♦ Default Value Permissions Description Editing Reusable Metadata Extensions 331 . Note: You cannot edit vendor-defined metadata extensions.Editing Reusable Metadata Extensions You can edit user-defined. and then click Edit. When you edit a reusable metadata extension. select the appropriate metadata extension in the Metadata Extensions dialog box. To change the value of a metadata extension. edit the repository object using the Designer or Workflow Manager. reusable metadata extensions for repository objects using the Repository Manager. you change the properties of the metadata extension. To edit a reusable metadata extension.

332 Chapter 14: Metadata Extensions . To delete a reusable metadata extension. Note: You cannot delete vendor-defined metadata extensions. When you delete a reusable metadata extension for a repository object.Deleting Reusable Metadata Extensions You can delete user-defined. reusable metadata extensions for repository objects using the Repository Manager. and click Delete. you remove the metadata extension and its values from the properties of all objects of that type. select the appropriate extension in the Metadata Extensions dialog box.

338 Source Views. 401 333 . 339 Target Views. 398 Folder View. 392 Repository View. and Task Views. 334 Database Definition View.Chapter 15 Using Metadata Exchange (MX) Views This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Viewing the Repository Metadata. 371 Security Views. 353 Metadata Extension Views. 366 Workflow. 395 PowerCenter Server Views. 390 Deployment Views. Worklet. 396 Change Management Views. 364 Transformation Views. 347 Mapping and Mapplet Views.

Table 15-1 lists the available MX views by category: Table 15-1. Therefore. Provides repository details such as repository name and connection information. Provides details such as server name and host name. Informatica strongly advises against altering the tables or data within the tables. see “Transformation Views” on page 366. see “Source Views” on page 339. Provides details of transformation instances by folder. and transformations used in mappings and mapplets by folder. For more information. use MX to access the repository. Provides a list of source definitions by folder. see “Mapping and Mapplet Views” on page 353. see “Database Definition View” on page 338. see “Target Views” on page 347. see “Deployment Views” on page 392. MX View Categories Category Database Sources Targets Mappings and Mapplets Description Provides a list of database definitions in the repository. Provides deployment details such as deployment groups and objects that were deployed from one repository to another. Provides a list of sources. For more information. see “Metadata Extension Views” on page 364. Provides static and run time details for workflows and worklets by folder. see “PowerCenter Server Views” on page 396. Metadata Extensions Transformations Workflows. see “Security Views” on page 390. do not directly access the actual repository tables. For more information. Provides user and group information. Worklet. Informatica is not responsible for corrupted data that is caused by customer alteration of the repository tables or data within those tables. For more information. MX View Categories MX views provide information to help you analyze metadata stored in the repository. For more information. Warning: The PowerCenter repository tables have an open architecture. Instead. For more information. Provides a list of target definitions by folder. Worklets. see “Repository View” on page 395. The Repository Manager generates these views when you create or upgrade a repository. For more information. For more information. and Task Views” on page 371. For more information. For more information. targets.Viewing the Repository Metadata Informatica Metadata Exchange (MX) provides a set of relational views that allow easy SQL access to the Informatica metadata repository. and Tasks Security Deployment Repository PowerCenter Server 334 Chapter 15: Using Metadata Exchange (MX) Views . Provides details of metadata extensions defined for objects. see “Workflow. Although you can view the repository tables. For more information.

Reduces time and resources required to support end-user requests. you could use REP_TBL_MAPPING. Note: The Designer includes an option to Save MX Data. such as Crystal Reports. see “Change Management Views” on page 398. For IS professionals. Using PowerCenter Metadata Reporter PowerCenter Metadata Reporter is a reporting tool that enables you to browse and analyze PowerCenter metadata. you could use the REP_SRC_MAPPING view to see how many mappings include this source. and you need to re-import the source definition into your repository. The prepackaged dashboards and reports enable you to analyze the following types of metadata stored in a PowerCenter repository: ♦ ♦ ♦ ♦ ♦ ♦ Source and target metadata Transformation metadata Mapping and mapplet metadata Workflow and worklet metadata Session metadata Change management metadata Viewing the Repository Metadata 335 . You can use these views to create reports using third-party reporting tools. Provides details such as folder name and description. data fields. see “Folder View” on page 401. mappings.Table 15-1. and transformation data. which can be easily customized to meet your business needs. For more information. MX allows you to drill down to the operational metadata level and expose information needed to support decisions. You can add comments to any object within PowerCenter through the Designer and Workflow Manager. table relationships. which is enabled by default. and data transformations. For example. the MX architecture provides the following benefits: ♦ ♦ ♦ Improves warehouse maintenance and management capability. Almost all views support access to comment information. MX facilitates the integration of decision support metadata between the PowerCenter repository and popular Decision Support System (DSS) tools. if a source table changes. data modeling tools. and any other metadata resources. The Metadata Reporter prepackages a set of reports and dashboards. Likewise. MX also helps you make precise information requests that draw from data models. MX View Categories Category Changed Management Folders Description Provide version history of object and label details. Expands the ability to provide information resources in a controlled manner. For more information. You can access comments about individual tables. if you want to view source and target dependencies for a mapping.

sq_) in the Designer.sq_ sybmxbld. Table 15-3 lists the SQL scripts to drop MX views: Table 15-3. SQL Script to Create MX Views Repository Database DB2 Informix Oracle Microsoft SQL Server Sybase Teradata SQL Script db2mxbld. the Repository Server executes a SQL script.♦ ♦ User and group metadata Operational metadata See the PowerCenter Installation and Configuration Guide for more information. the Repository Server executes a SQL script that drops the MX views.sq_ infmxbld. Table 15-2 lists the SQL scripts to create MX views: Table 15-2. SQL Definition of Views PowerCenter provides two sets of SQL scripts: one to create the MX views and one to drop MX views.sq_ sqlmxbld.sq_ infmxdrp.sq_ 336 Chapter 15: Using Metadata Exchange (MX) Views .sq_ oramxbld. You can run these SQL scripts (*mxdrp. Creating MX Views Each time you create or upgrade a repository.sq_ oramxdrp.sq_ termxbld. Dropping MX Views If you delete a repository.sq_ sqlmxdrp. SQL Script to Drop MX Views Repository Database DB2 Informix Oracle Microsoft SQL Server SQL Script db2mxdrp. that creates the MX views.sq_ These SQL scripts are stored in the PowerCenter Repository Server installation directory.

Integrating MX Views with Third-Party Software With MX software and support from Informatica. from pulling the Informatica metadata into product or user repositories to providing dynamic desktop pass-through access. Software vendors can integrate Informatica metadata with their products through different methods. SQL Script to Drop MX Views Repository Database Sybase Teradata SQL Script sybmxdrp. vendors of popular query and reporting tools can quickly create a metadata link between their products and the PowerCenter repository. The next generation of MX.sq_ termxdrp.sq_ These SQL scripts are stored in the PowerCenter Repository Server installation directory. called Metadata Exchange SDK. provides an object-based Application Programming Interface (API) to read and write metadata in Informatica repositories.Table 15-3. Viewing the Repository Metadata 337 .

REP_DATABASE_DEFS Table 15-4 lists database definition details: Table 15-4. Folder name. and the folder where the database definition resides. A database definition includes the source database names. 338 Chapter 15: Using Metadata Exchange (MX) Views .Database Definition View The database definition view provides a list of all database definitions in the repository. Version ID of the source. flat file or RDBMS. Informatica recommends using the fields in bold to join views. REP_DATABASE_DEFS MX View Column Name DATABASE_NAME DEF_SOURCE SUBJECT_AREA VERSION_ID Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER Description Database definition name. Source of the definition. MX provides the REP_DATABASE_DEFS view to help you analyze database definitions.

REP_ALL_SOURCES MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_SOURCE_NAME PARENT_SOURCE_BUSINESS_NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) Description Folder name. see “REP_ALL_SOURCE_FLDS” on page 341. This view provides a list of relational database table sources that have been analyzed through the Source Analyzer tool or imported from a DDL (Data Definition Language) file. This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View. Sources include both relational sources and non-relational sources such as XML files and flat files. see “REP_SRC_FILES” on page 343. This view provides a list of all file definitions in the repository. version. For more information. For more information. see “REP_SRC_TBL_FLDS” on page 346. Table 15-6 lists source information in the REP_ALL_SOURCES view: Table 15-6. Source definitions can be defined for both relational and nonrelational sources. Table 15-5 lists the different views that help you analyze source metadata: Table 15-5. For more information.Source Views Source views provide a list of the latest version of all source definitions defined by folder of any PowerCenter repository. Name of the parent source Business name of the parent source. Source Views View REP_ALL_SOURCES REP_ALL_SOURCE_FLDS Description This view provides a list of the latest version of sources defined in each folder of a repository. They also provide information such as source columns. For more information. and business name. see “REP_SRC_TBLS” on page 344. Folder ID. This view provides access to the fields in relational sources. source metadata extensions. Source Views 339 . You can use the source name to retrieve all the fields belonging to the source. These views also show source properties such as shortcuts. For more information. see “REP_ALL_SOURCES” on page 339. For more information. REP_SRC_FILES REP_SRC_TBLS REP_SRC_FILE_FLDS REP_SEG_FLDS REP_SRC_TBL_FLDS REP_ALL_SOURCES This view provides a list of the latest version of sources defined in each folder of a repository. These views provide access to the fields in a non-relational source. creation date. and mappings and mapplets where these sources are used. description. see “REP_SRC_FILE_FLDS and REP_SEG_FLDS” on page 345. column properties.

UTC time (Coordinated Universal Time) when the parent source was checked in. 340 Chapter 15: Using Metadata Exchange (MX) Views . Parent source version status. REP_ALL_SOURCES MX View Column Name PARENT_SOURCE_ID PARENT_SOURCE_DESCRIPTION PARENT_SOURCE_VERSION_NUMBER PARENT_SOURCE_VERSION_STATUS PARENT_SOURCE_UTC_CHECKIN PARENT_SOURCE_UTC_LAST_SAVED PARENT_SOURCE_CREATION_TIME PARENT_SOURCE_SCHEMA_NAME PARENT_SOURCE_FIRST_FIELD_ID PARENT_SOURCE_SELECT_INFO_ID PARENT_SOURCE_DISPLAY_SIZE PARENT_SOURCE_PHYSICAL_SIZE PARENT_SRC_MIN_PHYSICAL_SIZE PARENT_SOURCE_DATABASE_NAME PARENT_SOURCE_TYPE PARENT_SOURCE_DATABASE_TYPE SUBJECT_AREA SUBJECT_ID SOURCE_NAME SOURCE_ID SOURCE_DESC SOURCE_VERSION_NUMBER SOURCE_VERSION_STATUS SOURCE_UTC_CHECKIN SOURCE_UTC_LAST_SAVED SOURCE_LAST_SAVED Datatype NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (50) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER Description ID of the parent source. Source version number. Name of the source schema. Physical size (compressed binary). Source version number. Source description. Folder ID. ID of the first field in the source. UTC time when the parent source was last modified.Table 15-6. Description of the parent source. Parent source physical size (compressed binary). Source ID. Time when the parent source was last modified. UTC time for source checkin. Folder name. UTC time when the source display was last saved. Name of the database type of the parent source. File organization information. Specifies whether the source is a relational or a non-relational source. Specifies whether the source version is active or has been deleted. Database name of the parent source. Parent source display size (uncompressed binary). Time when the source was last saved. Source name.

the names of shortcut and the parent targets display. Description of the parent source. UTC time when the parent source was last saved. REP_ALL_SOURCE_FLDS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_SOURCE_NAME PARENT_SOURCE_BUSINESS_NAME PARENT_SOURCE_ID PARENT_SOURCE_DESCRIPTION PARENT_SOURCE_VERSION_NUMBER PARENT_SOURCE_VERSION_STATUS PARENT_SOURCE_UTC_CHECKIN PARENT_SOURCE_UTC_LAST_SAVED PARENT_SOURCE_CREATION_TIME PARENT_SOURCE_TYPE PARENT_SOURCE_DATABASE_NAME PARENT_SOURCE_DATABASE_TYPE Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) NUMBER VARCHAR2 (240) VARCHAR2 (50) Description Parent folder name. Status of the parent source version. The repository name.Table 15-6. Parent source ID. the name of the shortcut displays. Specifies whether the source is a global shortcut. Table 15-7 lists source field information in the REP_ALL_SOURCE_FLDS view: Table 15-7. REP_ALL_SOURCES MX View Column Name SOURCE_DATABASE_NAME REPOSITORY_NAME IS_SHORTCUT IS_GLOBAL_SHORTCUT Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER Description Source database name. UTC time when the parent source was checked in. Version number of the parent source. 1 = shortcut. Business name of the parent source. For local shortcuts. Specifies whether the source is a shortcut. Source type such as relational database or flat file. REP_ALL_SOURCE_FLDS This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View. Parent source name. 0 = not a shortcut. Time when the parent source was last modified. Parent folder ID. 1 = shortcut. Database type of the parent source. Source Views 341 . 0 = not a shortcut. Database name of the parent source. For global shortcuts. Informatica recommends using the fields in bold to join views.

Display field length. Specifies whether the source version is active or has been deleted. Source ID. Field level number for non-relational sources. Business name of the source field. Source field name. Source field number. Offset of this field within the source. 342 Chapter 15: Using Metadata Exchange (MX) Views . REP_ALL_SOURCE_FLDS MX View Column Name SUBJECT_AREA SUBJECT_ID SOURCE_NAME SOURCE_ID SOURCE_DESCRIPTION SOURCE_VERSION_NUMBER SOURCE_VERSION_STATUS SOURCE_UTC_CHECKIN SOURCT_UTC_LAST_SAVED SOURCE_LAST_SAVED SOURCE_DATABASE_NAME SOURCE_FIELD_NAME SOURCE_FIELD_BUSINESS_NAME SOURCE_FIELD_ID SOURCE_FIELD_DESCRIPTION SOURCE_FIELD_NUMBER SOURCE_FIELD_NEXT_FIELD_ID SOURCE_FIELD_LEVEL SOURCE_FIELD_PICTURE_TEXT SOURCE_FIELD_OCCURS_TIME SOURCE_FIELD_REDEFINES_FIELD SOURCE_FIELD_DISPLAY_OFFSET SOURCE_FIELD_DISPLAY_LENGTH SOURCE_FIELD_PHYSICAL_OFFSET SOURCE_FIELD_PHYSICAL_LENGTH SOURCE_FIELD_CHILD_FIELD_ID Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Description Folder name. ID of the field that follows the current field. The next child. for a non-relational COBOL source. Picture text that a COBOL source uses. Time when the source was last saved. UTC time when the source was last checked in. Folder ID. Source version number. Physical field length. if any. Identifies the field/record that this field/ record redefines. Offset of this field within this FD. Null for relational sources. Source name. UTC time when the source was last saved.Table 15-7. Number of time that the field (or record) occurs in the source. ID of the source field (primary key). Description of the source field. Name of the database for the source. Source description.

Scale for the field. Minimum physical size (varying records). Informatica recommends using the fields in bold to join views. 1 = shortcut. REP_SRC_FILES MX View Column Name FILE_ID SUBJECT_AREA DATABASE_TYPE DATABASE_NAME FILE_NAME SCHEMA_FILE_NAME SELECT_INFO_ID DISPLAY_SIZE PHYSICAL_SIZE MIN_PHYSICAL_SIZE Datatype INTEGER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER INTEGER INTEGER INTEGER Description Source ID (primary key). Repository name. Display size (uncompressed). Any flat file imported through the Source Analyzer has an entry. 1 = shortcut. 0 = not a shortcut. Source Views 343 . Type of database extracted from.Table 15-7. You can use FIRST_FIELD_ID to retrieve the fields belonging to a non-relational source by following the links in the REP_SRC_FILE_FLDS view. Table 15-8 lists file information in the REP_SRC_FILES view: Table 15-8. Name of file definitions. Specifies whether nulls are allows. Physical size (compressed binary). 0 = not a shortcut. Length or precision for the field. Folder name. 1 = nulls not allowed. REP_ALL_SOURCE_FLDS MX View Column Name SOURCE_FIELD_KEY_TYPE SOURCE_FIELD_DATATYPE SOURCE_FIELD_PRECISION SOURCE_FIELD_SCALE SOURCE_FIELD_PIC_USAGE_NAME SOURCE_FIELD_NULLTYPE REPOSITORY_NAME IS_SHORTCUT IS_GLOBAL_SHORTCUT Datatype VARCHAR2 (50) VARCHAR2 (40) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER Description Specifies whether the source field key is a primary key or a foreign key. File from which schema was extracted. REP_SRC_FILES This view provides a list of all file definitions in the repository. File organization information. Source field picture usage name. Specifies whether the source is a global shortcut. Field datatype. Name of database extracted from (DSN). Specifies whether the source is a shortcut. 0= nulls allowed.

Source version number. Type of database extracted from. 344 Chapter 15: Using Metadata Exchange (MX) Views . Unique key. Informatica recommends using the fields in bold to join views. Version ID. Folder name. Table 15-9 lists relational database table information in the REP_SRC_TBLS view: Table 15-9.Table 15-8. REP_SRC_TBLS This view provides a list of relational database table sources that have been analyzed through the Source Analyzer tool or imported from a DDL (Data Definition Language) file. Source description. Name of schema extracted from. Source version number. Informatica recommends using the fields in bold to join views. Source description. Business name of the table. Last time the source table was saved. REP_SRC_FILES MX View Column Name FIRST_FIELD_ID SOURCE_DESCRIPTION VERSION_ID SOURCE_VERSION_NUMBER Datatype INTEGER VARCHAR2 (2000) INTEGER NUMBER Description Link to first field of file definitions. Name of database extracted from. Link to first field. Folder ID. Folder version name. REP_SRC_TBLS MX View Column Name TABLE_NAME TABLE_BUSNAME TABLE_ID SUBJECT_AREA DATABASE_TYPE DATABASE_NAME SCHEMA_NAME FIRST_FIELD_ID SOURCE_DESCRIPTION VERSION_ID VERSION_NAME LAST_SAVED SOURCE_VERSION_NUMBER SUBJECT_ID Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2( 240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER Description Table name. Folder version ID.

Folder name. Order number of the field.e. Link to next field at this level. Field name. 0 = not a key. Display length. Key type. Link to child field if this is a group item.. Comments for this field. 1 = primary key. Each field is contained in the scanned tables listed in the REP_SEG_FLDS view. Field level (i.REP_SRC_FILE_FLDS and REP_SEG_FLDS These views provide access to the fields in a non-relational source. COMP type (binary compressed fields). Decimal scale for numeric fields. 02). Decimal precision for numeric fields or field length for CHAR fields. Number of OCCURS. 01. Table 15-10 lists source field information in the REP_SRC_FILE_FLDS and REP_SEG_FLDS views: Table 15-10. Informatica recommends using the fields in bold to join views. Source ID (primary key). PIC clause. REP_SRC_FILE_FLDS and REP_SEG_FLDS MX Views Column Name FIELD_ID SUBJECT_AREA FILE_ID FIELD_NAME FIELD_LEVEL FIELD_NUMBER FIELD_DESCRIPTION PICTURE_TEXT OCCURS REDEFINES_FIELD KEY_TYPE DISPLAY_OFFSET DISPLAY_LENGTH PHYSICAL_OFFSET PHYSICAL_LENGTH USAGE_TYPE DATA_PRECISION DATA_SCALE CHILD_ID SIBLING_ID VERSION_ID Datatype INTEGER VARCHAR2 (240) INTEGER VARCHAR2 (240) INTEGER INTEGER VARCHAR2 (2000) VARCHAR2 (240) INTEGER VARCHAR2 (240) INTEGER INTEGER INTEGER INTEGER INTEGER VARCHAR2 (240) INTEGER INTEGER INTEGER INTEGER INTEGER Description Field ID (primary key). Version ID of the source. Physical offset. Offset using display length. Source Views 345 . Physical length. Redefines this field.

Source table ID. REP_SRC_TBL_FLDS MX Views Column Name COLUMN_NAME COLUMN_BUSNAME COLUMN_ID SUBJECT_AREA TABLE_ID TABLE_NAME TABLE_BUSNAME COLUMN_NUMBER COLUMN_DESCRIPTION KEY_TYPE SOURCE_TYPE DATA_PRECISION DATA_SCALE NEXT_COLUMN_ID VERSION_ID VERSION_NAME SOURCE_VERSION_NUMBER SUBJECT_ID Datatype VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (2000) VARCHAR2 (240) INTEGER INTEGER INTEGER INTEGER INTEGER VARCHAR2 (240) NUMBER NUMBER Description Field name. Decimal precision for numeric fields or field length for CHAR fields. Folder version ID. You can use the source name to retrieve all the fields belonging to the source. Folder ID. Field ID (primary key). Informatica recommends using the fields in bold to join views. 346 Chapter 15: Using Metadata Exchange (MX) Views . Source version number. Table 15-11 lists relational source fields in the REP_SRC_TBL_FLDS view: Table 15-11. Business name of the table. Business name of the field. Order number of the column. Description of the column. Folder name. Key type for this column. Table name. The columns in this view are part of the tables listed in the REP_SRC_TBLS views. Link to next field in source table. Folder version name. Decimal scale for numeric fields.REP_SRC_TBL_FLDS This view provides access to the fields in relational sources. Data type for this column.

Target description. see “REP_ALL_TARGETS” on page 347. Target version number. Business name for the target.Target Views Target views provide a list of the latest version of all target definitions defined by folder of a PowerCenter repository for both relational and non-relational sources. Table 15-13 lists target details in the REP_ALL_TARGETS view: Table 15-13. the names of shortcut and the parent targets display. Table 15-12 lists the different views that help you analyze target metadata: Table 15-12. creation date. see “REP_TARG_TBL_COLS” on page 351. For more information. and business name. column properties. Targets include both relational and non-relational targets such as XML files and flat files. This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. REP_ALL_TARGETS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_TARGET_NAME PARENT_TARGET_BUSINESS_NAME PARENT_TARGET_ID PARENT_TARGET_DESCRIPTION PARENT_TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER Description Parent folder name. Target ID (primary key). REP_TARG_TBLS REP_TARG_TBL_COLS REP_ALL_TARGETS This view provides a list of the latest version of all targets defined in each folder of a repository. This view provides the properties of columns defined for the target tables in a data warehouse or data mart. version. Folder ID. Target Views View REP_ALL_TARGETS REP_ALL_TARGET_FIELDS Description This view provides a list of the latest version of all targets defined in each folder of a repository. For more information. This view provides a list of targets in the repository. Target Views 347 . For local shortcuts. see “REP_TARG_TBLS” on page 350. description. These views also show target properties such as shortcuts. target metadata extensions. FIRST_COLUMN_ID is a link to the set of columns for this table. the name of the shortcut displays. For more information. For more information. see “REP_ALL_TARGET_FIELDS” on page 349. and mappings and mapplets where these target are used. Target name. For global shortcuts. They also provide information such as target columns.

Folder ID. 1 = shortcut. UTC time (Coordinated Universal Time) when the parent target was checked in. Specifies whether the target is a global shortcut. 0 = not a shortcut.Table 15-13. UTC time (Coordinated Universal Time) when the target was last checked in. UTC time when the target was last saved. Target name. Informatica recommends using the fields in bold to join views. Target description. Options for use when generating DDL. REP_ALL_TARGETS MX View Column Name PARENT_TARGET_VERSION_STATUS PARENT_TARGET_UTC_CHECKIN PARENT_TARGET_UTC_LAST_SAVED PARENT_TARGET_CREATION_TIME PARENT_TARGET_FIRST_FIELD_ID PARENT_TARGET_CONSTRAINT PARENT_TARGET_CREATE_OPTIONS PARENT_TARGET_FIRST_INDEX_ID PARENT_TARGET_FILE_ID PARENT_TARGET_DATABASE_TYPE SUBJECT_AREA SUBJECT_ID TARGET_NAME TARGET_ID TARGET_DESCRIPTION TARGET_VERSION_NUMBER TARGET_VERSION_STATUS TARGET_UTC_CHECKIN TARGET_UTC_LAST_SAVED TARGET_CREATION_TIME REPOSITORY_NAME IS_SHORTCUT IS_GLOBAL_SHORTCUT Datatype NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 VARCHAR2 (2000) VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (50) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER Description Status of the parent target version. Repository name. ID for the parent target file. 1 = shortcut. Folder name. Link to first field of this table. Link to first field of this table. User-specified constraint string used when the DDL is generated. Time when the target was last modified. Time when the target was last saved. Target ID. Database type for the parent target. Target version number. 0 = not a shortcut. 348 Chapter 15: Using Metadata Exchange (MX) Views . Specifies whether the target is a shortcut. UTC time when the target was last saved. Status of the target version.

Folder ID. the shortcut name displays. Database type of parent target. Target description. Name of parent target. Status of the parent target version. Status of the target version. the names of the shortcut and the parent targets display. Time when the parent target was last modified. Target version number. Time when target was last modified. UTC time when the target was last checked in. Table 15-14 lists target field data in the REP_ALL_TARGET_FIELDS view: Table 15-14. For global shortcuts. UTC time when the parent target was last saved. Parent target ID. UTC time when the target was last saved. ID of parent target file.REP_ALL_TARGET_FIELDS This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. Folder ID. Description of parent target. Business name of the parent target. UTC time (Coordinated Universal Time) when the parent target was last checked in. For local shortcuts. Target ID. REP_ALL_TARGET_FIELDS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_TARGET_NAME PARENT_TARGET_BUSINESS_NAME PARENT_TARGET_ID PARENT_TARGET_DESCRIPTION PARENT_TARGET_VERSION_NUMBER PARENT_TARGET_VERSION_STATUS PARENT_TARGET_UTC_CHECKIN PARENT_TARGET_UTC_LAST_SAVED PARENT_TARGET_LAST_SAVED PARENT_TARGET_FILE_ID PARENT_TARGET_FIRST_FIELD_ID PARENT_TARGET_DATABASE_TYPE SUBJECT_AREA SUBJECT_ID TARGET_NAME TARGET_ID TARGET_DESCRIPTION TARGET_VERSION_NUMBER TARGET_VERSION_STATUS TARGET_UTC_CHECKIN TARGET_UTC_LAST_SAVED TARGET_CREATION_TIME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (50) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) Description Folder name. Folder name. ID of the first field of parent target. Target name. Target version number. Target Views 349 .

Target field number. REP_TARG_TBLS This view provides a list of targets in the repository. FIRST_COLUMN_ID is a link to the set of columns for this table. Text. Scale for target field. It is the primary table list used to delineate a PowerCenter data model. 1 = shortcut. Specifies whether the target is a shortcut. Money. 0 = not a shortcut. REP_ALL_TARGET_FIELDS MX View Column Name TARGET_FIELD_NAME TARGET_FIELD_BUSINESS_NAME TARGET_FIELD_ID TARGET_FIELD_DESC TARGET_FIELD_NUMBER TARGET_FIELD_NEXT_FIELD_ID TARGET_FIELD_PICTURE_TEXT TARGET_FIELD_IS_NULLABLE TARGET_FIELD_SOURCE_FIELD_ID TARGET_FIELD_KEY_TYPE TARGET_FIELD_DATATYPE TARGET_FIELD_DATATYPE_GROUP Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) CHAR (1) Description Target field name.Table 15-14. The tables are virtual. verify that the table exists before using this view. 1 = shortcut. Key type of target field. 0 = not a shortcut. Specifies whether the target is a global shortcut. Target field ID. not physically created. TARGET_FIELD_PRECISION TARGET_FIELD_SCALE REPOSITORY_NAME IS_SHORTCUT IS_GLOBAL_SHORTCUT NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER Informatica recommends using the fields in bold to join views. 0 = Null. Therefore. Datatype group codes. ID of the next field in target. Link to source from which this field was created. and Byte D = Date N = Numeric. String. Datatype of target field. Business name of target field. Specifies whether target field is null. B = Binary and Bit C = Character. 1 = Not Null. and Bigint Precision for target field. Picture text that COBOL sources use. All tables contained in the target table model are part of this view. Description of target field. Repository name. 350 Chapter 15: Using Metadata Exchange (MX) Views .

Business name of the table. Order number of the column. Table name. Link to first field of this table. Folder version ID. Business name of this column. Folder version name. Table business name. Target Views 351 . Table ID. Table 15-16 lists target table column properties for the REP_TARG_TBL_COLS view: Table 15-16. REP_TARG_TBL_COLS This view provides the properties of columns defined for the target tables in a data warehouse or data mart. Link to first index. Informatica recommends using the fields in bold to join views. Table this column belongs to. REP_TARG_TBLS MX View Column Name SUBJECT_AREA TABLE_NAME BUSNAME VERSION_ID VERSION_NAME DESCRIPTION FIRST_COLUMN_ID TABLE_CONSTRAINT CREATE_OPTIONS FIRST_INDEX_ID LAST_SAVED TARGET_VERSION_NUMBER SUBJECT_ID TABLE_ID Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (2000) INTEGER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER Description Folder name. Column name. Time target table was last saved. Folder ID. REP_TARG_TBL_COLS MX View Column Name SUBJECT_AREA TABLE_NAME TABLE_BUSNAME COLUMN_NAME COLUMN_BUSNAME COLUMN_NUMBER COLUMN_ID Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER INTEGER Description Folder name.Table 15-15 lists the columns in the REP_TARG_TBLS view: Table 15-15. Table creation options specified in the Warehouse Designer. Table constraint specified in Warehouse Designer. Target version number. Description of the table. Column ID (primary key).

Decimal scale for numeric columns. Not a Key. Column description. Foreign Key. Primary and Foreign Key. Native database datatype. Whether NULLs are accepted. REP_TARG_TBL_COLS MX View Column Name VERSION_ID VERSION_NAME DESCRIPTION COLUMN_KEYTYPE DATA_TYPE DATA_TYPE_GROUP Datatype INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) VARCHAR2 (240) CHAR (1) Description Folder version ID.Table 15-16. Link to source this column was created from. Folder version name. Datatype group. 352 Chapter 15: Using Metadata Exchange (MX) Views . Link to next column. Primary Key. Target version number. C = Character D = Date N = Numeric Decimal precision for numeric fields or field length for CHAR fields. DATA_PRECISION DATA_SCALE NEXT_COLUMN_ID IS_NULLABLE SOURCE_COLUMN_ID TARGET_VERSION_NUMBER INTEGER INTEGER INTEGER INTEGER INTEGER NUMBER Informatica recommends using the fields in bold to join views.

For more information. and transformations used in a mapping or a mapplet by folder in a PowerCenter repository. For more information. This view shows all sources used in a mapping. Mapping and Mapplet Views View REP_ALL_MAPPINGS Description This view provides a list of the latest version of all mappings defined in each folder of a repository. see “REP_SRC_FLD_MAP” on page 359. For more information. see “REP_ALL_MAPPLETS” on page 355.Mapping and Mapplet Views Mapping and mapplet views allow you to see the sources. targets. For more information. see “REP_TBL_MAPPING” on page 360. This view shows the source fields used by the target fields in a mapping. This view contains join information between target tables. see “REP_MAPPING_PORT_CONN” on page 363. see “REP_TARG_TBL_JOINS” on page 361. the validity of the mapping or mapplet. see “REP_MAPPING_UNCONN_PORTS” on page 362. For more information. see “REP_TARG_FLD_MAP” on page 357. and whether the mapping or the mapplet is a shortcut. This view shows compound field-level transformation expressions associated with a target. version and creation date. Table 15-17 lists the different views that help you analyze mapping and mapplet metadata: Table 15-17. This view shows all of the source fields used in a mapping. see “REP_FLD_MAPPING” on page 358. This view displays the port-level connections between the objects of a mapping. For more information. This view provides access to the compound table-level transformation expressions for each target table. and transformations in a mapping. For more information. For more information. For more information. For more information. REP_ALL_MAPPLETS REP_TARG_MAPPING REP_TARG_FLD_MAP REP_FLD_MAPPING REP_SRC_MAPPING REP_SRC_FLD_MAP REP_TBL_MAPPING REP_TARG_TBL_JOINS REP_MAPPING_UNCONN_PORTS REP_MAPPING_PORT_CONN Mapping and Mapplet Views 353 . This view shows all of the target tables used in a mapping and provides source to target mapping information. This is the companion view for the REP_TBL_MAPPING view. This view displays the unconnected ports in sources. For more information. see “REP_TARG_MAPPING” on page 356. targets. see “REP_SRC_MAPPING” on page 359. see “REP_ALL_MAPPINGS” on page 354. These views also display properties of mappings and mapplets such as description. This view provides a list of the latest version of all mapplets defined in each folder of a repository.

The UTC time when mapping was last saved. For global shortcuts. Parent folder ID. 1 = shortcut. Parent mapping description. UTC time when the mapping was last saved. Name of the parent mapping. the name of the shortcut displays. the names of the shortcut and the parent mappings display. REP_ALL_MAPPINGS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID SUBJECT_AREA SUBJECT_ID PARENT_MAPPING_NAME PARENT_MAPPING_ID PARENT_MAPPING_VERSION_NUMBER PARENT_MAPPING_VERSION_STATUS PARENT_MAPPING_UTC_CHECKIN PARENT_MAPPING_UTC_LAST_SAVED PARENT_MAPPING_LAST_SAVED PARENT_MAPPING_IS_VALID PARENT_MAPPING_DESCRIPTION MAPPING_NAME MAPPING_ID MAPPING_VERSION_NUMBER MAPPING_VERSION_STATUS MAPPING_UTC_CHECKIN MAPPING_UTC_LAST_SAVED MAPPING_LAST_SAVED MAPPING_DESCRIPTION REPOSITORY_NAME IS_GLOBAL_SHORTCUT Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER INTEGER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER Description Parent folder name. Parent mapping version number. Sequence ID for mapping. Specifies whether the mapping is a global shortcut. Table 15-18 lists mapping information in the REP_ALL_MAPPINGS view: Table 15-18. Repository name.REP_ALL_MAPPINGS This view provides a list of the latest version of all mappings defined in each folder of a repository. Status of the mapping version. UTC time (Coordinated Universal Time) when the parent mapping was checked in. Folder name. For local shortcuts. 0 = not a shortcut. Mapping description. Date and time when parent mapping was last saved. Folder ID. UTC time when the mapping was checked in. Mapping version number. Specifies whether the parent mapping is valid. Time when the mapping was last saved. Parent mapping version status. Name of mapping. 354 Chapter 15: Using Metadata Exchange (MX) Views . Sequence ID of the parent mapping.

Specifies whether the parent mapplet is valid. Parent mapplet description. Folder ID. Time when the mapplet was last saved. REP_ALL_MAPPINGS MX View Column Name IS_SHORTCUT Datatype NUMBER Description Specifies whether the mapping is a shortcut. Status of the mapplet version. Table 15-19 lists mapplet metadata in the REP_ALL_MAPPLETS view: Table 15-19. Mapplet version number. UTC time when the mapplet was last saved. For local shortcuts. Field ID (primary key). UTC time (Coordinated Universal Time) when the parent mapplet was checked in. Parent mapplet version status. The date and time when parent mapplet was last saved. Mapplet ID. REP_ALL_MAPPLETS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID SUBJECT_AREA SUBJECT_ID PARENT_MAPPLET_NAME PARENT_MAPPLET_ID PARENT_MAPPLET_VERSION_NUMBER PARENT_MAPPLET_VERSION_STATUS PARENT_MAPPLET_UTC_CHECKIN PARENT_MAPPLET_UTC_LAST_SAVED PARENT_MAPPLET_LAST_SAVED PARENT_MAPPLET_IS_VALID PARENT_MAPPLET_DESCRIPTION MAPPLET_NAME MAPPLET_ID MAPPLET_VERSION_NUMBER MAPPLET_VERSION_STATUS MAPPLET_UTC_CHECKIN MAPPLET_UTC_LAST_SAVED MAPPLET_LAST_SAVED Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER INTEGER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER Description Parent folder name. the names of the shortcut and the parent mapplets display. Folder name. Parent folder ID. Mapping and Mapplet Views 355 . 1 = shortcut. Sequence ID of parent mapplet. the name of the shortcut displays. Name of mapplet. Name of parent mapplet. For global shortcuts. 0 = not a shortcut. The UTC time when mapplet was last saved.Table 15-18. REP_ALL_MAPPLETS This view provides a list of the latest version of all mapplets defined in each folder of a repository. UTC time when the mapplet was checked in. Informatica recommends using the fields in bold to join views.

Compound SQL override expression. Folder version ID. 356 Chapter 15: Using Metadata Exchange (MX) Views . Folder name. This view contains information about mappings defined for target tables only. 1 = shortcut. Compound group by expression. 0 = not a shortcut. Folder version name. REP_TARG_MAPPING This view provides access to the compound table-level transformation expressions for each target table. 0 = not a shortcut. Foreign key that points to generated mapplet transformation. Note: Use the REP_TBL_MAPPING view to analyze source and target relationships. Specifies whether the mapplet is a global shortcut. It does not contain information about sources. This view pulls information from all the transformation objects that contribute to the target table in a valid mapping. Mapping name. Compound conditional load. Join REP_TBL_MAPPING and REP_TARG_MAPPING by MAPPING_NAME to include column-level mapping information in the REP_FLD_MAPPING view. 1 = shortcut. Repository name. IS_SHORTCUT NUMBER Informatica recommends using the fields in bold to join views. REP_ALL_MAPPLETS MX View Column Name MAPPLET_DESCRIPTION REF_WIDGET_ID REPOSITORY_NAME IS_GLOBAL_SHORTCUT Datatype VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER Description Mapplet description. Description of mapping. Table 15-20 lists expression information in the REP_TARG_MAPPING view: Table 15-20. Description of transformation expression. Specifies whether the mapplet is a shortcut.Table 15-19. Compound source filter condition. REP_TARG_MAPPING MX View Column Name TARGET_NAME TARG_BUSNAME SUBJECT_AREA MAPPING_NAME VERSION_ID VERSION_NAME SOURCE_FILTER CONDITIONAL_LOAD GROUP_BY_CLAUSE SQL_OVERRIDE DESCRIPTION MAPPING_COMMENT Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) Description Target name. Target business name.

Table 15-21 lists expression metadata that you find in the REP_TARG_FLD_MAP view: Table 15-21. This view pulls information from all transformation objects that contribute to the target table in a valid mapping. each distinguished by the MAPPING_NAME field. Administrator comment. Business name of target table. Folder version ID. Informatica recommends using the fields in bold to join views. Time the mapping was saved last. The field-level expression contains all the source fields (both file definition/non-relational source) that make up the value of the target field. Target version number. Compound transformation expression. Name of target (table). Folder name. REP_TARG_FLD_MAP MX View Column Name TARGET_COLUMN_NAME TARG_COL_BUSNAME TARGET_NAME TARG_BUSINESS_NAME SUBJECT_AREA MAPPING_NAME VERSION_ID VERSION_NAME TRANS_EXPRESSION USER_COMMENT DBA_COMMENT MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER Description Name of target field (table field). End user comment. Mapping comment. Mapping name. Target version number. Folder version name. Mapping and Mapplet Views 357 . Mapping version number. REP_TARG_MAPPING MX View Column Name MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER NUMBER Description Time the mapping was saved last. Business name of target field. REP_TARG_FLD_MAP This view shows compound field-level transformation expressions associated with a target. Informatica recommends using the fields in bold to join views. Mapping version number.Table 15-20. see the Transformation Language Reference. For details on the syntax of the transformation expression. There might be many mappings for a set of fields.

This is the companion view for the REP_TBL_MAPPING view. Target field transformation expression. Folder name. End user comment.REP_FLD_MAPPING This view shows the source fields used by the target fields in a mapping. Folder version name. Target version number. Folder version ID. Name of the target field. It contains both source and target column names and details. Administrator comment. Mapping comment. Informatica recommends using the fields in bold to join views. Mapping ID. 358 Chapter 15: Using Metadata Exchange (MX) Views . Time the mapping was saved last. Business name of the source field. REP_FLD_MAPPING MX View Column Name SOURCE_FIELD_NAME SRC_FLD_BUSNAME SOURCE_NAME SRC_BUSNAME TARGET_COLUMN_NAME TARG_COL_BUSNAME TARGET_NAME TARG_BUSNAME SUBJECT_AREA SUBJECT_ID MAPPING_NAME VERSION_ID VERSION_NAME TRANS_EXPRESSION USER_COMMENT DBA_COMMENT MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER SOURCE_VERSION_NUMBER TARGET_VERSION_NUMBER SOURCE_ID TARGET_ID MAPPING_ID Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER Descriptions Name of the source field. Name of the source table. Target name. Target table ID. Business name of the target. Table 15-22 lists the source and target field metadata in the REP_FLD_MAPPING view: Table 15-22. Folder ID. Name of the mapping. Source version number. Business name of the source table. Source table ID. Mapping version number. Business name of the target column.

Mapping and Mapplet Views 359 . Source version number. Business name of source table. This view creates these expressions by pulling information from all transformation objects that contribute to the target table in a valid mapping. This view contains the mapping names defined for an individual source table. Business name of the field. Mapping ID. Source ID. Query this view by MAPPING_NAME and VERSION_NAME. Mapping version number. Folder ID. Mapping comment. Folder name. Time the mapping was last saved.REP_SRC_MAPPING This view shows all sources used in a mapping. Folder version name. Table 15-24 lists mapping source fields: Table 15-24. Table 15-23 lists mapping source metadata in the REP_SRC_MAPPING view: Table 15-23. Folder version ID. Mapping name. REP_SRC_FLD_MAP This view shows all of the source fields used in a mapping. The REP_TBL_MAPPING view contains the entire source and target mapping relationship. Mapping Source Fields Column Name SOURCE_FIELD_NAME SRC_FLD_BUSNAME Datatype VARCHAR2 (240) VARCHAR2 (240) Description Source field name. REP_SRC_MAPPING MX View Column Name SOURCE_NAME SOURCE_ID SRC_BUSNAME SUBJECT_AREA SUBJECT_ID MAPPING_NAME MAPPING_ID VERSION_ID VERSION_NAME MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER SOURCE_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER Description Name of the source. It does not contain information about the targets involved in a mapping. A mapping might contain several sources. Informatica recommends using the fields in bold to join views. The transformation expression corresponds to the target fields that get data from a particular source field.

Administrator comment. Informatica recommends using the fields in bold to join views. Target name. Target version number. 360 Chapter 15: Using Metadata Exchange (MX) Views . Target ID. Folder version ID. End user comment. Folder name. Business name of the source table. Name of the mapping. This view pulls information from all transformation objects that contribute to the target table in a valid mapping to provide the table-level expressions. Compound target. Time the mapping was saved last. Folder name. Folder ID. Source version number. Table 15-25 lists mapping target metadata in the REP_TBL_MAPPING view: Table 15-25. Folder version name. Field transformation expression. Mapping comment. Business name of the source.Table 15-24. Business name of the target. Mapping Source Fields Column Name SOURCE_NAME SRC_BUSNAME SUBJECT_AREA MAPPING_NAME VERSION_ID VERSION_NAME TRANS_EXPRESSION USER_COMMENT DBA_COMMENT MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER SOURCE_VERSION_NUMBER TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER Description Name of the source. REP_TBL_MAPPING MX View Column Name SOURCE_NAME SOURCE_ID SRC_BUSNAME TARGET_NAME TARGET_ID TARG_BUSNAME SUBJECT_AREA SUBJECT_ID Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER Description Name of the source object. Source ID. REP_TBL_MAPPING This view shows all of the target tables used in a mapping and provides source to target mapping information. Mapping version number.

ID of first table in the join. Source version number. Name of column in first table. Mapping and Mapplet Views 361 . Name of first table in the join. Folder version name. Compound group by clause. Mapping comment. Folder version ID. Time the mapping was saved last. Table 15-26 lists target table join metadata in the REP_TARG_TBL_JOINS view: Table 15-26. Business name of column in first table. Description of transformation. It is populated when you link fields in the Warehouse Designer. Compound conditional load. REP_TARG_TBL_JOINS MX View Column Name SUBJECT_AREA VERSION_ID VERSION_NAME TABLE1_NAME TABLE1_BUSNAME TABLE1_ID COLUMN1_NAME COLUMN1_BUSNAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) Description Folder name. Use this view to query the PowerCenter defined joins for a target table model. Compound SQL override expression. Business name of first table. Mapping ID. Informatica recommends using the fields in bold to join views. Folder version name. REP_TARG_TBL_JOINS This view contains join information between target tables. Folder version ID. or through primary key-foreign key relationships. Compound source filter condition. Target version number.Table 15-25. Mapping version number. REP_TBL_MAPPING MX View Column Name MAPPING_NAME MAPPING_ID VERSION_ID VERSION_NAME SOURCE_FILTER CONDITIONAL_LOAD GROUP_BY_CLAUSE SQL_OVERRIDE DESCRIPTION MAPPING_COMMENT MAPPING_LAST_SAVED MAPPING_VERSION_NUMBER SOURCE_VERSION_NUMBER TARGET_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER INTEGER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER Description Name of the mapping.

REP_MAPPING_UNCONN_PORTS This view displays the unconnected ports in sources. Informatica recommends using the fields in bold to join views. Folder ID (primary key). REP_MAPPING_UNCONN_PORTS MX View Column Name SUBJECT_AREA SUBJECT_ID MAPPING_NAME MAPPING_ID MAPPING_VERSION_NUMBER OBJECT_INSTANCE_NAME OBJECT_INSTANCE_ID OBJECT_TYPE OBJECT_TYPE_NAME FIELD_ID FIELD_NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) Description Folder name. and transformations in a mapping. Number of column in second table. Table2 version number. Name of the mapping. Business name of column in second table. Sequence ID for the mapping (primary key). Source field ID (primary key). ID of column in first table. Table 15-27 lists unconnected port metadata in the REP_MAPPING_UNCONN_PORTS view: Table 15-27. Unique ID for the instance in a mapping. ID of column in second table. REP_TARG_TBL_JOINS MX View Column Name COLUMN1_NUMBER COLUMN1_ID TABLE2_NAME TABLE2_BUSNAME TABLE2_ID COLUMN2_NAME COLUMN2_BUSNAME COLUMN2_NUMBER COLUMN2_ID TABLE1_VERSION_NUMBER TABLE2_VERSION_NUMBER Datatype NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER Description Number of column in first table. Object type. Object type name. Name of column in second table.Table 15-26. Source field name. ID of second table in the join. Name of the instance. Name of second table in the join. 362 Chapter 15: Using Metadata Exchange (MX) Views . targets. Business name of second table. Table1 version number. Mapping version number.

targets. Source object field name. Folder name. Unconnected transformations are not included. Mapping and Mapplet Views 363 . Target object type name. mapplet. Source object instance ID. target. REP_MAPPING_UNCONN_PORTS MX View Column Name OBJECT_VERSION_NUMBER Datatype NUMBER Description Version number of the source. Mapping name. Informatica recommends using the fields in bold to join views. Target object ID.Table 15-27. Target object name. Table 15-28 lists port-level connection metadata in the REP_MAPPING_PORT_CONN view: Table 15-28. Source object ID. or transformation. transformations. Target object field name. Source object version number. Sequence ID for the mapping (primary key). Source object name. Source object type. and mapplets. Informatica recommends using the fields in bold to join views. Target object instance ID. Target object version number. REP_MAPPING_PORT_CONN This view displays the port-level connections between the objects of a mapping. Mapping version number. REP_MAPPING_PORT_CONN MX View Column Name SUBJECT_ID SUBJECT_AREA MAPPING_ID MAPPING_NAME MAPPING_VERSION_NUMBER FROM_OBJECT_ID FROM_OBJECT_TYPE FROM_OBJECT_TYPE_NAME FROM_OBJECT_NAME FROM_OBJECT_INSTANCE_ID FROM_OBJECT_FIELD_NAME FROM_OBJECT_VERSION_NUMBER TO_OBJECT_ID TO_OBJECT_TYPE TO_OBJECT_TYPE_NAME TO_OBJECT_NAME TO_OBJECT_INSTANCE_ID TO_OBJECT_FIELD_NAME TO_OBJECT_VERSION_NUMBER Datatype NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER Description Folder ID. Objects include sources. Name of the source object type. and transformation. target. Target object type such as port.

Object type the metadata is associated with. Metadata Extension Views View REP_METADATA_EXTNS REP_METADATA_EXTN_DEFINES Description This view displays the details of all metadata extensions in the repository. Description of the metadata extension. Unique name for a user-defined metadata domain. This view displays reusable metadata extensions defined for objects in metadata extension domains. Table 15-29 lists the different views that help you analyze metadata extensions metadata: Table 15-29. Object version number. REP_METADATA_EXTNS This view displays the details of all metadata extensions in the repository. Metadata extension name. Folder ID. see “REP_METADATA_EXTNS” on page 364. 364 Chapter 15: Using Metadata Exchange (MX) Views . Table 15-30 lists metadata extension information in the REP_METADATA_EXTNS view: Table 15-30.Metadata Extension Views Metadata views allow you to see metadata extension details including reusable metadata extensions defined for objects in metadata extension domains. Permissions type. Globally unique domain identifier. Metadata extension value. REP_METADATA_EXTNS MX View Column Name OBJECT_ID SUBJECT_ID METADATA_EXTN_NAME METADATA_EXTN_OBJECT_TYPE METADATA_EXTN_OBJECT_ID METADATA_EXTN_DATA_TYPE PERMISSIONS METADATA_EXTN_VALUE LINE_NO METADATA_EXTN_DESCRIPTION VERSION_NUMBER OBJECT_TYPE_NAME DOMAIN_ID DOMAIN_NAME Datatype NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER VARCHAR2 (240) Description Object the metadata is associated with. see “REP_METADATA_EXTN_DEFINES” on page 365. Object the metadata value is associated with. For more information. Name of the object type. For more information. Datatype of the metadata extension value. Line number of the text when there are multiple lines of text.

Name of the vendor. REP_METADATA_EXTN_DEFINES MX View Column Name DOMAIN_NAME DOMAIN_ID METAEXT_NAME OBJECT_TYPE_NAME DATABASE_TYPE METAEXT_DESC VENDOR_NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) Description Unique name for a user-defined domain Globally unique domain identifier. Description of the metadata extension. REP_METADATA_EXTNS MX View Column Name DOMAIN_KEY DOMAIN_USAGE Datatype VARCHAR2 (240) NUMBER Description Domain password. Unique name for metadata within a domain. Object type name. Name of the database type. Metadata Extension Views 365 . Domain description. Table 15-31 lists information in the REP_METADATA_EXTN_DEFINES view: Table 15-31. DOMAIN_DESCRIPTION VARCHAR2 (2000) Informatica recommends using the fields in bold to join views. Informatica recommends using the fields in bold to join views. 2= Domain is editable through client tool.Table 15-30. 1= Domain is visible through client tool. 4 = Domain has full access without a key. REP_METADATA_EXTN_DEFINES This view displays reusable metadata extensions defined for objects in metadata extension domains. Specifies domain usage.

Folder ID. REP_WIDGET_INST REP_WIDGET_DEP REP_WIDGET_ATTR REP_WIDGET_FIELD REP_ALL_TRANSFORMS This view provides a list of the latest version of all transformations and their properties in each folder of a repository. Table 15-32 lists the different views that help you analyze transformation metadata: Table 15-32. Table 15-33 lists transformation metadata in the REP_ALL_TRANFORMS view: Table 15-33. For more information. This view displays field level details for transformations. This view displays attribute details for transformations. For more information. see “REP_WIDGET_DEP” on page 368. Name of the parent transformation. the names of the shortcut and the parent transformation display. REP_ALL_TRANSFORMS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID SUBJECT_AREA SUBJECT_ID PARENT_WIDGET_NAME PARENT_WIDGET_ID Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER Description Parent folder name. the name of the shortcut displays. Parent folder ID. and field level details of transformations. For more information. instances. This view displays the details of dependencies between transformation instances in a mapping. For local shortcuts. see “REP_WIDGET_INST” on page 368. These views also display properties such as attributes. This view displays both reusable transformations defined in the Transformation Designer and transformation instances defined in mapping and mapplets. Folder name. It also shows all shortcut transformations in a folder. port-level connections. see “REP_WIDGET_FIELD” on page 369. see “REP_WIDGET_ATTR” on page 369. Parent transformation ID (primary key). For global shortcuts. For more information. and sessions. 366 Chapter 15: Using Metadata Exchange (MX) Views . see “REP_ALL_TRANSFORMS” on page 366. This view displays the details of all transformation instances. For more information. Transformation Views View REP_ALL_TRANSFORMS Description This view provides a list of the latest version of all transformations and their properties in each folder of a repository.Transformation Views Transformation views display details of all reusable and non-reusable transformation instances by folder in a PowerCenter repository. dependencies.

Time when the transformation was last saved. 0 = not a shortcut. Transformation Views 367 .Table 15-33. UTC time when the parent transformation was last saved. 1 = shortcut. Specifies whether the transformation is a shortcut. Transformation type name. 1 = shortcut. Parent transformation description. Name of the transformation. IS_SHORTCUT NUMBER Informatica recommends using the fields in bold to join views. Transformation type ID. UTC time (Coordinated Universal Time) when the parent transformation was last checked in. Transformation ID. UTC time when the transformation was checked in. Status of the transformation version. Date and time when transformation was last saved. UTC time when the transformation was last saved. Version number of the transformation. Specifies whether the transformation is a global shortcut. 0 = not reusable. Status of the parent transformation version. Repository name. 1= reusable. Transformation description. REP_ALL_TRANSFORMS MX View Column Name PARENT_WIDGET_VERSION_NUMBER PARENT_WIDGET_VERSION_STATUS PARENT_WIDGET_UTC_CHECKIN PARENT_WIDGET_UTC_LAST_SAVED PARENT_WIDGET_LAST_SAVED PARENT_WIDGET_IS_REUSABLE PARENT_WIDGET_DESCRIPTION WIDGET_NAME WIDGET_ID WIDGET_VERSION_NUMBER WIDGET_VERSION_STATUS WIDGET_UTC_CHECKIN WIDGET_UTC_LAST_SAVED WIDGET_LAST_SAVED WIDGET_TYPE_ID WIDGET_TYPE_NAME WIDGET_DESCRIPTION REPOSITORY_NAME IS_GLOBAL_SHORTCUT Datatype NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) NUMBER VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER Description Parent transformation ID. 0 = not a shortcut. Specifies whether the transformation is reusable.

Transformation type. REP_WIDGET_DEP This view displays the details of dependencies between transformation instances in a mapping. Table 15-35 lists transformation dependency information in the REP_WIDGET_DEP view: Table 15-35. REP_WIDGET_DEP MX View Column Name MAPPING_ID FROM_INSTANCE_ID FROM_FIELD_ID TO_INSTANCE_ID TO_FIELD_ID INSTANCE_NAME COMMENTS VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER Description Mapping ID Source transformation instance ID.REP_WIDGET_INST This view displays the details of all transformation instances. Version number of the mapping. Description of the transformation instance. Field ID of the target transformation instance. 368 Chapter 15: Using Metadata Exchange (MX) Views . Field ID of the source transformation instance. REP_WIDGET_INST MX View Column Name MAPPING_ID WIDGET_ID SUBJECT_ID WIDGET_TYPE WIDGET_TYPE_NAME INSTANCE_ID INSTANCE_NAME COMMENTS VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER Description Mapping ID Transformation ID Folder ID. Version number of the transformation. Name of the transformation instance. Informatica recommends using the fields in bold to join views. ID of the transformation instance. Description of the transformation instance. Informatica recommends using the fields in bold to join views. Target field ID. Table 15-34 list transformation metadata in the REP_WIDGET_INST view: Table 15-34. Name of the transformation instance. Transformation name.

REP_WIDGET_ATTR This view displays attribute details for transformations. Partition ID. Mapping ID. Session task ID. Informatica recommends using the fields in bold to join views. or transformation) version number. Attribute type. Table 15-36. Table 15-36 lists attribute details for transformations. REP_WIDGET_FIELD MX View Column Name WIDGET_ID FIELD_NAME FIELD_ID WGT_PREC Datatype NUMBER VARCHAR2 (240) NUMBER NUMBER Description Transformation ID. instances. Transformation field name. REP_EIDGET_ATTR MX View Column Name WIDGET_ID WIDGET_TYPE MAPPING_ID INSTANCE_ID ATTR_ID ATTR_COMMENT ATTR_DATATYPE ATTR_NAME ATTR_TYPE OBJECT_TYPE_ID LINE_NO ATTR_VALUE PARTITION_ID SESSION_TASK_ID VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER Description Transformation ID. Transformation field ID. and sessions. Attribute ID. Attribute data type Attribute name. Used to break up long strings into multiple rows. Object (session. Transformation type. Transformation Views 369 . REP_WIDGET_FIELD This view displays field level details for transformations. Transformation field precision. Object type ID. Description of the attribute. and sessions. Instance ID. mapping. Attribute value. instances. Table 15-37 lists transformation field information in the REP_WIDGET_FIELD view: Table 15-37.

Expression type. Informatica recommends using the fields in bold to join views. External database type. Transformation order. Transformation port type. REP_WIDGET_FIELD MX View Column Name WGT_SCALE WGT_DATATYPE PORTTYPE FIELD_ORDER COMMENTS WIDGET_FLD_PROP DEFAULT_VALUE SRC_FIELD_ID GROUP_ID VERSION_NUMBER DATATYPE_NUM DATATYPE DATATYPE_GROUP_CODE DATABASE_TYPE EXPRESSION EXPR_COMMENT EXPR_TYPE Datatype NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (40) CHAR (1) NUMBER VARCHAR2 (2000) VARCHAR2 (2000) NUMBER Description Transformation field scale. 370 Chapter 15: Using Metadata Exchange (MX) Views . Transformation datatype of the port. Comments on the field. Field-level property used by transformations. Comments on the expression.Table 15-37. Transformation version number. Datatype group code. Source field ID for normalizer transformation. Default value of the transformation field. Transformation field data type. Datatype number. Expression name. The ID of the corresponding instance in the mapplet's mapping.

This view contains information about connections associated with reusable sessions. and the PowerCenter Server on which a workflow or worklet runs and its run status. Workflow. Worklet. see “REP_TASK_INST_RUN” on page 378. see “REP_WFLOW_VAR” on page 375. For more information. creation date. end time. This view displays all task instances within workflows and worklets. see “REP_LOAD_SESSIONS” on page 380. For more information. see “REP_WORKFLOW_DEP” on page 377. This view provides information about reusable sessions in the repository. For more information. see “REP_ALL_TASKS” on page 374. see “REP_WORKFLOWS” on page 372. end time. and task metadata: Table 15-38. and task views provide both static and run time details about all workflows and worklets created in each folder in a PowerCenter repository. schedules. and run status. sources and targets defined in a session. This view displays the run statistics and folder reference for tasks within a workflow or worklet. For more information. see “REP_WFLOW_RUN” on page 379. and metadata extensions associated with a workflow or a worklet. This view shows how individual tasks and worklets are connected within a worklet or a workflow. see “REP_EVENT” on page 376. For more information. This view displays a list of schedulers by folder. This view displays the details of events created at the workflow or worklet level. For more information. see “REP_TASK_INST” on page 377. worklet. Table 15-38 lists the different views that help you analyze workflow. and metadata extensions associated with a sessions. These views provide information on worklets and sessions inside a workflow. This view displays the run statistics for all workflows by folder. see “REP_SESSION_CNXS” on page 381.Workflow. see “REP_ALL_SCHEDULERS” on page 374. workflow and worklet execution details such as start time. For more information. The views also provide information on events. For more information. Workflow. For more information. Task views provide both static and run time details about tasks such as sessions created in each folder of a PowerCenter repository. and Task Views 371 . Worklet. and Task Views Workflow. This view displays a list of all variables declared within a workflow or worklet. tasks. These views also give information on session runtime details like start time. and Task Views View REP_WORKFLOWS REP_ALL_TASKS REP_ALL_SCHEDULERS REP_WFLOW_VAR REP_EVENT REP_TASK_INST REP_WORKFLOW_DEP REP_TASK_INST_RUN REP_WFLOW_RUN REP_LOAD_SESSIONS REP_SESSION_CNXS Description This view contains information about individual workflows and workflow scheduling. session connections. For more information. For more information. These views provide information such as the validity of a session. Worklet. connections. This view provides a list of all reusable and non-reusable tasks that can be used by a workflow or a worklet. worklet.

see “REP_SESSION_FILES” on page 382. For more information. This view contains file connections associated with reusable sessions. This view contains information about the sources and targets used in a session. For more information. and Task Views View REP_SESSION_INSTANCES REP_SESSION_FILES REP_SESSION_INSTANCE_F ILES REP_SESS_WIDGET_CNXS REP_COMPONENT REP_SESS_PARTITION_DEF REP_SESS_CONFIG_PARM Description This view contains connection information for session instances. see “REP_COMPONENT” on page 384. see “REP_SESS_WIDGET_CNXS” on page 383. Worklet. Scheduler associated with the workflow. 372 Chapter 15: Using Metadata Exchange (MX) Views . targets. For more information. REP_TASK_ATTR REP_SESS_LOG REP_SESS_TBL_LOG REP_WORKFLOWS This view contains information about individual workflows and workflow scheduling. REP_WORKFLOWS MX View Column Name SUBJECT_AREA WORKFLOW_NAME SCHEDULER_NAME START_TIME END_TIME IS_RUN_ON_LIMIT Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) TIMESTAMP TIMESTAMP NUMBER Description Folder name. For more information. This view contains file connections associated with reusable sessions. Start time configured for the scheduler. For more information. This view displays session configuration parameter details. Table 15-39 lists workflow and scheduling information in the REP_WORKFLOWS view: Table 15-39. For more information. see “REP_SESS_TBL_LOG” on page 388. see “REP_SESS_LOG” on page 387. see “REP_SESS_PARTITION_DEF” on page 385. see “REP_TASK_ATTR” on page 386 This view provides log information about sessions. For more information. Workflow name. For more information. see “REP_SESS_CONFIG_PARM” on page 385.Table 15-38. see “REP_SESSION_INSTANCES” on page 381. This view displays the list of tasks such as a command or an email for each session. If the session overrides a parameter in the configured object. This view displays the attribute values and overridden values for session and workflow tasks. This view provides partition details of the sources. For more information. End time configured for the scheduler. For more information. see “REP_SESSION_INSTANCE_FILES” on page 383. This view contains information about the status of an individual session run against a target. Workflow. and transformations in a session. the view displays two rows.

END_OPTIONS INTEGER RUN_COUNT WORKFLOW_VERSION_NUMBER SCHEDULER_VERSION_NUMBER SUBJECT_ID WORKFLOW_ID WORKFLOW_IS_VALID WORKFLOW_LAST_SAVED WORKFLOW_COMMENTS SCHEDULER_ID SCHEDULER_IS_REUSABLE SCHEDULER_COMMENTS DELTA_VALUE SERVER_NAME SERVER_ID INTEGER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER Informatica recommends using the fields in bold to join views. Workflow. Date and time when the workflow was last saved. Number of seconds the PowerCenter Server waits between successive workflow runs. 1 = End after the number of runs stored in RUN_COUNT. 4 = Run every DELTA_VALUE seconds. Folder ID. Workflow version number. Version number of the scheduler. and Task Views 373 . Specifies if scheduler is reusable. Number of times the PowerCenter Server runs the workflow before stopping the workflow. 2 = Run forever. Records the following values for each schedule type: 1 = Run on demand. Specifies whether the workflow is valid or not. Workflow ID. Description of the workflow. Name of the PowerCenter server registered with the repository. 2 = Run once. REP_WORKFLOWS MX View Column Name RUN_OPTIONS Datatype INTEGER Description The workflow schedule type. 0 = invalid. Records the following values for each stop condition option: 0 = End on a date. PowerCenter Server ID. Worklet. Scheduler ID. Scheduler description. 1 = valid. 32 = Run continuously. 16 = Run on server initialization. The stop condition option for the workflow schedule type. 8 = Customized repeat.Table 15-39.

Specifies whether a workflow. 0 = invalid. Specifies whether the task is reusable or not. REP_ALL_SCHEDULERS MX View Column Name SUBJECT_ID SCHEDULER_ID SCHEDULER_NAME START_TIME Datatype NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (30) Description Folder ID. 0 = disabled. Informatica recommends using the fields in bold to join views. Table 15-40 lists reusable and non-reusable task information in the REP_ALL_TASKS view: Table 15-40. 0 = not reusable. Folder ID. Task ID. UTC checkin time. Table 15-41 lists information in the REP_ALL_SCHEDULERS view: Table 15-41. worklet.REP_ALL_TASKS This view provides a list of all reusable and non-reusable tasks that can be used by a workflow or a worklet. Task type. Scheduler ID (primary key). 1 = enabled. Task type name. Task name. 374 Chapter 15: Using Metadata Exchange (MX) Views . Values are: 1 = reusable. UTC time when task was last saved. REP_ALL_SCHEDULERS This view displays a list of schedulers by folder. Description of the task. Specifies whether the task is enabled or not. Version number of the task. 1 = valid. Start time configured for the object associated with the scheduler. or session is valid. Name of the scheduler. REP_ALL_TASKS MX View Column Name SUBJECT_AREA SUBJECT_ID TASK_NAME TASK_ID IS_VALID DESCRIPTION VERSION_NUMBER IS_ENABLED UTC_CHECKIN UTC_LAST_SAVED IS_REUSABLE TASK_TYPE TASK_TYPE_NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER VARCHAR2 (30) NUMBER NUMBER VARCHAR2 (240) Description Folder name.

Specifies whether the scheduler is reusable or not. Workflow. and Task Views 375 . UTC time (Coordinated Universal Time) when the scheduler was last saved. 18 = Run on server init and Run once schedule. Specifies when the task must stop running. Records the following values for each schedule type: 1 = Run on demand. Number of workflow runs. Date and time when this task was last saved. Workflow ID (primary key). Unique ID for a variable within a workflow (primary key). The scheduler type. 34 = Run continuously and Run once schedule. 20 = Run on server init and Delta schedule. Description of the scheduler. 24 = Run on server init and Custom repeat. REP_WFLOW_VAR MX View Column Name SUBJECT_ID WORKFLOW_ID VARIABLE_ID Datatype NUMBER NUMBER NUMBER Description Folder ID. 5 = Run on demand and Delta schedule. Used by END_OPTIONS column. Delta between successive runs (stored as seconds). Figure 15-42 lists variable information in the REP_WFLOW_VAR view: Table 15-42. 9 = Run on demand and Custom repeat.Table 15-41. Version number of the scheduler. 3 = Run on demand and Run once schedule. REP_ALL_SCHEDULERS MX View Column Name END_TIME RUN_OPTIONS Datatype VARCHAR2 (30) NUMBER Description End time configured for the object associated with the scheduler. 36 = Run continuously and Delta schedule. 2 = Run once schedule. END_OPTIONS DELTA_VALUE RUN_COUNT DESCRIPTION IS_REUSABLE LAST_SAVED VERSION_NUMBER UTC_LAST_SAVED UTC_CHECKIN NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER Informatica recommends using the fields in bold to join views. REP_WFLOW_VAR This view displays a list of all variables declared within a workflow or worklet. UTC checkin time. Worklet. 40 = Run continuously and Custom repeat.

Table 15-43 lists event information in the REP_EVENT view: Table 15-43. Variable type. 376 Chapter 15: Using Metadata Exchange (MX) Views . Comments on the variable.Table 15-42. Workflow ID (primary key). ID of the instance where the variable is defined. Name of the task instance. Workflow version number. Specifies whether the workflow variable is null or persistent. Event scope. REP_EVENT MX View Column Name SUBJECT_ID WORKFLOW_ID EVENT_ID EVENT_NAME EVENT_TYPE EVENT_SCOPE EVENT_DESCRIPTION LAST_SAVED Datatype NUMBER NUMBER NUMBER VARCHAR2 (30) NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (30) Description Folder ID. VARIABLE_DEFAULT_VALUE LAST_SAVED TASK_INST_ID TASK_INST_NAME BIT_OPTIONS VARCHAR2 (2000) VARCHAR2 (30) NUMBER VARCHAR2 (240) NUMBER VERSION_NUMBER NUMBER Informatica recommends using the fields in bold to join views. Date and time that this event was last saved. Date and time that this task was last saved. REP_EVENT This view displays the details of events created at the workflow or worklet level. Name of the event. REP_WFLOW_VAR MX View Column Name VARIABLE_NAME VARIABLE_TYPE VARIABLE_DESCRIPTION VARIABLE_DATATYPE Datatype VARCHAR2 (30) NUMBER VARCHAR2 (2000) NUMBER Description Name of the variable. Event description. 1 = workflow variable is persistent. 1 = user-defined. 2 = workflow variable is NULL. Event type. 3 = decimal 4 = integer 5 = small integer 7 = real 8 = double 11 = date/time 12 = string Default value of a variable. 0 = built in. Event ID (primary key). 1 = user-defined. Datatype of a workflow variable. 0 = built in.

Name of the instance. The ID of the source task instance. REP_EVENT MX View Column Name VERSION_NUMBER Datatype NUMBER Description Workflow version number. Task ID. Server ID associated with the workflow. Description of the task.Table 15-43. 1 = valid. 0 = invalid. REP_TASK_INST MX View Column Name WORKFLOW_ID INSTANCE_ID TASK_ID TASK_TYPE TASK_TYPE_NAME INSTANCE_NAME IS_ENABLED DESCRIPTION IS_VALID VERSION_NUMBER SERVER_ID Datatype NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER Description Workflow ID (primary key). Table 15-44 lists task instance information in the REP_TASK_INST view: Table 15-44. Workflow version number. Worklet. Table 15-45 lists task and worklet connection information in the REP_WORKFLOW_DEP view: Table 15-45. Name of the object. REP_WORKFLOW_DEP This view shows how individual tasks and worklets are connected within a worklet or a workflow. REP_TASK_INST This view displays all task instances within workflows and worklets. Informatica recommends using the fields in bold to join views. Specifies whether the task instance is enabled. Informatica recommends using the fields in bold to join views. Task type. Workflow. Instance ID (primary key). REP_WORKFLOW_DEP MX View Column Name WORKFLOW_ID FROM_INSTANCE_ID Datatype NUMBER NUMBER Description Workflow ID. and Task Views 377 . Specifies whether the task is valid.

Task type. Start time configured for task execution. Version number. Name of the task instance. Version number.Table 15-45. Run ID of a worklet in a workflow. The value that identifies the condition associated with the link. Informatica recommends using the fields in bold to join views. REP_WORKFLOW_DEP MX View Column Name TO_INSTANCE_ID CONDITION_ID VERSION_NUMBER CONDITION Datatype NUMBER NUMBER NUMBER VARCHAR2 (2000) Description The ID of the target task instance. Task error message. Run ID of a child task in a worklet. ID of an instance within a workflow or a worklet. ID of the parent workflow. Condition ID. Run ID of the parent workflow. End time configured for task execution. 378 Chapter 15: Using Metadata Exchange (MX) Views . Table 15-46 lists run statistics and folder reference information in the REP_TASK_INST_RUN view: Table 15-46. Workflow name. Object name. REP_TASK_INST_RUN MX View Column Name SUBJECT_AREA WORKFLOW_NAME VERSION_NUMBER SUBJECT_ID WORKFLOW_ID WORKFLOW_RUN_ID WORKLET_RUN_ID CHILD_RUN_ID INSTANCE_ID INSTANCE_NAME TASK_ID TASK_TYPE_NAME TASK_TYPE START_TIME END_TIME RUN_ERR_CODE RUN_ERR_MSG Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER DATE DATE NUMBER VARCHAR2 (2000) Description Folder name. Task ID. Folder ID. Task error code. REP_TASK_INST_RUN This view displays the run statistics and folder reference for tasks within a workflow or worklet.

Table 15-47 lists workflow run statistic information in the REP_WFLOW_RUN view: Table 15-47. Name of the server. Start time configured for the workflow. Workflow run ID. Task version number. and Task Views 379 . Workflow name. ID of the PowerCenter Server. Workflow ID. Server name. 1 = Suceeded 2 = Disabled 3 = Failed 4 = Stopped 5 = Aborted 6 = Running 7 = Suspending 8 = Suspended 9 = Stopping 10 = Aborting 11 = Waiting 12 = Scheduled 13 = Unscheduled 14 = Unknown 15 = Terminated Task name. Full path and name of the log file. Error message code. End time configured for the workflow. Worklet. REP_TASK_INST_RUN MX View Column Name RUN_STATUS_CODE Datatype NUMBER Description Status code of the task. PowerCenter Server ID. REP_WFLOW_RUN This view displays the run statistics for all workflows by folder. TASK_NAME TASK_VERSION_NUMBER SERVER_ID SERVER_NAME VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) Informatica recommends using the fields in bold to join views. REP_WFLOW_RUN MX View Column Name SUBJECT_ID WORKFLOW_ID WORFLOW_RUN_ID WORKFLOW_NAME SERVER_ID SERVER_NAME START_TIME END_TIME LOG_FILE RUN_ERR_CODE Datatype NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) DATE DATE VARCHAR2 (2000) NUMBER Description Folder ID. Workflow.Table 15-46.

Folder version name. Workflow version number.Table 15-47. Specifies how the workflow was run. 1 = Normal. Name of the user who ran the workflow. Table 15-48 lists reusable session information in the REP_LOAD_SESSIONS view: Table 15-48. Time the session was last saved. Version number of the mapping. Repeat count. Source ID. Status code for the workflow run. Name of the mapping this session uses. Session log file name. Informatica recommends using the fields in bold to join views. Version number of the session. Specifies whether the session is active. Folder version ID. REP_LOAD_SESSIONS MX View Column Name SUBJECT_AREA SESSION_NAME LAST_SAVED SESSION_ID MAPPING_NAME VERSION_ID VERSION_NAME IS_ACTIVE STARTTIME SESS_INTERVAL REPEAT_COUNT SESSION_LOG_FILE BAD_FILE_LOCATION TARGET_ID SOURCE_ID SESSION_VERSION_NUMBER MAPPING_VERSION_NUMBER Datatype VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Description Folder name. REP_WFLOW_RUN MX View Column Name RUN_ERR_MSG RUN_STATUS_CODE USER_NAME RUN_TYPE VERSION_NUMBER SUBJECT_AREA Datatype VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) Description Error message. 380 Chapter 15: Using Metadata Exchange (MX) Views . Session ID. Name of the session. Location of the reject file. Target ID. Folder name. REP_LOAD_SESSIONS This view provides information about reusable sessions in the repository. 2 = Recovery. Session interval. Session start time.

Name of the session. REP_LOAD_SESSIONS MX View Column Name SUBJECT_ID IS_VALID IS_REUSABLE COMMENTS MAPPING_ID Datatype NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER Description Folder ID. REP_SESSION_CNXS MX View Column Name SUBJECT_AREA SUBJECT_ID SESSION_NAME SESSION_ID IS_TARGET Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER INTEGER Description Folder name in which the session is stored. Sequence ID for the mapping associated with the session. Table 15-49 lists reusable session connection information in the REP_SESSION_CNXS view: Table 15-49. 0 = invalid. CONNECTION_NAME CONNECTION_ID SESSION_VERSION_NUMBER VARCHAR2 (240) INTEGER NUMBER Informatica recommends using the fields in bold to join views. Description of the session. this view shows the connection in the session instance and the connection information in the reusable session. 1 = target connection. If a session instance overrides the connection information in a reusable session. 1 = valid. Connection ID. and Task Views 381 . Specifies whether the session is valid or not. 0 = source connection. Folder ID. 0 = not reusable. Specifies whether the session is reusable or not. This view does not show connection information for reusable sessions that are not associated with any workflows. Specifies whether the connection is the target or the source. REP_SESSION_CNXS This view contains information about connections associated with reusable sessions. Version number of the session. Informatica recommends using the fields in bold to join views.Table 15-48. Session ID. Worklet. 1= reusable. REP_SESSION_INSTANCES This view contains connection information for session instances. Name of the connection. Workflow.

Table 15-50 lists session instance connection information in the REP_SESSION_INSTANCES view: Table 15-50. Name of the workflow the session instance belongs to. 1 = target file connection. Specifies the connection type. Workflow ID. Session instance name. Directory where the source or target file is stored. Name of the source or target file. Session ID. 1 = target connection. Connection ID associated with the session instance. 0 =source file connection. REP_SESSION_FILES MX View Column SUBJECT_AREA SESSION_NAME SESSION_VERSION_NUMBER IS_TARGET FILE_NAME DIR_NAME Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER INTEGER VARCHAR2 (240) VARCHAR2 (240) Description Name of the folder containing the session. Name of the connection associated with the session instance. Name of the session. Workflow version number. 0 = source connection. Specifies the connection type. Session instance ID. Session version number. Version number of the session. REP_SESSION_INSTANCES MX View Column Name SUBJECT_AREA SUBJECT_ID WORKFLOW_NAME WORKFLOW_ID SESSION_INSTANCE_NAME SESSION_INSTANCE_ID SESSION_ID IS_TARGET CONNECTION_NAME CONNECTION_ID WORKFLOW_VERSION_NUMBER SESSION_VERSION_NUMBER Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER INTEGER VARCHAR2 (240) INTEGER NUMBER NUMBER Description Folder name. Folder ID. Informatica recommends using the fields in bold to join views. Table 15-51 lists reusable session file connection information in the REP_SESSION_FILES view: Table 15-51. 382 Chapter 15: Using Metadata Exchange (MX) Views . REP_SESSION_FILES This view contains file connections associated with reusable sessions.

Table 15-51. 1 = target file connection. Informatica recommends using the fields in bold to join views. REP_SESS_WIDGET_CNXS MX View Column WIDGET_INSTANCE_ID WIDGET_TYPE INSTANCE_NAME Datatype NUMBER NUMBER VARCHAR2 (240) Description The instance ID of a source. Name of the workflow to which the session instance belongs. If a reusable session is not associated with a workflow. Identifies a source. Name of the session instance. target. or transformation. Informatica recommends using the fields in bold to join views. Instance name. Workflow version number. Code page associated with the source or target file. and Task Views 383 . Worklet. The reader and writer types and the connection name also display. Table 15-52 lists session instance file connection information in the REP_SESSION_INSTANCE_FILES view: Table 15-52. or transformation. Name of the source or target file. REP_SESS_WIDGET_CNXS This view contains information about the sources and targets used in a session. this view does not show file connection information for the session. 0 = source file connection. Table 15-53 lists connection information in the REP_SESS_WIDGET_CNXS view: Table 15-53. Workflow. Directory where the source or target file is stored. Specifies the connection type. REP_SESSION_INSTANCE_FILES MX View Column SUBJECT_AREA WORKFLOW_NAME WORKFLOW_VERSION_NUMBER SESSION_INSTANCE_NAME IS_TARGET FILE_NAME DIR_NAME CODE_PAGE Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) Description Name of the folder containing the session. REP_SESSION_FILES MX View Column CODE_PAGE Datatype VARCHAR2 (240) Description Code page associated with the source or target file. target. REP_SESSION_INSTANCE_FILES This view contains file connection information for session instances associated with workflows.

Component value. REP_SESS_WIDGET_CNXS MX View Column READER_WRITER_TYPE CNX_NAME SESSION_ID SESSION_WIDG_INST_ID SESS_EXTN_OBJECT_TYPE SESS_EXTN_OBJECT_SUBTYPE SESS_CNX_REFS_OBJECT_TYPE SESS_CNX_REFS_OBJECT_SUBTYPE SESS_CNX_REFS_OBJECT_ID WORKFLOW_ID SESSION_INSTANCE_ID SESSION_VERSION_NUMBER Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER Description Type of reader or writer used. Session instance ID. Session ID. Informatica recommends using the fields in bold to join views. Informatica recommends using the fields in bold to join views. Session instance ID. 78 = reader. Type of referenced object. Identifies the referred object's sequence type. Description of the value. Object version number. Object type. Indicates whether the object is a reader or a writer. ID of a task within a session. ID of the referenced object. Figure 15-54 lists session component information in the REP_COMPONENT view: Table 15-54. 384 Chapter 15: Using Metadata Exchange (MX) Views .Table 15-53. Session version number. Connection name. REP_COMPONENT MX View Column WORKFLOW_ID TASK_ID TASK_INST_ID REF_OBJ_TYPE OBJECT_TYPE OBJECT_SEQ_TYPE VERSION_NUMBER PM_VALUE VAL_NAME DESCRIPTION Datatype NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) VARCHAR2 (240) VARCHAR2 (2000) Description ID of the workflow to which the session belongs. REP_COMPONENT This view displays the list of tasks such as a command or an email for each session. Transformation instance ID referenced by a session (primary key). 79 = writer. Indicates a specific object. Session ID. Workflow ID. Name of the value. Indicates a specific reader or writer.

Informatica recommends using the fields in bold to join views. target. ID of a source. targets. Session configuration attribute type. Object type name. If the session overrides a parameter in the configured object. or transformation in a session. Description of the partition.REP_SESS_PARTITION_DEF This view provides partition details of the sources. REP_SESS_CONFIG_PARM This view displays session configuration parameter details. Session version number. Worklet. Session configuration attribute ID. and transformations in a session. Identifies a source. target. Partition ID Partition name. or transformation. Table 15-56 lists session configuration information in the REP_SESS_CONFIG_PARM view: Table 15-56. Select the row which contains the session ID reference. Session configuration ID. REP_SESS_CONFIG_PARM MX View Column SESSION_ID SESSION_VERSION_NUMBER CONFIG_ID ATTR_ID ATTR_TYPE Datatype NUMBER NUMBER NUMBER NUMBER NUMBER Description Session ID. Workflow. Session instance ID. ID of the mapping used by the session. Time when the partition was last modified. and Task Views 385 . Table 15-55 lists partition information in the REP_SESS_PARTITION_DEF view: Table 15-55. Session version number. Instance ID of a source. the view displays two rows. or transformation. REP_SESS_PARTITION_DEF MX View Column SESSION_ID SESS_WIDG_INST_ID PARTITION_ID PARTITION_NAME DESCRIPTION LAST_SAVED VERSION_NUMBER MAPPING_ID WIDGET_ID WIDGET_TYPE INSTANCE_ID INSTANCE_NAME TYPE_NAME Datatype NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (30) NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) Description Session ID. target. Instance name.

Task attribute ID. Attribute value. 386 Chapter 15: Using Metadata Exchange (MX) Views . Attribute value. Session ID. REP_TASK_ATTR MX View Column WORKFLOW_ID INSTANCE_ID TASK_ID TASK_TYPE REF_SESSION_ID TASK_TYPE_NAME ATTR_ID ATTR_NAME ATTR_VALUE LINE_NO GROUP_ID VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER Description Workflow ID. Table 15-57 lists attribute information in the REP_TASK_ATTR view: Table 15-57. Group ID. Session version number if task attribute is overridden at session level. Task type. Task attribute name. Workflow version number if task attribute is overridden at workflow level. Informatica recommends using the fields in bold to join views. Task type name. Task instance ID. Line number of attribute values. Informatica recommends using the fields in bold to join views. REP_TASK_ATTR This view displays the attribute values and overridden values for session and workflow tasks. Used for storing multiple lines of attribute values. Task ID. REP_SESS_CONFIG_PARM MX View Column ATTR_NAME ATTR_VALUE Datatype VARCHAR2 (240) VARCHAR2 (2000) Description Session configuration attribute name.Table 15-56.

Version number of the task. Folder ID. Location of the reject file. REP_SESS_LOG MX View Column SUBJECT_AREA SUBJECT_ID SESSION_ID SESSION_INSTANCE_NAME ACTUAL_START SESSION_TIMESTAMP RUN_STATUS_CODE Datatype VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) DATE (DB SPECIFIC) DATE (DB SPECIFIC) NUMBER Description Folder name. Last error message. Actual time session started. Time completed. which might contain one or many target tables. Number of successfully read source rows. Worklet. and Task Views 387 . 1 = Suceeded 2 = Disabled 3 = Failed 4 = Stopped 5 = Aborted 6 = Running 7 = Suspending 8 = Suspended 9 = Stopping 10 = Aborting 11 = Waiting 12 = Scheduled 13 = Unscheduled 14 = Unknown 15 = Terminated Last error code. This view supplies the status of the last session. Session log file name.REP_SESS_LOG This view provides log information about sessions. Number of successfully loaded target rows. Table 15-58 lists session log information in the REP_SESS_LOG view: Table 15-58. First error code. Number of failed target rows. Session instance name. LAST_ERROR_CODE LAST_ERROR TASK_VERSION_NUMBER WORKFLOW_VERSION_NUMBER SESSION_LOG_FILE BAD_FILE_LOCATION SUCCESSFUL_SOURCE_ROWS FAILED_SOURCE_ROWS SUCCESSFUL_ROWS FAILED_ROWS FIRST_ERROR_CODE NUMBER VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Workflow. Session ID. Run status code. Workflow version number. Number of failed source rows.

Session ID. Run ID of a worklet in a workflow. Workflow ID. row counts. Folder ID. Mapping name. Session instance ID. REP_SESS_LOG MX View Column FIRST_ERROR_MSG WORKFLOW_NAME MAPPING_NAME SESSION_NAME WORKFLOW_ID WORKFLOW_RUN_ID WORKLET_RUN_ID INSTANCE_ID TOTAL_ERR Datatype VARCHAR2 (2000) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Description First error message. Name of the session instance. Session name. REP_SESS_TBL_LOG MX View Column Name SUBJECT_AREA SUBJECT_ID SESSION_NAME SESSION_ID SESSION_INSTANCE_NAME SESSION_INSTANCE_ID WORKFLOW_ID WORKFLOW_VERSION_NUMBER TABLE_NAME TABLE_ID TABLE_VERSION_NUMBER TABLE_BUSNAME TABLE_INSTANCE _NAME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) Description Folder name. Total error code. Instance ID. Table 15-59 lists individual session information in the REP_SESS_TBL_LOG view: Table 15-59. Workflow run ID. Informatica recommends using the fields in bold to join views. 388 Chapter 15: Using Metadata Exchange (MX) Views . Target instance name for the session. Version number of the target. Target table ID. Workflow ID. Business name of the target. Session name. Workflow version number. It provides the last update time.Table 15-58. REP_SESS_TBL_LOG This view contains information about the status of an individual session run against a target. Name of the workflow that contains the session instance. Name of the table for this log. and error status based on a last update timestamp on a per target basis.

Object name.Table 15-59. Last error message. Workflow. and Task Views 389 . Number of affected target rows Number of failed target rows. Worklet. Object unique type ID. Mapplet instance name. REP_SESS_TBL_LOG MX View Column Name SUCCESSFUL_ROWS SUCCESSFUL_AFFECTED_ROWS FAILED_ROWS LAST_ERROR LAST_ERROR_CODE START_TIME END_TIME SESSION_TIMESTAMP BAD_FILE_LOCATION SESSION_VERSION_NUMBER PARTITION_NAME MAPPLET_INSTANCE_NAME WIDGET_NAME TYPE_NAME GROUP_NAME THROUGHPUT TYPE_ID Datatype NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER DATE DATE NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER Description Number of successfully loaded target rows. Time the target load started. Last error code. Group name. Location of the reject file. Session timestamp. Transformation name. Name of the partition. Time the target load ended. Version number of the session. Informatica recommends using the fields in bold to join views. Performance numbers for the target.

see “REP_USER_GROUPS” on page 391.Security Views Security views allow you to see user and group information such as privileges and contact information. 1 = valid. REP_USERS MX View Column USER_ID USER_NAME USER_PRIVILEGES1 USER_DESCRIPTION USER_FLAGS CONTACT_INFO IS_VISIBLE USER_ISENABLED USER_EXTERNAL_ID USER_EXTERNAL_LOGIN Datatype NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) Description User ID (primary key). This view provides association details between PowerCenter users and the group to which they belong. Privileges granted to the user. 0 = deleted. Specifies whether the user is system-created or usercreated. 0 = system-created. Unique global user ID. 1 = enabled. User contact information. REP_USERS This view provides a list of all PowerCenter users along with details on user privileges and contact information. For more information. Specifies whether user can log in. Table 15-61 lists user information in the REP_USERS view: Table 15-61. For more information. This view provides a list of PowerCenter groups along with details on group privileges and contact information. User login ID used by external authentication modules. Informatica recommends using the fields in bold to join views. Description of the user. Table 15-60 lists the different views that help you analyze security metadata: Table 15-60. see “REP_GROUPS” on page 391. Specifies whether user is valid. 0 = disabled. User name. see “REP_USERS” on page 390. For more information. Security Views View REP_USERS REP_USER_GROUPS REP_GROUPS Description This view provides a list of all PowerCenter users along with details on user privileges and contact information. 1 = user-created. 390 Chapter 15: Using Metadata Exchange (MX) Views .

REP_USER_GROUPS This view provides an association between PowerCenter users and the group to which they belong. Specifies whether the group is system-created or usercreated. Contact information for the group. Group name. Group ID. CONTACT_INFO VARCHAR2 (2000) Informatica recommends using the fields in bold to join views. Security Views 391 . REP_GROUPS MX View Column GROUP_ID GROUP_NAME GROUP_PRIVILEGES GROUP_DESCRIPTION GROUP_FLAGS Datatype NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER Description Group ID (primary key). Group description. Table 15-62 lists group association information in the REP_USER_GROUPS view: Table 15-62. Table 15-63 lists group information in the REP_GROUPS view: Table 15-63. REP_USER_GROUPS MX View Column USER_ID GROUP_ID Datatype NUMBER NUMBER Description User ID. REP_GROUPS This view provides a list of PowerCenter groups along with details on group privileges and contact information. Informatica recommends using the fields in bold to join views. 0 = system-created. Group privileges. 1 = user-created.

Query group ID. Deployment group name. REP_DEPLOY_GROUP This view provides information on deployment groups. Query description.Deployment Views Deployment views allow you to see deployment information such as deployment groups. source and target repository names associated with deployment. Query ID associated with a dynamic group. 392 Chapter 15: Using Metadata Exchange (MX) Views . For more information. 0 = static. For more information. Deployment group type. Name of user who created the query. Query user. Table 15-65 lists deployment group information in the REP_DEPLOY_GROUP view: Table 15-65. Name of user who created the deployment group. deployment date. User ID. This view provides Change Management deployment details. Query name associated with a dynamic group. and objects which were deployed from one repository to another. see “REP_DEPLOY_GROUP” on page 392. see “REP_DEPLOY_GROUP_DETAIL” on page 393. Group ID. Creation time. Deployment Views View REP_DEPLOY_GROUP REP_DEPLOY_GROUP_DETAIL Description This view provides information on deployment group in Change Management. Description of the group. Last saved time. Table 15-64 lists the different views that help you analyze deployment metadata: Table 15-64. 1 = dynamic. REP_DEPLOY_GROUP MX View Column DEP_GROUP_ID DEP_GROUP_NAME DESCRIPTION CREATED_BY OWNER_ID GROUP_ID CREATION_TIME LAST_SAVED GROUP_TYPE QUERY_ID QUERY_NAME QUERY_DESCRIPTION QUERY_CREATED_BY QUERY_OWNER_ID QUERY_GROUP_ID Datatype NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (30) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER Description Deployment group ID.

Object type name. Query last saved time. 2 = deploy from. 1 = deploy to. Deployment user ID. 0 = invalid. Folder ID in the source repository. 2 = personal. 1 = shortcut. TARGET_REP_NAME REP_GID USER_ID VARCHAR2 (240) VARCHAR2 (240) NUMBER Deployment Views 393 . REP_DEPLOY_GROUP MX View Column QUERY_CREATION_TIME QUERY_LAST_SAVED QUERY_TYPE Datatype VARCHAR2 (30) VARCHAR2 (30) NUMBER Description Query creation time. REP_DEPLOY_GROUP_DETAIL MX View Column DEP_RUN_ID OBJECT_ID OBJECT_NAME OBJECT_TYPE OBJECT_TYPE_NAME SRC_VERSION_NUMBER TARG_VERSION_NUMBER SRC_SUBJECT_ID SRC_SUBJECT_AREA TARG_SUBJECT_AREA IS_SHORTCUT DEP_GROUP_ID DEP_GROUP_NAME DEPLOY_TIME DEPLOY_TYPE Datatype NUMBER NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) NUMBER NUMBER Description Unique deployment run ID. Object type. 0 = not a shortcut Deployment group ID. Object version number in the source repository. Folder name in the target repository. Deployment group name.Table 15-65. Deployment start time. 1 = public. Table 15-66 lists deployment information in the REP_DEPLOY_GROUP_DETAIL view: Table 15-66. Object ID. Object version number in the target repository. REP_DEPLOY_GROUP_DETAIL This view provides deployment details. Specifies whether the object is a shortcut. Name of the object. Global ID of the repository. Informatica recommends using the fields in bold to join views. Folder name in the source repository. Deployment type. Query type. Target repository name.

ROLLBACK_TIME NUMBER Informatica recommends using the fields in bold to join views. Deployment rollback time. Deployment user name. UTC deployment time. 2 = rollback failed.Table 15-66. REP_DEPLOY_GROUP_DETAIL MX View Column GROUP_ID USER_NAME UTC_DEPLOY_TIME DEPLOY_STATUS Datatype NUMBER VARCHAR2 (240) NUMBER NUMBER Description Group ID. Deployment status. 394 Chapter 15: Using Metadata Exchange (MX) Views . 0 = deployed. 1 = rollback.

Table 15-67 lists repository information in the REP_REPOSIT_INFO view: Table 15-67. and whether the repository is local or global.Repository View The repository view allows you to see repository name. Name of the machine hosting the Repository Server. Description of the repository. DOMAIN_NAME DATABASE_USER DATABASE_TYPE HOSTNAME PORTNUM VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER Informatica recommends using the fields in bold to join views. Repository type. Repository type. Repository name. Repository ID. MX provides the REP_REPOSIT_INFO view to help you analyze repository metadata. REP_REPOSIT_INFO MX View Column RECID REPOSIT_NAME REPOSIT_DESCRIPTION REPOSITORY_ID REPOSITORY_TYPE Datatype NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER NUMBER Description Repository record ID. Global domain name. 1 = global. and database type. connection information on which the repository is created. domain name. Repository View 395 . REP_REPOSIT_INFO This view provides repository information such as repository name and type. Port number of the Repository Server. 3 = local. Database user name used to connect to the repository. database type. 2 = standalone.

Port number of the machine hosting the PowerCenter Server. see “REP_SERVER_NET” on page 397. Table 15-69 lists PowerCenter Server information in the REP_SERVER_INFO view: Table 15-69. The views allow you to see information about your server grid. location. For more information. Specified timeout when attempting to communicate with the server. IP address. host name. see “REP_SERVER_NET_REF” on page 397.PowerCenter Server Views The PowerCenter Server views allow you to see information about PowerCenter Server resources. see “REP_REPOSIT_INFO” on page 395. PowerCenter Server name. IP address. Information on the machine hosting the PowerCenter Server. and recent activity. This view provides information on PowerCenter Server description. and timeout. This view provides information about PowerCenter Server identification and usage. Time when an object was last saved. Name of the machine hosting the PowerCenter Server. and timeout. IP address of the host machine. REP_SERVER_NET REP_SERVER_NET_REF REP_SERVER_INFO This view provides PowerCenter Server information such as server name. PowerCenter Server Views View REP_SERVER_INFO Description This view provides information about PowerCenter Server name. such as server locations. REP_SERVER_INFO MX View Column SERVER_ID SERVER_NAME HOST_INFO TIMEOUT PORT_NO HOSTNAME IP_ADDRESS LAST_SAVED Datatype NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (30) Description PowerCenter Server ID (primary key). and usage. Table 15-68 lists the different views that help you analyze server resources and your access to them: Table 15-68. 396 Chapter 15: Using Metadata Exchange (MX) Views . For more information. such as the server name and host name that can be used to run workflows in PowerCenter. descriptions. host name. For more information. Informatica recommends using the fields in bold to join views.

PowerCenter Server Views 397 . Use network and used by network = 3. Time when the server was last saved.REP_SERVER_NET This view provides PowerCenter Server grid information and provides description and usage information. PowerCenter Server ID (primary key). Informatica recommends using the fields in bold to join views. PowerCenter Server job distribution options. Server name. REP_SERVER_NET MX View Column SERVER_NET_ID SERVER_NET_NAME SERVER_NET_DESCRIPTION LAST_SAVED Datatype NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (30) Description Server ID within the grid (primary key). REP_SERVER_NET_REF MX View Column SERVER_NET_ID SERVER_ID BIT_OPTIONS Datatype NUMBER NUMBER NUMBER Description PowerCenter Server ID within the grid (primary key). REP_SERVER_NET_REF This view provides PowerCenter Server identification within the grid and usage information. Informatica recommends using the fields in bold to join views. Description of the server. Table 15-71 lists PowerCenter Server identification and usage information within the grid in the REP_SERVER_NET_REF view: Table 15-71. Table 15-70 lists PowerCenter Server information in the REP_SERVER_NET view: Table 15-70. Use network = 1.

see “REP_CM_LABEL” on page 399. Change Management Views View REP_VERSION_PROPS REP_CM_LABEL REP_CM_LABEL_REF Description Provides information on the version history of all objects in a PowerCenter repository. Provides information on labels in Change Management. Folder ID. mapplets. workflows. User who last modified this version of the object. see “REP_CM_LABEL_REF” on page 399. mappings. Time when object was last saved. Object subtype ID. and tasks. see “REP_VERSION_PROPS” on page 398. UTC time when the object was last modified. Host machine name from which the version of the object is saved. Database name used by source objects. For more information. For more information. Table 15-72 lists the different views that help you analyze version history of objects and label metadata: Table 15-72. Objects can be defined as tables. Description of the object. For more information. REP_VERSION_PROPS This view provides the version history of all objects in a PowerCenter repository.Change Management Views Change Management views allow you to see the version history of all objects in a PowerCenter repository and label metadata. transformations. Object version number. Name of the object. Provides information on label details in Change Management. 398 Chapter 15: Using Metadata Exchange (MX) Views . Labels can be defined on all objects. worklets. sessions. REP_VERSION_PROPS MX View Column OBJECT_ID OBJECT_TYPE OBJECT_SUBTYPE VERSION_NUMBER SUBJECT_ID USER_ID OBJECT_NAME GROUP_NAME LAST_SAVED UTC_LAST_SAVED COMMENTS SAVED_FROM Datatype NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (30) NUMBER VARCHAR2 (2000) VARCHAR2(240) Description Object ID. Object type ID (primary key). Table 15-73 lists label information in the REP_VERSION_PROPS view: Table 15-73.

Table 15-75 lists label information in the REP_CM_LABEL_REF view: Table 15-75. REP_CM_LABEL MX View Column LABEL_ID LABEL_NAME DESCRIPTION CREATED_BY OWNER_ID GROUP_ID CREATION_TIME LAST_SAVED LABEL_TYPE LABEL_STATUS Datatype NUMBER VARCHAR2 (240) VARCHAR2 (2000) VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (30) NUMBER NUMBER Description Label ID. Informatica recommends using the fields in bold to join views. Table 15-74 lists label information in the REP_CM_LABEL view: Table 15-74. REP_CM_LABEL This view provides label information. Informatica recommends using the fields in bold to join views. Label description. Name of user who created the label. 2 = label locked. Label type. Object ID. User ID. Object version number. 2 = Can apply label to only one version of the object. Time when label was last saved. Group ID. Change Management Views 399 . Folder ID. REP_VERSION_PROPS MX View Column PURGED_BY_USERID Datatype NUMBER Description User ID who purged the object from the repository. Label status. Object type ID. 1 = label unlocked. Label name. REP_CM_LABEL_REF This view provides information on label details.Table 15-73. Label creation time. REP_CM_LABEL_REF MX View Column LABEL_ID OBJECT_ID OBJECT_TYPE VERSION_NUMBER SUBJECT_ID Datatype NUMBER NUMBER NUMBER NUMBER NUMBER Description Label ID.

REP_CM_LABEL_REF MX View Column USER_ID DESCRIPTION APPLY_TIME Datatype NUMBER VARCHAR2 (2000) VARCHAR2 (30) Description User ID. Label description.Table 15-75. 400 Chapter 15: Using Metadata Exchange (MX) Views . Time when label was applied to the object. Informatica recommends using the fields in bold to join views.

and description of each folder. MX provides the REP_SUBJECT view to help you analyze folder metadata: REP_SUBJECT This view displays folder information such as folder name and description. Informatica recommends using the fields in bold to join views. It describes the name. Folder View 401 . ID.Folder View The folder view allows you to see all the folders defined in the PowerCenter repository. REP_SUBJECT MX View Column SUBJECT_AREA SUBJECT_ID DESCRIPTION Datatype VARCHAR2 (240) NUMBER VARCHAR2 (2000) Description Folder name. Folder ID. Folder description. Table 15-76 lists folder information in the REP_SUBJECT view: Table 15-76.

402 Chapter 15: Using Metadata Exchange (MX) Views .

412 pmrep Security Commands. 477 Scripting pmrep and pmrepagent Commands. 460 pmrepagent Commands. 491 Tips. 406 Specifying Options and Arguments. 449 pmrep Change Management Commands.Chapter 16 Using pmrep and pmrepagent This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. 406 Running Commands in Interactive Mode. 492 403 . 407 pmrep System Commands. 410 pmrep Repository Commands. 404 Running Commands in Command Line Mode.

see “pmrep Change Management Commands” on page 460. see “pmrep System Commands” on page 410. create relational connections. Using pmrep Use pmrep to update session-related parameters and security information in the Informatica PowerCenter repository. pmrepagent runs in command line mode only. you can enter commands in interactive mode or command line mode. Connect to the repository. You can use pmrep in either command line mode or interactive mode. copy. 404 Chapter 16: Using pmrep and pmrepagent . pmrep uses the following types of commands to perform repository tasks: ♦ System commands. or delete deployment groups. Add or remove user and group privileges. Edit user profiles and password information. get help information. For more information on pmrepagent commands. Use system commands when you work with pmrep repository and security commands. see “pmrepagent Commands” on page 477. Using Native Connect Strings Some pmrep and pmrepagent commands.Overview pmrep and pmrepagent are command line programs that you use to update repository information and perform repository functions. pmrep and pmrepagent install in the Repository Server installation directory and also in the PowerCenter Client installation directory. When you use pmrep and pmrepagent. Repository commands. Import or export objects. Execute queries. see “pmrep Security Commands” on page 449. such as pmrep CreateConnection and pmrepagent Restore. Add. For more details on change management commands. change connection names. Change management commands. For more information on running commands in these modes. such as restoring repositories. Back up a repository. clean up persistent resources. Security commands. Check in objects. require a native connect string. For more information on repository commands. update session notification email addresses. and update server variables. For more details on security commands. ♦ ♦ ♦ Using pmrepagent Use pmrepagent to perform repository functions. For more information on system commands. Add or remove users and groups. see “Running Commands” on page 406. Add or delete labels. see “pmrep Repository Commands” on page 412. and exit pmrep.

world sambrown@mydatabase TeradataODBC TeradataODBC@mydatabase TeradataODBC@jsmith *Use Teradata ODBC drivers to connect to source and target databases. Overview 405 .Table 16-1 lists the native connect string syntax for each supported database when you create or update connections: Table 16-1. Native Connect String Syntax Database IBM DB2 Informix Microsoft SQL Server Oracle Sybase Teradata* Connect String Syntax dbname dbname@servername servername@dbname dbname.world (same as TNSNAMES entry) servername@dbname ODBC_data_source_name or ODBC_data_source_name@db_name or ODBC_data_source_name@db_user_name Example mydatabase mydatabase@informix sqlserver@mydatabase oracle.

The command line mode is useful if you want to run pmrep or pmrepagent commands through batch files. You cannot use pmrepagent in interactive mode. type the following command to run pmrep: pmrep command_name [-option1] argument_1 [-option2] argument_2. ♦ ♦ Interactive mode. Enter pmrep followed by the command name and its required options and arguments. To run pmrep commands in interactive mode: 1.. 2. Enter pmrep at the command prompt to invoke interactive mode. You can use command line mode to script pmrep and pmrepagent commands. switch to the directory where the pmrepagent executable is located. For more information on scripting pmrep or pmrepagent commands. type the following command to run pmrepagent: pmrepagent command_name [-option1] argument_1 [-option2] argument_2. 2. 3. 3. The Command syntax contains options and arguments you use when you specify commands. To run pmrepagent commands in command line mode: 1. At the command prompt. pmrep does not exit after it completes a command. Running Commands in Command Line Mode The command line mode invokes and exits pmrep or pmrepagent each time you issue a command. see “Scripting pmrep and pmrepagent Commands” on page 491. scripts.. You can issue pmrep commands from an interactive prompt.Running Commands When you use pmrep and pmrepagent. or other programs. To run pmrep commands in command line mode: 1. At the command prompt. At the command prompt. Command line mode. Enter pmrepagent followed by the command name and its required options and arguments.. you can enter commands in interactive mode or command line mode. At the command prompt. switch to the directory where the pmrep executable is located. You can issue pmrep and pmrepagent commands directly from the system command line.. Running Commands in Interactive Mode The interactive mode invokes pmrep and allows you to issue a series of commands from a pmrep prompt without exiting after each command. 406 Chapter 16: Using pmrep and pmrepagent .

At the pmrep> prompt. Specifying Options and Arguments Commands in pmrep and pmrepagent may require you to specify options and arguments. you must provide the name of the repository when using the connect command: connect -r production ♦ Specify options in any order.. Option Arguments Use the following rules to specify arguments: ♦ The first word after the option letter is considered the argument. Options Use the following rules when you specify command options and arguments: ♦ Specify options by typing a minus sign followed by a letter. 3. both of the following commands are valid: connect -r production -n sambrown connect -n sambrown -r production ♦ Options are case-sensitive when the command contains an upper-case and lower-case option. pmrep runs the command and displays the pmrep> prompt again. Running Commands 407 ♦ . such as -x and -X. type: command_name [-option1] argument_1 [-option2] argument_2. For example. An option and its argument do not have to be separated by a space. You do not have to type pmrep before each command in interactive mode. as shown using the Connect command: connect -r ♦ Most options require arguments. you can use both of the following Connect commands to connect to a repository: connect -r production connect -rproduction ♦ If any argument for an option or command contains more than one word. Type a command and its options and arguments. pmrep and pmrepagent ignore quotes that do not enclose an argument. you must enclose the argument in double quotes. Back quotes (‘) are not allowed. For example.This starts pmrep in interactive mode and displays a pmrep> prompt. For example. Commands fail and display an error message if any required option or argument is missing or not specified. 2. Type exit to end an interactive session..

At the shell prompt. You set the password on the PowerCenter Repository Server and encrypt it with the pmpasswd utility. The encryption utility generates and displays your encrypted password. To encrypt a password: 1. and pmrepserver in scripts. pmrepagent. In a UNIX session. Use the following steps as a guideline to use an encrypted password as an environment variable: 1. pmpasswd. To configure a password environment variable: If you are in a UNIX C shell environment. to encrypt your repository password. The following is sample output. pmrepagent. You can use the PASSWORD environment variable for commands such as Connect. and Backup. Configuring Repository Passwords on UNIX You can enter your repository password at the command line as an environment variable. In this example. 3. When you use password environment variables.” Encrypted string -->bX34dqq<-Will decrypt to -->monday<-- Your encrypted password is bX34dqq. You may want to encrypt your repository password to maintain security when you use pmrep. For more details on the pmrepserver command. The password is an encrypted value. Use the environment variable with the appropriate pmrep.Using Password Environment Variables Some pmrep commands use password environment variable options. you must encrypt your repository password. 2. 2. type: setenv PASSWORD YourEncryptedPassword 408 Chapter 16: Using pmrep and pmrepagent . navigate to the PowerCenter Server installation directory. Create. Configure the PASSWORD environment variable to set the encrypted value. the password entered was “monday. type: pmpasswd YourPassword This command runs the encryption utility pmpasswd located in the PowerCenter Server installation directory. see “Installing and Configuring the Repository Server on Windows” and “Installing and Configuring the Repository Server on UNIX” in the Installation and Configuration Guide. or pmrepserver command. Use the command line program.

In this example. 2. User variables take precedence over system variables. 2.If you are in a UNIX Bourne shell environment.” Encrypted string -->bX34dqq<-Will decrypt to -->monday<-- Your encrypted password is bX34dqq. type: pmpasswd YourPassword The encryption utility generates and displays your encrypted password. Using Password Environment Variables 409 . For information about setting environment variables for your Windows operating system. type: PASSWORD= YourEncryptedPassword export PASSWORD You can assign the environment variable any valid UNIX name. The password is an encrypted value. To encrypt a password: 1. consult your Windows documentation. Enter environment variables in the Windows System Properties. The following is sample output. Enter your encrypted password in the Value field. navigate to the PowerCenter Server installation directory. To configure a password environment variable: 1. At the command line. Configuring Repository Passwords on Windows You can enter your repository password at the command line as an environment variable. In Windows DOS. Enter the name of your password environment variable in the Variable field. You can set these up as either a user or system variable. the password entered was “monday.

Repository user name used to connect to the repository. All commands require a connection to the repository. Table 16-2 lists pmrep system commands: Table 16-2. The host name of the machine running the Repository Server. See “Connecting to a Repository (Connect)” on page 410. Cleans up persistent resources created by pmrep during a session. you must call the Connect command. pmrep System Commands pmrep Command Connect Help Cleanup Exit Command Description Connects to the repository. Use the -x or -X option. Use the -x or -X option. The port number the Repository Server uses for connections. 410 Chapter 16: Using pmrep and pmrepagent . Password for the repository user name. Connect uses the following command syntax: connect -r repository_name -n repository_username -x repository_password -X repository_password_environment_variable -h repserver_host_name -o repserver_port_number Table 16-3 lists pmrep Connect options and arguments: Table 16-3. See “Getting Help (Help)” on page 411. The password environment variable for the repository. Connecting to a Repository (Connect) The first time you use pmrep in either command line or interactive mode. See “Cleaning up Persistent Resources (Cleanup)” on page 411. Displays help for all commands or for a specified command. but not both. but not both.pmrep System Commands This section describes basic pmrep commands that you use in conjunction with other pmrep repository and security commands. Connect Options and Arguments (pmrep) Option -r -n -x -X -h -o Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Argument Name repository_name repository_username repository_password repository_password_ environment_variable repserver_host_name repserver_port_number Argument Description Name of the repository you want to connect to. “Exiting pmrep (Exit)” on page 411. Exits from pmrep.

options. pmrep retains the connection until you exit pmrep or connect again. This command also cleans up any connection information from previous sessions of pmrep. If you call Cleanup in the interactive mode. and specifies which arguments to provide. type exit. If you use pmrep to perform tasks in multiple repositories in a single session. pmrep uses the connection information specified in the last successful connection made to the repository from any previous session of pmrep. pmrep uses the information specified by the last call to connect to the repository. In command line mode. If the second connection fails. pmrep System Commands 411 . pmrep retains information from the last successful connection until you use the Cleanup command. pmrep connects to and disconnects from the repository with every command. pmrep disconnects from the first repository and then connects to the second repository. the previous connection remains disconnected and you will not be connected to any repository. use the following syntax: cleanup Exiting pmrep (Exit) The Exit command exits from the pmrep interactive mode. Informatica recommends calling Cleanup in the command line mode only. Calling Cleanup as the first command in a session always returns an error. To clean up persistent resources. it returns an error. Help uses the following command syntax: help [command] Cleaning up Persistent Resources (Cleanup) The Cleanup command cleans up any persistent resource created by pmrep. The help information printed to the screen shows the command name. The command line mode invokes and exits pmrep each time you issue a command. Getting Help (Help) The Help command prints help for all commands or for a specified command. In the interactive mode. If you call Connect again. If you issue a command that requires a connection to the repository. To exit the pmrep interactive mode. and you are not connected to that repository. If pmrep is called without a successful connect. you must issue the Connect command each time you want to switch to a different repository. pmrep disconnects any repository you are connected to.In the command line mode.

pmrep Repository Commands
pmrep allows you to perform repository administration tasks, such as backing up the repository, creating relational connections, and updating PowerCenter Server variables. Table 16-4 describes pmrep repository administration commands:
Table 16-4. pmrep Repository Commands pmrep Command Addserver Addrepository Backup CreateConnection Deleteconnection Deleteserver Disablerepository Enablerepository ListObjects Listtablesbysess ListObjectDependencies Notify ObjectExport ObjectImport Register Removerepository Run Command Description Adds a PowerCenter Server. See “Adding a Server (Addserver)” on page 413. Adds a repository configuration to the Repository Server. See “Adding Repository Configurations (Addrepository)” on page 414. Backs up a repository. See “Backing up a Repository (Backup)” on page 416. Creates a relational connection. See “Creating a Relational Connection (CreateConnection)” on page 417. Deletes an existing relational connection. See “Deleting a Connection (Deleteconnection)” on page 420. Deletes a PowerCenter Server. See “Deleting a Server (Deleteserver)” on page 421. Disables a repository. See “Disabling a Repository (Disablerepository)” on page 421. Enables a repository. See “Enabling a Repository (Enablerepository)” on page 422. Lists objects in the repository. See “Listing Repository Objects (ListObjects)” on page 423. Lists sources or targets in a session. See “Listing Tables by Session (Listtablesbysess)” on page 428. Lists dependent objects. See “Listing Object Dependencies (ListObjectDependencies)” on page 429. Sends notification messages. See “Sending Notification Messages (Notify)” on page 431. Exports objects to an XML file. See “Exporting Objects (ObjectExport)” on page 432. Imports objects from an XML file. See “Importing Objects (ObjectImport)” on page 433. Registers local repositories with global repositories. See “Registering Local Repositories (Register)” on page 434. Removes a repository from the Repository Server cache entry list. See “Removing Repositories From the Cache (Removerepository)” on page 435. Displays messages stating whether a run has completed or failed. See “Running Script Files (Run)” on page 436.

412

Chapter 16: Using pmrep and pmrepagent

Table 16-4. pmrep Repository Commands pmrep Command ShowConnectioninfo Command Description Shows repository name, server, port and user information for the current connection. See “Showing Connection Information (ShowConnectioninfo)” on page 437. Stops the repository you last connected to using pmrep. See “Stopping a Repository (StopRepository)” on page 437. Changes the name of an existing connection. See “Changing the Connection Name (SwitchConnection)” on page 438. Truncates log details from repository level, folder level, or workflow level. See “Truncating Workflow and Session Logs (Truncatelog)” on page 439. Unregisters local repositories from global repositories. See “Unregistering Local Repositories (Unregister)” on page 440. Changes user name, password, and connect string for a connection. See “Updating a Database Connection (UpdateConnection)” on page 441. Updates the session notification email addresses. See “Updating the Notification Email Addresses (Updateemailaddr)” on page 442. Updates transformation properties for Sequence Generator transformations. See “Updating Sequence Generator Transformations (Updateseqgenvals)” on page 444. Edit server details. See “Updating Server Details (Updateserver)” on page 443. Updates source table owner names. See “Updating the Source Table Owner Name (Updatesrcprefix)” on page 445. Updates server variables. See “Updating Server Variables (Updatesrvvar)” on page 446. Updates statistics for repository tables and indexes. See “Updating Repository Statistics (UpdateStatistics)” on page 447. Updates target table name prefixes. See “Updating the Target Table Name Prefix (Updatetargprefix)” on page 447.

StopRepository SwitchConnection Truncatelog Unregister UpdateConnection Updateemailaddr Updateseqgenvals

Updateserver Updatesrcprefix Updatesrvvar UpdateStatistics Updatetargprefix

Adding a Server (Addserver)
Use the Addserver command to add PowerCenter Servers. For more information about adding a PowerCenter Server see “Registering the PowerCenter Server” in the Installation and Configuration Guide. To add a server, you must have the Administer Repository privilege. Addserver uses the following command syntax:
addserver -v server_name -h new_host_name -o new_port_number -t new_timeout_value -p new_protocol_name -l new_codepage_name

pmrep Repository Commands

413

Table 16-5 lists pmrep Addserver options and arguments:
Table 16-5. Addserver Options and Arguments (pmrep) Option -v -h -o -t -p -l Required/ Optional Required Required Optional Optional Optional Optional Argument Name server_name new_host_name new_port_number new_timeout_value new_protocol_name new_codepage_name Argument Description The name of the PowerCenter Server you want to change. The server host name or IP address of the server machine. The port number of the server machine. The number of seconds the Workflow Manager waits for a response from the server. The protocol the server uses. The character set associated with the PowerCenter Server. Select the code page identical to the PowerCenter Server operating system code page. Must be identical to or compatible with the repository code page.

Adding Repository Configurations (Addrepository)
The Addrepository command adds repository configurations to the Repository Server. You might use Addrepository to add a repository configuration after restoring or creating a repository in the database using pmrepagent. When you add a repository configuration, pmrep connects to the Repository Server and adds a configuration file to the Repository Server installation directory. You do not need to connect to a repository to use this command.
Note: To configure other repository options, edit the repository configuration in the

Repository Server Administration Console. For more information on adding and editing repository configurations, see “Adding a Repository Configuration” on page 105. Addrepository uses the following command syntax:
addrepository -h repserver_host_name -o repserver_port_number -a repserver_password -A repserver_password_environment_variable -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m -c database_connect_string -d code_page -e DB2_tablespace_name -l license_file_name

414

Chapter 16: Using pmrep and pmrepagent

Table 16-6 lists pmrep Addrepository options and arguments:
Table 16-6. Addrepository Options and Arguments (pmrep) Option -h -o -a Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Required Argument Name repserver_host_name repserver_port_number repserver_password Argument Description The host name of the Repository Server that manages the repository. The port number of the Repository Server that manages the repository. The password you use to administer the Repository Server that manages the repository. Use the -a or -A option, but not both. The password environment variable you use to administer the Repository Server that manages the repository. Use the -a or -A option, but not both. The name of the repository. The type of database storing the repository. The account for the database containing the repository. Set up this account using the appropriate database client tools. Use a trusted connection to connect to the database. Valid for Microsoft SQL Server only. The repository database password corresponding to the database user. Must be in 7-bit ASCII. Not required if you are using option -m. Use the -p or -P option, but not both. The repository database password environment variable corresponding to the database user. Must be in 7-bit ASCII. Not required if you are using option -m. Use the -p or -P option, but not both. The native connect string the Repository Server uses to access the database containing the repository. For information on connect string syntax, see Table 16-1 on page 405. The repository code page. The Repository Server uses the character set encoded in the repository code page when writing data to the repository. If you omit this option, pmrep uses the code page of the global locale for the Repository Server.

-A

repserver_password_ environment_variable repository_name database_type database_user_name

-r -t -u

-m -p

Optional Required/ Optional

n/a database_password

-P

Required/ Optional

database_password_ environment_variable

-c

Required

database_connect_string

-d

Optional

code_page

pmrep Repository Commands

415

Table 16-6. Addrepository Options and Arguments (pmrep) Option -e Required/ Optional Optional Argument Name DB2_tablespace_name Argument Description The tablespace name for IBM DB2 repositories. When you specify the tablespace name, the Repository Server creates all repository tables in the same tablespace. You cannot use spaces in the tablespace name. Use the same tablespace name with this command and the pmrepagent Create and Restore commands. To improve repository performance on IBM DB2 EEE repositories, use a tablespace name with a single node. For more information on specifying the tablespace name, see “Adding a Repository Configuration” on page 105. The name of the license file.

-l

Optional

license_file_name

Backing up a Repository (Backup)
The Backup command backs up the repository to the file specified with the -o option. You must provide the backup filename. You can use this command when the repository is running. You must be connected to a repository to use this command. Backup uses the following command syntax:
backup -o output_file_name -f -d description -b skip_workflow/ session_logs -j skip_deploy_group_history -q skip_MX_data

Table 16-7 lists pmrep Backup options and arguments:
Table 16-7. Backup Options and Arguments (pmrep) Option -o -f -d Required/ Optional Required Optional Optional Argument Name output_file_name n/a description Argument Description The name and path of the file for the repository backup. Overwrites an existing file with the same name. Creates a description of the backup file based on the string that follows the option. The backup process truncates any character beyond 2,000. Specify this option if you want to skip tables related to workflow and session logs during backup. Skips deployment group history during backup. Skips tables related to MX data during backup.

-b -j -q

Optional Optional Optional

skip_workflow/ session_logs skip_deploy_group _history skip_MX_data

To restore the backup file, use the Repository Manager Administration Console, or use the pmrepagent Restore command. For details, see “Restoring a Repository (Restore)” on page 485.

416

Chapter 16: Using pmrep and pmrepagent

Note: You can also use the pmrepagent Backup command to back up a repository that is not

running. For details, see “Backing up a Repository (Backup)” on page 477.

Creating a Relational Connection (CreateConnection)
The CreateConnection command creates a relational source or target connection in the repository. You must be connected to a repository to use this command. Relational database connections for each relational subtype require a subset of all CreateConnection options and arguments. For example, Oracle connections do not accept the -z, -d, or -t options. CreateConnection uses the following command syntax:
createconnection -a data_source_name -s database_type -n connection_name -u username -p password -P password_environment_variable -c connect_string -l code_page -r rollback_segment -e environment_sql -z packet_size -b database_name -v server_name -d domain_name -t trusted_connection -x

Table 16-8 lists pmrep CreateConnection options and arguments:
Table 16-8. CreateConnection Options and Arguments (pmrep) Option -a -s -n -u -p Required/ Optional Required Required Required Required Required/ Optional Required/ Optional Required Argument Name data_source_name database_type connection_name username password Argument Description The Teradata ODBC data source name. Valid for Teradata connections only. The type of relational connection. For a list of valid database types, see Table 16-9 on page 418. The name of the connection. The user name used for authentication when you connect to the relational database. The password used for authentication when you connect to the relational database. Use the -p or -P option, but not both. The password environment variable used for authentication when you connect to the relational database. Use the -p or -P option, but not both. The connect string the PowerCenter Server uses to connect to the relational database. For a list of native connect strings, see Table 16-1 on page 405. The code page associated with the connection. For a list of valid code page IDs, see Table 16-10 on page 419. Valid for Oracle connections only. The name of the rollback segment. A rollback segment records database transactions that allow you to undo the transaction.

-P

password_environm ent_variable connect_string

-c

-l -r

Required Optional

code_page rollback_segment

pmrep Repository Commands

417

Table 16-8. CreateConnection Options and Arguments (pmrep) Option -e -z Required/ Optional Optional Optional Argument Name environment_sql packet_size Argument Description Enter SQL commands to set the database environment when you connect to the database. Valid for Sybase and Microsoft SQL Server connections only. Optimizes the ODBC connection to Sybase and Microsoft SQL Server. The name of the database. Valid for Sybase and Microsoft SQL Server connections only. The name of the database server. Valid for Sybase and Microsoft SQL Server connections only. Valid for Microsoft SQL Server connections only. The name of the domain. Used for Microsoft SQL Server on Windows. Valid for Microsoft SQL Server connections only. If selected, the PowerCenter Server uses Windows authentication to access the Microsoft SQL Server database. The user name that starts the PowerCenter Server must be a valid Windows user with access to the Microsoft SQL Server database. Enables enhanced security. Grants you read, write, and execute permissions. Public and world groups are not granted any permissions. If this option is not enabled, all groups and users are granted read, write, and execute permissions. For more information about enhanced security, see “Configuring the Workflow Manager” in the Workflow Administration Guide.

-b -v -d -t

Optional Optional Optional Optional

database_name server_name domain_name trusted_connection

-x

Optional

n/a

Specifying Database Type
When you create a new connection, you must specify a database type using the exact string associated with that database type in pmrep. The strings are not case-sensitive. Use quotes when specifying a string with spaces in an argument. Table 16-9 lists the required pmrep database type strings according to database:
Table 16-9. Database Type Strings Database IBM DB2 Informix Microsoft SQL Server ODBC Oracle Sybase Teradata Database Type String DB2 Informix Microsoft SQL Server ODBC Oracle Sybase Teradata

418

Chapter 16: Using pmrep and pmrepagent

Specifying Database Code Page Information
The -l option specifies the code page information for the database connection. To specify database code page information, you must use the string associated with the code page you want to assign to the database connection. If you configure the PowerCenter Server for data code page validation, changing the database connection code page can cause sessions to fail under the following conditions:
♦ ♦

The source database connection code page is not a subset of the PowerCenter Server code page. The target database connection code page is not a superset of the PowerCenter Server code page.

If you configure the PowerCenter Server for relaxed data code page validation, changing the database connection code page can cause data inconsistencies if the new code page is not compatible with the source or target database connection code pages. For details on data code page validation, see “Globalization Overview” in the Installation and Configuration Guide. For a list of supported code pages and code page compatibility reference, see “Code Pages” in the Installation and Configuration Guide. Table 16-10 lists the code page ID strings pmrep accepts to update database connection code page information:
Table 16-10. Code Page ID by Name (pmrep) Code Page Name 7-bit ASCII IBM EBCDIC Chinese (Simplified) IBM EBCDIC Chinese (Traditional) IBM EBCDIC French IBM EBCDIC German IBM EBCDIC International Latin-1 IBM EBCDIC Italian IBM EBCDIC Japanese IBM EBCDIC UK English IBM EBCDIC US English ISO 8859-1 Western European ISO 8859-2 Eastern European ISO 8859-3 Southeast European ISO 8859-4 Baltic ISO 8859-5 Cyrillic ISO 8859-6 Arabic pmrep ID String US-ASCII IBM935 IBM937 IBM297 IBM273 IBM500 IBM280 IBM930 IBM285 IBM037 Latin1 ISO-8859-2 ISO-8859-3 ISO-8859-4 ISO-8859-5 ISO-8859-6

pmrep Repository Commands

419

Table 16-10. Code Page ID by Name (pmrep) Code Page Name ISO 8859-7 Greek ISO 8859-8 Hebrew ISO 8859-9 Latin 5 (Turkish) ISO 8859-10 Latin 6 (Nordic) ISO 8859-15 Latin 9 (Western European) Japan Extended UNIX Code (incl. JIS x 0212) MS-DOS Thai, superset of TIS 620 MS Windows Arabic MS Windows Baltic Rim MS Windows Chinese (Simplified), superset of GB 2312-80, EUC encoding MS Windows Chinese (Traditional), superset of Big 5 MS Windows Cyrillic (Slavic) MS Windows Greek MS Windows Hebrew MS Windows Japanese, superset of Shift-JIS MS Windows Korean superset of KS C 5601-1992 MS Windows Korean (Johab) MS Windows Latin 1 (ANSI), superset of Latin 2 MS Windows Latin 2 (Central Europe) MS Windows Latin 5 (Turkish), superset of ISO 8859-9 MS Windows Vietnamese UTF-8 encoding of Unicode pmrep ID String ISO-8859-7 ISO-8859-8 ISO-8859-9 ISO-8859-10 ISO-8859-15 JapanEUC MS874 MS1256 MS1257 MS936 MS950 MS1251 MS1253 MS1255 MS932 MS949 MS1361 MS1252 MS1250 MS1254 MS1258 UTF-8

Deleting a Connection (Deleteconnection)
The Deleteconnection command deletes a relational connection from the repository. To delete a connection, you must have Administer Repository privilege, be the owner of the connection object, have write permission on the object, or belong to the same group as the owner. Deleteconnection uses the following command syntax:
deleteconnection -n relational_connection_name -f force_delete

420

Chapter 16: Using pmrep and pmrepagent

Table 16-11 lists pmrep Deleteconnection option and argument:
Table 16-11. Deleteconnection Options and Arguments (pmrep) Option -n -f Required/ Optional Required Optional Argument Name relational_connection_name force_delete Argument Description Name of the relational connection to delete. Connection will be deleted without further confirmation.

The command returns “deleteconnection completed successfully” or returns “Failed to execute deleteconnection” message. The delete might fail for the following reasons:
♦ ♦ ♦

The database connection does not exist. You do not have the appropriate privilege. The Repository Server cannot obtain a lock on the connection object.

Deleting a Server (Deleteserver)
The Deleteserver command deletes a server from the repository. To delete a server, you must have Administer Repository privilege. Deleteserver uses the following command syntax:
deleteserver -v server_name

Table 16-12 lists pmrep Deleteserver option and argument:
Table 16-12. Deleteserver Options and Arguments (pmrep) Option -v Required/ Optional Required Argument Name server_name Argument Description Name of the PowerCenter Server to delete.

The command returns an “operation successfully completed” or returns “operation failed” message. The delete might fail for the following reasons:
♦ ♦ ♦

The server does not exist. You do not have the appropriate permissions to delete a server. The Repository Server cannot acquire a lock on the object.

Disabling a Repository (Disablerepository)
The Disablerepository command disables a repository. If a running repository is disabled, it will continue to run. Once a disabled repository is stopped, it cannot be restarted until it is enabled. When you disable the repository, you must enable it before you can start it again. To disable a repository, you must have Administer Repository privilege.
pmrep Repository Commands 421

Disablerepository uses the following command syntax:
disablerepository -h host_name -o port_number -a repserver_password -A repserver_password_environment_variable -r repository_name

Table 16-13 lists pmrep Disablerepository option and argument:
Table 16-13. Disablerepository Options and Arguments (pmrep) Option -h -o -a -A Required/ Optional Required Required Required/ Optional Required/ Optional Required Argument Name host_name port_number repserver_password repserver_password_ environment_variable repository_name Argument Description Name of the machine hosting the Repository Server. Port number where the Repository Server is running. Repository Server administrator password. Use the -a or -A option, but not both. Repository Server administrator password environment variable. Use the -a or -A option, but not both. Name of the repository to disable.

-r

The command returns a “disablerepository completed successfully” or returns “Failed to execute disablerepository” message. The command might fail for the following reasons:
♦ ♦ ♦

You did not give the repository name in the argument. The connection to the repository server failed. The Repository Server failed to disable the repository.

Enabling a Repository (Enablerepository)
The Enablerepository command enables a repository that has been disabled. To enable a repository, you must have Administer Repository privilege. Enablerepository uses the following command syntax:
ensablerepository -h host_name -o port_number -a repserver_password -A repserver_password_environment_variable -r repository_name

Table 16-14 lists pmrep Enablerepository options and arguments:
Table 16-14. Enablerepository Options and Arguments (pmrep) Option -h -o -a Required/ Optional Required Required Required/ Optional Argument Name host_name port_number repserver_password Argument Description Name of the machine hosting the Repository Server. Port number where the Repository Server is running. Repository Server administrator password. Use the -a or -A option, but not both.

422

Chapter 16: Using pmrep and pmrepagent

To list objects. pmrep returns each object in a record and returns each object metadata in a column. Create a shell script that uses ListObjects to return Sequence Generator transformation information. You must connect to a repository to use this command.Table 16-14. The command might fail for the following reasons: ♦ ♦ ♦ You did not give the repository name in the argument. and then use the parsed data in another pmrep command. Listing Repository Objects (ListObjects) The ListObjects command returns objects in the repository. you do not need read permission on the folders. For example. Use the -a or -A option. you can use ListObjects to list all Sequence Generator transformations in the repository. and use Updateseqgenvals to update the sequence values. use characters that are not used in repository object names. You can use ListObjects in a shell script to return the object metadata. You can specify the character or characters to use to separate records and columns. pmrep Repository Commands 423 . Enablerepository Options and Arguments (pmrep) Option -A Required/ Optional Required/ Optional Required Argument Name repserver_password_ environment_variable repository_name Argument Description Repository Server administrator password environment variable. The Repository Server failed to enable the repository because the repository is not currently disabled. but not both. You can also specify the character or characters to indicate the end of the listing. It separates records by a new line by default. parse the data ListObjects returns. This helps you use a shell script to parse the object metadata. Name of the repository to enable. -r The command returns an “enablerepository completed successfully” or returns “Failed to execute enablerepository” message. pmrep returns object metadata to the screen. Tip: When you specify characters to separate records and columns and to indicate the end of the listing. you must have one of the following sets of privileges and permissions: ♦ ♦ Browse Repository privilege with read permission on the folder Super User privilege Note: When you list folders. The connection to the Repository Server failed. parse the metadata. When you list objects.

including shortcuts but excluding target instances. List targets with latest or checked out version in a folder. List reusable and non-reusable schedulers with latest or checked out version in a folder. List the workflows with latest version or checked out version in a folder. Sessionconfig. Task. List reusable and non-reusable sessions with latest or checked out version in a folder. List labels in the repository. 424 Chapter 16: Using pmrep and pmrepagent . List reusable and non-reusable tasks with latest or checked out version in a folder. Source. List sources with latest or checked out version in a folder. including shortcuts but excluding instances of reusable mapplets. Session. Query. Scheduler. Mapping. Mapplet. excluding instances of reusable worklets. Workflow.You can use the object_type option to define the objects you want to list. List folders in the repository Label. List deployment groups in the repository. and query object types are not associated with folders. List reusable and non-reusable transformations with latest or checked out version in a folder. including shortcuts but excluding instances of reusable mapplets. Folder. folder. excluding instances of reusable sessions. The command lists the latest versions or checked out versions of objects. The deploymentgroup. label. List mappings with latest or checked out version in a folder. Worklet. Transformation. ♦ ♦ ListObjects uses the following command syntax: listobjects -o object_type -t object_subtype -f folder_name -c column_separator -r end_of_record_separator -l end-of-listing_indicator -b verbose Do not use the -f option if the object type you list is not associated with a folder. including shortcuts but excluding source instances. List the session configurations with latest or checked out version in a folder. Target. but excluding objects according to the following rules for each object type: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Deploymentgroup. List mapplets with latest or checked out version in a folder. All other object types require the -f option. List queries in the repository. including shortcuts and excluding instances of reusable transformations. including shortcuts. List reusable and non-reusable worklets with latest version or checked out version in a folder.

The character or set of characters used to specify the end of the object metadata. such as label. When you specify transformation or task for the object type. and query. version number. -t Optional object_subtype -f -c Required Optional folder_name column_separator -r Optional end_of_record_separator -l Optional end_of_listing_indicator -b Optional verbose pmrep Repository Commands 425 . see Table 1616 on page 426. and connection. you must include the -f option. If you omit this option. folder name.When you specify objects other than folders. you might want to avoid using a space as a column separator. If you omit this option. The default is newline /n. and checked out information. Print more than the minimum information about the objects. you must include the -f option. The folder to search. Verbose format includes the label type. pmrep ignores the -t and -f options. . you print a shorter format including the object type. If any repository object name contains spaces. Use a character or set of characters that is not used in repository object names.Table 16-15 lists pmrep ListObjects options and arguments: Table 16-15.When you specify folder. query type. If you omit this option. you do not need to include any other option. Verbose format includes the object status. The short format for versioning objects. . Use a character or set of characters that is not used in repository object names. The type of transformation or task to list. folder. the word reusable or nonreusable. deployment group type.When you specify transformation or task. includes the object type and object name. deployment group. Specify a character or set of characters that is not used in repository object names. you can include this option to return a specific type. For a list of subtypes to use with ListObjects. the object name and path. and you can optionally include the -t option. Use this option for all object types except deploymentgroup. creator name and creation time. pmrep uses a period. ListObjects Options and Arguments (pmrep) Option -o Required/ Optional Required Argument Name object_type Argument Description The type of object to list. label. The character or set of characters used to specify the end of the object list. pmrep uses a single space. . query. The character or set of characters used to separate object metadata columns.

Table 16-16 lists the transformation types and values to use with pmrep commands: Table 16-16. Transformation and Task Types to Use with pmrep Object Type Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Transformation Task Task Task Task Task Task Task Subtype Custom Aggregator Application Source Qualifier Application Multi-Group Source Qualifier Expression External Procedure Filter Input Joiner Lookup Mapplet MQ Source Qualifier Normalizer Output Rank Router Sequence Generator Sorter Source Qualifier Stored Procedure Transaction Control Update Strategy XML Source Qualifier Assignment Command Control Decision Email Event-raise Event-wait Subtype Value custom_transformation aggregator application_source_qualifier app_multi-group_source_qualifier expression external_procedure filter input_transformation joiner lookup_procedure mapplet mq_source_qualifier normalizer output_transformation rank router sequence sorter source_qualifier stored_procedure transaction_control update_strategy xml_source_qualifier assignment command control decision email event_raise event_wait 426 Chapter 16: Using pmrep and pmrepagent .

For example. pmrep ignores the subtype and folder name.sp_nsproc sequence non-reusable smallmapplet. For example.transformation_name or mapplet_name. you can specify a different column separator and end of listing indicator: listobjects -o folder -c “**” -l # Listing Objects You can use ListObjects to list reusable and non-reusable objects in the repository or in a folder. enter the following text at the pmrep> prompt: listobjects -o transformation -f myfolder pmrep returns the following information: stored_procedure reusable sp_sproc1 expression reusable exp1 stored_procedure non-reusable mapping1. pmrep returns mapping_name. pmrep returns the name of the object with the path when applicable. to list all transformation types in a folder.sp_nsproc pmrep Repository Commands 427 . pmrep does not include instances of reusable objects. to list all Stored Procedure transformations in a folder. see Table 16-16 on page 426. enter the following text at the pmrep> prompt: listobjects -o folder Or.Table 16-16. For a list of transformation or task return values. Transformation and Task Types to Use with pmrep Object Type Task Task Subtype Start Timer Subtype Value start timer Listing Folders You can use ListObjects to return each folder in the repository. to list all folders in the repository. Or. When you list objects. enter the following text at the pmrep> prompt: listobjects -o transformation -t stored_procedure -f myfolder pmrep returns the following information: stored_procedure reusable sp_sproc1 stored_procedure non-reusable mapping1. when a transformation is in a mapping or mapplet. When you specify folder for the object type.listobjects completed successfully. For example.seqgen_empid . you must include the folder name for all objects that are associated with a folder.transformation_name.

pmrep returns source and target instance names as they appear in the session properties. For example.s_sales_Q3 session non-reusable wf_orders. To specify a non-reusable session in a workflow. You can use Listtablesbysess in a shell script with other pmrep commands..listobjects completed successfully. or specify target to list targets. if the mapping contains a mapplet with a source.session_name. The name of the session containing the sources or targets. When you list sources or targets. You can specify a reusable or non-reusable session. enter the workflow name and the session name as workflow_name. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Workflow Manager privilege with read permission on the folder Super User privilege Listtablesbysess uses the following command syntax: listtablesbysess -f folder_name -s session_name -t table_type Table 16-17 lists pmrep Listtablesbysess options and arguments: Table 16-17. you can create a shell script that uses Listtablesbysess to return source instance names and uses Updatesrcprefix to update the source owner name. Listtablesbysess Options and Arguments (pmrep) Option -f -s Required/ Optional Required Required Argument Name folder_name session_name Argument Description The name of the folder containing the session. To list all sessions in a folder. pmrep returns the source instance name in the following format: mapplet_name.source_name You must connect to a repository to use this command. When you use Listtablesbysess. enter the following text at the pmrep> prompt: listobjects -o session -f myfolder pmrep returns the following information: session reusable s_sales_by_CUSTID session non-reusable wf_sales. -t Required table_type 428 Chapter 16: Using pmrep and pmrepagent . pmrep returns source or target instance names to the screen.wl_shirt_orders. Specify source to list sources.s_shirt_orders . Listing Tables by Session (Listtablesbysess) The Listtablesbysess command returns sources or targets used in a session. For example.listobjects completed successfully. To list sources or targets. you cannot specify an instance of a reusable session. However.

you must have the following privileges and permissions: ♦ ♦ Browse Repository privilege Read permission on the folder ListObjectDependencies uses the following command syntax: ListObjectDependencies -n object_name -o object_type_name -t object_subtype -v version_number -f folder_name -i persistent_input_file -d dependency_object_type -p dependency_direction -s include_pk-fk_dependency -g across_repositories -u persistent_output_file_name -a append -c column_separator -r end-ofrecord_separator -l end-of-listing_indicator -b verbose pmrep Repository Commands 429 . Note: When the mapping contains a mapplet with a source.ORDERS Shortcut_To_ITEM_ID listtablesbysess completed successfully. If you create an output file. you must use a persistent input file containing object IDs. enter the following text at the pmrep> prompt: listtablesbysess -f myfolder -s s_reus_sess1 -t source pmrep returns the following information: ITEMS mapplet1. For more information on using a persistent input file.s_nrsess1 -t target pmrep returns the following information: target1_inst ORDERS_BY_CUSTID Shortcut_To_tgt2_inst listtablesbysess completed successfully. To list object dependencies. Note: ListObjectDependencies accepts a persistent input file and it can create a persistent output file. If you want to list dependencies for non-reusable objects. see “Using the Persistent Input File” on page 494.ORDERS. or Validate pmrep commands. Listing Object Dependencies (ListObjectDependencies) Use the ListObjectDependencies command list dependency objects for reusable and nonreusable objects. you can list all targets in a non-reusable session in a workflow: listtablesbysess -f myfolder -s wf_workkflow1. such as mapplet1. ListObjectDependencies returns the number of records if the command runs successfully. you can use it as input to the ApplyLabel. to list all sources in a reusable session. These files are the same format. For example.For example. You can create this file by running a query and choosing to create a text file. pmrep includes the mapplet name with the source. AddToDeployment Group.

see “Using the Persistent Input File” on page 494. If you use this option. children. You can specify source. Find object dependencies across repositories. You can specify parents.Note: ListObjectDependencies displays non-reusable objects as parent. Include the primary key-foreign key dependency object regardless of the direction of the dependency. The default sends the query result to stdout. mapping. and dimension. Table 16-18 lists pmrep ListObjectDependencies options and arguments: Table 16-18. -t -v -f Required/ Optional Optional Required/ Optional Optional object_subtype version_number folder_name -i persistent_input_file -d Optional dependency_object_t ype -p Required/ Optional Required/ Optional Optional Optional dependency_direction -s include_pkfk_dependency across_repositories persistent_output_file _name -g -u -a Optional append 430 Chapter 16: Using pmrep and pmrepagent . The folder containing object_name. Send the dependency result to a text file. then you cannot use the -n. If ALL. transformation. separate them by commas without spaces. worklet. You can specify ALL or one or more object types. target.parentobject_name. To specify multiple objects. scheduler. or both. then pmrep lists all supported dependent objects. For valid subtypes. ListObjectDependencies Options and Arguments (pmrep) Option -n -o Required/ Optional Optional Required Argument Name object_name object_type_name Argument Description The name of a specific object to list dependencies for. see Table 16-16 on page 426. The object type to list dependencies for. You can use the text file as input to the ApplyLabel. workflow. You must use this file if you want to list dependencies for non-reusable objects. The default is ALL. session config. cube. or Validate pmrep commands. Ignored for other object types. then pmrep lists dependent objects only for these types. AddToDeployment Group. task. Required if you do not use the -p option. If you choose one or more objects. session. -f options to specify objects. The type of dependent objects to list. For more information on using the persistent input file. List dependent objects for an object version other than the latest version. The parents or children dependent objects to list. session. Required if you do not use the -s option. Append the result to the persistent output file name file instead of overwriting it. -o. Folder is required if object type is not a folder and you are not using the -i option. The type of transformation or task. The text file of objects generated from ExecuteQuery or Validate commands.nonreusableobject_name.

pmrep uses a single space. deployment group. The default is newline /n. and connection. such as label. pmrep prints a shorter format including the object type. Use a character or set of characters that is not used in repository object names. Notify Options and Arguments (pmrep) Option -h -o Required/ Optional Required Required Argument Name hostname port_number Argument Description The name of the machine hosting the Repository Server. The short format for versioning objects. you might want to avoid using a space as a column separator. The character or set of characters used to specify the end of the object metadata. query. the object name and path. -r Optional end-ofrecord_separator -l Optional end-oflisting_indicator -b Optional verbose Sending Notification Messages (Notify) Use the Notify command to send notification messages to users connected to a repository or users connected to all repositories managed by a Repository Server. The character or set of characters used to specify the end of the object list. If you omit this option. Specify a character or set of characters that is not used in repository object names. If any repository object name contains spaces. you must have Administer Repository privilege. pmrep Repository Commands 431 . ListObjectDependencies Options and Arguments (pmrep) Option -c Required/ Optional Optional Argument Name column_separator Argument Description The character or set of characters used to separate object metadata columns. pmrep uses a period.Table 16-18. To send notification messages. The number of the port where the Repository Server is running. Verbose format includes the creator name and creation time. Use a character or set of characters that is not used in repository object names. includes the object type and object name. Print more than the minimum information about the objects. The Notify command uses the following command syntax: Notify -h hostname -o port_number [-a repserver_password | -A repserver_password_environment_variable] -r repository_name -t notify | broadcast -m message Table 16-19 lists pmrep Notify options and arguments: Table 16-19. the word reusable or nonreusable. If you omit this option. If you omit this option. Verbose format includes the version number and folder name.

objects referred by shortcut. You export an object by name. If you do not specify a version number.Table 16-19. The Repository Server failed to notify users. but not both. You failed to connect to the Repository Server. To export objects. Validate.dtd file. The Repository Server password environment variable. For more information on exporting objects. If you export a mapping. The name of the repository whose users you want to notify. you must have the following privileges and permissions: ♦ ♦ Browse Repository privilege Read permission on the source folder 432 Chapter 16: Using pmrep and pmrepagent . -r -t -m Required message The command returns “notify successfully completed” or returns “failed to execute notify” message. Notify Options and Arguments (pmrep) Option -a -A Required/ Optional Required/ Optional Required/ Optional Required Required Argument Name repserver_password repserver_password_ environment_variable repository_name notify | broadcast Argument Description The Repository Server password. Broadcast sends a message to users connected to all repositories managed by the given Repository Server. you export the latest version of the object. Use the -a or -A option. or ListObjectDependencies pmrep commands. For more information on using the persistent input file. you must add the appropriate pmrep options. The type of message you want to send to user. see “Using the Persistent Input File” on page 494. you must specify the folder that contains it. and related objects in a primary key-foreign key relationship. If you want to include dependent objects. If you specify an object. Use the -a or -A option. The message you want to send. You can optionally include reusable and non-reusable dependent objects. see “Overview” on page 264. You can create this file by using the ExecuteQuery. Notify sends a message to users connected to the repository. If you use the persistent input file then you do not use the other parameters to specify objects. Exporting Objects (ObjectExport) Use the ObjectExport command to export objects to an XML file defined by the powrmart. by default the PowerCenter client exports only the mapping and its instances. You can use a persistent input file to specify different objects to export at one time. The notification might fail for the following reasons: ♦ ♦ ♦ The message type you entered is invalid. but not both.

workflow. Export a version other than the latest version of the object. For more details about the control file. Specifies a log file to collect all the export files. then you must specify the folder containing the object. For valid subtypes. If you use this parameter. The text file list of objects generated from ExecuteQuery. -o. The object type of the object name. -o Required/ Optional Required/ Optional Optional Required object_type -t object_subtype -v -f version_number folder_name -i Optional persistent_input_file -u -l Required Optional xml_output_file_name log_file_name Importing Objects (ObjectImport) Use the ObjectImport command to import objects from an XML file. The name of the XML file to contain the object information. This command requires a control file to specify the objects to import and how to resolve conflicts. task. see “Importing Objects” on page 280. The type of transformation or task. then you cannot use the -n. If you do specify an object name. The name of the folder containing the object to export. -f options to specify objects.ObjectExport uses the following command syntax: ObjectExport -n object_name -o object_type -t object_subtype -v version_number -f folder_name -i persistent_input_file -u xml_output_file_name -l log_file_name Table 16-20 lists pmrep ObjectExport options and arguments: Table 16-20. worklet. or ListObjectDependencies. see “Using the Object Import Control File” on page 496. you must have the following privileges and permissions: ♦ Use Repository Manager privilege pmrep Repository Commands 433 . If you do not specify this option. For more information on importing objects. ObjectExport Options and Arguments (pmrep) Option -n Required/ Optional Optional Argument Name object_name Argument Description The name of a specific object to export. If you do not specify an object name. The control file is an XML file defined by the impcntl. target.dtd file. all the latest or checked out objects in the folder export. transformation. This argument is ignored for other object types. session config. You can specify source. see Table 16-16 on page 426. To import objects. It contains object records with encoded IDs. mapping. session. scheduler. then all the objects in this folder export. Validate.

Note: The ObjectImport command does not automatically create a folder if the folder you specify does not exist in the repository. Use the -x or -X option. The password you use to administer the global Repository Server. Use the -a or -A option.♦ Write permission on the target folder ObjectImport uses the following command syntax: ObjectImport -i input_XML_file_name -c control_file_name Table 16-21 lists pmrep ObjectImport options and arguments: Table 16-21. To register a local repository. but not both. The name of the control file that defines import options. The login password environment variable for the local target repository. but not both. See “Using the Object Import Control File” on page 496. you must have Administer Repository privilege. ObjectImport Options and Arguments (pmrep) Option -i -c Required/ Optional Required Required Argument Name input_XML_file_name control_file_name Argument Description The name of the XML file to import. The login password for the local target repository. but not both. -a 434 Chapter 16: Using pmrep and pmrepagent . You must connect to the global repository before you register the local repository. The local repository user name. Registering Local Repositories (Register) Use the Register command to register a local repository with a connected global repository. Use the -x or -X option. Register uses the following command syntax: Register -r repository_name -n repository_user_name [-x repository_password -X repository_password_environment_variable] [-a global_repserver_password | -A global_repserver_password_environment_variable] -h local_repository_host_name -o local_repository_port_number Table 16-22 lists pmrep Register options and arguments: Table 16-22. Register Options and Arguments (pmrep) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_ environment_variable global_repserver_password Argument Description The name of the local repository to register.

but not both. You failed to connect to the Repository Server. Removerepository Options and Arguments (pmrep) Option -h -o -a Required/ Optional Required Required Required/ Optional Argument Name hostname port_number repository_password Argument Description The hostname of the machine hosting the Repository Server. Use this option when the local repository is managed by a different Repository Server. The number of the port where the Repository Server is running. Use the -a or -A option. The port number of the Repository Server. If you use this option. you must use the -o option as well. Removing Repositories From the Cache (Removerepository) The Removerepository command removes repositories from the Repository Server cache entry list. The Repository Server failed to register the local repository with the global repository. The login password for the repository. Removerepository uses the following command syntax: Removerepository -h hostname -o port_number -a repository_password -A repository_server_password_environment_variable -r repository_name Table 16-23 lists pmrep Removerepository options and arguments: Table 16-23.Table 16-22. The Repository Server failed to initialize information about the global repository. Use this option when the local repository is managed by a different Repository Server. but not both. If you use this option. The hostname of the local repository. -h -o Optional local_repository_port_numb er The command returns “register successfully completed” or returns “failed to execute register” message. pmrep Repository Commands 435 . you must use the -h option as well. Register Options and Arguments (pmrep) Option -A Required/ Optional Required/ Optional Optional Argument Name global_repserver_password _environment_variable local_repository_host_name Argument Description The password environment variable you use to administer the global Repository Server. The registration might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. Use the -a or -A option.

436 Chapter 16: Using pmrep and pmrepagent . -e -s Optional Optional echo_commands stop_at_first_error The command returns “run successfully completed” or returns “run failed” message. Running Script Files (Run) The Run command takes a file containing multiple pmrep commands and runs those commands sequentially. The commands are echoed back to the script. The name of the repository to remove. Use the -a or -A option.Table 16-23. This option writes all messages generated by the commands in the script file into the output file. The name of the output file. -r The command returns “removerepository successfully completed” or “failed to execute removerepository” message. Stops the running of the script after a command returns an error. Run Options and Arguments (pmrep) Option -f -o Required/ Optional Required Optional Argument Name script_file_name output_file_name Argument Description The name of the script file. You failed to connect to the Repository Server. but not both. The run might fail if the Repository Server cannot open the script file or output file. All repository users can run script files. The Run command uses the following command syntax: run -f script_file_name -o output_file_name -e echo_commands -s stop_at_first_error Table 16-24 lists pmrep Run options and arguments: Table 16-24. The removal might fail for the following reasons: ♦ ♦ The repository name does not exist. Removerepository Options and Arguments (pmrep) Option -A Required/ Optional Required/ Optional Required Argument Name repository_password_ environment_variable repository_name Argument Description The login password environment variable for the repository.

if you do not specify a repository. For more information about connections in command line mode and interactive mode. if you run pmrep and enter: showconnectioninfo pmrep returns information similar to the following: connected to Repository MyRepository [servername:port#] connected as user MyUserName Use the ShowConnectioninfo command in interactive mode. StopRepository uses the following command syntax: stopRepository [-a repserver_password -A repserver_password_environment_variable] -h hostname -o port_number -r repository_name Note: If you use the -h. pmrep connects to the Repository Server and stops the Repository Agent. -o. see “Connecting to a Repository (Connect)” on page 410. However. the named repository stops.Showing Connection Information (ShowConnectioninfo) The ShowConnectioninfo command returns the repository name. When you use the ShowConnectioninfo command in command line mode. When you connect to a repository in interactive mode. You must be connected to a repository to use this command. pmrep does not keep connection information in command line mode. server. The ShowConnectioninfo command does not connect to the repository. ShowConnectioninfo requires no parameters. When you use the StopRepository command. port. the repository that you last connected to stops. a message indicating failure to execute the command is given. Stopping a Repository (StopRepository) The StopRepository command stops the repository you specify. pmrep Repository Commands 437 . Otherwise. and -r options. StopRepository stops the repository you last connected to. For example. the pmrep keeps the connection information in memory until you exit the repository or connect to a different repository. and user information for the current connection.

The password environment variable you use to administer the Repository Server that manages the repository. The name of the repository to stop. you must also use the -o and -r options. In a session. 438 Chapter 16: Using pmrep and pmrepagent . When you use this option. you must also use the -h and -r options. When you use SwitchConnection to replace the relational connection ITEMS with another relational connection. you specified the name ITEMS for a relational source connection instead of Relational:ITEMS. each called ITEMS. -A repserver_password_ environment_variable -h Optional hostname -o -r Optional Optional port_number repository_name Changing the Connection Name (SwitchConnection) The SwitchConnection command changes the name of an existing connection. You must be connected to a repository to use this command. The hostname of the Repository Server that manages the repository to stop.Table 16-25 lists pmrep StopRepository option and argument: Table 16-25. the Repository Server replaces the relational database connections for all sessions using the connection in one of the following locations: ♦ ♦ ♦ ♦ ♦ ♦ Source connection Target connection Connection Information property in Lookup transformations Connection Information property in Stored Procedure transformations $Source Connection Value session property $Target Connection Value session property If the repository contains both relational and application connections with the same name and you specified the connection type as relational in all locations in the repository. Use the -a or -A option. but not both. For example. StopRepository Option and Argument (pmrep) Option -a Required/ Optional Required/ Optional Required/ Optional Argument Name repserver_password Argument Description The password you use to administer the Repository Server that manages the repository. you must also use the -h and -o options. the Repository Server replaces the relational connection. but not both. you have a relational and an application source. When you use this option. pmrep does not replace any relational connection in the repository because it cannot determine the connection type for the source connection entered as ITEMS. The Repository Server port number. When you use this option. When you use SwitchConnection. Use the -a or -A option.

” Use “all” to delete all the logs. If you give both the folder name and workflow name. Truncatelog uses the following command syntax: Truncatelog -t all| endtime -f folder_name -w workflow_name Table 16-27 lists pmrep Truncatelog options and arguments: Table 16-27. The Repository Server deletes all logs from the repository if you do not give both the folder name and the workflow name. or delete logs for a folder or workflow. the Repository Server deletes logs associated with the workflow. Truncatelog Options and Arguments (pmrep) Option -t Required/ Optional Required Argument Name all | endtime Argument Description Use “all” or “endtime. Deletes logs associated with the folder. Truncating Workflow and Session Logs (Truncatelog) The Truncatelog command deletes details from the repository. Otherwise. The new connection name. use endtime and specify a time with a format of: MM/DD/YYYY HH24:MI:SS. -f Optional folder_name -w Optional workflow_name pmrep Repository Commands 439 . If you do not give both the folder name and the workflow name. To run Truncatelog.SwitchConnection uses the following command syntax: switchconnection -o old_connection_name -n new_connection_name To replace connections with pmrep. SwitchConnection Options and Arguments (pmrep) Option -o -n Required/ Optional Required Required Argument Name old_connection_name new_connection_name Argument Description The name of the existing connection you want to change. you must have Super User privilege. Table 16-26 lists pmrep SwitchConnection options and arguments: Table 16-26. you must also provide the folder name. Deletes logs associated with the workflow. you must have Administer Repository privilege. pmrep deletes all logs older than the endtime. You can also specify a date and delete all logs older than that date. then you delete all logs from the repository. You can delete all logs. If you specify the workflow name.

The truncation might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. Unregistering Local Repositories (Unregister) Use the Unregister command to unregister a local repository from a connected global repository. The login password for the local target repository. The login password environment variable for the local target repository. Use the -a or -A option. The password you use to administer the global Repository Server. The workflow does not exist in the given folder. To unregister a local repository. but not both. but not both. You must connect to the global repository before you unregister the local repository. Use the -a or -A option. Unregister Options and Arguments (pmrep) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_ environment_variable global_repserver_password Argument Description The name of the local repository to unregister. The local repository user name. but not both. The password environment variable you use to administer the global Repository Server. You specified a workflow. you must have Administer Repository privilege. but not both. -a -A global_repserver_password_ environment_variable 440 Chapter 16: Using pmrep and pmrepagent .The command returns “truncatelog completed successfully” or returns “Failed to execute truncatelog” message. Use the -x or -X option. but no folder name. Unregister uses the following command syntax: Register -r repository_name -n repository_user_name [-x repository_password | -X repository_password_environment_variable] [-a global_repserver_password | -A global_repserver_password_environment_variable] -h local_repository_host_name -o local_repository_port_number Table 16-28 lists pmrep Unregister options and arguments: Table 16-28. The folder name is invalid. Use the -x or -X option.

The Repository Server failed to unregister the local repository to the global repository. A failure might occur for the following reasons: ♦ ♦ ♦ ♦ ♦ The database type is not supported. password. you must have one of the following privileges and permissions: ♦ ♦ ♦ Write permission for the connection object Ownership of the object Membership in a group that owns the object The command returns an “operation successfully completed” or returns “operation failed” message. you must use the -h option as well.Table 16-28. Use this option when the local repository is managed by a different Repository Server. UpdateConnection uses the following command syntax: updateconnection -t database_type -d database_connection_name -u new_user_name -p new_database_password -P new_database_password_environment_variable -c new_database_connection_string -a attribute_name -v new_attribute_value pmrep Repository Commands 441 . pmrep cannot acquire a lock on the object. connect string. To update a connection. The number of the port where the Repository Server is running. Updating a Database Connection (UpdateConnection) The UpdateConnection command updates the user name. One of the required parameters is missing. The connection object does not exist. Unregister Options and Arguments (pmrep) Option -h Required/ Optional Optional Argument Name local_repository_host_name Argument Description The hostname of the local repository. The registration might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. You failed to connect to the Repository Server. Use this option when the local repository is managed by a different Repository Server. If you use this option. The current user does not have the appropriate permissions. -o Optional local_repository_port_number The command returns “unregister successfully completed” or returns “failed to execute unregister” message. and attributes for a database connection. The Repository Server failed to initialize information about the global repository. If you use this option. you must use the -o option as well.

You can specify different addresses to receive either success or failure notifications. If you did not previously specify a success or failure Email task for the session. The password used for authentication when you connect to the relational database. The user name used for authentication when you connect to the relational database.Table 16-29 lists pmrep UpdateConnection options and arguments: Table 16-29. The password environment variable used for authentication when you connect to the relational database. Enter “yes” or “no” for attributes you enable through a checkbox. For a list of native connect strings. The connect string the PowerCenter Server uses to connect to the relational database. Updateemailaddr uses the following command syntax: updateemailaddr -d folder_name -s session_name -u success_email_address f failure_email_address 442 Chapter 16: Using pmrep and pmrepagent . -P new_database_password_ environment_variable -c Required new_database_connection _string attribute_name new_attribute_value -a -v Optional Optional Updating the Notification Email Addresses (Updateemailaddr) The Updateemailaddr command updates the session notification email addresses associated with the Email tasks assigned to the session. Use the -p or -P option. see Table 16-9 on page 418. but not both. For a list of valid database types. You can update the email notification addresses only for a non-reusable session with a unique name in the folder. This command requires you to connect to a repository. The name of the attribute. the command does not update the email addresses. The new attribute value of the connection. Use the -p or -P option. see Table 16-1 on page 405. but not both. UpdateConnection Options and Arguments (pmrep) Option -t -d -u -p Required/ Optional Required Required Required Required/ Optional Required/ Optional Argument Name database_type database_connection_na me new_user_name new_database_password Argument Description The type of relational connection. The database connection name.

Table 16-30 lists pmrep Updateemailaddr options and arguments: Table 16-30. Must be identical to or compatible with the repository code page. The character set associated with the PowerCenter Server. The new name of the PowerCenter Server. Updateserver Options and Arguments (pmrep) Option -v -h -k -o -t -p -l Required/ Optional Required Optional Optional Optional Optional Optional Optional Argument Name server_name new_host_name new_servername new_port_number new_timeout_value new_protocol_name new_codepage_name Argument Description The name of the PowerCenter Server you want to change. Updateserver uses the following command syntax: updateserver -v server_name -h new_host_name -k new_servername -o new_port_number -t new_timeout_value -p new_protocol_name -l new_codepage_name Table 16-31 lists pmrep Updateserver options and arguments: Table 16-31. The server host name or IP address of the server machine. Email address to send session failure notifications. pmrep Repository Commands 443 . Email address to send session success notifications. The protocol the PowerCenter Server uses. Select the code page identical to the PowerCenter Server operating system code page. The number of seconds the Workflow Manager waits for a response from the PowerCenter Server. To update server details. you must have the Administer Repository privilege. Updating Server Details (Updateserver) The Updateserver command updates PowerCenter Server details with the values that you specify in the command. Updateemailaddr Options and Arguments (pmrep) Option -d -s -u -f Required/ Optional Required Required Required Required Argument Name folder_name session_name success_email_address failure_email_address Argument Description Name of the session folder. For more information about PowerCenter Server details see “Registering the PowerCenter Server” in the Installation and Configuration Guide. The port number the PowerCenter Server. Only the values that you specify update. Name of the session.

The Sequence Generator transformation name. you cannot update values for instances of reusable Sequence Generator transformations or shortcuts to Sequence Generator transformations. For more information on configuring Sequence Generator transformations. When you update values for a nonreusable Sequence Generator transformation. To update sequence values. You can use Updateseqgenvals to update reusable and non-reusable Sequence Generator transformations. The mapping name. You must connect to a repository to use this command. Updateseqgenvals Options and Arguments (pmrep) Option -f -m Required/ Optional Required Required/ Optional Required Argument Name folder_name mapping_name Argument Description The folder name. you must include the mapping name. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Designer privilege with write permission on the folder Super User privilege Updateseqgenvals uses the following command syntax: updateseqgenvals -f folder_name -m mapping_name -t sequence_generator_name -s start_value -e end_value -i increment_by -c current_value Table 16-32 lists pmrep Updateseqgenvals options and arguments: Table 16-32. -t sequence_generator_name 444 Chapter 16: Using pmrep and pmrepagent . see “Sequence Generator Transformation” in the Transformation Guide. However.Updating Sequence Generator Transformations (Updateseqgenvals) The Updateseqgenvals command updates one or more of the following properties for the specified Sequence Generator transformation: ♦ ♦ ♦ ♦ Start Value End Value Increment By Current Value You might want to update sequence values when you move a mapping from a development environment to a production environment.

If you select Cycle in the transformation properties. You must connect to a repository to use this command. pmrep gives an error message and does not update the Sequence Generator transformation. Enter the value you want the PowerCenter Server to use as the first value in the sequence. You can update the owner name for one or all sources in a session. pmrep gives an error message and does not update the Sequence Generator transformation. it fails the session. Updatesrcprefix updates the owner name for source tables at the session level. the current value must be greater than or equal to the start value and less than the end value. To update source table owner names. The difference between two consecutive values from the NEXTVAL port. pmrep gives an error message and does not update the Sequence Generator transformation. If you designate an invalid value. If you designate an invalid value. The maximum value the PowerCenter Server generates. If you designate an invalid value.Table 16-32. If the PowerCenter Server reaches this value during the session and the sequence is not configured to cycle. pmrep updates source table owner names only if you previously edited the source table name in the session properties. -e Optional end_value -i Optional increment_by -c Optional current_value Updating the Source Table Owner Name (Updatesrcprefix) Use the Updatesrcprefix command to update the owner name for session source tables. If you want to cycle through a series of values. The current value of the sequence. the PowerCenter Server cycles back to this value when it reaches the end value. pmrep gives an error message and does not update the Sequence Generator transformation. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Workflow Manager privilege with write permission on the folder Super User privilege pmrep Repository Commands 445 . If you designate an invalid value. Updateseqgenvals Options and Arguments (pmrep) Option -s Required/ Optional Optional Argument Name start_value Argument Description The start value of the generated sequence you want the PowerCenter Server to use if the Sequence Generator transformation uses the Cycle property.

pmrep matches the source_name argument with the source table names. -t Optional source_name -p -n Required Optional prefix_name n/a Updating Server Variables (Updatesrvvar) The Updatesrvvar command updates the value of the specified server variable. specify session_name. This option has no argument.session_name or workflow_name. .session_name. You can find the source dbd name in the Designer Navigator. you must also specify the session path. When you include this option. Updatesrvvar uses the following command syntax: updatesrvvar -s server_name -v variable_name -u new_value 446 Chapter 16: Using pmrep and pmrepagent . The name of the session containing the sources to update.When you include the -n option. you must enter the dbd name and the source table name as dbd_name. pmrep matches the source_name argument with source instance names.source_name.When you omit the -n option. but you can change the case of the default server variables. For reusable sessions. see “Configuring the Workflow Manager” in the Workflow Administration Guide. Informatica recommends you include the -n option. such as worklet_name. Updatesrcprefix Options and Arguments (pmrep) Option -f -s Required/ Optional Required Required Argument Name folder_name session_name Argument Description The name of the folder containing the session. The Designer generates the dbd name from the source type or data source name when you create a source definition in the repository. pmrep updates all source table owner names in the session. If you omit this option. For non-reusable sessions. . The owner name you want to update in the source table.Updatesrcprefix uses the following command syntax: Updatesrcprefix -f folder_name -s session_name -t source_name -p prefix_name -n Table 16-33 lists the pmrep Updatesrcprefix options and arguments: Table 16-33. You can update any of the PowerCenter Server variables using Updatesrvvar. The name of the source to update. For a list of server variables. When you do not include this option. This command requires you to connect to a repository. You cannot change default server variables. enter the name of the source instance as displayed in the session properties or as output by the Listtablesbysess command.

pmrep updates table name prefixes if you previously edited the table name prefix at the session level. Name of the server variable to update. Updatetargprefix updates the target table name prefix at the session level. The command returns “updatestatistics successfully completed” or returns “updatestatistics failed” message. To update repository statistics. You can update the owner name for one or all targets specified in a session. Updatesrvvar Options and Arguments (pmrep) Option -s -v -u Required/ Optional Required Required Required Argument Name server_name variable_name new_value Argument Description Name of the PowerCenter Server. Updatestatistics Options and Arguments (pmrep) Option -s Required/ Optional Optional Argument Name tables-to-skip_file_name Argument Description The name of the file that contains a list of repository tables to skip during update. Value of updated server variable. Updating Repository Statistics (UpdateStatistics) The UpdateStatistics command updates statistics for repository tables and indexes. The table name prefix specifies the owner of the table in the database. The update fails if you do not have Administer Repository privilege. see “Updating Repository Statistics” on page 60. For more information about updating statistics.Table 16-34 lists pmrep Updatesrvvar options and arguments: Table 16-34. You must connect to a repository to use this command. pmrep Repository Commands 447 . you must have Administer Repository privilege. UpdateStatistics uses the following command syntax: updatestatistics -s tables-to-skip_file_name Table 16-35 lists pmrep Updatestatistics options and arguments: Table 16-35. Updating the Target Table Name Prefix (Updatetargprefix) Use the Updatetargprefix command to update the table name prefix for session target tables.

The name of the session containing the targets to update. pmrep matches the target_name argument with the target table names. The table name prefix you want to update in the target table. When you include this option.session_name or workflow_name. specify session_name. If you omit this option. For non-reusable sessions. you must also specify the session path. The name of the target to update. When you omit the -n option.session_name. When you include the -n option. -t Optional target_name -p -n Required Optional prefix_name n/a 448 Chapter 16: Using pmrep and pmrepagent . you must have one of the following sets of privileges and permissions: ♦ ♦ Use Workflow Manager privilege with write permission on the folder Super User privilege Updatetargprefix uses the following command syntax: Updatetargprefix -f folder_name -s session_name -t target_name -p prefix_name -n Table 16-36 lists the pmrep Updatetargprefix options and arguments: Table 16-36. Informatica recommends you include the -n option. such as worklet_name. enter the name of the target instance as displayed in the session properties or as output by the Listtablesbysess command. When you do not include this option.To update target table name prefixes. Updatetargprefix Options and Arguments (pmrep) Option -f -s Required/ Optional Required Required Argument Name folder_name session_name Argument Description The name of the folder containing the session. This option has no argument. For reusable sessions. you must enter the target table name instead of the target instance name. pmrep updates all target table name prefixes in the session. pmrep matches the target_name argument with target instance names.

Removes a group from the repository. Lists all users registered with the repository. Deletes a folder. Creates a new folder. See “Deleting a Folder (DeleteFolder)” on page 453. See “Listing All Groups (Listallgroups)” on page 455. Lists all groups registered with the repository. See “Removing a User (Rmuser)” on page 458. See “Removing a Group (Rmgroup)” on page 457. Removes a privilege from a user or group. Registers a user from an external directory service to access the Repository. Edits the profile of a user. Table 16-37 describes commands you use to perform repository security tasks: Table 16-37. See “Creating a Group (Creategroup)” on page 452. See “Adding a Privilege (Addprivilege)” on page 450. pmrep Security Commands pmrep Command Addprivilege Addusertogroup Changepasswd CreateFolder Creategroup Createuser DeleteFolder Edituser Listallgroups Listallprivileges Listallusers ModifyFolder Registeruser Rmgroup Rmprivilege Rmuser Rmuserfromgroup Command Description Adds a privilege to a user or group. See “Modify Folder Properties (ModifyFolder)” on page 456. See “Editing a User (Edituser)” on page 454. You must have the Administer Repository privilege to use pmrep repository security commands. Lists all privileges that you can assign to a user or group. See “Creating a Folder (CreateFolder)” on page 451. See “Adding a User to a Group (Addusertogroup)” on page 450. Removes a user from a group. Creates a user. Changes the password for the user currently connected to the repository. See “Changing the Repository Password (Changepasswd)” on page 450. See “Listing All Users (Listallusers)” on page 455. Adds a user to a group.pmrep Security Commands pmrep allows you to perform security tasks for users and groups. Modifies folder properties. See “Listing All Privileges (Listallprivileges)” on page 455. See “Creating a User (Createuser)” on page 452. Creates a group. See “Removing a Privilege (Rmprivilege)” on page 458. See “Registering a User (Registeruser)” on page 457. pmrep Security Commands 449 . See “Removing a User from a Group (Rmuserfromgroup)” on page 459. Removes a user from the repository.

Addprivilege Options and Arguments (pmrep) Option -p Required/ Optional Required Argument Name privilege Argument Description The privilege you want to add. You must be connected to the repository to use this command. To add a user to a group. such as “Administer Repository. all users in the group inherit the privilege. If you add a privilege to a group. you cannot use the -g option. use the following syntax: addusertogroup -u username -g group_name Table 16-39 lists pmrep Addusertogroup options and arguments: Table 16-39. Changing the Repository Password (Changepasswd) The Changepasswd command changes the password of the user currently connected to the repository. The name of the group to which you want to add the privilege. you must enclose this argument in quotes. -u -g Required Required username group_name Adding a User to a Group (Addusertogroup) The Addusertogroup commands adds an existing user to a group. You must connect to the repository to use this command. You must connect to the repository to use this command. If you use this option. To add a privilege to a user or a group. If the privilege contains spaces. If you use this option. The name of the group to which you want to add the user. 450 Chapter 16: Using pmrep and pmrepagent . The user inherits all of the permissions and privileges associated with the group. use the following syntax: addprivilege -p privilege -u username -g group_name Table 16-38 lists pmrep Addprivilege options and arguments: Table 16-38. Addusertogroup Options and Arguments (pmrep) Option -u -g Required/ Optional Required Required Argument Name username group_name Argument Description The user name of the user to add to the group. Note: You cannot use this command with an external security module. It cannot add a privilege to a user and a group at the same time.” The name of the user to whom you want to add the privilege.Adding a Privilege (Addprivilege) The Addprivilege command adds a privilege to a user or group. you cannot use the -u option.

pmrep Security Commands 451 . To run CreateFolder. Only groups to which the owner belongs can be selected. you must use the -c option. Access rights for the folder. When you use this option. The password environment variable that replaces the existing password for the current user. Any user in the repository can be the folder owner. You must use this option when you use the -p option. This option confirms the new password. but not both. Changepasswd Options and Arguments (pmrep) Option -p Required/ Optional Required/ Optional Argument Name new_password Argument Description The password that replaces the existing password for the current user. do not use the -c option. Use the -p or -P option. but not both. When you use this option. If not specified. If selected. you must have Administer Repository privilege. The confirm_new_password argument must match the new_password argument. Repository user group to receive Owner’s Group permissions. Description of the folder that appears in the Repository Manager. Use the -p or -P option. The owner of the folder. CreateFolder uses the following command syntax: Createfolder -n folder_name -d folder_description -o owner_name -g group_name -s shared_folder -p permissions Table 16-41 lists CreateFolder options and arguments: Table 16-41. Repository Server assigns default permissions.To change the password of the user connected to the repository. CreateFolder Options and Arguments (pmrep) Option -n -d -o -g -s -p Required/ Optional Required Optional Optional Optional Optional Optional Argument Name folder_name folder_description owner_name group_name shared_folder permissions Argument Description Folder name. use the following syntax: changepasswd -p new_password -c confirm_new_password -P new_password_environment_variable Table 16-40 lists pmrep Changepasswd options and arguments: Table 16-40. The default owner is the user creating the folder. makes the folder shared. -c Required/ Optional confirm_new_password -P Required/ Optional new_password_environ ment_variable Creating a Folder (CreateFolder) The CreateFolder command creates a new folder in the repository.

If you create a user that has the same name as a user already registered with the repository. Creategroup Options and Arguments (pmrep) Option -g -d Required/ Optional Required Optional Argument Name group_name description Argument Description The name of the group you want to create. To create a group. use the following syntax: creategroup -g group_name -d description Table 16-42 lists pmrep Creategroup options and arguments: Table 16-42. if you want to assign default permissions. write. you specify 4. The command returns “createfolder successfully completed” or returns “createfolder failed” message. Each permission is associated with a number. and repository permissions by giving three digits when you use the -p option. Creating a Group (Creategroup) The Creategroup command adds a new group to the repository. The owner does not exist or does not belong to the group. The description of the group you want to create. 2 for write permission. 1. and 1 for execute permission. 2. The owner’s group has read and write permissions (6 = 4+2). you use the following command syntax: -p 764 This gives the folder owner read. group. or the sum of any of those numbers. Designate 4 for read permission. To assign permissions. The folder already exists. pmrep returns an error message. pmrep creates the group with the default permissions and privileges assigned to the Public group. The creation might fail for the following reasons: ♦ ♦ ♦ You do not have Administer Repository privilege. For example. Note: You cannot use this command if the repository is using an external security module. A valid user name has no spaces and is case-sensitive. You must connect to the repository before using this command. the second corresponds to the permissions of the group that the user belongs to. Specify one number for each set of permissions. All others have read permission. and execute permissions (7 = 4+2+1). 452 Chapter 16: Using pmrep and pmrepagent . and the third corresponds to all other permissions. The first digit corresponds to owner permissions.Assigning Permissions You can assign owner. Creating a User (Createuser) The Createuser command adds a new user to the repository.

The new user inherits all permissions and privileges granted to the group. The password is case-sensitive and cannot contain spaces. The group assigned to the new user. Use the -p or -P option. pmrep returns an error and does not carry out the command. The confirm_password argument must match the password argument. you must have Administer Repository privilege. DeleteFolder Options and Arguments (pmrep) Option -n Required/ Optional Required Argument Name folder_name Argument Description The name of the folder. pmrep Security Commands 453 . You must use this option when you use the -p option. -c Required/ Optional Required/ Optional confirm_password -P new_password_en vironment_variable -d -g Optional Optional description group_name If you specify a group that does not exist. The password of the new user. Use the -p or -P option. you add the user to the Public group. To delete a folder. do not use the -c option. If you do not specify a group. Createuser Options and Arguments (pmrep) Option -u -p Required/ Optional Required Required/ Optional Argument Name username password Argument Description User name of the new user. Deleting a Folder (DeleteFolder) The DeleteFolder command deletes an existing folder from the repository. use the following syntax: deletefolder -n folder_name Table 16-44 lists DeleteFolder option and argument: Table 16-44. but not both. A description of the new user. you must use the -c option. The password is case-sensitive and cannot contain spaces. This option ensures you enter the correct password. To delete a folder. The user name is case-sensitive and cannot contain spaces. but not both. The password environment variable of the new user. use the following syntax: createuser -u username -p password -c confirm_password -P new_password_environment_variable -d description -g group_name Table 16-43 lists pmrep Createuser options and arguments: Table 16-43. When you use this option. When you use this option. pmrep assigns the new user to the Public group. If you do not specify a group for the new user.To create a new user.

The folder does not exist. You can use this option if you are using native authentication security. Otherwise the command fails. -c Required/ Optional confirm_new_password -P Required/ Optional new_password_ environment_variable -d Optional description 454 Chapter 16: Using pmrep and pmrepagent . password. Replace the password of the user currently connected to the repository. Otherwise the command fails. You can use this option if you are using native authentication security. The new password environment variable to replace the password of the user currently connected to the repository. you must use the -c option. do not use the -c option. You can also disable or enable users. and description of the user currently connected to the repository.The command returns “DeleteFolder successfully completed” or returns “DeleteFolder failed. use the following syntax: edituser -u username -p new_password -c confirm_new_password -P new_password_environment_variable -d description -l login_name -e Table 16-45 lists pmrep Edituser options and arguments: Table 16-45. you must also use the -c option. Edituser Options and Arguments (pmrep) Option -u -p Required/ Optional Required Required/ Optional Argument Name username new_password Argument Description Replace the user name of the user currently connected to the repository. If you use the -p option with this command. When you use this option. Update the description of the user currently connected to the repository. Use the -p or -P option. but not both. This option ensures you enter the correct password.” The deletion might fail for the following reasons: ♦ ♦ ♦ You do not have Administer Repository privilege. The confirm_new_password argument must match the new_password argument. Use the -p or -P option. This command requires you to connect to the repository. The folder is being used by another user. Editing a User (Edituser) The Edituser command edits the user name. but not both. When you use this option. To edit the profile of the user currently connected to the repository.

Table 16-45. use the following syntax: listallgroups Listing All Privileges (Listallprivileges) The Listallprivileges command lists all valid repository privileges for users or groups. if you use LDAP to authenticate users in the repository. Use the no argument to disable a user. edituser -u JSmith -l JohnS -e yes The command associates his repository user name. Use the list of privileges to provide the privilege argument when adding or removing a privilege with pmrep. You must connect to the repository before using this command. To enable a user and specify a login name. use the -l option with this option. To list all repository privileges. Listing All Groups (Listallgroups) The Listallgroups command lists all groups registered with the repository by name. To list all users registered to the repository. use the following syntax: listallusers pmrep Security Commands 455 . Edituser Options and Arguments (pmrep) Option -l -e Required/ Optional Optional Optional Argument Name login_name n/a Argument Description Specifies a login to which to map the user name. JSmith with the external login name of JohnS and enables him to use the repository. For example. You can enter a yes or no argument. You can use this option only with an external directory service. you could use the following pmrep command to enable a user called JSmith. To list all groups registered to the repository. Enables or disables a user. You must connect to the repository before using this command. use the following syntax: listallprivileges Listing All Users (Listallusers) The Listallusers command lists all user names registered with the repository.

The default owner is the current user.Modify Folder Properties (ModifyFolder) The ModifyFolder command modifies folder properties. and the third corresponds to all other permissions. and execute permissions (7 = 4+2+1). and 1 for execute permission. If selected. or the sum of any of those numbers. 2. If not specified. For example. To assign permissions. you specify 4. if you want to assign default permissions. 456 Chapter 16: Using pmrep and pmrepagent . use the following syntax: modifyfolder -n folder_name -d folder_description -o owner_name -g group_name -s shared_folder -r new_folder_name -p permissions Table 16-46 lists the ModifyFolder options and arguments: Table 16-46. Rename the folder. Any user in the repository can be the folder owner. use the following command syntax: -p 764 This gives the folder owner read. The first digit corresponds to owner permissions. Specify one number for each set of permissions. All others have read permission. To modify a folder. Repository Server uses existing permissions. you must have Administer Repository privilege or be the folder owner. The current owner of the folder. -g Optional group_name -s -r -p Optional Optional Optional shared_folder new_folder_name permissions Assigning Permissions You can assign owner. Each permission is associated with a number. write. Description of the folder that appears in the Repository Manager. makes the folder shared. 2 for write permission. 1. and repository permissions by giving three digits when you use the -p option. To modify a folder. Access rights for the folder. Only groups to which the owner belongs can be selected. group. Designate 4 for read permission. the second corresponds to the permissions of the group that the user belongs to. ModifyFolder Option and Argument (pmrep) Option -n -d -o Required/ Optional Required Optional Optional Argument Name folder_name folder_description owner_name Argument Description Folder name. Repository user group to receive Owner’s Group permissions. The owner’s group has read and write permissions (6 = 4+2).

Assigns the user to a group. The modification might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have the appropriate privilege. The new owner does not exist or does not belong to the group. Registering a User (Registeruser) Use the Registeruser command to register a login from an external directory service and associate it with a repository user name. Note: You cannot remove the Public or Administrators group. The folder does not exist. Registeruser uses the following syntax: registeruser -u repository_user_name -l external_login -d description -g group_name -i contact_info Table 16-47 lists the pmrep Registeruser options and argument: Table 16-47.The command returns “ModifyFolder successfully completed” or returns “ModifyFolder Failed” message. A description of the user. When you remove a group. If any user in the group is connected to the repository when you remove the group. Use this command if you use LDAP to authenticate repository users. Contact information about the user. The login name in the external directory. A folder with the new folder name already exists. You must connect to the repository to use this command. Registeruser Option and Argument (pmrep) Option -u -l -d -g -i Required/ Optional Required Required Optional Optional Optional Argument Name repository_user_name external_login description group_name contact_info Argument Description The name to add as a repository user. use the following syntax: rmgroup -g group_name pmrep Security Commands 457 . If you omit this option. the user is assigned to Public. To remove a group. Removing a Group (Rmgroup) The Rmgroup command removes a group from the repository and reassigns all users in that group to the Public group. the privilege changes take effect the next time the user connects to the repository. users in the group lose the privileges inherited from the group.

To remove a user. Rmprivilege Options and Arguments (pmrep) Option -p Required/ Optional Required Argument Name privilege Argument Description The privilege you want to remove. If you use this option. such as “Administer Repository. If the user or users in the group are connected to the repository when you remove the privilege. use the following syntax: rmuser -u username 458 Chapter 16: Using pmrep and pmrepagent . The name of the group from which you want to remove the privilege. depending on the type of user authentication you use. you must enclose this argument in quotes. Rmgroup Option and Argument (pmrep) Option -g Required/ Optional Required Argument Name group_name Argument Description The name of the group you want to remove. you cannot use the -u option. use the following syntax: rmprivilege -p privilege -u username -g group_name Table 16-49 lists pmrep Rmprivilege options and arguments: Table 16-49. You cannot remove the Administrator user name from the repository. If you remove a user while the user is connected to the repository. If the privilege contains spaces. If you use this option. -u -g Required Required username group_name Removing a User (Rmuser) The Rmuser command removes a user from the repository or from the user name-login mapping. You must connect to a repository to use this command.Table 16-48 lists the pmrep Rmgroup option and argument: Table 16-48. you cannot use the -g option. the change takes effect the next time the user connects to the repository. To remove a privilege. the removal takes effect after the user disconnects from the repository. Removing a Privilege (Rmprivilege) The Rmprivilege command removes a privilege from a user or group. You cannot remove a privilege from a user and a group at the same time.” The name of the user from whom you want to remove the privilege. You must connect to the repository to use this command.

Removing a User from a Group (Rmuserfromgroup) The Rmuserfromgroup command removes an existing user from a group. To remove a user from a group. The user loses permissions and privileges associated with the group. the change takes effect the next time the user connects to the repository. use the following syntax: rmuserfromgroup -u username -g group_name Table 16-51 lists pmrep Rmuserfromgroup options and arguments: Table 16-51. Rmuser Option and Argument (pmrep) Option -u Required/ Optional Required Argument Name username Argument Description User name you want to remove from the repository. You must be connected to the repository to use this command. The name of the group from which to remove the user.Table 16-50 lists the pmrep Rmuser option and argument: Table 16-50. If the user is connected to the repository when you remove the user from a group. Rmuserfromgroup Options and Arguments (pmrep) Option -u -g Required/ Optional Required Required Argument Name username group_name Argument Description User name to remove from the group. pmrep Security Commands 459 .

Validates objects. See “Adding to a Deployment Group (AddToDeploymentGroup)” on page 461. checking objects in and out. See “Executing a Query (ExecuteQuery)” on page 470.pmrep Change Management Commands pmrep allows you to perform change management tasks such as deploying objects. See “Listing Checked Out Items (FindCheckout)” on page 472. See “Clearing a Deployment Group (ClearDeploymentGroup)” on page 465. Creates a label object. See “Validating Objects (Validate)” on page 474. Deploys a folder. running queries. and applying labels. See “Deploying a Folder (DeployFolder)” on page 469. Prints a list of checked out objects in the repository. Applies a label to an object or set of objects in a folder. Copies a deployment group. Checks in an object. See “Undoing a Checkout (UndoCheckout)” on page 473. Deletes a label object and all object references to the label. See “Deleting a Label (DeleteLabel)” on page 467. pmrep Change Management Commands pmrep Command AddToDeploymentGroup ApplyLabel Checkin ClearDeploymentGroup CreateDeployment Group CreateLabel DeleteDeploymentGroup DeleteLabel DeployDeploymentGroup DeployFolder ExecuteQuery FindCheckout UndoCheckout Validate Command Description Adds objects to a deployment group. Undoes an object check out. See “Deleting a Deployment Group (DeleteDeploymentGroup)” on page 466. Clears all objects from a deployment group. See “Labeling (ApplyLabel)” on page 462. Executes a query. 460 Chapter 16: Using pmrep and pmrepagent . See “Checking In Objects (Checkin)” on page 464. Deletes a deployment group. Creates a deployment group. See “Deploying a Deployment Group (DeployDeploymentGroup)” on page 467. release the lock and revert to the last checked in version. See “Creating a Label (CreateLabel)” on page 466. Table 16-52 describes the pmrep change management tasks: Table 16-52. See “Creating a Deployment Group (CreateDeploymentGroup)” on page 465.

If AddToDeploymentGroup runs successfully. The type of object you are adding. If the command fails. You must use this parameter when you add a specific object. The name of the object you are adding to the deployment group. session configuration. scheduler. You can specify source. workflow. mapping. For valid subtypes. target. If you use a persistent input file. you must use a persistent input file that contains encoded object IDs. target. session. You cannot add checked out objects to a deployment group. Use AddToDeploymentGroup to add source. -o Required/ Optional object_type -t Required/ Optional object_subtype pmrep Change Management Commands 461 . You cannot specify a checked out object. You can specify objects using command options or you can use a persistent input file. scheduler. transformation. and dimension. AddToDeploymentGroup Options and Arguments (pmrep) Option -p -n Required/ Optional Required Required/ Optional Argument Name deployment_group_name object_name Argument Description The name of the deployment group to add objects to. worklet. transformation. workflow. If you want to add non-reusable input objects. see “Using the Persistent Input File” on page 494. you can specify only the deployment group name option. it displays the reason for failure. Use AddToDeployment Group to add reusable input objects. For more information on adding to a deployment group. session configuration. For more information on using a persistent input file.Adding to a Deployment Group (AddToDeploymentGroup) The AddToDeploymentGroup command adds objects to a deployment group. cube. it either sends back no status information. The type of task or transformation you are adding. mapping. task. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager privilege Write permission on the folder AddToDeploymentGroup uses the following command syntax: AddToDeploymentGroup -p deployment_group_name -n object_name -o object_type -t object_subtype -v version_number -f folder_name -i persistent_input_file -d dependency_types Table 16-53 lists pmrep AddToDeploymentGroup options and arguments: Table 16-53. worklet. session. or it returns a list of objects that already are in the deployment group. To add objects to a deployment group. and task objects. You cannot specify an object if you use the -i option. see Table 16-16 on page 426. Required when adding a specific object. see “Working with Deployment Groups” on page 236.

The dependent objects to add to the deployment group with the object. pmrep labels all dependent objects. You must specify the folder if you specify an object name. pmrep displays either no status information or a list of objects that already have the label. If you use the dependent_object_type option. You can apply the label to dependent objects. see “Applying Labels” on page 221. or ListObjectDependencies that contains a list of object records with encoded IDs. You can specify “non-reusable” or “all. reusable and non-reusable. For more information on using a persistent input file. If ApplyLabel succeeds. see “Using the Persistent Input File” on page 494. -f -i Required/ Optional Optional folder_name persistent_input_file -d Optional dependency_types Labeling (ApplyLabel) Use the ApplyLabel command to apply a label to an object or a set of objects in a folder. and -f options. Use ApplyLabel to label reusable input objects. To apply a label to selected dependent objects. Validate. A text file generated from ExecuteQuery. The folder that contains the object you are adding. The default is to add the latest version of the object to the deployment group. If you specify a folder. If you use this parameter. To label objects. If the command fails. see “Using the Persistent Input File” on page 494. all the objects in the folder receive the label. to the deployment group. you must have the following privileges and permissions: ♦ ♦ ♦ Use Repository Manager privilege Read permission on the folder Execute permission on the label 462 Chapter 16: Using pmrep and pmrepagent . AddToDeploymentGroup Options and Arguments (pmrep) Option -v Required/ Optional Optional Argument Name version_number Argument Description The version of the object to add. pmrep adds the object(s) and all dependent objects. If you omit this parameter. If you specify “all”. pmrep does not allow the -n. -o. separate each object type name by a comma with no spaces between them on the command line. If you want to label non-reusable input objects. For more information on applying labels.” If you specify “non-reusable” pmrep adds the object(s) and the corresponding non-reusable dependent objects to the deployment group.Table 16-53. For more information about using a persistent input file. then you do not add dependent objects to the deployment group. pmrep displays the failure reason. you must use a persistent input file that contains encoded object IDs.

session config. or folder name to specify objects. The dependent parents or children to apply the label to. scheduler. -o Required/ Optional object_type -t Required object_subtype -v Optional version_number -f Optional folder_name -i Optional persistent_input_file -d Required dependent_object_type -p Optional dependency_direction pmrep Change Management Commands 463 . If you do not specify this option. For more information on using the persistent input file. or dimension. If you use this option. pmrep applies the label to all objects in the folder. You can specify parents. You can specify source. ListObjectDependency. The version of the object to apply the label to. Applies the label to the latest version of the object by default. The command fails if the version is checked out. cube. For valid subtypes. The folder that contains the object(s). If you specify an object type. or Validate. pmrep ignores other object types. but no object name. Contains a list of objects to receive the label. then do not use the object name. then this parameter is required. ApplyLabel Options and Arguments (pmrep) Option -a -n Required/ Optional Required Required/ Optional Argument Name label_name object_name Argument Description The label name to apply to the object. If you do not specify option -d. The kind of task or transformation you are labeling. The name of a text file generated from ExecuteQuery. Use this option with option -p. then the label applies to dependent objects of that object type. target. The name of the object to receive the label. all dependent objects receive the label. see Table 16-16 on page 426. mapping. If you specify a folder with an object name. The dependent objects to label. If you are updating a specific object. object type.ApplyLabel uses the following command syntax: ApplyLabel -a label_name -n object_name -o object_type -t object_subtype -v version_number -f folder_name -i persistent_input_file -d dependent_object_type -p dependency_direction -s include_pk-fk_dependency -m move_label -c comments Table 16-54 lists pmrep ApplyLabel options and arguments: Table 16-54. task. pmrep searches the folder for the object. transformation. worklet. session. If you specify a folder. The type of object to apply the label to. the label applies only to the specified object. You cannot specify a folder if you use the -i option. both. Required when applying a label to a specific object. workflow. You cannot specify objects if you use the -i option. children. see “Using the Persistent Input File” on page 494.

The type of task or transformation to check in. workflow. cube. To check in objects. task. See “Creating a Label (CreateLabel)” on page 466. Move a label from the current version to the latest version of an object. The version number is one number greater than the version number of the last checked-in version. scheduler.Table 16-54. mapping. Comments relating to ApplyLabel. -t Optional object_subtype -n -f -c Required Required Optional object_name folder_name comments 464 Chapter 16: Using pmrep and pmrepagent . Table 16-55 lists pmrep Checkin options and arguments: Table 16-55. You can use this argument only when the label type is one_per_object. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Repository Manager privilege and write permission on the folder Administer Repository privilege and write permission on the folder Checkin uses the following command syntax: Checkin -o object_type -t object_subtype -n object_name -f folder_name -c comments Users with Administer Repository privilege can check in objects for other users. Comments about the check in. target. Not required for other object types. session. Checkin Options and Arguments (pmrep) Option -o Required/ Optional Required Argument Name object_type Argument Description The type of object you are checking in: source. The name of the object that you are checking in. ApplyLabel Options and Arguments (pmrep) Option -s -m Required/ Optional Optional Optional Argument Name include_pk-fk_dependency move_label Argument Description Include the primary key-foreign key dependency objects regardless of the direction of the dependency. The folder to contain the new object version. For more information on checking in objects. worklet. When you check in an object. For valid subtypes. the repository creates a new version of the object and assigns it a version number. see “Checking In Objects” on page 213. or dimension. see Table 16-16 on page 426. transformation. -c Optional comments Checking In Objects (Checkin) Use the Checkin command to check in an object that you have checked out previously. session config.

To create a deployment group. Default is static. pmrep Change Management Commands 465 . You can create a dynamic or static deployment group. CreateDeploymentGroup uses the following command syntax: CreateDeploymentGroup -p deployment_group_name -t group_type -q query_name -u query_type -c comments Table 16-57 lists pmrep CreateDeploymentGroup options and arguments: Table 16-57. you must have the Use Repository Manager privilege. To clear a deployment group. and indicate whether the query is private or public. you must supply a query name. Create a static group or use a query to dynamically create the group. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager privilege Read and write permission on the deployment group ClearDeploymentGroup uses the following command syntax: ClearDeploymentGroup -p deployment_group_name -f force_delete Table 16-56 lists ClearDeploymentGroup options and arguments: Table 16-56. You can use this command to retain the deployment group but remove the objects. To create a dynamic deployment group. the command prompts you for a confirmation before it clears the objects. CreateDeploymentGroup Options and Arguments (pmrep) Option -p -t Required/ Optional Required Optional Argument Name deployment_group_name group_type Argument Description The name of the deployment group to create. For more information on creating deployment groups. Creating a Deployment Group (CreateDeploymentGroup) Use the CreateDeploymentGroup command to create a deployment group. see “Working with Deployment Groups” on page 236.Clearing a Deployment Group (ClearDeploymentGroup) Use the ClearDeploymentGroup command to clear all objects from a deployment group. ClearDeploymentGroup Options and Arguments (pmrep) Option -p -f Required/ Optional Required Optional Argument Name deployment_group_name force_delete Argument Description The name of the deployment group that you want to clear. You can specify static or dynamic. Remove objects without confirmation. If you omit this argument.

If you delete a static deployment group. CreateDeploymentGroup Options and Arguments (pmrep) Option -q Required/ Optional Required Argument Name query_name Argument Description The name of the query associated with the deployment group. CreateLabel uses the following command syntax: CreateLabel -a label_name -t label_type -c comments Table 16-58 lists pmrep CreateLabel options and arguments: Table 16-58. Comments about the label. you can apply the label to only one version. CreateLabel Options and Arguments (pmrep) Option -a -t Required/ Optional Required Optional Argument Name label_name label_type Argument Description The name of the label you are creating. or you can specify that a label can apply to only one version of an object (one per object). Required if the deployment group is dynamic. For more information on deleting deployment groups. You can associate a label with any versioned object or group of objects in a repository. The type of query to create a deployment group. you must have the Administer Repository privilege. When you create a label. but ignored if the group is static. -c Optional n/a Deleting a Deployment Group (DeleteDeploymentGroup) Use the DeleteDeploymentGroup command to delete a deployment group. -u Required query_type -c Optional comments Creating a Label (CreateLabel) Use the CreateLabel command to create a label that you can use to associate groups of objects during development. You can specify shared or personal. Allows multiple versions to have this label. For more information on creating labels. you also remove all objects from the deployment group. see “Creating and Editing Labels” on page 219.Table 16-57. If you omit this option. see “Working with Deployment Groups” on page 236. but ignored if the group is static. Required if the deployment group is dynamic. you can specify that the label can apply to multiple versions of an object (one per version). To create a label. Comments about the new deployment group. 466 Chapter 16: Using pmrep and pmrepagent .

DeleteDeploymentGroup Options and Arguments (pmrep) Option -p -f Required/ Optional Required Optional Argument Name deployment_group_name force_delete Argument Description The name of the deployment group to delete. If the label is locked. Deletes the Deployment Group without confirmation. Deleting a Label (DeleteLabel) Use the DeleteLabel command to delete a label and remove the label from all objects that use it. pmrep Change Management Commands 467 . If you omit this argument. Deploying a Deployment Group (DeployDeploymentGroup) Use the DeployDeploymentGroup command to deploy a deployment group. DeleteLabel uses the following command syntax: DeleteLabel -a label_name -f force_delete Table 16-60 lists pmrep DeleteLabel options and arguments: Table 16-60. the command prompts you for a confirmation before it deletes the label. see “Working with Labels” on page 219. Delete the label without confirmation. you must have the following privileges and permissions: ♦ ♦ Administer Repository privilege Write permission on the label For more information about deleting labels. pmrep prompts you for a confirmation before it deletes the Deployment Group. DeleteLabel Options and Arguments (pmrep) Option -a -f Required/ Optional Required Optional Argument Name label_name force_delete Argument Description The name of the label to delete. If you omit this argument. you must have the following privileges and permissions: ♦ ♦ Administer Repository privilege Write permission on the deployment group DeleteDeploymentGroup uses the following command syntax: DeleteDeploymentGroup -p deployment_group_name -f force_delete Table 16-59 lists pmrep DeleteDeploymentGroup options and arguments: Table 16-59. You can optionally use this command to copy deployment groups to different repositories. To delete a label.To delete a deployment group. the delete fails.

but not both. see “Using the Deployment Control File” on page 504. Not required if you are copying the deployment group to the same repository. you must create a control file with all the specifications that the Copy Wizard requires. Not required if you copy the deployment group to the same repository. The login password environment variable for the target repository. The repository you are deploying the group to. Not required if you copy the deployment group to the same repository. you must have the following privileges and permissions: ♦ ♦ ♦ Administer Repository Manager privilege Read permission on the original folders Read and execute permissions on the deployment group DeployDeploymentGroup uses the following command syntax: DeployDeploymentGroup -p deployment_group_name -c control_file_name -r target_repository_name -u target_repository_user_name -x target_repository_user_password -X target_repository_password_environment_variable -h target_repository_server_host_name -n target_repository_server_port_number -l log_file_name Table 16-61 lists pmrep DeployDeploymentGroup options and arguments: Table 16-61. The control file is an XML file defined by the depcntl. To copy a deployment group. For more information on using the control file. Use the -x or -X option. The login password for the target repository. DeployDeploymentGroup Options and Arguments (pmrep) Option -p -c Required/ Optional Required Required Argument Name deployment_group_name control_file_name Argument Description The name of the group to deploy. -r -u Required Required/ Optional Required/ Optional target_repository_name target_repository_user_name -x target_repository_user_passwo rd -X Required/ Optional target_repository_password_en vironment_variable -h Required/ Optional target_repository_server_host_ name 468 Chapter 16: Using pmrep and pmrepagent . The login user name for the target repository. but not both. Use the -x or -X option. For more information on deploying a deployment group. Not required if you copy the deployment group to the same repository. The host name of the Repository Server managing the target repository.To use this command.dtd file. see “Using the Deployment Control File” on page 504. The control file is required. see “Copying a Deployment Group” on page 254. For more details about the control file. The name of the XML file containing the Copy Wizard specifications.

The login password for the target repository. Use the -x or -X option.dtd file. -r Optional target_repository_name -u Optional target_repository_user_name -x Required/ Optional target_repository_user_passwo rd pmrep Change Management Commands 469 . Not required if you are copying the deployment group to the same repository. It requires a control file containing specifications that the Copy Wizard requires. The control file is an XML file defined by the depcntl. -l Deploying a Folder (DeployFolder) The DeployFolder command allows you to deploy a folder. it outputs to the screen. DeployDeploymentGroup Options and Arguments (pmrep) Option -n Required/ Optional Required/ Optional Optional Argument Name target_repository_server_port_ number log_file_name Argument Description The port number of the Repository Server. For more details about the control file. see “Using the Deployment Control File” on page 504.Table 16-61. The login user name for the target repository. The name of the XML file containing the copy wizard specifications. The repository name to deploy the group to. DeployFolder Options and Arguments (pmrep) Option -f -c Required/ Optional Required Required Argument Name folder_name control_file_name Argument Description The name of the folder to deploy. Not required if you are copying the deployment group to the same repository. but not both. see “Using the Deployment Control File” on page 504. you must have the following privileges and permissions: ♦ ♦ Administer Repository privilege Read permission on the original folder DeployFolder uses the following command syntax: DeployFolder -f folder_name -c control_file_name -r target_repository_ name -u target_repository_user_name -x target_repository_user_password -X target_repository_password_environment_variable -h target_repository_server_host_name -n target_repository_server_port_ number -l log_file_name Table 16-62 lists pmrep DeployFolder options and arguments: Table 16-62. To copy a folder. For more information on the control file. The log file that records each deployment step. If you omit this option. Not required if the target repository is the same as the source. Not required if you are copying the deployment group to the same repository.

-h Optional target_repository_server_host_ name target_repository_server_port_ number log_file_name -n Optional -l Optional Executing a Query (ExecuteQuery) Use the ExecuteQuery command to run a query. You can specify public or private. Not required if you copy the deployment group to the same repository. You can use this file as input to the ApplyLabel. Use the -x or -X option. AddToDeploymentGroup. If not specified. The port number of the Repository Server. To execute a query. If you omit this option. The log file that records each deployment step. it returns the total number of qualifying records.Table 16-62. Not required if you are copying the deployment group to the same repository. You can choose to display the result or write the result to a persistent input file. If the query is successful. ExecuteQuery Options and Arguments (pmrep) Option -q -t Required/ Optional Required Optional Argument Name query_name query_type Argument Description The name of the query to run. 470 Chapter 16: Using pmrep and pmrepagent . Not required if you copy the deployment group to the same repository. For more details on using a persistent input file. but not both. The host name of the Repository Server managing the target repository. it outputs to the screen. you must have the following privileges and permissions: ♦ ♦ ♦ Browse Repository privilege Write permission on the folder Read and execute permissions on the query ExecuteQuery uses the following command syntax: ExecuteQuery -q query_name -t query_type -u persistent_output_file_name a append -c column_separator -r end-of-record_separator -l end-oflisting_indicator -b verbose Table 16-63 lists pmrep ExecuteQuery options and arguments: Table 16-63. DeployFolder Options and Arguments (pmrep) Option -X Required/ Optional Required/ Optional Argument Name target_repository_password_en vironment_variable Argument Description The login password environment variable for the target repository. Then it searches the public queries. pmrep searches all the private queries first to find the matching query name. see “Using the Persistent Input File” on page 494. and Validate commands. The type of query to run.

query type. The character or set of characters used to specify the end of the object list. pmrep overwrites the file content. deployment group. The character or set of characters used to specify the end of the object metadata. pmrep prints a shorter format including the object type. Verbose format includes the label type. pmrep uses a new line. deployment group type. Use a character or set of characters that is not used in repository object names. If you do not specify to append. and connection. and creation time. pmrep uses a period. the word reusable or non-reusable. Specify a character or set of characters that is not used in repository object_names. query. pmrep uses a single space. Verbose format includes the object status. Use a character or set of characters that is not used in repository object names. The character or set of characters used to separate object metadata columns. creator name. If you omit this option. version number. The short format for versioning objects such as label. If you do not specify a file name. includes the object type and object name.Table 16-63. ExecuteQuery Options and Arguments (pmrep) Option -u -a Required/ Optional Optional Optional Argument Name persistent_output_file_name append Argument Description Send the query result to a text file. The option to append the query results to the persistent output file. you might want to avoid using a space as a column separator. and checked out information. Print more than the minimum information about the objects. the query result goes to stdout. If you omit this option. -c Optional column_separator -r Optional end-of-record_separator -l Optional end-of-listing_indicator -b Optional verbose pmrep Change Management Commands 471 . If any repository object name contains spaces. If you omit this option. the object name and path. folder name. If you omit this option.

The listing contains only your checked out items unless you specify “all users. FindCheckout Options and Arguments (pmrep) Option -o Required/ Optional Optional Argument Name object_type Argument Description The object type you want to list. Note: You can use FindCheckout with no options. For more information about finding checked out objects. you might want to avoid using a space as a column separator. workflow. Use a character or set of characters that is not used in repository object names. task. If you do not specify an object type. List the checked out objects by all users. or dimension. then you can list checked out objects in a specific folder or across all folders. target. session config. see “Checking Out and Checking In Objects” on page 211. The character or set of characters used to separate object metadata columns. Folder name is optional if you specify an object type. To list checked out items.Listing Checked Out Items (FindCheckout) Use the FindCheckout command to print a list of checked out objects in the repository. You can specify source. If any repository object name contains spaces. pmrep ignores the -f and -u options and the command returns all checked-out objects in the repository. The default is to list only checked out objects by the current user. mapping. -f Optional folder_name -u -c Optional Optional all_users column_separator 472 Chapter 16: Using pmrep and pmrepagent . scheduler. you must have the following privileges and permissions: ♦ ♦ Browse Repository privilege Read permission on the folder FindCheckout uses the following command syntax: FindCheckout -o object_type -f folder_name -u all_users -c column_ separator -r end-of-record_separator -l end-of-listing_indicator -b verbose Table 16-64 lists pmrep FindCheckout options and arguments: Table 16-64. If you omit this option. cube. pmrep uses a single space. If you omit object type. transformation.” If you choose an object type. Return a list of checked out objects for the object type in the specified folder. pmrep returns all the checked out objects in the repository. session. The default is to list objects for the object type across folders. worklet.

If you omit this option. The short format for versioning objects such as label. and connection. -l Optional end-of-listing_indicator -b Optional verbose Undoing a Checkout (UndoCheckout) Use the UndoCheckout command to undo a checkout of an object. Verbose format includes the version number and folder name. Print more than the minimum information about the objects. the repository releases the write-intent lock on the object and reverts to the most recently checked in version of the object. includes the object type and object name. pmrep prints a shorter format including the object type. To undo a checkout. Verbose format includes the creator name and creation time. FindCheckout Options and Arguments (pmrep) Option -r Required/ Optional Optional Argument Name end-of-record_separator Argument Description The character or set of characters used to specify the end of the object metadata. the object name and path. deployment group. query. the word reusable or non-reusable. UndoCheckout uses the following command syntax: UndoCheckout -o object_type -t object_subtype -n object_name -f folder_name pmrep Change Management Commands 473 . For details on undoing a checkout. When you undo a checkout. If you want to modify the object again. Use a character or set of characters that is not used in repository object names. or “Using the Workflow Manager” in the Workflow Administration Guide. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager or Administer Repository privilege Write permission on the folder Users with Administer Repository privilege can undo checkouts for other users. see “Using the Designer” in the Designer Guide. you must check it out. If you omit this option.Table 16-64. Use a character or set of characters that is not used in repository object names. The character or set of characters used to specify the end of the object list. pmrep uses a period. The default is newline /n.

transformation. You can validate the following types of objects: ♦ ♦ ♦ ♦ ♦ Mappings Mapplets Sessions Workflows Worklet objects If you use another type of object in the input parameter. invalid_before. UndoCheckout Options and Arguments (pmrep) Option -o Required/ Optional Required Argument Name object_type Argument Description The type of object. For valid subtypes. Objects saved after validation. workflow. You can specify source. pmrep reports an error and skips the object. You can choose to output the results to a persistent output file or standard output. invalid_after. dimension. invalid objects. The name of the checked out object. Objects invalid before the validation check. Objects that did not save because of lock conflicts or they were checked out by another user. The type of transformation or task. and skipped objects. If you use the wrong type of object in a persistent input file. skipped. -t -n -f Required/ Optional Required Required object_subtype object_name folder_name Validating Objects (Validate) The Validate command validates objects. pmrep returns an error. you can choose to output information about object status: ♦ ♦ ♦ ♦ ♦ ♦ valid. see Table 16-16 on page 426. Ignored for other object types. You can choose to save and check in the objects that change from invalid to valid. It also displays a validation summary to stdout. The persistent output file contains standard information. session config.Table 16-65 lists pmrep UndoCheckout options and arguments: Table 16-65. scheduler. The summary includes the number of valid objects. Note: The pmrep Validate command does not validate shortcuts. Objects successfully validated. and a CRC check. The name of the folder containing the object. When you run Validate. Shortcuts and object types that do not require validation. session. Objects invalid after the validation check. mapping. worklet. target. 474 Chapter 16: Using pmrep and pmrepagent . save_failed. encoded IDs. task. cube. saved.

save_failed. skipped. or -f arguments. saved. You cannot use this file if you are specifying objects using the -n. The default is the latest or checked out version of the object. session config. -t Required/ Optional Required Optional Optional object_subtype -f -v -i folder_name version_number persistent_input file -s -k -m Optional Optional Required/ Optional Optional save_upon_valid check_in_upon_valid check_in_comments -p output_options pmrep Change Management Commands 475 . Validate Options and Arguments (pmrep) Option -n -o Required/ Optional Required Required/ Optional Argument Name object_name object_type Argument Description The name of the object to validate. The type of object to validate. The name of the folder containing the object. Required if you are not using a persistent input file. target. workflow. For valid subtypes. and the current repository requires checkin comments. scheduler. Validate. Ignored for other object types. Contains a list of object records. You can specify valid. Check in saved objects. The kind of object you want to output to the persistent output file or stdout after validation. Save objects that change from invalid to valid to the repository. separate them by commas. invalid_before. worklet. The type of task or transformation. transformation. You can specify source. Do not use this option if you are using the -i argument.To validate objects. dimension. session. see Table 16-16 on page 426. Add comments when you check in an object. cube. Required if you use -s. To specify one or more options. -o. You should specify output_options when you use the persistent_output_file_name. or invalid_after. The text file from ExecuteQuery. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager privilege Write permission on the folder Validate uses the following command syntax: Validate -n object_name -o object_type -t object_subtype -f folder_name -v version_number -i persistent_input file -s save_upon_valid -k check_in_upon_valid -m check_in_comments -p output_options -u persistent_output_file_name -a append -c column_separator -r end-of-record_separator -l end-of-listing_indicator -b verbose Table 16-66 lists pmrep Validate options and arguments: Table 16-66. The version of the object to validate. or ListObjectDependencies commands. mapping. task. Required if you use the -k option.

query. the word reusable or non-reusable. pmrep uses a period. Use a character or set of characters that is not used in repository object names. The character or set of characters used to separate object metadata columns. Verbose format includes the version number and folder name. If you specify a file name. Validate Options and Arguments (pmrep) Option -u Required/ Optional Optional Argument Name persistent_output_file_name Argument Description The name of an output text file. Verbose format includes the creator name and creation time. If you omit this option. pmrep prints a shorter format including the object type. -a -c Optional Optional append column_separator -r Optional end-of-record_separator -l Optional end-of-listing_indicator -b Optional verbose 476 Chapter 16: Using pmrep and pmrepagent . Specify a character or set of characters that is not used in repository object names. If any repository object name contains spaces. Append the results to the persistent output file instead of overwriting it. deployment group. and connection. The character or set of characters used to specify the end of the object metadata. includes the object type and object name. If you omit this option. The short format for versioning objects such as label. The character or set of characters used to specify the end of the object list. You should also specify output_options. Use a character or set of characters that is not used in repository object names. the query writes the results to a file. you might want to avoid using a space as a column separator. Print more than the minimum information about the objects. If you omit this option. pmrep uses a single space.Table 16-66. the object name and path. The default is newline /n.

switch to the Repository Server \bin directory and enter pmrepagent followed by the command name and its required options and arguments. See “Upgrading a Repository (Upgrade)” on page 490. Creates repository tables in the database. Registers a new external module to the repository. Use this command when the repository is not running. See “Backing up a Repository (Backup)” on page 477. See “Deleting a Repository (Delete)” on page 481. You must provide the backup filename. See “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. See “Creating a Repository (Create)” on page 480. to perform repository functions such as restoring and deleting repositories. pmrepagent. pmrepagent runs in command line mode only. See “Restoring a Repository (Restore)” on page 485. See “Unregistering Plug-ins (Unregisterplugin)” on page 487. Table 16-67 describes pmrepagent commands: Table 16-67. Specify pmrepagent options and arguments the same way you specify pmrep options and arguments. pmrepagent Commands pmrepagent Command Backup Bulkrestore Create Delete Registerplugin Restore Unregisterplugin Upgrade Command Description Backs up a repository. Unregisters a plug-in module from the repository. Restores a Teradata repository from a repository backup file using Fastload. Backup uses the following command syntax: backup -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m trusted_connection -c database_connect_string -o output_file_name -d description -f -b skip_workflow/session_log -j skip_deploy_group_history -q skip_MX_data pmrepagent Commands 477 . See “Registering a Plug-in (Registerplugin)” on page 482. Deletes the repository tables from the database. Backing up a Repository (Backup) The Backup command backs up a repository to the file specified with the -o option. To run pmrepagent commands. Restores a repository from a repository backup file. Upgrades an existing repository to the latest version.pmrepagent Commands You can use the Repository Agent command line program.

Table 16-68 lists pmrepagent Backup options and arguments: Table 16-68. This option has no argument. see “Backing up a Repository (Backup)” on page 416. Use the -x or -X option. The repository database password. The repository password environment variable. 478 Chapter 16: Using pmrep and pmrepagent . The type of database the repository resides on. Use a trusted connection to connect to the database. Skips deployment group history during backup. Valid for Microsoft SQL Server only. The connect string the Repository Agent uses to connect to the repository database. For a list of connect string syntax. -P database_password_environ ment_variable trusted_connection database_connect_string -m -c -o -d -f -b -j -q Required Required Optional Optional Optional Optional output_file_name description n/a skip_workflow/session_log skip_deploy_group_history skip_MX_data Note: pmrep also allows you to back up a repository. Use the -p or -P option. but not both. but not both. Include this option if you want to overwrite any existing file with the same name. see Table 16-1 on page 405. You can use the pmrep Backup command when the repository is running. Backup Options and Arguments (pmrepagent) Option -r -n -x -X -t -u -p Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name repository_user_name repository_password repository_password_environ ment_variable database_type database_user_name database_password Argument Description The name of the repository you want to back up. The name and path of the file for the repository backup. but not both. Skips tables related to workflow and session logs during backup. The repository password. The description of the repository you backup. For details. Use the -p or -P option. but not both. Not required if you are using option -m. The repository database password. Use the -x or -X option. Not required if you are using option -m. The repository database user name. The repository user name. Skips tables related to MX data during backup.

Bulkrestore uses the following command syntax: bulkrestore -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string -d codepage -h host_name -o port_number -g -i backup_file_name -e external_loader_type -s server_name -a license_file_name -y enable_object_versioning -b skip_workflow/ session_log -j skip_deploy_group_history -q skip_MX_data Table 16-69 lists pmrepagent Bulkrestore options and arguments: Table 16-69. but not both. see Table 16-1 on page 405. If you do not specify a path. The name of the repository backup file. Use this option if you want to promote the repository to a global repository. The host name of the Repository Server that manages the repository. Enter “Teradata” to restore to a Teradata database. -d -h -o -g -i Optional Required Required Optional Required codepage host_name port_number n/a backup_file_name -e -s Required Required external_loader_type server_name pmrepagent Commands 479 . the Repository Server looks for the file in the Repository Server backup directory. The name of the Teradata database server. The connect string the Repository Agent uses to connect to the repository database. This option has no argument. For a list of connect string syntax.Restoring Teradata Repositories using Fastload (Bulkrestore) The pmrepagent Bulkrestore command restores Teradata repositories using Fastload. The repository code page. but not both. The repository database password. The repository database user name. Bulkrestore Options and Arguments (pmrepagent) Option -r -t -u -p -P -c Required/ Optional Required Required Required Required/ Optional Required/ Optional Required Argument Name repository_name database_type database_user_name database_password database_password_environ ment_variable database_connect_string Argument Description The name of the repository you want to restore. Use the -p or -P option. Enter “fastload” for Teradata. The repository database password environment variable. The port number of the Repository Server that manages the repository. You can specify any file name and path local to the Repository Server. The Bulkrestore command can be faster than the Restore command when the repository backup file is greater than 100 MB. Use the -p or -P option.

Skips tables related to workflow and session logs during backup. Before you can create a repository. but not both. Creating a Repository (Create) The pmrepagent Create command creates a repository in the database. The repository database password environment variable. Use the -p or -P option. Use a trusted connection to connect to the database. Not required if you are using option -m. Create Options and Arguments (pmrepagent) Option -r -t -u -p Required/ Optional Required Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name database_type database_user_name database_password Argument Description The name of the repository you want to create. Not required if you are using option -m. Enables object versioning. The connect string the Repository Agent uses to connect to the repository database. For a list of connect string syntax. Create uses the following command syntax: Create -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m -c database_connect_string -d code_page -h host_name -o port_number -g -v -a license_file_name -z repository_creation_parameters Table 16-70 lists pmrepagent Create options and arguments: Table 16-70. Skips deployment group history during backup. Valid for Microsoft SQL Server only. see Table 16-1 on page 405. see “Creating a Repository” on page 116. For more information on creating repositories. but not both. Use the -p or -P option. The type of database the repository resides on. -P database_password_environme nt_variable n/a database_connect_string -m -c 480 Chapter 16: Using pmrep and pmrepagent . Bulkrestore Options and Arguments (pmrepagent) Option -a -y -b -j -q Required/ Optional Required Optional Optional Optional Optional Argument Name license_file_name enable_object_versioning skip_workflow/session_log skip_deploy_group_history skip_MX_data Argument Description The name of the license file. you must create and configure the database to contain the repository. The repository database password. Skips tables related to MX data during backup. The repository database user name.Table 16-69.

-a -v Required Optional license_file_name n/a The name of the license file. This option has no argument. The repository user name. pmrepagent Commands 481 . Include this option if you want to enables object versioning for the repository. Delete Options and Arguments (pmrepagent) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_envir onment_variable Argument Description The name of the repository you want to delete. Deleting a Repository (Delete) The pmrepagent Delete command deletes the repository tables from the repository database. Use the -x or -X option. The port number of the Repository Server that manages the repository. pmrepagent interprets the spaces as part of the tablespace name. For more information about deleting a repository. Create Options and Arguments (pmrepagent) Option -d -h -o -g -z Required/ Optional Optional Required Required Optional Optional Argument Name code_page host_name port_number n/a repository_creation_parameters Argument Description The repository code page. but not both. Delete uses the following command syntax: Delete -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string -f Table 16-71 lists pmrepagent Delete options and arguments: Table 16-71. Use this option to specify the tablespace name for IBM DB2 EEE databases. but not both. see “Deleting a Repository” on page 64. The repository password environment variable. Use the following format to specify the tablespace name: “%tablespace=<tablespace_name>” Do not include spaces around the equals sign. Include this option if you want to promote the repository to a global repository. Use the -x or -X option. This option has no argument. The repository password.Table 16-70. The host name of the Repository Server that manages the repository.

Registering a plug-in adds its functionality to the repository. but not both. Delete Options and Arguments (pmrepagent) Option -t -u -p -P -c Required/ Optional Required Required Required/ Optional Required/ Optional Required Argument Name database_type database_user_name database_password database_password_enviro nment_variable database_connect_string Argument Description The type of database the repository resides on. The repository database password. Registerplugin Options and Arguments (pmrepagent) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_envir onment_variable Argument Description The name of the repository. The repository database password environment variable.Table 16-71. Use the -x or -X option. The repository password. For more information about registering a plug-in. The repository user name. The repository database user name. but not both. The connect string the Repository Agent uses to connect to the repository database. All registered local repositories must be running. Use the -p or -P option. For a list of connect string syntax. see “Registering a Repository Plug-in” on page 85. Use the -x or -X option. Use this option to delete a global repository. see Table 16-1 on page 405. 482 Chapter 16: Using pmrep and pmrepagent . Use the -p or -P option. but not both. Registerplugin uses the following command syntax: Registerplugin -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m -c database_connect_string -i input_xml_file_name -e -f force_registration -l login_name -w login_password -W login_password_environment_variable -k Table 16-72 lists pmrepagent Registerplugin options and arguments: Table 16-72. -f Required/ Optional n/a Registering a Plug-in (Registerplugin) The pmrepagent Registerplugin command registers an external plug-in to a repository. but not both. The repository password environment variable. You can use the Registerplugin command to update existing plug-ins. This option unregisters local repositories.

but not both. or the registration fails. The external directory password of the user registering the module. The password is not required if you are using option -m. Indicates to unregister and re-register a plug-in if it already exists. The connect string the Repository Agent uses to connect to the repository database. The repository database user name. If the plug-in exists. and you do not specify this option. The NIS login of the user registering an external security module. it generates an error. Use the -p or -P option. -P database_password_enviro nment_variable n/a database_connect_string -m -c -i -e -f Required Optional Optional input_xml_file_name n/a force_registration -l Required if registering security module components Required/ Optional login_name -w login_password pmrepagent Commands 483 . Use the -p or -P option. but not both. The password is not required if you are using option -m. Indicates to use a trusted connection to connect to the database. Update an existing plug-in. The name of the XML file describing the plug-in. Do not use this option for other plug-ins. Do not use this option for other plug-ins. Not applicable for authentication modules. Registerplugin Options and Arguments (pmrepagent) Option -t -u -p Required/ Optional Required Required Required/ Optional Required/ Optional Optional Required Argument Name database_type database_user_name database_password Argument Description The type of database the repository resides on. but not both. This login becomes the administrator user name in the repository. Not applicable for authentication modules. The repository database password environment variable. For a list of connect string syntax. Use the -w or -W option. The repository database password. Valid for Microsoft SQL Server only. Required if registering authentication module components. If the plug-in contains an authentication module you must supply the external login name. see Table 16-1 on page 405.Table 16-72. If the plug-in contains an authentication module you must supply the user password from the external directory or the registration fails.

Do not use this option for other plug-ins. When he upgrades PowerCenter. Note: The login name and password must be valid in the external directory. The -i option contains the XML file name that describes the security module. 484 Chapter 16: Using pmrep and pmrepagent . see “Registering and Unregistering LDAP Security Modules” on page 88. You can use the Registerplugin command to register the security plug-in. he decides to use the LDAP for repository user authentication. The administrator runs the pmrepagent command to register the new external module with the repository: pmrepagent registerplugin -r repositoryname -n Administrator -x RepoPasswd -t oracle -u admin-ora -p admin-passwd-ora -c oracle-server001 -i security/ldap_authen. it checks the library against the CRC. you must register the security module with the repository. Use the -w or -W option. If the plug-in contains an authentication module you must supply the user password from the external directory or the registration fails. the administrator user must use this login name and password to access the repository.xml -l adminuser -w admnpass The -l login name and -w login password options contain the valid NIS login information for the user running the pmrepagent command. When the Repository Agent loads the module. but not both. After registration.Table 16-72. or the administrator cannot access the repository using LDAP. Example An administrator administers PowerCenter for a company that has a centralized LDAP NIS for user authentication. The upgrade installs the LDAP security module in the repository security folder. For more information about this XML file. Required if registering authentication module components. Registerplugin Options and Arguments (pmrepagent) Option -W Required/ Optional Required/ Optional Argument Name login_password_environme nt_variable Argument Description The external directory password environment variable of the user registering the module. Stores the CRC of the plug-in library in the repository. -k Optional n/a Registering a Security Module If you want to use an external directory service to maintain users and passwords for a repository.

If you do not use these options. The repository code page.Restoring a Repository (Restore) The pmrepagent Restore command restores a repository backup file to a database. see “Restoring a Repository” on page 67. Not required if you are using option -m. but not both. Use the -p or -P option. then the Administrator’s password does not change when you restore the repository. Use a trusted connection to connect to the database. When you restore a repository to a different system. The target database must be empty. The repository database user name. Restore Options and Arguments (pmrepagent) Option -r -t -u -p Required/ Optional Required Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name database_type database_user_name database_password Argument Description The name of the repository you want to restore. The repository database password environment variable.” Note: If the repository uses repository authentication. The Repository Agent resets the Administrator’s password to “Administrator. Restore uses the following command syntax: Restore -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string -d code_page -h repserver_host_name -o repserver_port_number -g -i backup_file_name -z repository_creation_parameters -v administrator_username -x verify_password -X verify_password_environment_variable -a license_file_name -w -b skip_workflow/session_log -j skip_deploy_group_history -q skip_MX_data Table 16-73 lists pmrepagent Restore options and arguments: Table 16-73. Not required if you are using option -m. The repository database password. but not both. Use the -p or -P option. For a list of connect string syntax. If the repository you are restoring uses an external directory service. For more information about restoring a repository. or if the password is incorrect. The connect string the Repository Agent uses to connect to the repository database. -P database_password_environme nt_variable n/a database_connect_string -m -c -d Optional code_page pmrepagent Commands 485 . Valid for Microsoft SQL Server only. you can use the -v administrator_username and -x administrator_password to verify that one administrative user can connect to the repository if the restore completes. the Repository Agent does not assume that the same user authentication module is on the new system. the Repository Agent unregisters the external module and resets the Administrator password after the restore. see Table 16-1 on page 405. The type of database you want to restore to.

The port number of the Repository Server that manages the repository. Verify password. -x Required/ Optional verify_password 486 Chapter 16: Using pmrep and pmrepagent . Use this option to force the Repository Agent to verify that the administrator user is valid with the current authentication module.Table 16-73. This option has no argument. Include this option if you want to promote the repository to a global repository. The name of the repository backup file. The Repository Agent verifies that this password is valid for the user name on the target server. pmrepagent interprets the spaces as part of the tablespace name. Use the -x or -X option. The repository license file name. -v Optional/ Required for retaining an external security module. You can use any file name and path local to the Repository Server. Use the following format to specify the tablespace name: “%tablespace=<tablespace_name>” -i Required backup_file_name -z Optional repository_creation_parameters Do not include spaces around the equals sign. Restore Options and Arguments (pmrepagent) Option -h -l -o -g Required/ Optional Required Required Required Optional Argument Name repserver_host_name license_file_name repserver_port_number n/a Argument Description The host name of the Repository Server that manages the repository. You must use either the -x or -X option when you want to retain an external security module. administrator_username Specifies repository administrator user name. You must use this option to retain the external module registration after the restore. Use this option only with a repository using an external security module. Use this option only with a repository using an external security module. but not both. Use this option with the -v option when you want to retain the external security module after restoring. Use this option to specify the tablespace name for IBM DB2 EEE databases.

Skips deployment group history during backup.Table 16-73. see “Unregistering a Repository Plug-in” on page 86. Use the -x or -X option. -a -w -b -j -q Required Optional Optional Optional Optional license_file_name n/a skip_workflow/session_log skip_deploy_group_history skip_MX_data Note: You can also restore Teradata repositories using Fastload. Use this option with the -v option when you want to retain the external security module after restoring. You must use either the -x or -X option when you want to retain an external security module. Removes user name-login mapping. Use this option only with a repository using an external security module. For more information on unregistering plug-ins. Unregisterplugin uses the following command syntax: Unregisterplugin -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable-m -c database_connect_string -v vendor_id -l plugin_id -g remove_user_name_login_mapping -w new_password -W new_password_environment_variable pmrepagent Commands 487 . Skips tables related to workflow and session logs during backup. Skips tables related to MX data during backup. The name of the license file. Restore Options and Arguments (pmrepagent) Option -X Required/ Optional Required/ Optional Argument Name verify_password_environment_ variable Argument Description The verify password environment variable. Use this option only when unregistering an external module. The Repository Agent verifies that this password is valid for the user name on the target server. restore -r repository1 -t oracle -u admin-ora -p admin-passwd-ora -c oracle-server001 -h solaris001 -o 5001 -v adminuser -x adminpass -i repository1_backup. see “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479.rep Unregistering Plug-ins (Unregisterplugin) The pmrepagent Unregisterplugin command removes a plug-in from a repository. but not both. For more information. Example The following example restores a repository to a Solaris machine and specifies the administrator user name and password in order to keep the LDAP security module registration.

-P database_password_environment _variable -m -c Optional Required n/a database_connect_string -v Required vendor_id -l Required plugin_id -g Optional.Table 16-74 lists pmrepagent Unregisterplugin options and arguments: Table 16-74. but not both. Use this option only when you are unregistering a security module. The connect string the Repository Agent uses to connect to the repository database. Identifies the security plug-in by vendor identification number. but not both. The repository password. but the Repository Manager does not display them anywhere. For a list of connect string syntax. Valid for Microsoft SQL Server only. you retain the mapping in the repository. but not both. If you omit this option. You define this number when you register the plug-in. Removes the mapping between user names and login names in the repository when you unregister an external security module. The repository password environment variable. The repository database password. The password is not required if you are using option -m. Identifies the plug-in by identification number. The repository database password environment variable. Use the -x or -X option. You define this identification number when you register the plug-in. The repository database user name. Use the -p or -P option. Use the -x or -X option. The password is not required if you are using option -m. but not both. Indicates to use a trusted connection to connect to the database. remove_user_name_login_mappi ng 488 Chapter 16: Using pmrep and pmrepagent . Unregisterplugin Options and Arguments (pmrepagent) Option -r -n -x -X -t -u -p Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_environment _variable database_type database_user_name database_password Argument Description The name of the repository you want to upgrade. The type of relational connection. see Table 16-9 on page 418. Applicable when registering an external security module. see Table 16-1 on page 405. For a list of valid database types. Use the -p or -P option. The repository user name.

Unregisterplugin Options and Arguments (pmrepagent) Option -w Required/ Optional Required/ Optional Argument Name new_password Argument Description Specifies a new password for the user running the unregister command. Any users that you added to the system under repository authentication can log in with their old user names and passwords. -W Required/ Optional new_password_environment_vari able Unregistering an External Security Module You can use the Unregisterplugin command to discontinue using an external security module with a repository. pmrepagent Commands 489 . When you unregister an external authentication module. Specifies a new password environment variable for the user running the unregister command. Note: Although you can save the associations between external logins and repository user names. All user passwords reset to the values in the repository instead of the values in the external directory. all user passwords reset to the values in the repository. When you unregister an external authentication module. You remove the user name-login mapping. all user passwords reset to the values in the repository. Required when the plug-in contains a security module. but not both. you do not lose the mapping between the repository user names and the external security login names unless you specify the -g option. You must specify a new password in order to access the repository. When you unregister the security module. you decide to switch from the LDAP security module back to repository authentication. PowerCenter switches to repository authentication mode. the Repository Manager does not display the external logins while running under repository user authentication. He must also provide a new password to use after he switches back to repository user authentication.Table 16-74. If you unregister the external security module. Note: The Administrator must provide his LDAP NIS login and password to use the Unregisterplugin command. You must use the -w or -W option to create a new password for yourself when you unregister the security module. but not both. You must specify a new password in order to access the repository. Any users you added to the repository under the LDAP security cannot log in until you enable their user names. You can use the mapping again if you register a new security module. Required when the plug-in contains a security module. Example As an administrator. Use the -w or -W option. Use the -w or -W option.

Upgrade Options and Arguments (pmrepagent) Option -r -n -x -X -t -u -p Required/ Optional Required Required Required/ Optional Required/ Optional Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name repository_user_name repository_password repository_password_environment _variable database_type database_user_name database_password Argument Description The name of the repository you want to upgrade. The repository database password. Not required if you are using option -m. The connect string the Repository Agent uses to connect to the repository database. Not required if you are using option -m. Use the -x or -X option. The repository password. The type of database you want to upgrade to. The repository database password environment variable. The repository user name. Use the -p or -P option. see “Upgrading a Repository” in the Installation and Configuration Guide. For a list of connect string syntax. -P database_password_environment _variable n/a database_connect_string -m -c 490 Chapter 16: Using pmrep and pmrepagent . but not both. but not both. but not both. The repository password environment variable.The administrator might use a command similar to this: pmrepagent unregisterplugin -r repositoryname -n Administrator -x RepoPasswd -t oracle -u admin-ora -p admin-passwd-ora -c oracle-server001 -v 1 -l 3014 -g -w newadmnpass Upgrading a Repository (Upgrade) The pmrepagent Upgrade command upgrades a repository to the latest version. but not both. The repository database user name. For more information on upgrading repositories. Use the -p or -P option. see Table 16-1 on page 405. Valid for Microsoft SQL Server only. Use the -x or -X option. Upgrade uses the following command syntax: Upgrade -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string Table 16-75 lists pmrepagent Upgrade options and arguments: Table 16-75. Use a trusted connection to connect to the database.

Informatica recommends that you include a connect command as the first command called by the script file. For example. you might use pmrep to perform a daily backup of a production repository. For instance. c:\PowerCenter\pmrep\pmrep connect -r Production -n Administrator -x Adminpwd -t “microsoft sql server” -u sbrown -p sbrownx -c Central@Production echo Backing up repository Production. Tip: When you create script files using pmrep commands.. In this case. Scripting pmrep and pmrepagent Commands 491 . you might use some commands with specific options and arguments on a regular basis. This helps ensure you are performing tasks on the correct repository. You cannot run pmrep batch files while in pmrep interactive mode.rep You can run script files from the command interface...bat REM This batch file uses pmrep to connect to and back up the repository Production on the server Central @echo off echo Connecting to repository Production. connects to and backs up a repository called Production on a server named Central: backupproduction.Scripting pmrep and pmrepagent Commands When you use pmrep or pmrepagent. pmrep and pmrepagent indicate the success or failure of a command with a return code.bat. c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup. the following Windows batch file. Return code (0) indicates that the command succeeded.. backupproduction. you can create a script file to call one or more pmrep commands including its options and arguments. Return code (1) indicates the command failed.

the restored repository defaults to repository authentication mode. you must enter the name of the source or target instance for the -t option. 492 Chapter 16: Using pmrep and pmrepagent . If you do not specify this option with the valid administrator user name and password. Use characters that are not used in repository object names when you specify characters to separate records and columns. Use the -n option to use the Listtablesbysess command with the Updatesrcprefix or Updatetargprefix commands in a shell script if the source and target instance names match. end of record indicator. The source or target instance name must match the name displayed in the session properties or the name output by the Listtablesbysess command. When you include the -n option. Also. Bulkrestore uses Fastload when it restores a Teradata database. The Bulkrestore command is faster than the Restore command when the repository backup file is greater than 100 MB. This helps you use a shell script to parse the object metadata. When you include the -v option with Restore. you can retain the external directory service registration for the repository. You lose the login name-user name mappings. and end of listing indicator. Use the -n option when you use the Updatesrcprefix or Updatetargprefix commands.Tips Use Bulkrestore to restore Teradata repositories. Use the -v option when restoring a repository that uses an external directory service for user management. use the -n option to update a source even if the session uses a shortcut to a mapping. When using ListObjects. and to indicate the end of the listing. specify a character or set of characters that is not used in repository object names for the column separator.

496 Using the Deployment Control File. 494 Using the Object Import Control File.Appendix A Working with pmrep Files This appendix includes the following topics: ♦ ♦ ♦ ♦ Using the Persistent Input File. 504 Scripting pmrep and pmrepagent Commands. 507 493 .

none. object_subtype. and it can create one.EXPORT. The persistent input file represents objects already in your repository. ApplyLabel.3 1828891977:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944279765:138739712184505:137625613474:65536221345:65536133675:091734:090 53:65536156675. Add objects to a Deployment Group. see “CRCVALUE Codes” on page 267. For more information about the CRCVALUE. When you create a persistent input file with pmrep. and it can create one. Validate objects. Export objects to an XML file. List dependency objects. This command can use a persistent input file for processing. You can use the file for other pmrep commands.EXPORT. The following is a sample persistent input file: 2072670638:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944199885:138608640183285:1376256153425:131072168215:65536142655:0288235: 088154:65536122855. object_name. It also contains an encrypted repository GID.M_ITEMS. This ID identifies which repository the record comes from and prevents you from misusing the file and corrupting a repository. You can use a persistent input file with the following pmrep commands: ♦ ♦ ♦ ♦ ♦ ♦ AddToDeploymentGroup. ExecuteQuery. The persistent input file has the following format: encoded ID. You can create a persistent input file manually or by using pmrep. ObjectExport. resusable|non-reusable Creating a Persistent Input File with pmrep You can create a persistent input file using the pmrep ExecuteQuery. foldername. This command can use a persistent input file for processing. Label objects.1 494 Appendix A: Working with pmrep Files . Run a query to create a persistent input file.Using the Persistent Input File When you run pmrep with some tasks. You can specify a different path. These commands create files that contain a list of objects with encoded IDs and a CRCVALUE (Cyclic Redundancy Checking) code. Validate.M_ITEMS_2. The pmrep commands that use a persistent input file get object information from the encoded IDs.2 1995857227:57bfc2ff-df64-40fc-9cd4a15cb489bab8:3538944135065:13867417666804:1376256233835:19660880104:65536271545:0319425:01 7154:6553644164. Validate. you can use a persistent input file to specify repository objects that you want to process. The encoded IDs enable pmrep to process your input file quickly. ListObjectDependencies.mapping.EXPORT. version_number.none. it creates the file in the pmrep installation directory.M_NIELSEN.mapping. object_type.none.mapping. or ListObjectDependencies commands.

Object_subtype is the type of transformation or task.mapping. ExecuteQuery -q find_deleted_objects -t private -u deletes_workfile You can use deletes_workfile as the persistent input file to ObjectExport.newsrc. The record has the word “none” in place of the encoded ID. worklets. Use the “reusable or non-reusable” column only for object types that can be reusable or non-reusable.none.3267622055:57bfc2ff-df64-40fc-9cd4a15cb489bab8:353894462954:138805248300075:1376256151365:6553675414:65536174015:0273455:024 1435:65536261685. ObjectExport -i deletes_workfile -u exported_del_file Creating a Persistent Input File Manually If you manually create a persistent input file you must enter the word “none” in place of the encoded ID.none. such as transformations.” When you run the query with pmrep.EXPORT. it finds all the deleted objects in the repository and outputs the results to a persistent input file. ObjectExport exports all the referenced objects to an XML file called exported_del_file.2 The object is a source object.M_OS1.source. For information on valid transformations and task types see Table 16-16 on page 426. You must put the arguments in the correct order. sessions. and tasks.Oracle. For example. If the object is not a transformation or task. put the word “none” in the object_subtype argument. pmrep requires you to enter all the column arguments. This is an example from a manually created file: none. The pmrep commands get the object information from the other arguments in the records. You might create a query called “find_deleted_objects. and the record does not require the reusable argument. myfolder.1 Example You can use the ExecuteQuery command to create a persistent input file of objects to process in another pmrep command. Using the Persistent Input File 495 . suppose you want to export all logically deleted objects from the repository. except for the last column. It includes the database definition as a prefix.

but you must include its location in the input XML file. you must create an XML file defined by impcntl.Informatica Object Import Control DTD Grammar .Version 7. RESOLVECONFLICT?)> <!ATTLIST IMPORTPARAMS CHECKIN_AFTER_IMPORT CHECKIN_COMMENTS APPLY_LABEL_NAME RETAIN_GENERATED_VALUE COPY_SAP_PROGRAM APPLY_DEFAULT_CONNECTION > (YES | NO) "NO" CDATA CDATA #IMPLIED #IMPLIED (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "NO" <!--FOLDERMAP matches the folders in the imported file with the folders in the target repository --> <!ELEMENT FOLDERMAP EMPTY> <!ATTLIST FOLDERMAP SOURCEFOLDERNAME CDATA #REQUIRED #REQUIRED #REQUIRED #REQUIRED SOURCEREPOSITORYNAME CDATA TARGETFOLDERNAME CDATA TARGETREPOSITORYNAME CDATA > <!--Import will only import the objects in the selected types in TYPEFILTER node --> <!--TYPENAME type name to import.dtd. TYPEFILTER*.dtd.dtd file: <!-. TARGET and etc. normalizer and XML DSQ current values in the destination --> <!--COPY_SAP_PROGRAM Copy SAP program information into the target repository --> <!--APPLY_DEFAULT_CONNECTION Apply the default connection when a connection used by a session does not exist in the target repository --> <!ELEMENT IMPORTPARAMS (FOLDERMAP*.--> <!ELEMENT TYPEFILTER EMPTY> <!ATTLIST TYPEFILTER 496 Appendix A: Working with pmrep Files . you can supply a control file to answer questions that you normally address when you import objects with the Import Wizard.Using the Object Import Control File When you use the pmrep ObjectImport command.1 --> <!--IMPORTPARAMS This inputs the options and inputs required for import operation --> <!--CHECKIN_AFTER_IMPORT Check in objects on successful import operation --> <!--CHECKIN_COMMENTS Check in comments --> <!--APPLY_LABEL_NAME Apply the given label name on imported objects --> <!--RETAIN_GENERATED_VALUE Retain existing sequence generator. To create a control file.g. The import control file installs with the PowerCenter Client. e. The following is a sample of the impcntl. SOURCE. This should comforming to the element name in powermart.

TYPENAME > CDATA #REQUIRED <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. The combination of specified child nodes can be supplied --> <!ELEMENT RESOLVECONFLICT (LABELOBJECT | QUERYOBJECT | TYPEOBJECT | SPECIFICOBJECT)*> <!--LABELOBJECT allows objects in the target with label name to apply replace/reuse upon conflict --> <!ELEMENT LABELOBJECT EMPTY> <!ATTLIST LABELOBJECT LABELNAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--QUERYOBJECT allows objects result from a query to apply replace/reuse upon conflict --> <!ELEMENT QUERYOBJECT EMPTY> <!ATTLIST QUERYOBJECT QUERYNAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--TYPEOBJECT allows objects of certain type to apply replace/reuse upon conflict--> <!ELEMENT TYPEOBJECT EMPTY> <!ATTLIST TYPEOBJECT OBJECTTYPENAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--SPECIFICOBJECT allows a particular object(name.required for source object to identify uniquely--> <!--OBJECTTYPENAME Object type name--> <!--FOLDERNAME Folder which the object belongs to--> <!--REPOSITORYNAME Repository name that this object belongs to--> <!--RESOLUTION Resolution to apply for the object in case of conflict--> <!ELEMENT SPECIFICOBJECT EMPTY> <!ATTLIST SPECIFICOBJECT NAME DBDNAME CDATA CDATA #REQUIRED #IMPLIED #REQUIRED #REQUIRED #REQUIRED #REQUIRED> OBJECTTYPENAME CDATA FOLDERNAME CDATA REPOSITORYNAME CDATA RESOLUTION (REPLACE | REUSE | RENAME) Using the Object Import Control File 497 .) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name . typename etc.

COPY_SAP_PROGRAM APPLY_DEFAULT_CONNECTION FOLDERMAP SOURCEFOLDERNAME SOURCEREPOSITORYNAME TARGETFOLDERNAME TARGETREPOSITORYNAME TYPEFILTER RESOLVECONFLICT LABELOBJECT TYPENAME (see the following elements) LABELNAME RESOLUTION QUERYOBJECT QUERYNAME RESOLUTION TYPEOBJECT OBJECTTYPENAME RESOLUTION SPECIFICOBJECT NAME DBDNAME OBJECTTYPENAME 498 Appendix A: Working with pmrep Files . Specifies the target folder name for matching. Reuse. Specifies the import folder name to match to a folder in the target repository. Copies SAP program information into the target repository. Specifies the repository containing the source folder. and XML Source Qualifier transformation current values in the destination. targets. Replace. or Rename. Identifies objects by label name for conflict resolution specification. Normalizer. Reuse.Object Import Control File Parameters Table A-1 lists pmrep Object Import control file parameters: Table A-1. or Rename. Object Import Control File Elements and Attributes (pmrep) Element IMPORTPARAMS Attribute Name CHECKIN_AFTER_IMPORT CHECKIN_COMMENTS APPLY_LABEL_NAME RETAIN_GENERATED_VALUE Attribute Description Checks in objects when they successfully import. or mappings. Allows you to specify conflict resolutions for objects. Replace. Applies the label name on the imported objects. Applies the comments to the checked in objects. Reuse. for conflict resolution specification. such as sources. The default connection is the first connection from the sorted list of available connections. Rename. Object type for this conflict resolution. Specifies the repository containing the target folder. Applies the default connection when a connection used by a session does not exist in the target repository. Find the list of connections in the Workflow Manager. Replace. Specific object name for this conflict resolution. Source DBD name to identify source object. Retains existing Sequence Generator. Imports just the objects from a specific node. Identifies objects by type. Identifies objects from this query result for conflict resolution specification.

The repository containing the object. or Rename. Reuse.Table A-1. Replace. Using the Object Import Control File 499 . Object Import Control File Elements and Attributes (pmrep) Element Attribute Name FOLDERNAME REPOSITORYNAME RESOLUTION Attribute Description The folder the containing object.

Example Suppose you want to import only source objects. In the target folder. The file specifies the target folder and repository. <?xml version="1.dtd"> <IMPORTPARAMS CHECKIN_AFTER_IMPORT ="NO"> <FOLDERMAP SOURCEFOLDERNAME ="OLD_ACCOUNTING" SOURCEREPOSITORYNAME ="OLD_REPOS" TARGETFOLDERNAME ="NEW_ACCOUNTING" TARGETREPOSITORYNAME ="NEW_REPOS"/> <TYPEFILTER TYPENAME ="SOURCE"/> <RESOLVECONFLICT> <LABELOBJECT LABELNAME ="Monthend" RESOLUTION = "REPLACE"/> <QUERYOBJECT QUERYNAME ="yr_end_qry" RESOLUTION ="RENAME"/> </RESOLVECONFLICT> </IMPORTPARAMS> Sample Import XML File The following is a sample XML control file for ObjectImport.” However.0" encoding="ISO-8859-1"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. You have a query called “yr_end_qry” that finds these objects.dtd"> <!--IMPORTPARAMS This inputs the options and inputs required for import operation --> <!--CHECKIN_AFTER_IMPORT Check in objects on successful import operation --> <!--CHECKIN_COMMENTS Check in comments --> <!--APPLY_LABEL_NAME Apply the given label name on imported objects --> 500 Appendix A: Working with pmrep Files . you want to replace all the duplicate objects labeled “Monthend. and specifying resolutions for specific objects.0" encoding="UTF-8"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. It lists what types of objects to import and shows several methods that you can use to resolve conflicts. You might create a control file with the following attributes: <?xml version="1. you want to rename conflicting source objects that contain “Yr_End” in the object name. including specifying a resolution for query results. It specifies to check in the imported objects and label them. specifying resolutions for object types.

SOURCE.g. The combination of specified child nodes can be supplied --> <RESOLVECONFLICT> <!--QUERYOBJECT allows objects result from a query to apply replace/reuse upon conflict --> <QUERYOBJECT QUERYNAME="Q_MAPS_CREATED_1027" RESOLUTION="RENAME"/> <!--LABELOBJECT allows objects in the target with label name to apply replace/reuse upon conflict --> <LABELOBJECT LABELNAME="LABEL_DT1027" RESOLUTION="REPLACE"/> <!--TYPEOBJECT allows objects of certain type to apply replace/reuse upon conflict--> <TYPEOBJECT OBJECTTYPENAME="WORKFLOW" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="WORKLET" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="SESSION" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="MAPPING" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="MAPPLET" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="Source definition" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Target definition" RESOLUTION="REUSE"/> Using the Object Import Control File 501 . TARGET and etc.dtd.<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="PMREP_IMPORT_PARENT_TYPOBJ_REPLACE_CHILDREUSE" APPLY_LABEL_NAME="LABEL_IMPORT_PARENT_REPLACE_CHILDREUSE_ALL"> <!--FOLDERMAP matches the folders in the imported file with the folders in the target repository --> <FOLDERMAP SOURCEFOLDERNAME="PMREP_CHECKED_OUT" SOURCEREPOSITORYNAME="PMREP_AUTOMATION_1027" TARGETFOLDERNAME="PMREP_CHECKED_OUT_IMPORT" TARGETREPOSITORYNAME="PMREP_AUTOMATION_1027"/> <!--Import will only import the objects in the selected types in TYPEFILTER node --> <!--TYPENAME type name to import. This should conforming to the element name in powermart.--> <TYPEFILTER TYPENAME="SOURCE"/> <TYPEFILTER TYPENAME="TARGET"/> <TYPEFILTER TYPENAME="MAPPLET"/> <TYPEFILTER TYPENAME="MAPPING"/> <TYPEFILTER TYPENAME="TRANSFORMATION"/> <TYPEFILTER TYPENAME="SHORTCUT"/> <TYPEFILTER TYPENAME="CONFIG"/> <TYPEFILTER TYPENAME="TASK"/> <TYPEFILTER TYPENAME="SESSION"/> <TYPEFILTER TYPENAME="SCHEDULER"/> <TYPEFILTER TYPENAME="WORKFLOW"/> <TYPEFILTER TYPENAME="SCHEDULER"/> <TYPEFILTER TYPENAME="WORKLET"/> <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. e.

<TYPEOBJECT OBJECTTYPENAME="Expression" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Filter" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Aggregator" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Rank" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Normalizer" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Router" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Sequence" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Sorter" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="update strategy" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Custom Transformation" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Lookup Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Transaction control" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Stored Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="External Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Joiner" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="SessionConfig" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Email" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Command" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Scheduler" RESOLUTION="REUSE"/> <!--SPECIFICOBJECT allows a particular object(name.) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .required for source object to identify uniquely--> <!--OBJECTTYPENAME Object type name--> <!--FOLDERNAME Folder which the object belongs to--> <!--REPOSITORYNAME Repository name that this object belongs to--> <!--RESOLUTION Resolution to apply for the object in case of conflict--> <SPECIFICOBJECT NAME="ADDRESS" DBDNAME="sol805" OBJECTTYPENAME="Source Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="ADDRESS1" DBDNAME="sol805" OBJECTTYPENAME="Target Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="MAP_MLET_ADD1" OBJECTTYPENAME="Mapplet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="MAP_ADD1" OBJECTTYPENAME="Mapping" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="R_AGG1" OBJECTTYPENAME="Aggregator" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_CUSTOM11_M" OBJECTTYPENAME="Custom Transformation" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_EXP11_M" OBJECTTYPENAME="Expression" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_FIL11_M" OBJECTTYPENAME="Filter" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> 502 Appendix A: Working with pmrep Files . typename etc.

<SPECIFICOBJECT NAME="R_LKP1_M" OBJECTTYPENAME="Lookup Procedure" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_JOIN1_M" OBJECTTYPENAME="Joiner" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_RANK1_M" OBJECTTYPENAME="Rank" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_RANK1_M" OBJECTTYPENAME="Rank" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_RTR1_M" OBJECTTYPENAME="Router" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_SEQ1_M" OBJECTTYPENAME="Sequence" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_SORT1_M" OBJECTTYPENAME="Sorter" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_TC1_M" OBJECTTYPENAME="Transaction control" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_UPD11_M" OBJECTTYPENAME="update strategy" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="SP_CREATEINDEX1_M" OBJECTTYPENAME="Stored Procedure" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="SP_DROPINDEX1_M" OBJECTTYPENAME="Stored Procedure" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="SP_External_M" OBJECTTYPENAME="External Procedure" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="default_session_config" OBJECTTYPENAME="SessionConfig" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="Config1" OBJECTTYPENAME="SessionConfig" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="Sched1" OBJECTTYPENAME="Scheduler" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="Command" OBJECTTYPENAME="Command" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="Email" OBJECTTYPENAME="Email" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="s_M_FLAT" OBJECTTYPENAME="Session" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="s_M_FLAT1" OBJECTTYPENAME="Session" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="WLET1" OBJECTTYPENAME="Worklet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="WLET_CYCLE" OBJECTTYPENAME="Worklet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="WF_ALL_REUSE_OBJS" OBJECTTYPENAME="Workflow" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="WF_NESTED" OBJECTTYPENAME="Workflow" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> </RESOLVECONFLICT> </IMPORTPARAMS> Using the Object Import Control File 503 .

DEPLOYGROUP?)> <!ATTLIST DEPLOYPARAMS DEFAULTSERVERNAME COPYPROGRAMINFO COPYMAPVARPERVALS COPYWFLOWVARPERVALS COPYWFLOWSESSLOGS COPYDEPENDENCY LATESTVERSIONONLY RETAINGENERATEDVAL RETAINSERVERNETVALS CDATA #IMPLIED (YES | NO) "YES" (YES | NO) "NO" (YES | NO) "NO" (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "YES"> <!--criteria specific to deploying folders--> <!ELEMENT DEPLOYFOLDER (REPLACEFOLDER?. OVERRIDEFOLDER*)> <!ATTLIST DEPLOYFOLDER NEWFOLDERNAME CDATA #IMPLIED> <!--criteria for replacing a target folder--> <!ELEMENT REPLACEFOLDER EMPTY> <!ATTLIST REPLACEFOLDER FOLDERNAME RETAINMAPVARPERVALS CDATA #REQUIRED (YES | NO) "NO" RETAINWFLOWVARPERVALS (YES | NO) "YES" RETAINWFLOWSESSLOGS MODIFIEDMANUALLY (YES | NO) "NO" (YES | NO) "NO"> <!--shared folder to override--> <!ELEMENT OVERRIDEFOLDER EMPTY> <!ATTLIST OVERRIDEFOLDER SOURCEFOLDERNAME SOURCEFOLDERTYPE TARGETFOLDERNAME TARGETFOLDERTYPE CDATA #REQUIRED (LOCAL | GLOBAL) "LOCAL" CDATA #REQUIRED (LOCAL | GLOBAL) "LOCAL" 504 Appendix A: Working with pmrep Files .dtd file.dtd. To use pmrep deployment commands you must create an XML file that works with depcntl. The following is a sample of the depcntl. but you should include its location in the input XML file. you can use a control file to answer questions that you see when you deploy objects using the Copy Wizard. The deployment control file installs with the PowerCenter Client. <!ELEMENT DEPLOYPARAMS (DEPLOYFOLDER?.Using the Deployment Control File When you use DeployDeploymentGroup or DeployFolder pmrep commands.

Indicates local or global folder. Creates a new folder with this name. Copies mapping variable persistent values. Does not allow replacing of manually modified target folders. Retains workflow session logs in the target. Retains mapping variable persistent values in the target. Retains server network related values in tasks. Copies workflow variable persistent values.<!--criteria for clearing a source group in DeployDeploymentGroup--> <!ELEMENT DEPLOYGROUP (OVERRIDEFOLDER*. Using the Deployment Control File 505 . Name the folder after replacing it. Specifies the current folder that shortcuts point to. Copies SAP R/3 installed ABAP program. Copies workflow logs. Copies dependency information for objects in mappings. Deployment Control File Elements and Attributes (pmrep) Element DEPLOYPARMS Attribute Name DEFAULTSERVERNAME COPYPROGRAMINFO COPYMAPVARPERVALS COPYWFLOWVARPERVALS COPYWFLOWSESSLOGS COPYDEPENDENCY LATESTVERSIONONLY RETAINGENERATEDVAL RETAINSERVERNETVALS DEPLOYFOLDER REPLACEFOLDER NEWFOLDERNAME FOLDERNAME RETAINMAPVARPERVALS RETAINFLOWVARPERVALS RETAINWFLOWSESSLOGS MODIFIEDMANUALLY OVERRIDEFOLDER SOURCEFOLDERNAME SOURCEFOLDERTYPE Attribute Description Specifies the PowerCenter Server in the target repository to run workflows. Retains workflow variable persistent values. Keeps the current value for Sequence Generator or Normalizer transformations. Copies only the latest version. APPLYLABEL?)> <!ATTLIST DEPLOYGROUP CLEARSRCDEPLOYGROUP (YES | NO) "NO"> <!--labels used to apply on the src objects and deployed objects--> <!ELEMENT APPLYLABEL EMPTY> <!ATTLIST APPLYLABEL SOURCELABELNAME SOURCEMOVELABEL TARGETLABELNAME TARGETMOVELABEL CDATA (YES | NO) CDATA YES | NO) #IMPLIED "NO" #IMPLIED "NO"> Deployment Control File Parameters Table A-2 lists pmrep deployment control file parameters: Table A-2.

you can choose to move the label to the selected version of the object.” You might create a control file with following attributes: <?xml version="1.dtd"> <DEPLOYPARAMS DEFAULTSERVERNAME ="info7261" COPYPROGRAMINFO ="NO" COPYWFLOWVARPERVALS ="NO" COPYWFLOWSESSLOGS ="NO" COPYDEPENDENCY ="YES" LATESTVERSIONONLY = "NO"> <REPLACEFOLDER FOLDERNAME ="NEW_YEAR" RETAINVARPERVALS ="YES"/> <OVERRIDEFOLDER SOURCEFOLDERNAME ="SC_FOLDER" OVERRIDEFOLDERNAME ="NEW_SC_FOLDER"/> </DEPLOYPARAMS> 506 Appendix A: Working with pmrep Files . TARGETLABELNAME TARGETMOVELABEL Example Suppose you want to deploy the latest version of a folder and include all dependencies. Indicates local or global folder. Moves the label from a different version of the object in the source group to the deployment group version of the object. and you need to point the shortcuts from the sc_folder to the new_sc_folder. Applies a label to all the objects in the source group. Deployment Control File Elements and Attributes (pmrep) Element Attribute Name TARGETFOLDERNAME TARGETFOLDERTYPE DEPLOYGROUP APPLYLABEL CLEARSRCDEPLOYGROUP SOURCELABELNAME SOURCEMOVELABEL Attribute Description Changes folder that shortcuts point to.Table A-2. you want to rename it to “new_year.0" encoding="ISO-8859-1"?> <!DOCTYPE DEPLOYPARAMS SYSTEM "depcntl. If the Repository Agent detects the label is applied to another version of the same object. If the Repository Agent detects the label is applied to another version of the same object. Moves the label from a different version of the object in the target group to the deployment group version of the object. After you copy the folder. Removes objects from source group after deploying. you can choose to move the label to the latest version of the object. Applies a label to all the objects deployed to the target repository. You need to retain the current values in a Sequence Generator transformation.

you can create a script file to call one or more pmrep commands including options and arguments. For instance. Informatica recommends that you include a connect command as the first command called by the script file.Scripting pmrep and pmrepagent Commands When you use pmrep or pmrepagent. you might use commands with specific options and arguments on a regular basis. you might use pmrep to perform a daily backup of a production repository.rep You can run script files from the command interface.bat REM This batch file uses pmrep to connect to and back up the repository Production on the server Central @echo off echo Connecting to repository Production. connects to and backs up a repository called Production on a server named Central: backupproduction..bat. Return code (0) indicates that the command succeeded. You cannot run pmrep batch files while in pmrep interactive mode. the following Windows batch file. backupproduction. In this case. Return code (-1) indicates the command failed. c:\PowerCenter\pmrep\pmrep connect -r Production -n Administrator -x Adminpwd -t “microsoft sql server” -u sbrown -p sbrownx -c Central@Production echo Backing up repository Production. pmrep and pmrepagent indicate the success or failure of a command with a return code.. Tip: When you create script files using pmrep commands. Scripting pmrep and pmrepagent Commands 507 . For example.. This helps ensure you are performing tasks on the correct repository. c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup..

508 Appendix A: Working with pmrep Files .

516 pmrep Tasks. 519 pmrepagent Tasks. 510 Workflow Manager Tasks. 520 509 . It then lists the repository privileges and folder permissions required to perform each task in these tools: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Designer Tasks. 513 pmcmd Tasks. 511 Workflow Monitor Tasks. 515 Repository Manager Tasks.Appendix B Permissions and Privileges by Task This appendix summarizes the available tasks in the PowerCenter Client tools.

targets. Read permission in the originating folder. For example. Read and write permission in the destination folder. targets. transformations. and mappings Create/edit sources. Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources. you can edit a mapping if you have one of the following sets of privileges and permissions: ♦ ♦ Use Designer privilege with both read and write permission on the folder Super User privilege Table B-1 lists the required privileges and permissions for Designer tasks: Table B-1. and mappings Create shortcuts from a shared folder Repository Privilege Use Designer Use Designer Use Designer Use Designer Folder Permission None required Read Read/Write Read permission in the shared folder. Read/Write Read Read Read/Write Read Read/Execute Read Copy object from one folder to another Copy and paste objects in mappings or mapplets in the same folder Compare objects Export objects Import objects Edit breakpoints Create a debug session Use Designer Use Designer Use Designer Use Designer Use Designer Use Designer Use Designer and Use Workflow Manager Use Designer and Workflow Operator 510 Appendix B: Permissions and Privileges by Task . you must have one of the listed sets of privileges and permissions.Designer Tasks To perform the following Designer tasks. Read and write permission for the destination folder. transformations.

you must have one of the listed sets of privileges and permissions. you can edit a session if you have one of the following sets of permissions and privileges: ♦ ♦ Use Workflow Manager privilege with both read and write permission on the folder Super User privilege Note: In addition. you must also have read permission for connection objects associated with the session. if you enabled enhanced security.Workflow Manager Tasks To perform the following Workflow Manager tasks. Execute None required Execute Execute Workflow Manager Task Connect to the repository using the Workflow Manager Create workflows and tasks Edit workflows and tasks Create and edit sessions Delete Connection Folder Permission None required Read/Write Read/Write Read/Write None required None required None required Schedule or unschedule workflows Use Workflow Manager Workflow Operator Read/Execute Read Read/Execute Read Start workflows immediately Use Workflow Manager Workflow Operator Workflow Manager Tasks 511 . Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Administer Repository Use Workflow Manager Use Workflow Manager Connection Object Permission None required None required None required Read Write Write permission and own the connection object. Table B-2 lists the required privileges and permissions for Workflow Manager tasks: Table B-2. For example. Write permission and belong to the same group as the owner of the connection object.

FTP. FTP. Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager and Administer Server Use Workflow Manager Use Workflow Manager Administer Repository Administer Server Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Connection Object Permission None required Workflow Manager Task Stop the PowerCenter Server Folder Permission None required Configure database.Table B-2. and external loader connections in the Workflow Manager Edit database. Write None required None required Read Read/Write Read/Write None required None required None required None required None required None required None required 512 Appendix B: Permissions and Privileges by Task . and external loader connections in the Workflow Manager Manage connection object permissions Register PowerCenter Servers and configure server variable directories Export objects Import objects Validate workflows and tasks Run Workflow Monitor None required None required None required Read.

Use Workflow Manager privilege with read and execute permissions for the folder containing the workflow. Super User privilege Table B-3 lists the required privileges and permissions for Workflow Monitor tasks: Table B-3. For example. you can restart a workflow if you have one of the following sets of permissions and privileges: ♦ ♦ ♦ Workflow Operator privilege with execute permission for the folder containing the workflow. Required Privileges and Permissions for Workflow Monitor Tasks Workflow Monitor Task Connect to repository Repository Privilege Use Workflow Manager or Workflow Operator Workflow Operator Use Workflow Manager View the session log Workflow Operator Use Workflow Manager Restart workflow Workflow Operator Use Workflow Manager Stop workflow Workflow Operator Use Workflow Manager Abort workflow Workflow Operator Use Workflow Manager Resume workflow Workflow Operator Use Workflow Manager Folder Permission None required Connection Object Permission None required Connect to the PowerCenter Server None required None required Read Read/Execute Execute Execute Execute Execute Execute Execute Execute Execute None required None required None required None required None required None required None required None required None required None required None required None required Workflow Monitor Tasks 513 .Workflow Monitor Tasks To perform the following Workflow Monitor tasks. you must have one of the listed sets of privileges and permissions.

Table B-3. Required Privileges and Permissions for Workflow Monitor Tasks Workflow Monitor Task View session details and session performance details Repository Privilege Use Workflow Manager Use Workflow Manager Folder Permission Read Read Connection Object Permission None required None required 514 Appendix B: Permissions and Privileges by Task .

pmcmd Tasks To perform the following pmcmd tasks. Required Privileges and Permissions for pmcmd Tasks pmcmd Task Ping the PowerCenter Server Stop the PowerCenter Server All other tasks Repository Privilege None required Administer Server Use Workflow Manager Workflow Operator Folder Permission None required None required Execute None required Connection Object Permission None required None required Execute Execute pmcmd Tasks 515 . you can start a workflow using pmcmd if you have the following permissions and privileges: ♦ ♦ Workflow Operator privilege Execute permission on the folder Note: If you enabled enhanced security. For example. you must have one of the listed sets of privileges and permissions. you must have execute permission for connection objects associated with the session in addition to the privileges and permissions listed above. Table B-4 lists the required privileges and permissions for pmcmd tasks: Table B-4.

you must have one of the listed sets of privileges and permissions.Repository Manager Tasks To perform the following Repository Manager tasks. you can edit the properties of a folder if you have one of the following sets of permissions or privileges: ♦ ♦ ♦ Browse Repository privilege. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Add to deployment group Apply label Change object version comments Change status of an object Change your password Check in Check in/undo check out for other users Check out/undo check out Connect to the repository using the Repository Manager Copy a folder to a different repository Repository Privilege Use Repository Manager Use Repository Manager Use Repository Manager or be check-out owner Use Repository Manager Browse Repository Use Repository Manager Administer Repository Use Repository Manager Browse Repository Browse Repository on the originating repository and Administer Repository on the destination repository Administer Repository Folder Permission Read Read Write Write None required Write Write Write None required Read permission on the original folder None required None required None required None required None required None required Read Other Permission Write on deployment group Execute on label Copy a folder within the same repository Read permission on the original folder Read permission on the original folder Read on the original folders Write on target Read Browse Repository None required Copy global object Use Repository Manager 516 Appendix B: Permissions and Privileges by Task . as the folder owner with read permission on the folder Administer Repository privilege with read permission on the folder Super User privilege Table B-5 lists the required permissions and privileges for Repository Manager tasks: Table B-5. For example.

Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Create a folder Create or edit deployment group Create or edit label Create or edit query Delete (versioning) Delete a folder Repository Privilege Administer Repository Administer Repository Administer Repository Browse Repository Use Repository Manager Browse Repository Administer Repository Delete from Deployment Group Deploy Edit folder Use Repository Manager Administer Repository Browse Repository Administer Repository Edit folder properties Browse Repository Administer Repository Export objects Freeze folder Use Repository Manager Browse Repository Administer Repository Import objects Import. and privileges Mass update Purge (versioning) Receive user and group notifications Recover Remove Label References Run Query Use Repository Manager Browse Repository Administer Repository Super User Administer Repository Super User Use Repository Manager Use Repository Manager Browse Repository Manager Folder Permission None required N/A N/A N/A Write Folder owner and read permission Read N/A Read on the original folder.Table B-5. or remove the registry Manage users. Folder owner and read permission Read Folder owner and read permission Read Read Folder owner and read permission Read Read/Write None required None required Write Write None required Write N/A N/A Other Permission None required Edit: Write on deployment group Edit: Write on label Write on query None required None required None required Write on deployment group Read and execute on deployment group None required None required None required None required None required None required None required None required None required None required None required None required None required None required None required Read on query Repository Manager Tasks 517 . groups. export.

Table B-5. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Search target tables by keyword Terminate other users and unlock objects Unlock an object or folder locked by your username Unlock any locked object or folder in the repository View dependencies Repository Privilege Browse Repository Super User Browse Repository Super User Browse Repository Folder Permission Read None required Read None required Read Other Permission None required None required None required None required None required 518 Appendix B: Permissions and Privileges by Task .

you must have one of the listed sets of privileges and permissions. Required Permissions and Privileges for pmrep Tasks pmrep Task List repository objects (Listobjects) List sources or targets in a session (Listtablesbysess) Export objects (ObjectExport) Import objects (ObjectImport) Change the name of an existing connection (Switchconnection) Update email addresses (Updateemailaddr) Update source table owner names (Updatesrcprefix) Update target table name prefixes (Updatetargprefix) Update transformation properties for Sequence Generator transformations (Updateseqgenvals) All other tasks Repository Privilege Browse Repository Use Workflow Manager Use Repository Manager Use Repository Manager Super User Folder Permission Read Read Read Read/Write None required Connection Object Permission None required None required None required None required None required Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Designer Write Write Write Write None required None required None required None required Administer Repository None required None required pmrep Tasks 519 . you can list objects in a repository if you have one of the following permissions or privileges: ♦ ♦ Browse Repository privilege with read permission on the folder Super User privilege Table B-6 lists the required permissions and privileges for pmrep tasks: Table B-6.pmrep Tasks To perform the following pmrep tasks. For example.

However. The repository user name does not require any folder or connection object permissions.pmrepagent Tasks You do not need any privilege or permission to perform pmrepagent tasks. when you must provide a repository user name and password. 520 Appendix B: Permissions and Privileges by Task . use one with the Administer Repository privilege.

Index A activity log Administration Console 56 addprivilege description 450 Addrepository description 414 Addserver description 413 AddToDeploymentGroup description 461 Addusertogroup description 450 Administer Repository privilege limiting 161 Administration Console activity log 56 adding repository configurations 105 backing up repositories 66 closing connections 83 connecting to Repository Server 58 Console Tree 52 copying repositories 62 creating repositories 116 deleting repositories 64 disabling repositories 73 editing repository configurations 113 enabling repositories 71 exporting repository configurations 115 HTML view 53 importing repository configurations 115 List view 53 Main window 53 MMC 52 overview 50 privileges 50 promoting repositories 117 propagating domain information 78 registering local repositories 75 registering repository plug-ins 85 removing repository configurations 114 repositories node 54 repository name node 54 Repository Server name node 54 Repository Servers node 54 restoring repositories 67 sending repository notifications 74 starting 52 starting repositories 71 stopping repositories 71 unregistering repository plug-ins 85 updating licenses 111 using 52 viewing connections 79 advanced mode copying deployment groups 259 copying folders 244 521 .

192 command line program See pmrep See also pmrepagent comments accessing metadata 335 comparing See also Designer Guide See also Workflow Administration Guide folders 174 Repository objects 45 Workflow Manager objects 21. 31 connection objects See also Workflow Administration Guide definition 10 permissions and privileges 245 connections terminating 83 viewing 79 connectivity connect string examples 405 connectivity license keys overview 119 ConnectString setting for repository configuration 107 Console Tree Administration Console 52 control file deployment 504 object import 496 ObjectImport XML example 500 Copy Wizard copying objects 302 resolving conflicts 300 viewing object dependencies 305 .ApplyLabel description 462 associating server with sessions 245 audit trails 208 configuration setting 110 creating 153 authenticating users description 131 authentication switching methods 133 using LDAP 131 B backing up repositories 66 repositories with pmrep 416 repositories with pmrepagent 477 Backup command pmrep 416 pmrepagent 477 Bulkrestore command description 479 C Changepassword description 450 Checkin description 464 CheckinCommentsRequired repository configuration 110 checking in description 213 non-reusable objects 213 when importing objects 280 checking out description 211 non-reusable objects 211 undoing a checkout 213 checkouts searching for checked out objects 211 viewing 211 Cleanup description 411 ClearDeploymentGroup description 465 code pages See also Installation and Configuration Guide 522 Index exporting objects 266 global repository 117 importing objects 266 local repository 75 repository 51. 45 conflicts copying Designer objects 310 copying workflow segments 308 database connections 307 mapping 307 resolving when importing 281 connect string examples 405 syntax 405 connecting to repositories 30.

copying See also copying deployment groups 254 See also copying folders 248 Copy Wizard procedure 302 deployment groups 254 Designer objects 310 folders 250 in Workflow Manager 306 mapping segments 310 mapping variables 307 mapplet segments 310 repositories 62 resolving conflicts 300 sessions 306 shortcuts 195 workflow segments 308 workflows 306 worklets 306 copying deployment groups copying composite objects 255 copying shortcuts 256 in advanced mode 244 in typical mode 244 steps 258 copying folders from local to global repositories 250 in advanced mode 244 in typical mode 244 shortcuts in folders 249 within a repository 250 CRCVALUE codes overview 267 Create command description 480 CreateConnection description 417 CreateDeploymentGroup description 465 Creategroup description 452 CreateLabel description 466 Createuser description 452 creating global shortcuts 190 local shortcuts 187 metadata extensions 328 MX views 336 repositories 116 repositories using pmrepagent 480 repository users 134 user groups 128 users under an external directory 137 D database connections See also Workflow Administration Guide during folder or deployment group copy 245 permissions and privileges 245 database definitions MX view 338 DatabaseArrayOperationSize configuration setting 110 setting for repository configuration 110 DatabaseConnectionTimeout setting for repository configuration 110 DatabasePoolSize setting for repository configuration 110 DatabaseType setting for repository configuration 107 DateDisplayFormat setting for repository configuration 109 DB2 See IBM DB2 DBPassword setting for repository configuration 107 DBUser setting for repository configuration 107 Decision Support Systems (DSS) working with Informatica metadata 335 default groups security 127 default users editing 131 Delete command description 481 Deleteconnection description 420 DeleteDeploymentGroup description 466 DeleteFolder description 453 DeleteLabel description 467 Deleteserver description 421 deleting folders 173 metadata extensions 332 Index 523 .

258 copying composite objects 255 copying shortcuts 256 creating 237 definition 218 dynamic 240 editing 237 rolling back a deployment 238 static 239 Designer See also Designer Guide copying objects 310 permissions 510 development license key overview 119 Disablerepository description 421 documentation conventions xxxvii description xxxvi domains building 13 configuring for global shortcuts 192 connectivity 75 reusing data 15 dropping MX views 336 DTD file exporting and importing objects 267 plug-in template 484 dynamic deployment groups associating with a query 240 definition 236 editing 240 DynamicConfigRefreshInterval setting for repository configuration 110 E editing folder permissions 149 folders 173 metadata extensions 331 repository users 138 user 138 user groups 129 Edituser description 454 Enablerepository description 422 enabling a user description 139 environment variables repository username and password 408 Error Severity Level Repository Agent messages 101 Repository Server messages 98 setting for repository configuration 109 exchanging metadata 314 execute lock description (repository) 154 ExecuteQuery description 470 Exit description 411 exiting pmrep 411 exporting metadata 314 registries 32 repository configurations 115 sources and targets 314 exporting objects code pages 266 dependent objects 270 multiple objects 269 overview 264. 37 dependent objects exporting and importing 270 DeployDeploymentGroup description 467 DeployFolder description 469 deploying objects depcntl.dtd 504 rolling back a deployment 238 deployment groups copying 254.recovering deleted objects 215 repositories 64 repositories using pmrepagent 481 user groups 129 versioned objects 215 depcntl. 276 parent objects 271 permissions 266 524 Index .dtd listing 504 dependencies source-target 27 viewing 27.

171 renaming 173 Repository Manager uses 166 shared 15.dtd 267 privileges 266 sessions 272 shortcuts 270 steps for 285 versioned objects 273 external loader connections during folder or deployment group copy 245 permissions and privileges 245 external security module registering 484 unregistering 489 properties 168. 192 creating 14 promoting 112. 249 environment 192 repository usernames 193 server username 193 tips 197 updating 194 updating views 194 groups creating user 128 default security 127 editing description 129 F FindCheckout description 472 flat files MX view of repository file definitions 343 view of fields 345 folder permissions description 126 editing 149 overview 148. 249 copying between local repositories 250 copying global shortcuts 250 copying local shortcuts 249 copying or replacing 250 copying shortcuts 249 creating 171 deleting 173. 453 deploying 469 Designer uses 166 editing 173 editing permissions 149 locking during folder copy 249 maintaining connections during copy 245 modifying 456 naming copies 249 organizing 166 overview 166 owner and owner’s group 169 H HTML view Administration Console 53 I IBM DB2 connect string example 405 setting tablespace name 107 Import Wizard importing objects 287 resolving object conflicts 281 Index 525 . 169 shortcuts 249 Workflow Manager uses 166 FTP connections during folder or deployment group copy 245 permissions and privileges 245 G global objects See Workflow Administration Guide global repositories code page 117. 117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182.powrmart. 168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245.

466 definition 218 deleting 467 editing 219 launching Administration Console 52 LDAP authentication description 131 LDAP authentication module configuring 92 LDAP security module registering 88 unregistering 95 license files compatibility between files 122 overview 120 PowerCenter Server 122 repository 120 license key types development 119 production 119 license keys connectivity 119 option 119 overview 119 product 119 repository types 119 licenses See also license files 119 See also license keys 119 overview 119 rules and guidelines 123 updating 111 List view Administration Console 53 Listallgroups description 455 Listallprivileges description 455 Listallusers description 455 ListObjectDependencies description 429 Listobjects description 423 listing folders 427 listing transformations 427 transformation types 426 Listtablesbysess description 428 . 462 applying when importing 280 526 Index creating 219.dtd 267 privileges 266 resolving conflicts 281 sessions 272 shortcuts 274 steps for 287 validating objects 281 validating XML file 280 XML file 267 Informatica documentation xxxvi Webzine xxxviii Informix connect string syntax 405 interactive mode pmrep 406 in-use lock description (repository) 154 K KeepAliveTimeout setting for repository configuration 110 keywords searching for target definitions 34 L labels applying 221.importing metadata 314 objects 280 ODBC data sources 33 registries 32 repository configurations 115 sources and target 314 importing objects code pages 266 CRCVALUE codes 267 dependent objects 270 DTD file 267 impcntl.dtd 496 Import Wizard 287 multiple objects 269 ObjectImport XML example 500 overview 264 parent objects 271 permissions 266 powrmart.

249 tips 197 updating 194 updating views 194 locking description 126 during deployment group copy 254 during folder copy 249 locks releasing 83 viewing 80. 157 log entries truncating 48 log files codes 97 Repository Agent 100 Repository Server 98 LogFileName setting for repository configuration 110 logs deleting 439 Repository Agent 100 Repository Server 98 M main window Administration Console 53 sorting and organizing 25 mapping segments copying 310 mappings See also Designer Guide conflicts 307 copying mapping variables 307 copying segments 310 dependencies 27 description 9 metadata extensions in 326 view of source fields 359 view of source fields used by targets 358 view of sources 359 view of target tables 360 mapplet segments copying 310 mapplets See also Designer Guide description 9 metadata extensions in 326 MaximumConnections setting for repository configuration 109 MaximumLocks setting for repository configuration 110 MessageReceiveTimeOut setting for repository configuration 108 MessageSendTimeout setting for repository configuration 108 metadata adding to repository 9 analyzing 335 definition 2 exchanging 314 exporting 314 importing 314 multi-dimensional 9 protection levels within folders 168 reusing 14 reusing across folders 182 sharing 14 viewing 334 metadata exchange See MX (Metadata Exchange) metadata extensions copying 246 creating 328 deleting 332 description 326 editing 331 non-reusable 327 overview 326 reusable 327 Microsoft Management Console See MMC Microsoft SQL Server connect string syntax 405 MMC Administration Console 52 Modifyfolder description 456 MQ connections See PowerCenter Connect for IBM MQSeries User and Administrator Guide Index 527 .local repositories See also repositories code page 75. 192 promoting to global 112 registering 75 local shortcuts behavior when copying folders 249 creating 187 definition 182.

MX (Metadata Exchange) Change Management views 398 database definition views 338 deployment views 392. 396 folder view 401 integrating views with third-party software 337 label views 398 mapping views 353 mapplet views 353 metadata extension views 364 overview 334 PowerCenter Server views 396 repository view 395 security views 390 source views 339 target views 347 task views 371 transformation views 366 workflow views 371 worklet views 371 MX views categories 334 creating 336 dropping 336 field-level summary 338 integrating with third-party software 337 REP_ALL_MAPPINGS 354 REP_ALL_MAPPLETS 355 REP_ALL_SCHEDULERS 374 REP_ALL_SOURCE_FLDS 341 REP_ALL_SOURCES 339 REP_ALL_TARGET_FIELDS 349 REP_ALL_TARGETS 347 REP_ALL_TASKS 374 REP_ALL_TRANSFORMS 366 REP_CM_LABEL 399 REP_CM_LABEL_REF 399 REP_COMPONENT 384 REP_DATABASE_DEFS 338 REP_DEPLOY_GROUP 392 REP_DEPLOY_GROUP_DETAIL 393 REP_EVENT 376 REP_FLD_MAPPING 358 REP_GROUPS 391 REP_LOAD_SESSIONS 380 REP_MAPPING_PORT_CONN 363 REP_MAPPING_UNCONN_PORTS 362 REP_METADATA_EXTN_DEFINES 365 REP_METADATA_EXTNS 364 REP_REPOSIT_INFO 395 REP_SEG_FLDS 345 REP_SERVER_INFO 396 REP_SERVER_NET 397 REP_SERVER_NET_REF 397 REP_SESS_CONFIG_PARM 385 REP_SESS_LOG 387 REP_SESS_PARTITION_DEP 385 REP_SESS_TBL_LOG 388 REP_SESS_WIDGET_CNXS 383 REP_SESSION_CNXS 381 REP_SESSION_FILES 382 REP_SESSION_INSTANCE_FILES 383 REP_SESSION_INSTANCES 381 REP_SRC_FILE_FLDS 345 REP_SRC_FILES 343 REP_SRC_FLD_MAP 359 REP_SRC_MAPPING 359 REP_SRC_TBL_FLDS 346 REP_SRC_TBLS 344 REP_SUBJECT 401 REP_TARG_FLD_MAP 357 REP_TARG_MAPPING 356 REP_TARG_TBL_COLS 351 REP_TARG_TBL_JOINS 361 REP_TARG_TBLS 350 REP_TASK_ATTR 386 REP_TASK_INST 377 REP_TASK_INST_RUN 378 REP_TBL_MAPPING 360 REP_USER_GROUPS 391 REP_USERS 390 REP_VERSION_PROPS 398 REP_WFLOW_RUN 379 REP_WFLOW_VAR 375 REP_WIDGET_ATTR 369 REP_WIDGET_DEP 368 REP_WIDGET_FIELD 369 REP_WIDGET_INST 368 REP_WORKFLOW_DEP 377 REP_WORKFLOWS 372 SQL scripts 336 N naming copied folders 249 replaced folders 249 native connect string See connect string Navigator Administration Console 52 528 Index .

432 importing 280.Repository Manager 23 notifications receiving in Designer 6 receiving in Repository Manager 6 sending 74 notify description 431 Owner’s Group security level description (folder) 148 P parent objects exporting and importing 271 password editing user 136 permissions Administration Console tasks 50 configuring for folders 148 configuring for versioning objects 149 Designer tasks 510 editing folder 149 exporting objects 266 folder types 168 importing objects 266 pmcmd 515 pmrep tasks 519 pmrepagent tasks 520 Repository Manager tasks 516 security levels (folder) 169 troubleshooting 163 Workflow Manager tasks 511 Workflow Monitor tasks 513 persistent input file creating with pmrep 494 persistent resources cleaning up with pmrep 411 plug-ins See also repository plug-ins XML templates 484 pmcmd permissions 515 See also Workflow Administration Guide pmrep adding a privilege 450 adding a user to a group 450 adding to a deployment group 461 applying a label 462 backing up a repository 416 Change Management commands 460 changing the connection name 438 changing the repository password 450 checking in an object 464 cleaning persistent resources 411 clearing deployment group 465 command arguments 407 command line modes 406 O object dependencies viewing from the Copy Wizard 305 object locks See also locks overview 155 object queries associating with a deployment group 240 configuring multiple conditions 225 configuring query conditions 225 definition 218 running 232 searching for dependent objects 225 validating 231 object status changing 206 description 206 ObjectExport description 432 ObjectImport description 433 objects checking in 464 copying 302 exporting 276. 433 modifying in XML file 277 validating for import 281 validating multiple 42 viewing dependencies 37 ODBC data sources See also Installation and Configuration Guide importing 33 option license keys overview 119 Oracle connect string syntax 405 Output window Repository Manager 28 Owner security level description (folder) 148 Index 529 .

overview 126 shared folders 170 PowerCenter Client security 126 PowerCenter Metadata Reporter using 335 PowerCenter Server See also Workflow Administration Guide during folder copy 245 licenses 122 security 126 server variables 245 starting 193 PowerCenter Server license files overview 122 powrmart.command options 407 command tips 492 commands 410 connecting to a repository 410 creating a deployment group 465 creating a group 452 creating a label 466 creating a persistent input file 494 creating a user 452 deleting a deployment group 466 deleting a folder 453 deleting a label 467 deleting a server 421 deploying a deployment group 467 deploying a folder 469 deployment control parameters 505 disabling a repository 421 editing a user 454 enabling a repository 422 executing a query 470 exiting 411 exporting objects 432 importing objects 433 interactive mode 406 listing all groups 455 listing all privileges 455 listing all users 455 listing checked-out objects 472 listing object dependencies 429 listing objects 423 listings tables by session 428 modifying folder properties 456 object import control parameters 498 overview 404 permissions 519 registering a user 457 registering local repositories 434 removing a group 457 removing a privilege 458 removing a user 458 removing a user from a group 459 removing repositories 435 repository commands 412 running script files 436 security commands 449 sending notification messages 431 showing connection information 437 stopping a repository 437 undoing check-out 473 unregistering local repositories 440 updating a database connection 441 updating email addresses 442 updating notification email addresses 442 updating repository statistics 447 updating sequence values 444 updating server details 443 updating server variables 446 updating table owner name 445 updating target table name prefix 447 using script files 507 using scripts 491 validating objects 474 pmrepagent backing up repositories 477 command tips 492 commands 477 creating repositories 480 deleting repositories 481 permissions 520 registering a plug-in 482 restoring repositories 485 restoring Teradata repositories 479 unregistering plug-ins 487 upgrading repositories 490 using script files 507 using scripts 491 post-session email updating addresses with pmrep 442 PowerCenter building domains 13 copy from local to global repositories 250 security.dtd overview 267 privileges See also permissions See also repository privileges Administration Console tasks 50 530 Index .

troubleshooting 163 starting 71 Index 531 . 117. 160 security log file 153 security. 50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. overview 142 troubleshooting 163 Workflow Manager tasks 511 product license keys overview 119 promoting repositories 117 purging description 216 objects 216 Q queries See also object queries executing 470 R recovering deleted objects 215 register description 434 registering a user 457 plug-in using pmrepagent 482 security module using pmrepagent 484 Registerplugin description 482 Registeruser description 457 registry exporting 32 importing 32 releasing repository locks 83. overview 155 overview 2. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126. 250 reports metadata 335 repositories adding 29 adding metadata 9 administration overview 11 architecture 3 avoiding shared accounts 160 backing up 66 backing up with pmrepagent 477 changing a code page 117 checking status 54 code pages 51. 421 enabling 71 enabling version control 118 exporting/importing registries 32 licenses 120 limiting access 161 locks 154 log file codes 97 log files 97 managing 52 moving to a different Repository Server 77 object locking. 192 connecting to 30 connecting to multiple 31 connecting with pmrep 410 connectivity 4 copying 62 copying folders between local 250 creating 116 creating relational connections 417 creating users 134 database definition views 338 default privileges 143 deleting 64 disabling 73. 158 removerepsitory description 435 removing repositories 29 users 141 replacing folders 248.Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. 75.

stopping 71 stopping with pmrep 437 types of 50 unregistering 440 version control 16 view of associated target tables 350 view of target table properties 351 viewing details 26 viewing locks 157 viewing metadata 334 repository deleting details from 439 enabling 422 Repository Agent architecture 3 checking status 54 connectivity 4 disabling 73 enabling 71 identifying process ID 97 log file codes 97 logging 100 starting 71 stopping 71 repository configuration CheckinCommentsRequired 110 creating 104 dynamically updating 113 editing 113 exporting 115 importing 115 removing 114 setting CodePage 107 setting ConnectString 107 setting DatabaseArrayOperationSize 110 setting DatabaseConnectionTimeout 110 setting DatabasePoolSize 110 setting DatabaseType 107 setting DateDisplayFormat 109 setting DBPassword 107 setting DBUser 107 setting DynamicConfigRefreshInterval 110 setting Error Severity Level 109 setting KeepAliveTimeout 110 setting LogFileName 110 setting MaximumConnections 109 setting MaximumLocks 110 setting MessageReceiveTimeOut 108 setting MessageSendTimeOut 108 setting SecurityAuditTrail 110 setting TablespaceName 107 setting ThreadWaitTimeout 110 repository connections terminating 83. 151 repository license files overview 120 repository license key overview 120 repository locks overview 154 releasing 158 types of 154 viewing 157 Repository Manager components 22 dependency window 27 folder maintenance overview 166 folders 23 main window 25 Navigator 23 Output window 28 overview 20 permissions 516 repository details 26 sessions node details 26 windows 23 repository notifications overview 6 receiving in PowerCenter Server 7 receiving in Workflow Manager 7 receiving in Workflow Monitor 7 sending 74 repository objects description 10 metadata extensions in 326 repository plug-ins registering 85 removing 85 updating 86 repository privileges See also permissions assigning 146 description 126 overview 142 revoking 146. 152 viewing 79. 147 repository security level description (folder) 148 Repository Server Administration Console 50 architecture 3 client connections 3 532 Index .

configuring system environment 5 connecting 58 connectivity 4 identifying process ID 97 log file codes 97 logging 98 managing individual repositories 52 moving repositories 77 notifications 6 Propagate command 78 repository type license keys 119 repository users creating 134 creating global shortcuts 193 creating with default security 134 default privileges 143 default repository privileges 143 description 126 editing 138 editing password 136 overview 131 resolving object conflicts importing objects 281 Restore command description 485 restoring repositories 67 repositories using pmrepagent Bulkrestore 479 repositories using pmrepagent Restore 485 reusable transformations description 9 Rmgroup description 457 Rmprivilege description 458 Rmuser description 458 Rmuserfromgroup description 459 Run description 436 S script files running 436 scripts using 491 search See also Designer Guide keyword 34 security creating an audit trail 153 overview 126 pmrep commands 449 repository users 131 tips 160 troubleshooting 163 security module restoring repositories with 67 SecurityAuditTrail logging activities 153 setting for repository configuration 110 server variables during folder copy 245 updating with pmrep 446 Servers adding 413 session directories See server variables 245 session logs truncating 48 Session Operator privilege limiting 162 sessions copying 306 copying mapping variables 307 database connection conflicts 307 description 10 exporting 272 importing 272 metadata extensions in 326 view of current logs 387 view of current scheduled 380 view of individual session 388 sessions nodes details viewing 26 shared accounts avoiding 160 shared folders See also folders description 15 shortcuts See also Designer Guide advantages 183 behavior when copying folders 249. 250 copying 195 default names 184 dependencies 27 Index 533 .

185 refreshing properties 194 renaming source qualifiers 196 tips 197 to folders 249 troubleshooting 198 updating 194 updating views 194 using 194 using queries to locate 230 Showconnectioninfo description 437 source databases view of analyzed or imported sources 344 view of fields 346 source definitions description 9 metadata extensions in 326 source file connections node viewing details 26 sources exporting to BI tools 314 importing from BI tools 314 source-target dependencies description 27 SQL scripts for creating/dropping MX views 336 starting Administration Console 52 repositories 71 static deployment groups definition 236 editing 239 statistics updating repository 447 status user statuses with LDAP 131 status bar progress indicator 22 stopping repositories 71 repositories with pmrep 437 stopRepository command pmrep 437 Super User privilege limiting 161 SwitchConnection description 438 T table owner name updating with pmrep 445 TablespaceName setting for repository configuration 107 target definitions description 9 keyword searches 34 metadata extensions in 326 view of associated transformations 357 view of joins between target tables 361 view of table-level transformations 356 targets exporting to BI tools 314 importing from BI tools 314 tasks metadata extensions in 326 Teradata connect string example 405 restoring repositories using pmrepagent 479 ThreadWaitTimeout setting for repository configuration 110 tips pmrep commands 492 pmrepagent commands 492 repository security 160 shortcuts 197 transformations description 9 metadata extensions in 326 troubleshooting exporting objects 296 importing objects 296 repository security 163 shortcuts 198 Truncatelog description 439 typical mode copying folders 244 534 Index .description 9 descriptions inherited 184 exporting 270 global 182. 187 overview 182 properties 184 referenced objects 183. 190. 192 importing 274 local 182.

152 viewing 79.U UndoCheckout description 473 unregister description 440 unregistering plug-ins using pmrepagent 487 security module using pmrepagent 489 Unregisterplugin description 487 UpdateConnection description 441 Updateemailaddr description 442 Updateseqgenvals description 444 Updateserver description 443 Updatesrcprefix description 445 updating non-reusable sessions 446 Updatesrvvar description 446 Updatestatistics description 447 Updatetargetprefix description 447 updating non-reusable sessions 448 updating repository license files 111 shortcuts 194 Upgrade description 490 upgrading repositories using pmrepagent 490 user connections description 126 terminating 83. 151 user groups creating 128 default repository privileges 143 defaults 127 deleting 129 description 126 editing 129 folder permissions 128 limiting privileges 160 overview 127 users adding to repositories 134 adding under an external directory 137 authentication 131 customizing privileges 161 default users 131 editing 138 enabling 139 LDAP authentication 131 removing 141 valid statuses with LDAP 131 V validating objects 42 validating objects with pmrep Validate 474 variables copying mapping variables 307 updating with pmrep 446 version control enabling for repositories 118 version history viewing 208 versioned objects checking in 211 checking out 211 deleting 215 exporting 273 object status 205 overview 200 purging 216 recovering a deleted object 215 sample scenario 201 tracking changes 208 viewing applied labels 205 viewing history 208 viewing object properties 203 viewing properties 203 viewing version properties 204 versioning object permissions description 126 versioning objects configuring permissions 149 definition 218 deployment groups 236 labels 219 object queries 224 Index 535 .

versions purging 216 tracking changes 208 viewing object version history 208 viewing properties 203 viewing repository locks 80 user connections 79 validating for object import 280 validating objects 281 W webzine xxxviii windows displaying Repository Manager 23 workflow logs truncating 48 Workflow Manager See also Workflow Administration Guide copying in 306 permissions 511 Workflow Monitor See also Workflow Administration Guide permissions 513 workflow segments copying 308 workflow tasks See also Workflow Administration Guide description 10 workflows See also Workflow Administration Guide copying 306 description 10 metadata extensions in 326 worklets See also Workflow Administration Guide copying 306 description 10 metadata extensions in 326 write permission description (folder) 168 write-intent lock description (repository) 154 X XML file CRCVALUE codes 267 exporting and importing objects 267 modifying objects 277 plug-in templates 484 536 Index .