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

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

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

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

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

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

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

xvi Table of Contents .

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

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

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

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

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

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

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

xxii List of Tables .

transforming. and efficient manner. PowerCenter can simplify and accelerate the process of moving data warehouses from development to test to production. including extracting.Preface Welcome to PowerCenter. and support high-speed loads. loading. Informatica’s software product that delivers an open. data migration. 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. usable. and information hubs. handle complex transformations on the data. data synchronization. xxiii . The PowerCenter metadata repository coordinates and drives a variety of core functions. PowerCenter combines the latest technology enhancements for reliably managing data repositories and delivering information resources in a timely. and managing data.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

xl Preface .

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

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

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

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

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

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

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

For more information on creating and sending notification messages. 8 Chapter 1: Understanding the Repository .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. or to users connected to all of the repositories managed by a Repository Server. Use notification messages tell users to disconnect if you want to shut down the repository.

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

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

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

Permissions permit or restrict access to folders and objects in the repository. see “Repository Security” on page 125. 12 Chapter 1: Understanding the Repository . running sessions. 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.

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

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

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

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

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

18 Chapter 1: Understanding the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

such as a session. 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.If you choose a Workflow Manager object. Comparing Repository Objects 47 . Displays the properties of the node you select. Differences between object properties are marked. Compare object instances.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Repository Server Log File Sample The following sample is an excerpt from a Repository Server log file that illustrates log file codes: INFO : SF_34058 [Fri Jul 16 09:16:46 2004] : (1324|1452) Service started. INFO : REP_51005 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized database connection information. Reading the Repository Log Files 99 . Messages sent from the Repository Server display PmRepServer in the Source column. the messages appear in the Application Log component of the Windows Event Viewer. However. you must view the text of the message. INFO : REP_51008 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized request dispatcher. Database : penguin@production. since some message codes are embedded within other codes. INFO : REP_51007 [Fri Jul 16 09:37:33 2004] : (1396|1952) Repository runtime manager initialized. to ensure you are viewing the true message code. 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. Sample Application Log If you configure the Repository Server to log messages in the event log. 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.When you configure the Repository Server to write Trace or Debug severity level messages to the Repository Server log file. 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. Database User : admin1 INFO : REP_51009 [Fri Jul 16 09:37:37 2004] : (1396|1952) Informatica repository agent ready to receive request on port 5003. INFO : SF_34012 : (1324|1452) Opened Server Port [5001] to listen for client connections. 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_34003 [Fri Jul 16 09:16:47 2004] : (1324|1452) Server initialization completed. INFO : REP_51006 [Fri Jul 16 09:37:33 2004] : (1396|1952) Initialized configuration information.

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

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

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

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

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

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

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

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

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

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

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

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

you can back it up and restore it. Tip: To change the repository code page after you create the repository. The Administration Console saves the repository configuration and adds it to the Repository Server configuration directory. When you restore a repository. see “Working with PowerCenter Licenses” on page 119. When the Repository Server finishes creating the repository. the Repository Server begins building the repository in the database. 12.For more information on licenses. the repository appears in the Console Tree under the Repositories node. 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 . Click OK to save the configuration options.

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

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

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

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

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

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

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

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

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

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

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

124 Chapter 4: Configuring the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

Creating and Editing Repository Users 137 . but it must match a valid login name in the directory. 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. 2. In the Repository Manager. click Check Names. To add users with an external directory service: 1. 3. 4. Select a login name from the external directory list and click Add. the names display at the bottom separated by semi-colons. The login name displays at the bottom of the screen. To check the spelling. The Add Users dialog box displays a list of names from the external directory service. connect to a repository. Choose Security-Manage Users and Privileges. you add repository users from a list of login names from the external directory. Click Add. You do not create repository user passwords. Note: You can type a name at the bottom of the screen.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

164 Chapter 5: Repository Security .

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

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

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

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

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

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

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

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

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

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

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. 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.

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

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

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

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

180 Chapter 6: Working with Folders .

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

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

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

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

any shortcuts created after the change then contain the latest description.For example. Object and Shortcut Description Description from the original object Description added to the shortcut Shortcuts do not inherit edits to the description of the referenced object. Locating the Referenced Object Each shortcut tracks the location of the object it references and displays it in the transformation property sheet. The shortcut object displays the following details about the referenced object: ♦ ♦ ♦ Repository name Folder name Table or transformation name Understanding Shortcut Properties 185 . 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Figure 9-4 shows the Apply Label Wizard: Figure 9-4. browse to select the label to apply and choose label options. see Table 9-1 on page 222. Working with Labels 223 . Label all objects in a selected repository. You can select Preview to view the objects the Repository Agent labels. Label selected objects. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

