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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

Use notification messages tell users to disconnect if you want to shut down 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. or to users connected to all of the repositories managed by a Repository Server. 8 Chapter 1: Understanding the Repository . see “Sending Repository Notifications” on page 74.

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

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

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

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

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

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. Progress Indicator 22 Chapter 2: Using the Repository Manager . The Repository Manager can display the following windows: ♦ ♦ ♦ ♦ Navigator Main Dependency Output Figure 2-1 shows the Repository Manager components: Figure 2-1. the Status Bar reflects the connection in progress with a progress indicator.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

88

Chapter 3: Managing the Repository

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

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

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

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

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

Registering and Unregistering LDAP Security Modules

89

The Repository Server lists the available plug-ins.

4.

Select the Authentication Module, and choose Action-Register.

90

Chapter 3: Managing the Repository

The Register Security Module dialog box displays.

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

5.

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

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

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

3.

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

4.

Enter LDAP server options.

92

Chapter 3: Managing the Repository

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

Principal User Name Principal User Password 5.

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

Registering and Unregistering LDAP Security Modules

93

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

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

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

94

Chapter 3: Managing the Repository

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

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

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

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

3.

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

Registering and Unregistering LDAP Security Modules

95

The Unregister Package dialog box displays.

4.

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

96

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

♦ ♦

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

98

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

To check the spelling. The Add Users dialog box displays a list of names from the external directory service. In the Repository Manager. you add repository users from a list of login names from the external directory. To add users with an external directory service: 1. click Check Names. 3. but it must match a valid login name in the directory. Click Add. The login name displays at the bottom of the screen. If you select more than one name. 4. 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. 2. Note: You can type a name at the bottom of the screen. connect to a repository. the names display at the bottom separated by semi-colons. Select a login name from the external directory list and click Add. Creating and Editing Repository Users 137 . Choose Security-Manage Users and Privileges.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

♦ ♦

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

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

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

224

Chapter 9: Grouping Versioned Objects

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

Specify query conditions.

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

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

Working with Object Queries

225

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

Add logical operators. Add multiple query conditions.

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

4

3

226

Chapter 9: Grouping Versioned Objects

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

Check-in time

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

Date/time Numeric

Comments

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

String

Deployment Dispatch History

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

Date/time Numeric

Deployment Receive History

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

Date/time Numeric

Working with Object Queries

227

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

Include Children

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

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

Include Children and Parents

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

Where (Value 1) depends on (Value 2)

Include Parents

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

Where (Value 1) depends on (Value 2)

Include Primary/ Foreign Key Dependencies

Displays primary key-foreign key dependencies.

N/A

228

Chapter 9: Grouping Versioned Objects

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

Last Saved Time

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

Latest Status

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

Checked-out Latest checked-in Older

Metadata Extension

Is Equal To Is Not Equal To

User-defined metadata domain Any vendor-defined metadata extensions

Object Name

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

String

Working with Object Queries

229

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

Object Used Status

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

Is Equal To

Shortcut status

Is Equal To

Is Not Shortcut Is Shortcut

Reusable Status User

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

Non-reusable Reusable Users in specified repository

Valid Status Version Status

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

Invalid Valid Deleted Not deleted

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

230

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

Working with Object Queries

231

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

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

232

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

objects in the repository.

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

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

Working with Object Queries

233

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

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

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

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

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

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

234

Chapter 9: Grouping Versioned Objects

Select source definitions and target definitions for Value 1 and select mapping for Value 2. To search for parent and child dependencies.Finding Object Dependencies The following query returns sources and targets in the Vendors folder that are dependent on the mapping. Mapping_deploy. 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 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

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

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

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

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

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

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

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

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

For more information on comparing sources or targets.10. 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 . Click Next to proceed through the Conflict Resolution Wizard. see “Comparing Objects” in the Designer Guide. The Metadata Import Wizard imports all objects. 12. 11. Resolve object conflicts as they appear in the Conflict Resolution Wizard.

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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. reusable metadata extensions for repository objects using the Repository Manager. edit the repository object using the Designer or Workflow Manager. and then click Edit. you change the properties of the metadata extension. To change the value of a metadata extension. When you edit a reusable metadata extension. Note: You cannot edit vendor-defined metadata extensions.Editing Reusable Metadata Extensions You can edit user-defined. To edit a reusable metadata extension.

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

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

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

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

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

