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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. When you click the hyperlink.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

88

Chapter 3: Managing the Repository

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

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

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

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

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

Registering and Unregistering LDAP Security Modules

89

The Repository Server lists the available plug-ins.

4.

Select the Authentication Module, and choose Action-Register.

90

Chapter 3: Managing the Repository

The Register Security Module dialog box displays.

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

5.

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

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

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

3.

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

4.

Enter LDAP server options.

92

Chapter 3: Managing the Repository

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

Principal User Name Principal User Password 5.

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

Registering and Unregistering LDAP Security Modules

93

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

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

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

94

Chapter 3: Managing the Repository

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

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

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

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

3.

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

Registering and Unregistering LDAP Security Modules

95

The Unregister Package dialog box displays.

4.

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

96

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

♦ ♦

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

98

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

In a repository. For example. You can create a folder for each repository user. mappings. Overview 167 . 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. and reusable transformations) that you create through the Designer. user. or type of metadata. subject area. schemas. You might create a different folder for each type of metadata (source definitions. if you want to organize accounting data. designed to store work for that user only. If users work on separate projects. you might create folders for each development project. target definitions. For example: ♦ You might create a single folder for each type of data. ♦ ♦ 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.

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

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

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

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

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

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

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

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

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

you can view the current status of the object. and comments associated with the label. Object Status Properties On the Object Status tab. Labels Properties For more information on creating and applying labels. the time the label was applied. 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. For each label.Labels Properties On the Labels tab. you can view all labels applied to the object. see “Working with Labels” on page 219. Working with Version Properties 205 . you can also view the name of the user who applied the label.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

♦ ♦

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

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

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

224

Chapter 9: Grouping Versioned Objects

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

Specify query conditions.

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

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

Working with Object Queries

225

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

Add logical operators. Add multiple query conditions.

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

4

3

226

Chapter 9: Grouping Versioned Objects

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

Check-in time

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

Date/time Numeric

Comments

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

String

Deployment Dispatch History

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

Date/time Numeric

Deployment Receive History

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

Date/time Numeric

Working with Object Queries

227

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

Include Children

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

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

Include Children and Parents

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

Where (Value 1) depends on (Value 2)

Include Parents

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

Where (Value 1) depends on (Value 2)

Include Primary/ Foreign Key Dependencies

Displays primary key-foreign key dependencies.

N/A

228

Chapter 9: Grouping Versioned Objects

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

Last Saved Time

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

Latest Status

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

Checked-out Latest checked-in Older

Metadata Extension

Is Equal To Is Not Equal To

User-defined metadata domain Any vendor-defined metadata extensions

Object Name

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

String

Working with Object Queries

229

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

Object Used Status

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

Is Equal To

Shortcut status

Is Equal To

Is Not Shortcut Is Shortcut

Reusable Status User

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

Non-reusable Reusable Users in specified repository

Valid Status Version Status

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

Invalid Valid Deleted Not deleted

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

230

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

Working with Object Queries

231

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

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

232

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

objects in the repository.

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

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

Working with Object Queries

233

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

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

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

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

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

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

234

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Tip: You can create a new folder in the destination repository by clicking Create Folder. Steps for Importing Objects 289 . Click Next. 8. The Folder Selection dialog box appears. Select a folder in the destination repository and click OK. 7. 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. or when you import a shortcut object in the Designer. You must select a different folder for each folder listed in the Import Wizard.6. Click the Open button for a folder listed in the Import Wizard. You can match folders listed in the XML file to folders in the destination repository.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

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

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

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

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

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

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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. To delete a reusable metadata extension. When you delete a reusable metadata extension for a repository object. and click Delete. 332 Chapter 14: Metadata Extensions . you remove the metadata extension and its values from the properties of all objects of that type.Deleting Reusable Metadata Extensions You can delete user-defined.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Session ID. Line number of attribute values. Attribute value. Task instance ID. Task attribute name. Group ID. Informatica recommends using the fields in bold to join views. 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. Used for storing multiple lines of attribute values. Workflow version number if task attribute is overridden at workflow level. Task ID.Table 15-56. Task type. Table 15-57 lists attribute information in the REP_TASK_ATTR view: Table 15-57. Task attribute ID. REP_SESS_CONFIG_PARM MX View Column ATTR_NAME ATTR_VALUE Datatype VARCHAR2 (240) VARCHAR2 (2000) Description Session configuration attribute name. Task type name. Session version number if task attribute is overridden at session level. 386 Chapter 15: Using Metadata Exchange (MX) Views . Attribute value. 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-58 lists session log information in the REP_SESS_LOG view: Table 15-58. and Task Views 387 . Number of successfully read source rows. Worklet. First error code. Run status code. Actual time session started. 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. Session instance name. Version number of the task. which might contain one or many target tables. 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. Time completed. Last error message. This view supplies the status of the last session.REP_SESS_LOG This view provides log information about sessions. 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. Folder ID. Number of failed source rows. Number of failed target rows. Location of the reject file. Number of successfully loaded target rows. Session ID.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. Native Connect String Syntax Database IBM DB2 Informix Microsoft SQL Server Oracle Sybase Teradata* Connect String Syntax dbname dbname@servername servername@dbname dbname.world sambrown@mydatabase TeradataODBC TeradataODBC@mydatabase TeradataODBC@jsmith *Use Teradata ODBC drivers to connect to source and target databases.Table 16-1 lists the native connect string syntax for each supported database when you create or update connections: Table 16-1. Overview 405 .

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

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

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

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

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

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

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

List reusable and non-reusable transformations with latest or checked out version in a folder. excluding instances of reusable worklets. Query. The command lists the latest versions or checked out versions of objects. including shortcuts and excluding instances of reusable transformations. Mapping. Source. 424 Chapter 16: Using pmrep and pmrepagent . Sessionconfig. List reusable and non-reusable sessions with latest or checked out version in a folder. Transformation. List the session configurations with latest or checked out version in a folder. including shortcuts but excluding target instances. List reusable and non-reusable worklets with latest version or checked out version in a folder. including shortcuts but excluding instances of reusable mapplets. Session. List labels in the repository. The deploymentgroup.You can use the object_type option to define the objects you want to list. Task. List reusable and non-reusable schedulers with latest or checked out version in a folder. folder. but excluding objects according to the following rules for each object type: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Deploymentgroup. label. Target. Folder. Workflow. including shortcuts but excluding instances of reusable mapplets. including shortcuts. List the workflows with latest version or checked out version in a folder. excluding instances of reusable sessions. including shortcuts but excluding source instances. List folders in the repository Label. List queries in the repository. List reusable and non-reusable tasks with latest or checked out version in a folder. List mapplets with latest or checked out version in a folder. List deployment groups in the repository. Worklet. and query object types are not associated with folders. List mappings with latest or checked out version in a folder. All other object types require the -f option. Scheduler. List targets with latest or checked out version in a folder. ♦ ♦ ListObjects uses the following command syntax: listobjects -o object_type -t object_subtype -f folder_name -c column_separator -r end_of_record_separator -l end-of-listing_indicator -b verbose Do not use the -f option if the object type you list is not associated with a folder. Mapplet. List sources with latest or checked out version in a folder.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<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.dtd. e. This should conforming to the element name in powermart. TARGET and etc.--> <TYPEFILTER TYPENAME="SOURCE"/> <TYPEFILTER TYPENAME="TARGET"/> <TYPEFILTER TYPENAME="MAPPLET"/> <TYPEFILTER TYPENAME="MAPPING"/> <TYPEFILTER TYPENAME="TRANSFORMATION"/> <TYPEFILTER TYPENAME="SHORTCUT"/> <TYPEFILTER TYPENAME="CONFIG"/> <TYPEFILTER TYPENAME="TASK"/> <TYPEFILTER TYPENAME="SESSION"/> <TYPEFILTER TYPENAME="SCHEDULER"/> <TYPEFILTER TYPENAME="WORKFLOW"/> <TYPEFILTER TYPENAME="SCHEDULER"/> <TYPEFILTER TYPENAME="WORKLET"/> <!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. SOURCE.g. The combination of specified child nodes can be supplied --> <RESOLVECONFLICT> <!--QUERYOBJECT allows objects result from a query to apply replace/reuse upon conflict --> <QUERYOBJECT QUERYNAME="Q_MAPS_CREATED_1027" RESOLUTION="RENAME"/> <!--LABELOBJECT allows objects in the target with label name to apply replace/reuse upon conflict --> <LABELOBJECT LABELNAME="LABEL_DT1027" RESOLUTION="REPLACE"/> <!--TYPEOBJECT allows objects of certain type to apply replace/reuse upon conflict--> <TYPEOBJECT OBJECTTYPENAME="WORKFLOW" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="WORKLET" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="SESSION" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="MAPPING" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="MAPPLET" RESOLUTION="REPLACE"/> <TYPEOBJECT OBJECTTYPENAME="Source definition" RESOLUTION="REUSE"/> <TYPEOBJECT OBJECTTYPENAME="Target definition" RESOLUTION="REUSE"/> Using the Object Import Control File 501 .

) to apply replace/reuse upon conflict --> <!--NAME Object name--> <!--EXTRANAME Source DBD name .required for source object to identify uniquely--> <!--OBJECTTYPENAME Object type name--> <!--FOLDERNAME Folder which the object belongs to--> <!--REPOSITORYNAME Repository name that this object belongs to--> <!--RESOLUTION Resolution to apply for the object in case of conflict--> <SPECIFICOBJECT NAME="ADDRESS" DBDNAME="sol805" OBJECTTYPENAME="Source Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="ADDRESS1" DBDNAME="sol805" OBJECTTYPENAME="Target Definition" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REUSE"/> <SPECIFICOBJECT NAME="MAP_MLET_ADD1" OBJECTTYPENAME="Mapplet" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="MAP_ADD1" OBJECTTYPENAME="Mapping" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="REPLACE"/> <SPECIFICOBJECT NAME="R_AGG1" OBJECTTYPENAME="Aggregator" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> <SPECIFICOBJECT NAME="R_CUSTOM11_M" OBJECTTYPENAME="Custom Transformation" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_EXP11_M" OBJECTTYPENAME="Expression" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/ > <SPECIFICOBJECT NAME="R_FIL11_M" OBJECTTYPENAME="Filter" FOLDERNAME="PMREP_CHECKED_OUT" REPOSITORYNAME="PMREP_AUTOMATION_1027" RESOLUTION="RENAME"/> 502 Appendix A: Working with pmrep Files .<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 .

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

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

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

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

