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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

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. see “Sending Repository Notifications” on page 74. 8 Chapter 1: Understanding the Repository . Use notification messages tell users to disconnect if you want to shut down the repository. For more information on creating and sending notification messages.

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

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

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

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

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

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

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

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

see “Copying Folders and Deployment Groups” on page 241. For more information on using pmrep for change management. you can automate the process for copying deployment groups. For more information on copying objects in a deployment group. 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. This allows you to use pmrep scripts and files to automate change management tasks. Version Control 17 .repository. see “Using pmrep and pmrepagent” on page 403. For example.

18 Chapter 1: Understanding the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Select the Locks node under the repository. 2. 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.Viewing Locks in the Administration Console Use the following procedure to view locks in the Administration Console. In the Console Tree. To sort your view of the locks by column. select the repository containing the locks you want to view. 82 Chapter 3: Managing the Repository .

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

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

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

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

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

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

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

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

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

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

88

Chapter 3: Managing the Repository

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

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

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

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

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

Registering and Unregistering LDAP Security Modules

89

The Repository Server lists the available plug-ins.

4.

Select the Authentication Module, and choose Action-Register.

90

Chapter 3: Managing the Repository

The Register Security Module dialog box displays.

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

5.

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

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

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

3.

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

4.

Enter LDAP server options.

92

Chapter 3: Managing the Repository

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

Principal User Name Principal User Password 5.

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

Registering and Unregistering LDAP Security Modules

93

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

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

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

94

Chapter 3: Managing the Repository

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

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

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

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

3.

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

Registering and Unregistering LDAP Security Modules

95

The Unregister Package dialog box displays.

4.

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

96

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

♦ ♦

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

98

Chapter 3: Managing the Repository

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

Click OK. 7. Enter the new password twice to confirm it. connect to the repository. and click Remove. Note: You cannot remove a user from a group when the user belongs to only one group. 2. 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. 136 Chapter 5: Repository Security . Choose Security-Change Current Password. 8. Click OK to return to the Repository Manager. To edit a password: 1.The group appears in the Member list. you can edit your user password. In the Repository Manager. To remove the user from a group. Enter the old password. 3. 4. Editing a User Password If you are using default authentication. 5.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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-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.Table 6-2.

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

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

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 .Figure 7-2 shows the transformation property sheet with the referenced shortcut objects: Figure 7-2. the shortcut becomes invalid.

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

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

4.

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

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

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

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

6.

Choose Repository-Save.

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

Creating a Local Shortcut

189

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

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

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

190

Chapter 7: Local and Global Shortcuts

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

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

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

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

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

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

2.

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

3. 4.

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

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

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

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

6.

Choose Repository-Save.

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

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

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

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

3.

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

4. 5.

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

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

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

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

7.

Choose Repository-Save.

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

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

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

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

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

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

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

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

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

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

Creating a Global Shortcut

193

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

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

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

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

194

Chapter 7: Local and Global Shortcuts

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

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

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

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

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

Working with Shortcuts

195

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

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

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

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

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

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

Tips

197

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

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

♦ ♦ ♦

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

198

Chapter 7: Local and Global Shortcuts

Chapter 8

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

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

199

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Label selected objects. Working with Labels 223 . Apply Label Wizard Select the folder or folders containing objects you want to label. For more information about label options. After you select objects to label.Figure 9-4 shows the Apply Label Wizard: Figure 9-4. see Table 9-1 on page 222. 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.

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

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

♦ ♦

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

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

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

224

Chapter 9: Grouping Versioned Objects

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

Specify query conditions.

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

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

Working with Object Queries

225

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

Add logical operators. Add multiple query conditions.

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

4

3

226

Chapter 9: Grouping Versioned Objects

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

Check-in time

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

Date/time Numeric

Comments

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

String

Deployment Dispatch History

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

Date/time Numeric

Deployment Receive History

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

Date/time Numeric

Working with Object Queries

227

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

Include Children

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

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

Include Children and Parents

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

Where (Value 1) depends on (Value 2)

Include Parents

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

Where (Value 1) depends on (Value 2)

