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

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

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

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

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

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

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

xvi Table of Contents .

. . . . . . . . . . . . .. . . . . . 9-5. . . . . . . . . . . . 8-2. .. . . . . . . . . . . . . . .. 25 . . . . . . . . . . . . . ... . . . . . .. . . 9-4. . . . 40 . 9-3. . . . . . .. . . . Sample Query Results . .. . . . . . . . . . . . . . . . . . . . . . . Deployment Group Editor . 9-9. 9-6. . . . . . . . . . . . . . . . .. 7-4. . . . .. . . Version Properties .. . . . . . . . . . . . . . . .. . ... . . .. . . . . . . . Results View Windows List . .. . . .. . . . .. . . . . . . . ... . . . .. . 9-12. . . . . . . . . . . . .. ... . . . . . . . . . . 9-11. . . ... . . . . 27 . .. . . . . Repository User Names and External Login Names 6-1. . . . . . . . . . . 2-3. . Apply Label Wizard .. . . . . .. . Activity Log Window . . . .. . . . .. . . View Dependencies Window . . 55 . .. . . .. . . . . . . . . . .. . . . . . .. .. . . . . . . . . . . . . . . . . . . ... . .. . . .. ... .. . .. . . . . Object Dependencies Saved as HTML . . ... . Query Browser ... . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. .. .. Referenced Shortcut Object . . ... . . . . . . . . . . . . . . .. . ... . . ... . . . . . . . . .. . . . .. . . . . . 7-1. . .. . . . 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 .. . . . .. . .. .. . . . . . Application Log Message Detail .. .. . . . One-Way and Two-Way Comparisons . . . . . . . 9-2. . . . . . . 22 .. .. . .. . . . . . . PowerCenter Repository Connectivity . . . . .. . . . . .. . .. . . .. . . . ... . . . . .. . . .. .. 11-1. .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. . . . . .. . . . . . . . . . . . .. . . ... . . . . .. . . . . .. . . . . . . . . . . . . . .. . . . . . Deployment Group Browser ... .. . . . . . . . . .. . . ... . . . .. . .. . .. . . . ... . . . . . . . .. 8-4. . . . . . . . . . . . . . . .. . .. . . . . . .. . . . 9-8. ... . .. . .. . . . . . . . . . . .. . . . . .. . . 7-3. . . .. .. .. .. 2-7. .. . . . . . .. . .. . . . .. . .. . . . . ... .. . . . .. .. CRCVALUE Code in an Exported XML File . . . . . .. . . . .. .. . Dependencies Dialog Box . . . .. .. .. . . . . 3-4. . . . . . . . . . .. . 2-5. ... . . ... . ... Object Properties . . . . .. . .. . . . . . . . .. . . . . . . . Repository Manager Components . Deployment Group History . . . . . . . . . . . 24 . . . . . Validate Objects Results . . . . . . . . . . . . . . . . . . . Output Window . . . . . . . . . 43 . . . . . . . . . . .. . . . . . . . . . . .. Object Status Properties . . . . . .. . Dependency for Deployment Group Dialog Box . . . ... . . . . . .. . . . 3-5. .. . View History Window .. . . . . . . . .. . ... . .. . .. . . . .. . .. . . . . .. . .. 3-2. .. 8-6. . . . .. . . . .. ... . . . . . 52 . .. 2-8. . . . . . . . . . . . .. . . . . . . . . . . . . . Dependency Window . . .. . . 9-10. . . . . . .. . . . . . . . .. . . .. . . . Label Editor Options . Label Browser . .. Object and Shortcut Description . . . . . . . .. . . . . .. 8-1. . Labels Properties . . . .. . 5-1. .. . . . . . ... . . . .. . . .. . . . . . . . .. . . . . . . . . . . .. . . .. . . .. .. . . . . . .. . . . . . . . . . . . .. Administration Console . . . Transformation Shortcut Icon . . . Create a Global Shortcut . . . . . .... .. . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5.. . .. . . . .. . 7-2.. . . . . . . . .. .. . . . . 2-9. . . .. . . .. . .. . . . . . . . .. . . . . . . . . . . . . . .. .. . . . . . . .. . . . . .. . . . . . . .. . . . . .. . . . . . . . . . . .. . . . . . . . .. . . . . . . . .. . . . . . . . . . .. .. . .. . . . . . 41 . .. Repository Manager Navigator .. . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . 9-7. . . .. Repository Details . . . . . . Query Editor . .. . . . . . . . . . . 9-1. . . . 8-3. . . . . .. . . . . . . . Source Definition Object Properties . .. . 3-3. . . .. . . ... . . . . . . . . .. . . . . . . ... . . . . . . .. . . . . . . 4 . . . . . . . . . . . . . . . . . 2-6. . . . .. . . . . . . . .. . . . ... .. . . Apply Label Dialog Box . . . . . .. . . . . . . . . . . .. . . . . . . . Event Viewer Application Log Message . . 2-4. .. . ... . . . . . . .. . . . . . . . . . . . . 39 . . . . . . 2-2. . . . . .. .. . . . . . . . . . 28 . . . . . . . . . . .. . Query with Multiple Conditions . . . . . .. . . 3-1. 2-1. .

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

. . . . . 2-5. . . Versioning Object Security Levels . . Tasks Available in View Checkouts Window . . . . . . . . . . 54 . . .. ... . . . . . . . . 4-1. 2-4. . . Repositories Node Details . . . . . . . . . . Tasks Available in Query Results Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2. . . . . . . . . . . . . LDAP Login Properties Options . 8-2. . . . . . . . . . . Query Parameters and Values . . . . . . . . . . . . . . . . . 2-3. . Compared Object Types and Attributes . . . . . . . . New Repository . . .. . . . . . . . .. . 3-1. . 96 . . . 6-1. .. . . . . . . . . . . . . . . Repository Details .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . . . . . 54 . . . . . 7-1. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 . . . 94 . . . . . .. 3-6. . . . . . . . . . . . . . . . . . . .. . . Repository Log Codes . . . 26 . . . . . . . . . . . . . . . . . . . . . .. . . .. . HTML Links for Performing Repository Tasks . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . Copy Folder Wizard Prompts (Copying a Folder) . . .. . . . .. . . . ... . . . . . . . . .. . . . .. 3-11. . . . . . . . . . . . . Change In Object Status After Copying Deployment Group Objects . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . Object Details Displayed in Repository Main Window .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5. ... . . . . . . . . . Dependencies Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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. .. . . . . . . .Database Connection Tab . . . .. . . .. . . .. . . . . . . . . . .. . . . . 9-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting Special Characters in Repository License File Names . Folder Object Security Levels . . . . . . . . . .. . 3-9. . . . . Default Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repository Connection Properties . . . . . . .. 9-2. . . 3-2. Register Security Module Options. . . . . . . . . . . . . . . . . . . . . . . . . 55 . . . . . .. . . . . .. . . . . . 4-3. . . . . . . . . . . . . . 4-6. . . . . . . . . . . . . . . . . . . . . . 91 . . . . .. . . . . . . Object Lock Properties . . . . . . 10-2. . . . . . . . . . . . . . . . . . New Repository . .. . . . .. . Object Properties for View Dependencies Window . . . . . . . . . . . . . . . . . . . . . .. . . Validate Objects Properties. . . . . . . . . . . . . . . . . . . . . . . . Copying Global or Local Shortcuts . . . . . . . . . . . ... . . . . . Viewing Object Dependencies . . 3-5. . . . . . 5-6. . . . . . . . 93 . . . 8-1. . . . . 3-10. . . . . .. . . . . . . .. . . 5-4. .. . . . . . . . . . New Repository . . . . . . 10-1. . . . . 3-4. . . . . . . . . . Label Options and Description . . . . . . . . . . . . . . . . . .. . . . . . .. .. .. . . . . . . . . . . . .. . . 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 . . . . . . .Configuration Tab .. . . . . . . . . . . . 3-7. . . . . .. . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 4-2. . 55 . . . .. . . . . . . . . . . . . . .. . License File Compatibility Requirements . . Compared Objects in Compare . . . .. . .Network Tab . . . . . . . .. . . . . . Repository Servers Node Details . . . . . . . . . .. . . . . . . . 5-3. . . .. . .. . . . . .. . . . . 9-3. . . . . . Tasks Available in View History Window . . . . . . . 6-3. .. . . . . . . . . 5-7.. . . . . . . . . . 5-1. . .. . 3-3. . . . . . . 4-5. . . . LDAP Login Properties Options . . . . . . . Repository User Connection Details . .. . . . . . . . . . . . . . . . 43 . . . .. . . . . 79 . . 6-2. . . . . . . . . .. . . . . . . . . . Folder Permissions . . . . . 4-4.. . . . 40 .. . . . . . . 39 . . . . . Repository Locks . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . .. . . . . . LDAP Server Configuration Options . . . . 3-8.. . 5-2. . . . . . . Object Lock Properties . . . . . Extended Repository Privileges . . . . . . .. . .. . . . . . . . . . . . New Repository . . . 81 .General Tab . . . . . . . .

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

. . REP_TASK_INST MX View . . . . .. . . . . . .. ... . .... . .. . .. . . 15-45. . . . . . . Workflow. . . . .. REP_WORKFLOW_DEP MX View . . .. . . . . . . . . .. . . . . .. Deployment Views . .. REP_ALL_TASKS MX View . .. . . . . . . . Worklet. . .. .. . .. .. .. . . . . . .. . . . . .. .. . . .. . REP_USERS MX View . ... . . . . . . . . .. . . . . . .. .. . . . . . ... Change Management Views . . . . .. . . . . . . . . . .. .. . . . . . . . 15-48. . . . . . . . . .. 15-40. . . .. . ... . . . . ... . . ... . . . . .. . . . . . 15-43. .. . . 15-50. . . . . . . ... . . REP_SERVER_INFO MX View . . REP_SESS_TBL_LOG MX View . .. . . . . . . . . 15-65. . . . . . . . . . REP_SESSION_INSTANCE_FILES MX View REP_SESS_WIDGET_CNXS MX View . . . . . 15-75. . . . . . . . . .. . . .. .. .. . . . .. . .. . ... . . .. . . . . .. .. . . . . . . . .. ... . .. . . . . .. . . . . . . . . . . .. . . . . . .. . REP_COMPONENT MX View . . . .. . .. . . . ... . . ... . ... .. . . . .. . . . . . . . ... . . ... .. . . . . .. .. . . PowerCenter Server Views . .. and Task Views .... . . . . . . . REP_USER_GROUPS MX View . .. .. . . . . . . . . . . . . . . . ... . .. .. . . REP_REPOSIT_INFO MX View .. . . . .. . .. . . . . . . . . .. . . . . . . . . . . . . . .. REP_EVENT MX View . .. . . . . . . . . . . . . . . . .. . . .. . . . REP_WORKFLOWS MX View . .. . .. 15-60. . . .. 15-62. . . . . . . . . . REP_SESS_PARTITION_DEF MX View . .. . . 15-63. . . . . . .... .. . . . .. . . . . ... . . REP_CM_LABEL_REF MX View . . .. 15-74... . .. . . . . . .. . .. .. . .. . . 15-34. .. . . . .. . . . . .. .. .. ... . . . .. . . . REP_ALL_TRANSFORMS 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. . . .. . . REP_SESSION_FILES MX View . . . . ... . .. .. . . . . . . .. . . . 15-68.. . . REP_TASK_ATTR MX View .. . . . . REP_CM_LABEL MX View . .. . . . .. .. . . . . . . . . . .. . . . . ... .. . . . . . REP_SERVER_NET MX View . .. . . . REP_SESS_LOG MX View .. .. . . . . .. Security Views . . ... . . . . ... .. .. . REP_SESSION_INSTANCES MX View . . . . ... . .. . . . . . . .... . . . ..... . .. . . . . . . . . . . .. . . ...... . . . . .. . . . . . . . . . .. .. REP_SERVER_NET_REF MX View. . . . .. . . 15-44. .... . . . . . . . . .. . . REP_TASK_INST_RUN MX View .. . . . . . . . . . . . . . . . . . REP_EIDGET_ATTR MX View . REP_WFLOW_VAR MX View . . . . . . . 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 . . . . . . . . . . . . . . . REP_LOAD_SESSIONS MX View . . . 15-66. . . .. . . ... . . . . . ... .. .. . . . . . . . . . . 15-72. ... REP_WFLOW_RUN MX View .. .. . . . . . . . . . . . . . .. ... . 15-55. ... . . 15-67. . . . . . . . . . . . . . . . . . . REP_WIDGET_INST MX View . . .. . . . . . . ... REP_WIDGET_FIELD MX View . . .. . . .. . . . . . ... . . . . . . 15-53. . . . . .. . . . REP_ALL_SCHEDULERS MX View . . . 15-73. . . . .. REP_DEPLOY_GROUP_DETAIL MX View . .. . . . . . . . . . . . . 15-51. . . . . . . . . . .. . . . . .. . . . .. . 15-46. . . . . . . . . . .. . . 15-52. . . .. . . .. . .... .. . . . . .. . . . . . . . . . . . REP_SESS_CONFIG_PARM MX View .. . . . . . . .. . . . .. ... . . . 15-49. . .. . REP_SESSION_CNXS MX View . . . . . . . . 15-42.. . . .. . REP_GROUPS MX View .. .. 15-58. . . . . . . 15-57. . . . . .. . .. . . . . . . . . . . . . . . . . . . .. . ..... . . . . . . . .. . . . ... . . . .. . . . . . . 15-47. .. . . . .. .. . . . . . .. . . .. ... . . ... . .. 15-38. . . .. . 15-54. . . . . . . 15-69.. .. . .. .. . . . . .. . . 15-37. . . . .. ... . . . . . .. . . .. . .. . . . . . . . . .. . .. . . 15-70. . . . . .. . . . . . . . . . . . . .. . . . . . REP_WIDGET_DEP MX View . . . . . . ... . . . . .. . 15-56. 15-39. . . . . . . . . . . .. . . . . . . . . . .. .. . . . .. . .. . . .. . . ... 15-59. . . . 15-41.. . . . .. . . .. . . .. . . .. .. . ... . . . . .. . . . . .. . . . . . . . . 15-61. . . .. .. . . . 15-35. . . . . .. . .. . . . . . . . . .. .. . . . . . 15-36. .. REP_DEPLOY_GROUP MX View . .. 15-64. . . .. . . . REP_VERSION_PROPS MX View . 15-71. . . ... . . .... . . .. . . .

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

ModifyFolder Option and Argument (pmrep) . .. . . . . . .. . ClearDeploymentGroup Options and Arguments (pmrep) . . . 16-52. . . . 16-57. . . . .. . . .. .. . . .. .. . . . . . . . . . .. . . . . . . . . . . . . 16-62. . . . Rmuserfromgroup Options and Arguments (pmrep) . . . .. .. 16-50. . . . . .. . . . . . . . . . . . . . . . . . . . . Deployment Control File Elements and Attributes (pmrep) . . . . . . .. . . . . . . . .. . . . . . . . . DeleteDeploymentGroup Options and Arguments (pmrep) .. . . . . . .... . . . . . . . . . . . . . Required Permissions and Privileges for Repository Manager Tasks B-6. .. . . . . . . .. . .. . .. 16-48. . .. . . . . . . . . . . . .. FindCheckout Options and Arguments (pmrep) . . . . . . . . . . . . . . . .. . . .. . Required Privileges and Permissions for Workflow Manager Tasks . .. . . . .. . . pmrepagent Commands . .. . . . . . .. B-3. . . . Required Privileges and Permissions for Workflow Monitor Tasks ... . . B-2. B-1. . . . . . .. . . . . . . 16-59. . ... . . .. Required Permissions and Privileges for pmrep Tasks. .. . . ExecuteQuery Options and Arguments (pmrep) . . . 16-61. . . . . A-2. Validate Options and Arguments (pmrep) . .. . . . .. . . . . . . 16-71. . . . . . .. .. . . .. . .. . . . . A-1. . . 16-64. . . . . . . . . . DeployDeploymentGroup Options and Arguments (pmrep) . . . . .. . . .. . . . . Required Privileges and Permissions for pmcmd Tasks . Rmuser Option and Argument (pmrep) . . . . . . . .. .. . . . . 16-53.. .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. . . . . . . . UndoCheckout Options and Arguments (pmrep) . . . 16-58... . . .. . Bulkrestore Options and Arguments (pmrepagent) .. 16-51. . . . . Delete Options and Arguments (pmrepagent) .. . . . . . . . 16-46. .. . ... . . . . . . . . . . . . . .. . . . . . . . . . . . ... . . CreateDeploymentGroup Options and Arguments (pmrep) . . . 16-56.. . . . . . . . . . . . . .. . . .. . . . . . . . . . . . . . DeleteFolder Options and Arguments (pmrep) . . . .. 16-54. .. . . . . .. 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 . . . .. .. . . .. . . . . .. . . . . . . . . . . B-5. . . . . . . . . . . .. . . . . . 16-73. . . . .. . . 16-67. . . . . . . . Registerplugin Options and Arguments (pmrepagent) . . . . . . . Registeruser Option and Argument (pmrep) . . ... . . Object Import Control File Elements and Attributes (pmrep) . . . . Required Privileges and Permissions for Designer Tasks . . 16-63. . . . Backup Options and Arguments (pmrepagent) . . . . Rmgroup Option and Argument (pmrep). Upgrade Options and Arguments (pmrepagent) . . .. . .. . . .. . . . . . . . . . . 16-49. . . . . . . . . .. . . . . . . 16-60. . . . ... . . Unregisterplugin Options and Arguments (pmrepagent) . . .. . . . .. . . .. . 16-74. . . . . . .. . . . . . . . . . . . . . . . . .. DeleteLabel Options and Arguments (pmrep) . . . . . . . . . .. . . . . . . . . . ..... . . . . . . . . 16-47. .. 16-65. . . . .. AddToDeploymentGroup Options and Arguments (pmrep) . 16-69. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . .. . . . . . .. CreateLabel Options and Arguments (pmrep) . . . . DeployFolder Options and Arguments (pmrep) .. . 16-45.. . . . ... . . . . . . . . . . . . . . . . . . . . .. 16-44. . .. . .. . . .. . . . . . . . . . . . . . . . . . . . ApplyLabel Options and Arguments (pmrep) ... . . . . . 16-75. . . .. Create Options and Arguments (pmrepagent) . . Rmprivilege Options and Arguments (pmrep) . . . ... ... .. . . . 16-55. . . 16-72. . . . . . . . . . . Checkin Options and Arguments (pmrep) . . . . . . pmrep Change Management Commands . . . .. . 16-66. 16-70. . . . . .. . .. . .. . . .. . . . .. . . . Createuser Options and Arguments (pmrep) . .. . . . . . . . . . . . . .. . . . . . .. . . . . . . . . . .. . . . .. . . . . . . . .. . . . Edituser Options and Arguments (pmrep) . . . . . . . . . . . . . . B-4. . 16-68. . . . . Restore Options and Arguments (pmrepagent) .. . . . . .

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