Table 15-3. SQL Script to Drop MX Views Repository Database Sybase Teradata SQL Script sybmxdrp. Software vendors can integrate Informatica metadata with their products through different methods.sq_ termxdrp. Viewing the Repository Metadata 337 . The next generation of MX. provides an object-based Application Programming Interface (API) to read and write metadata in Informatica repositories. 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. vendors of popular query and reporting tools can quickly create a metadata link between their products and the PowerCenter repository. called Metadata Exchange SDK. Integrating MX Views with Third-Party Software With MX software and support from Informatica.

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

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

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

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

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

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

344 Chapter 15: Using Metadata Exchange (MX) Views . Folder ID. Source version number. Source description. Folder name. Business name of the table. 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. Informatica recommends using the fields in bold to join views. Type of database extracted from. Unique key. Informatica recommends using the fields in bold to join views. Table 15-9 lists relational database table information in the REP_SRC_TBLS view: Table 15-9. Last time the source table was saved. 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. Link to first field. Version ID. Name of schema extracted from. Source version number. Source description.Table 15-8. Name of database extracted from. Folder version ID. REP_SRC_TBLS This view provides a list of relational database table sources that have been analyzed through the Source Analyzer tool or imported from a DDL (Data Definition Language) file. Folder version name.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

you must call the Connect command. but not both. See “Connecting to a Repository (Connect)” on page 410. “Exiting pmrep (Exit)” on page 411. The port number the Repository Server uses for connections. pmrep System Commands pmrep Command Connect Help Cleanup Exit Command Description Connects to the repository. The host name of the machine running the Repository Server. All commands require a connection to the repository. Connect uses the following command syntax: connect -r repository_name -n repository_username -x repository_password -X repository_password_environment_variable -h repserver_host_name -o repserver_port_number Table 16-3 lists pmrep Connect options and arguments: Table 16-3. See “Cleaning up Persistent Resources (Cleanup)” on page 411. Use the -x or -X option. See “Getting Help (Help)” on page 411. Password for the repository user name. Connecting to a Repository (Connect) The first time you use pmrep in either command line or interactive mode. Table 16-2 lists pmrep system commands: Table 16-2. 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. Cleans up persistent resources created by pmrep during a session. Repository user name used to connect to the repository. 410 Chapter 16: Using pmrep and pmrepagent . but not both. The password environment variable for the repository. Exits from pmrep. 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. Use the -x or -X option.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You can update any of the PowerCenter Server variables using Updatesrvvar. you must enter the dbd name and the source table name as dbd_name. pmrep matches the source_name argument with source instance names.session_name or workflow_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.source_name. enter the name of the source instance as displayed in the session properties or as output by the Listtablesbysess command. Informatica recommends you include the -n option. If you omit this option. specify session_name.session_name. For reusable sessions.When you omit the -n option. For a list of server variables. . see “Configuring the Workflow Manager” in the Workflow Administration Guide. 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. When you include this option. You cannot change default server variables. but you can change the case of the default server variables. pmrep matches the source_name argument with the source table names. The owner name you want to update in the source table. pmrep updates all source table owner names in the session. This command requires you to connect to a repository. 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 . Updatesrcprefix Options and Arguments (pmrep) Option -f -s Required/ Optional Required Required Argument Name folder_name session_name Argument Description The name of the folder containing the session. You can find the source dbd name in the Designer Navigator. The name of the session containing the sources to update. This option has no argument. such as worklet_name. When you do not include this option. The name of the source to update. you must also specify the session path.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Include this option if you want to enables object versioning for the repository.Table 16-70. This option has no argument. Use the -x or -X option. For more information about deleting a repository. The port number of the Repository Server that manages the repository. see “Deleting a Repository” on page 64. 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. Deleting a Repository (Delete) The pmrepagent Delete command deletes the repository tables from the repository database. but not both. The repository user name. Delete Options and Arguments (pmrepagent) Option -r -n -x -X Required/ Optional Required Required Required/ Optional Required/ Optional Argument Name repository_name repository_user_name repository_password repository_password_envir onment_variable Argument Description The name of the repository you want to delete. The repository password. pmrepagent interprets the spaces as part of the tablespace name. Use this option to specify the tablespace name for IBM DB2 EEE databases. The repository password environment variable. Use the -x or -X option. pmrepagent Commands 481 . Include this option if you want to promote the repository to a global repository. -a -v Required Optional license_file_name n/a The name of the license file. The host name 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. but not both. This option has no argument. 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.

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

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

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

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

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

