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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

the Status Bar reflects the connection in progress with a progress indicator. The Repository Manager can display the following windows: ♦ ♦ ♦ ♦ Navigator Main Dependency Output Figure 2-1 shows the Repository Manager components: Figure 2-1. Repository Manager Components Navigator Window Dependency Window Output Window Status Bar Main Window When the Repository Manager accesses the repository.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 .

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

and then clicking the View Properties button in the toolbar. Note: If you enable versioning when you create the repository.Figure 2-2 shows the Navigator components: Figure 2-2. see “Viewing Version Properties” on page 203. You can also right-click the object in the Navigator and select Properties from the shortcut menu. 24 Chapter 2: Using the Repository Manager . you can view all tabs on the Properties dialog box. For more information about object properties. Repository Manager Navigator Repositories Deployment Groups Shared Folder Mappings Nodes Workflows Viewing Properties You can view the properties of the objects in the Navigator by selecting the object.

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

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

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

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

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

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

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

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

choose Tools-Import Registry. In the Repository Manager. Working with Repository Connections 33 . 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. A dialog box appears.You can now distribute this file for import on other client machines with the same operating systems. To import the registry: 1. 3. 2. Click Open.

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

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

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

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

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

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

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

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

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

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

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

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

Choose Edit-Compare Objects. A dialog box similar to the following one appears: 4. 46 Chapter 2: Using the Repository Manager .3. the Sources window shows the result of comparing two sources: View object differences. such as a source. Click Compare. If you choose a Designer 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. Comparing Repository Objects 47 . such as a session. Displays the properties of the node you select.If you choose a Workflow Manager object. Differences between objects are highlighted and the nodes are flagged. Compare object instances.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

and enter your repository user name and password. 76 Chapter 3: Managing the Repository . 4. Click Register. the host name of the Repository Server. choose Managed By the Same Repository Server and select a repository from the local repository list. 6. 3. 8. Choose the global repository from the global repository list. Click Close. Enter the repository user name and password for the local repository. and the port number the Repository Server uses for connections.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. If you want to register a local repository managed by a different Repository Server. 5. If you want to register a local repository managed by the same Repository Server. 7.

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

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

The identification number assigned to the repository connection. The repository client application associated with the connection. To view user connection details: 1. 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 User Connections and Locks 79 . 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 time the user connected to the repository. Viewing Connection Details in the Repository Manager Use the following procedure to view connection details in the Repository Manager. 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. 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. Table 3-5 describes the repository user connection details: Table 3-5. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

88

Chapter 3: Managing the Repository

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

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

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

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

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

Registering and Unregistering LDAP Security Modules

89

The Repository Server lists the available plug-ins.

4.

Select the Authentication Module, and choose Action-Register.

90

Chapter 3: Managing the Repository

The Register Security Module dialog box displays.

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

5.

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

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

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

3.

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

4.

Enter LDAP server options.

92

Chapter 3: Managing the Repository

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

Principal User Name Principal User Password 5.

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

Registering and Unregistering LDAP Security Modules

93

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

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

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

94

Chapter 3: Managing the Repository

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

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

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

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

3.

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

Registering and Unregistering LDAP Security Modules

95

The Unregister Package dialog box displays.

4.

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

96

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

♦ ♦

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

98

Chapter 3: Managing the Repository

INFO : REP_51006 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized configuration information. INFO : SF_34003 [Fri Jul 16 09:16:47 2004] : (1324|1452) Server initialization completed. the messages appear in the Application Log component of the Windows Event Viewer. Database : penguin@production. INFO : REP_51008 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized request dispatcher. Reading the Repository Log Files 99 . INFO : SF_34002 [Fri Jul 16 09:16:46 2004] : (1324|1452) Server starting up. since some message codes are embedded within other codes. However. Informatica recommends setting the Severity Level option in the Repository Server configuration to Warning or Error unless you are troubleshooting a problem with the Repository Server. INFO : 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. Repository Server Log File Sample The following sample is an excerpt from a Repository Server log file that illustrates log file codes: INFO : SF_34058 [Fri Jul 16 09:16:46 2004] : (1324|1452) Service started. INFO : REP_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. Messages sent from the Repository Server display PmRepServer in the Source column. to ensure you are viewing the true message code. Sample Application Log If you configure the Repository Server to log messages in the event log. INFO : REP_51005 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized database connection information.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. you must view the text of the message. the file can grow to contain a large number of entries. 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.