262 Chapter 10: Copying Folders and Deployment Groups .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You can save the comparison as a text or HTML file. 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. Click Compare Conflict to compare conflicting objects in the XML file and target repository. 15. Use the Conflict Resolution Wizard to resolve specific object conflicts. The Conflict Resolution Wizard is similar to the Copy Wizard. 292 Chapter 11: Exporting and Importing Objects . The Diff Tool window appears. see “Copying Objects” on page 297.

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

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

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

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

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

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

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

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

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. The selected resolution reuses the object. Figure 12-2. Copy Wizard Resolutions The wizard prompts you to select a resolution for each unresolved object in your copy. click Apply This Resolution To and choose either All Conflicts or conflicts for just the specified object type. Optionally. Resolving Copy Conflicts 301 . or to all conflicts in your copy. you can apply the resolution to all unresolved objects of the same type. To apply the resolution to more objects.

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

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

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

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

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

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

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

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

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

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

312 Chapter 12: Copying Objects .

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

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

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

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

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

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

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

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

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

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

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

324 Chapter 13: Exchanging Metadata .

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

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

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

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

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

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

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

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

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

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

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

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

The next generation of MX. called Metadata Exchange SDK. Viewing the Repository Metadata 337 . Software vendors can integrate Informatica metadata with their products through different methods. provides an object-based Application Programming Interface (API) to read and write metadata in Informatica repositories.sq_ termxdrp. Integrating MX Views with Third-Party Software With MX software and support from Informatica. from pulling the Informatica metadata into product or user repositories to providing dynamic desktop pass-through access.Table 15-3. SQL Script to Drop MX Views Repository Database Sybase Teradata SQL Script sybmxdrp. vendors of popular query and reporting tools can quickly create a metadata link between their products and the PowerCenter repository.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. Informatica recommends using the fields in bold to join views. A database definition includes the source database names. MX provides the REP_DATABASE_DEFS view to help you analyze database definitions. Version ID of the source. 338 Chapter 15: Using Metadata Exchange (MX) Views .Database Definition View The database definition view provides a list of all database definitions in the repository. Folder 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

16 = Run on server initialization. 2 = Run forever. Number of seconds the PowerCenter Server waits between successive workflow runs. 32 = Run continuously. Description of the workflow. 1 = valid. and Task Views 373 .Table 15-39. Records the following values for each stop condition option: 0 = End on a date. Worklet. 1 = End after the number of runs stored in RUN_COUNT. 0 = invalid. Records the following values for each schedule type: 1 = Run on demand. Scheduler description. Workflow version number. PowerCenter Server ID. 8 = Customized repeat. Date and time when the workflow was last saved. Folder ID. 4 = Run every DELTA_VALUE seconds. Name of the PowerCenter server registered with the repository. Version number of the scheduler. REP_WORKFLOWS MX View Column Name RUN_OPTIONS Datatype INTEGER Description The workflow schedule type. Specifies if scheduler is reusable. Workflow ID. 2 = Run once. Specifies whether the workflow is valid or not. Number of times the PowerCenter Server runs the workflow before stopping the workflow. Scheduler ID. END_OPTIONS INTEGER RUN_COUNT WORKFLOW_VERSION_NUMBER SCHEDULER_VERSION_NUMBER SUBJECT_ID WORKFLOW_ID WORKFLOW_IS_VALID WORKFLOW_LAST_SAVED WORKFLOW_COMMENTS SCHEDULER_ID SCHEDULER_IS_REUSABLE SCHEDULER_COMMENTS DELTA_VALUE SERVER_NAME SERVER_ID INTEGER NUMBER NUMBER NUMBER NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (2000) NUMBER NUMBER VARCHAR2 (2000) NUMBER VARCHAR2 (240) NUMBER Informatica recommends using the fields in bold to join views. Workflow. The stop condition option for the workflow schedule type.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Deployment status. 1 = rollback. 2 = rollback failed. UTC deployment time.Table 15-66. Deployment user name. 394 Chapter 15: Using Metadata Exchange (MX) Views . Deployment rollback time. 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. 0 = deployed.

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

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