For more information on copying objects in a deployment group. Version Control 17 . For more information on using pmrep for change management. see “Using pmrep and pmrepagent” on page 403. You can also use pmrep to perform change management tasks. you can automate the process for copying deployment groups. see “Copying Folders and Deployment Groups” on page 241. For example.repository. This allows you to use pmrep scripts and files to automate change management tasks. 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.

18 Chapter 1: Understanding the Repository .

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

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

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

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 Components Navigator Window Dependency Window Output Window Status Bar Main Window When the Repository Manager accesses the repository. Progress Indicator 22 Chapter 2: Using the Repository Manager . the Status Bar reflects the connection in progress with a progress indicator.Repository Manager Windows The Repository Manager has a main window and a status bar for information on the operation you are performing.

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

Note: If you enable versioning when you create the repository. 24 Chapter 2: Using the Repository Manager . You can also right-click the object in the Navigator and select Properties from the shortcut menu. you can view all tabs on the Properties dialog box. see “Viewing Version Properties” on page 203.Figure 2-2 shows the Navigator components: Figure 2-2. and then clicking the View Properties button in the toolbar. For more information about object properties. 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.

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

Displays properties for each workflow in the folder. Displays connection properties for each target connection associated with the session. targets. The Sessions Logs node displays under each session in the Sessions node. Select a transformation to view details for the specified transformation ports. Select a target in a mapping to view details for each port in the selected target definition. Displays connection properties for each source connection associated with the session. Select a mapping to view sources. 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 workflow to view information for tasks and objects associated with the selected workflow. Displays properties for each session in the folder. Select a task to view the task details. Select a static deployment group to view details for deployment group objects. and other objects associated with the worklet. Displays properties for each worklet in the folder. Select a session to view session logs. and transformations used in the mapping. Select a target definition to view details for each target definition port. tasks. Displays the properties for each reusable transformation in the selected node. 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. targets. Select a worklet to view the nodes for sessions. Displays workflow log information for the selected workflow.and post-session email and commands. Displays the properties for each source within the selected node. source connections and target connections nodes for the selected session. The Target Connections node displays under each session in the Sessions node and under each session associated with a workflow under the Workflows node. Displays the properties for each mapplet in the selected node. Displays properties for each task in the selected node. Select a mapplet to view the Transformations node containing the mapplet. The Main window also displays information about pre. Select a source definition to view details for each port in the selected source definition.Table 2-1 shows the object details displayed in the Repository Manager Main window: Table 2-1. Displays the properties for each target with the selected node. Displays properties for each deployment group in the selected repository. 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. 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 . Displays properties for each source file associated with the session. Displays session log information for the selected session. Displays the properties for each mapping in the node. and transformation nodes that contain the sources. The Workflow Logs node displays under each workflow in the Workflows node.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Host name for the machine hosting the object. comments. 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. Status of object as reusable. and label information associated with the object. To save the list of dependent objects as an HTML file. Object Dependencies Saved as HTML Viewing Object Dependencies 41 .Table 2-4. choose File-Save to File. The Labels window displays labels associated with the object and information associated with the label object. Name of the user who purged the object. User who created the object. Status of object deletion. Yes or No. Repository hosting the object. Type of checkout for object. The Output window displays validation information. and the Comments window displays text entered during object check in or check out. Persistent or Non-Persistent. The View Dependencies window also displays output. Yes or No. Figure 2-8 shows an example of the HTML file saved from a View Dependencies window: Figure 2-8.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

or restoring the repository. Click OK. If you are restoring a repository.To skip information when copying. 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. Note: You can optimize repository performance for repositories on IBM DB2 EEE. For more information. Select the data you want to skip. Click the Advanced button on the Copy From Another Repository dialog box. Tuning Repository Performance 61 . follow the steps to copy a repository in “Copying a Repository” on page 62. 2. backing up. follow the steps to restore a repository in “Restoring a Repository” on page 67. If you are backing up repository. and continue copying. backing up. 4. 3. If you are copying a repository. or restoring a repository: 1. Backup Repository dialog box. or Restore Repository dialog box.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3. 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. 7. 6. If you want to register a local repository managed by a different Repository Server. the host name of the Repository Server. Choose the global repository from the global repository list. 8. Enter the repository user name and password for the local repository. and enter your repository user name and password. choose Managed By a Different Repository Server and enter the name of the local repository.The Register Repositories dialog box appears. Click Close. 76 Chapter 3: Managing the Repository . and the port number the Repository Server uses for connections. 5. Click Register. If you want to register a local repository managed by the same 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. and stop the repository. Connect to the target Repository Server. Remove the repository configuration from the existing Repository Server. 6. and start the repository. 3. Select the repository configuration under the new Repository Server. move and propagate each repository completely before moving another repository. you must propagate domain connectivity information for the repository. Migrating the Repository to a Different Repository Server 77 . For details. 5. and add a repository configuration. see “Propagating Repository Domain Connection Information” on page 78. 4. For details. Connect to the Repository Server hosting the repository. see “Connecting to the Repository Server” on page 58 and “Stopping the Repository” on page 72. 2. For details. Use the following steps to migrate a repository to a different Repository Server: 1. see “Starting the Repository” on page 71. and import the configuration into the target Repository Server. propagate domain connectivity information for the repository.Migrating the Repository to a Different Repository Server You can change the Repository Server that manages a repository. For details. You can also export the repository configuration from the existing Repository Server. The repository contacts other repositories in the domain and updates the domain connectivity information. If you want to migrate a repository that is in a domain. For details on propagating domain connectivity information. For details. If you want to move multiple repositories in a domain to different Repository Servers. see “Propagating Repository Domain Connection Information” on page 78. see “Removing a Repository Configuration” on page 114. see “Exporting and Importing Repository Configurations” on page 115. If the repository you are moving is in a domain.

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

Table 3-5 describes the repository user connection details: Table 3-5. Viewing Connection Details in the Repository Manager Use the following procedure to view connection details in the Repository Manager. Launch the Repository Manager and connect to the repository. The repository client application associated with the connection. The port number the machine hosting the repository client application uses to communicate with the repository. The identification number assigned to the repository 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. The time of the last metadata transaction between the repository client application and the repository. Viewing User Connections and Locks 79 . 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. To view user connection details: 1. The time the user connected to the repository. The TCP/IP address of the machine associated with the connection.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 name of the machine running the application.

The Administration Console displays the repository user connection details in the Main window: 2.2. and select the Connections node. Choose Edit-Show User Connections. click on the column name. select the repository containing the user connections you want to view. Viewing Locks You can view locks and identify residual locks in the Repository Manager or in the Administration Console. In the Console Tree. 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. To sort the connections by column. click on the column name. 80 Chapter 3: Managing the Repository . 3. To sort the connections by column. To view user connection details: 1.

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

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

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

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

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

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

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

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_51008 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized request dispatcher. INFO : SF_34002 [Fri Jul 16 09:16:46 2004] : (1324|1452) Server starting up. INFO : REP_51007 [Fri Jul 16 09:37:33 2004] : (1396|1952) Repository runtime manager initialized. INFO : REP_51005 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized database connection information. to ensure you are viewing the true message code.When you configure the Repository Server to write Trace or Debug severity level messages to the Repository Server log file. since some message codes are embedded within other codes. the file can grow to contain a large number of entries. Messages sent from the Repository Server display PmRepServer in the Source column. 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. 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. you must view the text of the message. 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. the messages appear in the Application Log component of the Windows Event Viewer. Sample Application Log If you configure the Repository Server to log messages in the event log. Reading the Repository Log Files 99 . However. INFO : REP_51006 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized configuration information. Database : penguin@production. 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. INFO : SF_34012 : (1324|1452) Opened Server Port [5001] to listen for client connections. INFO : SF_34003 [Fri Jul 16 09:16:47 2004] : (1324|1452) Server initialization completed. 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.

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

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

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

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

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

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

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

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

108 Chapter 4: Configuring the Repository . Enter the network information. Click the Network tab.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. Default is 3. Default is 3. 5. Number of seconds the Repository Server waits while sending a message to a client application before timing out. New Repository .4. Table 4-3 describes the options available on the Network tab: Table 4-3.

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

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

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

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

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

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

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

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

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

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

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

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

Working with PowerCenter Licenses 121 . or if the file contains an invalid or expired product license key. When you start a repository. add them to the license file after you add the product license key. If the Repository Server cannot find the license file. < > \ | \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. For more information on adding license keys to the repository license file. the Repository Server verifies that the license file exists in the Repository Server installation directory. If you have option or connectivity license keys. see “Adding a Repository Configuration” on page 105. it fails to start the repository. Converting Special Characters in Repository License File Names Special Character in Repository Name ! % ^ & * ( ) [ ] { } ' " .Table 4-5. : / ? .

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. To view user connection details: 1. The name of the machine running the application. The Repository Manager also allows you to terminate user connections. The TCP/IP address of the machine associated with the connection. The repository client application associated with the connection. Click Close to return to the Repository Manager.Managing User Connections The Repository Manager allows you to view the connection details for users connected to the repository. Table 5-5 describes the properties in the Repository Connections dialog box: Table 5-5. The Repository Connections dialog box appears. The time of the last metadata transaction between the repository client application and the repository. Launch the Repository Manager and connect to the repository. Choose Edit-Show User Connections. 2. 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. 3. The time the user connected to the repository. Managing User Connections 151 . The identification number assigned to the repository connection.

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

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

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

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

156 Chapter 5: Repository Security . The Repository Server releases a lock when you choose Repository-Save. if Finance is the root directory of your tree. with General Ledger and Accounts Receivable as subdirectories. 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. You can use the Show Locks feature to see if the business component or objects it points to are locked. For details. see “Handling Locks” on page 157.

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

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

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

The simplest way to prevent security breaches is to limit the number of users accessing the repository. the easier it is to maintain. Once you establish separate groups. determine how many types of users access the repository. The more distinct your user groups.Tips When setting up repository security. Do not use shared accounts. you can create appropriate user groups. limit the ability of other repository users to perform unnecessary actions. 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. The repository creates locks on objects in use. 160 Chapter 5: Repository Security . and limit folder permissions. Create groups with limited privileges. but the simpler the configuration. keep it simple. assign the appropriate privileges to those groups and design folder permissions to allow their access to particular folders. such as running sessions or administering the repository. the tighter your repository security. limit privileges. To do this. You have the tools to create a complex web of security. Then create separate user groups for each type. across all folders? Before implementing security measures. answer the following questions: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ After you evaluate the needs of the repository users. Using shared accounts negates the usefulness of the repository locking feature. Breaking a valid lock can cause repository and inconsistencies. Then. To avoid repository inconsistencies: ♦ Do not use shared accounts.

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

For details. The folder appears in the Navigator. If the folder is shared. This option applies to versioned repositories only. see “Permissions” on page 168. 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. 172 Chapter 6: Working with Folders . Only groups to which the owner belongs can be selected. Description of the folder that appears in the Repository Manager. Owner of the folder. The status applied to all objects in the folder. Folder permissions for users in the repository. For more information on object status. Any user in the repository can be the folder owner.2. the folder displays an open hand icon. Click OK. If selected. Choose Folder-Create. makes the folder shared.

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

You must also have privileges to access the repositories containing the folders. If you use a versioned repository. Table 6-2 lists the object types and attributes you can compare: Table 6-2. 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 . You can specify the object types to compare and display between folders. You can also compare two objects of the same type using Compare Objects. see “Comparing Objects” in the Designer Guide. You must have read permission for each folder you want to compare. The 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.Comparing Folders Before you copy or replace a folder in a repository. Direction of comparison. Compared Attributes and Object Differentiation The Compare Folders Wizard compares objects based on specific object attributes. You can specify either one-way or two-way comparisons. The wizard performs directional comparisons. The Repository Manager lets you quickly and accurately compare the objects in different folders using the Compare Folders Wizard. Compare objects between two folders in different repositories. See Table 6-2 on page 174 for a list of compared attributes for object types. A directional comparison checks the contents of one folder against the contents of the other. you might want to verify the contents of a folder or compare it with other folders. the Repository Manager uses the latest checked in version of an object for comparison. Object types to compare. 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. For more information on Compare Objects.

Table 6-2. 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 . 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. regardless of whether you select the other objects to compare.

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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

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. Referenced Shortcut Object Original Object Location Note: If you move or delete an object referenced by a shortcut.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

you might group objects for deployment on a certain date and deploy all objects at once. You manually add or delete objects from a static deployment group. In the View History window. Select to deploy all child dependencies. You can add checked in objects to a static deployment group from the Repository Manager. choose Tools-Add to deployment group. see “Copying Folders and Deployment Groups” on page 241. For information on deploying groups to a repository. Select to deploy non-reusable dependent child objects. Dependency for Deployment Group Dialog Box When you select All Dependencies. select the group of objects in the Navigator and drag them into the deployment group. Non-reusable. No dependencies. To add objects from the Query Results or View History windows. For example. To add several 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. Working with Deployment Groups 239 . You cannot add checked out objects to a deployment group. In the Repository Manager. 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. You can specify the following conditions for adding child dependencies: ♦ ♦ ♦ All dependencies. Select to skip deploying dependent objects. When you add objects to a static deployment group. you add all dependent objects to the static 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. right-click an object in the Navigator or in a detail window. and choose Versioning-View History. choose Tools-Add to deployment group. 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.

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

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

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

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

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

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

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

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

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

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

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

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

Lists all FTP connections in the folder. Choose to retain persisted values. 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 . If the target repository contains less than two PowerCenter Servers. Choose to retain the assigned PowerCenter Server information for workflows and sessions configured to run on specific PowerCenter Servers in a server grid. Lists all external loader connections in the folder. Lists local shared folders in the target repository that you need to copy first. Copy dependency information for objects in mappings. indicating the connections for which you do not have read permission. the wizard skips this step. Choose to copy workflow logs if they exist. it appends the date to the original folder name. Lists global shared folders in the target repository that you need to copy first. Copy persisted values for workflow variables. 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. indicating the connections for which you do not have read permission. if it exists. click Cancel and copy all listed local shared folders before copying the folder. indicating the connections for which you do not have read permission. Rename the target folder if a folder of the same name exists in the target repository. choose to retain persisted values for mapping variables. indicating the connections for which you do not have read permission. Lists all application connections in the folder. Choose to retain existing workflow logs in the target folder if you choose not to copy workflow logs from the source folder.Table 10-1. Lists all database connections in the folder. To preserve shortcuts and prevent invalid mappings. Otherwise. To preserve shortcuts and prevent invalid mappings. Lists all MQ connections in the folder. Allows you to select a PowerCenter Server to run all nonassociated workflows. click Cancel and copy all listed local shared folders before copying the folder. Lists plug-in application information upon which the source folder depends if the plug-in information does not exist in the target repository.

If there are differences between the folders. Lists the results from the folder compare. a message warns you that shortcuts to missing objects will be removed. click Cancel and copy all listed local shared folders before copying 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. Allows you to compare folders if the folders you choose in Override Shared Folder dialog box are different. Also lists the folder that contains shortcuts and the folder to which you can establish shortcuts. Displays objects that exist in the local shared folder but not in the global shared folder. To preserve shortcuts and prevent invalid mappings. You can choose to accept or override the shared folder.Table 10-1. The wizard takes you back to Select Shared Folders dialog box. Select Shared Folders Advanced Override Shared Folder Advanced Compare Shared Folder Compare Results Advanced Advanced Copying or Replacing a Folder 253 . Lists all dependent local and global shared folders. Also displays objects that are older or newer than matching objects in the global shared folder. 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.

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

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

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

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

For example. you might want to move a label from the last version to the latest version before you deploy an object. Clear the static deployment group when you finish copying.Table 10-2 describes the status an object may take after copying the deployment group. You can apply labels to the deployment group objects in the source and target repositories. For example. Apply labels to source and target objects. Also. The repository stores a deployment history for each deployment group. You can remove the copied objects from a static deployment group when you finish copying them into the target repository. It also allows you to perform the following tasks: ♦ ♦ Choose deployment folders. 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. You can move labels from version to version in source and target repositories. Or. You can choose the specific folders in the target repository you want to deploy. 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. 258 Chapter 10: Copying Folders and Deployment Groups . For details on viewing a deployment history. verify that existing objects in the target repository are not checked out or locked. Move labels. associated non-reusable objects also have a deleted status. copy dependent shared folders for shortcuts in the deployment group. 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. see “Working with Deployment Groups” on page 236. Before you copy a deployment group. depending on the status of the source and target objects: Table 10-2. If a parent composite object has a deleted status. Steps for Copying a Deployment Group Use the Copy Deployment Group Wizard to copy objects in a deployment group. The Copy Deployment Group Wizard allows you to perform all of the tasks listed in “Using the Copy Wizards” on page 244.