508 Appendix A: Working with pmrep Files .

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

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

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

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 . FTP.Table B-2. and external loader connections in the Workflow Manager Edit database. 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.

Super User privilege Table B-3 lists the required privileges and permissions for Workflow Monitor tasks: Table B-3. 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. you must have one of the listed sets of privileges and permissions.Workflow Monitor Tasks To perform the following Workflow Monitor tasks. 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 . For example. Use Workflow Manager privilege with read and execute permissions for the folder containing the workflow.

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

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

For example. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Add to deployment group Apply label Change object version comments Change status of an object Change your password Check in Check in/undo check out for other users Check out/undo check out Connect to the repository using the Repository Manager Copy a folder to a different repository Repository Privilege Use Repository Manager Use Repository Manager Use Repository Manager or be check-out owner Use Repository Manager Browse Repository Use Repository Manager Administer Repository Use Repository Manager Browse Repository Browse Repository on the originating repository and Administer Repository on the destination repository Administer Repository Folder Permission Read Read Write Write None required Write Write Write None required Read permission on the original folder None required None required None required None required None required None required Read Other Permission Write on deployment group Execute on label Copy a folder within the same repository Read permission on the original folder Read permission on the original folder Read on the original folders Write on target Read Browse Repository None required Copy global object Use Repository Manager 516 Appendix B: Permissions and Privileges by Task .Repository Manager Tasks To perform the following Repository Manager tasks. as the folder owner with read permission on the folder Administer Repository privilege with read permission on the folder Super User privilege Table B-5 lists the required permissions and privileges for Repository Manager tasks: Table B-5. you 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. groups. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task Create a folder Create or edit deployment group Create or edit label Create or edit query Delete (versioning) Delete a folder Repository Privilege Administer Repository Administer Repository Administer Repository Browse Repository Use Repository Manager Browse Repository Administer Repository Delete from Deployment Group Deploy Edit folder Use Repository Manager Administer Repository Browse Repository Administer Repository Edit folder properties Browse Repository Administer Repository Export objects Freeze folder Use Repository Manager Browse Repository Administer Repository Import objects Import. 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. or remove the registry Manage users.Table B-5. Folder owner and read permission Read Folder owner and read permission Read Read Folder owner and read permission Read Read/Write None required None required Write Write None required Write N/A N/A Other Permission None required Edit: Write on deployment group Edit: Write on label Write on query None required None required None required Write on deployment group Read and execute on deployment group None required None required None required None required None required None required None required None required None required None required None required None required None required None required None required Read on query Repository Manager Tasks 517 .

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

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

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

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

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

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

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

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. 117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182. 171 renaming 173 Repository Manager uses 166 shared 15. 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 .powrmart. 168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245. 192 creating 14 promoting 112. 169 shortcuts 249 Workflow Manager uses 166 FTP connections during folder or deployment group copy 245 permissions and privileges 245 G global objects See Workflow Administration Guide global repositories code page 117. 249 environment 192 repository usernames 193 server username 193 tips 197 updating 194 updating views 194 groups creating user 128 default security 127 editing description 129 F FindCheckout description 472 flat files MX view of repository file definitions 343 view of fields 345 folder permissions description 126 editing 149 overview 148.dtd 267 privileges 266 sessions 272 shortcuts 270 steps for 285 versioned objects 273 external loader connections during folder or deployment group copy 245 permissions and privileges 245 external security module registering 484 unregistering 489 properties 168.

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

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

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

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

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.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.dtd overview 267 privileges See also permissions See also repository privileges Administration Console tasks 50 530 Index .

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

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

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

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

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

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