Repository Guide

Informatica PowerCenter®
(Version 7.1.1)

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

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

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

i

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

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

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

ii

Table of Contents

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

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

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

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

iv

Table of Contents

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

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

Table of Contents

v

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

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

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

vi

Table of Contents

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

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

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

Table of Contents

vii

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

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

viii

Table of Contents

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

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

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

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

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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The repository client application associated with the connection. The name of the machine running the application. To view user connection details: 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. Viewing User Connections You can use the Repository Manager or the Administration Console to view connection details for users and applications connected to the repository. The time the user connected to the repository. Table 3-5 describes the repository user connection details: Table 3-5. 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.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. Repository User Connection Details Property User Connection ID Application Hostname Host Address Login Time Last Active Time Remote Host Port Description The user name associated with the connection. Viewing User Connections and Locks 79 . The time of the last metadata transaction between the repository client application and the repository. The identification number assigned to the repository connection.

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

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

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

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

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

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

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

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

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

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

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

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

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

88

Chapter 3: Managing the Repository

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

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

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

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

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

Registering and Unregistering LDAP Security Modules

89

The Repository Server lists the available plug-ins.

4.

Select the Authentication Module, and choose Action-Register.

90

Chapter 3: Managing the Repository

The Register Security Module dialog box displays.

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

5.

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

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

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

3.

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

4.

Enter LDAP server options.

92

Chapter 3: Managing the Repository

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

Principal User Name Principal User Password 5.

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

Registering and Unregistering LDAP Security Modules

93

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

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

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

94

Chapter 3: Managing the Repository

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

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

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

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

3.

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

Registering and Unregistering LDAP Security Modules

95

The Unregister Package dialog box displays.

4.

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

96

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

♦ ♦

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

98

Chapter 3: Managing the Repository

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

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

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

. TRACE : REP_51047 [Fri Jul 16 10:46:17 2004] : (2280|1980) Sending message of size 278 bytes.1. . . port 2706. 102 Chapter 3: Managing the Repository . 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.72.com (10.173). ERROR : CNX_53021 [Wed Jul 14 13:20:54 2004] : (2588|2336) Received an invalid request.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Locking occurs at the root directory of the business component tree. 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. 156 Chapter 5: Repository Security . with General Ledger and Accounts Receivable as subdirectories. The Repository Server releases a lock when you choose Repository-Save. For example. if Finance is the root directory of your tree. For details.

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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

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

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

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

4.

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

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

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

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

6.

Choose Repository-Save.

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

Creating a Local Shortcut

189

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

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

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

190

Chapter 7: Local and Global Shortcuts

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

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

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

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

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

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

2.

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

3. 4.

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

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

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

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

6.

Choose Repository-Save.

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

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

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

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

3.

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

4. 5.

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

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

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

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

7.

Choose Repository-Save.

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

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

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

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

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

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

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

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

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

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

Creating a Global Shortcut

193

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

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

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

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

194

Chapter 7: Local and Global Shortcuts

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

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

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

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

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

Working with Shortcuts

195

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

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

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

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

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

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

Tips

197

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

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

♦ ♦ ♦

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

198

Chapter 7: Local and Global Shortcuts

Chapter 8

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

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

199

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You can check in objects from the Designer. For more information on performing a check in. Workflow Manager. or Repository Manager. 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.You must save an object before you can check it in.

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

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

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

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

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

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

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

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

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

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

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

♦ ♦

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

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

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

224

Chapter 9: Grouping Versioned Objects

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

Specify query conditions.

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

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

Working with Object Queries

225

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

Add logical operators. Add multiple query conditions.

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

4

3

226

Chapter 9: Grouping Versioned Objects

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

Check-in time

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

Date/time Numeric

Comments

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

String

Deployment Dispatch History

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

Date/time Numeric

Deployment Receive History

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

Date/time Numeric

Working with Object Queries

227

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

Include Children

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

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

Include Children and Parents

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

Where (Value 1) depends on (Value 2)

Include Parents

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

Where (Value 1) depends on (Value 2)

Include Primary/ Foreign Key Dependencies

Displays primary key-foreign key dependencies.

N/A

228