2. The Copy Deployment Group Wizard dialog box prompts you to select a mode: ♦ ♦ Typical. Choose to remove objects from the deployment group after the wizard completes the deployment operation. You can override the defaults for shortcuts to local and global shared folders. The wizard might have to determine how the folders are related before establishing shortcuts. Copy dependency information for objects in mappings. The Copy Deployment Group Wizard appears. Choose to retain persisted values. Choose to retain persisted values for mapping variables. 5. Table 10-3 lists the dialog boxes and prompts that you may see when you copy a deployment group: Table 10-3. The wizard uses the defaults for shortcuts to local and global shared folders. displaying the folder name and target repository name. click Cancel. Connect to the source and target repositories. Advanced.Use the following steps as a guideline when you copy a deployment group. Select the folders you want to compare. Select the deployment group to copy. The wizard rolls back all changes. Click Next. Select a label in the source repository to apply to the copied object versions. Override the default selections for deployment folders. 4. and select a label in the target repository to apply to the newly created object versions. if they exist. Click and drag or paste the deployment group to the target repository. Choose to retain current values for Sequence Generator and Normalizer transformations. To stop the replacement. 3. 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 Wizard prompts you for more information based on the content of the folders and the copy mode you selected. To copy a deployment group: 1. 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. You can choose the shared folders to associate shortcuts.

If the target repository contains less than two PowerCenter Servers. click Cancel and copy all listed local shared folders before copying the folder. Lists all FTP connections in the folder. Lists local shared folders in the target repository that you need to copy first. Lists outdated folders in the target repository that you need to copy first. 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. click Cancel and copy all listed local shared folders before copying 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. Lists all dependent local and global shared folders. Also lists the folder that contains shortcuts and the folder to which you can establish shortcuts.Table 10-3. Lists all application connections in the folder. To preserve shortcuts and prevent invalid mappings. To preserve shortcuts and prevent invalid mappings. 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 . indicating the connections for which you do not have read permission. Lists all database connections in the folder. indicating the connections for which you do not have read permission. Lists all external loader connections in the folder. Lists plug-in application information upon which the source folder depends if the plug-in information does not exist in the target repository. the wizard skips this step. Allows you to select a PowerCenter Server to run all nonassociated workflows. indicating the connections for which you do not have read permission. You can choose to accept or override the shared folder. Lists all MQ 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.

Table 10-3. 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. Also displays objects that are older or newer than matching objects in the global shared folder. Displays objects that exist in the local shared folder but not in the global shared folder. The wizard takes you back to Select Shared Folders dialog box. Lists the results from the folder compare. Copying a Deployment Group 261 . If there are differences between the folders. a message warns you that shortcuts to missing objects will be removed.

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

If the two repository code pages are not compatible. Permissions and Privileges To export and import repository objects. The code page of the originating repository must be a subset of the destination repository code page. Table 11-1 lists the permissions and privileges you need to export and import objects: Table 11-1. you must have the proper folder permissions and user privileges. you export an Advanced External Procedure transformation from an earlier repository version. see “Globalization Overview” and “Code Pages” in the Installation and Configuration Guide. 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. see “Upgrading Repository Metadata” in the Installation and Configuration Guide. The PowerCenter Client imports the transformation and changes it to a Custom transformation. 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. The permissions and privileges required to import and export objects change depending on whether you are using the Designer. You import the transformation in the current repository version. Workflow Manager. For example. For details on code page compatibility. 266 Chapter 11: Exporting and Importing Objects . the PowerCenter Client displays an error message and does not import any object. the PowerCenter Client only allows you to export and import objects between repositories with compatible code pages.When you import an object exported from an earlier repository version. or Repository Manager.

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

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

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

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

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

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

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

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

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

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

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

Table 11-5. The Create New column indicates which objects you can define directly in the XML file and then import. 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.

Table 11-5. 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 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

the Import Wizard proceeds with the import process. 294 Chapter 11: Exporting and Importing Objects . When you resolve conflicts for all objects in all folders. the Import Wizard displays the status of that folder as unresolved. Note: If you cancel the Conflict Resolution Wizard for a folder. You can click View/Edit to view or edit the object conflicts for the objects in that folder.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.

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

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

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

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

Next Conflict/Option displays only with session or workflow conflicts that you resolve by renaming or replacing the target. 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. Displays the elected resolution or a list of choices for resolution. For more information.It displays a red icon next to each object with a conflict. and action taken to resolve the conflict. existing conflicts. Identifies the current conflict and the name of the object with the conflict.Table 12-1 describes the areas of the Copy Wizard: Table 12-1. After you choose a resolution. Displays object dependencies for the current object. original instance name. Enables you to edit the object name if you choose to rename the object. Compares duplicate objects in the target folder to the objects you are copying. Choices might be different. see “Viewing Object Dependencies” on page 305. and a green icon next to each object without a conflict. such as applying default connections or retaining server connections during the copy. depending on the conflict. For more information. Overview 299 . Displays the items to copy. see “Comparing Repository Objects” on page 45. 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. Applies the resolution to all unresolved conflicts or just the conflicts for the same object type. the message describes the resolution. target instance name. if any.

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

Resolving Copy Conflicts 301 . Copy Wizard Resolutions The wizard prompts you to select a resolution for each unresolved object in your copy. Optionally. you can apply the resolution to all unresolved objects of the same type. Figure 12-2. click Apply This Resolution To and choose either All Conflicts or conflicts for just the specified object type. The selected resolution reuses the object. To apply the resolution to more objects.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.

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

You cannot export shortcuts. However. Overview 315 . You can import multiple source and target definitions at a time. the Repository Agent also exports the source or target containing the corresponding primary key. You cannot export source and target definitions at the same time. you can export targets to some tools as dimensions. see “Working with PowerCenter Licenses” on page 119.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. You cannot export cubes and dimensions. For more information on licenses. You must have a Metadata Exchange option license key to exchange metadata for a specific tool. When you export a source or target with a foreign key. You can export multiple source definitions or multiple target definitions at a time.

Choose the target tool you want to export the object to. and choose Repository-Export Metadata. In the Repository Manager Navigator. To export metadata: 1. 316 Chapter 13: Exchanging Metadata . You can click More Info to read about the tool requirements. Choose a path and file name. 2. 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. select the object or objects you want to export.

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

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

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

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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. Click Done. the Repository Manager grants Share Read permission as well. Specifies whether the metadata extension is visible in vendor domains. the Repository Manager grants Client Visible permission as well. Specifies whether the value of the metadata extension is editable in PowerCenter. If you select this option. Specifies whether the metadata extension is visible in PowerCenter. Optional description of the metadata extension. Optional Click Create. 7. Specifies whether the value of the metadata extension is editable across vendor domains. If you enable Share Write permission. Specifies whether the metadata extension is private to the domain in which it is created.Table 14-1. 330 Chapter 14: Metadata Extensions . The Repository Manager enables this option when third-party application vendors create vendor-defined metadata extensions only. Share Read Share Write Optional Optional Private Optional Description 6.

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

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

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

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

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

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

sq_ termxdrp. Integrating MX Views with Third-Party Software With MX software and support from Informatica. called Metadata Exchange SDK.Table 15-3. from pulling the Informatica metadata into product or user repositories to providing dynamic desktop pass-through access. Viewing the Repository Metadata 337 .sq_ These SQL scripts are stored in the PowerCenter Repository Server installation directory. 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. Software vendors can integrate Informatica metadata with their products through different methods. The next generation of MX. provides an object-based Application Programming Interface (API) to read and write metadata in Informatica repositories.

Version ID of the source. flat file or RDBMS. 338 Chapter 15: Using Metadata Exchange (MX) Views . Informatica recommends using the fields in bold to join views. A database definition includes the source database names. Folder name. Source of the definition. and the folder where the database definition resides. REP_DATABASE_DEFS Table 15-4 lists database definition details: Table 15-4.Database Definition View The database definition view provides a list of all database definitions in the repository. MX provides the REP_DATABASE_DEFS view to help you analyze database definitions. 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.

see “REP_ALL_SOURCES” on page 339. see “REP_ALL_SOURCE_FLDS” on page 341. Name of the parent source Business name of the parent source. and mappings and mapplets where these sources are used. see “REP_SRC_TBLS” on page 344. creation date. see “REP_SRC_FILES” on page 343. see “REP_SRC_TBL_FLDS” on page 346. source metadata extensions. Source definitions can be defined for both relational and nonrelational sources. For more information. column properties. For more information. Folder ID. Table 15-6 lists source information in the REP_ALL_SOURCES view: Table 15-6. For more information. These views provide access to the fields in a non-relational source. 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. Source Views 339 . You can use the source name to retrieve all the fields belonging to the source. They also provide information such as source columns. This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View. 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. 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.Source Views Source views provide a list of the latest version of all source definitions defined by folder of any PowerCenter repository. description. 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. version. These views also show source properties such as shortcuts. For more information. This view provides a list of all file definitions in the repository. and business name. see “REP_SRC_FILE_FLDS and REP_SEG_FLDS” on page 345. This view provides access to the fields in relational sources. Sources include both relational sources and non-relational sources such as XML files and flat files. Table 15-5 lists the different views that help you analyze source metadata: Table 15-5. For more information. For more information.

UTC time for source checkin. UTC time when the parent source was last modified. Folder ID. Parent source display size (uncompressed binary). 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. Time when the parent source was last modified. UTC time when the source display was last saved. Specifies whether the source version is active or has been deleted. Source name.Table 15-6. Physical size (compressed binary). Time when the source was last saved. Parent source physical size (compressed binary). Name of the database type of the parent source. Folder name. Source description. Database name of the parent source. UTC time (Coordinated Universal Time) when the parent source was checked in. Parent source version status. ID of the first field in the source. Description of the parent source. 340 Chapter 15: Using Metadata Exchange (MX) Views . Source version number. File organization information. Name of the source schema. Specifies whether the source is a relational or a non-relational source. Source ID.

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. the names of shortcut and the parent targets display. Business name of the parent source. UTC time when the parent source was last saved. 1 = shortcut. Version number of the parent source. Informatica recommends using the fields in bold to join views. Parent source name.Table 15-6. Specifies whether the source is a shortcut. REP_ALL_SOURCE_FLDS This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View. Status of the parent source version. Time when the parent source was last modified. Database type of the parent source. 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. Parent source ID. Specifies whether the source is a global shortcut. Source type such as relational database or flat file. The repository name. 0 = not a shortcut. 0 = not a shortcut. the name of the shortcut displays. Source Views 341 . For local shortcuts. For global shortcuts. Database name of the parent source. Description of the parent source. 1 = shortcut. UTC time when the parent source was checked in. Parent folder ID. Table 15-7 lists source field information in the REP_ALL_SOURCE_FLDS view: Table 15-7.

UTC time when the source was last checked in. Picture text that a COBOL source uses. Field level number for non-relational sources. Description of the source field. Specifies whether the source version is active or has been deleted. Source name. Source ID. Offset of this field within the source. The next child. Time when the source was last saved. Source description. 342 Chapter 15: Using Metadata Exchange (MX) Views . UTC time when the source was last saved. Identifies the field/record that this field/ record redefines. Business name of the source field. Null for relational sources. Name of the database for the source. Source field number. ID of the field that follows the current field. Physical field length. Offset of this field within this FD.Table 15-7. 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. Folder ID. ID of the source field (primary key). for a non-relational COBOL source. if any. Source version number. Source field name. Display field length. Number of time that the field (or record) occurs in the source.

Specifies whether nulls are allows. 1 = shortcut. 0 = not a shortcut. Physical size (compressed binary). Source Views 343 . Specifies whether the source is a global 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). Minimum physical size (varying records). Any flat file imported through the Source Analyzer has an entry.Table 15-7. 0 = not a shortcut. Name of database extracted from (DSN). Table 15-8 lists file information in the REP_SRC_FILES view: Table 15-8. Display size (uncompressed). REP_SRC_FILES This view provides a list of all file definitions in the repository. Source field picture usage name. 1 = nulls not allowed. Informatica recommends using the fields in bold to join views. Length or precision for the field. 0= nulls allowed. 1 = shortcut. Type of database extracted from. Folder name. Repository name. File organization information. Specifies whether the source is a shortcut. Field datatype. Name of file definitions. 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. Scale for the field. 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. File from which schema was extracted.

Source version number.Table 15-8. Unique key. Source description. Type of database extracted from. 344 Chapter 15: Using Metadata Exchange (MX) Views . 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. Last time the source table was saved. Table 15-9 lists relational database table information in the REP_SRC_TBLS view: Table 15-9. Name of database extracted from. Folder version name. Link to first field. Source description. 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. 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. Source version number. Folder ID. Informatica recommends using the fields in bold to join views. Informatica recommends using the fields in bold to join views. Version ID. Name of schema extracted from. Business name of the table. Folder name.

1 = primary key. 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). Source Views 345 . COMP type (binary compressed fields). Decimal precision for numeric fields or field length for CHAR fields. Version ID of the source. Physical length. 02). Number of OCCURS. Folder name. Comments for this field. Source ID (primary key). Display length. Link to next field at this level. 01. Field name. Each field is contained in the scanned tables listed in the REP_SEG_FLDS view.. 0 = not a key. PIC clause.e. Field level (i. Link to child field if this is a group item. Physical offset. Decimal scale for numeric fields. Key type. Table 15-10 lists source field information in the REP_SRC_FILE_FLDS and REP_SEG_FLDS views: Table 15-10. Order number of the field. Informatica recommends using the fields in bold to join views.REP_SRC_FILE_FLDS and REP_SEG_FLDS These views provide access to the fields in a non-relational source. Redefines this field. Offset using display length.

Decimal scale for numeric fields. Folder version name. Informatica recommends using the fields in bold to join views. Source version number. Source table ID. You can use the source name to retrieve all the fields belonging to the source. The columns in this view are part of the tables listed in the REP_SRC_TBLS views. Order number of the column. Business name of the table. Folder ID. Business name of the field. Data type for this column. Link to next field in source table. Key type for this column. 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. Table name. Folder name. Folder version ID.REP_SRC_TBL_FLDS This view provides access to the fields in relational sources. 346 Chapter 15: Using Metadata Exchange (MX) Views . Field ID (primary key). Table 15-11 lists relational source fields in the REP_SRC_TBL_FLDS view: Table 15-11. Description of the column.

FIRST_COLUMN_ID is a link to the set of columns for this table. see “REP_ALL_TARGET_FIELDS” on page 349. These views also show target properties such as shortcuts. Target ID (primary key). Target description. creation date. Table 15-12 lists the different views that help you analyze target metadata: Table 15-12. and mappings and mapplets where these target are used. For more information. target metadata extensions. This view provides the properties of columns defined for the target tables in a data warehouse or data mart. For local shortcuts. This view provides a list of targets in the repository. 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. Table 15-13 lists target details in the REP_ALL_TARGETS view: Table 15-13. Target Views 347 . For more information. Targets include both relational and non-relational targets such as XML files and flat files. For more information. see “REP_ALL_TARGETS” on page 347. Business name for the target. Target version number. column properties. see “REP_TARG_TBLS” on page 350. and business name. the name of the shortcut displays.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. see “REP_TARG_TBL_COLS” on page 351. They also provide information such as target columns. version. 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. For more information. This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. Folder ID. For global shortcuts. the names of shortcut and the parent targets display. 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 name. description.

Specifies whether the target is a global shortcut. Options for use when generating DDL. Status of the target version. ID for the parent target file. UTC time (Coordinated Universal Time) when the parent target was checked in. Time when the target was last modified. Target version number. Repository name. Target ID. UTC time (Coordinated Universal Time) when the target was last checked in. Target name. Specifies whether the target is a shortcut. Folder ID. UTC time when the target was last saved. Informatica recommends using the fields in bold to join views. Link to first field of this table. Database type for the parent target. Time when the target was last saved.Table 15-13. Folder name. 1 = shortcut. 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. User-specified constraint string used when the DDL is generated. UTC time when the target was last saved. 1 = shortcut. 348 Chapter 15: Using Metadata Exchange (MX) Views . 0 = not a shortcut. Target description. Link to first field of this table. 0 = not a shortcut.

ID of parent target file. Time when target was last modified. For global shortcuts. UTC time when the target was last checked in. Target name. Description of parent target. For local shortcuts. ID of the first field of parent target. the shortcut name displays. the names of the shortcut and the parent targets display. Target version number.REP_ALL_TARGET_FIELDS This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. Target version number. Target Views 349 . Parent target ID. Status of the target version. Table 15-14 lists target field data in the REP_ALL_TARGET_FIELDS view: Table 15-14. Target ID. Folder ID. UTC time when the parent target was last saved. Time when the parent target was last modified. Status of the parent target version. Database type of parent target. UTC time (Coordinated Universal Time) when the parent target was last checked in. Folder name. 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 ID. Business name of the parent target. UTC time when the target was last saved. Name of parent target. Target description.

Datatype group codes. Scale for target field. Specifies whether target field is null. 1 = shortcut. 0 = not a shortcut. Target field number. Link to source from which this field was created. Repository name. ID of the next field in target. 1 = shortcut. Key type of target field. Picture text that COBOL sources use. REP_TARG_TBLS This view provides a list of targets in the repository. and Bigint Precision for target field. Business name of target field. It is the primary table list used to delineate a PowerCenter data model. String. 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. Money. not physically created. 350 Chapter 15: Using Metadata Exchange (MX) Views . Specifies whether the target is a shortcut. Specifies whether the target is a global shortcut. FIRST_COLUMN_ID is a link to the set of columns for this table. 0 = not a shortcut.Table 15-14. Therefore. Datatype of target field. B = Binary and Bit C = Character. The tables are virtual. Description of target field. verify that the table exists before using this view. Text. 0 = Null. 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. and Byte D = Date N = Numeric. All tables contained in the target table model are part of this view. Target field ID. 1 = Not Null.

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. Link to first index. Column name. 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. Description of the table. Folder version name. Business name of the table. Link to first field of this table. Time target table was last saved. Folder version ID. Folder ID. Order number of the column. Target Views 351 . Business name of this column. Table ID. Table this column belongs to. Table creation options specified in the Warehouse Designer. Table 15-16 lists target table column properties for the REP_TARG_TBL_COLS view: Table 15-16. Column ID (primary key). Informatica recommends using the fields in bold to join views. Table business name.Table 15-15 lists the columns in the REP_TARG_TBLS view: Table 15-15. Table constraint specified in Warehouse Designer. Target version number. REP_TARG_TBL_COLS This view provides the properties of columns defined for the target tables in a data warehouse or data mart. Table name.

Datatype group. Column description. Link to source this column was created from. Decimal scale for numeric columns. 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. Primary and Foreign Key. Link to next column. Not a Key. 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. 352 Chapter 15: Using Metadata Exchange (MX) Views . Whether NULLs are accepted.Table 15-16. C = Character D = Date N = Numeric Decimal precision for numeric fields or field length for CHAR fields. Target version number. Primary Key. Native database datatype. Folder version name. Foreign Key.

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

Name of mapping. UTC time when the mapping was checked in. Time when the mapping was last saved. 0 = not a shortcut. The UTC time when mapping was last saved. Sequence ID of the parent mapping. Folder ID. Repository name.REP_ALL_MAPPINGS This view provides a list of the latest version of all mappings defined in each folder of a repository. Specifies whether the parent mapping is valid. the names of the shortcut and the parent mappings display. Table 15-18 lists mapping information in the REP_ALL_MAPPINGS view: Table 15-18. Mapping description. the name of the shortcut displays. UTC time when the mapping was last saved. 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. Folder name. Parent mapping description. UTC time (Coordinated Universal Time) when the parent mapping was checked in. Mapping version number. Specifies whether the mapping is a global shortcut. Parent mapping version number. Status of the mapping version. 1 = shortcut. Sequence ID for mapping. For global shortcuts. Name of the parent mapping. For local shortcuts. Date and time when parent mapping was last saved. Parent mapping version status. 354 Chapter 15: Using Metadata Exchange (MX) Views . Parent folder ID.

The UTC time when mapplet was last saved. UTC time when the mapplet was last saved. UTC time (Coordinated Universal Time) when the parent mapplet was checked in. the names of the shortcut and the parent mapplets display. Name of mapplet. 1 = shortcut. Mapplet version number. Parent mapplet version status. REP_ALL_MAPPLETS This view provides a list of the latest version of all mapplets defined in each folder of a repository. 0 = not a shortcut. Name of parent mapplet. Specifies whether the parent mapplet is valid. Parent folder ID. Folder name. Status of the mapplet version. Table 15-19 lists mapplet metadata in the REP_ALL_MAPPLETS view: Table 15-19. Mapping and Mapplet Views 355 . For local shortcuts. Field ID (primary key). the name of the shortcut displays. For global shortcuts. The date and time when parent mapplet was last saved. Sequence ID of parent mapplet. Informatica recommends using the fields in bold to join views. UTC time when the mapplet was checked in. 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. Time when the mapplet was last saved. Parent mapplet description. Folder ID. Mapplet ID. REP_ALL_MAPPINGS MX View Column Name IS_SHORTCUT Datatype NUMBER Description Specifies whether the mapping is a shortcut.Table 15-18.

It does not contain information about sources. 0 = not a shortcut. 356 Chapter 15: Using Metadata Exchange (MX) Views . 0 = not a shortcut. 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. This view pulls information from all the transformation objects that contribute to the target table in a valid mapping. Specifies whether the mapplet is a global shortcut. 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. Compound source filter condition. Specifies whether the mapplet is a shortcut. Folder name. Compound SQL override expression.Table 15-19. IS_SHORTCUT NUMBER Informatica recommends using the fields in bold to join views. Description of mapping. Description of transformation expression. Foreign key that points to generated mapplet transformation. 1 = shortcut. Folder version ID. Repository name. Table 15-20 lists expression information in the REP_TARG_MAPPING view: Table 15-20. Target business name. Note: Use the REP_TBL_MAPPING view to analyze source and target relationships. This view contains information about mappings defined for target tables only. Compound group by expression. Mapping name. 1 = shortcut. 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. REP_TARG_MAPPING This view provides access to the compound table-level transformation expressions for each target table. Folder version name.

Mapping version number. For details on the syntax of the transformation expression. Mapping and Mapplet Views 357 . Folder name. Table 15-21 lists expression metadata that you find in the REP_TARG_FLD_MAP view: Table 15-21. Target version number. 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. Business name of target field. End user comment. Mapping name. The field-level expression contains all the source fields (both file definition/non-relational source) that make up the value of the target field. see the Transformation Language Reference. Administrator comment. Folder version name. Business name of target table. Mapping comment. 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. Folder version ID. Mapping version number. There might be many mappings for a set of fields. Target version number. Informatica recommends using the fields in bold to join views. Time the mapping was saved last. each distinguished by the MAPPING_NAME field. This view pulls information from all transformation objects that contribute to the target table in a valid mapping. Name of target (table). 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).Table 15-20. Compound transformation expression.