Example The following example restores a repository to a Solaris machine and specifies the administrator user name and password in order to keep the LDAP security module registration. For more information on unregistering plug-ins. The Repository Agent verifies that this password is valid for the user name on the target server. Use this option with the -v option when you want to retain the external security module after restoring. For more information. Skips tables related to MX data during backup. Use this option only when unregistering an external module. Removes user name-login mapping. Skips tables related to workflow and session logs during backup. -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.Table 16-73. The name of the license file. Restore Options and Arguments (pmrepagent) Option -X Required/ Optional Required/ Optional Argument Name verify_password_environment_ variable Argument Description The verify password environment variable. Skips deployment group history during backup. Unregisterplugin uses the following command syntax: Unregisterplugin -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable-m -c database_connect_string -v vendor_id -l plugin_id -g remove_user_name_login_mapping -w new_password -W new_password_environment_variable pmrepagent Commands 487 . but not both. see “Unregistering a Repository Plug-in” on page 86. see “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. Use this option only with a repository using an external security module.rep Unregistering Plug-ins (Unregisterplugin) The pmrepagent Unregisterplugin command removes a plug-in from a repository. Use the -x or -X option. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

508 Appendix A: Working with pmrep Files .

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

and mappings Create shortcuts from a shared folder Repository Privilege Use Designer Use Designer Use Designer Use Designer Folder Permission None required Read Read/Write Read permission in the shared folder. and mappings Create/edit sources. For example. targets. Read permission in the originating folder. Read and write permission for the destination folder. transformations. Read and write permission in the destination folder. targets. 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 . Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources.Designer Tasks To perform the following Designer tasks. you must have one of the listed sets of privileges and permissions. 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.Workflow Manager Tasks To perform the following Workflow Manager tasks. For example. Table B-2 lists the required privileges and permissions for Workflow Manager tasks: Table B-2. Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Administer Repository Use Workflow Manager Use Workflow Manager Connection Object Permission None required None required None required Read Write Write permission and own the connection object. you can edit a session if you have one of the following sets of permissions and privileges: ♦ ♦ Use Workflow Manager privilege with both read and write permission on the folder Super User privilege Note: In addition. you must 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 . Write permission and belong to the same group as the owner of the connection object. if you enabled enhanced security.

FTP.Table B-2. 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. FTP. Write None required None required Read Read/Write Read/Write None required None required None required None required None required None required None required 512 Appendix B: Permissions and Privileges by Task . Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager and Administer Server Use Workflow Manager Use Workflow Manager Administer Repository Administer Server Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Connection Object Permission None required Workflow Manager Task Stop the PowerCenter Server Folder Permission None required Configure database. and external loader connections in the Workflow Manager Edit database.

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

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

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

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. 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 . For example.Repository Manager Tasks To perform the following Repository Manager tasks.

