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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

flat files. Emphasized subjects. This is generic text that should be replaced with user-supplied values. The material in this book is available for online use. or mainframe systems in your environment. italicized text boldfaced text italicized monospaced text Note: Tip: Warning: monospaced text bold monospaced text Preface xxxvii . refer to the documentation accompanying your database products. The following paragraph provides suggested uses. The following paragraph provides additional facts. This guide assumes you have knowledge of relational database concepts. This is a code example. unless you follow the specified procedure. The following paragraph notes situations where you can overwrite or corrupt data.About this Book The Repository Guide is written for the database administrator and developers who manage the repositories. and the database engines. 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. For additional information on related database connectivity issues not covered by this guide.

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

Progress Indicator 22 Chapter 2: Using the Repository Manager . Repository Manager Components Navigator Window Dependency Window Output Window Status Bar Main Window When the Repository Manager accesses the repository. 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. The Repository Manager can display the following windows: ♦ ♦ ♦ ♦ Navigator Main Dependency Output Figure 2-1 shows the Repository Manager components: Figure 2-1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

To view user connection details: 1. The TCP/IP address of the machine associated with the connection. Viewing Connection Details in the Repository Manager Use the following procedure to view connection details in the Repository Manager. The time the user connected to the repository.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 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. The identification number assigned to the repository connection. Table 3-5 describes the repository user connection details: Table 3-5. Viewing User Connections You can use the Repository Manager or the Administration Console to view connection details for users and applications connected to the repository. Launch the Repository Manager and connect to the repository. The port number the machine hosting the repository client application uses to communicate with the repository. The repository client application associated with the connection.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Change owner. Change group. Click to define permissions. To configure permissions for versioning objects. folder permissions. 150 Chapter 5: Repository Security . see “Repository Privileges” on page 142. select a versioning object in a versioning objects browser and click 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. The Permissions dialog box displays. Add a new group or user. and versioning object permissions.

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

Table 6-3 lists objects the wizard compares by default when you select certain objects to compare: Table 6-3. Compared Objects in Compare Selected Object Source field Target field Reusable transformation field Mapping variable External procedure initialization properties Session component Compared Object Source Target Reusable transformation Mapping Transformation instance Session Comparing Folders 175 . 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-2. regardless of whether you select the other objects to compare.

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

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

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

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

180 Chapter 6: Working with Folders .

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

the Designer creates a copy of the object instead. 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 always inherits the properties of the latest version of the object that it references. one in each folder. Once you create a shortcut. Note: In a versioned repository. ensuring uniform metadata. 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. For example. you use a source definition in 10 mappings in 10 different folders. By using a shortcut instead of a copy. A shortcut created in the same repository as the original object. and you add a column to the definition. When the object the shortcut references changes. You can create shortcuts to objects in shared folders. you can create 10 shortcuts to the original source definition. You can create the following types of shortcuts: ♦ ♦ 182 Chapter 7: Local and Global Shortcuts . the shortcut inherits the additional column. Instead of creating 10 copies of the same source definition. the shortcut inherits those changes. you ensure each use of the shortcut matches the original object. For example. Global shortcut. A shortcut created in a local repository that references an object in a global repository. if you have a shortcut to a target definition. you can configure the shortcut name and description.Overview Shortcuts allow you to use metadata across folders without making copies.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. 286 Chapter 11: Exporting and Importing Objects . 7. You can click View File to view the XML file the PowerCenter Client creates. Click Close in the Exported Objects dialog box.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

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

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

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

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

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

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Transformation field ID. Object (session. REP_WIDGET_FIELD This view displays field level details for transformations. Table 15-37 lists transformation field information in the REP_WIDGET_FIELD view: Table 15-37. Transformation Views 369 . Table 15-36. Partition ID. REP_WIDGET_FIELD MX View Column Name WIDGET_ID FIELD_NAME FIELD_ID WGT_PREC Datatype NUMBER VARCHAR2 (240) NUMBER NUMBER Description Transformation ID. 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 type. Attribute value. Attribute ID. Informatica recommends using the fields in bold to join views. Session task ID. or transformation) version number. Transformation field name. Attribute data type Attribute name. Transformation type. instances. Table 15-36 lists attribute details for transformations. Instance ID. instances. Object type ID. and sessions. Used to break up long strings into multiple rows. mapping. and sessions. Transformation field precision. Description of the attribute.REP_WIDGET_ATTR This view displays attribute details for transformations. Mapping ID.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Informatica recommends using the fields in bold to join views. Label description.Table 15-75. 400 Chapter 15: Using Metadata Exchange (MX) Views . 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 .

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

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

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

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

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

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

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

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

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

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

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

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. The hostname of the Repository Server that manages the repository to stop. The Repository Server port number. When you use this option. you must also use the -o and -r options.Table 16-25 lists pmrep StopRepository option and argument: Table 16-25. When you use this option. When you use SwitchConnection. The name of the repository to stop. you must also use the -h and -o options. you must also use the -h and -r options. You must be connected to a repository to use this command. you have a relational and an application source. you specified the name ITEMS for a relational source connection instead of Relational:ITEMS. -A repserver_password_ environment_variable -h Optional hostname -o -r Optional Optional port_number repository_name Changing the Connection Name (SwitchConnection) The SwitchConnection command changes the name of an existing connection. When you use this option. In a session. pmrep does not replace any relational connection in the repository because it cannot determine the connection type for the source connection entered as ITEMS. Use the -a or -A option. each called ITEMS. 438 Chapter 16: Using pmrep and pmrepagent . Use the -a or -A option. but not both. When you use SwitchConnection to replace the relational connection ITEMS with another relational connection. but not both. 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. the Repository Server replaces the relational connection. The password environment variable you use to administer the Repository Server that manages the repository.

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

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

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

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

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

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