PowerCenter Server job distribution options. Use network = 1. Informatica recommends using the fields in bold to join views. 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). 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. Server name. 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). Use network and used by network = 3. Table 15-70 lists PowerCenter Server information in the REP_SERVER_NET view: Table 15-70. Table 15-71 lists PowerCenter Server identification and usage information within the grid in the REP_SERVER_NET_REF view: Table 15-71. Informatica recommends using the fields in bold to join views. PowerCenter Server ID (primary key).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

412

Chapter 16: Using pmrep and pmrepagent

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

StopRepository SwitchConnection Truncatelog Unregister UpdateConnection Updateemailaddr Updateseqgenvals

Updateserver Updatesrcprefix Updatesrvvar UpdateStatistics Updatetargprefix

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

pmrep Repository Commands

413

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

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

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

414

Chapter 16: Using pmrep and pmrepagent

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

-A

repserver_password_ environment_variable repository_name database_type database_user_name

-r -t -u

-m -p

Optional Required/ Optional

n/a database_password

-P

Required/ Optional

database_password_ environment_variable

-c

Required

database_connect_string

-d

Optional

code_page

pmrep Repository Commands

415

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

-l

Optional

license_file_name

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

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

-b -j -q

Optional Optional Optional

skip_workflow/ session_logs skip_deploy_group _history skip_MX_data

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

416

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

-P

password_environm ent_variable connect_string

-c

-l -r

Required Optional

code_page rollback_segment

pmrep Repository Commands

417

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

-b -v -d -t

Optional Optional Optional Optional

database_name server_name domain_name trusted_connection

-x

Optional

n/a

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

418

Chapter 16: Using pmrep and pmrepagent

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

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

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

pmrep Repository Commands

419

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

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

420

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

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

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

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

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

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

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

-r

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

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

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

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

422

Chapter 16: Using pmrep and pmrepagent

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

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

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

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

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

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

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

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

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

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

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

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

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

The commands are echoed back to the script.Table 16-23. The name of the repository to remove. The run might fail if the Repository Server cannot open the script file or output file. Run Options and Arguments (pmrep) Option -f -o Required/ Optional Required Optional Argument Name script_file_name output_file_name Argument Description The name of the script file. -r The command returns “removerepository successfully completed” or “failed to execute removerepository” message. 436 Chapter 16: Using pmrep and pmrepagent . The removal might fail for the following reasons: ♦ ♦ The repository name does not exist. Stops the running of the script after a command returns an error. but not both. Use the -a or -A option. All repository users can run script files. -e -s Optional Optional echo_commands stop_at_first_error The command returns “run successfully completed” or returns “run failed” message. 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. Running Script Files (Run) The Run command takes a file containing multiple pmrep commands and runs those commands sequentially. This option writes all messages generated by the commands in the script file into the output file. You failed to connect to the Repository Server. The name of the output file. 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 named repository stops. However. pmrep Repository Commands 437 . and -r options. pmrep connects to the Repository Server and stops the Repository Agent. the repository that you last connected to stops. StopRepository stops the repository you last connected to. When you use the ShowConnectioninfo command in command line mode. see “Connecting to a Repository (Connect)” on page 410. For example. the pmrep keeps the connection information in memory until you exit the repository or connect to a different repository. port.Showing Connection Information (ShowConnectioninfo) The ShowConnectioninfo command returns the repository name. ShowConnectioninfo requires no parameters. Stopping a Repository (StopRepository) The StopRepository command stops the repository you specify. -o. You must be connected to a repository to use this command. server. The ShowConnectioninfo command does not connect to the repository. Otherwise. and user information for the current connection. StopRepository uses the following command syntax: stopRepository [-a repserver_password -A repserver_password_environment_variable] -h hostname -o port_number -r repository_name Note: If you use the -h. When you use the StopRepository command. pmrep does not keep connection information in command line mode. if you do not specify a repository. When you connect to a repository in interactive mode. a message indicating failure to execute the command is given. 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. For more information about connections in command line mode and interactive mode.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

508 Appendix A: Working with pmrep Files .

519 pmrepagent Tasks. 510 Workflow Manager Tasks. 515 Repository Manager 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. 513 pmcmd Tasks.Appendix B Permissions and Privileges by Task This appendix summarizes the available tasks in the PowerCenter Client tools. 520 509 .

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

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

