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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

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

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

and then clicking the View Properties button in the toolbar. 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-2 shows the Navigator components: Figure 2-2. 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 view all tabs on the Properties dialog box. 24 Chapter 2: Using the Repository Manager . see “Viewing Version Properties” on page 203. For more information about object properties.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2. You must delete the existing repository in the target database before creating the new repository. For more information. the global and local repository code pages must be compatible. see “Globalization Overview” in the Installation and Configuration Guide. Tip: To change the repository code page after you create the repository. License keys. The repository code page must be compatible with the PowerCenter Server and Client code pages. once you create a global repository. you must create at least one folder before you can create objects in the Designer or Workflow Manager. ♦ Note: You can create a repository after you add a repository configuration. In the Console Tree. When registering local repositories with a global repository. select the repository you want to promote. For more information on licenses. In the Console Tree. Contains the character set of the data in the repository. make sure the repository code page is compatible with each local repository you want to register. see “Adding a Repository Configuration” on page 105. To create a repository: 1. To promote a repository: 1. Note: If a repository already exists in the database. Promoting a PowerCenter Repository After you create a local repository. it starts the Repository Agent.♦ Code page. For more information. you cannot change the code page. Once specified. you cannot change it to a local repository. When you restore a repository. You can see the progress in the Activity Log. see “Creating a Folder” on page 171. Choose Action-Create. the Repository Server does not create the repository. see “PowerCenter Domains” on page 13. Verify the repository license file contains a valid product license key and any connectivity and option license key. Before promoting a repository to a global repository. see “Working with PowerCenter Licenses” on page 119. When the Repository Server finishes creating the repository. For details on global and local repositories. 2. After creating a repository. Creating or Promoting a Repository 117 . you can specify a compatible code page. select a repository configuration under the Repositories node. you can promote it to a global repository. you can back up and restore it. Choose Action-Properties. However. For details. The Repository Server begins building the repository. You must start the repository before you can promote it to a global repository. 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 enable version control. you can enable it for version control. control development on the object. Once you enable version control for a repository. 3. queries. The Repository Server promotes the repository to a global repository. Version control allows you to maintain multiple versions of an object. For more information on using labels. select the Supports Version Control option. and track changes. The Administrator Console displays the Login Information dialog box. see “Grouping Versioned Objects” on page 217. see “Working with Versioned Objects” on page 199. When you enable version control for a repository. 4. The Repository Server enables version control for the repository and stops and restarts the repository for the changes to take effect. In the Properties dialog box. and click OK. In the Properties dialog box. you cannot disable it. The Administrator Console displays the Login Information dialog box. 2. the repository assigns all versioned objects version number 1 and each object has an active status. select the repository for which you want to enable version control. and deployment groups. Note: To enable a repository for version control. you must have the Team-Based Development option license key in the repository license file. and deployment groups to associate and copy specific groups of objects from one repository to another. queries. select the Global Data Repository option. For more information on working with versioned objects and versioned object properties. Enter your repository user name and password. Enabling Version Control After you create a repository.3. To enable version control for a repository: 1. In the Console Tree. Choose Action-Properties. 118 Chapter 4: Configuring the Repository . Enter your repository user name and password and click OK. 4. You can also use labels.

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

For information on tasks you can perform with user privileges. folder permissions. Change owner. Click to define permissions. Add a new group or user. Change group. 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. see “Repository Privileges” on page 142. The Permissions dialog box displays. To configure permissions for versioning objects. and versioning object permissions. 150 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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

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

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

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

4.

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

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

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

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

6.

Choose Repository-Save.

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

Creating a Local Shortcut

189

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

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

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

190

Chapter 7: Local and Global Shortcuts

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

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

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

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

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

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

2.

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

3. 4.

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

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

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

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

6.

Choose Repository-Save.

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

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

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

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

3.

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

4. 5.

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

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

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

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

7.

Choose Repository-Save.

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

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

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

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

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

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

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

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

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

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

Creating a Global Shortcut

193

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

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

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

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

194

Chapter 7: Local and Global Shortcuts

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

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

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

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

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

Working with Shortcuts

195

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

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

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

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

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

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

Tips

197

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

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

♦ ♦ ♦

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

198

Chapter 7: Local and Global Shortcuts

Chapter 8

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

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

199

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

♦ ♦

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

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

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

224

Chapter 9: Grouping Versioned Objects

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

Specify query conditions.

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

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

Working with Object Queries

225

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