Application Log Message Detail Repository Agent Log File By default.Figure 3-4 shows a sample Windows Event Viewer: Figure 3-4.log. You can specify a unique log file name for individual repositories by configuring the LogFileName option when you create or edit a repository configuration. Event Viewer Application Log Message Figure 3-5 shows the text of the message when you double-click it: Figure 3-5. You can view the repository log file using a text editor program such as Windows Notepad. 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 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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. 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. Compared Objects in Compare Selected Object Source field Target field Reusable transformation field Mapping variable External procedure initialization properties Session component Compared Object Source Target Reusable transformation Mapping Transformation instance Session Comparing Folders 175 .Table 6-2.

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

However.For example. as well as comments for the shortcut: Figure 7-1. The shortcut object displays the following details about the referenced object: ♦ ♦ ♦ Repository name Folder name Table or transformation name Understanding Shortcut Properties 185 . 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. 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.

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.

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

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

4.

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

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

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

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

6.

Choose Repository-Save.

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

Creating a Local Shortcut

189

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

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

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

190

Chapter 7: Local and Global Shortcuts

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

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

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

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

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

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

2.

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

3. 4.

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

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

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

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

6.

Choose Repository-Save.

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

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

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

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

3.

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

4. 5.

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

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

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

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

7.

Choose Repository-Save.

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

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

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

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

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

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

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

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

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

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

Creating a Global Shortcut

193

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

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

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

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

194

Chapter 7: Local and Global Shortcuts

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

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

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

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

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

Working with Shortcuts

195

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

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

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

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

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

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

Tips

197

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

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

♦ ♦ ♦

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

198

Chapter 7: Local and Global Shortcuts

Chapter 8

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

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

199

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

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

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

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

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

You can also change the object status on this tab from the Repository Manager. the time the label was applied. Figure 8-4 shows the Labels tab of the Properties dialog box: Figure 8-4. see “Working with Labels” on page 219. and comments associated with the label. 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. you can view all labels applied to the object. For each label.Labels Properties On the Labels tab. you can view the current status of the object. Object Status Properties On the Object Status tab.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

♦ ♦

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

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

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

224

Chapter 9: Grouping Versioned Objects

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

Specify query conditions.

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

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

Working with Object Queries

225

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

Add logical operators. Add multiple query conditions.

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

4

3

226

Chapter 9: Grouping Versioned Objects

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

Check-in time

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

Date/time Numeric

Comments

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

String

Deployment Dispatch History

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

Date/time Numeric

Deployment Receive History

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

Date/time Numeric

Working with Object Queries

227

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

Include Children

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

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

Include Children and Parents

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

Where (Value 1) depends on (Value 2)

Include Parents

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

Where (Value 1) depends on (Value 2)

Include Primary/ Foreign Key Dependencies

Displays primary key-foreign key dependencies.

N/A

228

Chapter 9: Grouping Versioned Objects

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

Last Saved Time

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

Latest Status

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

Checked-out Latest checked-in Older

Metadata Extension

Is Equal To Is Not Equal To

User-defined metadata domain Any vendor-defined metadata extensions

Object Name

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

String

Working with Object Queries

229

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

Object Used Status

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

Is Equal To

Shortcut status

Is Equal To

Is Not Shortcut Is Shortcut

Reusable Status User

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

Non-reusable Reusable Users in specified repository

Valid Status Version Status

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

Invalid Valid Deleted Not deleted

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

230

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

Working with Object Queries

231

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

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

232

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

objects in the repository.

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

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

Working with Object Queries

233

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

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

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

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

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

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

234

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

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

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

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