Include Primary/ Foreign Key Dependencies

Displays primary key-foreign key dependencies.

N/A

228

Chapter 9: Grouping Versioned Objects

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

Last Saved Time

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

Latest Status

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

Checked-out Latest checked-in Older

Metadata Extension

Is Equal To Is Not Equal To

User-defined metadata domain Any vendor-defined metadata extensions

Object Name

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

String

Working with Object Queries

229

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

Object Used Status

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

Is Equal To

Shortcut status

Is Equal To

Is Not Shortcut Is Shortcut

Reusable Status User

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

Non-reusable Reusable Users in specified repository

Valid Status Version Status

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

Invalid Valid Deleted Not deleted

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

230

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

Working with Object Queries

231

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

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

232

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

objects in the repository.

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

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

Working with Object Queries

233

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

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

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

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

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

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

234

Chapter 9: Grouping Versioned Objects

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

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

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

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

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

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

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Table 15-26. REP_MAPPING_UNCONN_PORTS This view displays the unconnected ports in sources. Table 15-27 lists unconnected port metadata in the REP_MAPPING_UNCONN_PORTS view: Table 15-27. Object type name. Mapping version number. targets. Number of column in second table. Source field ID (primary key). Name of the instance. ID of second table in the join. 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. Folder ID (primary key). Source field name. Sequence ID for the mapping (primary key). Name of column in second table. Informatica recommends using the fields in bold to join views. 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. Business name of column in second table. Name of second table in the join. Name of the mapping. 362 Chapter 15: Using Metadata Exchange (MX) Views . Object type. ID of column in second table. Unique ID for the instance in a mapping. Business name of second table. and transformations in a mapping. ID of column in first table. Table1 version number.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Run status code. First error code. LAST_ERROR_CODE LAST_ERROR TASK_VERSION_NUMBER WORKFLOW_VERSION_NUMBER SESSION_LOG_FILE BAD_FILE_LOCATION SUCCESSFUL_SOURCE_ROWS FAILED_SOURCE_ROWS SUCCESSFUL_ROWS FAILED_ROWS FIRST_ERROR_CODE NUMBER VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (240) VARCHAR2 (240) NUMBER NUMBER NUMBER NUMBER NUMBER Workflow.REP_SESS_LOG This view provides log information about sessions. Number of successfully read source rows. Number of failed source rows. Actual time session started. Worklet. Folder ID. Number of successfully loaded target rows. Session instance name. Last error message. REP_SESS_LOG MX View Column SUBJECT_AREA SUBJECT_ID SESSION_ID SESSION_INSTANCE_NAME ACTUAL_START SESSION_TIMESTAMP RUN_STATUS_CODE Datatype VARCHAR2 (240) NUMBER NUMBER VARCHAR2 (240) DATE (DB SPECIFIC) DATE (DB SPECIFIC) NUMBER Description Folder name. Time completed. Version number of the task. Session log file name. Session ID. Workflow version number. Table 15-58 lists session log information in the REP_SESS_LOG view: Table 15-58. This view supplies the status of the last session. Location of the reject file. which might contain one or many target tables. 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. and Task Views 387 . Number of failed target rows.

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

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

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

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

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

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

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

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

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

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

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

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

400 Chapter 15: Using Metadata Exchange (MX) Views . Label description. Informatica recommends using the fields in bold to join views.Table 15-75. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