groups.Table B-5. Folder owner and read permission Read Folder owner and read permission Read Read Folder owner and read permission Read Read/Write None required None required Write Write None required Write N/A N/A Other Permission None required Edit: Write on deployment group Edit: Write on label Write on query None required None required None required Write on deployment group Read and execute on deployment group None required None required None required None required None required None required None required None required None required None required None required None required None required None required None required Read on query Repository Manager Tasks 517 . and privileges Mass update Purge (versioning) Receive user and group notifications Recover Remove Label References Run Query Use Repository Manager Browse Repository Administer Repository Super User Administer Repository Super User Use Repository Manager Use Repository Manager Browse Repository Manager Folder Permission None required N/A N/A N/A Write Folder owner and read permission Read N/A Read on the original folder. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Create a folder Create or edit deployment group Create or edit label Create or edit query Delete (versioning) Delete a folder Repository Privilege Administer Repository Administer Repository Administer Repository Browse Repository Use Repository Manager Browse Repository Administer Repository Delete from Deployment Group Deploy Edit folder Use Repository Manager Administer Repository Browse Repository Administer Repository Edit folder properties Browse Repository Administer Repository Export objects Freeze folder Use Repository Manager Browse Repository Administer Repository Import objects Import. or remove the registry Manage users. 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. you must have one of the listed sets of privileges and permissions.pmrep Tasks To perform the following pmrep tasks.

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

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

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. 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. 31 connection objects See also Workflow Administration Guide definition 10 permissions and privileges 245 connections terminating 83 viewing 79 connectivity connect string examples 405 connectivity license keys overview 119 ConnectString setting for repository configuration 107 Console Tree Administration Console 52 control file deployment 504 object import 496 ObjectImport XML example 500 Copy Wizard copying objects 302 resolving conflicts 300 viewing object dependencies 305 .

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

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

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

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

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

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

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.

75. 158 removerepsitory description 435 removing repositories 29 users 141 replacing folders 248. 192 connecting to 30 connecting to multiple 31 connecting with pmrep 410 connectivity 4 copying 62 copying folders between local 250 creating 116 creating relational connections 417 creating users 134 database definition views 338 default privileges 143 deleting 64 disabling 73. overview 155 overview 2. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126. 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. 160 security log file 153 security. troubleshooting 163 starting 71 Index 531 . 117.Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. 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. 50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29.

stopping 71 stopping with pmrep 437 types of 50 unregistering 440 version control 16 view of associated target tables 350 view of target table properties 351 viewing details 26 viewing locks 157 viewing metadata 334 repository deleting details from 439 enabling 422 Repository Agent architecture 3 checking status 54 connectivity 4 disabling 73 enabling 71 identifying process ID 97 log file codes 97 logging 100 starting 71 stopping 71 repository configuration CheckinCommentsRequired 110 creating 104 dynamically updating 113 editing 113 exporting 115 importing 115 removing 114 setting CodePage 107 setting ConnectString 107 setting DatabaseArrayOperationSize 110 setting DatabaseConnectionTimeout 110 setting DatabasePoolSize 110 setting DatabaseType 107 setting DateDisplayFormat 109 setting DBPassword 107 setting DBUser 107 setting DynamicConfigRefreshInterval 110 setting Error Severity Level 109 setting KeepAliveTimeout 110 setting LogFileName 110 setting MaximumConnections 109 setting MaximumLocks 110 setting MessageReceiveTimeOut 108 setting MessageSendTimeOut 108 setting SecurityAuditTrail 110 setting TablespaceName 107 setting ThreadWaitTimeout 110 repository connections terminating 83. 152 viewing 79. 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.

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

description 9 descriptions inherited 184 exporting 270 global 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 . 190. 187 overview 182 properties 184 referenced objects 183. 192 importing 274 local 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 . 152 viewing 79.U UndoCheckout description 473 unregister description 440 unregistering plug-ins using pmrepagent 487 security module using pmrepagent 489 Unregisterplugin description 487 UpdateConnection description 441 Updateemailaddr description 442 Updateseqgenvals description 444 Updateserver description 443 Updatesrcprefix description 445 updating non-reusable sessions 446 Updatesrvvar description 446 Updatestatistics description 447 Updatetargetprefix description 447 updating non-reusable sessions 448 updating repository license files 111 shortcuts 194 Upgrade description 490 upgrading repositories using pmrepagent 490 user connections description 126 terminating 83.

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