FTP.Table B-2. FTP. Required Privileges and Permissions for Workflow Manager Tasks Repository Privilege Use Workflow Manager and Administer Server Use Workflow Manager Use Workflow Manager Administer Repository Administer Server Use Workflow Manager Use Workflow Manager Use Workflow Manager Use Workflow Manager Connection Object Permission None required Workflow Manager Task Stop the PowerCenter Server Folder Permission None required Configure database. 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. and external loader connections in the Workflow Manager Edit database. Write None required None required Read Read/Write Read/Write None required None required None required None required None required None required None required 512 Appendix B: Permissions and Privileges by Task .

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

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

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

Repository Manager Tasks To perform the following Repository Manager tasks. as the folder owner with read permission on the folder Administer Repository privilege with read permission on the folder Super User privilege Table B-5 lists the required permissions and privileges for Repository Manager tasks: Table B-5. you must have one of the listed sets of privileges and permissions. For example. you can edit the properties of a folder if you have one of the following sets of permissions or privileges: ♦ ♦ ♦ Browse Repository privilege. Required Permissions and Privileges for Repository Manager Tasks Repository Manager Task 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 .

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

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

For example.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. 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.

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

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 .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. 45 conflicts copying Designer objects 310 copying workflow segments 308 database connections 307 mapping 307 resolving when importing 281 connect string examples 405 syntax 405 connecting to repositories 30. 192 command line program See pmrep See also pmrepagent comments accessing metadata 335 comparing See also Designer Guide See also Workflow Administration Guide folders 174 Repository objects 45 Workflow Manager objects 21.

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

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

249 copying between local repositories 250 copying global shortcuts 250 copying local shortcuts 249 copying or replacing 250 copying shortcuts 249 creating 171 deleting 173. 171 renaming 173 Repository Manager uses 166 shared 15. 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.powrmart. 192 creating 14 promoting 112.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. 168 security levels 148 user groups 128 folder status changing 207 description 207 folders comparing 174 copying 245. 453 deploying 469 Designer uses 166 editing 173 editing permissions 149 locking during folder copy 249 maintaining connections during copy 245 modifying 456 naming copies 249 organizing 166 overview 166 owner and owner’s group 169 H HTML view Administration Console 53 I IBM DB2 connect string example 405 setting tablespace name 107 Import Wizard importing objects 287 resolving object conflicts 281 Index 525 . 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. 117 purpose 13 shared folders 170 global shortcuts behavior when copying folders 250 creating 190 definition 182.

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

192 promoting to global 112 registering 75 local shortcuts behavior when copying folders 249 creating 187 definition 182. 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. 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.

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

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

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

192 connecting to 30 connecting to multiple 31 connecting with pmrep 410 connectivity 4 copying 62 copying folders between local 250 creating 116 creating relational connections 417 creating users 134 database definition views 338 default privileges 143 deleting 64 disabling 73.Designer tasks 510 exporting objects 266 importing objects 266 limiting 160 removing 458 Repository Manager tasks 516 repository. troubleshooting 163 starting 71 Index 531 . 75. 158 removerepsitory description 435 removing repositories 29 users 141 replacing folders 248. 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. 50 promoting 117 propagating domain information 78 referencing objects with shortcuts 183 registering 434 registering local repositories 75 removing 29. 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. overview 155 overview 2. 250 reports metadata 335 repositories adding 29 adding metadata 9 administration overview 11 architecture 3 avoiding shared accounts 160 backing up 66 backing up with pmrepagent 477 changing a code page 117 checking status 54 code pages 51. 160 security log file 153 security. 435 requirements 116 restoring 67 restricted characters for repository name 106 security 126.

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. 147 repository security level description (folder) 148 Repository Server Administration Console 50 architecture 3 client connections 3 532 Index . 152 viewing 79. 151 repository license files overview 120 repository license key overview 120 repository locks overview 154 releasing 158 types of 154 viewing 157 Repository Manager components 22 dependency window 27 folder maintenance overview 166 folders 23 main window 25 Navigator 23 Output window 28 overview 20 permissions 516 repository details 26 sessions node details 26 windows 23 repository notifications overview 6 receiving in PowerCenter Server 7 receiving in Workflow Manager 7 receiving in Workflow Monitor 7 sending 74 repository objects description 10 metadata extensions in 326 repository plug-ins registering 85 removing 85 updating 86 repository privileges See also permissions assigning 146 description 126 overview 142 revoking 146.

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

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

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

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