Add logical operators. Add multiple query conditions.

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

4

3

226

Chapter 9: Grouping Versioned Objects

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

Check-in time

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

Date/time Numeric

Comments

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

String

Deployment Dispatch History

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

Date/time Numeric

Deployment Receive History

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

Date/time Numeric

Working with Object Queries

227

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

Include Children

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

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

Include Children and Parents

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

Where (Value 1) depends on (Value 2)

Include Parents

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

Where (Value 1) depends on (Value 2)

Include Primary/ Foreign Key Dependencies

Displays primary key-foreign key dependencies.

N/A

228

Chapter 9: Grouping Versioned Objects

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

Last Saved Time

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

Latest Status

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

Checked-out Latest checked-in Older

Metadata Extension

Is Equal To Is Not Equal To

User-defined metadata domain Any vendor-defined metadata extensions

Object Name

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

String

Working with Object Queries

229

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

Object Used Status

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

Is Equal To

Shortcut status

Is Equal To

Is Not Shortcut Is Shortcut

Reusable Status User

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

Non-reusable Reusable Users in specified repository

Valid Status Version Status

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

Invalid Valid Deleted Not deleted

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

230

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

Working with Object Queries

231

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

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

232

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

objects in the repository.

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

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

Working with Object Queries

233

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

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

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

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

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

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

234

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

To apply the resolution to more objects. Figure 12-2. 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. Resolving Copy Conflicts 301 . or to all conflicts in your copy. The selected resolution reuses the object. click Apply This Resolution To and choose either All Conflicts or conflicts for just the specified object type. Optionally.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.

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

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

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

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

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

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

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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. select the appropriate extension in the Metadata Extensions dialog box. reusable metadata extensions for repository objects using the Repository Manager. To delete a reusable metadata extension. Note: You cannot delete vendor-defined metadata extensions. 332 Chapter 14: Metadata Extensions .Deleting Reusable Metadata Extensions You can delete user-defined. and click Delete.

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

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

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

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

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

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

creation date. 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_TBLS” on page 344. You can use the source name to retrieve all the fields belonging to the source. see “REP_SRC_TBL_FLDS” on page 346. For more information. see “REP_ALL_SOURCES” on page 339. For more information. Folder ID. 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. and business name. This view provides access to the fields in relational sources. Name of the parent source Business name of the parent source. source metadata extensions. version. 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. These views provide access to the fields in a non-relational source. Source Views 339 . column properties.Source Views Source views provide a list of the latest version of all source definitions defined by folder of any PowerCenter repository. This view provides a list of all file definitions in the repository. For more information. see “REP_ALL_SOURCE_FLDS” on page 341. see “REP_SRC_FILE_FLDS and REP_SEG_FLDS” on page 345. see “REP_SRC_FILES” on page 343. For more information. description. Sources include both relational sources and non-relational sources such as XML files and flat files. For more information. They also provide information such as source columns. This view provides all the fields and field properties for all sources defined in REP_ALL_SOURCES MX View. and mappings and mapplets where these sources are used. 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. For more information. This view provides a list of relational database table sources that have been analyzed through the Source Analyzer tool or imported from a DDL (Data Definition Language) file. These views also show source properties such as shortcuts. Source definitions can be defined for both relational and nonrelational sources.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

368 Chapter 15: Using Metadata Exchange (MX) Views . Informatica recommends using the fields in bold to join views. Version number of the transformation.REP_WIDGET_INST This view displays the details of all transformation instances. Informatica recommends using the fields in bold to join views. 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. Name of the transformation instance. Target field ID. Transformation type. REP_WIDGET_DEP This view displays the details of dependencies between transformation instances in a mapping. Table 15-34 list transformation metadata in the REP_WIDGET_INST view: Table 15-34. 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. Description of the transformation instance. Description of the transformation instance. Field ID of the source transformation instance. ID of the transformation instance. Version number of the mapping. Table 15-35 lists transformation dependency information in the REP_WIDGET_DEP view: Table 15-35. Field ID of the target transformation instance. Name of the transformation instance. Transformation name.

