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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

Repository Manager Components Navigator Window Dependency Window Output Window Status Bar Main Window When the Repository Manager accesses the repository.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. the Status Bar reflects the connection in progress with a progress indicator. Progress Indicator 22 Chapter 2: Using the Repository Manager .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 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. Table 3-5 describes the repository user connection details: Table 3-5. Launch the Repository Manager and connect to the repository. The repository client application associated with the connection. The name of the machine running the application. To view user connection details: 1. Viewing User Connections You can use the Repository Manager or the Administration Console to view connection details for users and applications connected to the repository. The identification number assigned to the repository connection.Viewing User Connections and Locks The Repository Manager and Administration Console allow you to view the connection details and locks details for users connected to a repository. The time the user connected to the repository. The port number the machine hosting the repository client application uses to communicate with the repository.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

The group to which the user belongs appears in the Member Of list. select the group in the Not Member list.4. with no leading or trailing spaces. 6. To add the user to a group. Enter a user name and password between 1 and 75 characters long. Creating and Editing Repository Users 135 . Click Group Memberships. 5. 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. and click Add.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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. 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 . Table 6-3 lists objects the wizard compares by default when you select certain objects to compare: Table 6-3. regardless of whether you select the other objects to compare.

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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. as well as comments for the shortcut: Figure 7-1. Object and Shortcut Description Description from the original object Description added to the shortcut Shortcuts do not inherit edits to the description of the referenced object. However. Figure 7-1 shows the shortcut with a description inherited from the original transformation. The shortcut object displays the following details about the referenced object: ♦ ♦ ♦ Repository name Folder name Table or transformation name Understanding Shortcut Properties 185 .

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

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

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

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

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

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

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

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

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

Labels Properties On the Labels tab. Object Status Properties On the Object Status tab. 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. and comments associated with the label. Working with Version Properties 205 . For each label. you can view all labels applied to the object. you can view the current status of the object. Labels Properties For more information on creating and applying labels. the time the label was applied. you can also view the name of the user who applied the label.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. The wizard takes you back to Select Shared Folders dialog box. If there are differences between the folders.Table 10-3. Displays objects that exist in the local shared folder but not in the global shared folder. Copying a Deployment Group 261 . Lists the results from the folder compare. Copy Deployment Group Wizard Prompts Copy Deployment Group Wizard Dialog Box Compare Shared Folder Compare Results Mode Advanced Advanced Prompt Allows you to compare folders if the folders you choose in Override Shared Folder dialog box are different.

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Conflict Resolution Wizard The Conflict Resolution Wizard is similar to the Copy Wizard. The Import Wizard is ready to import these objects. see “Copying Objects” on page 297. you return to the Import Wizard. It also displays the object resolution status for objects in each folder: ♦ Unresolved. ♦ When the Import Wizard detects unresolved conflicts for objects in a folder. it opens the Conflict Resolution Wizard. For information on resolving conflicts in the Copy Wizard. However. Resolved. Some objects in this folder conflict with objects in the target folder. 284 Chapter 11: Exporting and Importing Objects .The Import Wizard displays all folders listed in the XML file. Click Resolve to resolve the object conflicts. No object in this folder conflicts with objects in the target folder. After you resolve object conflicts in the Conflict Resolution Wizard. You must resolve all object conflicts before you can import objects. 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. Figure 11-5 shows the Conflict Resolution Wizard: Figure 11-5.

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

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

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

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

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

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

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

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

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

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. When you resolve conflicts for all objects in all folders. the Import Wizard displays the status of that folder as unresolved. Note: If you cancel the Conflict Resolution Wizard for a folder. Click Resolve in the Action column for that folder to open the Conflict Resolution Wizard and resolve the object conflicts. the Import Wizard proceeds with the import process.The Import Wizard opens the Conflict Resolution Wizard for objects in any other folder listed in the XML file.

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