The difference between two consecutive values from the NEXTVAL port. If you designate an invalid value. it fails the session. pmrep gives an error message and does not update the Sequence Generator transformation. If you designate an invalid value. the PowerCenter Server cycles back to this value when it reaches the end value. To update source table owner names. The maximum value the PowerCenter Server generates. 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 . 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. If you designate an invalid value. pmrep updates source table owner names only if you previously edited the source table name in the session properties.Table 16-32. If you want to cycle through a series of values. Enter the value you want the PowerCenter Server to use as the first value in the sequence. pmrep gives an error message and does not update the Sequence Generator transformation. -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. The current value of the sequence. If the PowerCenter Server reaches this value during the session and the sequence is not configured to cycle. If you designate an invalid value. If you select Cycle in the transformation properties. Updatesrcprefix updates the owner name for source tables at the session level. Updateseqgenvals Options and Arguments (pmrep) Option -s Required/ Optional Optional Argument Name start_value Argument Description The start value of the generated sequence you want the PowerCenter Server to use if the Sequence Generator transformation uses the Cycle property. pmrep gives an error message and does not update the Sequence Generator transformation. You can update the owner name for one or all sources in a session. You must connect to a repository to use this command.

This option has no argument. When you do not include this option. The name of the session containing the sources to update. -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. but you can change the case of the default server variables. Informatica recommends you include the -n option.source_name. specify session_name.When you omit the -n option. The name of the source to update. enter the name of the source instance as displayed in the session properties or as output by the Listtablesbysess command. Updatesrvvar uses the following command syntax: updatesrvvar -s server_name -v variable_name -u new_value 446 Chapter 16: Using pmrep and pmrepagent . pmrep updates all source table owner names in the session. You cannot change default server variables.session_name. For a list of server variables. This command requires you to connect to a repository.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. such as worklet_name. If you omit this option. The owner name you want to update in the source table.When you include the -n option. see “Configuring the Workflow Manager” in the Workflow Administration Guide. You can update any of the PowerCenter Server variables using Updatesrvvar. pmrep matches the source_name argument with source instance names. 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. For non-reusable sessions. pmrep matches the source_name argument with the source table names.session_name or workflow_name. The Designer generates the dbd name from the source type or data source name when you create a source definition in the repository. You can find the source dbd name in the Designer Navigator. . you must also specify the session path. . For reusable sessions. you must enter the dbd name and the source table name as dbd_name. When you include this option.

The update fails if you do not have Administer Repository privilege. pmrep Repository Commands 447 . 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. Updatetargprefix updates the target table name prefix at the session level. pmrep updates table name prefixes if you previously edited the table name prefix at the session level. The table name prefix specifies the owner of the table in the database. see “Updating Repository Statistics” on page 60. Name of the server variable to update. 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. To update repository statistics. 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. For more information about updating statistics. you must have Administer Repository privilege. Value of updated server variable. 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 connect to a repository to use this command.Table 16-34 lists pmrep Updatesrvvar options and arguments: Table 16-34.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