REP_WIDGET_FIELD This view displays field level details for transformations. Transformation Views 369 . Transformation field ID. mapping. Informatica recommends using the fields in bold to join views. Table 15-36. Table 15-37 lists transformation field information in the REP_WIDGET_FIELD view: Table 15-37. instances. Partition ID. Object type ID.REP_WIDGET_ATTR This view displays attribute details for transformations. 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. Mapping ID. Attribute ID. Table 15-36 lists attribute details for transformations. Attribute type. Transformation type. and sessions. Transformation field precision. or transformation) version number. Attribute data type Attribute name. Object (session. Session task ID. Transformation field name. Used to break up long strings into multiple rows. and sessions. Attribute value. instances. Description of the attribute. 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. Datatype group code. Transformation datatype of the port. 370 Chapter 15: Using Metadata Exchange (MX) Views . Transformation field data type. External database type. Datatype number. The ID of the corresponding instance in the mapplet's mapping.Table 15-37. Expression 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. Transformation order. Transformation port type. Field-level property used by transformations. Default value of the transformation field. Transformation version number. Comments on the expression. Source field ID for normalizer transformation. Expression name.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Time when label was applied to the object. 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 . Label description.Table 15-75.

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

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

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

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

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

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

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

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

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

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

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

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

412

Chapter 16: Using pmrep and pmrepagent

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

StopRepository SwitchConnection Truncatelog Unregister UpdateConnection Updateemailaddr Updateseqgenvals

Updateserver Updatesrcprefix Updatesrvvar UpdateStatistics Updatetargprefix

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

pmrep Repository Commands

413

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

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

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

414

Chapter 16: Using pmrep and pmrepagent

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

-A

repserver_password_ environment_variable repository_name database_type database_user_name

-r -t -u

-m -p

Optional Required/ Optional

n/a database_password

-P

Required/ Optional

database_password_ environment_variable

-c

Required

database_connect_string

-d

Optional

code_page

pmrep Repository Commands

415

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

-l

Optional

license_file_name

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

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

-b -j -q

Optional Optional Optional

skip_workflow/ session_logs skip_deploy_group _history skip_MX_data

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

416

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

-P

password_environm ent_variable connect_string

-c

-l -r

Required Optional

code_page rollback_segment

pmrep Repository Commands

417

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

-b -v -d -t

Optional Optional Optional Optional

database_name server_name domain_name trusted_connection

-x

Optional

n/a

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

418

Chapter 16: Using pmrep and pmrepagent

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

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

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

pmrep Repository Commands

419

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

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

420

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

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

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

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

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

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

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

-r

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

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

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

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

422

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

For more information on using a persistent input file. To apply a label to selected dependent objects. AddToDeploymentGroup Options and Arguments (pmrep) Option -v Required/ Optional Optional Argument Name version_number Argument Description The version of the object to add. The dependent objects to add to the deployment group with the object. or ListObjectDependencies that contains a list of object records with encoded IDs. If you omit this parameter. then you do not add dependent objects to the deployment group. The folder that contains the object you are adding. If you want to label non-reusable input objects. If you specify a folder. If you use the dependent_object_type option. -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. If you use this parameter. pmrep labels all dependent objects. If ApplyLabel succeeds. and -f options. A text file generated from ExecuteQuery. reusable and non-reusable. Use ApplyLabel to label reusable input objects. pmrep displays either no status information or a list of objects that already have the label. pmrep adds the object(s) and all dependent objects. you must use a persistent input file that contains encoded object IDs. The default is to add the latest version of the object to the deployment group. see “Using the Persistent Input File” on page 494. all the objects in the folder receive the label.” If you specify “non-reusable” pmrep adds the object(s) and the corresponding non-reusable dependent objects to the deployment group. To label objects. You must specify the folder if you specify an object name. see “Using the Persistent Input File” on page 494. If the command fails. see “Applying Labels” on page 221. separate each object type name by a comma with no spaces between them on the command line. For more information about using a persistent input file. For more information on applying labels.Table 16-53. pmrep does not allow the -n. You can apply the label to dependent objects. pmrep displays the failure reason. to the deployment group. Validate. -o. You can specify “non-reusable” or “all. If you specify “all”. 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 type of object to apply the label to. task. The dependent parents or children to apply the label to. or Validate. or folder name to specify objects. mapping. Required when applying a label to a specific object. ListObjectDependency. transformation. If you use this option. The name of the object to receive the label. For more information on using the persistent input file. Use this option with option -p. You can specify parents. You can specify source. The version of the object to apply the label to. target. both. The dependent objects to label. scheduler. all dependent objects receive the label. If you do not specify option -d. pmrep searches the folder for the object. session config. worklet. then the label applies to dependent objects of that object type. see “Using the Persistent Input File” on page 494. workflow.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. see Table 16-16 on page 426. If you specify a folder with an object name. The folder that contains the object(s). or dimension. The command fails if the version is checked out. but no object name. Contains a list of objects to receive the label. -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 . session. pmrep ignores other object types. then do not use the object name. For valid subtypes. The name of a text file generated from ExecuteQuery. If you do not specify this option. pmrep applies the label to all objects in the folder. If you specify a folder. object type. cube. Applies the label to the latest version of the object by default. children. the label applies only to the specified object. You cannot specify a folder if you use the -i option. The kind of task or transformation you are labeling. ApplyLabel Options and Arguments (pmrep) Option -a -n Required/ Optional Required Required/ Optional Argument Name label_name object_name Argument Description The label name to apply to the object. If you specify an object type. then this parameter is required. If you are updating a specific object. You cannot specify objects if you use the -i option.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

SOURCE.dtd file: <!-.--> <!ELEMENT TYPEFILTER EMPTY> <!ATTLIST TYPEFILTER 496 Appendix A: Working with pmrep Files . The following is a sample of the impcntl. TARGET and etc.Informatica Object Import Control DTD Grammar .dtd. but you must include its location in the input XML file. This should comforming to the element name in powermart.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. TYPEFILTER*. you must create an XML file defined by impcntl. you can supply a control file to answer questions that you normally address when you import objects with the Import Wizard. The import control file installs with the PowerCenter Client. e.1 --> <!--IMPORTPARAMS This inputs the options and inputs required for import operation --> <!--CHECKIN_AFTER_IMPORT Check in objects on successful import operation --> <!--CHECKIN_COMMENTS Check in comments --> <!--APPLY_LABEL_NAME Apply the given label name on imported objects --> <!--RETAIN_GENERATED_VALUE Retain existing sequence generator.g.dtd.Version 7.

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

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

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

0" encoding="UTF-8"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. including specifying a resolution for query results. You have a query called “yr_end_qry” that finds these objects.0" encoding="ISO-8859-1"?> <!DOCTYPE IMPORTPARAMS SYSTEM "impcntl. you want to replace all the duplicate objects labeled “Monthend. In the target folder.dtd"> <IMPORTPARAMS CHECKIN_AFTER_IMPORT ="NO"> <FOLDERMAP SOURCEFOLDERNAME ="OLD_ACCOUNTING" SOURCEREPOSITORYNAME ="OLD_REPOS" TARGETFOLDERNAME ="NEW_ACCOUNTING" TARGETREPOSITORYNAME ="NEW_REPOS"/> <TYPEFILTER TYPENAME ="SOURCE"/> <RESOLVECONFLICT> <LABELOBJECT LABELNAME ="Monthend" RESOLUTION = "REPLACE"/> <QUERYOBJECT QUERYNAME ="yr_end_qry" RESOLUTION ="RENAME"/> </RESOLVECONFLICT> </IMPORTPARAMS> Sample Import XML File The following is a sample XML control file for ObjectImport. It specifies to check in the imported objects and label them. specifying resolutions for object types. and specifying resolutions for specific objects. <?xml version="1.” However. The file specifies the target folder and repository. You might create a control file with the following attributes: <?xml version="1.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. you want to rename conflicting source objects that contain “Yr_End” in the object name.Example Suppose you want to import only source objects.

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

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

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

The following is a sample of the depcntl. To use pmrep deployment commands you must create an XML file that works with depcntl. DEPLOYGROUP?)> <!ATTLIST DEPLOYPARAMS DEFAULTSERVERNAME COPYPROGRAMINFO COPYMAPVARPERVALS COPYWFLOWVARPERVALS COPYWFLOWSESSLOGS COPYDEPENDENCY LATESTVERSIONONLY RETAINGENERATEDVAL RETAINSERVERNETVALS CDATA #IMPLIED (YES | NO) "YES" (YES | NO) "NO" (YES | NO) "NO" (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "YES"> <!--criteria specific to deploying folders--> <!ELEMENT DEPLOYFOLDER (REPLACEFOLDER?. The deployment control file installs with the PowerCenter Client. you can use a control file to answer questions that you see when you deploy objects using the Copy Wizard.dtd. but you should include its location in the input XML file. <!ELEMENT DEPLOYPARAMS (DEPLOYFOLDER?.Using the Deployment Control File When you use DeployDeploymentGroup or DeployFolder pmrep commands.dtd 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 .