Folder version ID. 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. Folder name. This is the companion view for the REP_TBL_MAPPING view. 358 Chapter 15: Using Metadata Exchange (MX) Views . Name of the target field.REP_FLD_MAPPING This view shows the source fields used by the target fields in a mapping. It contains both source and target column names and details. Administrator comment. Target field transformation expression. Name of the source table. Mapping version number. Business name of the source field. Target version number. Folder version name. Target name. Informatica recommends using the fields in bold to join views. Mapping ID. Source version number. Business name of the source table. Folder ID. Time the mapping was saved last. End user comment. Target table ID. Table 15-22 lists the source and target field metadata in the REP_FLD_MAPPING view: Table 15-22. Source table ID. Mapping comment. Business name of the target. Business name of the target column. Name of the mapping.

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

Table 15-24. Folder name. End user comment. Folder version ID. REP_TBL_MAPPING This view shows all of the target tables used in a mapping and provides source to target mapping information. Business 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. Time the mapping was saved last. Table 15-25 lists mapping target metadata in the REP_TBL_MAPPING view: Table 15-25. Mapping comment. 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. Field transformation expression. This view pulls information from all transformation objects that contribute to the target table in a valid mapping to provide the table-level expressions. Folder ID. 360 Chapter 15: Using Metadata Exchange (MX) Views . Compound target. Name of the mapping. Mapping version number. Target version number. Business name of the source table. Informatica recommends using the fields in bold to join views. Target ID. Folder name. Business name of the target. Target name. Source version number. Folder version name. Administrator comment. Source ID.

or through primary key-foreign key relationships. Mapping ID. Use this view to query the PowerCenter defined joins for a target table model. Name of first table in the join. Mapping version number. Time the mapping was saved last. Folder version name. Folder version ID. Source version number. REP_TARG_TBL_JOINS This view contains join information between target tables. Folder version name.Table 15-25. Mapping comment. ID of first table in the join. Description of transformation. 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. 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. Folder version ID. It is populated when you link fields in the Warehouse Designer. Target version number. Business name of column in first table. Compound group by clause. Table 15-26 lists target table join metadata in the REP_TARG_TBL_JOINS view: Table 15-26. Name of column in first table. Mapping and Mapplet Views 361 . Compound source filter condition. Informatica recommends using the fields in bold to join views. Compound SQL override expression. Business name of first table.

Source field name. and transformations in a mapping. ID of column in second table. Folder ID (primary key). Sequence ID for the mapping (primary key). Mapping version number. ID of column in first table. Business name of second table. Informatica recommends using the fields in bold to join views. Table1 version number. REP_MAPPING_UNCONN_PORTS This view displays the unconnected ports in sources. Table 15-27 lists unconnected port metadata in the REP_MAPPING_UNCONN_PORTS view: Table 15-27. Name of second table in the join. Unique ID for the instance in a mapping. Name of the instance. Source field ID (primary key). Object type name. Name of the mapping. 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. 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. 362 Chapter 15: Using Metadata Exchange (MX) Views . targets. Name of column in second table. Table2 version number.Table 15-26. Number of column in second table. ID of second table in the join. Business name of column in second table.

Mapping name. Target object type name. transformations. or transformation. Target object type such as port. Table 15-28 lists port-level connection metadata in the REP_MAPPING_PORT_CONN view: Table 15-28. Source object name. Unconnected transformations are not included. Mapping and Mapplet Views 363 . 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.Table 15-27. Target object ID. targets. Informatica recommends using the fields in bold to join views. Source object field name. Source object ID. Target object version number. Source object type. Target object field name. REP_MAPPING_PORT_CONN This view displays the port-level connections between the objects of a mapping. mapplet. target. Target object instance ID. Source object instance ID. Target object name. Name of the source object type. Sequence ID for the mapping (primary key). and mapplets. Source object version number. REP_MAPPING_UNCONN_PORTS MX View Column Name OBJECT_VERSION_NUMBER Datatype NUMBER Description Version number of the source. Informatica recommends using the fields in bold to join views. and transformation. Mapping version number. Folder name. target.

Unique name for a user-defined metadata domain. Folder ID. Datatype of the metadata extension value.Metadata Extension Views Metadata views allow you to see metadata extension details including reusable metadata extensions defined for objects in metadata extension domains. see “REP_METADATA_EXTNS” on page 364. Metadata extension value. For more information. Table 15-30 lists metadata extension information in the REP_METADATA_EXTNS view: Table 15-30. Line number of the text when there are multiple lines of text. REP_METADATA_EXTNS This view displays the details of all metadata extensions in the repository. 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. Name of the object type. Table 15-29 lists the different views that help you analyze metadata extensions metadata: Table 15-29. 364 Chapter 15: Using Metadata Exchange (MX) Views . 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. This view displays reusable metadata extensions defined for objects in metadata extension domains. Object the metadata value is associated with. Globally unique domain identifier. Metadata extension name. For more information. Object type the metadata is associated with. see “REP_METADATA_EXTN_DEFINES” on page 365. Object version number. Permissions type.

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

see “REP_WIDGET_FIELD” on page 369. This view displays the details of all transformation instances. 366 Chapter 15: Using Metadata Exchange (MX) Views . This view displays both reusable transformations defined in the Transformation Designer and transformation instances defined in mapping and mapplets. the names of the shortcut and the parent transformation display. For more information. It also shows all shortcut transformations in a folder. Table 15-32 lists the different views that help you analyze transformation metadata: Table 15-32. dependencies. and field level details of transformations. instances. see “REP_WIDGET_ATTR” on page 369. These views also display properties such as attributes. Name of the parent transformation. the name of the shortcut displays. Parent transformation ID (primary key). For more information. Folder ID. For local shortcuts. see “REP_WIDGET_DEP” on page 368. Table 15-33 lists transformation metadata in the REP_ALL_TRANFORMS view: Table 15-33. For more information. For global shortcuts. see “REP_WIDGET_INST” on page 368. 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. port-level connections. see “REP_ALL_TRANSFORMS” on page 366. This view displays the details of dependencies between transformation instances in a mapping. This view displays field level details for transformations. Folder name. Parent folder ID. and sessions. For more information. 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. For more information. 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.Transformation Views Transformation views display details of all reusable and non-reusable transformation instances by folder in a PowerCenter repository. This view displays attribute details for transformations.

Transformation description. IS_SHORTCUT NUMBER Informatica recommends using the fields in bold to join views. Specifies whether the transformation is a shortcut. Date and time when transformation was last saved. Specifies whether the transformation is a global shortcut. 0 = not a shortcut. Time when the transformation was last saved. 1= reusable. UTC time when the transformation was last saved. UTC time when the transformation was checked in. 1 = shortcut. Status of the parent transformation version. Transformation type ID. Specifies whether the transformation is reusable. Transformation ID.Table 15-33. Version number of the transformation. 0 = not reusable. Transformation Views 367 . 1 = shortcut. UTC time when the parent transformation was last saved. UTC time (Coordinated Universal Time) when the parent transformation was last checked in. Transformation type name. 0 = not a shortcut. Repository name. 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. Parent transformation description. Status of the transformation version. Name of the transformation.