To send notification messages. If you omit this option. The character or set of characters used to specify the end of the object list. The character or set of characters used to specify the end of the object metadata. pmrep uses a single space.Table 16-18. deployment group. pmrep prints a shorter format including the object type. such as label. If you omit this option. Verbose format includes the version number and folder name. Print more than the minimum information about the objects. The short format for versioning objects. ListObjectDependencies Options and Arguments (pmrep) Option -c Required/ Optional Optional Argument Name column_separator Argument Description The character or set of characters used to separate object metadata columns. Use a character or set of characters that is not used in repository object names. Verbose format includes the creator name and creation time. the object name and path. you must have Administer Repository privilege. Use a character or set of characters that is not used in repository object names. includes the object type and object name. The default is newline /n. The Notify command uses the following command syntax: Notify -h hostname -o port_number [-a repserver_password | -A repserver_password_environment_variable] -r repository_name -t notify | broadcast -m message Table 16-19 lists pmrep Notify options and arguments: Table 16-19. query. pmrep uses a period. If you omit this option. The number of the port where the Repository Server is running. Notify Options and Arguments (pmrep) Option -h -o Required/ Optional Required Required Argument Name hostname port_number Argument Description The name of the machine hosting the Repository Server. If any repository object name contains spaces. pmrep Repository Commands 431 . you might want to avoid using a space as a column separator. Specify a character or set of characters that is not used in repository object names. the word reusable or nonreusable. -r Optional end-ofrecord_separator -l Optional end-oflisting_indicator -b Optional verbose Sending Notification Messages (Notify) Use the Notify command to send notification messages to users connected to a repository or users connected to all repositories managed by a Repository Server. and connection.

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

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

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

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

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

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

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

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

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

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

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

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

To update sequence values. 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. When you update values for a nonreusable Sequence Generator transformation. The Sequence Generator transformation name. -t sequence_generator_name 444 Chapter 16: Using pmrep and pmrepagent . you must include the mapping 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 can use Updateseqgenvals to update reusable and non-reusable Sequence Generator transformations. The mapping name. For more information on configuring Sequence Generator transformations. you cannot update values for instances of reusable Sequence Generator transformations or shortcuts to Sequence Generator transformations. However. You must connect to a repository to use this command. see “Sequence Generator Transformation” in the Transformation 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Use the -p or -P option. The repository database password environment variable. see “Registering a Repository Plug-in” on page 85. but not both. The repository user name.Table 16-71. This option unregisters local repositories. The repository password environment variable. The repository password. The connect string the Repository Agent uses to connect to the repository database. Registerplugin uses the following command syntax: Registerplugin -r repository_name -n repository_user_name -x repository_password -X repository_password_environment_variable -t database_type -u database_user_name -p database_password -P database_password_environment_variable -m -c database_connect_string -i input_xml_file_name -e -f force_registration -l login_name -w login_password -W login_password_environment_variable -k Table 16-72 lists pmrepagent Registerplugin options and arguments: Table 16-72. Use the -x or -X option. The repository database password. see Table 16-1 on page 405. 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. but not both. but not both. For more information about registering a plug-in. The repository database user name. 482 Chapter 16: Using pmrep and pmrepagent . 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. 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. For a list of connect string syntax. but not both. Registering a plug-in adds its functionality to the repository. Use this option to delete a global repository. You can use the Registerplugin command to update existing plug-ins. Use the -x or -X option. Use the -p or -P option.

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

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

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

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

rep Unregistering Plug-ins (Unregisterplugin) The pmrepagent Unregisterplugin command removes a plug-in from a repository. but not both. see “Unregistering a Repository Plug-in” on page 86. Skips deployment group history during backup. The name of the license file. 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 . -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. For more information. 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. Use this option with the -v option when you want to retain the external security module after restoring. Restore Options and Arguments (pmrepagent) Option -X Required/ Optional Required/ Optional Argument Name verify_password_environment_ variable Argument Description The verify password environment variable. For more information on unregistering plug-ins. You must use either the -x or -X option when you want to retain an external security module. Example The following example restores a repository to a Solaris machine and specifies the administrator user name and password in order to keep the LDAP security module registration. Removes user name-login mapping. see “Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479. Skips tables related to MX data during backup. Use this option only when unregistering an external module. The Repository Agent verifies that this password is valid for the user name on the target server. Use the -x or -X option. Use this option only with a repository using an external security module.Table 16-73.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

508 Appendix A: Working with pmrep Files .

510 Workflow Manager Tasks. 513 pmcmd Tasks. 520 509 . 519 pmrepagent Tasks. It then lists the repository privileges and folder permissions required to perform each task in these tools: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Designer 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.