Indicates local or global folder. Copies workflow logs. Retains workflow session logs in the target. APPLYLABEL?)> <!ATTLIST DEPLOYGROUP CLEARSRCDEPLOYGROUP (YES | NO) "NO"> <!--labels used to apply on the src objects and deployed objects--> <!ELEMENT APPLYLABEL EMPTY> <!ATTLIST APPLYLABEL SOURCELABELNAME SOURCEMOVELABEL TARGETLABELNAME TARGETMOVELABEL CDATA (YES | NO) CDATA YES | NO) #IMPLIED "NO" #IMPLIED "NO"> Deployment Control File Parameters Table A-2 lists pmrep deployment control file parameters: Table A-2. Copies only the latest version.<!--criteria for clearing a source group in DeployDeploymentGroup--> <!ELEMENT DEPLOYGROUP (OVERRIDEFOLDER*. Does not allow replacing of manually modified target folders. Name the folder after replacing it. Retains workflow variable persistent values. 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. Specifies the current folder that shortcuts point to. Retains mapping variable persistent values in the target. Copies SAP R/3 installed ABAP program. Copies workflow variable persistent values. Keeps the current value for Sequence Generator or Normalizer transformations. Creates a new folder with this name. Copies dependency information for objects in mappings. Retains server network related values in tasks. Copies mapping variable persistent values. Using the Deployment Control File 505 .

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

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