Description of the transformation instance. REP_WIDGET_DEP This view displays the details of dependencies between transformation instances in a mapping. Transformation name. Version number of the mapping. Field ID of the source transformation instance. 368 Chapter 15: Using Metadata Exchange (MX) Views . Informatica recommends using the fields in bold to join views. Name of the transformation instance. Version number of the transformation. Transformation type. Table 15-35 lists transformation dependency information in the REP_WIDGET_DEP view: Table 15-35. ID of the transformation instance. Description of the transformation instance. Table 15-34 list transformation metadata in the REP_WIDGET_INST view: Table 15-34. Name of the transformation instance. Target field ID. Field ID of the target 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. Informatica recommends using the fields in bold to join views.REP_WIDGET_INST This view displays the details of all transformation instances. 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_ATTR This view displays attribute details for transformations. Table 15-36. and sessions. 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. Attribute ID. or transformation) version number. Attribute type. Attribute value. Session task ID. Partition ID. Table 15-37 lists transformation field information in the REP_WIDGET_FIELD view: Table 15-37. Description of the attribute. Transformation field precision. Instance ID. instances. Transformation field ID. Mapping ID. Attribute data type Attribute name. Transformation Views 369 . Informatica recommends using the fields in bold to join views. mapping. REP_WIDGET_FIELD This view displays field level details for transformations. Table 15-36 lists attribute details for transformations. Object (session. Used to break up long strings into multiple rows. and sessions. Transformation type. Transformation field name. Object type ID. instances. REP_WIDGET_FIELD MX View Column Name WIDGET_ID FIELD_NAME FIELD_ID WGT_PREC Datatype NUMBER VARCHAR2 (240) NUMBER NUMBER Description Transformation ID.

Expression type. Transformation field data type. Transformation version number. Transformation datatype of the port. Datatype group code. Expression name. Field-level property used by transformations. Informatica recommends using the fields in bold to join views. 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 . Default value of the transformation field. External database type. Comments on the field. Datatype number. Transformation port type. Transformation order. Source field ID for normalizer transformation. Comments on the expression. The ID of the corresponding instance in the mapplet's mapping.Table 15-37.

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

see “REP_SESS_LOG” on page 387. Start time configured for the scheduler. Workflow. This view contains information about the status of an individual session run against a target. REP_TASK_ATTR REP_SESS_LOG REP_SESS_TBL_LOG REP_WORKFLOWS This view contains information about individual workflows and workflow scheduling. see “REP_SESS_PARTITION_DEF” on page 385. For more information.Table 15-38. For more information. This view displays the list of tasks such as a command or an email for each session. see “REP_SESS_CONFIG_PARM” on page 385. the view displays two rows. see “REP_SESSION_FILES” on page 382. see “REP_SESSION_INSTANCE_FILES” on page 383. Workflow name. 372 Chapter 15: Using Metadata Exchange (MX) Views . 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. Scheduler associated with the workflow. For more information. This view contains information about the sources and targets used in a session. This view displays the attribute values and overridden values for session and workflow tasks. This view displays session configuration parameter details. see “REP_SESS_TBL_LOG” on page 388. see “REP_SESS_WIDGET_CNXS” on page 383. see “REP_SESSION_INSTANCES” on page 381. see “REP_TASK_ATTR” on page 386 This view provides log information about sessions. For more information. For more information. Worklet. targets. This view provides partition details of the sources. see “REP_COMPONENT” on page 384. Table 15-39 lists workflow and scheduling information in the REP_WORKFLOWS view: Table 15-39. 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. For more information. For more information. End time configured for the scheduler. For more information. For more information. This view contains file connections associated with reusable sessions. This view contains file connections associated with reusable sessions. If the session overrides a parameter in the configured object. and transformations in a session. For more information.

Records the following values for each schedule type: 1 = Run on demand. 4 = Run every DELTA_VALUE seconds. Folder ID. and Task Views 373 . 0 = invalid. Workflow. Records the following values for each stop condition option: 0 = End on a date. PowerCenter Server ID. Description of the workflow. The stop condition option for the workflow schedule type. 32 = Run continuously. Worklet. 8 = Customized repeat. Scheduler description. Scheduler ID. Date and time when the workflow was last saved. Specifies whether the workflow is valid or not. Workflow ID. 16 = Run on server initialization. Name of the PowerCenter server registered with the repository. 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. REP_WORKFLOWS MX View Column Name RUN_OPTIONS Datatype INTEGER Description The workflow schedule type. Workflow version number. 2 = Run forever. Specifies if scheduler is reusable. Number of times the PowerCenter Server runs the workflow before stopping the workflow. 1 = End after the number of runs stored in RUN_COUNT. 2 = Run once. Number of seconds the PowerCenter Server waits between successive workflow runs. 1 = valid.Table 15-39. Version number of the scheduler.

REP_ALL_SCHEDULERS This view displays a list of schedulers by folder. or session is valid. 0 = disabled. 1 = valid. Task type. 374 Chapter 15: Using Metadata Exchange (MX) Views . Values are: 1 = reusable. Task name. UTC time when task was last saved. Description of the task. 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. UTC checkin time. Version number of the task. Folder ID. Table 15-41 lists information in the REP_ALL_SCHEDULERS view: Table 15-41. 0 = not reusable. Start time configured for the object associated with the scheduler. Scheduler ID (primary key). Specifies whether the task is enabled or not. Table 15-40 lists reusable and non-reusable task information in the REP_ALL_TASKS view: Table 15-40. 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. Name of the scheduler. Informatica recommends using the fields in bold to join views. 0 = invalid. Specifies whether the task is reusable or not. Specifies whether a workflow. Task ID.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. worklet. 1 = enabled. Task type name.

3 = Run on demand and Run once schedule.Table 15-41. Workflow ID (primary key). 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. Number of workflow runs. Figure 15-42 lists variable information in the REP_WFLOW_VAR view: Table 15-42. Date and time when this task was last saved. Delta between successive runs (stored as seconds). REP_WFLOW_VAR This view displays a list of all variables declared within a workflow or worklet. The scheduler type. 36 = Run continuously and Delta schedule. UTC time (Coordinated Universal Time) when the scheduler was last saved. Description of the scheduler. REP_WFLOW_VAR MX View Column Name SUBJECT_ID WORKFLOW_ID VARIABLE_ID Datatype NUMBER NUMBER NUMBER Description Folder ID. Version number of the scheduler. 5 = Run on demand and Delta schedule. 40 = Run continuously and Custom repeat. 34 = Run continuously and Run once schedule. UTC checkin time. 2 = Run once schedule. Specifies when the task must stop running. Used by END_OPTIONS column. 9 = Run on demand and Custom repeat. Worklet. and Task Views 375 . 24 = Run on server init and Custom repeat. Unique ID for a variable within a workflow (primary key). Workflow. 18 = Run on server init and Run once schedule. Specifies whether the scheduler is reusable or not. 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. Records the following values for each schedule type: 1 = Run on demand. 20 = Run on server init and Delta schedule.

Date and time that this event was last saved. Event type. Event description. 1 = user-defined.Table 15-42. ID of the instance where the variable is defined. 1 = user-defined. Comments on the variable. Date and time that this task was last saved. Name of the task instance. Workflow ID (primary key). 3 = decimal 4 = integer 5 = small integer 7 = real 8 = double 11 = date/time 12 = string Default value of a variable. Datatype of a workflow variable. 2 = workflow variable is NULL. 376 Chapter 15: Using Metadata Exchange (MX) Views . Event ID (primary key). Workflow version number. 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. 0 = built in. Table 15-43 lists event information in the REP_EVENT view: Table 15-43. 0 = built in. 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 scope. Name of the event. REP_EVENT This view displays the details of events created at the workflow or worklet level. 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. Specifies whether the workflow variable is null or persistent. 1 = workflow variable is persistent. Variable type.

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

Task ID. Task error message. Name of the task instance. Version number. The value that identifies the condition associated with the link.Table 15-45. ID of the parent workflow. 378 Chapter 15: Using Metadata Exchange (MX) Views . ID of an instance within a workflow or a worklet. Version number. Table 15-46 lists run statistics and folder reference information in the REP_TASK_INST_RUN view: Table 15-46. Run ID of a child task in a worklet. Run ID of the parent workflow. Folder ID. Task error code. Run ID of a worklet in a workflow. End time configured for task execution. REP_TASK_INST_RUN This view displays the run statistics and folder reference for tasks within a workflow or worklet. Condition ID. 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. Object name. 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 type. Informatica recommends using the fields in bold to join views. Start time configured for task execution. Workflow name.

Error message code. Worklet. ID of the PowerCenter Server. Task version number. 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.Table 15-46. End time configured for the workflow. Workflow. 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. Workflow ID. Workflow run ID. Full path and name of the log file. Server name. Table 15-47 lists workflow run statistic information in the REP_WFLOW_RUN view: Table 15-47. and Task Views 379 . 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 This view displays the run statistics for all workflows by folder. REP_TASK_INST_RUN MX View Column Name RUN_STATUS_CODE Datatype NUMBER Description Status code of the task. PowerCenter Server ID. Start time configured for the workflow. Name of the server. Workflow name.

1 = Normal. 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. Session interval. Name of the user who ran the workflow. Session start time. Informatica recommends using the fields in bold to join views. 2 = Recovery. Version number of the mapping. Folder version ID. Folder version name. Name of the mapping this session uses. Source ID. Workflow version number. Session ID. REP_LOAD_SESSIONS This view provides information about reusable sessions in the repository. Table 15-48 lists reusable session information in the REP_LOAD_SESSIONS view: Table 15-48. Time the session was last saved. Target ID. Session log file 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. Repeat count. Name of the session. 380 Chapter 15: Using Metadata Exchange (MX) Views . Specifies how the workflow was run. Status code for the workflow run.Table 15-47. Folder name. Version number of the session. Location of the reject file. Specifies whether the session is active.

and Task Views 381 . REP_SESSION_CNXS This view contains information about connections associated with reusable sessions. 1 = target connection. Workflow. Name of the connection.Table 15-48. 1= reusable. 0 = invalid. 0 = not reusable. Specifies whether the connection is the target or the source. this view shows the connection in the session instance and the connection information in the reusable session. Session ID. Informatica recommends using the fields in bold to join views. 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. 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. 1 = valid. Worklet. 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. If a session instance overrides the connection information in a reusable session. Version number of the session. 0 = source connection. Folder ID. Description of the session. Specifies whether the session is reusable or not. Name of the session. Connection ID. REP_SESSION_INSTANCES This view contains connection information for session instances. CONNECTION_NAME CONNECTION_ID SESSION_VERSION_NUMBER VARCHAR2 (240) INTEGER NUMBER Informatica recommends using the fields in bold to join views. Specifies whether the session is valid or not. This view does not show connection information for reusable sessions that are not associated with any workflows.

Session version number. Connection ID associated with the session instance. Folder ID. Session ID. 1 = target connection. Name of the session. 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. Specifies the connection type. Session instance ID. Table 15-51 lists reusable session file connection information in the REP_SESSION_FILES view: Table 15-51. Session instance name.Table 15-50 lists session instance connection information in the REP_SESSION_INSTANCES view: Table 15-50. Informatica recommends using the fields in bold to join views. 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. Name of the workflow the session instance belongs to. 0 =source file connection. Name of the source or target file. 0 = source connection. Directory where the source or target file is stored. Specifies the connection type. 1 = target file connection. Workflow ID. Workflow version number. Version number of the session. 382 Chapter 15: Using Metadata Exchange (MX) Views . REP_SESSION_FILES This view contains file connections associated with reusable sessions.

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

Session version number. Session instance ID. Informatica recommends using the fields in bold to join views. Component value. Type of referenced object. Figure 15-54 lists session component information in the REP_COMPONENT view: Table 15-54. Name of the value. 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. Session ID. ID of a task within a session. Transformation instance ID referenced by a session (primary key). ID of the referenced object. Object version number. Session ID. Workflow ID. Informatica recommends using the fields in bold to join views. Session instance ID. REP_COMPONENT This view displays the list of tasks such as a command or an email for each session. Identifies the referred object's sequence type. Indicates whether the object is a reader or a writer. Indicates a specific reader or writer. 78 = reader. 384 Chapter 15: Using Metadata Exchange (MX) Views . Object type. Description of the value.Table 15-53. 79 = writer. 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. Indicates a specific object.

target. Object type name. targets. or transformation in a session. Instance name. Select the row which contains the session ID reference. If the session overrides a parameter in the configured object. and transformations in a session. Workflow. Identifies a source. target. Session configuration attribute type. Session version number. Description of the partition. Instance ID of a source. Session configuration ID. Session instance ID. 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. Informatica recommends using the fields in bold to join views. the view displays two rows. 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. Table 15-56 lists session configuration information in the REP_SESS_CONFIG_PARM view: Table 15-56. Time when the partition was last modified. or transformation. Partition ID Partition name. and Task Views 385 . or transformation. Worklet.REP_SESS_PARTITION_DEF This view provides partition details of the sources. ID of the mapping used by the session. REP_SESS_CONFIG_PARM This view displays session configuration parameter details. ID of a source. Table 15-55 lists partition information in the REP_SESS_PARTITION_DEF view: Table 15-55. Session configuration attribute ID. Session version number.

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

which might contain one or many target tables. Session instance name. Session ID. Time completed. Location of the reject file. Number of failed source rows. Version number of the task. 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. Folder ID. First error code. 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. and Task Views 387 . Run status code. Session log file name. Number of successfully loaded target rows.REP_SESS_LOG This view provides log information about sessions. Worklet. Actual time session started. Workflow version number. Table 15-58 lists session log information in the REP_SESS_LOG view: Table 15-58. Number of failed target rows. Last error message. 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. Number of successfully read source rows.

REP_SESS_TBL_LOG This view contains information about the status of an individual session run against a target. Run ID of a worklet in a workflow. Total error code. row counts. 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. Folder ID. It provides the last update time. Workflow ID. 388 Chapter 15: Using Metadata Exchange (MX) Views . Name of the workflow that contains the session instance. Table 15-59 lists individual session information in the REP_SESS_TBL_LOG view: Table 15-59. 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. Session name. Name of the session instance. Session name. Session ID.Table 15-58. Version number of the target. Mapping name. Informatica recommends using the fields in bold to join views. and error status based on a last update timestamp on a per target basis. Workflow run ID. Workflow ID. Target instance name for the session. Target table ID. Session instance ID. Workflow version number. Business name of the target. Name of the table for this log. Instance ID.

Object unique type ID. Last error code. Version number of the session. 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. Name of the partition. Group name. Number of affected target rows Number of failed target rows. and Task Views 389 . Mapplet instance name. Performance numbers for the target. Last error message.Table 15-59. Transformation name. Session timestamp. Time the target load ended. Worklet. Object name. Workflow. Location of the reject file. Informatica recommends using the fields in bold to join views.

For more information. 1 = user-created. 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). 0 = deleted. Unique global user ID. Specifies whether the user is system-created or usercreated. Privileges granted to the user. 0 = disabled. 390 Chapter 15: Using Metadata Exchange (MX) Views . This view provides association details between PowerCenter users and the group to which they belong. Specifies whether user can log in. For more information. Specifies whether user is valid. Description of the user. 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. User contact information. 0 = system-created. 1 = enabled. see “REP_USERS” on page 390. User name. Informatica recommends using the fields in bold to join views. see “REP_GROUPS” on page 391. REP_USERS This view provides a list of all PowerCenter users along with details on user privileges and contact information.Security Views Security views allow you to see user and group information such as privileges and contact information. 1 = valid. This view provides a list of PowerCenter groups along with details on group privileges and contact information. For more information. Table 15-60 lists the different views that help you analyze security metadata: Table 15-60. see “REP_USER_GROUPS” on page 391. Table 15-61 lists user information in the REP_USERS view: Table 15-61. User login ID used by external authentication modules.

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. CONTACT_INFO VARCHAR2 (2000) Informatica recommends using the fields in bold to join views. Group ID.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. Group name. 0 = system-created. Group description. 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). Table 15-63 lists group information in the REP_GROUPS view: Table 15-63. Informatica recommends using the fields in bold to join views. Table 15-62 lists group association information in the REP_USER_GROUPS view: Table 15-62. Contact information for the group. Group privileges. Security Views 391 . 1 = user-created.

0 = static. deployment date. and objects which were deployed from one repository to another. Table 15-65 lists deployment group information in the REP_DEPLOY_GROUP view: Table 15-65. 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. 392 Chapter 15: Using Metadata Exchange (MX) Views . see “REP_DEPLOY_GROUP” on page 392. see “REP_DEPLOY_GROUP_DETAIL” on page 393. Name of user who created the query. Group ID. Query ID associated with a dynamic group. For more information. REP_DEPLOY_GROUP This view provides information on deployment groups. This view provides Change Management deployment details. User ID. Name of user who created the deployment group. Last saved time. Query name associated with a dynamic group. Query group ID. 1 = dynamic. For more information. Description of the group.Deployment Views Deployment views allow you to see deployment information such as deployment groups. Creation time. Query description. Table 15-64 lists the different views that help you analyze deployment metadata: Table 15-64. Deployment group name. Query user. Deployment group type. source and target repository names associated with deployment. Deployment Views View REP_DEPLOY_GROUP REP_DEPLOY_GROUP_DETAIL Description This view provides information on deployment group in Change Management.

Global ID of the repository. Object type.Table 15-65. 0 = not a shortcut Deployment group ID. REP_DEPLOY_GROUP_DETAIL This view provides deployment details. Folder name in the target repository. Name of the object. 2 = personal. 1 = public. Table 15-66 lists deployment information in the REP_DEPLOY_GROUP_DETAIL view: Table 15-66. Specifies whether the object is a shortcut. Query type. Query last saved time. 2 = deploy from. 1 = shortcut. Object ID. Folder name in the source repository. Object version number in the target repository. 1 = deploy to. Deployment user ID. 0 = invalid. Deployment group name. REP_DEPLOY_GROUP MX View Column QUERY_CREATION_TIME QUERY_LAST_SAVED QUERY_TYPE Datatype VARCHAR2 (30) VARCHAR2 (30) NUMBER Description Query creation time. Object type name. Folder ID in the source repository. Deployment start time. TARGET_REP_NAME REP_GID USER_ID VARCHAR2 (240) VARCHAR2 (240) NUMBER Deployment Views 393 . Object version number in the source repository. Informatica recommends using the fields in bold to join views. 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. Deployment type. Target repository name.

UTC deployment time. 2 = rollback failed. 394 Chapter 15: Using Metadata Exchange (MX) Views . 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. 1 = rollback. Deployment user name. Deployment rollback time.Table 15-66. Deployment status. 0 = deployed. ROLLBACK_TIME NUMBER Informatica recommends using the fields in bold to join views.

connection information on which the repository is created. Name of the machine hosting the Repository Server. database type. 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. Port number of the Repository Server. Repository name. 3 = local. and database type. Repository ID. MX provides the REP_REPOSIT_INFO view to help you analyze repository metadata. domain name. Repository View 395 . 1 = global. Description of the repository. REP_REPOSIT_INFO This view provides repository information such as repository name and type. Repository type. and whether the repository is local or global.Repository View The repository view allows you to see repository name. 2 = standalone. Table 15-67 lists repository information in the REP_REPOSIT_INFO view: Table 15-67. Database user name used to connect to the repository. Global domain name. 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.

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

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). PowerCenter Server job distribution options. Time when the server was last saved. Table 15-70 lists PowerCenter Server information in the REP_SERVER_NET view: Table 15-70. Informatica recommends using the fields in bold to join views. Table 15-71 lists PowerCenter Server identification and usage information within the grid in the REP_SERVER_NET_REF view: Table 15-71. 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). PowerCenter Server ID (primary key). Server name. PowerCenter Server Views 397 . Description of the server. Use network and used by network = 3. Informatica recommends using the fields in bold to join views. Use network = 1. REP_SERVER_NET_REF This view provides PowerCenter Server identification within the grid and usage information.REP_SERVER_NET This view provides PowerCenter Server grid information and provides description and usage information.

Table 15-72 lists the different views that help you analyze version history of objects and label metadata: Table 15-72. For more information. worklets. workflows. Host machine name from which the version of the object is saved. 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 subtype ID. Provides information on labels in Change Management. 398 Chapter 15: Using Metadata Exchange (MX) Views . Provides information on label details in Change Management. Database name used by source objects. mappings. Object type ID (primary key). REP_VERSION_PROPS This view provides the version history of all objects in a PowerCenter repository. Table 15-73 lists label information in the REP_VERSION_PROPS view: Table 15-73. Folder ID. mapplets. 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. sessions. see “REP_VERSION_PROPS” on page 398. For more information. see “REP_CM_LABEL_REF” on page 399. Object version number. Time when object was last saved. Description of the object. see “REP_CM_LABEL” on page 399. For more information. Objects can be defined as tables. transformations. User who last modified this version of the object.Change Management Views Change Management views allow you to see the version history of all objects in a PowerCenter repository and label metadata. Name of the object. Labels can be defined on all objects. and tasks. UTC time when the object was last modified.

Object type ID. Label name. User ID. Informatica recommends using the fields in bold to join views. Informatica recommends using the fields in bold to join views. REP_CM_LABEL_REF This view provides information on label details. Name of user who created the label. Group ID. Object version number. Folder ID. 2 = Can apply label to only one version of the object. Table 15-74 lists label information in the REP_CM_LABEL view: Table 15-74. Change Management Views 399 . Label type. REP_VERSION_PROPS MX View Column PURGED_BY_USERID Datatype NUMBER Description User ID who purged the object from the repository. REP_CM_LABEL This view provides label information. 2 = label locked. Object ID. Label description. Label creation time. Label status. Time when label was last saved. Table 15-75 lists label information in the REP_CM_LABEL_REF view: Table 15-75. 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 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.Table 15-73. 1 = label unlocked.

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

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. REP_SUBJECT MX View Column SUBJECT_AREA SUBJECT_ID DESCRIPTION Datatype VARCHAR2 (240) NUMBER VARCHAR2 (2000) Description Folder name. It describes the name. Table 15-76 lists folder information in the REP_SUBJECT view: Table 15-76. Folder View 401 . and description of each folder.Folder View The folder view allows you to see all the folders defined in the PowerCenter repository. Folder description. ID. Informatica recommends using the fields in bold to join views. Folder ID.

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

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

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

Overview 405 .Table 16-1 lists the native connect string syntax for each supported database when you create or update connections: Table 16-1.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. Native Connect String Syntax Database IBM DB2 Informix Microsoft SQL Server Oracle Sybase Teradata* Connect String Syntax dbname dbname@servername servername@dbname dbname.world sambrown@mydatabase TeradataODBC TeradataODBC@mydatabase TeradataODBC@jsmith *Use Teradata ODBC drivers to connect to source and target databases.

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

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

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

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

The host name of the machine running the Repository Server. but not both. Table 16-2 lists pmrep system commands: Table 16-2. The password environment variable for the repository. but not both. 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. Cleans up persistent resources created by pmrep during a session. See “Cleaning up Persistent Resources (Cleanup)” on page 411. Password for the repository user name. pmrep System Commands pmrep Command Connect Help Cleanup Exit Command Description Connects to the repository. Displays help for all commands or for a specified command. “Exiting pmrep (Exit)” on page 411.pmrep System Commands This section describes basic pmrep commands that you use in conjunction with other pmrep repository and security commands. Repository user name used to connect to the repository. See “Connecting to a Repository (Connect)” on page 410. Connecting to a Repository (Connect) The first time you use pmrep in either command line or interactive mode. All commands require a connection to the repository. 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. Use the -x or -X option. you must call the Connect command. Exits from pmrep. See “Getting Help (Help)” on page 411. The port number the Repository Server uses for connections. Use the -x or -X option. 410 Chapter 16: Using pmrep and pmrepagent .

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