For example. 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. make sure the source is not a VSAM source. Make sure that the metadata you define in the XML file is valid. When I tried to import a shortcut to an object. To import a shortcut to an object into a repository. it imports the object the shortcut references using the metadata in the XML file. 296 Chapter 11: Exporting and Importing Objects . the Designer must be able to connect to the source repository to re-establish the shortcut. the Designer imported the actual object instead of the shortcut. I imported a mapping from an XML file I modified. The Designer marks mapplets with VSAM sources as invalid. if you edit the metadata for a mapplet. but the Designer marked it invalid.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Open a target 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. 2. Copy the segment to the clipboard by pressing Ctrl+C or choosing Edit-Copy. Copying Designer Objects 311 . 4. Choose Edit-Paste or press Ctrl+V. the Designer assigns a unique name to the new object. Select a segment by highlighting each object you want to copy. 3. If you are creating duplicate objects in a folder.To copy a segment of a mapping or mapplet: 1. You can select multiple objects. Open a mapping or mapplet. 5.

312 Chapter 12: Copying Objects .

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

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

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

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

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

7. 318 Chapter 13: Exchanging Metadata . 8. 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.

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

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

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

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

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. For more information on comparing sources or targets.10. Steps for Importing Metadata 323 . 11. 12. see “Comparing Objects” in the Designer Guide. Click Next to proceed through the Conflict Resolution Wizard. Click Close when you resolve all conflicts. The Metadata Import Wizard imports all objects.

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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

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

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

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

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

The next generation of MX. SQL Script to Drop MX Views Repository Database Sybase Teradata SQL Script sybmxdrp. from pulling the Informatica metadata into product or user repositories to providing dynamic desktop pass-through access. Viewing the Repository Metadata 337 . called Metadata Exchange SDK. Software vendors can integrate Informatica metadata with their products through different methods. 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.Table 15-3.sq_ termxdrp.sq_ These SQL scripts are stored in the PowerCenter Repository Server installation directory. Integrating MX Views with Third-Party Software With MX software and support from Informatica.

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

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

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

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

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

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

Source description. REP_SRC_TBLS MX View Column Name TABLE_NAME TABLE_BUSNAME TABLE_ID SUBJECT_AREA DATABASE_TYPE DATABASE_NAME SCHEMA_NAME FIRST_FIELD_ID SOURCE_DESCRIPTION VERSION_ID VERSION_NAME LAST_SAVED SOURCE_VERSION_NUMBER SUBJECT_ID Datatype VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2( 240) VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) INTEGER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER Description Table name. Folder version ID. Informatica recommends using the fields in bold to join views. Source description. Link to first field. Name 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. Informatica recommends using the fields in bold to join views. Name of schema extracted from. Table 15-9 lists relational database table information in the REP_SRC_TBLS view: Table 15-9. Business name of the table. Type of database extracted from. 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. Folder version name. 344 Chapter 15: Using Metadata Exchange (MX) Views . Source version number. Source version number. Unique key. Version ID. Folder name. Last time the source table was saved.Table 15-8.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

which might contain one or many target tables. Number of failed source rows. 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. and Task Views 387 . 1 = Suceeded 2 = Disabled 3 = Failed 4 = Stopped 5 = Aborted 6 = Running 7 = Suspending 8 = Suspended 9 = Stopping 10 = Aborting 11 = Waiting 12 = Scheduled 13 = Unscheduled 14 = Unknown 15 = Terminated Last error code. Last error message. Worklet. Number of successfully loaded target rows. Location of the reject file. Table 15-58 lists session log information in the REP_SESS_LOG view: Table 15-58. Actual time session started. Number of failed target rows. Session instance name.REP_SESS_LOG This view provides log information about sessions. Session log file name. First error code. Session ID. Workflow version number. 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. Time completed. Run status code. Number of successfully read source rows. This view supplies the status of the last session. Folder ID. Version number of the task.

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

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