targets. transformations. Read and write permission for the destination folder. you must have one of the listed sets of privileges and permissions. 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. Required Privileges and Permissions for Designer Tasks Designer Task Connect to the repository using the Designer View sources. and mappings Create/edit sources. For example.Designer Tasks To perform the following Designer tasks. Read permission in the originating folder. targets. 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 . 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. Read and write permission in the destination folder. transformations.

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

and external loader connections in the Workflow Manager Edit database. FTP.Table B-2. FTP. and external loader connections in the Workflow Manager Manage connection object permissions Register PowerCenter Servers and configure server variable directories Export objects Import objects Validate workflows and tasks Run Workflow Monitor None required None required None required Read. Write None required None required Read Read/Write Read/Write None required None required None required None required None required None required None required 512 Appendix B: Permissions and Privileges by Task . 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. Use Workflow Manager privilege with read and execute permissions for the folder containing the workflow. Required Privileges and Permissions for Workflow Monitor Tasks Workflow Monitor Task Connect to repository Repository Privilege Use Workflow Manager or Workflow Operator Workflow Operator Use Workflow Manager View the session log Workflow Operator Use Workflow Manager Restart workflow Workflow Operator Use Workflow Manager Stop workflow Workflow Operator Use Workflow Manager Abort workflow Workflow Operator Use Workflow Manager Resume workflow Workflow Operator Use Workflow Manager Folder Permission None required Connection Object Permission None required Connect to the PowerCenter Server None required None required Read Read/Execute Execute Execute Execute Execute Execute Execute Execute Execute None required None required None required None required None required None required None required None required None required None required None required None required Workflow Monitor Tasks 513 .Workflow Monitor Tasks To perform the following Workflow Monitor tasks. For example. you can restart a workflow if you have one of the following sets of permissions and privileges: ♦ ♦ ♦ Workflow Operator privilege with execute permission for the folder containing the workflow. you must have one of the listed sets of privileges and permissions.

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

you must have execute permission for connection objects associated with the session in addition to the privileges and permissions listed above. Table B-4 lists the required privileges and permissions for pmcmd tasks: Table B-4. For example.pmcmd Tasks To perform the following pmcmd tasks. 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. 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 .

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

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

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

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

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

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

31 connection objects See also Workflow Administration Guide definition 10 permissions and privileges 245 connections terminating 83 viewing 79 connectivity connect string examples 405 connectivity license keys overview 119 ConnectString setting for repository configuration 107 Console Tree Administration Console 52 control file deployment 504 object import 496 ObjectImport XML example 500 Copy Wizard copying objects 302 resolving conflicts 300 viewing object dependencies 305 . 45 conflicts copying Designer objects 310 copying workflow segments 308 database connections 307 mapping 307 resolving when importing 281 connect string examples 405 syntax 405 connecting to repositories 30.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 .

276 parent objects 271 permissions 266 524 Index . 37 dependent objects exporting and importing 270 DeployDeploymentGroup description 467 DeployFolder description 469 deploying objects depcntl.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.dtd 504 rolling back a deployment 238 deployment groups copying 254.

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. 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 .dtd 267 privileges 266 sessions 272 shortcuts 270 steps for 285 versioned objects 273 external loader connections during folder or deployment group copy 245 permissions and privileges 245 external security module registering 484 unregistering 489 properties 168. 171 renaming 173 Repository Manager uses 166 shared 15. 192 creating 14 promoting 112.powrmart. 168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245. 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.

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

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

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

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 .

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

overview 155 overview 2. 50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. 158 removerepsitory description 435 removing repositories 29 users 141 replacing folders 248. 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. 75. 421 enabling 71 enabling version control 118 exporting/importing registries 32 licenses 120 limiting access 161 locks 154 log file codes 97 log files 97 managing 52 moving to a different Repository Server 77 object locking.Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. troubleshooting 163 starting 71 Index 531 . 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. 160 security log file 153 security. 192 connecting to 30 connecting to multiple 31 connecting with pmrep 410 connectivity 4 copying 62 copying folders between local 250 creating 116 creating relational connections 417 creating users 134 database definition views 338 default privileges 143 deleting 64 disabling 73.

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

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. 190. 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 . 187 overview 182 properties 184 referenced objects 183.

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

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