depending on which operation the PowerCenter Server tried to perform. or task while a repository is blocked. For example. The PowerCenter Server fetches the repository object and completes the workflow. When the repository allows access again. The current operation will resume. the message appears in the workflow log. or task. workflow log. session. it displays the following message: The folder/object deployment has completed. or session log. The current operation will be suspended until the deployment is completed.Server tries to access the repository to run a workflow. Overview 243 . session. The error message appears in either the server log. 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. if the PowerCenter Server tried to fetch session information to run a session in a workflow. The PowerCenter Server pauses until the repository completes the deploy.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

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

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

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

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

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

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Overview 405 .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. Native Connect String Syntax Database IBM DB2 Informix Microsoft SQL Server Oracle Sybase Teradata* Connect String Syntax dbname dbname@servername servername@dbname dbname.world (same as TNSNAMES entry) servername@dbname ODBC_data_source_name or ODBC_data_source_name@db_name or ODBC_data_source_name@db_user_name Example mydatabase mydatabase@informix sqlserver@mydatabase oracle.

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

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

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

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

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

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

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

412

Chapter 16: Using pmrep and pmrepagent

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

StopRepository SwitchConnection Truncatelog Unregister UpdateConnection Updateemailaddr Updateseqgenvals

Updateserver Updatesrcprefix Updatesrvvar UpdateStatistics Updatetargprefix

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

pmrep Repository Commands

413

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

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

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

414

Chapter 16: Using pmrep and pmrepagent

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

-A

repserver_password_ environment_variable repository_name database_type database_user_name

-r -t -u

-m -p

Optional Required/ Optional

n/a database_password

-P

Required/ Optional

database_password_ environment_variable

-c

Required

database_connect_string

-d

Optional

code_page

pmrep Repository Commands

415

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

-l

Optional

license_file_name

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

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

-b -j -q

Optional Optional Optional

skip_workflow/ session_logs skip_deploy_group _history skip_MX_data

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

416

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

-P

password_environm ent_variable connect_string

-c

-l -r

Required Optional

code_page rollback_segment

pmrep Repository Commands

417

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

-b -v -d -t

Optional Optional Optional Optional

database_name server_name domain_name trusted_connection

-x

Optional

n/a

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

418

Chapter 16: Using pmrep and pmrepagent

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

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

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

pmrep Repository Commands

419

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

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

420

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

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

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

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

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

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

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

-r

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

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

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

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

422

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

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

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

or Validate pmrep commands. to list all sources in a reusable session.ORDERS Shortcut_To_ITEM_ID listtablesbysess completed successfully. Note: When the mapping contains a mapplet with a source. For example. enter the following text at the pmrep> prompt: listtablesbysess -f myfolder -s s_reus_sess1 -t source pmrep returns the following information: ITEMS mapplet1. If you want to list dependencies for non-reusable objects. you can list all targets in a non-reusable session in a workflow: listtablesbysess -f myfolder -s wf_workkflow1. Note: ListObjectDependencies accepts a persistent input file and it can create a persistent output file.For example. These files are the same format.ORDERS. see “Using the Persistent Input File” on page 494. pmrep includes the mapplet name with the source. To list object dependencies. ListObjectDependencies returns the number of records if the command runs successfully. you must use a persistent input file containing object IDs. If you create an output file. you must have the following privileges and permissions: ♦ ♦ Browse Repository privilege Read permission on the folder ListObjectDependencies uses the following command syntax: ListObjectDependencies -n object_name -o object_type_name -t object_subtype -v version_number -f folder_name -i persistent_input_file -d dependency_object_type -p dependency_direction -s include_pk-fk_dependency -g across_repositories -u persistent_output_file_name -a append -c column_separator -r end-ofrecord_separator -l end-of-listing_indicator -b verbose pmrep Repository Commands 429 . For more information on using a persistent input file. you can use it as input to the ApplyLabel. You can create this file by running a query and choosing to create a text file. AddToDeployment Group.s_nrsess1 -t target pmrep returns the following information: target1_inst ORDERS_BY_CUSTID Shortcut_To_tgt2_inst listtablesbysess completed successfully. Listing Object Dependencies (ListObjectDependencies) Use the ListObjectDependencies command list dependency objects for reusable and nonreusable objects. such as mapplet1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You must use this parameter when you add a specific object. You cannot specify an object if you use the -i option. You can specify source. or it returns a list of objects that already are in the deployment group. If the command fails. The name of the object you are adding to the deployment group. see Table 16-16 on page 426. For valid subtypes. cube. The type of object you are adding. You can specify objects using command options or you can use a persistent input file. you must use a persistent input file that contains encoded object IDs. workflow. transformation. target. session. worklet. For more information on adding to a deployment group. You cannot specify a checked out object. AddToDeploymentGroup Options and Arguments (pmrep) Option -p -n Required/ Optional Required Required/ Optional Argument Name deployment_group_name object_name Argument Description The name of the deployment group to add objects to. You cannot add checked out objects to a deployment group. see “Working with Deployment Groups” on page 236. you can specify only the deployment group name option. session configuration. scheduler. task. If AddToDeploymentGroup runs successfully. Use AddToDeploymentGroup to add source.Adding to a Deployment Group (AddToDeploymentGroup) The AddToDeploymentGroup command adds objects to a deployment group. transformation. Required when adding a specific object. The type of task or transformation you are adding. you must have the following privileges and permissions: ♦ ♦ Use Repository Manager privilege Write permission on the folder AddToDeploymentGroup uses the following command syntax: AddToDeploymentGroup -p deployment_group_name -n object_name -o object_type -t object_subtype -v version_number -f folder_name -i persistent_input_file -d dependency_types Table 16-53 lists pmrep AddToDeploymentGroup options and arguments: Table 16-53. For more information on using a persistent input file. and task objects. worklet. scheduler. To add objects to a deployment group. If you use a persistent input file. see “Using the Persistent Input File” on page 494. -o Required/ Optional object_type -t Required/ Optional object_subtype pmrep Change Management Commands 461 . mapping. If you want to add non-reusable input objects. mapping. session configuration. workflow. session. it displays the reason for failure. target. and dimension. it either sends back no status information. Use AddToDeployment Group to add reusable input objects.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

