Repository Guide

Informatica PowerCenter®
(Version 7.1.1)

Informatica PowerCenter Repository Guide Version 7.1.1 August 2004 Copyright (c) 1998–2004 Informatica Corporation. All rights reserved. Printed in the USA. This software and documentation contain proprietary information of Informatica Corporation, they are provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free. Informatica, PowerMart, PowerCenter, PowerChannel, PowerCenter Connect, MX, and SuperGlue are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software are copyrighted by DataDirect Technologies, 1999-2002. Informatica PowerCenter products contain ACE (TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved. Portions of this software contain copyrighted material from The JBoss Group, LLC. Your right to use such materials is set forth in the GNU Lesser General Public License Agreement, which may be found at http://www.opensource.org/licenses/lgpl-license.php. The JBoss materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Portions of this software contain copyrighted material from Meta Integration Technology, Inc. Meta Integration® is a registered trademark of Meta Integration Technology, Inc. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software is Copyright (c) 1999-2004 The Apache Software Foundation. All rights reserved. DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

Table of Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv PowerCenter 7.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv PowerCenter 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi PowerCenter 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx About Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvii Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvii Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Webzine . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . xxxviii Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxix

Chapter 1: Understanding the Repository . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Repository Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Repository Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Repository Server Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Repository Manager . . . . . . . . . . . . . . . . . 6 Receiving Notifications in the Workflow Manager . . . . . . . . . . . . . . . . . . 7 Receiving Notifications in the Workflow Monitor . . . . . . . . . . . . . . . . . . 7 PowerCenter Server Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 User-Created Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Understanding Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Administering Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

i

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PowerCenter Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Building the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Reusing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Reusing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2: Using the Repository Manager . . . . . . . . . . . . . . . . . . . . . 19
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Displaying Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Navigator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Adding and Removing a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Adding a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Removing a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Working with Repository Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Connecting to a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Connecting to Multiple Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Exporting/Importing Repository Connection Information . . . . . . . . . . . 32 Searching for Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Performing Keyword Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Searching All Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Validating Multiple Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Comparing Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Truncating Workflow and Session Log Entries . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 3: Managing the Repository . . . . . . . . . . . . . . . . . . . . . . . . . 49
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Permissions and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Repository Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Navigating the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

ii

Table of Contents

Console Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Registering and Connecting to the Repository Server . . . . . . . . . . . . . . . . . . 58 Registering a Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Connecting to the Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Disconnecting from the Repository Server . . . . . . . . . . . . . . . . . . . . . . 59 Tuning Repository Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Updating Repository Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Increasing Repository Copy, Backup, and Restore Performance . . . . . . . 60 Copying a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Deleting a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Backing Up and Restoring a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Backing Up a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Restoring a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Starting and Stopping the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Enabling the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Starting the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Stopping the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Disabling the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Sending Repository Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Registering a PowerCenter Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Migrating the Repository to a Different Repository Server . . . . . . . . . . . . . . 77 Propagating Repository Domain Connection Information . . . . . . . . . . . . . . 78 Viewing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Viewing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Viewing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Closing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Closing Connections in the Repository Manager . . . . . . . . . . . . . . . . . . 83 Closing Connections in the Administration Console . . . . . . . . . . . . . . . 84 Registering and Unregistering Repository Plug-ins . . . . . . . . . . . . . . . . . . . 85 Registering a Repository Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Unregistering a Repository Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Registering and Unregistering LDAP Security Modules . . . . . . . . . . . . . . . . 88 Registering an LDAP Security Module . . . . . . . . . . . . . . . . . . . . . . . . . 88 Unregistering an LDAP Security Module . . . . . . . . . . . . . . . . . . . . . . . 95 Reading the Repository Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Log File Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Process Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table of Contents iii

Repository Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Repository Agent Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 4: Configuring the Repository . . . . . . . . . . . . . . . . . . . . . . 103
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Adding a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Editing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Removing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Exporting and Importing Repository Configurations . . . . . . . . . . . . . . . . . 115 Exporting a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . 115 Importing a Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . 115 Creating or Promoting a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Promoting a PowerCenter Repository . . . . . . . . . . . . . . . . . . . . . . . . . 117 Enabling Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Working with PowerCenter Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License Key Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License Key Repository Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 License File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Managing License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 5: Repository Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Default Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 User Groups and Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Creating a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Editing a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Deleting a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using Default Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using LDAP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Switching Between Default and External User Authentication . . . . . . . 133 Creating and Editing Repository Users . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Editing a User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Creating a Repository User Under an External Directory Service . . . . . 137

iv

Table of Contents

Editing a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Enabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Disabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Removing a Repository User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Default Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Extended Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Assigning and Revoking a Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Configuring Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Configuring Versioning Object Permissions . . . . . . . . . . . . . . . . . . . . 149 Managing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Viewing User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Handling User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Creating an Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Repository Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Locking the Same Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Locking Within Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Locking with Cubes and Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 155 Locking Business Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Handling Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Viewing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Releasing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Chapter 6: Working with Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Repository Manager . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Using Folders in the Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . 166 Organizing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Folder Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Folder Owner and Owner's Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Shared Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Configuring a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Table of Contents

v

Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Editing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Deleting a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Comparing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Compared Attributes and Object Differentiation . . . . . . . . . . . . . . . . . 174 One-Way and Two-Way Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . 176 Editing and Saving Results Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Steps for Comparing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 7: Local and Global Shortcuts . . . . . . . . . . . . . . . . . . . . . . 181
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Shortcuts Versus Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Understanding Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Default Shortcut Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Describing the Object and the Shortcut . . . . . . . . . . . . . . . . . . . . . . . 184 Locating the Referenced Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Creating a Local Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Creating a Global Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Configuring the Global Shortcut Environment . . . . . . . . . . . . . . . . . . 192 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Refreshing Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Copying a Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Renaming Source Qualifiers to Shortcut Sources . . . . . . . . . . . . . . . . . 196 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Chapter 8: Working with Versioned Objects . . . . . . . . . . . . . . . . . . 199
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Sample Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Viewing Results View Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Working with Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Viewing Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Labels Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Object Status Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Changing Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

vi

Table of Contents

Changing Folder Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Tracking Changes to Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Viewing Object History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Comparing Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Checking Out and Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Checking Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Viewing Checked Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Undoing a Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Deleting and Purging Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Deleting a Versioned Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Recovering a Deleted Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Purging a Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Chapter 9: Grouping Versioned Objects . . . . . . . . . . . . . . . . . . . . . 217
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Working with Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Creating and Editing Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Applying Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Working with Object Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Configuring Query Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Validating and Saving a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Running a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Viewing Query Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Sample Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Working with Deployment Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Creating and Editing a Deployment Group . . . . . . . . . . . . . . . . . . . . . 237 Viewing Deployment History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Rolling Back a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Working with Static Deployment Groups . . . . . . . . . . . . . . . . . . . . . . 239 Working with Dynamic Deployment Groups . . . . . . . . . . . . . . . . . . . 240

Chapter 10: Copying Folders and Deployment Groups . . . . . . . . . . 241
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 PowerCenter Server Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Using the Copy Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Copy Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Table of Contents

vii

Registered PowerCenter Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Copying Plug-in Application Information . . . . . . . . . . . . . . . . . . . . . . 247 Copying or Replacing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Copying Within a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Copying From Local Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Steps for Copying or Replacing a Folder . . . . . . . . . . . . . . . . . . . . . . . 250 Copying a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Copying Composite Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Copying Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Object Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Steps for Copying a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . 258

Chapter 11: Exporting and Importing Objects . . . . . . . . . . . . . . . . . 263
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Working with Objects and Object Types . . . . . . . . . . . . . . . . . . . . . . . 265 Working with Different Repository Versions . . . . . . . . . . . . . . . . . . . . 265 Permissions and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 The XML and DTD Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 CRCVALUE Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Exporting and Importing Multiple Objects and Object Types . . . . . . . . . . . 269 Working with Dependent Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Exporting and Importing Parent Objects . . . . . . . . . . . . . . . . . . . . . . . 271 Working with Object Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Shortcut Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Importing Shortcuts to Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Modifying an Exported XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Modifiable Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

viii

Table of Contents

Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Validating XML Files Against the DTD . . . . . . . . . . . . . . . . . . . . . . . 280 Validating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Resolving Object Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Steps for Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Steps for Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Chapter 12: Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Resolving Copy Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Steps for Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Copying Workflow Manager Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Workflows and Worklets . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Copying Workflow Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Copying Designer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Copying Mapping and Mapplets Segments . . . . . . . . . . . . . . . . . . . . . 310

Chapter 13: Exchanging Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Steps for Exporting Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Steps for Importing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Chapter 14: Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Working with Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Creating Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Editing Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Deleting Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Chapter 15: Using Metadata Exchange (MX) Views . . . . . . . . . . . . . 333
Viewing the Repository Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 MX View Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Using PowerCenter Metadata Reporter . . . . . . . . . . . . . . . . . . . . . . . . 335
Table of Contents ix

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

Progress Indicator 22 Chapter 2: Using the Repository Manager .Repository Manager Windows The Repository Manager has a main window and a status bar for information on the operation you are performing. the Status Bar reflects the connection in progress with a progress indicator. Repository Manager Components Navigator Window Dependency Window Output Window Status Bar Main Window When the Repository Manager accesses the repository. The Repository Manager can display the following windows: ♦ ♦ ♦ ♦ Navigator Main Dependency Output Figure 2-1 shows the Repository Manager components: Figure 2-1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Right-click the Repository Server and choose Disconnect. In the Console Tree. 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. To disconnect from the Repository Server: 1. 2.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Launch the Repository Manager and connect to the repository. Viewing Connection Details in the Repository Manager Use the following procedure to view connection details in the Repository Manager. Repository User Connection Details Property User Connection ID Application Hostname Host Address Login Time Last Active Time Remote Host Port Description The user name associated with the connection. The TCP/IP address of the machine associated with the connection. The port number the machine hosting the repository client application uses to communicate with the repository. The time of the last metadata transaction between the repository client application and the repository. The name of the machine running the application. Viewing User Connections and Locks 79 .Viewing User Connections and Locks The Repository Manager and Administration Console allow you to view the connection details and locks details for users connected to a repository. The time the user connected to the repository. 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. To view user connection details: 1. The identification number assigned to the repository connection. The repository client application associated with the connection.

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

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

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

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

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

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

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

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

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

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

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

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

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

88

Chapter 3: Managing the Repository

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

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

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

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

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

Registering and Unregistering LDAP Security Modules

89

The Repository Server lists the available plug-ins.

4.

Select the Authentication Module, and choose Action-Register.

90

Chapter 3: Managing the Repository

The Register Security Module dialog box displays.

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

5.

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

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

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

3.

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

4.

Enter LDAP server options.

92

Chapter 3: Managing the Repository

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

Principal User Name Principal User Password 5.

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

Registering and Unregistering LDAP Security Modules

93

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

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

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

94

Chapter 3: Managing the Repository

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

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

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

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

3.

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

Registering and Unregistering LDAP Security Modules

95

The Unregister Package dialog box displays.

4.

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

96

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

♦ ♦

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

98

Chapter 3: Managing the Repository

INFO : REP_51007 [Fri Jul 16 09:37:33 2004] : (1396|1952) Repository runtime manager initialized. Informatica recommends setting the Severity Level option in the Repository Server configuration to Warning or Error unless you are troubleshooting a problem with the Repository Server. INFO : REP_51008 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized request dispatcher. INFO : SF_34002 [Fri Jul 16 09:16:46 2004] : (1324|1452) Server starting up. the messages appear in the Application Log component of the Windows Event Viewer. 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. Reading the Repository Log Files 99 . INFO : REP_51006 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized configuration information.When you configure the Repository Server to write Trace or Debug severity level messages to the Repository Server log file. INFO : REP_51005 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized database connection information. since some message codes are embedded within other codes. to ensure you are viewing the true message code. However. Messages sent from the Repository Server display PmRepServer in the Source column. Database User : admin1 INFO : REP_51009 [Fri Jul 16 09:37:37 2004] : (1396|1952) Informatica repository agent ready to receive request on port 5003. INFO : REP_51003 [Fri Jul 16 09:37:33 2004] : (1396|1952) Copyright (c) Informatica Corporation 2000-2001 INFO : REP_51004 [Fri Jul 16 09:37:33 2004] : (1396|1952) Informatica Repository Agent starting up. INFO : SF_34003 [Fri Jul 16 09:16:47 2004] : (1324|1452) Server initialization completed. Sample Application Log If you configure the Repository Server to log messages in the event log. 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. Database : penguin@production. the file can grow to contain a large number of entries. you must view the text of the message.

Event Viewer Application Log Message Figure 3-5 shows the text of the message when you double-click it: Figure 3-5. Application Log Message Detail Repository Agent Log File By default. 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 specify a unique log file name for individual repositories by configuring the LogFileName option when you create or edit a repository configuration. You can write repository log messages from multiple repositories to the same log file. 100 Chapter 3: Managing the Repository .log.Figure 3-4 shows a sample Windows Event Viewer: Figure 3-4.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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

the shortcut becomes invalid. 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. 186 Chapter 7: Local and Global Shortcuts .

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

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

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

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

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

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

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

Version Properties 204 Chapter 8: Working with Versioned Objects .Figure 8-2 shows the Object tab in the Properties dialog box: Figure 8-2. 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. Object Properties Version Properties On the Version tab. and any comments associated with the version. Figure 8-3 shows the Version tab in the Properties dialog box: Figure 8-3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Also displays objects that are older or newer than matching objects in the global shared folder. Copying a Deployment Group 261 . The wizard takes you back to Select Shared Folders dialog box. a message warns you that shortcuts to missing objects will be removed. If there are differences between the folders. Lists the results from the folder compare. Copy Deployment Group Wizard Prompts Copy Deployment Group Wizard Dialog Box Compare Shared Folder Compare Results Mode Advanced Advanced Prompt Allows you to compare folders if the folders you choose in Override Shared Folder dialog box are different.Table 10-3. Displays objects that exist in the local shared folder but not in the global shared folder.

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 .you can modify for an exported object and then import. Table 11-5.

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

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

a mapplet cannot contain a target definition. For details on CRCVALUE codes. Importing Objects 281 . 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. Create rules on the Specify Rules for Conflict Resolutions page of the Import Wizard. When you create an object resolution rule. The PowerCenter Client validates each object in the XML file to ensure that it conforms to the PowerCenter specifications for that object. see “The XML and DTD Files” on page 267. 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. For example.Validating Objects You can only import valid objects into the repository. 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. In addition. You can choose to resolve object conflicts in the following ways: ♦ ♦ Create general object resolution rules. 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. Resolve specific object conflicts. The PowerCenter Client does not import objects with CRCVALUE codes that have been modified nor objects that do not conform to PowerCenter specifications. Resolving Object Conflicts When you import objects.

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

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

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

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

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

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

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

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

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. 10.9. select Apply Label and click Select Label. You can only apply a label to the objects if you choose to check them in. To check in all objects after importing them. Click Next. In the Label Browser dialog box. 290 Chapter 11: Exporting and Importing Objects . choose the label and click OK. 11. You can check in the objects and apply labels to the them after importing. select Check In and enter comments in the comment field.

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

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

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

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

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

if you edit the metadata for a mapplet. 296 Chapter 11: Exporting and Importing Objects . 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. You must be able to create the object you define in the Designer or Workflow Manager. make sure the source is not a VSAM source.Troubleshooting The solutions to the following situations might help you with exporting and importing objects. but the Designer marked it invalid. it imports the object the shortcut references using the metadata in the XML file. The Designer marks mapplets with VSAM sources as invalid. 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. For example. Make sure that the metadata you define in the XML file is valid. To import a shortcut to an object into a repository.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

You can export multiple source definitions or multiple target definitions at a time. For more information on licenses.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. the Repository Agent also exports the source or target containing the corresponding primary key. You cannot export cubes and dimensions. You can import multiple source and target definitions at a time. You cannot export shortcuts. Overview 315 . However. When you export a source or target with a foreign key. see “Working with PowerCenter Licenses” on page 119. You cannot export source and target definitions at the same time. You must have a Metadata Exchange option license key to exchange metadata for a specific tool. you can export targets to some tools as dimensions.

You can click More Info to read about the tool requirements. and choose Repository-Export Metadata.Steps for Exporting Metadata Use the following procedure to export metadata from PowerCenter to a file recognized by the target BI or data modeling tool. To export metadata: 1. In the Repository Manager Navigator. The Metadata Export Wizard appears. 316 Chapter 13: Exchanging Metadata . select the object or objects you want to export. Choose the target tool you want to export the object to. 2. Choose a path and file name.

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

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

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

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

UTC time when the parent target was last saved. Folder ID. the names of the shortcut and the parent targets display. Database type of parent target. UTC time (Coordinated Universal Time) when the parent target was last checked in. Name of parent target.REP_ALL_TARGET_FIELDS This view provides all the fields and field properties for targets defined in REP_ALL_TARGETS view. For global shortcuts. ID of the first field of parent target. Time when target was last modified. Target description. Folder ID. Table 15-14 lists target field data in the REP_ALL_TARGET_FIELDS view: Table 15-14. Time when the parent target was last modified. Parent target ID. Status of the target version. Target Views 349 . Folder name. UTC time when the target was last checked in. Status of the parent target version. Target version number. Target version number. Business name of the parent target. Target name. REP_ALL_TARGET_FIELDS MX View Column Name PARENT_SUBJECT_AREA PARENT_SUBJECT_ID PARENT_TARGET_NAME PARENT_TARGET_BUSINESS_NAME PARENT_TARGET_ID PARENT_TARGET_DESCRIPTION PARENT_TARGET_VERSION_NUMBER PARENT_TARGET_VERSION_STATUS PARENT_TARGET_UTC_CHECKIN PARENT_TARGET_UTC_LAST_SAVED PARENT_TARGET_LAST_SAVED PARENT_TARGET_FILE_ID PARENT_TARGET_FIRST_FIELD_ID PARENT_TARGET_DATABASE_TYPE SUBJECT_AREA SUBJECT_ID TARGET_NAME TARGET_ID TARGET_DESCRIPTION TARGET_VERSION_NUMBER TARGET_VERSION_STATUS TARGET_UTC_CHECKIN TARGET_UTC_LAST_SAVED TARGET_CREATION_TIME Datatype VARCHAR2 (240) NUMBER VARCHAR2 (240) VARCHAR2 (2000) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (50) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) Description Folder name. For local shortcuts. Description of parent target. Target ID. UTC time when the target was last saved. the shortcut name displays. ID of parent target file.

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

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

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

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

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

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

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

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

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

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

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

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

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