508 Appendix A: Working with pmrep Files .

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

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

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

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

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

Required Privileges and Permissions for Workflow Monitor Tasks Workflow Monitor Task 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 .Table B-3.

you must have execute permission for connection objects associated with the session in addition to the privileges and permissions listed above. For example. 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. Table B-4 lists the required privileges and permissions for pmcmd tasks: Table B-4.pmcmd Tasks To perform the following pmcmd tasks. you must have one of the listed sets of privileges and permissions.

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

Table B-5. 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. Folder owner and read permission Read Folder owner and read permission Read Read Folder owner and read permission Read Read/Write None required None required Write Write None required Write N/A N/A Other Permission None required Edit: Write on deployment group Edit: Write on label Write on query None required None required None required Write on deployment group Read and execute on deployment group None required None required None required None required None required None required None required None required None required None required None required None required None required None required None required Read on query Repository Manager Tasks 517 . or remove the registry Manage users. groups. 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. export.

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

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 can list objects in a repository if you have one of the following permissions or privileges: ♦ ♦ Browse Repository privilege with read permission on the folder Super User privilege Table B-6 lists the required permissions and privileges for pmrep tasks: Table B-6.pmrep Tasks To perform the following pmrep tasks. you must have one of the listed sets of privileges and permissions.

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

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

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

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

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

168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245. 171 renaming 173 Repository Manager uses 166 shared 15. 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. 453 deploying 469 Designer uses 166 editing 173 editing permissions 149 locking during folder copy 249 maintaining connections during copy 245 modifying 456 naming copies 249 organizing 166 overview 166 owner and owner’s group 169 H HTML view Administration Console 53 I IBM DB2 connect string example 405 setting tablespace name 107 Import Wizard importing objects 287 resolving object conflicts 281 Index 525 . 169 shortcuts 249 Workflow Manager uses 166 FTP connections during folder or deployment group copy 245 permissions and privileges 245 G global objects See Workflow Administration Guide global repositories code page 117.powrmart. 192 creating 14 promoting 112. 249 copying between local repositories 250 copying global shortcuts 250 copying local shortcuts 249 copying or replacing 250 copying shortcuts 249 creating 171 deleting 173.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. 117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182.

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

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

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

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

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

Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. 50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. 117. 75. 160 security log file 153 security. 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. 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. overview 155 overview 2. 158 removerepsitory description 435 removing repositories 29 users 141 replacing folders 248. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126. troubleshooting 163 starting 71 Index 531 . 421 enabling 71 enabling version control 118 exporting/importing registries 32 licenses 120 limiting access 161 locks 154 log file codes 97 log files 97 managing 52 moving to a different Repository Server 77 object locking. overview 142 troubleshooting 163 Workflow Manager tasks 511 product license keys overview 119 promoting repositories 117 purging description 216 objects 216 Q queries See also object queries executing 470 R recovering deleted objects 215 register description 434 registering a user 457 plug-in using pmrepagent 482 security module using pmrepagent 484 Registerplugin description 482 Registeruser description 457 registry exporting 32 importing 32 releasing repository locks 83.

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

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

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

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

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