For more information on unregistering plug-ins.rep Unregistering Plug-ins (Unregisterplugin) The pmrepagent Unregisterplugin command removes a plug-in from a repository. The name of the license file. Use this option only with a repository using an external security module. see “Unregistering a Repository Plug-in” on page 86. Use this option only when unregistering an external module. -a -w -b -j -q Required Optional Optional Optional Optional license_file_name n/a skip_workflow/session_log skip_deploy_group_history skip_MX_data Note: You can also restore Teradata repositories using Fastload. 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. Use the -x or -X option. see “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. Removes user name-login mapping. For more information. Restore Options and Arguments (pmrepagent) Option -X Required/ Optional Required/ Optional Argument Name verify_password_environment_ variable Argument Description The verify password environment variable. You must use either the -x or -X option when you want to retain an external security module. 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 . Skips tables related to workflow and session logs during backup.Table 16-73. Skips tables related to MX data during backup. Example The following example restores a repository to a Solaris machine and specifies the administrator user name and password in order to keep the LDAP security module registration. 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. but not both. Skips deployment group history during backup.

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

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

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

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

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

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

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

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

Using the Object Import Control File When you use the pmrep ObjectImport command. you can supply a control file to answer questions that you normally address when you import objects with the Import Wizard.g. The following is a sample of the impcntl. e. but you must include its location in the input XML file.dtd. The import control file installs with the PowerCenter Client.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. TARGET and etc. RESOLVECONFLICT?)> <!ATTLIST IMPORTPARAMS CHECKIN_AFTER_IMPORT CHECKIN_COMMENTS APPLY_LABEL_NAME RETAIN_GENERATED_VALUE COPY_SAP_PROGRAM APPLY_DEFAULT_CONNECTION > (YES | NO) "NO" CDATA CDATA #IMPLIED #IMPLIED (YES | NO) "NO" (YES | NO) "YES" (YES | NO) "NO" <!--FOLDERMAP matches the folders in the imported file with the folders in the target repository --> <!ELEMENT FOLDERMAP EMPTY> <!ATTLIST FOLDERMAP SOURCEFOLDERNAME CDATA #REQUIRED #REQUIRED #REQUIRED #REQUIRED SOURCEREPOSITORYNAME CDATA TARGETFOLDERNAME CDATA TARGETREPOSITORYNAME CDATA > <!--Import will only import the objects in the selected types in TYPEFILTER node --> <!--TYPENAME type name to import. you must create an XML file defined by impcntl. This should comforming to the element name in powermart. 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*.Version 7.--> <!ELEMENT TYPEFILTER EMPTY> <!ATTLIST TYPEFILTER 496 Appendix A: Working with pmrep Files .dtd file: <!-. To create a control file.dtd. SOURCE.Informatica Object Import Control DTD Grammar . TYPEFILTER*.

) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .required for source object to identify uniquely--> <!--OBJECTTYPENAME Object type name--> <!--FOLDERNAME Folder which the object belongs to--> <!--REPOSITORYNAME Repository name that this object belongs to--> <!--RESOLUTION Resolution to apply for the object in case of conflict--> <!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 . typename etc.TYPENAME > CDATA #REQUIRED <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. 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.

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

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

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