496 Using the Deployment Control File. 507 493 .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.

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

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

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

) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name . typename etc. 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 > CDATA #REQUIRED <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import.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 .

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

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

specifying resolutions for object types. It specifies to check in the imported objects and label them.dtd"> <!--IMPORTPARAMS This inputs the options and inputs required for import operation --> <!--CHECKIN_AFTER_IMPORT Check in objects on successful import operation --> <!--CHECKIN_COMMENTS Check in comments --> <!--APPLY_LABEL_NAME Apply the given label name on imported objects --> 500 Appendix A: Working with pmrep Files . you want to rename conflicting source objects that contain “Yr_End” in the object name. You have a query called “yr_end_qry” that finds these objects. It lists what types of objects to import and shows several methods that you can use to resolve conflicts. and specifying resolutions for specific objects.” However. <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. including specifying a resolution for query results. you want to replace all the duplicate objects labeled “Monthend.Example Suppose you want to import only source objects. In the target folder.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. You might create a control file with the following attributes: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. The file specifies the target folder and repository.

SOURCE.dtd.g. e. TARGET and etc. 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 . This should conforming to the element name in powermart.<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.--> <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.

) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .required for source object to identify uniquely--> <!--OBJECTTYPENAME Object type name--> <!--FOLDERNAME Folder which the object belongs to--> <!--REPOSITORYNAME Repository name that this object belongs to--> <!--RESOLUTION Resolution to apply for the object in case of conflict--> <SPECIFICOBJECT NAME="ADDRESS" DBDNAME="sol805" OBJECTTYPENAME="Source Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="ADDRESS1" DBDNAME="sol805" OBJECTTYPENAME="Target Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="MAP_MLET_ADD1" OBJECTTYPENAME="Mapplet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="MAP_ADD1" OBJECTTYPENAME="Mapping" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="R_AGG1" OBJECTTYPENAME="Aggregator" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_CUSTOM11_M" OBJECTTYPENAME="Custom Transformation" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_EXP11_M" OBJECTTYPENAME="Expression" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_FIL11_M" OBJECTTYPENAME="Filter" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> 502 Appendix A: Working with pmrep Files . typename etc.<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.

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

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