and transformation. Informatica recommends using the fields in bold to join views. targets. target. Unconnected transformations are not included. Mapping and Mapplet Views 363 . Objects include sources. REP_MAPPING_UNCONN_PORTS MX View Column Name OBJECT_VERSION_NUMBER Datatype NUMBER Description Version number of the source. Folder name.Table 15-27. or transformation. Source object ID. target. Sequence ID for the mapping (primary key). Source object version number. Mapping version number. Name of the source object type. Source object type. Source object name. Target object version number. REP_MAPPING_PORT_CONN This view displays the port-level connections between the objects of a mapping. Table 15-28 lists port-level connection metadata in the REP_MAPPING_PORT_CONN view: Table 15-28. Target object ID. Target object instance ID. and mapplets. Target object field name. Informatica recommends using the fields in bold to join views. Source object instance ID. Mapping name. Source object field name. mapplet. Target object type name. Target object type such as port. transformations. Target object name. REP_MAPPING_PORT_CONN MX View Column Name SUBJECT_ID SUBJECT_AREA MAPPING_ID MAPPING_NAME MAPPING_VERSION_NUMBER FROM_OBJECT_ID FROM_OBJECT_TYPE FROM_OBJECT_TYPE_NAME FROM_OBJECT_NAME FROM_OBJECT_INSTANCE_ID FROM_OBJECT_FIELD_NAME FROM_OBJECT_VERSION_NUMBER TO_OBJECT_ID TO_OBJECT_TYPE TO_OBJECT_TYPE_NAME TO_OBJECT_NAME TO_OBJECT_INSTANCE_ID TO_OBJECT_FIELD_NAME TO_OBJECT_VERSION_NUMBER Datatype NUMBER VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER VARCHAR2 (240) NUMBER Description Folder ID.

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

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

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

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

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