dtd.<IMPORTPARAMS CHECKIN_AFTER_IMPORT="YES" CHECKIN_COMMENTS="PMREP_IMPORT_PARENT_TYPOBJ_REPLACE_CHILDREUSE" APPLY_LABEL_NAME="LABEL_IMPORT_PARENT_REPLACE_CHILDREUSE_ALL"> <!--FOLDERMAP matches the folders in the imported file with the folders in the target repository --> <FOLDERMAP SOURCEFOLDERNAME="PMREP_CHECKED_OUT" SOURCEREPOSITORYNAME="PMREP_AUTOMATION_1027" TARGETFOLDERNAME="PMREP_CHECKED_OUT_IMPORT" TARGETREPOSITORYNAME="PMREP_AUTOMATION_1027"/> <!--Import will only import the objects in the selected types in TYPEFILTER node --> <!--TYPENAME type name to import. 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. e. This should conforming to the element name in powermart.g. TARGET and etc. SOURCE.

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

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

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

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

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

508 Appendix A: Working with pmrep Files .

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

targets. transformations. you can edit a mapping if you have one of the following sets of privileges and permissions: ♦ ♦ Use Designer privilege with both read and write permission on the folder Super User privilege Table B-1 lists the required privileges and permissions for Designer tasks: Table B-1. targets. Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources. transformations. Read/Write Read Read Read/Write Read Read/Execute Read Copy object from one folder to another Copy and paste objects in mappings or mapplets in the same folder Compare objects Export objects Import objects Edit breakpoints Create a debug session Use Designer Use Designer Use Designer Use Designer Use Designer Use Designer Use Designer and Use Workflow Manager Use Designer and Workflow Operator 510 Appendix B: Permissions and Privileges by Task . For example. you must have one of the listed sets of privileges and permissions. Read permission in the originating folder. Read and write permission for the destination folder. and mappings Create shortcuts from a shared folder Repository Privilege Use Designer Use Designer Use Designer Use Designer Folder Permission None required Read Read/Write Read permission in the shared folder. and mappings Create/edit sources.Designer Tasks To perform the following Designer tasks. Read and write permission in the destination folder.

if you enabled enhanced security. Table B-2 lists the required privileges and permissions for Workflow Manager tasks: Table B-2. Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Administer Repository Use Workflow Manager Use Workflow Manager Connection Object Permission None required None required None required Read Write Write permission and own the connection object. you can edit a session if you have one of the following sets of permissions and privileges: ♦ ♦ Use Workflow Manager privilege with both read and write permission on the folder Super User privilege Note: In addition. Execute None required Execute Execute Workflow Manager Task Connect to the repository using the Workflow Manager Create workflows and tasks Edit workflows and tasks Create and edit sessions Delete Connection Folder Permission None required Read/Write Read/Write Read/Write None required None required None required Schedule or unschedule workflows Use Workflow Manager Workflow Operator Read/Execute Read Read/Execute Read Start workflows immediately Use Workflow Manager Workflow Operator Workflow Manager Tasks 511 . you must have one of the listed sets of privileges and permissions.Workflow Manager Tasks To perform the following Workflow Manager tasks. For example. Write permission and belong to the same group as the owner of the connection object. you must also have read permission for connection objects associated with the session.