Chapter 9: Grouping Versioned Objects

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

Last Saved Time

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

Latest Status

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

Checked-out Latest checked-in Older

Metadata Extension

Is Equal To Is Not Equal To

User-defined metadata domain Any vendor-defined metadata extensions

Object Name

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

String

Working with Object Queries

229

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

Object Used Status

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

Is Equal To

Shortcut status

Is Equal To

Is Not Shortcut Is Shortcut

Reusable Status User

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

Non-reusable Reusable Users in specified repository

Valid Status Version Status

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

Invalid Valid Deleted Not deleted

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

230

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

Working with Object Queries

231

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

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

232

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

objects in the repository.

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

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

Working with Object Queries

233

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

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

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

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

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

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

234

Chapter 9: Grouping Versioned Objects

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 . Select source definitions and target definitions for Value 1 and select mapping for Value 2. To search for parent and child dependencies. To include reusable and non-reusable dependencies. Mapping_deploy. choose to include children and parent dependencies.

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

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

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

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

If you want to find the latest versions of objects in a dynamic deployment group. you must create all mappings in the group with labels. the Repository Agent runs the query at the time of deployment. but did not apply a label to the latest version of the object. the group will not deploy. For more information on managing versioned objects. For more information on deploying groups of objects.Working with Dynamic Deployment Groups You might want to create a dynamic deployment group if you expect the set of deployment objects to change frequently. For example. If the dynamic deployment group contains a non-reusable object in an unlabeled mapping. Using Queries with Dynamic Deployment Groups When you associate an object query with the deployment group. You can associate an object query with a deployment group when you edit or create a deployment group. 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 . 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 can run the dynamic deployment group query multiple times and add new objects to the group each time you run the query. you might use a dynamic deployment group if you develop multiple objects for deployment on different schedules. see “Copying Folders and Deployment Groups” on page 241.

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

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

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

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

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

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

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

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