see “REP_USER_GROUPS” on page 391. User name. For more information. 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). For more information. Informatica recommends using the fields in bold to join views. 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. REP_USERS 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. For more information. 1 = valid. Specifies whether the user is system-created or usercreated. see “REP_USERS” on page 390. Unique global user ID. Specifies whether user is valid. 0 = disabled. Specifies whether user can log in. Description of the user. 1 = user-created. Table 15-61 lists user information in the REP_USERS view: Table 15-61. 390 Chapter 15: Using Metadata Exchange (MX) Views . 0 = system-created. 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. Privileges granted to the user. see “REP_GROUPS” on page 391. 0 = deleted. Table 15-60 lists the different views that help you analyze security metadata: Table 15-60. 1 = enabled. User login ID used by external authentication modules. User contact information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 .Table 16-16 lists the transformation types and values to use with pmrep commands: Table 16-16.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Table 16-34 lists pmrep Updatesrvvar options and arguments: Table 16-34. The command returns “updatestatistics successfully completed” or returns “updatestatistics failed” message. UpdateStatistics uses the following command syntax: updatestatistics -s tables-to-skip_file_name Table 16-35 lists pmrep Updatestatistics options and arguments: Table 16-35. Updating the Target Table Name Prefix (Updatetargprefix) Use the Updatetargprefix command to update the table name prefix for session target tables. Updatetargprefix updates the target table name prefix at the session level. For more information about updating statistics. see “Updating Repository Statistics” on page 60. To update repository statistics. Name of the server variable to update. You can update the owner name for one or all targets specified in a session. The update fails if you do not have Administer Repository privilege. You must connect to a repository to use this command. 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. The table name prefix specifies the owner of the table in the database. Updating Repository Statistics (UpdateStatistics) The UpdateStatistics command updates statistics for repository tables and indexes. pmrep updates table name prefixes if you previously edited the table name prefix at the session level. you must have Administer Repository privilege. 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. pmrep Repository Commands 447 . Value of updated server variable.

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

Removes a user from the repository. See “Creating a User (Createuser)” on page 452. See “Removing a Privilege (Rmprivilege)” on page 458. See “Listing All Users (Listallusers)” on page 455. See “Adding a User to a Group (Addusertogroup)” on page 450. Removes a group from the repository. Edits the profile of a user. See “Removing a User from a Group (Rmuserfromgroup)” on page 459. See “Creating a Folder (CreateFolder)” on page 451. Creates a new folder. Registers a user from an external directory service to access the Repository. See “Registering a User (Registeruser)” on page 457. Lists all privileges that you can assign to a user or group. Creates a user. Creates a group. pmrep Security Commands 449 . See “Creating a Group (Creategroup)” on page 452. See “Changing the Repository Password (Changepasswd)” on page 450. Table 16-37 describes commands you use to perform repository security tasks: Table 16-37.pmrep Security Commands pmrep allows you to perform security tasks for users and groups. Lists all groups registered with the repository. Removes a user from a group. Lists all users registered with the repository. Modifies folder properties. See “Modify Folder Properties (ModifyFolder)” on page 456. See “Removing a User (Rmuser)” on page 458. Changes the password for the user currently connected to the repository. pmrep Security Commands pmrep Command Addprivilege Addusertogroup Changepasswd CreateFolder Creategroup Createuser DeleteFolder Edituser Listallgroups Listallprivileges Listallusers ModifyFolder Registeruser Rmgroup Rmprivilege Rmuser Rmuserfromgroup Command Description Adds a privilege to a user or group. See “Deleting a Folder (DeleteFolder)” on page 453. See “Adding a Privilege (Addprivilege)” on page 450. See “Removing a Group (Rmgroup)” on page 457. See “Editing a User (Edituser)” on page 454. Deletes a folder. See “Listing All Privileges (Listallprivileges)” on page 455. Adds a user to a group. See “Listing All Groups (Listallgroups)” on page 455. You must have the Administer Repository privilege to use pmrep repository security commands. Removes a privilege from a user or 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. Addprivilege Options and Arguments (pmrep) Option -p Required/ Optional Required Argument Name privilege Argument Description The privilege you want to add. Changing the Repository Password (Changepasswd) The Changepasswd command changes the password of the user currently connected to the repository. such as “Administer Repository. If you use this option. Note: You cannot use this command with an external security module. To add a privilege to a user or a group. 450 Chapter 16: Using pmrep and pmrepagent . use the following syntax: addprivilege -p privilege -u username -g group_name Table 16-38 lists pmrep Addprivilege options and arguments: Table 16-38. The user inherits all of the permissions and privileges associated with the group. It cannot add a privilege to a user and a group at the same time. all users in the group inherit the privilege. You must be connected to the repository to use this command. you cannot use the -u option. The name of the group to which you want to add the privilege. -u -g Required Required username group_name Adding a User to a Group (Addusertogroup) The Addusertogroup commands adds an existing user to a group. If you use this option. If the privilege contains spaces.” The name of the user to whom you want to add the privilege. You must connect to the repository to use this command. To add a user to a group. If you add a privilege to a group. you must enclose this argument in quotes. You must connect to the repository to use this command. use the following syntax: addusertogroup -u username -g group_name Table 16-39 lists pmrep Addusertogroup options and arguments: Table 16-39.Adding a Privilege (Addprivilege) The Addprivilege command adds a privilege to a user or group. The name of the group to which you want to add the user.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