pmrep returns object metadata to the screen. The connection to the Repository Server failed. but not both. Listing Repository Objects (ListObjects) The ListObjects command returns objects in the repository. Tip: When you specify characters to separate records and columns and to indicate the end of the listing. You can specify the character or characters to use to separate records and columns. pmrep Repository Commands 423 . pmrep returns each object in a record and returns each object metadata in a column. -r The command returns an “enablerepository completed successfully” or returns “Failed to execute enablerepository” message. For example. Use the -a or -A option.Table 16-14. Name of the repository to enable. It separates records by a new line by default. and then use the parsed data in another pmrep command. To list objects. and use Updateseqgenvals to update the sequence values. parse the data ListObjects returns. You can use ListObjects in a shell script to return the object metadata. you do not need read permission on the folders. This helps you use a shell script to parse the object metadata. The Repository Server failed to enable the repository because the repository is not currently disabled. You must connect to a repository to use this command. 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 command might fail for the following reasons: ♦ ♦ ♦ You did not give the repository name in the argument. use characters that are not used in repository object names. parse the metadata. When you list objects. You can also specify the character or characters to indicate the end of the listing. you can use ListObjects to list all Sequence Generator transformations in the repository. Create a shell script that uses ListObjects to return Sequence Generator transformation information. 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.

excluding instances of reusable sessions. including shortcuts. Sessionconfig. All other object types require the -f option. Mapping. including shortcuts but excluding source instances. Source. List reusable and non-reusable tasks with latest or checked out version in a folder. Workflow.You can use the object_type option to define the objects you want to list. including shortcuts but excluding instances of reusable mapplets. Transformation. List folders in the repository Label. Target. Scheduler. Mapplet. 424 Chapter 16: Using pmrep and pmrepagent . Worklet. Session. List the workflows with latest version or checked out version in a folder. List mappings with latest or checked out version in a folder. but excluding objects according to the following rules for each object type: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Deploymentgroup. List labels in the repository. including shortcuts but excluding instances of reusable mapplets. Query. List reusable and non-reusable transformations with latest or checked out version in a folder. The command lists the latest versions or checked out versions of objects. and query object types are not associated with folders. including shortcuts but excluding target instances. List reusable and non-reusable worklets with latest version or checked out version in a folder. List the session configurations with latest or checked out version in a folder. Folder. label. List deployment groups in the repository. List reusable and non-reusable schedulers with latest or checked out version in a folder. folder. ♦ ♦ 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. The deploymentgroup. Task. List sources with latest or checked out version in a folder. excluding instances of reusable worklets. List mapplets with latest or checked out version in a folder. including shortcuts and excluding instances of reusable transformations. List queries in the repository. List targets with latest or checked out version in a folder. List reusable and non-reusable sessions with latest or checked out version in a folder.

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

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. to list all Stored Procedure transformations in a folder. When you list objects. to list all folders in the repository.transformation_name or mapplet_name. enter the following text at the pmrep> prompt: listobjects -o folder Or.Table 16-16. see Table 16-16 on page 426. pmrep returns the name of the object with the path when applicable.sp_nsproc sequence non-reusable smallmapplet. For example. Or. 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. For example. When you specify folder for the object type. when a transformation is in a mapping or mapplet. you must include the folder name for all objects that are associated with a folder.transformation_name. pmrep does not include instances of reusable objects. 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. pmrep ignores the subtype and folder name. pmrep returns mapping_name. For a list of transformation or task return values. 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.listobjects completed successfully. to list all transformation types in a folder.seqgen_empid . 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.sp_nsproc pmrep Repository Commands 427 .

To specify a non-reusable session in a workflow. or specify target to list targets.wl_shirt_orders.source_name You must connect to a repository to use this command. Listing Tables by Session (Listtablesbysess) The Listtablesbysess command returns sources or targets used in a session. 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. You can specify a reusable or non-reusable session. pmrep returns the source instance name in the following format: mapplet_name. To list all sessions in a folder. Specify source to list sources. The name of the session containing the sources or targets. To list sources or targets. enter the workflow name and the session name as workflow_name.s_sales_Q3 session non-reusable wf_orders. You can use Listtablesbysess in a shell script with other pmrep commands. When you use Listtablesbysess. -t Required table_type 428 Chapter 16: Using pmrep and pmrepagent . When you list sources or targets.listobjects completed successfully. you can create a shell script that uses Listtablesbysess to return source instance names and uses Updatesrcprefix to update the source owner name. However. if the mapping contains a mapplet with a source. pmrep returns source and target instance names as they appear in the session properties. 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. For example. you cannot specify an instance of a reusable session.session_name.s_shirt_orders . 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. pmrep returns source or target instance names to the screen.listobjects completed successfully.. For example.

pmrep includes the mapplet name with the source.ORDERS Shortcut_To_ITEM_ID listtablesbysess completed successfully. These files are the same format. To list object dependencies. 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 . such as mapplet1.For example. For more information on using a persistent input file. AddToDeployment Group. Listing Object Dependencies (ListObjectDependencies) Use the ListObjectDependencies command list dependency objects for reusable and nonreusable objects. For example. You can create this file by running a query and choosing to create a text file. to list all sources in a reusable session. or Validate pmrep commands. you can use it as input to the ApplyLabel. enter the following text at the pmrep> prompt: listtablesbysess -f myfolder -s s_reus_sess1 -t source pmrep returns the following information: ITEMS mapplet1. ListObjectDependencies returns the number of records if the command runs successfully.s_nrsess1 -t target pmrep returns the following information: target1_inst ORDERS_BY_CUSTID Shortcut_To_tgt2_inst listtablesbysess completed successfully. Note: When the mapping contains a mapplet with a source. you must use a persistent input file containing object IDs. If you want to list dependencies for non-reusable objects. Note: ListObjectDependencies accepts a persistent input file and it can create a persistent output file.ORDERS. see “Using the Persistent Input File” on page 494. you can list all targets in a non-reusable session in a workflow: listtablesbysess -f myfolder -s wf_workkflow1. If you create an output file.

-o. You must use this file if you want to list dependencies for non-reusable objects. session config. session. cube. or Validate pmrep commands. separate them by commas without spaces. task.parentobject_name. workflow. You can specify ALL or one or more object types. The folder containing object_name. Folder is required if object type is not a folder and you are not using the -i option. worklet. Append the result to the persistent output file name file instead of overwriting it. If ALL. then pmrep lists all supported dependent objects. The default sends the query result to stdout. The type of dependent objects to list. children. The parents or children dependent objects to list. The text file of objects generated from ExecuteQuery or Validate commands. If you use this option. session. AddToDeployment Group. To specify multiple objects. mapping. List dependent objects for an object version other than the latest version. 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.nonreusableobject_name. -f options to specify objects. You can specify parents. target. see Table 16-16 on page 426. You can specify source. -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 . see “Using the Persistent Input File” on page 494. and dimension. Send the dependency result to a text file. then pmrep lists dependent objects only for these types. The default is ALL. Required if you do not use the -p option. The object type to list dependencies for. For valid subtypes. then you cannot use the -n. scheduler. For more information on using the persistent input file. You can use the text file as input to the ApplyLabel. Include the primary key-foreign key dependency object regardless of the direction of the dependency. Table 16-18 lists pmrep ListObjectDependencies options and arguments: Table 16-18. The type of transformation or task.Note: ListObjectDependencies displays non-reusable objects as parent. Find object dependencies across repositories. Ignored for other object types. If you choose one or more objects. or both. Required if you do not use the -s option. transformation.

Print more than the minimum information about the objects. includes the object type and object name. If you omit this option. pmrep Repository Commands 431 . pmrep prints a shorter format including the object type. Use a character or set of characters that is not used in repository object names. Verbose format includes the version number and folder name. 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 object name and path. such as label. query. 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. and connection. you might want to avoid using a space as a column separator. you must have Administer Repository privilege.Table 16-18. pmrep uses a period. deployment group. The number of the port where the Repository Server is running. -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. 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. If you omit this option. The short format for versioning objects. Verbose format includes the creator name and creation time. If you omit this option. The default is newline /n. The character or set of characters used to specify the end of the object list. The character or set of characters used to specify the end of the object metadata. the word reusable or nonreusable. To send notification messages. Use a character or set of characters that is not used in repository object names. Specify a character or set of characters that is not used in repository object names. If any repository object name contains spaces. pmrep uses a single space.

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

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

The password you use to administer the global Repository Server. To register a local repository. -a 434 Chapter 16: Using pmrep and pmrepagent . 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 environment variable for the local target repository. but not both. See “Using the Object Import Control File” on page 496. Registering Local Repositories (Register) Use the Register command to register a local repository with a connected global repository. 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. you must have Administer Repository privilege. 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. Note: The ObjectImport command does not automatically create a folder if the folder you specify does not exist in the repository. Use the -a or -A option. The name of the control file that defines import options. You must connect to the global repository before you register the local repository. Use the -x or -X option. but not both. The login password for the local target repository.♦ 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. Use the -x or -X option. but not both. The local repository user name.

Use the -a or -A option. The number of the port where the Repository Server is running. If you use this option. Use the -a or -A option.Table 16-22. but not both. The hostname of the local repository. You failed to connect to the Repository Server. If you use this option. 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. Removing Repositories From the Cache (Removerepository) The Removerepository command removes repositories from the Repository Server cache entry list. you must use the -o option as well. The port number of the Repository Server. Use this option when the local repository is managed by a different Repository Server. The registration might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. pmrep Repository Commands 435 . 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. The Repository Server failed to register the local repository with the global repository. -h -o Optional local_repository_port_numb er The command returns “register successfully completed” or returns “failed to execute register” message. but not both. you must use the -h option as well. The Repository Server failed to initialize information about the global repository. 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. The login password for the repository. Use this option when the local repository is managed by a different Repository Server.

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. All repository users can run script files. Running Script Files (Run) The Run command takes a file containing multiple pmrep commands and runs those commands sequentially. This option writes all messages generated by the commands in the script file into the output file. -e -s Optional Optional echo_commands stop_at_first_error The command returns “run successfully completed” or returns “run failed” message. Stops the running of the script after a command returns an error. but not both. 436 Chapter 16: Using pmrep and pmrepagent . You failed to connect to the Repository Server. The name of the repository to remove. The removal might fail for the following reasons: ♦ ♦ The repository name does not exist. The run might fail if the Repository Server cannot open the script file or output file.Table 16-23. The commands are echoed back to the script. Use the -a or -A option. 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. -r The command returns “removerepository successfully completed” or “failed to execute removerepository” message. 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. The name of the output file.

When you use the ShowConnectioninfo command in command line mode. ShowConnectioninfo requires no parameters. if you do not specify a repository. The ShowConnectioninfo command does not connect to the repository. For example.Showing Connection Information (ShowConnectioninfo) The ShowConnectioninfo command returns the repository name. a message indicating failure to execute the command is given. pmrep Repository Commands 437 . the pmrep keeps the connection information in memory until you exit the repository or connect to a different repository. StopRepository stops the repository you last connected to. 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. and user information for the current connection. 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 does not keep connection information in command line mode. and -r options. port. -o. Otherwise. the named repository stops. pmrep connects to the Repository Server and stops the Repository Agent. When you use the StopRepository command. see “Connecting to a Repository (Connect)” on page 410. the repository that you last connected to stops. Stopping a Repository (StopRepository) The StopRepository command stops the repository you specify. server. You must be connected to a repository to use this command. For more information about connections in command line mode and interactive mode. When you connect to a repository in interactive mode. However.

In a session. you must also use the -h and -o options. The name of the repository to stop. you have a relational and an application source. Use the -a or -A option. 438 Chapter 16: Using pmrep and pmrepagent . 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. For example. When you use this option. The hostname of the Repository Server that manages the repository to stop. 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 be connected to a repository to use this command. 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 password environment variable you use to administer the Repository Server that manages the repository. you specified the name ITEMS for a relational source connection instead of Relational:ITEMS. When you use this option. -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. but not both. you must also use the -h and -r options. each called ITEMS. When you use this option. you must also use the -o and -r options. When you use SwitchConnection. When you use SwitchConnection to replace the relational connection ITEMS with another relational connection. The Repository Server port number. Use the -a or -A option. but not both.Table 16-25 lists pmrep StopRepository option and argument: Table 16-25. the Repository Server replaces the relational connection.

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

Use the -a or -A option. but not both. but not both. The password you use to administer the global Repository Server. To unregister a local repository. but not both. You specified a workflow. 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. 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. but not both. The password environment variable you use to administer the global Repository Server. The login password environment variable for the local target repository. Unregistering Local Repositories (Unregister) Use the Unregister command to unregister a local repository from a connected global repository. The folder name is invalid. You must connect to the global repository before you unregister the local repository. Use the -x or -X option. but no folder name. -a -A global_repserver_password_ environment_variable 440 Chapter 16: Using pmrep and pmrepagent . Use the -x or -X option. The truncation might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. The workflow does not exist in the given folder.The command returns “truncatelog completed successfully” or returns “Failed to execute truncatelog” message. Use the -a or -A option. The login password for the local target repository. you must have Administer Repository privilege.

One of the required parameters is missing. 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. If you use this option. To update a connection. You failed to connect to the Repository Server.Table 16-28. 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 . you must use the -o option as well. password. The Repository Server failed to initialize information about the global repository. If you use this option. -o Optional local_repository_port_number The command returns “unregister successfully completed” or returns “failed to execute unregister” message. The connection object does not exist. A failure might occur for the following reasons: ♦ ♦ ♦ ♦ ♦ The database type is not supported. Unregister Options and Arguments (pmrep) Option -h Required/ Optional Optional Argument Name local_repository_host_name Argument Description The hostname of the local repository. connect string. you must use the -h option as well. and attributes for a database connection. 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. The current user does not have the appropriate permissions. The Repository Server failed to unregister the local repository to the global repository. Updating a Database Connection (UpdateConnection) The UpdateConnection command updates the user name. The registration might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have Administer Repository privilege. pmrep cannot acquire a lock on the object. Use this option when the local repository is managed by a different Repository Server.

Enter “yes” or “no” for attributes you enable through a checkbox. This command requires you to connect to a repository. For a list of native connect strings. the command does not update the email addresses. -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. You can specify different addresses to receive either success or failure notifications. Use the -p or -P option. 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 . If you did not previously specify a success or failure Email task for the session. The new attribute value of the connection. 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 connect string the PowerCenter Server uses to connect to the relational database. but not both. The name of the attribute. The user name used for authentication when you connect to the relational database. Use the -p or -P option.Table 16-29 lists pmrep UpdateConnection options and arguments: Table 16-29. You can update the email notification addresses only for a non-reusable session with a unique name in the folder. The password environment variable used for authentication when you connect to the relational database. The password used for authentication when you connect to the relational database. The database connection name. see Table 16-1 on page 405. For a list of valid database types. see Table 16-9 on page 418. but not both.

pmrep Repository Commands 443 . The protocol the PowerCenter Server uses. The server host name or IP address of the server machine. The new name of the PowerCenter Server. To update server details. 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 character set associated with the PowerCenter Server. Email address to send session failure notifications. The number of seconds the Workflow Manager waits for a response from the PowerCenter Server.Table 16-30 lists pmrep Updateemailaddr options and arguments: Table 16-30. Must be identical to or compatible with the repository code page. 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. Email address to send session success notifications. The port number the PowerCenter Server. Select the code page identical to the PowerCenter Server operating system code page. you must have the Administer Repository privilege. 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. Name of the session. Updating Server Details (Updateserver) The Updateserver command updates PowerCenter Server details with the values that you specify in the command. Only the values that you specify update. For more information about PowerCenter Server details see “Registering the PowerCenter Server” in the Installation and Configuration Guide.

The mapping name. you cannot update values for instances of reusable Sequence Generator transformations or shortcuts to Sequence Generator transformations. You must connect to a repository to use this command. 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. You can use Updateseqgenvals to update reusable and non-reusable Sequence Generator transformations. To update sequence values. 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. see “Sequence Generator Transformation” in the Transformation Guide. For more information on configuring Sequence Generator transformations. 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. The Sequence Generator transformation name. you must include the mapping name. -t sequence_generator_name 444 Chapter 16: Using pmrep and pmrepagent . When you update values for a nonreusable Sequence Generator transformation.

If you designate an invalid value. the current value must be greater than or equal to the start value and less than the end value. pmrep gives an error message and does not update the Sequence Generator transformation. You must connect to a repository to use this command. pmrep gives an error message and does not update the Sequence Generator transformation. 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. Enter the value you want the PowerCenter Server to use as the first value in the sequence. If you select Cycle in the transformation properties.Table 16-32. The difference between two consecutive values from the NEXTVAL port. 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 . pmrep gives an error message and does not update the Sequence Generator transformation. If the PowerCenter Server reaches this value during the session and the sequence is not configured to cycle. You can update the owner name for one or all sources in a session. The current value of the sequence. The maximum value the PowerCenter Server generates. 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. If you want to cycle through a series of values. If you designate an invalid value. If you designate an invalid value. 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. Updatesrcprefix updates the owner name for source tables at the session level. it fails the session. To update source table owner names. If you designate an invalid value.

The name of the source to update. pmrep updates all source table owner names in the session. When you do not include this option.When you omit the -n option.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.session_name or workflow_name. pmrep matches the source_name argument with source instance names. This command requires you to connect to a repository.source_name. For reusable sessions. you must enter the dbd name and the source table name as dbd_name. . see “Configuring the Workflow Manager” in the Workflow Administration Guide. If you omit this option. . -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. you must also specify the session path. You cannot change default server variables. but you can change the case of the default server variables. You can find the source dbd name in the Designer Navigator. You can update any of the PowerCenter Server variables using Updatesrvvar. Informatica recommends you include the -n option. The Designer generates the dbd name from the source type or data source name when you create a source definition in the repository. pmrep matches the source_name argument with the source table names. For non-reusable sessions. such as worklet_name. specify session_name.session_name. Updatesrvvar uses the following command syntax: updatesrvvar -s server_name -v variable_name -u new_value 446 Chapter 16: Using pmrep and pmrepagent . When you include this option. enter the name of the source instance as displayed in the session properties or as output by the Listtablesbysess command. For a list of server variables. The name of the session containing the sources to update. This option has no argument. The owner name you want to update in the source table.When you include the -n option. 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 update fails if you do not have Administer Repository privilege.Table 16-34 lists pmrep Updatesrvvar options and arguments: Table 16-34. pmrep Repository Commands 447 . To update repository statistics. Name of the server variable to update. You must connect to a repository to use this command. You can update the owner name for one or all targets specified in a session. 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. Updating Repository Statistics (UpdateStatistics) The UpdateStatistics command updates statistics for repository tables and indexes. pmrep updates table name prefixes if you previously edited the table name prefix at the session level. Updating the Target Table Name Prefix (Updatetargprefix) Use the Updatetargprefix command to update the table name prefix for session target tables. The command returns “updatestatistics successfully completed” or returns “updatestatistics failed” message. you must have Administer Repository privilege. The table name prefix specifies the owner of the table in the database. 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. see “Updating Repository Statistics” on page 60. For more information about updating statistics. Updatetargprefix updates the target table name prefix at the session level. 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. Value of updated server variable.