Description of the attribute. Transformation field ID. REP_EIDGET_ATTR MX View Column Name WIDGET_ID WIDGET_TYPE MAPPING_ID INSTANCE_ID ATTR_ID ATTR_COMMENT ATTR_DATATYPE ATTR_NAME ATTR_TYPE OBJECT_TYPE_ID LINE_NO ATTR_VALUE PARTITION_ID SESSION_TASK_ID VERSION_NUMBER Datatype NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER NUMBER NUMBER VARCHAR2 (2000) NUMBER NUMBER NUMBER Description Transformation ID. Table 15-37 lists transformation field information in the REP_WIDGET_FIELD view: Table 15-37.REP_WIDGET_ATTR This view displays attribute details for transformations. REP_WIDGET_FIELD MX View Column Name WIDGET_ID FIELD_NAME FIELD_ID WGT_PREC Datatype NUMBER VARCHAR2 (240) NUMBER NUMBER Description Transformation ID. and sessions. and sessions. Table 15-36. instances. Attribute value. instances. Object type ID. Session task ID. REP_WIDGET_FIELD This view displays field level details for transformations. Used to break up long strings into multiple rows. mapping. Transformation Views 369 . Transformation field precision. Attribute type. Table 15-36 lists attribute details for transformations. Attribute data type Attribute name. or transformation) version number. Attribute ID. Partition ID. Instance ID. Object (session. Transformation field name. Transformation type. Mapping ID. Informatica recommends using the fields in bold to join views.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

-t sequence_generator_name 444 Chapter 16: Using pmrep and pmrepagent . The Sequence Generator transformation name. For more information on configuring Sequence Generator transformations. see “Sequence Generator Transformation” in the Transformation Guide. When you update values for a nonreusable Sequence Generator transformation. However. you cannot update values for instances of reusable Sequence Generator transformations or shortcuts to Sequence Generator transformations.Updating Sequence Generator Transformations (Updateseqgenvals) The Updateseqgenvals command updates one or more of the following properties for the specified Sequence Generator transformation: ♦ ♦ ♦ ♦ Start Value End Value Increment By Current Value You might want to update sequence values when you move a mapping from a development environment to a production environment. You can use Updateseqgenvals to update reusable and non-reusable Sequence Generator transformations. 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. you must include the mapping 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. You must connect to a repository to use this command. The mapping name.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You must provide the backup filename. See “Upgrading a Repository (Upgrade)” on page 490. switch to the Repository Server \bin directory and enter pmrepagent followed by the command name and its required options and arguments.pmrepagent Commands You can use the Repository Agent command line program. Table 16-67 describes pmrepagent commands: Table 16-67. Unregisters a plug-in module from the repository. See “Backing up a Repository (Backup)” on page 477. Deletes the repository tables from the database. To run pmrepagent commands. See “Restoring a Repository (Restore)” on page 485. See “Unregistering Plug-ins (Unregisterplugin)” on page 487. Backing up a Repository (Backup) The Backup command backs up a repository to the file specified with the -o option. Registers a new external module to the repository. Restores a Teradata repository from a repository backup file using Fastload. to perform repository functions such as restoring and deleting repositories. pmrepagent runs in command line mode only. Specify pmrepagent options and arguments the same way you specify pmrep options and arguments. See “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. Backup uses the following command syntax: backup -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m trusted_connection -c database_connect_string -o output_file_name -d description -f -b skip_workflow/session_log -j skip_deploy_group_history -q skip_MX_data pmrepagent Commands 477 . See “Deleting a Repository (Delete)” on page 481. Upgrades an existing repository to the latest version. See “Creating a Repository (Create)” on page 480. pmrepagent. See “Registering a Plug-in (Registerplugin)” on page 482. Use this command when the repository is not running. Creates repository tables in the database. Restores a repository from a repository backup file. pmrepagent Commands pmrepagent Command Backup Bulkrestore Create Delete Registerplugin Restore Unregisterplugin Upgrade Command Description Backs up a repository.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

TYPENAME > CDATA #REQUIRED <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. 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--> <!ELEMENT SPECIFICOBJECT EMPTY> <!ATTLIST SPECIFICOBJECT NAME DBDNAME CDATA CDATA #REQUIRED #IMPLIED #REQUIRED #REQUIRED #REQUIRED #REQUIRED> OBJECTTYPENAME CDATA FOLDERNAME CDATA REPOSITORYNAME CDATA RESOLUTION (REPLACE | REUSE | RENAME) Using the Object Import Control File 497 .) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name . 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.

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

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

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

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

) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .required for source object to identify uniquely--> <!--OBJECTTYPENAME Object type name--> <!--FOLDERNAME Folder which the object belongs to--> <!--REPOSITORYNAME Repository name that this object belongs to--> <!--RESOLUTION Resolution to apply for the object in case of conflict--> <SPECIFICOBJECT NAME="ADDRESS" DBDNAME="sol805" OBJECTTYPENAME="Source Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="ADDRESS1" DBDNAME="sol805" OBJECTTYPENAME="Target Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="MAP_MLET_ADD1" OBJECTTYPENAME="Mapplet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="MAP_ADD1" OBJECTTYPENAME="Mapping" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="R_AGG1" OBJECTTYPENAME="Aggregator" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_CUSTOM11_M" OBJECTTYPENAME="Custom Transformation" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_EXP11_M" OBJECTTYPENAME="Expression" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_FIL11_M" OBJECTTYPENAME="Filter" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> 502 Appendix A: Working with pmrep Files . typename etc.<TYPEOBJECT OBJECTTYPENAME="Expression" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Filter" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Aggregator" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Rank" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Normalizer" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Router" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Sequence" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Sorter" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="update strategy" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Custom Transformation" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Lookup Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Transaction control" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Stored Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="External Procedure" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Joiner" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="SessionConfig" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Email" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Command" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Scheduler" RESOLUTION="REUSE"/> <!--SPECIFICOBJECT allows a particular object(name.

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

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

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

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

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