typename etc.) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name . The combination of specified child nodes can be supplied --> <!ELEMENT RESOLVECONFLICT (LABELOBJECT | QUERYOBJECT | TYPEOBJECT | SPECIFICOBJECT)*> <!--LABELOBJECT allows objects in the target with label name to apply replace/reuse upon conflict --> <!ELEMENT LABELOBJECT EMPTY> <!ATTLIST LABELOBJECT LABELNAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--QUERYOBJECT allows objects result from a query to apply replace/reuse upon conflict --> <!ELEMENT QUERYOBJECT EMPTY> <!ATTLIST QUERYOBJECT QUERYNAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--TYPEOBJECT allows objects of certain type to apply replace/reuse upon conflict--> <!ELEMENT TYPEOBJECT EMPTY> <!ATTLIST TYPEOBJECT OBJECTTYPENAMECDATA #REQUIRED #REQUIRED RESOLUTION(REPLACE | REUSE | RENAME) > <!--SPECIFICOBJECT allows a particular object(name.TYPENAME > 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 .

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

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

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

<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.dtd. 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 . e. This should conforming to the element name in powermart.--> <TYPEFILTER TYPENAME="SOURCE"/> <TYPEFILTER TYPENAME="TARGET"/> <TYPEFILTER TYPENAME="MAPPLET"/> <TYPEFILTER TYPENAME="MAPPING"/> <TYPEFILTER TYPENAME="TRANSFORMATION"/> <TYPEFILTER TYPENAME="SHORTCUT"/> <TYPEFILTER TYPENAME="CONFIG"/> <TYPEFILTER TYPENAME="TASK"/> <TYPEFILTER TYPENAME="SESSION"/> <TYPEFILTER TYPENAME="SCHEDULER"/> <TYPEFILTER TYPENAME="WORKFLOW"/> <TYPEFILTER TYPENAME="SCHEDULER"/> <TYPEFILTER TYPENAME="WORKLET"/> <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. TARGET and etc.g. SOURCE.

<TYPEOBJECT OBJECTTYPENAME="Expression" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Filter" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Aggregator" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Rank" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Normalizer" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Router" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Sequence" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Sorter" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="update strategy" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Custom Transformation" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Lookup Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Transaction control" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Stored Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="External Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Joiner" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="SessionConfig" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Email" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Command" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Scheduler" RESOLUTION="REUSE"/> <!--SPECIFICOBJECT allows a particular object(name. typename etc.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 .) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD 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 .

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

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

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

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