The name of the target to update. 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. This option has no argument. For reusable sessions. 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. pmrep updates all target table name prefixes in the session. When you omit the -n option.session_name or workflow_name. Informatica recommends you include the -n option. The name of the session containing the targets to update. enter the name of the target instance as displayed in the session properties or as output by the Listtablesbysess command.session_name. When you include the -n option. pmrep matches the target_name argument with the target table names. When you do not include this option.To update target table name prefixes. -t Optional target_name -p -n Required Optional prefix_name n/a 448 Chapter 16: Using pmrep and pmrepagent . pmrep matches the target_name argument with target instance names. such as worklet_name. If you omit this option. The table name prefix you want to update in the target table. you must enter the target table name instead of the target instance name. specify session_name. For non-reusable sessions. When you include this option. you must also specify the session path.

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

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

Any user in the repository can be the folder owner. 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. Use the -p or -P option. When you use this option. but not both. 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. If selected. Description of the folder that appears in the Repository Manager. The owner of the folder. Repository Server assigns default permissions. You must use this option when you use the -p option. This option confirms the new password. you must use the -c option. When you use this option. 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. The password environment variable that replaces the existing password for the current user.To change the password of the user connected to the repository. pmrep Security Commands 451 . Use the -p or -P option. If not specified. Only groups to which the owner belongs can be selected. but not both. The default owner is the user creating the folder. The confirm_new_password argument must match the new_password argument. Repository user group to receive Owner’s Group permissions. makes the folder shared. 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. Access rights for the folder. you must have Administer Repository privilege. -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. do not use the -c option. To run CreateFolder.

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

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

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

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

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

the user is assigned to Public. A description of the user. use the following syntax: rmgroup -g group_name pmrep Security Commands 457 . The login name in the external directory. The new owner does not exist or does not belong to the group. If you omit this option. To remove a group. You must connect to the repository to use this command. Contact information about the user. 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 modification might fail for the following reasons: ♦ ♦ ♦ ♦ You do not have the appropriate privilege. Removing a Group (Rmgroup) The Rmgroup command removes a group from the repository and reassigns all users in that group to the Public group. 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. A folder with the new folder name already exists.The command returns “ModifyFolder successfully completed” or returns “ModifyFolder Failed” message. Use this command if you use LDAP to authenticate repository users. users in the group lose the privileges inherited from the group. The folder does not exist. When you remove a 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. If any user in the group is connected to the repository when you remove the group. the privilege changes take effect the next time the user connects to the repository. Assigns the user to a group.

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

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

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

If you use a persistent input file.Adding to a Deployment Group (AddToDeploymentGroup) The AddToDeploymentGroup command adds objects to a deployment group. To add objects to a deployment group. worklet. You can specify objects using command options or you can use a persistent input file. you must use a persistent input file that contains encoded object IDs. The name of the object you are adding to the deployment group. see “Using the Persistent Input File” on page 494. Use AddToDeploymentGroup to add source. transformation. session configuration. target. You can specify source. If AddToDeploymentGroup runs successfully. scheduler. session configuration. For valid subtypes. session. workflow. cube. see Table 16-16 on page 426. The type of object you are adding. You cannot specify an object if you use the -i option. workflow. You cannot specify a checked out object. and dimension. For more information on adding to a deployment group. Required when adding a specific object. mapping. mapping. -o Required/ Optional object_type -t Required/ Optional object_subtype pmrep Change Management Commands 461 . target. For more information on using a persistent input file. transformation. and task objects. or it returns a list of objects that already are in the deployment group. see “Working with Deployment Groups” on page 236. If the command fails. worklet. session. scheduler. it displays the reason for failure. You cannot add checked out objects to a deployment group. The type of task or transformation you are adding. You must use this parameter when you add a specific object. it either sends back no status information. you can specify only the deployment group name option. Use AddToDeployment Group to add reusable input objects. If you want to add non-reusable input objects. 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. 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. task.

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

If you do not specify option -d. then the label applies to dependent objects of that object type. You can specify parents. pmrep searches the folder for the object. task. session. or folder name to specify objects. cube. If you specify a folder with an object name. The type of object to apply the label to. If you are updating a specific object. workflow. Use this option with option -p. For more information on using the persistent input file. mapping. You cannot specify objects if you use the -i option. For valid subtypes. The name of the object to receive the label. Contains a list of objects to receive the label. You cannot specify a folder if you use the -i option. but no object name. scheduler. all dependent objects receive the label. The dependent parents or children to apply the label to. ListObjectDependency. You can specify source.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. target. The folder that contains the object(s). The name of a text file generated from ExecuteQuery. see “Using the Persistent Input File” on page 494. pmrep ignores other object types. Required when applying a label to a specific object. the label applies only to the specified object. If you specify a folder. If you do not specify this option. If you use this option. If you specify an object type. 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. The dependent objects to label. pmrep applies the label to all objects in the folder. then do not use the object name. or dimension. worklet. see Table 16-16 on page 426. or Validate. Applies the label to the latest version of the object by default. object type. children. -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 . both. transformation. then this parameter is required. session config. The command fails if the version is checked out. The version of the object to apply the label to. The kind of task or transformation you are labeling.

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. The version number is one number greater than the version number of the last checked-in version. Comments relating to ApplyLabel. Move a label from the current version to the latest version of an object. 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. session config. For valid subtypes. The type of task or transformation to check in. -t Optional object_subtype -n -f -c Required Required Optional object_name folder_name comments 464 Chapter 16: Using pmrep and pmrepagent . The name of the object that you are checking in. target. workflow. task.Table 16-54. When you check in an object. transformation. 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. -c Optional comments Checking In Objects (Checkin) Use the Checkin command to check in an object that you have checked out previously. The folder to contain the new object version. You can use this argument only when the label type is one_per_object. scheduler. See “Creating a Label (CreateLabel)” on page 466. cube. For more information on checking in objects. Comments about the check in. see Table 16-16 on page 426. To check in objects. see “Checking In Objects” on page 213. mapping. or dimension. session. Table 16-55 lists pmrep Checkin options and arguments: Table 16-55. Not required for other object types. the repository creates a new version of the object and assigns it a version number. worklet.

You can create a dynamic or static deployment group. To create a dynamic 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. For more information on creating deployment groups. pmrep Change Management Commands 465 . You can use this command to retain the deployment group but remove the objects. To clear a deployment group. You can specify static or dynamic. Creating a Deployment Group (CreateDeploymentGroup) Use the CreateDeploymentGroup command to create a deployment group.Clearing a Deployment Group (ClearDeploymentGroup) Use the ClearDeploymentGroup command to clear all objects from a deployment group. To create a deployment group. Create a static group or use a query to dynamically create the group. Remove objects without confirmation. you must have the Use Repository Manager privilege. Default is static. the command prompts you for a confirmation before it clears the objects. you must supply a query name. 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 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. If you omit this argument. 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. and indicate whether the query is private or public. see “Working with Deployment Groups” on page 236.

-c Optional n/a Deleting a Deployment Group (DeleteDeploymentGroup) Use the DeleteDeploymentGroup command to delete a deployment group. see “Working with Deployment Groups” on page 236. If you omit this option. 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. you can specify that the label can apply to multiple versions of an object (one per version). If you delete a static deployment group. or you can specify that a label can apply to only one version of an object (one per object). You can specify shared or personal. 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. Allows multiple versions to have this label. you can apply the label to only one version. When you create a label. but ignored if the group is static. Required if the deployment group is dynamic. 466 Chapter 16: Using pmrep and pmrepagent . but ignored if the group is static. you must have the Administer Repository privilege. 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.Table 16-57. For more information on deleting deployment groups. Comments about the label. To create a label. Required if the deployment group is dynamic. Comments about the new deployment group. The type of query to create a deployment group. You can associate a label with any versioned object or group of objects in a repository. For more information on creating labels. -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 also remove all objects from the deployment group. see “Creating and Editing Labels” on page 219.

To delete a label. If the label is locked. 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. see “Working with Labels” on page 219. pmrep prompts you for a confirmation before it deletes the Deployment Group. Deleting a Label (DeleteLabel) Use the DeleteLabel command to delete a label and remove the label from all objects that use it. Deletes the Deployment Group without confirmation. 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. 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. You can optionally use this command to copy deployment groups to different repositories. the delete fails. 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. 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. the command prompts you for a confirmation before it deletes the label.To delete a deployment group. Deploying a Deployment Group (DeployDeploymentGroup) Use the DeployDeploymentGroup command to deploy a deployment group. pmrep Change Management Commands 467 . If you omit this argument. If you omit this argument.

see “Copying a Deployment Group” on page 254.To use this command. For more information on deploying a deployment group. Not required if you are copying the deployment group to the same repository. Not required if you copy the deployment group to the same repository. The repository you are deploying the group to. The login password environment variable for the target repository. The login user name for the target repository. Use the -x or -X option. -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 name of the XML file containing the Copy Wizard specifications. 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. 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. you must create a control file with all the specifications that the Copy Wizard requires. The login password for the target repository. but not both. For more information on using the control file. The control file is an XML file defined by the depcntl.dtd file. but not both. see “Using the Deployment Control File” on page 504. see “Using the Deployment Control File” on page 504. The control file is required. The host name of the Repository Server managing the target repository. For more details about the control file. Not required if you copy the deployment group to the same repository. Use the -x or -X option. To copy a deployment group. Not required if you copy the deployment group to the same repository.

Not required if you are copying the deployment group to the same repository. but not both. -l Deploying a Folder (DeployFolder) The DeployFolder command allows you to deploy a folder.dtd file. see “Using the Deployment Control File” on page 504. Not required if you are copying the deployment group to the same repository. The repository name to deploy the group to. The name of the XML file containing the copy wizard specifications. For more details about the control file. 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 information on the control file.Table 16-61. To copy a folder. The control file is an XML file defined by the depcntl. 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. 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. Not required if the target repository is the same as the source. It requires a control file containing specifications that the Copy Wizard requires. -r Optional target_repository_name -u Optional target_repository_user_name -x Required/ Optional target_repository_user_passwo rd pmrep Change Management Commands 469 . see “Using the Deployment Control File” on page 504. The log file that records each deployment step. The login user name for the target repository. If you omit this option. The login password for the target repository. it outputs to the screen. Use the -x or -X option.

Use the -x or -X option. To execute a query. You can use this file as input to the ApplyLabel. The host name of the Repository Server managing the target repository. If you omit this option. For more details on using a persistent input file. Not required if you are copying the deployment group to the same repository. 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. and Validate commands. it returns the total number of qualifying records.Table 16-62. If not specified. it outputs to the screen. Not required if you copy the deployment group to the same repository. You can choose to display the result or write the result to a persistent input file. The type of query to run. 470 Chapter 16: Using pmrep and pmrepagent . The log file that records each deployment step. Not required if you copy the deployment group to the same repository. but not both. 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. see “Using the Persistent Input File” on page 494. pmrep searches all the private queries first to find the matching query name. -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. Then it searches the public queries. You can specify public or private. 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. AddToDeploymentGroup. The port number of the Repository Server. If the query is successful.

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

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. -f Optional folder_name -u -c Optional Optional all_users column_separator 472 Chapter 16: Using pmrep and pmrepagent . cube. You can specify source. see “Checking Out and Checking In Objects” on page 211. target. The character or set of characters used to separate object metadata columns. mapping. If you do not specify an object type. pmrep ignores the -f and -u options and the command returns all checked-out objects in the repository. If you omit this option. To list checked out items. If any repository object name contains spaces.Listing Checked Out Items (FindCheckout) Use the FindCheckout command to print a list of checked out objects in the repository. 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. task. Folder name is optional if you specify an object type. pmrep uses a single space. For more information about finding checked out objects. pmrep returns all the checked out objects in the repository. workflow. If you omit object type. you might want to avoid using a space as a column separator.” If you choose an object type. Use a character or set of characters that is not used in repository object names. Note: You can use FindCheckout with no options. session. session config. scheduler. worklet. then you can list checked out objects in a specific folder or across all folders. Return a list of checked out objects for the object type in the specified folder. or dimension. The default is to list only checked out objects by the current user. The default is to list objects for the object type across folders. transformation. List the checked out objects by all users.

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. If you want to modify the object again. UndoCheckout uses the following command syntax: UndoCheckout -o object_type -t object_subtype -n object_name -f folder_name pmrep Change Management Commands 473 . 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. To undo a checkout. Verbose format includes the version number and folder name. the word reusable or non-reusable. see “Using the Designer” in the Designer Guide. -l Optional end-of-listing_indicator -b Optional verbose Undoing a Checkout (UndoCheckout) Use the UndoCheckout command to undo a checkout of an object. Use a character or set of characters that is not used in repository object names. you must check it out. Verbose format includes the creator name and creation time. If you omit this option. or “Using the Workflow Manager” in the Workflow Administration Guide. When you undo a checkout. and connection. pmrep uses a period. The default is newline /n. deployment group. the repository releases the write-intent lock on the object and reverts to the most recently checked in version of the object.Table 16-64. the object name and path. For details on undoing a checkout. pmrep prints a shorter format including the object type. query. The short format for versioning objects such as label. 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. If you omit this option. Print more than the minimum information about the objects. includes the object type and object name.

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

Check in saved objects. The default is the latest or checked out version of the object. session. workflow. invalid_before. task. dimension. 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. Ignored for other object types. mapping. transformation. 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. save_failed. You can specify source. You should specify output_options when you use the persistent_output_file_name. The type of object to validate. cube. You cannot use this file if you are specifying objects using the -n. scheduler.To validate objects. -o. You can specify valid. Validate. Required if you are not using a persistent input file. Do not use this option if you are using the -i argument. The type of task or transformation. Contains a list of object records. Add comments when you check in an object. Required if you use the -k option. worklet. To specify one or more options. -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 . target. or -f arguments. Required if you use -s. The text file from ExecuteQuery. Save objects that change from invalid to valid to the repository. The name of the folder containing the object. or ListObjectDependencies commands. The kind of object you want to output to the persistent output file or stdout after validation. or invalid_after. For valid subtypes. session config. skipped. The version of the object to validate. and the current repository requires checkin comments. separate them by commas. saved. see Table 16-16 on page 426.

If you omit this option. 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. and connection. If you omit this option. If you specify a file name. Verbose format includes the version number and folder name.Table 16-66. deployment group. pmrep uses a single space. the query writes the results to a file. Use a character or set of characters that is not used in repository object names. 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. Verbose format includes the creator name and creation time. pmrep uses a period. If any repository object name contains spaces. pmrep prints a shorter format including the object type. includes the object type and object name. The character or set of characters used to separate object metadata columns. Append the results to the persistent output file instead of overwriting it. -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 . If you omit this option. you might want to avoid using a space as a column separator. You should also specify output_options. the word reusable or non-reusable. Print more than the minimum information about the objects. The default is newline /n. Specify 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 metadata. query. the object name and path. The short format for versioning objects such as label.

Deletes the repository tables from the database. See “Restoring a Repository (Restore)” on page 485. pmrepagent Commands pmrepagent Command Backup Bulkrestore Create Delete Registerplugin Restore Unregisterplugin Upgrade Command Description Backs up a repository. See “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. pmrepagent. See “Backing up a Repository (Backup)” on page 477. See “Upgrading a Repository (Upgrade)” on page 490. To run pmrepagent commands. Unregisters a plug-in module from the repository. Use this command when the repository is not running. Upgrades an existing repository to the latest version. Registers a new external module to the repository. switch to the Repository Server \bin directory and enter pmrepagent followed by the command name and its required options and arguments. Table 16-67 describes pmrepagent commands: Table 16-67. You must provide the backup filename. Specify pmrepagent options and arguments the same way you specify pmrep options and arguments. Restores a Teradata repository from a repository backup file using Fastload. See “Registering a Plug-in (Registerplugin)” on page 482. 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 . to perform repository functions such as restoring and deleting repositories. See “Deleting a Repository (Delete)” on page 481.pmrepagent Commands You can use the Repository Agent command line program. pmrepagent runs in command line mode only. See “Unregistering Plug-ins (Unregisterplugin)” on page 487. Restores a repository from a repository backup file. Creates repository tables in the database. See “Creating a Repository (Create)” on page 480. Backing up a Repository (Backup) The Backup command backs up a repository to the file specified with the -o option.

but not both. The repository database password. see “Backing up a Repository (Backup)” on page 416. For details. The repository database user name. The name and path of the file for the repository backup. Not required if you are using option -m. The connect string the Repository Agent uses to connect to the repository database. The repository password environment variable. Use the -x or -X option. but not both. Not required if you are using option -m. The repository database password. but not both. The repository user name. You can use the pmrep Backup command when the repository is running. -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. 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. Skips tables related to workflow and session logs during backup. Skips deployment group history during backup. Use a trusted connection to connect to the database. The type of database the repository resides on. Skips tables related to MX data during backup. The description of the repository you backup. Valid for Microsoft SQL Server only. 478 Chapter 16: Using pmrep and pmrepagent . For a list of connect string syntax. Use the -x or -X option. The repository password.Table 16-68 lists pmrepagent Backup options and arguments: Table 16-68. This option has no argument. see Table 16-1 on page 405. Use the -p or -P option. but not both. Include this option if you want to overwrite any existing file with the same name.