508 Appendix A: Working with pmrep Files .

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

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

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

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 . and external loader connections in the Workflow Manager Edit database. FTP. FTP. 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.Table B-2. and external loader connections in the Workflow Manager Manage connection object permissions Register PowerCenter Servers and configure server variable directories Export objects Import objects Validate workflows and tasks Run Workflow Monitor None required None required None required Read.

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

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 .pmcmd Tasks To perform the following pmcmd tasks. Table B-4 lists the required privileges and permissions for pmcmd tasks: Table B-4. For example. you must have one of the listed sets of privileges and permissions. you can start a workflow using pmcmd if you have the following permissions and privileges: ♦ ♦ Workflow Operator privilege Execute permission on the folder Note: If you enabled enhanced security. you must have execute permission for connection objects associated with the session in addition to the privileges and permissions listed above.

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

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

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.

pmrep Tasks To perform the following pmrep tasks. you must have one of the listed sets of privileges and permissions. 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 . 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.

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

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 .

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

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

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

117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182. 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. 169 shortcuts 249 Workflow Manager uses 166 FTP connections during folder or deployment group copy 245 permissions and privileges 245 G global objects See Workflow Administration Guide global repositories code page 117. 249 copying between local repositories 250 copying global shortcuts 250 copying local shortcuts 249 copying or replacing 250 copying shortcuts 249 creating 171 deleting 173.dtd 267 privileges 266 sessions 272 shortcuts 270 steps for 285 versioned objects 273 external loader connections during folder or deployment group copy 245 permissions and privileges 245 external security module registering 484 unregistering 489 properties 168. 171 renaming 173 Repository Manager uses 166 shared 15.powrmart. 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 .