Deployment Control File Elements and Attributes (pmrep) Element DEPLOYPARMS Attribute Name DEFAULTSERVERNAME COPYPROGRAMINFO COPYMAPVARPERVALS COPYWFLOWVARPERVALS COPYWFLOWSESSLOGS COPYDEPENDENCY LATESTVERSIONONLY RETAINGENERATEDVAL RETAINSERVERNETVALS DEPLOYFOLDER REPLACEFOLDER NEWFOLDERNAME FOLDERNAME RETAINMAPVARPERVALS RETAINFLOWVARPERVALS RETAINWFLOWSESSLOGS MODIFIEDMANUALLY OVERRIDEFOLDER SOURCEFOLDERNAME SOURCEFOLDERTYPE Attribute Description Specifies the PowerCenter Server in the target repository to run workflows. Retains workflow session logs in the target. Retains workflow variable persistent values. Copies workflow variable persistent values.<!--criteria for clearing a source group in DeployDeploymentGroup--> <!ELEMENT DEPLOYGROUP (OVERRIDEFOLDER*. Retains mapping variable persistent values in the target. Name the folder after replacing it. Using the Deployment Control File 505 . Keeps the current value for Sequence Generator or Normalizer transformations. Indicates local or global folder. Copies mapping variable persistent values. Retains server network related values in tasks. 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 workflow logs. Copies dependency information for objects in mappings. Creates a new folder with this name. Specifies the current folder that shortcuts point to. Copies SAP R/3 installed ABAP program. Does not allow replacing of manually modified target folders.

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

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

508 Appendix A: Working with pmrep Files .

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

and mappings Create shortcuts from a shared folder Repository Privilege Use Designer Use Designer Use Designer Use Designer Folder Permission None required Read Read/Write Read permission in the shared folder. Read and write permission in the destination folder. 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. Read permission in the originating folder. and mappings Create/edit sources.Designer Tasks To perform the following Designer tasks. you must have one of the listed sets of privileges and permissions. 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 . For example. Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources. targets. Read and write permission for the destination folder. targets. transformations. transformations.

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

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 . 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. 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.Table B-2. FTP.

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

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 .

For example. 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.pmcmd Tasks To perform the following pmcmd tasks. you must have one of the listed sets of privileges and permissions. Table B-4 lists the required privileges and permissions for pmcmd tasks: Table B-4. Required Privileges and Permissions for pmcmd Tasks pmcmd Task Ping the PowerCenter Server Stop the PowerCenter Server All other tasks Repository Privilege None required Administer Server Use Workflow Manager Workflow Operator Folder Permission None required None required Execute None required Connection Object Permission None required None required Execute Execute pmcmd Tasks 515 . you must have execute permission for connection objects associated with the session in addition to the privileges and permissions listed above.

you can edit the properties of a folder if you have one of the following sets of permissions or privileges: ♦ ♦ ♦ Browse Repository privilege. you must have one of the listed sets of privileges and permissions. For example. 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. 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 .Repository Manager Tasks To perform the following Repository Manager tasks.

or remove the registry Manage users. and privileges Mass update Purge (versioning) Receive user and group notifications Recover Remove Label References Run Query Use Repository Manager Browse Repository Administer Repository Super User Administer Repository Super User Use Repository Manager Use Repository Manager Browse Repository Manager Folder Permission None required N/A N/A N/A Write Folder owner and read permission Read N/A Read on the original folder.Table B-5. 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. groups. export. 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 .

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.

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

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

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 .

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 . 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.ApplyLabel description 462 associating server with sessions 245 audit trails 208 configuration setting 110 creating 153 authenticating users description 131 authentication switching methods 133 using LDAP 131 B backing up repositories 66 repositories with pmrep 416 repositories with pmrepagent 477 Backup command pmrep 416 pmrepagent 477 Bulkrestore command description 479 C Changepassword description 450 Checkin description 464 CheckinCommentsRequired repository configuration 110 checking in description 213 non-reusable objects 213 when importing objects 280 checking out description 211 non-reusable objects 211 undoing a checkout 213 checkouts searching for checked out objects 211 viewing 211 Cleanup description 411 ClearDeploymentGroup description 465 code pages See also Installation and Configuration Guide 522 Index exporting objects 266 global repository 117 importing objects 266 local repository 75 repository 51. 45 conflicts copying Designer objects 310 copying workflow segments 308 database connections 307 mapping 307 resolving when importing 281 connect string examples 405 syntax 405 connecting to repositories 30.

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

dtd 504 rolling back a deployment 238 deployment groups copying 254. 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.dtd listing 504 dependencies source-target 27 viewing 27. 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. 37 dependent objects exporting and importing 270 DeployDeploymentGroup description 467 DeployFolder description 469 deploying objects depcntl.

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. 192 creating 14 promoting 112.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. 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. 117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182. 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. 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.

462 applying when importing 280 526 Index creating 219.importing metadata 314 objects 280 ODBC data sources 33 registries 32 repository configurations 115 sources and target 314 importing objects code pages 266 CRCVALUE codes 267 dependent objects 270 DTD file 267 impcntl.dtd 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. 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 496 Import Wizard 287 multiple objects 269 ObjectImport XML example 500 overview 264 parent objects 271 permissions 266 powrmart.

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. 192 promoting to global 112 registering 75 local shortcuts behavior when copying folders 249 creating 187 definition 182.local repositories See also repositories code page 75.

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

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

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

50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. 250 reports metadata 335 repositories adding 29 adding metadata 9 administration overview 11 architecture 3 avoiding shared accounts 160 backing up 66 backing up with pmrepagent 477 changing a code page 117 checking status 54 code pages 51. 421 enabling 71 enabling version control 118 exporting/importing registries 32 licenses 120 limiting access 161 locks 154 log file codes 97 log files 97 managing 52 moving to a different Repository Server 77 object locking. 160 security log file 153 security. troubleshooting 163 starting 71 Index 531 .Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. 158 removerepsitory description 435 removing repositories 29 users 141 replacing folders 248. overview 155 overview 2. 75. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126. 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. 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. 117.

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

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

190.description 9 descriptions inherited 184 exporting 270 global 182. 187 overview 182 properties 184 referenced objects 183. 192 importing 274 local 182. 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 .

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 .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. 152 viewing 79.

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 .