The wizard does not establish shortcuts to an outdated shared folder. see “Working with Version Properties” on page 203. the wizard does not allow you to copy a folder when the folder. and yyyy=year). If you copy the folder from the global repository to a local repository in the same domain. are being saved. Before you copy a folder. the wizard deletes all shortcuts and marks all affected mappings invalid. 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. you must copy shared folders before copying the folder. In typical mode. If you are replacing a folder in a repository that is enabled for versioning. verify that no objects in the target folder are checked out. if you edit the original shared folder after you copy it to the target repository. If shared folders exist in the target repository. the wizard asks you to copy it again. Therefore. If you a replacing a folder in a target repository enabled for versioning. For details on locking. to copy shortcuts correctly.Naming When you copy a folder. see “Viewing Checked Out Objects” on page 211. and you choose not to replace it. local shortcuts become global shortcuts. Copying or Replacing a Folder 249 . Likewise. you cannot save objects in a folder as the wizard copies the folder. Shortcuts to folders in the same repository are known as local shortcuts. If you do not copy the shared folders before copying the folder. For more information on searching for checkouts in the repository. For more information on changing the status of an object. Therefore. you must also verify that no objects in the target folder are checked out. In the advanced mode. the wizard appends the date to the folder name. 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. see “Repository Security” on page 125. Locking and Checkouts To protect the integrity of the repository. dd=days. If the folder name already exists in the repository. the wizard verifies whether the copy is current. as follows: <folder_name>_mm/dd/yyyy (where mm=months. Shortcuts to the global repository are called global shortcuts. view object locks to verify that the folder is not in use. you can compare the folders to see which folder is most recent. you can keep shortcuts intact by copying the necessary local shared folders to the target repository before copying the folder. the wizard names the copy after the folder. or 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. Copying Within a Repository When you copy a folder within the same repository. The Copy Wizard will either reestablish global shortcuts as a local shortcuts. or establish the copied shortcuts as global shortcuts. When you copy a folder from a local repository to its global repository. you can also choose to establish local shortcuts to the shared folder in the local repository. you establish global shortcuts to the shared folder in the global repository. the wizard uses the folder name for the copied folder. the wizard recreates global shortcuts to the global repository. it asks you to rename the folder. Copying From Local Repositories When you copy a folder from a local repository to another repository. If you choose to copy the folder in typical mode.For example. The wizard reestablishes all shortcuts. You might want to ask all users to exit the repository Also. You might want to rename existing shared folders before performing the copy. If you want to copy the folder again. If you copy a folder that contains global shortcuts between domains. and the copied folder continues to use the same connection and server information. you might want to rename the existing folder in the target repository. If it does not. using a naming convention that clearly defines the existing folder. If you copy the folder in advanced mode. When you copy a folder from a global repository to a local repository within the domain. use the Repository Manager to verify no users are accessing objects in the folder. If it does. 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. Then copy the non-shared folder. the wizard asks you to rename the folder. the global shortcuts become local shortcuts. If you have edited objects in any local shared folders used by the folder. First copy the shared folder into the local repository. local shortcuts become global shortcuts. you must copy those shared folders into the target repository before copying the folder. the wizard verifies whether a folder of the same name exists in the target repository. you want to copy a shared folder and a non-shared folder with shortcuts from a global repository to a local repository. copy dependent 250 Chapter 10: Copying Folders and Deployment Groups . Steps for Copying or Replacing a Folder Before you copy a folder.

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

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

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

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

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

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

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

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

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

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

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

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

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

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

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

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

The Metadata Import Wizard appears. 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. To import metadata: 1. Steps for Importing Metadata 319 . and choose Repository-Import Metadata. You can click More Info to read about the tool requirements. In the Repository Manager. Choose the target tool from which you want to import the object. 2. The wizard uses the file name as the source database name for each object you import.

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Attribute value. Session version number if task attribute is overridden at session level. Task type name. Task attribute name. Task attribute ID. Workflow version number if task attribute is overridden at workflow level. 386 Chapter 15: Using Metadata Exchange (MX) Views . Task ID. Used for storing multiple lines of attribute values. 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. REP_TASK_ATTR This view displays the attribute values and overridden values for session and workflow tasks. Informatica recommends using the fields in bold to join views.Table 15-56. Informatica recommends using the fields in bold to join views. Attribute value. Task instance ID. Table 15-57 lists attribute information in the REP_TASK_ATTR view: Table 15-57. Task type. Group ID. Line number of attribute values. Session 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. Number of successfully read source rows. Location of the reject file. which might contain one or many target tables. Run status code. Number of failed source rows. and Task Views 387 . Number of successfully loaded target rows. Worklet. Table 15-58 lists session log information in the REP_SESS_LOG view: Table 15-58. Session instance name. Time completed. Version number of the task. 1 = Suceeded 2 = Disabled 3 = Failed 4 = Stopped 5 = Aborted 6 = Running 7 = Suspending 8 = Suspended 9 = Stopping 10 = Aborting 11 = Waiting 12 = Scheduled 13 = Unscheduled 14 = Unknown 15 = Terminated Last error code. Last error message. First error code. This view supplies the status of the last session. 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. Workflow version number. Session log file name. Actual time session started. Number of failed target rows.REP_SESS_LOG This view provides log information about sessions. Session ID. Folder ID.

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

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

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

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

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

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

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

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

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

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

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

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

Label description.Table 15-75. 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. Informatica recommends using the fields in bold to join views. Time when label was applied to the object.

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

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

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

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

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.

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

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

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

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

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

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

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

412

Chapter 16: Using pmrep and pmrepagent

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

StopRepository SwitchConnection Truncatelog Unregister UpdateConnection Updateemailaddr Updateseqgenvals

Updateserver Updatesrcprefix Updatesrvvar UpdateStatistics Updatetargprefix

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

pmrep Repository Commands

413

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

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

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

414

Chapter 16: Using pmrep and pmrepagent

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

-A

repserver_password_ environment_variable repository_name database_type database_user_name

-r -t -u

-m -p

Optional Required/ Optional

n/a database_password

-P

Required/ Optional

database_password_ environment_variable

-c

Required

database_connect_string

-d

Optional

code_page

pmrep Repository Commands

415

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

-l

Optional

license_file_name

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

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

-b -j -q

Optional Optional Optional

skip_workflow/ session_logs skip_deploy_group _history skip_MX_data

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

416

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

-P

password_environm ent_variable connect_string

-c

-l -r

Required Optional

code_page rollback_segment

pmrep Repository Commands

417

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

-b -v -d -t

Optional Optional Optional Optional

database_name server_name domain_name trusted_connection

-x

Optional

n/a

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

418

Chapter 16: Using pmrep and pmrepagent

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

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

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

pmrep Repository Commands

419

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

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

420

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

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

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

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

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

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

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

-r

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

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

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

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

422

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

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

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

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

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

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

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

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

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

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

Running Script Files (Run) The Run command takes a file containing multiple pmrep commands and runs those commands sequentially. The Run command uses the following command syntax: run -f script_file_name -o output_file_name -e echo_commands -s stop_at_first_error Table 16-24 lists pmrep Run options and arguments: Table 16-24. The commands are echoed back to the script. Use the -a or -A option. The run might fail if the Repository Server cannot open the script file or output file. 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. -r The command returns “removerepository successfully completed” or “failed to execute removerepository” message. -e -s Optional Optional echo_commands stop_at_first_error The command returns “run successfully completed” or returns “run failed” message. The name of the output file. The removal might fail for the following reasons: ♦ ♦ The repository name does not exist. 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. All repository users can run script files. but not both.Table 16-23. Stops the running of the script after a command returns an error. 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.

When you use the StopRepository command. Stopping a Repository (StopRepository) The StopRepository command stops the repository you specify. a message indicating failure to execute the command is given. pmrep does not keep connection information in command line mode. the pmrep keeps the connection information in memory until you exit the repository or connect to a different repository. the repository that you last connected to stops. pmrep connects to the Repository Server and stops the Repository Agent. the named repository stops. see “Connecting to a Repository (Connect)” on page 410. Otherwise. The ShowConnectioninfo command does not connect to the repository. However. You must be connected to a repository to use this command. For more information about connections in command line mode and interactive mode. ShowConnectioninfo requires no parameters. and -r options. port. pmrep Repository Commands 437 . 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.Showing Connection Information (ShowConnectioninfo) The ShowConnectioninfo command returns the repository name. and user information for the current connection. StopRepository stops the repository you last connected to. When you use the ShowConnectioninfo command in command line mode. server. 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. -o. When you connect to a repository in interactive mode. For example. if you do not specify a 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. When you use this option. When you use this option. but not both. For example. In a session. you must also use the -h and -o options. Use the -a or -A option. The hostname of the Repository Server that manages the repository to stop. When you use SwitchConnection. When you use this option. you must also use the -h and -r options. 438 Chapter 16: Using pmrep and pmrepagent . each called ITEMS. StopRepository Option and Argument (pmrep) Option -a Required/ Optional Required/ Optional Required/ Optional Argument Name repserver_password Argument Description The password you use to administer the Repository Server that manages the repository. The name of the repository to stop. -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. you specified the name ITEMS for a relational source connection instead of Relational:ITEMS. Use the -a or -A option. but not both. The password environment variable you use to administer the Repository Server that manages the repository. When you use SwitchConnection to replace the relational connection ITEMS with another relational connection. you must also use the -o and -r options. You must be connected to a repository to use this command. you have a relational and an application source. the Repository Server replaces the relational connection. 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 Repository Server port number.

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

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

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

The user name used for authentication when you connect to the relational database.Table 16-29 lists pmrep UpdateConnection options and arguments: Table 16-29. see Table 16-1 on page 405. Use the -p or -P option. Enter “yes” or “no” for attributes you enable through a checkbox. For a list of valid database types. the command does not update the email addresses. -P new_database_password_ environment_variable -c Required new_database_connection _string attribute_name new_attribute_value -a -v Optional Optional Updating the Notification Email Addresses (Updateemailaddr) The Updateemailaddr command updates the session notification email addresses associated with the Email tasks assigned to the session. The new attribute value of the connection. Updateemailaddr uses the following command syntax: updateemailaddr -d folder_name -s session_name -u success_email_address f failure_email_address 442 Chapter 16: Using pmrep and pmrepagent . You can update the email notification addresses only for a non-reusable session with a unique name in the folder. see Table 16-9 on page 418. The connect string the PowerCenter Server uses to connect to the relational database. but not both. 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. The name of the attribute. The database connection name. You can specify different addresses to receive either success or failure notifications. Use the -p or -P option. UpdateConnection Options and Arguments (pmrep) Option -t -d -u -p Required/ Optional Required Required Required Required/ Optional Required/ Optional Argument Name database_type database_connection_na me new_user_name new_database_password Argument Description The type of relational connection. For a list of native connect strings. This command requires you to connect to a repository. but not both. The password used for authentication when you connect to the relational database.

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

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. -t sequence_generator_name 444 Chapter 16: Using pmrep and pmrepagent . You can use Updateseqgenvals to update reusable and non-reusable Sequence Generator transformations. 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. To update sequence values. you must have one of the following sets of privileges and permissions: ♦ ♦ Use Designer privilege with write permission on the folder Super User privilege Updateseqgenvals uses the following command syntax: updateseqgenvals -f folder_name -m mapping_name -t sequence_generator_name -s start_value -e end_value -i increment_by -c current_value Table 16-32 lists pmrep Updateseqgenvals options and arguments: Table 16-32. The Sequence Generator transformation name. You must connect to a repository to use this command.Updating Sequence Generator Transformations (Updateseqgenvals) The Updateseqgenvals command updates one or more of the following properties for the specified Sequence Generator transformation: ♦ ♦ ♦ ♦ Start Value End Value Increment By Current Value You might want to update sequence values when you move a mapping from a development environment to a production environment. you must include the mapping name. The mapping name. see “Sequence Generator Transformation” in the Transformation Guide. For more information on configuring Sequence Generator transformations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Use the -x or -X option. The control file is required. The repository you are deploying the group to. The login user name for the target repository. you must have the following privileges and permissions: ♦ ♦ ♦ Administer Repository Manager privilege Read permission on the original folders Read and execute permissions on the deployment group DeployDeploymentGroup uses the following command syntax: DeployDeploymentGroup -p deployment_group_name -c control_file_name -r target_repository_name -u target_repository_user_name -x target_repository_user_password -X target_repository_password_environment_variable -h target_repository_server_host_name -n target_repository_server_port_number -l log_file_name Table 16-61 lists pmrep DeployDeploymentGroup options and arguments: Table 16-61. 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. 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.To use this command. The host name of the Repository Server managing the target repository. The login password for the target repository. The login password environment variable for the target repository. but not both. The name of the XML file containing the Copy Wizard specifications. Not required if you copy the deployment group to the same repository. -r -u Required Required/ Optional Required/ Optional target_repository_name target_repository_user_name -x target_repository_user_passwo rd -X Required/ Optional target_repository_password_en vironment_variable -h Required/ Optional target_repository_server_host_ name 468 Chapter 16: Using pmrep and pmrepagent . For more details about the control file. For more information on deploying a deployment group. To copy a deployment group. Not required if you copy the deployment group to the same repository.dtd file. you must create a control file with all the specifications that the Copy Wizard requires. Use the -x or -X option. Not required if you copy the deployment group to the same repository. see “Copying a Deployment Group” on page 254. but not both. The control file is an XML file defined by the depcntl. For more information on using the control file.

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

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

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

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

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

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

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

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

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

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

The name of the Teradata database server. The repository database password environment variable. The name of the repository backup file. If you do not specify a path. The port number of the Repository Server that manages the repository. but not both. You can specify any file name and path local to the Repository Server. Bulkrestore Options and Arguments (pmrepagent) Option -r -t -u -p -P -c Required/ Optional Required Required Required Required/ Optional Required/ Optional Required Argument Name repository_name database_type database_user_name database_password database_password_environ ment_variable database_connect_string Argument Description The name of the repository you want to restore. The repository code page. The repository database password. The host name of the Repository Server that manages the repository.Restoring Teradata Repositories using Fastload (Bulkrestore) The pmrepagent Bulkrestore command restores Teradata repositories using Fastload. but not both. see Table 16-1 on page 405. Use the -p or -P option. The repository database user name. This option has no argument. Use the -p or -P option. For a list of connect string syntax. The Bulkrestore command can be faster than the Restore command when the repository backup file is greater than 100 MB. Enter “fastload” for Teradata. the Repository Server looks for the file in the Repository Server backup directory. The connect string the Repository Agent uses to connect to the repository database. Bulkrestore uses the following command syntax: bulkrestore -r repository_name -t database_type -u database_user_name -p database_password -P database_password_environment_variable -c database_connect_string -d codepage -h host_name -o port_number -g -i backup_file_name -e external_loader_type -s server_name -a license_file_name -y enable_object_versioning -b skip_workflow/ session_log -j skip_deploy_group_history -q skip_MX_data Table 16-69 lists pmrepagent Bulkrestore options and arguments: Table 16-69. Use this option if you want to promote the repository to a global repository. -d -h -o -g -i Optional Required Required Optional Required codepage host_name port_number n/a backup_file_name -e -s Required Required external_loader_type server_name pmrepagent Commands 479 . Enter “Teradata” to restore to a Teradata 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 connect string the Repository Agent uses to connect to the repository database. Before you can create a repository. see “Creating a Repository” on page 116. Use the -p or -P option. The repository database password environment variable. For a list of connect string syntax. Creating a Repository (Create) The pmrepagent Create command creates a repository in the database. Enables object versioning. Use a trusted connection to connect to the database. Valid for Microsoft SQL Server only. Skips tables related to MX data during backup. but not both. Use the -p or -P option. Skips tables related to workflow and session logs during backup. Not required if you are using option -m.Table 16-69. The type of database the repository resides on. 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. Not required if you are using option -m. you must create and configure the database to contain the repository. The repository database user name. Skips deployment group history during backup. but not both. Create Options and Arguments (pmrepagent) Option -r -t -u -p Required/ Optional Required Required Required Required/ Optional Required/ Optional Optional Required Argument Name repository_name database_type database_user_name database_password Argument Description The name of the repository you want to create. The repository database password. -P database_password_environme nt_variable n/a database_connect_string -m -c 480 Chapter 16: Using pmrep and pmrepagent . For more information on creating repositories.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

but you should include its location in the input XML 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?. The deployment control file installs with the PowerCenter Client. 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 . you can use a control file to answer questions that you see when you deploy objects using the Copy Wizard. <!ELEMENT DEPLOYPARAMS (DEPLOYFOLDER?.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.dtd file.

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

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

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

508 Appendix A: Working with pmrep Files .

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

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

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

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

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

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

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

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

export. 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. 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 . groups.Table B-5. or remove the registry Manage users. and privileges Mass update Purge (versioning) Receive user and group notifications Recover Remove Label References Run Query Use Repository Manager Browse Repository Administer Repository Super User Administer Repository Super User Use Repository Manager Use Repository Manager Browse Repository Manager Folder Permission None required N/A N/A N/A Write Folder owner and read permission Read N/A Read on the original folder.

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

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

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

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

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

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

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

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

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

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

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

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

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

117.Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. troubleshooting 163 starting 71 Index 531 . 158 removerepsitory description 435 removing repositories 29 users 141 replacing folders 248. 75. 160 security log file 153 security. 192 connecting to 30 connecting to multiple 31 connecting with pmrep 410 connectivity 4 copying 62 copying folders between local 250 creating 116 creating relational connections 417 creating users 134 database definition views 338 default privileges 143 deleting 64 disabling 73. 250 reports metadata 335 repositories adding 29 adding metadata 9 administration overview 11 architecture 3 avoiding shared accounts 160 backing up 66 backing up with pmrepagent 477 changing a code page 117 checking status 54 code pages 51. 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. 50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. overview 142 troubleshooting 163 Workflow Manager tasks 511 product license keys overview 119 promoting repositories 117 purging description 216 objects 216 Q queries See also object queries executing 470 R recovering deleted objects 215 register description 434 registering a user 457 plug-in using pmrepagent 482 security module using pmrepagent 484 Registerplugin description 482 Registeruser description 457 registry exporting 32 importing 32 releasing repository locks 83. overview 155 overview 2. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126.

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

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 .

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

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

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