The repository database user name. The name of the Teradata database server. The port number of the Repository Server that manages the repository. -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 code page. 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. This option has no argument. The connect string the Repository Agent uses to connect to the repository database. Use the -p or -P option. 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. Enter “fastload” for Teradata. The Bulkrestore command can be faster than the Restore command when the repository backup file is greater than 100 MB. For a list of connect string syntax. but not both. see Table 16-1 on page 405. Use the -p or -P option. The repository database password environment variable. You can specify any file name and path local to the Repository Server. the Repository Server looks for the file in the Repository Server backup directory. The repository database password. Enter “Teradata” to restore to a Teradata database. If you do not specify a path. but not both. 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. The name of the repository backup file.Restoring Teradata Repositories using Fastload (Bulkrestore) The pmrepagent Bulkrestore command restores Teradata repositories using Fastload.

Use a trusted connection to connect to the database. For a list of connect string syntax. The repository database password. you must create and configure the database to contain the repository. The connect string the Repository Agent uses to connect to the repository database. 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. Before you can create a repository. Creating a Repository (Create) The pmrepagent Create command creates a repository in the database. Valid for Microsoft SQL Server only. but not both. Skips deployment group history during backup. 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. see Table 16-1 on page 405. 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. -P database_password_environme nt_variable n/a database_connect_string -m -c 480 Chapter 16: Using pmrep and pmrepagent . Skips tables related to MX data during backup. see “Creating a Repository” on page 116. Not required if you are using option -m. but not both. Use the -p or -P option. The repository database password environment variable. The repository database user name.Table 16-69. Enables object versioning. For more information on creating repositories. Use the -p or -P option. The type of database the repository resides on. Skips tables related to workflow and session logs during backup.

pmrepagent Commands 481 . see “Deleting a Repository” on page 64. This option has no argument. The port number of the Repository Server that manages 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. Use this option to specify the tablespace name for IBM DB2 EEE databases. Deleting a Repository (Delete) The pmrepagent Delete command deletes the repository tables from the repository database. The repository user name. Use the -x or -X option. For more information about deleting a repository. Use the following format to specify the tablespace name: “%tablespace=<tablespace_name>” Do not include spaces around the equals sign. This option has no argument. The host name of the Repository Server that manages the repository. Include this option if you want to promote the repository to a global repository. Include this option if you want to enables object versioning for the repository. Use the -x or -X option. -a -v Required Optional license_file_name n/a The name of the license file. pmrepagent interprets the spaces as part of the tablespace name. The repository password environment variable. 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.Table 16-70. but not both. 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. The repository password. but not both.

Use the -x or -X option. Use the -x or -X option. The repository user name. The connect string the Repository Agent uses to connect to the repository database. but not both. 482 Chapter 16: Using pmrep and pmrepagent . see Table 16-1 on page 405. 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. This option unregisters local repositories. 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. but not both. Use this option to delete a global repository. The repository database user name. see “Registering a Repository Plug-in” on page 85. The repository database password. The repository password. Registering a plug-in adds its functionality to the repository. but not both. -f Required/ Optional n/a Registering a Plug-in (Registerplugin) The pmrepagent Registerplugin command registers an external plug-in to a repository. For a list of connect string syntax. You can use the Registerplugin command to update existing plug-ins. For more information about registering a plug-in.Table 16-71. Use the -p or -P option. All registered local repositories must be running. 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. Use the -p or -P option. The repository password environment variable. but not both. The repository database password environment variable.

Use the -p or -P option. and you do not specify this option. Required if registering authentication module components. The password is not required if you are using option -m. Use the -w or -W option. Valid for Microsoft SQL Server only. it generates an error. see Table 16-1 on page 405. The external directory password of the user registering the module. The password is not required if you are using option -m.Table 16-72. This login becomes the administrator user name in the repository. but not both. The repository database password environment variable. 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. Indicates to use a trusted connection to connect to the database. or the registration fails. The repository database user name. Indicates to unregister and re-register a plug-in if it already exists. The name of the XML file describing the plug-in. The connect string the Repository Agent uses to connect to the repository database. The NIS login of the user registering an external security module. -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 . Do not use this option for other plug-ins. Not applicable for authentication modules. but not both. but not both. If the plug-in exists. For a list of connect string syntax. If the plug-in contains an authentication module you must supply the external login name. 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. Use the -p or -P option. The repository database password. Update an existing plug-in. Not applicable for authentication modules.

Use the -w or -W option. he decides to use the LDAP for repository user authentication. Do not use this option for other plug-ins. or the administrator cannot access the repository using LDAP. the administrator user must use this login name and password to access the repository. Note: The login name and password must be valid in the external directory. but not both. You can use the Registerplugin command to register the security plug-in. see “Registering and Unregistering LDAP Security Modules” on page 88.Table 16-72. When the Repository Agent loads the module. When he upgrades PowerCenter. Required if registering authentication module components. Stores the CRC of the plug-in library in the repository. For more information about this XML file. If the plug-in contains an authentication module you must supply the user password from the external directory or the registration fails. -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. After registration. The upgrade installs the LDAP security module in the repository security folder. 484 Chapter 16: Using pmrep and pmrepagent . 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. The -i option contains the XML file name that describes the security module. Example An administrator administers PowerCenter for a company that has a centralized LDAP NIS for 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. you must register the security module with 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. it checks the library against the CRC.

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. If the repository you are restoring uses an external directory service. The connect string the Repository Agent uses to connect to the repository database. The type of database you want to restore to. the Repository Agent unregisters the external module and resets the Administrator password after the restore. the Repository Agent does not assume that the same user authentication module is on the new system. The repository database password environment variable.Restoring a Repository (Restore) The pmrepagent Restore command restores a repository backup file to a database. For a list of connect string syntax. For more information about restoring a repository. The repository database password. 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. 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. Valid for Microsoft SQL Server only. If you do not use these options. 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.” Note: If the repository uses repository authentication. When you restore a repository to a different system. The repository code page. but not both. Use the -p or -P option. Not required if you are using option -m. or if the password is incorrect. but not both. The Repository Agent resets the Administrator’s password to “Administrator. The repository database user name. The target database must be empty. see “Restoring a Repository” on page 67. -P database_password_environme nt_variable n/a database_connect_string -m -c -d Optional code_page pmrepagent Commands 485 . see Table 16-1 on page 405. Not required if you are using option -m.

Use this option with the -v option when you want to retain the external security module after restoring. The name of the repository backup file. -x Required/ Optional verify_password 486 Chapter 16: Using pmrep and pmrepagent . The repository license file name. Include this option if you want to promote the repository to a global repository. -v Optional/ Required for retaining an external security module. pmrepagent interprets the spaces as part of the tablespace name. You can use any file name and path local to the Repository Server. You must use this option to retain the external module registration after the restore. Use this option to force the Repository Agent to verify that the administrator user is valid with the current authentication module. You must use either the -x or -X option when you want to retain an external security module. Use this option to specify the tablespace name for IBM DB2 EEE databases. The port number of the Repository Server that manages the repository. 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. Use this option only with a repository using an external security module. This option has no argument.Table 16-73. but not both. Use the -x or -X option. administrator_username Specifies repository administrator user name. 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. Use this option only with a repository using an external security module. The Repository Agent verifies that this password is valid for the user name on the target server. Verify password.

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. For more information. You must use either the -x or -X option when you want to retain an external security module. For more information on unregistering plug-ins. Restore Options and Arguments (pmrepagent) Option -X Required/ Optional Required/ Optional Argument Name verify_password_environment_ variable Argument Description The verify password environment variable. 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. Removes user name-login mapping. -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. see “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479.Table 16-73.rep Unregistering Plug-ins (Unregisterplugin) The pmrepagent Unregisterplugin command removes a plug-in from a repository. Use the -x or -X option. Skips tables related to MX data during backup. see “Unregistering a Repository Plug-in” on page 86. The Repository Agent verifies that this password is valid for the user name on the target server. Skips deployment group history during backup. Use this option only with a repository using an external security module. Use this option only when unregistering an external module. but not both. 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 . Use this option with the -v option when you want to retain the external security module after restoring. The name of the license file. Skips tables related to workflow and session logs during backup.

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

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

The repository database password environment variable. Not required if you are using option -m. Use the -x or -X option. The connect string the Repository Agent uses to connect to the repository database. but not both. The repository password. Valid for Microsoft SQL Server only. -P database_password_environment _variable n/a database_connect_string -m -c 490 Chapter 16: Using pmrep and pmrepagent . but not both. The repository user name. The type of database you want to upgrade to. see “Upgrading a Repository” in the Installation and Configuration Guide. Not required if you are using option -m. For more information on upgrading repositories. The repository password environment variable. Use the -p or -P option. The repository database password. 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. 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. but not both. The repository database user name. but not both. For a list of connect string syntax. see Table 16-1 on page 405. Use the -p or -P option.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. Use a trusted connection to connect to the database. Use the -x or -X option.

You cannot run pmrep batch files while in pmrep interactive mode.rep You can run script files from the command interface. This helps ensure you are performing tasks on the correct repository. Scripting pmrep and pmrepagent Commands 491 . In this case. you might use some commands with specific options and arguments on a regular basis.. Informatica recommends that you include a connect command as the first command called by the script file. For example. For instance.. pmrep and pmrepagent indicate the success or failure of a command with a return code. 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.. you might use pmrep to perform a daily backup of a production repository.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. Return code (1) indicates the command failed. c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup. the following Windows batch file.bat.Scripting pmrep and pmrepagent Commands When you use pmrep or pmrepagent. you can create a script file to call one or more pmrep commands including its options and arguments. Return code (0) indicates that the command succeeded. connects to and backs up a repository called Production on a server named Central: backupproduction.. backupproduction. Tip: When you create script files using pmrep commands.

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

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

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

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

To create a control file.dtd file: <!-.g. The import control file installs with the PowerCenter Client.Version 7.--> <!ELEMENT TYPEFILTER EMPTY> <!ATTLIST TYPEFILTER 496 Appendix A: Working with pmrep Files .Using the Object Import Control File When you use the pmrep ObjectImport command.Informatica Object Import Control DTD Grammar .dtd. e. The following is a sample of the impcntl. 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. you can supply a control file to answer questions that you normally address when you import objects with the Import Wizard. SOURCE.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. 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*. you must create an XML file defined by impcntl. TYPEFILTER*.dtd. but you must include its location in the input XML file. This should comforming to the element name in powermart. TARGET and etc.

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 . 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. typename etc.TYPENAME > CDATA #REQUIRED <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import.

Object type for this conflict resolution. or Rename. Specifies the import folder name to match to a folder in the target repository. Copies SAP program information into the target repository. Allows you to specify conflict resolutions for objects. Specifies the target folder name for matching. Source DBD name to identify source object. Specific object name for this conflict resolution. Imports just the objects from a specific node. Identifies objects by type. Applies the label name on the imported objects. Reuse. or mappings. Specifies the repository containing the target folder. Retains existing Sequence Generator. Replace. targets. Replace. Reuse. for conflict resolution specification. Applies the default connection when a connection used by a session does not exist in the target repository. or Rename. such as sources. Identifies objects from this query result for conflict resolution specification. 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. and XML Source Qualifier transformation current values in the destination. Specifies the repository containing the source folder. Replace. Normalizer. 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 . Reuse. Rename. Applies the comments to the checked in objects. The default connection is the first connection from the sorted list of available connections.Object Import Control File Parameters Table A-1 lists pmrep Object Import control file parameters: Table A-1. Identifies objects by label name for conflict resolution specification. Find the list of connections in the Workflow Manager.

The repository containing the object.Table A-1. or Rename. 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. Reuse. Replace.

” However. you want to rename conflicting source objects that contain “Yr_End” in the object name.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. specifying resolutions for object types.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.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 . The file specifies the target folder and repository.0" encoding="ISO-8859-1"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. <?xml version="1. you want to replace all the duplicate objects labeled “Monthend. In the target folder. You have a query called “yr_end_qry” that finds these objects. and specifying resolutions for specific objects.Example Suppose you want to import only source objects. including specifying a resolution for query results. It specifies to check in the imported objects and label them.

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.g. SOURCE. e.--> <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. 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.

) 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 .<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. 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 .

Using the Deployment Control File When you use DeployDeploymentGroup or DeployFolder pmrep commands. The following is a sample of the depcntl. you can use a control file to answer questions that you see when you deploy objects using the Copy Wizard. 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?.dtd file.dtd. <!ELEMENT DEPLOYPARAMS (DEPLOYFOLDER?. but you should include its location in the input XML file. To use pmrep deployment commands you must create an XML file that works with depcntl. The deployment control file installs with the PowerCenter Client. 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 .

Retains workflow session logs in the target. Copies workflow logs. 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. Copies only the latest version. 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. Name the folder after replacing it. Retains workflow variable persistent values. Specifies the current folder that shortcuts point to. Keeps the current value for Sequence Generator or Normalizer transformations. Copies mapping variable persistent values. Does not allow replacing of manually modified target folders. Creates a new folder with this name. Indicates local or global folder. Retains mapping variable persistent values in the target. Retains server network related values in tasks.<!--criteria for clearing a source group in DeployDeploymentGroup--> <!ELEMENT DEPLOYGROUP (OVERRIDEFOLDER*. Copies SAP R/3 installed ABAP program. Copies workflow variable persistent values. Using the Deployment Control File 505 .

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 .Table A-2. Indicates local or global folder. Removes objects from source group after deploying. If the Repository Agent detects the label is applied to another version of the same object.” You might create a control file with following attributes: <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE DEPLOYPARAMS SYSTEM "depcntl. and you need to point the shortcuts from the sc_folder to the new_sc_folder. Moves the label from a different version of the object in the source group to the deployment group version of the object. you can choose to move the label to the latest version of the object. 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. TARGETLABELNAME TARGETMOVELABEL Example Suppose you want to deploy the latest version of a folder and include all dependencies. Applies a label to all the objects deployed to the target repository. If the Repository Agent detects the label is applied to another version of the same object. you want to rename it to “new_year. you can choose to move the label to the selected version of the object. Moves the label from a different version of the object in the target group to the deployment group version of the object. You need to retain the current values in a Sequence Generator transformation. After you copy the folder. Applies a label to all the objects in the source group.

pmrep and pmrepagent indicate the success or failure of a command with a return code. For example. Scripting pmrep and pmrepagent Commands 507 . c:\PowerCenter\pmrep\pmrep backup -o c:\backup\Production_backup.bat.rep You can run script files from the command interface. backupproduction. you can create a script file to call one or more pmrep commands including options and arguments. Return code (-1) indicates the command failed..Scripting pmrep and pmrepagent Commands When you use pmrep or pmrepagent. the following Windows batch file. You cannot run pmrep batch files while in pmrep interactive mode. Informatica recommends that you include a connect command as the first command called by the script file. connects to and backs up a repository called Production on a server named Central: backupproduction.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... you might use pmrep to perform a daily backup of a production repository. Return code (0) indicates that the command succeeded. Tip: When you create script files using pmrep commands. In this case.. you might use commands with specific options and arguments on a regular basis. For instance. This helps ensure you are performing tasks on the correct repository. 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.

508 Appendix A: Working with pmrep Files .

510 Workflow Manager 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. 520 509 . 516 pmrep Tasks. 519 pmrepagent Tasks. 513 pmcmd Tasks. It then lists the repository privileges and folder permissions required to perform each task in these tools: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Designer Tasks.

Read and write permission in the destination folder. Read permission in the originating folder. 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. targets. Read and write permission for the destination folder. For example. 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 .Designer Tasks To perform the following Designer tasks. transformations. targets. you must have one of the listed sets of privileges and permissions. transformations. 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/edit sources. Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources.

you must have one of the listed sets of privileges and permissions. 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.Workflow Manager Tasks To perform the following Workflow Manager tasks. if you enabled enhanced security. Write permission and belong to the same group as the owner of the connection object. 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 . 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. Table B-2 lists the required privileges and permissions for Workflow Manager tasks: Table B-2. For example.

FTP. 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. 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 . 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. and external loader connections in the Workflow Manager Edit database.Table B-2.

Super User privilege Table B-3 lists the required privileges and permissions for Workflow Monitor tasks: Table B-3. Use Workflow Manager privilege with read and execute permissions 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 . 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. you must have one of the listed sets of privileges and permissions.Workflow Monitor Tasks To perform the following Workflow Monitor tasks.

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 .

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. 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 . Table B-4 lists the required privileges and permissions for pmcmd tasks: Table B-4. For example.pmcmd Tasks To perform the following pmcmd tasks. 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.

Repository Manager Tasks To perform the following Repository Manager tasks. 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. you must have one of the listed sets of privileges and permissions. 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 . For example.

export.Table B-5. 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 . or remove the registry Manage users. 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. groups.

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 .Table B-5.

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. 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 .pmrep Tasks To perform the following pmrep tasks. For example. you must have one of the listed sets of privileges and permissions.

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

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 .

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.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. 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 .

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 .

276 parent objects 271 permissions 266 524 Index .recovering deleted objects 215 repositories 64 repositories using pmrepagent 481 user groups 129 versioned objects 215 depcntl.dtd listing 504 dependencies source-target 27 viewing 27. 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.

powrmart.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. 171 renaming 173 Repository Manager uses 166 shared 15. 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 . 168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245. 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. 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. 192 creating 14 promoting 112. 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.

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. 462 applying when importing 280 526 Index creating 219. 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 .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.dtd 496 Import Wizard 287 multiple objects 269 ObjectImport XML example 500 overview 264 parent objects 271 permissions 266 powrmart.

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. 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 . 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.

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 .MX (Metadata Exchange) Change Management views 398 database definition views 338 deployment views 392.

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. 432 importing 280. 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 .

dtd overview 267 privileges See also permissions See also repository privileges Administration Console tasks 50 530 Index . 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.

160 security log file 153 security. 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. 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. 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.Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. 75. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126. 117. 50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. troubleshooting 163 starting 71 Index 531 . 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. overview 155 overview 2.

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.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. 147 repository security level description (folder) 148 Repository Server Administration Console 50 architecture 3 client connections 3 532 Index .

250 copying 195 default names 184 dependencies 27 Index 533 .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.

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. 192 importing 274 local 182. 190. 187 overview 182 properties 184 referenced objects 183.

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 . 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.

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 .