508 Appendix A: Working with pmrep Files .

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

Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources. you can edit a mapping if you have one of the following sets of privileges and permissions: ♦ ♦ Use Designer privilege with both read and write permission on the folder Super User privilege Table B-1 lists the required privileges and permissions for Designer tasks: Table B-1. and mappings Create/edit sources. 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 . Read and write permission in the destination folder. Read permission in the originating folder. Read and write permission for the destination folder. transformations. transformations. For example.Designer Tasks To perform the following Designer tasks. targets. targets. you must have one of the listed sets of privileges and permissions. 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.

Write permission and belong to the same group as the owner of the connection object. you must have one of the listed sets of privileges and permissions. you can edit a session if you have one of the following sets of permissions and privileges: ♦ ♦ Use Workflow Manager privilege with both read and write permission on the folder Super User privilege Note: In addition. 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 . if you enabled enhanced security. Table B-2 lists the required privileges and permissions for Workflow Manager tasks: Table B-2. 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. you must also have read permission for connection objects associated with the session.Workflow Manager Tasks To perform the following Workflow Manager tasks. For example.

FTP. and external loader connections in the Workflow Manager Edit database. 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. 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. Write None required None required Read Read/Write Read/Write None required None required None required None required None required None required None required 512 Appendix B: Permissions and Privileges by Task . FTP.

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

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 .

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

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

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

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

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

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. when you must provide a repository user name and password. 520 Appendix B: Permissions and Privileges by Task . However.

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

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

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

37 dependent objects exporting and importing 270 DeployDeploymentGroup description 467 DeployFolder description 469 deploying objects depcntl. 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 504 rolling back a deployment 238 deployment groups copying 254.dtd listing 504 dependencies source-target 27 viewing 27.recovering deleted objects 215 repositories 64 repositories using pmrepagent 481 user groups 129 versioned objects 215 depcntl. 276 parent objects 271 permissions 266 524 Index .

168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245.powrmart. 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 copying between local repositories 250 copying global shortcuts 250 copying local shortcuts 249 copying or replacing 250 copying shortcuts 249 creating 171 deleting 173. 192 creating 14 promoting 112. 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 . 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.dtd 267 privileges 266 sessions 272 shortcuts 270 steps for 285 versioned objects 273 external loader connections during folder or deployment group copy 245 permissions and privileges 245 external security module registering 484 unregistering 489 properties 168. 171 renaming 173 Repository Manager uses 166 shared 15.

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

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

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

432 importing 280. 433 modifying in XML file 277 validating for import 281 validating multiple 42 viewing dependencies 37 ODBC data sources See also Installation and Configuration Guide importing 33 option license keys overview 119 Oracle connect string syntax 405 Output window Repository Manager 28 Owner security level description (folder) 148 Index 529 .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.

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

75. overview 155 overview 2. 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. 160 security log file 153 security. 421 enabling 71 enabling version control 118 exporting/importing registries 32 licenses 120 limiting access 161 locks 154 log file codes 97 log files 97 managing 52 moving to a different Repository Server 77 object locking. 117. troubleshooting 163 starting 71 Index 531 . 158 removerepsitory description 435 removing repositories 29 users 141 replacing folders 248.Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126. 50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. 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. 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.

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

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

190. 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 .description 9 descriptions inherited 184 exporting 270 global 182.

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. 151 user groups creating 128 default repository privileges 143 defaults 127 deleting 129 description 126 editing 129 folder permissions 128 limiting privileges 160 overview 127 users adding to repositories 134 adding under an external directory 137 authentication 131 customizing privileges 161 default users 131 editing 138 enabling 139 LDAP authentication 131 removing 141 valid statuses with LDAP 131 V validating objects 42 validating objects with pmrep Validate 474 variables copying mapping variables 307 updating with pmrep 446 version control enabling for repositories 118 version history viewing 208 versioned objects checking in 211 checking out 211 deleting 215 exporting 273 object status 205 overview 200 purging 216 recovering a deleted object 215 sample scenario 201 tracking changes 208 viewing applied labels 205 viewing history 208 viewing object properties 203 viewing properties 203 viewing version properties 204 versioning object permissions description 126 versioning objects configuring permissions 149 definition 218 deployment groups 236 labels 219 object queries 224 Index 535 .

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