Write None required None required Read Read/Write Read/Write None required None required None required None required None required None required None required 512 Appendix B: Permissions and Privileges by Task . Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager and Administer Server Use Workflow Manager Use Workflow Manager Administer Repository Administer Server Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Connection Object Permission None required Workflow Manager Task Stop the PowerCenter Server Folder Permission None required Configure database. FTP.Table B-2. and external loader connections in the Workflow Manager Edit database. FTP. and external loader connections in the Workflow Manager Manage connection object permissions Register PowerCenter Servers and configure server variable directories Export objects Import objects Validate workflows and tasks Run Workflow Monitor None required None required None required Read.

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

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

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

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

Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Create a folder Create or edit deployment group Create or edit label Create or edit query Delete (versioning) Delete a folder Repository Privilege Administer Repository Administer Repository Administer Repository Browse Repository Use Repository Manager Browse Repository Administer Repository Delete from Deployment Group Deploy Edit folder Use Repository Manager Administer Repository Browse Repository Administer Repository Edit folder properties Browse Repository Administer Repository Export objects Freeze folder Use Repository Manager Browse Repository Administer Repository Import objects Import. export. or remove the registry Manage users. and privileges Mass update Purge (versioning) Receive user and group notifications Recover Remove Label References Run Query Use Repository Manager Browse Repository Administer Repository Super User Administer Repository Super User Use Repository Manager Use Repository Manager Browse Repository Manager Folder Permission None required N/A N/A N/A Write Folder owner and read permission Read N/A Read on the original folder. 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 .

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

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

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

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

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

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

168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245. 192 creating 14 promoting 112. 453 deploying 469 Designer uses 166 editing 173 editing permissions 149 locking during folder copy 249 maintaining connections during copy 245 modifying 456 naming copies 249 organizing 166 overview 166 owner and owner’s group 169 H HTML view Administration Console 53 I IBM DB2 connect string example 405 setting tablespace name 107 Import Wizard importing objects 287 resolving object conflicts 281 Index 525 . 171 renaming 173 Repository Manager uses 166 shared 15. 169 shortcuts 249 Workflow Manager uses 166 FTP connections during folder or deployment group copy 245 permissions and privileges 245 G global objects See Workflow Administration Guide global repositories code page 117. 117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182.powrmart. 249 environment 192 repository usernames 193 server username 193 tips 197 updating 194 updating views 194 groups creating user 128 default security 127 editing description 129 F FindCheckout description 472 flat files MX view of repository file definitions 343 view of fields 345 folder permissions description 126 editing 149 overview 148.dtd 267 privileges 266 sessions 272 shortcuts 270 steps for 285 versioned objects 273 external loader connections during folder or deployment group copy 245 permissions and privileges 245 external security module registering 484 unregistering 489 properties 168. 249 copying between local repositories 250 copying global shortcuts 250 copying local shortcuts 249 copying or replacing 250 copying shortcuts 249 creating 171 deleting 173.

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

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

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

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

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

50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. overview 142 troubleshooting 163 Workflow Manager tasks 511 product license keys overview 119 promoting repositories 117 purging description 216 objects 216 Q queries See also object queries executing 470 R recovering deleted objects 215 register description 434 registering a user 457 plug-in using pmrepagent 482 security module using pmrepagent 484 Registerplugin description 482 Registeruser description 457 registry exporting 32 importing 32 releasing repository locks 83. 250 reports metadata 335 repositories adding 29 adding metadata 9 administration overview 11 architecture 3 avoiding shared accounts 160 backing up 66 backing up with pmrepagent 477 changing a code page 117 checking status 54 code pages 51. 117. 75. 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. troubleshooting 163 starting 71 Index 531 . 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.Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126. overview 155 overview 2. 160 security log file 153 security.

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

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

U UndoCheckout description 473 unregister description 440 unregistering plug-ins using pmrepagent 487 security module using pmrepagent 489 Unregisterplugin description 487 UpdateConnection description 441 Updateemailaddr description 442 Updateseqgenvals description 444 Updateserver description 443 Updatesrcprefix description 445 updating non-reusable sessions 446 Updatesrvvar description 446 Updatestatistics description 447 Updatetargetprefix description 447 updating non-reusable sessions 448 updating repository license files 111 shortcuts 194 Upgrade description 490 upgrading repositories using pmrepagent 490 user connections description 126 terminating 83. 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.

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 .