importing metadata 314 objects 280 ODBC data sources 33 registries 32 repository configurations 115 sources and target 314 importing objects code pages 266 CRCVALUE codes 267 dependent objects 270 DTD file 267 impcntl.dtd 496 Import Wizard 287 multiple objects 269 ObjectImport XML example 500 overview 264 parent objects 271 permissions 266 powrmart. 462 applying when importing 280 526 Index creating 219.dtd 267 privileges 266 resolving conflicts 281 sessions 272 shortcuts 274 steps for 287 validating objects 281 validating XML file 280 XML file 267 Informatica documentation xxxvi Webzine xxxviii Informix connect string syntax 405 interactive mode pmrep 406 in-use lock description (repository) 154 K KeepAliveTimeout setting for repository configuration 110 keywords searching for target definitions 34 L labels applying 221. 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 .

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

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

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

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

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

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

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

192 importing 274 local 182.description 9 descriptions inherited 184 exporting 270 global 182. 185 refreshing properties 194 renaming source qualifiers 196 tips 197 to folders 249 troubleshooting 198 updating 194 updating views 194 using 194 using queries to locate 230 Showconnectioninfo description 437 source databases view of analyzed or imported sources 344 view of fields 346 source definitions description 9 metadata extensions in 326 source file connections node viewing details 26 sources exporting to BI tools 314 importing from BI tools 314 source-target dependencies description 27 SQL scripts for creating/dropping MX views 336 starting Administration Console 52 repositories 71 static deployment groups definition 236 editing 239 statistics updating repository 447 status user statuses with LDAP 131 status bar progress indicator 22 stopping repositories 71 repositories with pmrep 437 stopRepository command pmrep 437 Super User privilege limiting 161 SwitchConnection description 438 T table owner name updating with pmrep 445 TablespaceName setting for repository configuration 107 target definitions description 9 keyword searches 34 metadata extensions in 326 view of associated transformations 357 view of joins between target tables 361 view of table-level transformations 356 targets exporting to BI tools 314 importing from BI tools 314 tasks metadata extensions in 326 Teradata connect string example 405 restoring repositories using pmrepagent 479 ThreadWaitTimeout setting for repository configuration 110 tips pmrep commands 492 pmrepagent commands 492 repository security 160 shortcuts 197 transformations description 9 metadata extensions in 326 troubleshooting exporting objects 296 importing objects 296 repository security 163 shortcuts 198 Truncatelog description 439 typical mode copying folders 244 534 Index . 187 overview 182 properties 184 referenced objects 183. 190.

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

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