Escolar Documentos
Profissional Documentos
Cultura Documentos
Informatica PowerCenter®
(Version 7.1.1)
Informatica PowerCenter Repository Guide
Version 7.1.1
August 2004
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.
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
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
i
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
PowerCenter Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Building the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Reusing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Reusing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
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
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
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
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
Table of Contents ix
SQL Definition of Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Integrating MX Views with Third-Party Software . . . . . . . . . . . . . . . . 337
Database Definition View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
REP_DATABASE_DEFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Source Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
REP_ALL_SOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
REP_ALL_SOURCE_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
REP_SRC_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
REP_SRC_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
REP_SRC_FILE_FLDS and REP_SEG_FLDS . . . . . . . . . . . . . . . . . . 345
REP_SRC_TBL_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Target Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
REP_ALL_TARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
REP_ALL_TARGET_FIELDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
REP_TARG_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
REP_TARG_TBL_COLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Mapping and Mapplet Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
REP_ALL_MAPPINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
REP_ALL_MAPPLETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
REP_TARG_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
REP_TARG_FLD_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
REP_FLD_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
REP_SRC_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
REP_SRC_FLD_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
REP_TBL_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
REP_TARG_TBL_JOINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
REP_MAPPING_UNCONN_PORTS . . . . . . . . . . . . . . . . . . . . . . . . 362
REP_MAPPING_PORT_CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Metadata Extension Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
REP_METADATA_EXTNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
REP_METADATA_EXTN_DEFINES . . . . . . . . . . . . . . . . . . . . . . . . 365
Transformation Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
REP_ALL_TRANSFORMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
REP_WIDGET_INST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
REP_WIDGET_DEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
REP_WIDGET_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
REP_WIDGET_FIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Workflow, Worklet, and Task Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
x Table of Contents
REP_WORKFLOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
REP_ALL_TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
REP_ALL_SCHEDULERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
REP_WFLOW_VAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
REP_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
REP_TASK_INST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
REP_WORKFLOW_DEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
REP_TASK_INST_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
REP_WFLOW_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
REP_LOAD_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
REP_SESSION_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
REP_SESSION_INSTANCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
REP_SESSION_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
REP_SESSION_INSTANCE_FILES . . . . . . . . . . . . . . . . . . . . . . . . . 383
REP_SESS_WIDGET_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
REP_COMPONENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
REP_SESS_PARTITION_DEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
REP_SESS_CONFIG_PARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
REP_TASK_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
REP_SESS_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
REP_SESS_TBL_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Security Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
REP_USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
REP_USER_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
REP_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Deployment Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
REP_DEPLOY_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
REP_DEPLOY_GROUP_DETAIL . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Repository View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
REP_REPOSIT_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
PowerCenter Server Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
REP_SERVER_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
REP_SERVER_NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
REP_SERVER_NET_REF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Change Management Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
REP_VERSION_PROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
REP_CM_LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
REP_CM_LABEL_REF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Table of Contents xi
Folder View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
REP_SUBJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Table of Contents xv
xvi Table of Contents
List of Figures
Figure 1-1. PowerCenter Repository Connectivity . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . .. 4
Figure 2-1. Repository Manager Components . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 22
Figure 2-2. Repository Manager Navigator . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 24
Figure 2-3. Source Definition Object Properties . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 25
Figure 2-4. Dependency Window . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 27
Figure 2-5. Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 28
Figure 2-6. Dependencies Dialog Box . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 39
Figure 2-7. View Dependencies Window . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 40
Figure 2-8. Object Dependencies Saved as HTML . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 41
Figure 2-9. Validate Objects Results . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 43
Figure 3-1. Administration Console . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 52
Figure 3-2. Repository Details . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 55
Figure 3-3. Activity Log Window . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . . 56
Figure 3-4. Event Viewer Application Log Message . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 100
Figure 3-5. Application Log Message Detail . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 100
Figure 5-1. Repository User Names and External Login Names . .. . . .. . . .. . .. . . .. . .. . 132
Figure 6-1. One-Way and Two-Way Comparisons . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 177
Figure 7-1. Object and Shortcut Description . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 185
Figure 7-2. Referenced Shortcut Object . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 186
Figure 7-3. Transformation Shortcut Icon . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 187
Figure 7-4. Create a Global Shortcut . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 190
Figure 8-1. Results View Windows List . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 202
Figure 8-2. Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 204
Figure 8-3. Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 204
Figure 8-4. Labels Properties . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 205
Figure 8-5. Object Status Properties . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 206
Figure 8-6. View History Window . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 209
Figure 9-1. Label Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 220
Figure 9-2. Label Editor Options . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 220
Figure 9-3. Apply Label Dialog Box . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 221
Figure 9-4. Apply Label Wizard . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 223
Figure 9-5. Query Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 224
Figure 9-6. Query Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 225
Figure 9-7. Query with Multiple Conditions . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 226
Figure 9-8. Sample Query Results . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 232
Figure 9-9. Deployment Group Browser . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 236
Figure 9-10. Deployment Group Editor . . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 237
Figure 9-11. Deployment Group History . . . . . . . . . . . . . . . . . .. . . .. . . .. . .. . . .. . .. . 238
Figure 9-12. Dependency for Deployment Group Dialog Box . . .. . . .. . . .. . .. . . .. . .. . 239
Figure 11-1. CRCVALUE Code in an Exported XML File . . . . . .. . . .. . . .. . .. . . .. . .. . 268
List of Figures xv
Figure 11-2. Export Options Dialog Box . . . . . . . . . . . . . . . . ... . . .. . .. . . .. . . .. . .. . .271
Figure 11-3. Import Wizard - Resolve General Object Conflicts .. . . .. . .. . . .. . . .. . .. . .282
Figure 11-4. Import Wizard - Resolve Specific Object Conflicts .. . . .. . .. . . .. . . .. . .. . .283
Figure 11-5. Conflict Resolution Wizard . . . . . . . . . . . . . . . . ... . . .. . .. . . .. . . .. . .. . .284
Figure 12-1. The Copy Wizard . . . . . . . . . . . . . . . . . . . . . . . ... . . .. . .. . . .. . . .. . .. . .298
Figure 12-2. Copy Wizard Resolutions . . . . . . . . . . . . . . . . . . ... . . .. . .. . . .. . . .. . .. . .301
Figure 12-3. Copy Wizard Mapping Conflicts . . . . . . . . . . . . ... . . .. . .. . . .. . . .. . .. . .303
xx List of Tables
Table 16-43. Createuser Options and Arguments (pmrep) . . . . . . . . . . . . . . . . .. . . .. . .. . 453
Table 16-44. DeleteFolder Options and Arguments (pmrep) . . . . . . . . . . . . . . . .. . . .. . .. . 453
Table 16-45. Edituser Options and Arguments (pmrep) . . . . . . . . . . . . . . . . . . .. . . .. . .. . 454
Table 16-46. ModifyFolder Option and Argument (pmrep) . . . . . . . . . . . . . . . .. . . .. . .. . 456
Table 16-47. Registeruser Option and Argument (pmrep) . . . . . . . . . . . . . . . . . .. . . .. . .. . 457
Table 16-48. Rmgroup Option and Argument (pmrep). . . . . . . . . . . . . . . . . . . .. . . .. . .. . 458
Table 16-49. Rmprivilege Options and Arguments (pmrep) . . . . . . . . . . . . . . . .. . . .. . .. . 458
Table 16-50. Rmuser Option and Argument (pmrep) . . . . . . . . . . . . . . . . . . . . .. . . .. . .. . 459
Table 16-51. Rmuserfromgroup Options and Arguments (pmrep) . . . . . . . . . . . .. . . .. . .. . 459
Table 16-52. pmrep Change Management Commands . . . . . . . . . . . . . . . . . . . .. . . .. . .. . 460
Table 16-53. AddToDeploymentGroup Options and Arguments (pmrep) . . . . . .. . . .. . .. . 461
Table 16-54. ApplyLabel Options and Arguments (pmrep) . . . . . . . . . . . . . . . . .. . . .. . .. . 463
Table 16-55. Checkin Options and Arguments (pmrep) . . . . . . . . . . . . . . . . . . .. . . .. . .. . 464
Table 16-56. ClearDeploymentGroup Options and Arguments (pmrep) . . . . . . .. . . .. . .. . 465
Table 16-57. CreateDeploymentGroup Options and Arguments (pmrep) . . . . . .. . . .. . .. . 465
Table 16-58. CreateLabel Options and Arguments (pmrep) . . . . . . . . . . . . . . . .. . . .. . .. . 466
Table 16-59. DeleteDeploymentGroup Options and Arguments (pmrep) . . . . . .. . . .. . .. . 467
Table 16-60. DeleteLabel Options and Arguments (pmrep) . . . . . . . . . . . . . . . .. . . .. . .. . 467
Table 16-61. DeployDeploymentGroup Options and Arguments (pmrep) . . . . . .. . . .. . .. . 468
Table 16-62. DeployFolder Options and Arguments (pmrep) . . . . . . . . . . . . . . .. . . .. . .. . 469
Table 16-63. ExecuteQuery Options and Arguments (pmrep) . . . . . . . . . . . . . . .. . . .. . .. . 470
Table 16-64. FindCheckout Options and Arguments (pmrep) . . . . . . . . . . . . . . .. . . .. . .. . 472
Table 16-65. UndoCheckout Options and Arguments (pmrep) . . . . . . . . . . . . . .. . . .. . .. . 474
Table 16-66. Validate Options and Arguments (pmrep) . . . . . . . . . . . . . . . . . . .. . . .. . .. . 475
Table 16-67. pmrepagent Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . .. . 477
Table 16-68. Backup Options and Arguments (pmrepagent) . . . . . . . . . . . . . . . .. . . .. . .. . 478
Table 16-69. Bulkrestore Options and Arguments (pmrepagent) . . . . . . . . . . . . .. . . .. . .. . 479
Table 16-70. Create Options and Arguments (pmrepagent) . . . . . . . . . . . . . . . .. . . .. . .. . 480
Table 16-71. Delete Options and Arguments (pmrepagent) . . . . . . . . . . . . . . . .. . . .. . .. . 481
Table 16-72. Registerplugin Options and Arguments (pmrepagent) . . . . . . . . . . .. . . .. . .. . 482
Table 16-73. Restore Options and Arguments (pmrepagent) . . . . . . . . . . . . . . . .. . . .. . .. . 485
Table 16-74. Unregisterplugin Options and Arguments (pmrepagent) . . . . . . . . .. . . .. . .. . 488
Table 16-75. Upgrade Options and Arguments (pmrepagent) . . . . . . . . . . . . . . .. . . .. . .. . 490
Table A-1. Object Import Control File Elements and Attributes (pmrep) . . . . . .. . . .. . .. . 498
Table A-2. Deployment Control File Elements and Attributes (pmrep) . . . . . . . .. . . .. . .. . 505
Table B-1. Required Privileges and Permissions for Designer Tasks . . . . . . . . . . .. . . .. . .. . 510
Table B-2. Required Privileges and Permissions for Workflow Manager Tasks . . .. . . .. . .. . 511
Table B-3. Required Privileges and Permissions for Workflow Monitor Tasks . . .. . . .. . .. . 513
Table B-4. Required Privileges and Permissions for pmcmd Tasks . . . . . . . . . . . .. . . .. . .. . 515
Table B-5. Required Permissions and Privileges for Repository Manager Tasks . .. . . .. . .. . 516
Table B-6. Required Permissions and Privileges for pmrep Tasks. . . . . . . . . . . . .. . . .. . .. . 519
Welcome to PowerCenter, Informatica’s software product that delivers an open, scalable data
integration solution addressing the complete life cycle for all data integration projects
including data warehouses and data marts, data migration, data synchronization, and
information hubs. PowerCenter combines the latest technology enhancements for reliably
managing data repositories and delivering information resources in a timely, usable, and
efficient manner.
The PowerCenter metadata repository coordinates and drives a variety of core functions,
including extracting, transforming, loading, and managing data. The PowerCenter Server can
extract large volumes of data from multiple platforms, handle complex transformations on the
data, and support high-speed loads. PowerCenter can simplify and accelerate the process of
moving data warehouses from development to test to production.
xxiii
New Features and Enhancements
This section describes new features and enhancements to PowerCenter 7.1.1, 7.1, and 7.0.
PowerCenter 7.1.1
This section describes new features and enhancements to PowerCenter 7.1.1.
Data Profiling
♦ Data sampling. You can create a data profile for a sample of source data instead of the
entire source. You can view a profile from a random sample of data, a specified percentage
of data, or for a specified number of rows starting with the first row.
♦ Verbose data enhancements. You can specify the type of verbose data you want the
PowerCenter Server to write to the Data Profiling warehouse. The PowerCenter Server can
write all rows, the rows that meet the business rule, or the rows that do not meet the
business rule.
♦ Session enhancement. You can save sessions that you create from the Profile Manager to
the repository.
♦ Domain Inference function tuning. You can configure the Data Profiling Wizard to filter
the Domain Inference function results. You can configure a maximum number of patterns
and a minimum pattern frequency. You may want to narrow the scope of patterns returned
to view only the primary domains, or you may want to widen the scope of patterns
returned to view exception data.
♦ Row Uniqueness function. You can determine unique rows for a source based on a
selection of columns for the specified source.
♦ Define mapping, session, and workflow prefixes. You can define default mapping,
session, and workflow prefixes for the mappings, sessions, and workflows generated when
you create a data profile.
♦ Profile mapping display in the Designer. The Designer displays profile mappings under a
profile mappings node in the Navigator.
PowerCenter Server
♦ Code page. PowerCenter supports additional Japanese language code pages, such as JIPSE-
kana, JEF-kana, and MELCOM-kana.
♦ Flat file partitioning. When you create multiple partitions for a flat file source session, you
can configure the session to create multiple threads to read the flat file source.
♦ pmcmd. You can use parameter files that reside on a local machine with the Startworkflow
command in the pmcmd program. When you use a local parameter file, pmcmd passes
variables and values in the file to the PowerCenter Server.
xxiv Preface
♦ SuSE Linux support. The PowerCenter Server runs on SuSE Linux. On SuSE Linux, you
can connect to IBM, DB2, Oracle, and Sybase sources, targets, and repositories using
native drivers. Use ODBC drivers to access other sources and targets.
♦ Reserved word support. If any source, target, or lookup table name or column name
contains a database reserved word, you can create and maintain a file, reswords.txt,
containing reserved words. When the PowerCenter Server initializes a session, it searches
for reswords.txt in the PowerCenter Server installation directory. If the file exists, the
PowerCenter Server places quotes around matching reserved words when it executes SQL
against the database.
♦ Teradata external loader. When you load to Teradata using an external loader, you can
now override the control file. Depending on the loader you use, you can also override the
error, log, and work table names by specifying different tables on the same or different
Teradata database.
Repository
♦ Exchange metadata with other tools. You can exchange source and target metadata with
other BI or data modeling tools, such as Business Objects Designer. You can export or
import multiple objects at a time. When you export metadata, the PowerCenter Client
creates a file format recognized by the target tool.
Repository Server
♦ pmrep. You can use pmrep to perform the following functions:
− Remove repositories from the Repository Server cache entry list.
− Enable enhanced security when you create a relational source or target connection in the
repository.
− Update a connection attribute value when you update the connection.
♦ SuSE Linux support. The Repository Server runs on SuSE Linux. On SuSE Linux, you
can connect to IBM, DB2, Oracle, and Sybase repositories.
Security
♦ Oracle OS Authentication. You can now use Oracle OS Authentication to authenticate
database users. Oracle OS Authentication allows you to log on to an Oracle database if you
have a logon to the operating system. You do not need to know a database user name and
password. PowerCenter uses Oracle OS Authentication when the user name for an Oracle
connection is PmNullUser.
Preface xxv
♦ Pipeline partitioning. You can create multiple partitions in a session containing web
service source and target definitions. The PowerCenter Server creates a connection to the
Web Services Hub based on the number of sources, targets, and partitions in the session.
XML
♦ Multi-level pivoting. You can now pivot more than one multiple-occurring element in an
XML view. You can also pivot the view row.
PowerCenter 7.1
This section describes new features and enhancements to PowerCenter 7.1.
Data Profiling
♦ Data Profiling for VSAM sources. You can now create a data profile for VSAM sources.
♦ Support for verbose mode for source-level functions. You can now create data profiles
with source-level functions and write data to the Data Profiling warehouse in verbose
mode.
♦ Aggregator function in auto profiles. Auto profiles now include the Aggregator function.
♦ Creating auto profile enhancements. 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.
♦ Purging data from the Data Profiling warehouse. You can now purge data from the Data
Profiling warehouse.
♦ Source View in the Profile Manager. You can now view data profiles by source definition
in the Profile Manager.
♦ PowerCenter Data Profiling report enhancements. You can now view PowerCenter Data
Profiling reports in a separate browser window, resize columns in a report, and view
verbose data for Distinct Value Count functions.
♦ Prepackaged domains. Informatica provides a set of prepackaged domains that you can
include in a Domain Validation function in a data profile.
Documentation
♦ Web Services Provider Guide. This is a new book that describes the functionality of Real-time
Web Services. It also includes information from the version 7.0 Web Services Hub Guide.
♦ XML User Guide. This book consolidates XML information previously documented in the
Designer Guide, Workflow Administration Guide, and Transformation Guide.
Licensing
Informatica provides licenses for each CPU and each repository rather than for each
installation. Informatica provides licenses for product, connectivity, and options. You store
xxvi Preface
the license keys in a license key file. You can manage the license files using the Repository
Server Administration Console, the PowerCenter Server Setup, and the command line
program, pmlic.
PowerCenter Server
♦ 64-bit support. You can now run 64-bit PowerCenter Servers on AIX and HP-UX
(Itanium).
♦ Partitioning enhancements. If you have the Partitioning option, you can define up to 64
partitions at any partition point in a pipeline that supports multiple partitions.
♦ PowerCenter Server processing enhancements. The PowerCenter Server now reads a
block of rows at a time. This improves processing performance for most sessions.
♦ CLOB/BLOB datatype support. You can now read and write CLOB/BLOB datatypes.
Repository Server
♦ Updating repository statistics. PowerCenter now identifies and updates statistics for all
repository tables and indexes when you copy, upgrade, and restore repositories. This
improves performance when PowerCenter accesses the repository.
♦ Increased repository performance. You can increase repository performance by skipping
information when you copy, back up, or restore a repository. You can choose to skip MX
data, workflow and session log history, and deploy group history.
♦ pmrep. You can use pmrep to back up, disable, or enable a repository, delete a relational
connection from a repository, delete repository details, truncate log files, and run multiple
pmrep commands sequentially. You can also use pmrep to create, modify, and delete a
folder.
Repository
♦ Exchange metadata with business intelligence tools. You can export metadata to and
import metadata from other business intelligence tools, such as Cognos Report Net and
Business Objects.
♦ Object import and export enhancements. You can compare objects in an XML file to
objects in the target repository when you import objects.
♦ MX views. MX views have been added to help you analyze metadata stored in the
repository. REP_SERVER_NET and REP_SERVER_NET_REF views allow you to see
information about server grids. REP_VERSION_PROPS allows you to see the version
history of all objects in a PowerCenter repository.
Preface xxvii
Transformations
♦ Flat file lookup. You can now perform lookups on flat files. When you create a Lookup
transformation using a flat file as a lookup source, the Designer invokes the Flat File
Wizard. You can also use a lookup file parameter if you want to change the name or
location of a lookup between session runs.
♦ Dynamic lookup cache enhancements. When you use a dynamic lookup cache, the
PowerCenter Server can ignore some ports when it compares values in lookup and input
ports before it updates a row in the cache. Also, you can choose whether the PowerCenter
Server outputs old or new values from the lookup/output ports when it updates a row. 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.
♦ Union transformation. You can use the Union transformation to merge multiple sources
into a single pipeline. The Union transformation is similar to using the UNION ALL SQL
statement to combine the results from two or more SQL statements.
♦ Custom transformation API enhancements. 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. Use these functions to take advantage of the
PowerCenter Server processing enhancements.
♦ Midstream XML transformations. You can now create an XML Parser transformation or
an XML Generator transformation to parse or generate XML inside a pipeline. The XML
transformations enable you to extract XML data stored in relational tables, such as data
stored in a CLOB column. You can also extract data from messaging systems, such as
TIBCO or IBM MQSeries.
Usability
♦ Viewing active folders. The Designer and the Workflow Manager highlight the active
folder in the Navigator.
♦ Enhanced printing. The quality of printed workspace has improved.
Version Control
You can run object queries that return shortcut objects. You can also run object queries based
on the latest status of an object. 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.
xxviii Preface
Note: PowerCenter Connect for Web Services allows you to create sources, targets, and
transformations to call web services hosted by other providers. For more informations, see
PowerCenter Connect for Web Services User and Administrator Guide.
Workflow Monitor
The Workflow Monitor includes the following performance and usability enhancements:
♦ When you connect to the PowerCenter Server, you no longer distinguish between online
or offline mode.
♦ You can open multiple instances of the Workflow Monitor on one machine.
♦ You can simultaneously monitor multiple PowerCenter Servers registered to the same
repository.
♦ The Workflow Monitor includes improved options for filtering tasks by start and end
time.
♦ The Workflow Monitor displays workflow runs in Task view chronologically with the most
recent run at the top. It displays folders alphabetically.
♦ You can remove the Navigator and Output window.
XML Support
PowerCenter XML support now includes the following features:
♦ Enhanced datatype support. You can use XML schemas that contain simple and complex
datatypes.
♦ Additional options for XML definitions. When you import XML definitions, you can
choose how you want the Designer to represent the metadata associated with the imported
files. You can choose to generate XML views using hierarchy or entity relationships. In a
view with hierarchy relationships, the Designer expands each element and reference under
its parent element. When you create views with entity relationships, the Designer creates
separate entities for references and multiple-occurring elements.
♦ Synchronizing XML definitions. You can synchronize one or more XML definition when
the underlying schema changes. You can synchronize an XML definition with any
repository definition or file used to create the XML definition, including relational sources
or targets, XML files, DTD files, or schema files.
♦ XML workspace. You can edit XML views and relationships between views in the
workspace. You can create views, add or delete columns from views, and define
relationships between views.
♦ Midstream XML transformations. You can now create an XML Parser transformation or
an XML Generator transformation to parse or generate XML inside a pipeline. The XML
transformations enable you to extract XML data stored in relational tables, such as data
stored in a CLOB column. You can also extract data from messaging systems, such as
TIBCO or IBM MQSeries.
Preface xxix
♦ Support for circular references. Circular references occur when an element is a direct or
indirect child of itself. PowerCenter now supports XML files, DTD files, and XML
schemas that use circular definitions.
♦ Increased performance for large XML targets. You can create XML files of several
gigabytes in a PowerCenter 7.1 XML session by using the following enhancements:
− Spill to disk. You can specify the size of the cache used to store the XML tree. If the size
of the tree exceeds the cache size, the XML data spills to disk in order to free up
memory.
− User-defined commits. You can define commits to trigger flushes for XML target files.
− Support for multiple XML output files. You can output XML data to multiple XML
targets. You can also define the file names for XML output files in the mapping.
PowerCenter 7.0
This section describes new features and enhancements to PowerCenter 7.0.
Data Profiling
If you have the Data Profiling option, you can profile source data to evaluate source data and
detect patterns and exceptions. For example, you can determine implicit data type, suggest
candidate keys, detect data patterns, and evaluate join criteria. After you create a profiling
warehouse, you can create profiling mappings and run sessions. Then you can view reports
based on the profile data in the profiling warehouse.
The PowerCenter Client provides a Profile Manager and a Profile Wizard to complete these
tasks.
Documentation
♦ Glossary. The Installation and Configuration Guide contains a glossary of new PowerCenter
terms.
♦ Installation and Configuration Guide. 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.”
♦ Upgrading metadata. The Installation and Configuration Guide now contains a chapter
titled “Upgrading Repository Metadata.” This chapter describes changes to repository
xxx Preface
objects impacted by the upgrade process. The change in functionality for existing objects
depends on the version of the existing objects. Consult the upgrade information in this
chapter for each upgraded object to determine whether the upgrade applies to your current
version of PowerCenter.
Functions
♦ Soundex. The Soundex function encodes a string value into a four-character string.
SOUNDEX works for characters in the English alphabet (A-Z). 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. The Metaphone function encodes string values. You can specify the length of
the string that you want to encode. METAPHONE encodes characters of the English
language alphabet (A-Z). It encodes both uppercase and lowercase letters in uppercase.
Installation
♦ Remote PowerCenter Client installation. You can create a control file containing
installation information, and distribute it to other users to install the PowerCenter Client.
You access the Informatica installation CD from the command line to create the control
file and install the product.
PowerCenter Server
♦ DB2 bulk loading. You can enable bulk loading when you load to IBM DB2 8.1.
♦ Distributed processing. If you purchase the Server Grid option, you can group
PowerCenter Servers registered to the same repository into a server grid. In a server grid,
PowerCenter Servers balance the workload among all the servers in the grid.
♦ Row error logging. The session configuration object has new properties that allow you to
define error logging. You can choose to log row errors in a central location to help
understand the cause and source of errors.
♦ External loading enhancements. When using external loaders on Windows, you can now
choose to load from a named pipe. When using external loaders on UNIX, you can now
choose to load from staged files.
Preface xxxi
♦ External loading using Teradata Warehouse Builder. You can use Teradata Warehouse
Builder to load to Teradata. You can choose to insert, update, upsert, or delete data.
Additionally, Teradata Warehouse Builder can simultaneously read from multiple sources
and load data into one or more tables.
♦ Mixed mode processing for Teradata external loaders. You can now use data driven load
mode with Teradata external loaders. When you select data driven loading, the
PowerCenter Server flags rows for insert, delete, or update. It writes a column in the target
file or named pipe to indicate the update strategy. The control file uses these values to
determine how to load data to the target.
♦ Concurrent processing. The PowerCenter Server now reads data concurrently from
sources within a target load order group. This enables more efficient joins with minimal
usage of memory and disk cache.
♦ Real time processing enhancements. You can now use real-time processing in sessions that
also process active transformations, such as the Aggregator transformation. You can apply
the transformation logic to rows defined by transaction boundaries.
Repository Server
♦ Object export and import enhancements. You can now export and import objects using
the Repository Manager and pmrep. You can export and import multiple objects and
objects types. You can export and import objects with or without their dependent objects.
You can also export objects from a query result or objects history.
♦ pmrep commands. You can use pmrep to perform change management tasks, such as
maintaining deployment groups and labels, checking in, deploying, importing, exporting,
and listing objects. You can also use pmrep to run queries. The deployment and object
import commands require you to use a control file to define options and resolve conflicts.
♦ Trusted connections. You can now use a Microsoft SQL Server trusted connection to
connect to the repository.
Security
♦ LDAP user authentication. You can now use default repository user authentication or
Lightweight Directory Access Protocol (LDAP) to authenticate users. If you use LDAP, the
repository maintains an association between your repository user name and your external
login name. When you log in to the repository, the security module passes your login name
to the external directory for authentication. The repository maintains a status for each
user. You can now enable or disable users from accessing the repository by changing the
status. You do not have to delete user names from the repository.
♦ Use Repository Manager privilege. The Use Repository Manager privilege allows you to
perform tasks in the Repository Manager, such as copy object, maintain labels, and change
object status. You can perform the same tasks in the Designer and Workflow Manager if
you have the Use Designer and Use Workflow Manager privileges.
♦ Audit trail. You can track changes to repository users, groups, privileges, and permissions
through the Repository Server Administration Console. The Repository Agent logs
security changes to a log file stored in the Repository Server installation directory. The
xxxii Preface
audit trail log contains information, such as changes to folder properties, adding or
removing a user or group, and adding or removing privileges.
Transformations
♦ Custom transformation. Custom transformations operate in conjunction with procedures
you create outside of the Designer interface to extend PowerCenter functionality. The
Custom transformation replaces the Advanced External Procedure transformation. You can
create Custom transformations with multiple input and output groups, and you can
compile the procedure with any C compiler.
You can create templates that customize the appearance and available properties of a
Custom transformation you develop. You can specify the icons used for transformation,
the colors, and the properties a mapping developer can modify. When you create a Custom
transformation template, distribute the template with the DLL or shared library you
develop.
♦ Joiner transformation. You can use the Joiner transformation to join two data streams that
originate from the same source.
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 allows you to maintain
multiple versions of an object, control development on the object, track changes, and use
deployment groups to copy specific groups of objects from one repository to another. Version
control in PowerCenter includes the following features:
♦ Object versioning. Individual objects in the repository are now versioned. This allows you
to store multiple copies of a given object during the development cycle. Each version is a
separate object with unique properties.
♦ Check out and check in versioned objects. You can check out and reserve an object you
want to edit, and check in the object when you are ready to create a new version of the
object in the repository.
♦ Compare objects. The Repository Manager and Workflow Manager allow you to compare
two repository objects of the same type to identify differences between them. You can
compare Designer objects and Workflow Manager objects in the Repository Manager. You
can compare tasks, sessions, worklets, and workflows in the Workflow Manager. The
PowerCenter Client tools allow you to compare objects across open folders and
repositories. You can also compare different versions of the same object.
♦ Delete or purge a version. You can delete an object from view and continue to store it in
the repository. You can recover or undelete deleted objects. If you want to permanently
remove an object version, you can purge it from the repository.
♦ Deployment. Unlike copying a folder, 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.
Preface xxxiii
♦ Deployment groups. You can create a deployment group that contains references to
objects from multiple folders across the repository. You can create a static deployment
group that you manually add objects to, or create a dynamic deployment group that uses a
query to populate the group.
♦ Labels. A label is an object that you can apply to versioned objects in the repository. This
allows you to associate multiple objects in groups defined by the label. You can use labels
to track versioned objects during development, improve query results, and organize groups
of objects for deployment or export and import.
♦ Queries. You can create a query that specifies conditions to search for objects in the
repository. You can save queries for later use. You can make a private query, or you can
share it with all users in the repository.
♦ Track changes to an object. 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. This allows you
to see the changes made to an object over time.
XML Support
PowerCenter contains XML features that allow you to validate an XML file against an XML
schema, declare multiple namespaces, use XPath to locate XML nodes, increase performance
for large XML files, format your XML file output for increased readability, and parse or
generate XML data from various sources. XML support in PowerCenter includes the
following features:
♦ XML schema. You can use an XML schema to validate an XML file and to generate source
and target definitions. XML schemas allow you to declare multiple namespaces so you can
use prefixes for elements and attributes. XML schemas also allow you to define some
complex datatypes.
♦ XPath support. The XML wizard allows you to view the structure of XML schema. You
can use XPath to locate XML nodes.
♦ Increased performance for large XML files. When you process an XML file or stream, 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.
♦ XML target enhancements. You can format the XML target file so that you can easily view
the XML file in a text editor. You can also configure the PowerCenter Server to not output
empty elements to the XML target.
Usability
♦ Copying objects. You can now copy objects from all the PowerCenter Client tools using
the copy wizard to resolve conflicts. You can copy objects within folders, to other folders,
and to different repositories. Within the Designer, you can also copy segments of
mappings to a workspace in a new folder or repository.
♦ Comparing objects. You can compare workflows and tasks from the Workflow Manager.
You can also compare all objects from within the Repository Manager.
xxxiv Preface
♦ Change propagation. When you edit a port in a mapping, you can choose to propagate
changed attributes throughout the mapping. The Designer propagates ports, expressions,
and conditions based on the direction that you propagate and the attributes you choose to
propagate.
♦ Enhanced partitioning interface. The Session Wizard is enhanced to provide a graphical
depiction of a mapping when you configure partitioning.
♦ Revert to saved. You can now revert to the last saved version of an object in the Workflow
Manager. When you do this, the Workflow Manager accesses the repository to retrieve the
last-saved version of the object.
♦ Enhanced validation messages. The PowerCenter Client writes messages in the Output
window that describe why it invalidates a mapping or workflow when you modify a
dependent object.
♦ Validate multiple objects. You can validate multiple objects in the repository without
fetching them into the workspace. 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,
mappings, mapplets, workflows, and worklets.
♦ View dependencies. Before you edit or delete versioned objects, such as sources, targets,
mappings, or workflows, you can view dependencies to see the impact on other objects.
You can view parent and child dependencies and global shortcuts across repositories.
Viewing dependencies help you modify objects and composite objects without breaking
dependencies.
♦ Refresh session mappings. In the Workflow Manager, you can refresh a session mapping.
Preface xxxv
About Informatica Documentation
The complete set of documentation for PowerCenter includes the following books:
♦ Data Profiling Guide. Provides information about how to profile PowerCenter sources to
evaluate source data and detect patterns and exceptions.
♦ Designer Guide. Provides information needed to use the Designer. Includes information to
help you create mappings, mapplets, and transformations. Also includes a description of
the transformation datatypes used to process and transform source data.
♦ Getting Started. Provides basic tutorials for getting started.
♦ Installation and Configuration Guide. Provides information needed to install and
configure the PowerCenter tools, including details on environment variables and database
connections.
♦ PowerCenter Connect® for JMS® User and Administrator Guide. Provides information
to install PowerCenter Connect for JMS, build mappings, extract data from JMS messages,
and load data into JMS messages.
♦ Repository Guide. Provides information needed to administer the repository using the
Repository Manager or the pmrep command line program. Includes details on
functionality available in the Repository Manager and Administration Console, such as
creating and maintaining repositories, folders, users, groups, and permissions and
privileges.
♦ Transformation Language Reference. Provides syntax descriptions and examples for each
transformation function provided with PowerCenter.
♦ Transformation Guide. Provides information on how to create and configure each type of
transformation in the Designer.
♦ Troubleshooting Guide. Lists error messages that you might encounter while using
PowerCenter. Each error message includes one or more possible causes and actions that
you can take to correct the condition.
♦ Web Services Provider Guide. Provides information you need to install and configure the Web
Services Hub. This guide also provides information about how to use the web services that the
Web Services Hub hosts. The Web Services Hub hosts Real-time Web Services, Batch Web
Services, and Metadata Web Services.
♦ Workflow Administration Guide. Provides information to help you create and run
workflows in the Workflow Manager, as well as monitor workflows in the Workflow
Monitor. Also contains information on administering the PowerCenter Server and
performance tuning.
♦ XML User Guide. Provides information you need to create XML definitions from XML,
XSD, or DTD files, and relational or other XML definitions. Includes information on
running sessions with XML data. Also includes details on using the midstream XML
transformations to parse or generate XML data within a pipeline.
xxxvi Preface
About this Book
The Repository Guide is written for the database administrator and developers who manage the
repositories. This guide assumes you have knowledge of relational database concepts, and the
database engines, flat files, or mainframe systems in your environment. You should also be
familiar with the interface requirements of your supporting applications. For additional
information on related database connectivity issues not covered by this guide, refer to the
documentation accompanying your database products.
The material in this book is available for online use.
Document Conventions
This guide uses the following formatting conventions:
italicized monospaced text This is the variable name for a value you enter as part of an
operating system command. This is generic text that should be
replaced with user-supplied values.
Warning: The following paragraph notes situations where you can overwrite
or corrupt data, unless you follow the specified procedure.
bold monospaced text This is an operating system command you enter from a prompt to
run a task.
Preface xxxvii
Other Informatica Resources
In addition to the product manuals, Informatica provides these other resources:
♦ Informatica Customer Portal
♦ Informatica Webzine
♦ Informatica web site
♦ Informatica Developer Network
♦ Informatica Technical Support
xxxviii Preface
The site contains information on how to create, market, and support customer-oriented add-
on solutions based on Informatica’s interoperability interfaces.
Belgium
Phone: +32 15 281 702
Hours: 9 a.m. - 5:30 p.m. (local time)
France
Phone: +33 1 41 38 92 26
Hours: 9 a.m. - 5:30 p.m. (local time)
Germany
Phone: +49 1805 702 702
Hours: 9 a.m. - 5:30 p.m. (local time)
Netherlands
Phone: +31 306 082 089
Hours: 9 a.m. - 5:30 p.m. (local time)
Singapore
Phone: +65 322 8589
Hours: 9 a.m. - 5 p.m. (local time)
Switzerland
Phone: +41 800 81 80 70
Hours: 8 a.m. - 5 p.m. (local time)
Preface xxxix
xl Preface
Chapter 1
Understanding the
Repository
This chapter covers the following topics:
♦ Overview, 2
♦ Repository Architecture, 3
♦ Repository Connectivity, 4
♦ Repository Server Notifications, 6
♦ Understanding Metadata, 9
♦ Administering Repositories, 11
♦ PowerCenter Domains, 13
♦ Version Control, 16
1
Overview
The PowerCenter repository is a relational database managed by the Repository Server that
stores information, or metadata, used by the PowerCenter Server and Client tools.
The repository uses database tables to store metadata. Metadata describes different types of
objects, such as mappings or transformations, that you can create or modify using the
PowerCenter Client tools. The PowerCenter Server uses repository objects to extract,
transform, and load data. The repository also stores administrative information such as user
names, passwords, permissions, and privileges.
All repository client applications access the repository database tables through the Repository
Server. The Repository Server protects metadata in the repository by managing repository
connections and using object locking to ensure object consistency. The Repository Server also
notifies you when objects you are working with are modified or deleted by another user.
For each repository database it manages, the Repository Server uses a process called the
Repository Agent to access the database tables. The Repository Server uses multiple
Repository Agent processes to manage multiple repositories on different machines on the
network.
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. When a client application connects to the repository, the Repository
Server connects the client application directly to the Repository Agent process.
Administer the repository using the Repository Manager client tool or the pmrep and
pmrepagent command line programs. Repository administration tasks include the following:
♦ Back up. You can back up the repository to a binary file.
♦ Restore. You can restore the repository from a binary backup file.
♦ Copy. You can copy the repository to another database.
♦ Delete. You can delete all of the repository tables on the database.
♦ Create folders. You can create folders in the repository to organize metadata.
♦ Configure security. You can create user and group profiles and configure folder
permissions.
You can connect multiple repositories in a domain. When you configure shared folders in a
repository, you can share the objects in the folder with other repositories in the domain.
Sharing objects allows you to reuse metadata.
If you purchase the Team-Based Development option with PowerCenter, you can enable the
repository for version control. You can store multiple versions of objects in a versioned
repository. Enabling version control also allows you to perform change management tasks
such as version comparison, change tracking, labeling, querying, and deployment.
Repository Architecture 3
Repository Connectivity
PowerCenter applications such as the PowerCenter Client, PowerCenter Server, pmrep, and
pmrepagent connect to the repository through the Repository Server.
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 Server stores the connectivity information required for the Repository Agent
process to connect to the repository database. The Repository Server uses one Repository
Agent process for each repository database. The Repository Agent process uses native drivers
to communicate directly with the repository database.
The Repository Agent maintains a pool of database connections for client applications. These
connections remain open, and the Repository Agent re-uses them to service requests from
client tools or the server. Each client tool opens a separate connection to the Repository Agent
process. The Repository Agent process supports multiple connections from each client. The
PowerCenter Server opens additional connections to the Repository Agent process for each
Load Manager and DTM process.
The Repository Agent creates new database connections only if all the current connections are
in use. For example, if ten clients send requests to the Repository Agent one at a time, it
requires only one connection. It reuses the same database connection for all the requests. If
the ten clients send requests simultaneously, the Repository Agent opens ten connections. You
can set the maximum number of open connections for a repository by setting the Database
Pool Size parameter in the repository configuration file.
Figure 1-1 illustrates the connectivity between the Repository Server, repository database, and
repository client applications:
Repository Connectivity 5
Repository Server Notifications
The Repository Server sends notification messages when users create, modify, or delete
repository objects. Each PowerCenter Client tool and the PowerCenter Server receive
notification messages for different types of objects.
Repository Server notification messages keep you informed of ongoing changes to metadata
you are working with. For example, suppose you are working with a mapping in the Designer.
Another user opens and edits the properties of a source definition used in the mapping and
save the changes to the repository. The Repository Server notifies you of the change so that
you know the source in your mapping is out of date. In this case, you can update the mapping
with the version of the source definition saved in the repository. For more information, see
“Mappings” in the Designer Guide.
Understanding Metadata 9
For details on using the Designer to work with repository objects, see the Designer Guide and
the Transformation Guide.
Use the Workflow Manager to create and edit the following repository objects:
♦ Database connections. The PowerCenter Client and Server use database connections to
connect to the source and target databases.
♦ Connection objects. You create connection objects in the repository when you define
database, FTP, and external loader connections in the Workflow Manager.
♦ Sessions. Sessions are workflow tasks that contain information about how the
PowerCenter Server moves data through mappings. You create a session for each mapping
you want to run. To run the session, place it in a workflow. Use the Workflow Designer in
the Workflow Manager to create sessions.
♦ Workflows. A workflow is a set of instructions, divided into tasks, the PowerCenter Server
uses to extract, transform, and load data.
♦ Workflow tasks. Workflow tasks are instructions the PowerCenter Server executes when
running a workflow. Workflow tasks perform functions supplementary to extracting,
transforming, and loading data. Workflow tasks include commands, decisions, timers, and
email notification.
♦ Worklets. Worklets are objects that represent a set of workflow tasks that allow you to
reuse a set of workflow logic in several workflows. You can run worklets in workflows, and
nest worklets in other worklets.
For details on working with repository objects using the Workflow Manager, see the Workflow
Administration Guide.
Use the Repository Manager to create and edit the following repository objects:
♦ Folders. Folders organize and store metadata in the repository. You can control access to a
folder by configuring the folder permissions. You can also configure a folder to share
stored metadata with other repository users.
♦ Users. Repository users have a user name and password that allow access to the repository.
You can also configure a repository user with privileges that allow the user to perform
specific tasks in the repository. Each repository user belongs to at least one user group.
♦ User groups. User groups organize individual repository users. You can assign privileges to
a user group. Individual users inherit all privileges assigned to the user group.
If you enable version control, PowerCenter allows you to store multiple versions of metadata
objects in the repository. For details on version control and change management, see “Version
Control” on page 16.
PowerCenter also allows you to extend the metadata stored in the repository by associating
information with repository objects. For example, when someone in your company creates a
source definition, you may wish to store the name of that person with the source definition. You
associate information with repository metadata using metadata extensions. For details on using
metadata extensions, see “Metadata Extensions” on page 325.
Creating Folders
After you create the repository, you can add folders to it. Folders let you organize repository
objects, providing a way to separate different types of metadata or different projects into easily
identifiable areas. You can configure a folder to be shared, so its contents are available to all
other folders in the same repository. If you plan to use the same object in several projects, you
might put it in the shared folder.
For example, you can put a definition of the CUSTOMERS table that provides data for a
variety of purposes in a shared folder. You can make shortcuts to the table in other folders in
the same repository. If you are working in a domain, you can also make shortcuts to the table
in folders in local repositories registered to the repository.
For details on working with folders, see “Working with Folders” on page 165.
Security
To secure data in your repository, the repository provides a system of users, user groups,
repository privileges, folder permissions, and object locking. After you create a repository, set
up users and user groups and determine the repository privileges you want them to have.
When you create a folder, you designate a user as the owner of the folder, and then assign
different folder permissions to that user, the user’s group, and others accessing the repository.
Administering Repositories 11
Privileges permit or restrict the ability for users to perform tasks such as creating mappings,
running sessions, or backing up the repository. Permissions permit or restrict access to folders
and objects in the repository.
For details on configuring repository security, see “Repository Security” on page 125.
PowerCenter Domains 13
Connecting separate repositories into a domain is a three-step process:
1. Create a repository and configure it as a global repository.
You create a global repository by promoting an existing local repository. Once you make a
repository a global repository, you cannot demote it to a local repository.
For details on creating and configure a repository, see “Creating or Promoting a
Repository” on page 116.
2. Register other repositories with the global repository.
Once the local repository is registered, you can connect to the global repository from the
local repository, and to the local repository from the global.
For details on registering repositories, see “Registering a PowerCenter Repository” on
page 75.
3. Create user profiles for users performing cross-repository work.
A user who needs to connect to multiple repositories must have an identical repository
user name and password in each repository. Although the user name and password must
remain the same, the user can be a member of different user groups and can have a
completely different set of privileges in each repository.
For details on creating user profiles and configuring repository security, see “Repository
Security” on page 125.
Reusing Metadata
In a domain you frequently need to share metadata across repositories. PowerCenter provides
a mechanism for sharing metadata among multiple repositories.
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. For example, a sales
division develops a standard calculation for the profitability of each product. This calculation
is likely to be complex, based on variables such as production costs and marketing expenses.
Since profitability is important information when investing in product development, building
a sales strategy, or making other decisions, you need everyone in all parts of the organization
to use the same calculation. If you can share the profitability calculation, you can be sure that
everyone looks at the value of each product to the company in the same way.
When you develop the component of a mapping that performs this calculation, you might
want to reuse it in other mappings, even in other repositories. The profitability calculation
might appear in several mappings in the sales division repository. The R&D, marketing, and
accounting divisions also need to use the same calculation in many mappings in their
repositories.
Reusing Data
The need to share data is just as pressing as the need to share metadata. Often, several
departments in the same organization need the same information. For example, each
department may need to read the same product data from operational sources, perform the
same profitability calculations, and format this information to make it easy to review.
If each department reads, transforms, and writes this product data separately, the throughput
for the entire organization is lower than it could be. A more efficient approach would be to
read, transform, and write the data to one central data store shared by all users.
A central data store improves throughput at the level of the entire enterprise. To improve
performance further, you might want to capture incremental changes to sources. For example,
rather than reading all the product data each time you update the central data store, you can
improve performance by capturing only the inserts, deletes, and updates that have occurred in
the PRODUCTS table since the last time you updated the central data store.
The central data store also allows you to format data in a standard fashion. For example, you
can filter employee data that should remain confidential. Or you can display date and time
values in a standard format. You can perform these and other data cleansing tasks when you
move data into the central data store instead of performing them repeatedly.
PowerCenter Domains 15
Version Control
If you have the Team-Based Development option, you can enable version control for the
repository. A versioned repository can store multiple copies, or versions, of an object. Each
version is a separate object with unique properties. PowerCenter version control features allow
you to efficiently develop, test, and deploy metadata into production.
During development, 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 check out and reserve an object you
want to edit, and check in the object when you are ready to create a new version of the
object in the repository.
♦ Compare objects. The Repository Manager, Workflow Manager, and Designer allow you
to compare two repository objects of the same type to identify differences between them.
The PowerCenter Client tools allow you to compare objects across open folders and
repositories. You can also compare different versions of the same object.
♦ Track changes to an object. You can view an object history that includes all versions of the
object. You can also compare any version of the object in the history to any other version.
This allows you to see the changes made to an object over time.
♦ Delete or purge a version. You can delete an object from view and continue to store it in
the repository. You can recover, or undelete, deleted objects. If you want to permanently
remove an object version, you can purge it from the repository.
For more information on working with versioned objects, see “Working with Versioned
Objects” on page 199.
You can use the following features to group versioned objects:
♦ Labels. A label is an object that you can apply to versioned objects in the repository. This
allows you to associate multiple objects in groups defined by the label. You can use labels
to track versioned objects during development, mark development milestones, improve
query results, and organize groups of objects for deployment or import and export.
♦ Queries. You can create a query that specifies conditions to search for objects in the
repository. You can save queries for later use. You can make a private query, or you can
share it with all users in the repository.
♦ Deployment groups. You can create a deployment group that contains references to
objects from multiple folders across the repository. You can create a static deployment
group that you manually add objects to, or create a dynamic deployment group that uses a
query to populate the group. You can also roll back a deployment operation.
For more information on grouping versioned objects, see “Grouping Versioned Objects” on
page 217.
You can copy objects in a deployment group from one repository to another. Unlike copying a
folder, copying a deployment group allows you to copy one or more objects from multiple
folders in the source repository to multiple folders in the target repository. You can also
choose to copy part of a composite object, provided that the object is present in the target
Version Control 17
18 Chapter 1: Understanding the Repository
Chapter 2
19
Overview
The Repository Manager allows you to navigate through multiple folders and repositories and
perform basic repository tasks.
Overview 21
Repository Manager Windows
The Repository Manager has a main window and a status bar for information on the
operation you are performing. The Repository Manager can display the following windows:
♦ Navigator
♦ Main
♦ Dependency
♦ Output
Figure 2-1 shows the Repository Manager components:
Navigator
Window
Dependency
Window
Output
Window
Status Bar
Main Window
When the Repository Manager accesses the repository, the Status Bar reflects the connection
in progress with a progress indicator.
Progress Indicator
To display a window:
To close a window:
♦ Click the small x in the upper right corner of the window.
Navigator Window
Use the Navigator window to connect to a repository and navigate through the folders and
objects in the repository. The Navigator window displays the following objects when they
exist in the repository:
♦ Repositories. PowerCenter repositories can be standalone, local, or global.
♦ Deployment groups. Deployment groups contain collections of objects for deployment to
another repository in the domain.
♦ Folders. Folders can be shared or not shared.
♦ Nodes. Nodes can include sessions, sources, targets, transformations, mapplets, workflows,
tasks, worklets, and mappings.
♦ Repository objects. Repository objects displayed in the Navigator can include sources,
targets, transformations, mappings, mapplets, sessions, tasks, workflows, worklets,
workflow logs, and session logs.
Repositories
Deployment
Groups
Shared Folder
Mappings
Nodes
Workflows
Viewing Properties
You can view the properties of the objects in the Navigator by selecting the object, and then
clicking the View Properties button in the toolbar. You can also right-click the object in the
Navigator and select Properties from the shortcut menu. For more information about object
properties, see “Viewing Version Properties” on page 203.
Note: If you enable versioning when you create the repository, you can view all tabs on the
Properties dialog box.
Main Window
The Main window of the Repository Manager displays details about the object selected in the
Navigator. For example, if you select a repository in the Navigator, the Main window displays
all the folders in the repository along with additional folder information, such as whether the
folder is shared or in use.
Repository Node Displays properties for each folder in the selected repository.
Deployment Displays properties for each deployment group in the selected repository. Select a static
Groups Node deployment group to view details for deployment group objects.
Sources Node Displays the properties for each source within the selected node. Select a source definition to
view details for each port in the selected source definition.
Targets Node Displays the properties for each target with the selected node. Select a target definition to view
details for each target definition port.
Transformations Displays the properties for each reusable transformation in the selected node. Select a
Node transformation to view details for the specified transformation ports.
Mapplets Node Displays the properties for each mapplet in the selected node. Select a mapplet to view the
Transformations node containing the mapplet.
Mappings Node Displays the properties for each mapping in the node. Select a mapping to view sources, targets,
and transformation nodes that contain the sources, targets, and transformations used in the
mapping. Select a target in a mapping to view details for each port in the selected target
definition.
Tasks Node Displays properties for each task in the selected node. Select a task to view the task details.
Sessions Node Displays properties for each session in the folder. Select a session to view session logs, source
connections and target connections nodes for the selected session. The Main window also
displays information about pre- and post-session email and commands.
Worklets Node Displays properties for each worklet in the folder. Select a worklet to view the nodes for sessions,
tasks, and other objects associated with the worklet.
Workflows Node Displays properties for each workflow in the folder. Select a workflow to view information for
tasks and objects associated with the selected workflow.
Workflow Logs Displays workflow log information for the selected workflow. The Workflow Logs node displays
Node under each workflow in the Workflows node.
Session Logs Node Displays session log information for the selected session. The Sessions Logs node displays
under each session in the Sessions node.
Source Displays connection properties for each source connection associated with the session. The
Connections Node Source Connections node displays under each session in the Sessions node and under each
session associated with a workflow under the Workflows node.
Source File Displays properties for each source file associated with the session. The Source File
Connections Node Connections node displays under each session in the Sessions node and under each session
associated with a workflow under the Workflows node.
Target Connections Displays connection properties for each target connection associated with the session. The
Node Target Connections node displays under each session in the Sessions node and under each
session associated with a workflow under the Workflows node.
Target File Displays properties for each target file associated with the session. The Target File Connections
Connections Node node displays under each session in the Sessions node and under each session associated with
a workflow under the Workflows node.
Transformation Displays log details for each transformation in the session when you select the Transformation
Logs Node Logs node.
Dependency Window
The Dependency window appears when you configure the Repository Manager to display
dependencies. You can view dependencies by using the menu items or the dependency
buttons on the toolbar.
You can also view dependencies using the Dependency dialog box. For information on using
the Dependency dialog box, see “Viewing Object Dependencies” on page 37.
When viewing dependencies, the left pane of the Dependency window lists the object for
which you want dependency information, and the dependency information appears in the
right pane of the window.
Figure 2-4 shows the Dependency window:
Output Window
When possible, the Repository Manager displays status messages in the status bar. With more
complex operations, however, the Repository Manager displays detailed information in the
Output window.
For example, when you connect to a repository, the status bar displays the following message:
Accessing the repository...
Once connected to the repository, the status bar displays the word Ready.
When you perform a more lengthy operation, such as copying a folder, the Repository
Manager writes details about the operation into the Output window.
Figure 2-5 shows the Output window:
You can change the font type and size displayed in the output window by right-clicking the
window and selecting Change Font.
Adding a Repository
Add a repository when a repository already exists but does not appear in the Navigator of the
PowerCenter Client. After adding a repository, you can connect to it. For details on
connecting to a repository, see “Connecting to a Repository” on page 30.
Adding a repository to the Navigator window does not create the repository. For details on
creating a repository, see “Creating or Promoting a Repository” on page 116.
To add a repository:
Removing a Repository
When you remove a repository, you remove it from the Navigator of the PowerCenter Client.
The repository remains intact, but you can no longer access it. After you remove a repository,
you can reverse your action by adding it.
1. In the Navigator of the Repository Manager, select the repository you want to remove.
2. Press Delete.
After you remove a repository from the Navigator, you can also remove it from the
PowerCenter Client registry. To reverse this action, you need to add the repository and
reconfigure the connection information.
1. In the Navigator of the Repository Manager, select the repository you want to remove.
2. Choose Tools-Remove Repository.
3. Select the repository you want to remove, and click Delete.
4. When a message box appears, click OK to remove the repository.
Connecting to a Repository
You can connect to a repository for the first time or connect to a repository you have
previously accessed.
4. Enter the database user name and password used to create the repository.
6. Enter the host name of the machine the Repository Server is running on and the port
number the Repository Server uses for connections.
7. Click Connect.
The Repository Server now opens a connection to the database, and a new icon representing
the repository appears in the Repository Manager. Folders within the repository now appear
underneath the icon for that repository.
Option Description
Exact Match If selected, the Repository Manager only looks for the entire keyword
entered. If not selected, the Repository Manager looks for keywords that
contain the keyword entered. For example, if you enter REPOS without
selecting the Exact Match option, the search would return a keyword match
for REPOSITORY.
Ignore Case If selected, the Repository Manager does not try to match the case of the
keyword entered. Otherwise, the keyword search is case-sensitive.
5. Click OK.
The Repository Manager now searches for matching keywords in all target definitions in
the repository. The screen splits, displaying the list of matching keywords in the bottom
window.
Sources Mapplet Designer - Sources within the same folder that reference the source through
Mapping Designer a foreign key relationship.
Source Analyzer - Global and local shortcuts to the source.
Targets Mapping Designer - Targets within the same folder that reference the target through a
Warehouse Designer foreign key relationship.
- Global and local shortcuts to the target.
You can view object dependencies in the Workflow Manager and Designer when you work
with objects in the workspace. You can view object dependencies when you open objects in
the following tools:
♦ Mapping Designer
♦ Mapplet Designer
♦ Workflow Designer
♦ Worklet Designer
The Dependencies dialog box displays the object name, object type, and a list of dependent
objects and their properties.
When you search for dependencies, you can filter the results by selecting options and object
types.
Table 2-3 shows the options you can select when you search for dependencies:
Option Description
All Parents View the objects that use the selected object. For example, if you
search for the parent objects for a session, the results might include a
workflow or worklet.
All Children View the objects that the selected object uses. For example, if you
search for the child objects for a workflow, the results might include
sessions and worklets.
PK/FK Dependencies View primary and source object dependencies where there is a primary
key-foreign key relationship.
Go Across Repositories View global shortcuts across repositories. You can select this option
when you search for parents, children, or primary key-foreign key
dependencies.
When you search for dependencies, the results window displays the properties for each
dependent object.
Object
Properties
Output
Window
Comments
Window
Labels
Window
Table 2-4 describes the object properties that display in the View Dependencies window:
Properties Description
Group Name DBD associated with the source of the object. For example, the group
type can be Oracle, DB2, or XML.
Object Type The type of dependent object. Dependent objects can be any of the
following types:
- Foreign key dependency
- Shortcuts
- Mappings
- Mapplets
- Sessions
- Workflows
- Worklets
- Target definition
- Source definition
Properties Description
Folder Name The folder name where the dependent object resides.
Host Name Host name for the machine hosting the object.
The View Dependencies window also displays output, comments, and label information
associated with the object. The Output window displays validation information, and the
Comments window displays text entered during object check in or check out. The Labels
window displays labels associated with the object and information associated with the label
object.
To save the list of dependent objects as an HTML file, choose File-Save to File.
Figure 2-8 shows an example of the HTML file saved from a View Dependencies window:
Table 2-5 describes the information that displays in the Validate Objects window.
Properties Description
Objects provided for The total number of objects that you selected to validate. The total
validation includes skipped objects.
Objects that were invalid The number of invalid objects provided for validation.
before the validation
Objects still invalid The number of objects that require fixing or editing.
Saved/checked in objects The total number of objects saved. If you do not choose the Save
Objects or Check In Objects options, this number is zero.
Cannot save objects due The number of validated objects you cannot save because someone
to lock conflict has them locked.
4. Click Compare.
If you choose a Designer object, such as a source, the Sources window shows the result of
comparing two sources:
View object
differences.
Compare
object
instances.
Differences between
objects are highlighted
and the nodes are
flagged.
Differences
between object
properties are
marked.
Displays the
properties of the
node you select.
1. In the Repository Manager, select the workflow in the Navigator window or in the Main
window.
2. Choose Edit-Truncate Log.
The Truncate Workflow Log dialog box appears.
3. Choose whether you want to delete all workflow and session log entries, or all workflow
and session log entries with an end time older than a certain date.
4. If you want to delete all entries older than a certain date, enter the date and time.
5. Click OK. The Repository Server deletes the workflow and session log entries from the
repository.
49
Overview
The PowerCenter repository is a collection of database tables containing metadata. The
Repository Server manages repositories. The Repository Server performs all metadata
transactions between the repository database and repository client applications. A Repository
Server can manage multiple repositories. You use the Repository Server Administration
Console to create and administer the repository through the Repository Server.
You can use the Administration Console to perform the following tasks:
♦ Add, edit, and remove repository configurations.
♦ Export and import repository configurations.
♦ Edit repository license files.
♦ Create a repository.
♦ Promote a local repository to a global repository.
♦ Copy a repository.
♦ Delete a repository from the database.
♦ Back up and restore a repository.
♦ Start, stop, enable, and disable repositories.
♦ Send repository notification messages.
♦ Register and unregister a repository.
♦ Propagate domain connection information for a repository.
♦ View repository connections and locks.
♦ Close repository connections.
♦ Register and remove repository plug-ins.
♦ Upgrade a repository.
For details on working with repository configurations, creating repositories, promoting
repositories, and licenses, see “Configuring the Repository” on page 103.
For details on upgrading a repository, see “Upgrading a Repository” in the Installation and
Configuration Guide.
For details on repository architecture and connectivity, see “Repository Architecture” on
page 3 and “Repository Connectivity” on page 4.
Overview 51
Navigating the Administration Console
Use the Administration Console to connect to the Repository Server and perform repository
administration tasks, such as creating, starting, and backing up repositories.
You must start the Repository Server before you can perform repository administration tasks.
On Windows, start the Repository Server service from the Services control panel. On UNIX,
start the Repository Server from the command line. For details on starting and stopping the
Repository Server, see “Installing and Configuring the Repository Server on Windows” and
“Installing and Configuring the Repository Server on UNIX” in the Installation and
Configuration Guide.
To launch the Administration Console from the Repository Manager, choose Repository-
Manage Repository Server. You can also launch the Administration Console from the
Windows Start menu.
The Administration Console uses Microsoft Management Console (MMC) technology.
MMC is a console framework for server and network management applications called snap-
ins. The Administration Console is a snap-in for MMC. For more information on using
MMC, see the online help for MMC.
The Administration Console allows you to navigate multiple Repository Servers and
repositories and perform repository management tasks.
Figure 3-1 shows the Administration Console:
Main Window
Console Tree
Nodes
Console Tree
The Console Tree allows you to browse Repository Servers and managed repositories. The
Administration Console displays a different set of Action menu items depending on which
Main Window
The Main window displays details of the node you select in the Console Tree. For example, if
you select a repository in the Console Tree, the Main window displays the properties of the
repository, such as the status and start time.
The Main window displays results in the following views:
♦ List view. Displays a collection of items that includes an icon and a label. In List view, you
can arrange the items in different ways by choosing the View menu. You can view items as
large or small icons, or you can list them with or without item details. Choose View-
Details to view detailed information for a node in List view. Figure 3-1 on page 52 shows
the Administration Console in List view.
♦ HTML view. Displays repository information as a dynamic HTML page. HTML view
includes hypertext links that allow you to perform actions on the selected node. The
hypertext links are shortcuts to some Action menu items. The Administration Console
only displays repositories in HTML view. Figure 3-2 on page 55 shows the Administration
Console in HTML view.
Host Name The name of the computer hosting the Repository Server.
Port Number The port number used to access the Repository Server.
Status The connection status of the repository, either connected or not connected.
HTML View
Hypertext Link
Attribute Description
Status The status of the repository, either running, starting, stopped, stopping, or disabled.
Start Time The date and time the repository last started. The date display format is
MM/DD/YYYY 24 HH:MI:SS.
Number of Restarts The total number of times the repository started since the Repository Server started. If you
shut down the Repository Server, this property resets to 0.
Process ID The Windows or UNIX process identification number assigned to the Repository Agent.
The Repository Server and Repository Agent append this number to entries in the
Repository Server and Repository Agent log files. When you troubleshoot the repository,
use this number to identify which error messages apply to the Repository Agent. For more
information on the repository log file, see “Reading the Repository Log Files” on page 97.
Table 3-4 lists the HTML links for performing some repository tasks:
Stop Stop the repository. For more information, see “Stopping the Repository” on page 72.
Backup Back up the repository to a binary file. For more information, see “Backing Up a Repository” on
page 66.
Restore Recover metadata from a repository binary backup file. For more information see “Restoring a
Repository” on page 67.
Upgrade Upgrade the repository to the latest version. For more information, see “Upgrading a
Repository” in the Installation and Configuration Guide.
Properties View general, network, database, and server configuration parameters for the repository. For
more information, see “Adding a Repository Configuration” on page 105.
1. Launch the Administration Console and select the Repository Servers node.
2. Choose Action-New Server Registration.
3. Enter the Repository Server host name and port number, and click OK.
The Administration Console adds the Repository Server to the Console Tree.
1. Launch the Administration Console and expand the Repository Servers node in the
Console Tree.
2. Right-click the Repository Server and choose Connect.
3. In the Connecting to Repository Server dialog box, enter the password you use to
administer the Repository Server and the port number used to access the Repository
Server. Click OK.
The Administration Console connects to the Repository Server and displays the managed
repositories.
1. If you are copying a repository, follow the steps to copy a repository in “Copying a
Repository” on page 62. If you are backing up repository, follow the steps to back up a
repository in “Backing Up a Repository” on page 66. If you are restoring a repository,
follow the steps to restore a repository in “Restoring a Repository” on page 67.
2. Click the Advanced button on the Copy From Another Repository dialog box, Backup
Repository dialog box, or Restore Repository dialog box.
3. Select the data you want to skip.
4. Click OK, and continue copying, backing up, or restoring the repository.
Note: You can optimize repository performance for repositories on IBM DB2 EEE. For more
information, see “Creating a Repository” in the Installation and Configuration Guide.
To copy a repository:
3. If you want to copy a repository managed by the same Repository Server, choose
Managed By the Same Repository Server, and select a repository from the repository list.
Copying a Repository 63
Deleting a Repository
Delete a repository when you want to delete all metadata and repository database tables in the
repository. You might delete a repository if metadata is obsolete. Deleting a repository is an
irreversible action. If the repository contains information that you might need, back up the
repository before you delete it.
If the repository you want to delete is a global repository, you must choose to unregister all
local repositories. Unless you unregister all local repositories, the Repository Server does not
delete the global repository. The Administration Console displays the following message:
This repository, <global repository name>, contains registered
repositories (<local repository names>).
You must stop and disable the repository before you delete it. For more information on
stopping and disabling the repository, see “Stopping the Repository” on page 72 and
“Disabling the Repository” on page 73.
Note: You can also use the pmrepagent Delete command to delete repositories. For more
information, see “Deleting a Repository (Delete)” on page 481.
To delete a repository:
10. Click No to keep the repository configuration, or click Yes to remove it.
When you click Yes, the Administration Console removes the repository from the
Console Tree, and it keeps a backup of the repository configuration file in the Repository
Server configuration directory.
When you click No, the Administration Console keeps the repository in the Console
Tree.
Deleting a Repository 65
Backing Up and Restoring a Repository
Regularly back up your repositories to prevent data loss due to hardware or software
problems. When you back up a repository, the Repository Server saves the repository in a
binary file, including the repository objects, connection information, and code page
information. If you need to recover the repository, you can restore the contents of the
repository from this binary file.
Backing Up a Repository
When you back up a repository, the Repository Server stores the file in the Repository Server
backup directory. The Repository Server uses the extension .rep for all repository backups.
Specify the backup directory in the Repository Server setup.
To back up a repository:
1. In the Console Tree, select the repository you want to back up.
2. Choose Action-All Tasks-Backup.
Tip: You can also click Backup in the Main window.
3. Enter your repository user name, password, and file name for the repository backup file.
Specify a name for the backup file. You can also enter a description for the backup file.
The Repository Server saves the backup file in the Repository Server backup directory.
Use an easily distinguishable name for the file. For example, if the name of the repository
is DEVELOPMENT, and the backup occurs the first week of May, you might name the
file DEVELOPMENTMay7.rep.
Restoring a Repository
You can recover metadata from a repository binary backup file. When restoring a repository,
you must have a database available for the repository. You can restore the repository in a
database that has a compatible code page with the original database. In the Administration
Console, you can restore a repository from either the Backups node or a repository name
node.
If a repository already exists at the target database location, you must delete it before restoring
a repository backup file. The Repository Server does not restore a repository if one already
exists in the target database location. You must delete the repository database before restoring
a backup repository.
PowerCenter can restore repositories from the current version only. If you have a backup file
from an earlier version of PowerCenter or PowerMart, you must use the earlier version to
restore the repository.
If you want to restore a repository, you must have at least the minimum system resources
required to create a repository. For details on the minimum system resources required to
create a repository, see “Creating a Repository” on page 116. The actual amount of disk space
required to restore the repository depends on the size of the repository backup file.
Verify you add the product, option, and connectivity license keys to the repository license file
when you edit the repository configuration you use to restore the repository backup file. For
example, you must have a Team-Based Development option license key to restore a versioned
repository.
For more information on licenses, see “Working with PowerCenter Licenses” on page 119.
You can also use the pmrepagent Restore command to restore repositories, or the Bulkrestore
command to restore Teradata repositories. For more information, see “Restoring a Repository
(Restore)” on page 485 and “Restoring Teradata Repositories using Fastload (Bulkrestore)” on
page 479.
Note: If you want to create, restore, or upgrade a Sybase repository, set allow nulls by default to
TRUE at the database level. Setting this option changes the default null type of the column to
null in compliance with the SQL standard.
2. In the Main window, select the repository backup file to restore, and choose Action-
Restore.
The Restore Repository dialog box appears.
6. If the Restore Repository-Security Module dialog box displays, you must choose whether
to restore the repository with the external module or to unregister the security module
when you restore.
If you choose to keep the external module, 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, so it verifies that the administrative user can
connect to the repository if the restore completes. The Repository Agent verifies that the
password is valid for the user name on the target server.
If you choose to unregister the security module, the Administrator account password
becomes “Administrator.” The other user names become disabled.
7. Click OK.
The Repository Server restores the repository. You can view the restore process in the
Activity Log.
1. In the Console Tree, select a repository configuration under the Repositories node to use
for the restored repository.
2. Choose Action-All Tasks-Restore.
6. If the Restore Repository-Security Module dialog box displays, you must choose whether
to restore the repository with the external module or to unregister the security module
when you restore.
If you choose to keep the external module, 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, so it verifies that the administrative user can
connect to the repository if the restore completes. The Repository Agent verifies that the
password is valid for the user name on the target server.
If you choose to unregister the security module, the Administrator account password
becomes “Administrator.” The other user names become disabled.
7. Click OK.
The Repository Server restores the repository. You can view the restore process in the
Activity Log.
1. In the Console Tree, select the repository you want to send the message to.
2. Choose Action-All Tasks-Notify Users.
The Notification Message dialog box appears.
3. Choose whether you want to send the notification message to users connected to the
selected repository or all repositories managed by the Repository Server.
4. Enter the message you want to send, and click OK.
The Repository Server sends the notification message to all PowerCenter Client users
connected to the repository. A message box informs the user that the notification was
received. You can view the message text on the Notifications tab of the PowerCenter
Client Output window.
3. Choose the global repository from the global repository list, and enter your repository
user name and password.
4. If you want to register a local repository managed by the same Repository Server, choose
Managed By the Same Repository Server and select a repository from the local repository
list.
5. If you want to register a local repository managed by a different Repository Server, choose
Managed By a Different Repository Server and enter the name of the local repository, the
host name of the Repository Server, and the port number the Repository Server uses for
connections.
6. Enter the repository user name and password for the local repository.
7. Click Register.
The Repository Server registers the local repository with the global repository.
8. Click Close.
1. In the Console Tree, select the repository for which you want to change the repository
connection information.
2. Choose Action-All Tasks-Propagate.
3. Enter your repository user name and password. Click OK.
The Repository Server contacts other registered repositories in the domain and updates
the connectivity information for the repository.
Property Description
Host Address The TCP/IP address of the machine associated with the connection.
Last Active Time The time of the last metadata transaction between the repository client application
and the repository.
Remote Host Port The port number the machine hosting the repository client application uses to
communicate with the repository.
1. In the Console Tree, select the repository containing the user connections you want to
view, and select the Connections node.
The Administration Console displays the repository user connection details in the Main
window:
Viewing Locks
You can view locks and identify residual locks in the Repository Manager or in the
Administration Console.
Application Application locking the object: Designer, Workflow Manager, or Repository Manager.
3. To sort your view of the locks by column, click on the column name.
4. To view updated lock information, click Refresh.
1. In the Console Tree, select the repository containing the locks you want to view.
2. Select the Locks node under the repository.
The Administration Console displays the repository object lock details in the Main
window:
3. To sort your view of the locks by column, click on the column name.
1. In the Console Tree, select the repository containing the connection you want to release,
and select the Connections node.
The Main window displays the connections details.
2. Select the user connection and choose Action-End Connection.
3. To terminate a connection associated with a residual lock, first view the repository object
locks to identify the connection ID number associated with the locks you want to release.
For more information, see “Viewing Locks in the Administration Console” on page 82.
4. Verify the user is not connected to the repository.
5. Enter the repository user name and password.
You can enter the user name and password associated with the connection, or a user name
and password with Super User privilege.
The Repository Server closes the connection and releases all locks associated with the
connection.
To register a plug-in:
4. In the Register Security Module dialog box, select the repository in which to register the
plug-in.
5. Enter your repository user name and password.
You can choose to update a plug-in already registered in the repository. You might choose
to do this when you upgrade the plug-in to a new version.
6. Click OK.
The Repository Server registers the plug-in with the repository. You can view the
registration process in the Activity Log.
To unregister a plug-in:
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"/>
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.
Table 3-7 describes the information to enter in the Register Security Module dialog box:.
Field Description
Update Security Check this box if you are updating an existing security module. Leave it blank if this is the
Module Registration first time you are registering this module.
Username Enter a user name that has Repository administrator privileges. You must have
administrator privileges to register the security module.
External Directory Enter a valid external login name for the module to use to connect to the external
Login directory service.
Password Enter the correct password for the external login name.
Enable CRC 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.
1. Open the Repository Server Administration Console and connect to the Repository
server.
2. 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.
Field Description
Port Port number to connect to the LDAP server. The port is usually 636 for SSL enabled
servers, or 389 for non-SSL enabled servers.
Search Base Distinguished name (DN) of the entry that serves as the starting point to search for user
names.
Principal User Distinguished name (DN) for the principal user. Leave this blank for anonymous login.
Name
Principal User Password for the principal user. Leave this blank for anonymous login.
Password
5. Click the Login Properties Tab to enter login properties and SSL information.
Field Description
Login Filter Condition to filter results for user search. The filter can specify attribute types, assertion
values, and matching criteria.
Certificate Database 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
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=
scope=subtree
loginAttr=uid
useSSL=no
certDB=
1. Open the Repository Server Administration Console and connect to the Repository
Server.
2. 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.
Field Description
Administrator Username The external login name for the repository administrator.
New Administrator The new password for the administrator to use with repository security after
Password unregistering the external security module.
Keep Username/ Keeps the mapping between the external user names and the login names in the
External Login Mapping repository. You can reuse this mapping if you register another external security
module.
REP Messages related to communication between the Repository Agent and Repository Server.
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.
Figure 3-5 shows the text of the message when you double-click it:
.
ERROR : CNX_53021 [Wed Jul 14 13:20:54 2004] : (2588|2336) Received an
invalid request.
103
Overview
Each repository managed by the Repository Server contains connection information saved in
a configuration file. You configure this file on the following tabs of the New Repository dialog
box:
♦ General. This includes information, such as repository name and version control.
♦ Database connection. The Repository Server uses this information to connect to the
repository database.
♦ Network. This includes receive and send timeout limits.
♦ Configuration. This includes repository configuration information, such as refresh
interval and maximum connections.
When you connect to the repository, the Repository Server starts the repository using the
stored connection information.
♦ Licenses. This displays the license key information stored in the repository license file. You
can also update the license keys in the license file.
Use the Administration Console to perform the following tasks:
♦ Add repository configurations.
♦ Edit repository configurations.
♦ Remove repository configurations.
♦ Export repository configurations.
♦ Import repository configurations.
♦ Edit repository license files.
♦ Create a repository.
♦ Promote a local repository to a global repository.
♦ Enable version control for a repository.
1. In the Console Tree, select the Repositories node and choose Action-New Repository.
The New Repository dialog box appears, displaying the General tab.
Required/
Option Description
Optional
Name Required The name of the repository. Do not use the following characters
when creating a repository name:
\ / : * ? < > " | .
Global Data Repository Optional Creates a global repository. Once created, you cannot change a
global repository to a local repository. Only enable this option if
you are sure you want to create a global repository. You can
promote an existing local repository to a global repository later.
Enable Version Control Optional Creates a versioned repository. Only enable this option if you are
sure you want to create a versioned repository. You can promote
an existing repository to a versioned repository later.
To enable a repository for version control, you must have the
Team-Based Development option license key in the repository
license file. Add the license key on the Licenses tab.
Creation Mode Required Choose to create a new repository based on this repository
configuration, or to add the repository configuration without
creating a repository in the database.
Required/
Option Description
Optional
CodePage Required The repository code page. The Repository Server uses the character
set encoded in the repository code page when writing data to the
repository.
ConnectString Required The native connect string the Repository Server uses to access the
database containing the repository.
Note that for most databases, this is not an ODBC data source name,
but a native connect string (for example, servername@dbname for
Microsoft SQL Server, or dbname.world for Oracle).
For Teradata databases, use the ODBC data source name.
For a list of connect string syntax, see Table 16-1 on page 405.
DBUser Required The account for the database containing the repository. Set up this
account using the appropriate database client tools.
DBPassword Required The repository database password corresponding to the database user.
Must be in 7-bit ASCII.
Trusted Connection Optional If selected, the Repository Server uses Windows authentication to
access the Microsoft SQL Server database. The user name that starts
the Repository Server must be a valid Windows user with access to the
Microsoft SQL Server database.
TablespaceName Optional 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.
To improve repository performance on IBM DB2 EEE repositories,
specify a tablespace name with one node.
For more information on using the tablespace names, see “Creating a
Repository” in the Installation and Configuration Guide.
Required/
Option Description
Optional
MessageSendTimeout Required Number of seconds the Repository Server waits while sending a
message to a client application before timing out. Default is 3.
Required/
Option Description
Optional
ErrorSeverityLevel Required The level of error messages written to the Repository Agent log
file. Specify one of the following message levels:
- Error. Writes ERROR code messages to the log file.
- Warning. Writes WARNING and ERROR code messages to
the log file.
- Information. Writes INFO, WARNING, and ERROR code
messages to the log file.
- Trace. Writes TRACE, INFO, WARNING, and ERROR code
messages to the log file.
Informatica recommends using the Trace and Information
logging levels for troubleshooting purposes only.
DateDisplayFormat Required The Repository Server validates the date display format and
uses it when writing entries to the repository log file. If the date
display format is invalid, the Repository Server uses the
PowerCenter default date display format. The default date
display format is DY MON DD HH 24:MI:SS YYYY.
Required/
Option Description
Optional
DynamicConfig Required The number of seconds the repository waits to poll for updates
RefreshInterval to its configuration. Default is 10.
ThreadWaitTimeout Required The number of seconds the master thread running repository
processes waits for process threads to stop before stopping.
Default is 60.
LogFileName Required The path and name of the Repository Agent log file. The
default is pmrepagent.log.
If you specify the same log file name for multiple repositories,
the Repository Agent writes messages for each repository to
the same file.
KeepAliveTimeout Required The number of seconds the Repository Agent waits for a
response from a repository client application before closing the
connection. If the Repository Agent receives no response from
the repository client application in three times the number of
specified seconds, the Repository Agent closes the
connection.
Default is 60. Minimum is 30. If you set this option to 0, the
Repository Agent does not timeout or close connections.
SecurityAuditTrail Optional Select to track changes made to users, groups, privileges, and
permissions. Logged to pmsecaudit.<repository_name>.log file
in the Repository Server installation/bin directory. For more
information, see “Repository Security” on page 125.
DatabaseArrayOperationSize Optional The number of rows to fetch each time an array database
operation, such as insert or fetch, is issued. Default is 100.
You can use the Licenses tab to update and view the repository license file. The license
file name is repository_name-es.lic and is located in the Repository Server installation
directory. However, when you use special characters in the repository name, the
Administration Console converts them to an underscore and a letter. For more
information about how the Administration Console creates repository file names, see
“Repository License Files” on page 120.
10. Add the product license key in the License Key field and click Update. PowerCenter adds
the product license key to the license file.
11. If you have any option or connectivity license key, enter the key in the License Key field,
and click Update. Do this for every option and connectivity license key.
Consider the following rules and guidelines when you add license keys:
♦ You must add the product license key to the license file before you enter any option or
connectivity license key. PowerCenter only adds option and connectivity license keys
to a license file when the license file contains a valid product license key.
♦ The option and connectivity license keys you add must match the repository type,
either development or production, of the other license keys in the license file.
♦ You can also add license keys at any time.
When you enter a valid license key string, the Administration Console informs you it
updated the license file successfully. The Administration Console does not add invalid or
expired license keys or license keys that already exist in the license file.
4. Choose to remove the repository from the server cache. This instructs the Repository
Server to remove the repository configuration only.
Note: If you select Delete the Repository, the Repository Server deletes the repository
from the database. For more information, see “Deleting a Repository” on page 64.
5. Click OK.
The Repository Server removes the repository configuration. It does not remove the
repository license file.
1. In the Console Tree, select the repository from which you want to export the
configuration information, and choose Action-All Tasks-Export Connection.
The Export Repository Configuration to a File dialog box appears.
2. Enter a name and location to store the export configuration file.
By default, the Administration Console saves the file in the Repository Server
configuration directory.
3. Click OK.
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
When you create a repository, you must have the following information available:
♦ Database user name and password. This login must have database permissions to create
the repository. In the new repository, this login becomes a default user with full privileges
in the repository. The password must be in 7-bit ASCII.
To create a repository:
1. In the Console Tree, select a repository configuration under the Repositories node.
2. Choose Action-Create.
The Repository Server begins building the repository. You can see the progress in the
Activity Log.
Note: If a repository already exists in the database, the Repository Server does not create
the repository. You must delete the existing repository in the target database before
creating the new repository.
When the Repository Server finishes creating the repository, it starts the Repository Agent.
After creating a repository, you must create at least one folder before you can create objects in
the Designer or Workflow Manager. For details, see “Creating a Folder” on page 171.
Tip: To change the repository code page after you create the repository, you can back up and
restore it. When you restore a repository, you can specify a compatible code page.
To promote a repository:
1. In the Console Tree, select the repository for which you want to enable version control.
2. Choose Action-Properties.
3. In the Properties dialog box, select the Supports Version Control option.
The Administrator Console displays the Login Information dialog box.
4. Enter your repository user name and password and click OK.
The Repository Server enables version control for the repository and stops and restarts
the repository for the changes to take effect.
_ _0
. _A
+ _B
- _C
= _D
~ _E
` _F
! _G
% _H
^ _I
& _J
* _K
( _L
) _M
[ _N
] _O
{ _P
} _Q
' _R
" _S
; _T
: _U
/ _V
? _W
, _X
< _Y
> _Z
\ _a
| _b
\t (tab) _c
\r (carriage return) _d
\n (new line) _e
You must add a valid product license key to the repository license file when you create the
repository configuration. If you have option or connectivity license keys, add them to the
license file after you add the product license key. For more information on adding license keys
to the repository license file, see “Adding a Repository Configuration” on page 105.
When you start a repository, the Repository Server verifies that the license file exists in the
Repository Server installation directory. If the Repository Server cannot find the license file,
or if the file contains an invalid or expired product license key, it fails to start the repository.
Workflow configured to run on a server grid. Server grid option license key.
Source or target definition using a relational database The connectivity license key for that relational database.
connection.
Application Source Qualifier transformation. The connectivity license key for the particular PowerCenter
Connect product.
Source definition configured to extract data from web PowerCenter Connect for Web Services connectivity license
services. key.
Parse or Address transformation available with the Data Cleansing option license key.
Data Cleansing option.
Repository Security
125
Overview
PowerCenter offers several layers of security that you can customize for your repository. You
can plan and implement security using these features:
♦ User groups. Repository groups for user names. You can assign users to multiple groups.
You can also assign privileges to groups. Every user in a group receives the privileges for
that group.
♦ Repository users. User name used to access the repository. You can assign privileges to
individual user names. Each user must have a unique repository user name to use folder
and object locking properly. You must assign each user to at least one user group. You can
use an external directory service to manage your user names and passwords.
♦ Repository privileges. The ability to perform actions within the repository and to start
and stop the PowerCenter Server. You assign repository privileges to users and groups.
Even if you have the repository privilege to perform certain tasks in the repository, you
may require permission to perform the task within a given folder.
♦ Folder permissions. The ability to perform tasks within an individual folder. You can grant
permissions on three levels: to the folder owner, a group to which the owner belongs, and
the rest of the repository users. You can perform some tasks with folder permissions only.
Most tasks also require the appropriate repository privileges.
♦ Versioning objects permissions. The ability to use versioning objects for change
management. Versioning objects include labels, deployment groups, and queries. You can
grant versioning object permissions to users and groups.
♦ User connections. You can use the Repository Manager to monitor user connections to the
repository. You can end connections when necessary, but to avoid repository
inconsistencies, you need to determine if the user has an active connection before closing
the connection.
♦ Locking. The repository locks repository objects and folders by user. The repository
creates five kinds of locks depending on your task: in-use, write-intent, execute, fetch, and
save. The Repository Server locks and unlocks all objects in the repository. You can
manually release a lock on an object by ending the connection of the user holding the lock.
To avoid repository inconsistencies, you need to determine if the owner of the lock is using
the object.
Informatica recommends taking time to plan your overall strategy so that you can implement
appropriate security measures to protect your repository.
Default Groups
When you create a repository, the Repository Manager creates two repository user groups.
These two groups exist so you can immediately create users and begin developing repository
objects. However, you can also create custom groups and assign specific privileges and
permissions to those groups.
There are two default repository user groups:
♦ Administrators
♦ Public
You cannot delete these groups from the repository or change the default privileges. For a list
of default privileges, see “Default Privileges” on page 143.
The Repository Manager creates two default users in the Administrators group:
♦ Administrator
♦ The database user name used to create the repository
You cannot delete these users from the repository or remove them from the Administrators
group.
The Repository Manager does not create any default user for the Public group.
User Status
Login Name
Repository User
Name
The user status indicates if a user can access the repository. Users can have one of the
following statuses:
♦ Enabled. The user name is valid for accessing the repository. When you add new users they
receive the enabled status.
♦ Disabled. Explicitly disabled from accessing the repository by the Administrator.
♦ No login assigned. The repository user name is not linked to an external login name. The
user cannot access the repository. This status occurs when you change from the default
authentication to an external directory service. The Repository Administrator must
explicitly enable the user by linking the user name to the login name.
The group to which the user belongs appears in the Member Of list. The remaining
groups appear in the Not Member Of list.
6. To add the user to a group, select the group in the Not Member list, and click Add.
7. To remove the user from a group, select the group in the Member list, and click Remove.
Note: You cannot remove a user from a group when the user belongs to only one group.
To edit a password:
The login name displays at the bottom of the screen. If you select more than one name,
the names display at the bottom separated by semi-colons.
Note: You can type a name at the bottom of the screen, but it must match a valid login
name in the directory. To check the spelling, click Check Names.
6. Click OK on the Add Names dialog box to add your selections to the user name-login
name association. The Manage Users and Privileges screen displays the user name, login
name and enabled status.
Refer to the next section for information on adding a user to a group, or editing a user
description.
Editing a User
You can edit users to maintain their group memberships and change their login status. If you
use an external directory service you can change the user name-login association, so the
repository user name maps to a new login name. If you use default authentication, you can
change a user password.
You can edit users with the following exceptions:
♦ You cannot edit passwords if you use an external directory for security.
♦ You cannot change group memberships for the Administrator user.
♦ You cannot edit any property for the Database user except contact information.
♦ You cannot change a user name. If a user name becomes obsolete, you can remove it from
the repository.
To edit a user:
Enabling a User
A user with a status other than enabled cannot access the repository. You must explicitly
enable the user. When you enable a user and you are using an external directory service, you
link their repository user name with their directory login name. When you enable a user
under default authentication, only the status changes.
To enable a user:
1. Choose Security-Manage Users and Privileges. The Manage Users and Privileges dialog
box displays.
2. Select the users you want to enable. You can select multiple users at a time.
3. Click Enable. One of the following actions occurs for each selected user:
♦ The user status changes to enabled. This occurs if you use default authentication, or if
you are enabling a user that has a suggested login name.
♦ The Select Login Name dialog box displays. This dialog box displays a list of valid
login names from the external directory service. It displays if you are using an external
directory service.
4. If you use the Select Login Name dialog box, select a login name from the list and click
OK.
The Manage Users and Privileges dialog box displays the login name and the associated
repository user name. The user status becomes enabled. If you enable more than one user,
this dialog box displays again for the next user.
Disabling a User
When you disable a repository user you change the user status from enabled to disabled.
Disabled users cannot access the repository. When you disable a user, you retain the user name
in the repository, so you can quickly enable the user at a later time. You can disable users
when you use default security or external user authentication.
Use Workflow n/a n/a - Connect to the repository using the Workflow
Manager Manager.
- Create database, FTP, and external loader
connections in the Workflow Manager.
- Run the Workflow Monitor.
- Perform Use Repository Manager tasks in the
Workflow Manager.
Extended Privileges
In addition to the default privileges listed above, the Repository Manager provides extended
privileges that you can assign to users and groups. The Repository Manager grants extended
privileges to the Administrator group by default.
Table 5-2 lists the extended repository privileges:
Extended Permission
Permission Grants You the Ability to
Privilege Object
Extended Permission
Permission Grants You the Ability to
Privilege Object
Super User n/a n/a - Perform all tasks, across all folders in the repository.
- Manage connection object permissions.
- Manage versioning object permissions.
- Mass updates.
Execute Folder - Use pmcmd to start workflows in folders for which you
Execute Connection have execute permission.
The default privileges allow you to perform basic tasks in the Designer, Repository Manager,
Workflow Manager, and Workflow Monitor. Extended privileges allow you to perform more
tasks and expand the access you have to repository objects. Informatica recommends that you
reserve extended privileges for individual users and grant default privileges to groups.
Level Includes
Owner’s Group Each member of the group to which the owner belongs, including the owner. If the owner
belongs to more than one group, you must select one of those groups in the folder dialog
box. This becomes the Owner’s Group.
Each permission level includes the members of the level above it. For example, if you grant
only read permission to a folder Owner, and grant read and write permission to the Owner’s
Group, the folder owner has both read and write permission on the folder.
Level Includes
User Group Repository group of user names. Every user in a group receives the privileges for that
group.
Each versioning object has a permissions list. The permissions list contains users or groups
and their permissions for the object. When you add users or groups, you can assign them
permissions. You also can change the object owner.
When you configure versioning object permissions, use the following rules and guidelines:
♦ The object owner receives all permissions by default.
♦ Users that belong to the Administrators group receive all permissions by default.
♦ World users receive no permissions by default.
♦ Users with Super User privilege receive all permissions by default.
Permissions 149
For information on tasks you can perform with user privileges, folder permissions, and
versioning object permissions, see “Repository Privileges” on page 142.
To configure permissions for versioning objects, select a versioning object in a versioning
objects browser and click Permissions.
Click to define
permissions.
Change owner.
Change group.
Table 5-5 describes the properties in the Repository Connections dialog box:
Property Description
User The user name of the user associated with the connection.
Host Address The TCP/IP address of the machine associated with the connection.
Last Active Time The time of the last metadata transaction between the repository client application
and the repository.
The repository then issues an in-use lock for the object, allowing you to view the object.
The repository allows only one execute lock per object. This keeps you from starting a
workflow that is already running, which can cause the PowerCenter Server to load duplicate
or inaccurate data.
Table 5-6 lists each repository lock and the conditions that create it:
In-use - Viewing an object in a folder for which you do not have write Unlimited
permission.
- Viewing an object that is already write-locked.
- Exporting an object.
Write-intent - Viewing an object in a folder for which you have write permission. 1
- Editing a repository object in a folder for which you have write
permission.
- Importing an object.
Viewing Locks
You can view existing locks in the repository in the Repository Manager. Use the Show Locks
menu command to view all locks in the repository.
Table 5-7 describes the object lock information in the Object Locks dialog box:
Application Application locking the object: Designer, Workflow Manager, or Repository Manager.
3. To sort your view of the locks by column, click on the column name.
4. To view updated lock information, click the Refresh button.
Releasing Locks
If a system or network problem causes the repository to retain residual locks, you may need to
unlock an object before using it.
Warning: Before unlocking any object, note which user owns the lock, verify that the object is
not being used and verify that the user is not connected to the repository.
You can unlock objects and folders by identifying the user connection associated with the lock
and terminating the user connection.
You do not need special privileges to terminate connections associated with your repository
user name. For information on the privileges and permissions to terminate other user
connections and unlock objects see “Repository Manager Tasks” on page 516.
Tips 161
Restrict the Workflow Operator privilege.
With the Workflow Operator privilege, you can use the Workflow Manager to start any
workflow within the repository for which you have read permission. You can also use the
pmcmd program to start any workflow in the repository. Misuse of the privilege can result in
invalid data in your target.
Where possible, avoid granting the Workflow Operator privilege. Instead, if the user needs to
use the Workflow Manager to start workflows, you can assign the user the Use Workflow
Manager privilege, and read and execute permission for the folders in which the user works. If
the user uses pmcmd to start workflows, the user needs only execute permission for the folder.
After creating users and user groups, and granting different sets of privileges, I find that
none of the repository users can perform certain tasks, even the Administrator.
Repository privileges are limited by the database privileges granted to the database user who
created the repository. 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
need to edit the database user to allow all privileges in the database.
I created a new group and removed the Browse Repository privilege from the group. Why
does every user in the group still have that privilege?
Privileges granted to individual users take precedence over any group restrictions. Browse
Repository is a default privilege granted to all new users and groups. Therefore, to remove the
privilege from users in a group, you must remove the privilege from the group, and every user
in the group.
How does read permission affect the use of the pmcmd program?
To use pmcmd, you do not need to view a folder before starting a workflow within the folder.
Therefore, you do not need read permission to start workflows with pmcmd. You must,
however, know the exact name of the workflow and the folder in which it exists.
With pmcmd, you can start any workflow in the repository if you have the Workflow Operator
privilege or execute permission on the folder.
My privileges indicate I should be able to edit objects in the repository, but I cannot edit
any metadata.
You may be working in a folder with restrictive permissions. Check the folder permissions to
see if you belong to a group whose privileges are restricted by the folder owner.
I have the Administer Repository Privilege, but I cannot access a repository using the
Repository Manager.
To perform administration tasks in the Repository Manager with the Administer Repository
privilege, you must also have the default privilege Browse Repository. You can assign Browse
Repository directly to a user login, or you can inherit Browse Repository from a group.
Troubleshooting 163
164 Chapter 5: Repository Security
Chapter 6
165
Overview
Folders provide a way to organize and store all metadata in the repository, including
mappings, schemas, and sessions. Folders are designed to be flexible, to help you logically
organize the repository. Each folder has a set of configurable properties that help you define
how users access the folder. For example, you can create a folder that allows all repository
users to see objects within the folder, but not to edit them. Or, you can create a folder that
allows users to share objects within the folder. You can create shared and non-shared folders.
Note: You must create a folder in a repository before you can connect to the repository using
the Designer or Workflow Manager.
Organizing Folders
Folders are designed to be flexible, providing the means to organize the repository in the most
logical way. Keep in mind that any mapping in a folder can use only those objects that are
stored in the same folder, or stored in a shared folder and accessed through a shortcut.
Overview 167
Folder Properties
Each folder has several configurable properties on the folder property sheet. You can use these
properties to protect metadata saved in the folder, while permitting the appropriate users
access to the folder.
Folders have the following properties:
♦ Folder permissions
♦ Folder owner
♦ Owner’s group
♦ Allow shortcuts
If folder is in a repository enabled for version control, you can apply a status to all versioned
objects in the folder. For more information on changing the status of all objects in a folder,
see “Working with Version Properties” on page 203.
Permissions
Permissions allow repository users to perform tasks within a folder. With folder permissions,
you can control user access to the folder, and the tasks you permit them to perform.
Folder permissions work closely with repository privileges. Privileges grant access to specific
tasks while permissions allow you to read, write, and execute tasks within a specific folder.
Folders have the following permission types:
♦ Read permission. Allows you to view the folder as well as objects in the folder.
♦ Write permission. Allows you to create or edit objects in the folder.
♦ Execute permission. Allows you to execute or schedule a workflow in the folder.
Note: Any user with the Super User privilege has read, write, and execute all tasks across all
folders in the repository and can perform any task using the PowerCenter Client tools.
For details on how folder permissions interact with repository privileges, see “Repository
Security” on page 125.
For list of permissions and privileges combinations allowing you to perform each task, see
“Permissions and Privileges by Task” on page 509.
Owner’s Group Each user in the owner’s repository user group. If the owner belongs to more than one
group, you must select one group for the Owner’s Group.
Each permission level includes the members in the level above it. If you restrict a permission
from the Owner or Owner’s Group, then grant the same permission to Repository, the Owner
and Owner’s Group retain the permission.
Note: All users in the Administrators group or with the Super User privilege have full access to
all folders in the repository.
Shared Folders
You can designate a folder to be shared. In the Designer, shared folders allow users to create
shortcuts to objects in the folder. If you have an object that you want to use in several
mappings or across multiple folders, like an Expression transformation that calculates sales
Creating a Folder
For information on the privileges and permissions to create a folder, see “Repository Manager
Tasks” on page 516.
To create a folder:
Required/
Folder Properties Description
Optional
Description Optional Description of the folder that appears in the Repository Manager.
Owner Required Owner of the folder. Any user in the repository can be the folder
owner.
Owner’s Group Required Repository user group to receive Owner’s Group permissions. Only
groups to which the owner belongs can be selected.
Status Required The status applied to all objects in the folder. This option applies to
versioned repositories only. For more information on object status,
see “Working with Version Properties” on page 203.
Permissions Required Folder permissions for users in the repository. For details, see
“Permissions” on page 168.
4. Click OK.
The folder appears in the Navigator. If the folder is shared, the folder displays an open
hand icon.
To edit a folder:
Deleting a Folder
If a folder becomes obsolete, you can delete that folder from the repository. For information
on the privileges and permissions to delete a folder see “Repository Manager Tasks” on
page 516.
To delete a folder:
Some objects you choose to compare also cause the wizard to compare other objects,
regardless of whether you select the other objects to compare.
Table 6-3 lists objects the wizard compares by default when you select certain objects to
compare:
The wizard compares the attribute of each object in the source folder with the attribute of
each object in the target folder. You can choose to compare based on the following criteria:
♦ Different objects. Object name and type exist in one folder but not the other.
♦ Similar objects. Object name, type, and modification date are the same in both folders.
♦ Outdated objects. Object modification date is older than objects with the same name.
The wizard does not compare the field attributes of the objects in the folders when
performing the comparison. For example, if two folders have matching source names and
column or port names but differing port or column attributes, such as precision or datatype,
the wizard does not note these as different.
A two-way comparison
A one-way comparison does not
notes the absence of
note the presence of
ORDER_ITEMS in
ORDER_ITEMS in ADS2 as a
ADS1 as a difference.
difference.
To compare folders:
Connect to repository.
4. Click Next.
5. Select the object types you want to compare.
6. Click Next.
8. Click Next.
The wizard always displays the number of differences, similarities, and outdated objects.
9. View the results of the comparison.
10. If you want to save the comparison results to a file, select Save results to file.
11. Click Finish.
12. If you chose to save the results to a file, specify the file type, name, and directory.
13. Click Save.
181
Overview
Shortcuts allow you to use metadata across folders without making copies, ensuring uniform
metadata. A shortcut inherits all properties of the object to which it points. Once you create a
shortcut, you can configure the shortcut name and description.
When the object the shortcut references changes, the shortcut inherits those changes. By
using a shortcut instead of a copy, you ensure each use of the shortcut matches the original
object. For example, if you have a shortcut to a target definition, and you add a column to the
definition, the shortcut inherits the additional column.
Shortcuts allow you to reuse an object without creating multiple objects in the repository. For
example, you use a source definition in 10 mappings in 10 different folders. Instead of
creating 10 copies of the same source definition, one in each folder, you can create 10
shortcuts to the original source definition.
Note: In a versioned repository, a shortcut always inherits the properties of the latest version of
the object that it references.
You can create shortcuts to objects in shared folders. If you try to create a shortcut to a non-
shared folder, the Designer creates a copy of the object instead.
You can create shortcuts to the following repository objects:
♦ Source definitions
♦ Reusable transformations
♦ Mapplets
♦ Mappings
♦ Target definitions
♦ Business components
You can create the following types of shortcuts:
♦ Local shortcut. A shortcut created in the same repository as the original object.
♦ Global shortcut. A shortcut created in a local repository that references an object in a
global repository.
Shortcuts do not inherit edits to the description of the referenced object. However, any
shortcuts created after the change then contain the latest description.
Note: If you move or delete an object referenced by a shortcut, the shortcut becomes invalid.
Shared Folder
Original Object
Shortcut Icon
Shortcut
1. In the Navigator, expand the shared folder containing the object you want to use and drill
down to locate the object.
2. Open the destination folder, the folder in which you want the shortcut.
3. Drag the object from the shared folder to the destination folder.
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.
4. When prompted for confirmation, click OK to create a shortcut, or click Cancel to
cancel the operation.
The shortcut now appears in the Navigator.
5. Choose Repository-Save.
You can now use the shortcut in this folder.
1. In the Navigator, expand the shared folder containing the object you want to use and drill
down to locate the object.
2. Open the destination folder, the folder in which you want the shortcut.
3. 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.
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.
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.
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. In the global repository, drill down through the shared folder until you locate the object
you want to use.
4. 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.
1. In the Designer, connect to the local repository and open the folder in which you want a
shortcut.
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.
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.
Local shortcut Standalone repository Another folder, same Local shortcut to original object
repository
Local shortcut Local repository Another folder, same Local shortcut to original object
repository
Local shortcut Local repository Different local repository, Copy of the shortcut object
same domain*
Global shortcut Local repository Different local repository, Global shortcut to original
same domain* object
Global shortcut Local repository Different repository, different Copy of the shortcut object
domain*
Local shortcut Global repository Local repository, same Global shortcut to original
domain object
Local shortcut Global repository Different repository, different Copy of the shortcut object
domain*
* 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.
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.
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.
199
Overview
If you have the team-based development license, you can configure the repository to store
multiple versions of objects. You can configure a repository for versioning when you create it,
or you can upgrade an existing repository to support versioned objects. Object versioning
allows you to store copies of previous versions of objects in development, track changes to
those objects, and prepare them for deployment to a production environment.
A versioned repository assigns multiple version numbers to versions of the same object. Each
time you check in an object, the repository increments the version number by one and stores
a new version of the object in the repository database. 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
You can perform the following tasks when you work with a versioned object:
♦ View object version properties. Each versioned object has a set of version properties and a
status. You can also configure the status of a folder to freeze all objects it contains or make
them active for editing.
♦ Track changes to an object. You can view a history that includes all versions of a given
object, and compare any version of the object in the history to any other version. This
allows you to determine changes made to an object over time.
♦ Check the object version in and out. You can check out an object to reserve it while you
edit the object. When you check in an object, the repository saves a new version of the
object and allows you to add comments to the version. You can also find objects checked
out by yourself and other users.
♦ Delete or purge the object version. You can delete an object from view and continue to
store it in the repository. You can recover, or undelete, deleted objects. If you want to
permanently remove an object version, you can purge it from the repository.
Sample Scenario
Suppose your environment includes a development repository and a production repository.
You create and test metadata in the development repository, and then copy it to the
production repository. While working in the development repository, you want to exclusively
edit objects, retain older versions, and freeze the folder when you are finished with
development to prevent further changes to the objects it contains.
Overview 201
Freezing a Folder
After you finish developing and testing your metadata, you decide to freeze the folder.
Freezing the folder prevents other users from checking out objects. You choose to freeze the
folder and allow deployment of objects in the folder.
Later, a query locates the object in the repository and includes it in a dynamic deployment
group. The deployment group specifies objects in the development repository you want to put
into production.
For more information about creating deployment groups, see “Working with Deployment
Groups” on page 236.
Object Properties
The Object tab of the Properties dialog box shows the object properties. 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.
Version Properties
On the Version tab, you can view properties that are specific to the latest version of the object.
This includes the version number, the user and host that created the version, and any
comments associated with the version.
Figure 8-3 shows the Version tab in the Properties dialog box:
For more information on creating and applying labels, see “Working with Labels” on
page 219.
The object status defines what actions you and other users can perform on the object. An
object can have one of the following statuses:
♦ Active. You and other users can edit the object.
♦ Deleted. The object is marked as deleted and is not visible in the Navigator. You can find a
deleted object through a query.
You can manually change the status of an object from the Repository Manager.
1. In the Repository Manager, right-click the object in the Navigator and choose
Versioning-View History. The View History window appears.
2. Select the latest version of the object, and choose Tools-View Properties. The object
properties appear.
3. In the Properties dialog box, choose the Object Status tab.
4. From the Object Status list, choose a status for the object.
5. Click OK.
6. Check in the object for other users to view changes to the status.
You can also change the status of folders in the repository. For more information, see “Folder
Properties” on page 168.
Table 8-1 lists additional tasks you can perform from the View History window:
Task Description
Purge a version. See “Deleting and Purging Versioned Objects” on page 215.
Add version to deployment group. See “Working with Deployment Groups” on page 236.
Undo check out or check in. See “Checking Out and Checking In Objects” on page 211.
Save object version history to a file. To save the version history to an HTML file, choose File-Save to File.
Export object version to an XML file. Export the version to an XML file. For more information on exporting and
importing objects, see “Exporting and Importing Objects” on page 263.
To view checkouts:
Specify folders.
Specify users.
Table 8-2 lists additional tasks you can perform from the View Checkouts window:
Compare versions. Compare the selected checkout with the previous checked in version. For
more information, see “Comparing Versions” on page 210.
View version properties. View the object and version properties of the checkout. For more
information, see “Viewing Version Properties” on page 203.
View object dependencies. View dependencies for the selected checkout. For more information, see
“Viewing Object Dependencies” on page 37.
Undo check out or check in. Check in or undo check out for the selected unmodified checkouts. See
“Undoing a Checkout” on page 213 and “Checking In Objects” on
page 213.
Save object version history to a file. To save the version history to an HTML file, choose File-Save to File.
View object history. View the object version history for the selected checkout. For more
information, see “Viewing Object History” on page 208.
Export object version to an XML file. Export the version to an XML file. For more information on exporting and
importing objects, see “Exporting and Importing Objects” on page 263.
Undoing a Checkout
You can undo a checkout. When you undo a checkout, the repository releases the write-intent
lock on the object and removes the checkout version from the repository. The most recently
checked in version of the object becomes the latest version of the object. If you want to
modify the object again, you must check it out.
You can undo a check out when you review the results of the following tasks:
♦ View object history. You can undo a check out from the View History window.
♦ View checkouts. You can undo a check out from the View Checkouts window.
♦ View query results. You can undo a checkout from the Query Results window when you
search for object dependencies or run an object query.
To undo a check out, select the checkout object and choose Tools-Undo Checkout.
Checking In Objects
When you finish making changes to a checked out object, you can check it in and commit the
changes to the repository. When you check in an object, the repository creates a new version
of the object and assigns it a version number. The repository increments the version number
each time you check in an object.
When you work with composite objects, the Repository Agent treats non-reusable objects as
part of the parent object, so you cannot check in or out individual non-reusable objects. For
example, if you have a mapping that contains a non-reusable Aggregator transformation, you
cannot check in the Aggregator transformation individually. When you check in the parent
mapping, the Repository Agent checks in the non-reusable Aggregator transformation
implicitly.
The Repository Agent does not check in reusable objects when you check in a composite
parent object, such as a mapping. If you want to check in all objects used in a mapping, you
must check in reusable objects separately.
Purging a Version
To permanently remove an object version from the repository, you must purge it from the
Repository Manager. When you purge an object version, the repository permanently removes
it from the repository database. You can also purge multiple versions of an object from the
repository at the same time. To completely purge an object from the repository, you must
purge all versions. You can purge a version from the View History window.
If you purge a version earlier than the latest version, the repository maintains a record of the
purge in the object history. If you purge the latest version, the repository does not maintain or
keep a record of the purge.
If you purge the latest version, and the prior version has a different name, the prior version
takes the name of purged version. For example, you have the source src_Records. The latest
version is named src_Records, but the name of the previous version in the history is
src_RecordsWeekly. If you purge the latest version, the name of the previous version changes
to src_Records.
To purge a version, select it from the object version history in the Repository Manager.
Choose Tools-Purge Object Version.
Grouping Versioned
Objects
This chapter includes the following topics:
♦ Overview, 218
♦ Working with Labels, 219
♦ Working with Object Queries, 224
♦ Working with Deployment Groups, 236
217
Overview
You can use labels, queries, and deployment groups to identify versioned objects that meet a
certain criteria. You can create labels, queries, and deployment groups in the Repository
Manager, and you can group objects from the Designer, Workflow Manager, and Repository
Manager.
You can group objects in the following ways:
♦ Apply labels. You use labels to associate groups of versioned objects in a repository. You
can apply a label to a group of objects across repositories in a domain. Use labels to track
versioned objects. For information about labels, see “Working with Labels” on page 219.
♦ Run queries. You use queries to search for versioned objects in the repository. You might
want to run a query to find objects to export or deploy, or to compare versions. For more
information about queries, see “Working with Object Queries” on page 224.
♦ Create deployment groups. You create deployment groups to deploy objects to another
repository within the domain. You can deploy objects when you move from test to
production. For more information about deployment groups, see “Working with
Deployment Groups” on page 236.
You can use labels, queries, and deployment groups to locate and group objects for
deployment. For example, your environment includes a development repository and a
production repository. You create and test metadata in the development repository, and then
deploy it to the production repository. While working in the development repository, you
want to track the different versions of objects you create and deploy the latest versions of these
objects to the production repository.
As you create objects, you assign a deployment label to those objects you have tested and are
ready to deploy. You then create a query to locate all the objects that use the deployment label.
The query returns objects that reside in different folders in your development repository.
Finally, you create a deployment group to identify objects for deployment to another
repository. You want to deploy the objects that you test each day. To do this, you create a
dynamic deployment group that runs a query against the source database at deployment time.
This populates the deployment group with a new set of objects each time you deploy the
group.
Select New to open the Label Editor. Select from the options in the Label Editor to create a
label object.
Figure 9-2 shows the Label Editor options:
When you edit a label object, you can edit the name or the comments associated with it, or
you can choose to lock the label to prevent other users from editing or applying the label.
Applying Labels
You can apply one or more labels to any versioned object in the repository. You can select any
label you have execute permissions for. You can also apply the label to selected dependent
objects. For example, if you want to group dependencies for a workflow, you can choose to
label all children objects. The Repository Server applies labels to sources, targets, mappings,
and tasks associated with the workflow.
Or, if you deploy objects to multiple repositories, you can apply the label to global shortcut
dependencies. When you deploy labels to global shortcut dependencies, you can apply the
label to dependent objects in a global repository from a local repository. Or, you can apply the
label to dependent objects in all registered local repositories in a global repository.
You can apply labels to objects when you complete one of the following tasks from the
Designer, Workflow Manager, or Repository Manager:
♦ View the history of an object. When you view the history of an object, choose Tools-
Labels-Apply Label from the View History window.
♦ Create an object query. When you run an object query, choose Tools-Labels-Apply Label
from the Query Results window.
Or, you can apply labels by selecting Versioning-Apply Labels in the Repository Manager. In
the Repository Manager, you open the Label Wizard, which allows you to apply labels to
groups of objects.
Figure 9-3 shows the Apply Label dialog box:
Move Label Moves the label from a previous version of the object to the latest version of the object.
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.
Label all Children Applies the label to all repository objects that the selected object uses.
Label all Parents Applies the label to all repository objects that use the selected object.
Primary/Foreign Key Applies the label to the source object containing the primary key referenced by the
Dependencies foreign key in the selected source object.
Global Shortcut Applies the label to global shortcut objects. Select one of the previous options, such as
Dependencies Label all children, and select Global Shortcut dependencies. The Repository Agent
applies the label to global shortcuts that meet the conditions you specify.
Preview Previews the group of objects that the Repository Agent applies the label to when you
apply labels to dependent objects.
When you apply a label to parent or child objects, the Repository Agent applies the label to
objects that are checked in to the repository. You cannot apply labels to checked out objects.
When you search for an object, view an object history, or view object properties, you can view
metadata for the labels applied to an object. You can view the label owner, the timestamp
when the label was applied, and the comments you entered when applying the label to the
object.
After you select objects to label, browse to select the label to apply and choose label options.
For more information about label options, see Table 9-1 on page 222.
You can select Preview to view the objects the Repository Agent labels.
Edit a query.
Delete a query.
Create a query.
Configure permissions.
Run a query.
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.
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
Check-in time Displays objects that are checked in at, Greater Than Date/time
before, or after a specified time or Is Between Numeric
within a specified number of days. Less Than
Is Not Between
Within Last (days)
Deployment Receive Displays objects deployed from another Greater Than Date/time
History folder or repository using deployment Is Between Numeric
groups in a given time period. Less Than
Is Not Between
Within Last (days)
Include Children and Displays child and parent dependent Where (Value 1) Any
Parents objects. depends on (Value Source Definition
For more information about object 2) Target Definition
dependencies, see “Viewing Object Transformation
Dependencies” on page 37. Mapplet
Mapping
Cube
Dimension
Task
Session
Worklet
Workflow
Scheduler
SessionConfig
Label Displays objects associated with a Is Equal To Labels for which you
label or group of labels. Is Not Equal To have execute
Is Not One Of permissions
Is One Of
Last Saved Time Displays objects saved at a particular Greater Than Date/time
time or within a particular time range. Is Between Numeric
Less Than
Is Not Between
Within Last (days)
Object Used Status Displays objects that are used by other Is Equal To Unused
objects. For example, you can find Used
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.
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:
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:
Check in. See “Checking Out and Checking In Objects” on page 211.
Undo check out. See “Checking Out and Checking In Objects” on page 211.
Export to an XML file. See “Exporting and Importing Objects” on page 263.
Add version to deployment group. See “Working with Deployment Groups” on page 236.
Save object version history to a file. To save the version history to an HTML file, choose File-Save to File.
Open object in a workspace. 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.
Sample Queries
The following sample queries illustrate how to create query conditions with different
parameters, operators, and values.
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.
Once you create the deployment group, you add objects to a static group or associate an
object query with a dynamic group.
Initiate a rollback.
1. Select a deployment group in the Deployment Group Browser and choose View History.
2. Select a deployment to roll back.
3. Click Rollback.
The Repository Agent checks the object versions in the deployment run against the objects in
the target repository. If any of the checks fail, the Repository Agent notifies you of the object
that caused the failure. The rollback results display at the end of processing.
When you select All Dependencies, you add all dependent objects to the static deployment
group. Dependent objects can include dependent objects within a workflow or mapping as
well as objects that shortcuts reference and primary key sources where there is a primary key-
foreign key relationship.
For information on deploying groups to a repository, see “Copying Folders and Deployment
Groups” on page 241.
241
Overview
You can use the Repository Manager to copy multiple objects from one repository to another.
You can perform the following copy operations:
♦ Copy a folder. You can copy a folder and all of its contents within a repository, or from a
source repository into a target repository.
♦ Replace a folder. You can copy a folder and all of its contents from a source repository and
replace an existing folder of the same name in the target repository. The contents of the
replaced folder are overwritten.
♦ Copy a deployment group. You can copy the objects in a dynamic or static deployment
group to multiple target folders in the target repository. The deployment operation creates
new versions of existing objects in the target folders.
If you want to archive or share metadata or deploy metadata into production, you may use
copy folder to copy an entire folder. If you want to update the metadata in a folder already in
production, you can replace the folder.
For example, you have a folder called Sales in the development repository. When it is ready
for production, you copy the Sales folder into the production repository. After a week in
production, you want to make minor changes. You edit the Sales folder in the development
repository and test the changes. When the folder is ready for production, you can either copy
the folder into the production repository, resulting in two copies of the folder in production,
or you can replace the existing Sales folder with the new one. Replacing the folder allows you
to update the production repository without creating multiple copies of the folder.
If the repository is enabled for versioning, you may also copy the objects in a deployment
group from one repository to another. 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. Copying a deployment group also allows you to
specify individual objects to copy, rather than the entire contents of a folder.
You can also effectively use different copy operations together. You might use copy folder and
copy deployment group together in your repository environment at different stages of the
development process.
For example, you have a development and production repository. When you complete initial
development for the metadata in a new folder and you are ready to deploy the objects into
production you copy the folder and all of its objects into the production repository.
As development continues you make changes to a session in the folder. You do not need to
copy all of the metadata in the folder to production, so you add the session to a deployment
group. When you copy the deployment group, the Copy Deployment Group wizard creates a
new version of the session in the target folder.
The error message appears in either the server log, workflow log, or session log, depending on
which operation the PowerCenter Server tried to perform. For example, if the PowerCenter
Server tried to fetch session information to run a session in a workflow, the message appears in
the workflow log.
The PowerCenter Server pauses until the repository completes the deploy. It cannot fetch
objects in that repository during this time.
When the repository allows access again, it displays the following message:
The folder/object deployment has completed. The current operation will
resume.
The PowerCenter Server fetches the repository object and completes the workflow, session, or
task.
Overview 243
Using the Copy Wizards
The Repository Manager provides a wizard to copy and replace folders and to copy
deployment groups. The wizard steps vary depending on the operation and the contents of
the folder or deployment group you want to copy.
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. Use the PowerCenter Server to run all workflows in the
folder if a matching server does not exist in the target repository.
♦ Retain assigned PowerCenter Server settings. Retain the assigned server settings for
workflows and session instances configured to run on specific PowerCenter Servers in a
server grid.
♦ Copy connections. Copy database, FTP, external loader, and Application connection
information if matching connection names do not exist in the target repository.
♦ Copy plug-in application information. Copy plug-in application component information
that does not exist in the target repository.
♦ Copy persisted values. Copy the saved persisted values for mapping variables used in a
session and workflow variables used in a workflow.
♦ Copy metadata extension values. Copy the metadata extension values associated with
repository objects.
For specific instructions on using the Copy Folder Wizard to copy or replace a folder, see
“Copying or Replacing a Folder” on page 248. For specific instructions on using the Copy
Deployment Group Wizard to copy a deployment group, see “Copying a Deployment Group”
on page 254.
Copy Modes
When you copy a folder or deployment group, you must choose from the following Copy
Wizard modes:
♦ Typical. The wizard uses the defaults for shortcuts to local and global shared folders.
♦ Advanced. You can override the defaults for shortcuts to local and global shared folders.
You can choose the shared folder to associate shortcuts. The wizard might have to
determine how the folders are related before establishing shortcuts.
Connections
The Copy Wizard copies connections used by sessions in the folder or deployment group. If
the connection already exists in the target repository, the Copy Wizard uses the existing
connection. The wizard does not overwrite connections in the target repository.
Metadata Extensions
When you copy objects to another repository, the Copy Wizard copies the metadata extension
values associated with those objects to the target repository. The metadata extension values
may or may not be available in the target repository. This depends on whether the extensions
are non-reusable or reusable.
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. Shortcuts to folders in the same
repository are known as local shortcuts. Shortcuts to the global repository are called global
shortcuts.
Local Shortcuts
The wizard can reestablish local shortcuts to shared folders if you have a current copy of the
shared folders in the target repository. Therefore, you can keep shortcuts intact by copying the
necessary local shared folders to the target repository before copying the folder.
If you do not copy the shared folders before copying the folder, the wizard deletes all shortcuts
and marks all affected mappings invalid.
If shared folders exist in the target repository, the wizard verifies whether the copy is current.
In typical mode, if you edit the original shared folder after you copy it to the target repository,
the wizard asks you to copy it again. In the advanced mode, you can compare the folders to
see which folder is most recent. The wizard does not establish shortcuts to an outdated shared
folder. Therefore, to copy shortcuts correctly, you must copy shared folders before copying
the folder.
If you copy the folder from the global repository to a local repository in the same domain,
local shortcuts become global shortcuts.
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 recreates global shortcuts to the global repository.
♦ When you copy a folder from a local repository to its global repository, the global
shortcuts become local shortcuts.
♦ When you copy a folder from a global repository to a local repository within the domain,
local shortcuts become global shortcuts.
If you copy a folder that contains global shortcuts between domains, 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. The Copy Wizard will either reestablish global shortcuts as a
local shortcuts, or establish the copied shortcuts as global shortcuts.
1. In the Repository Manager, connect to the source repository and select the folder you
want to copy.
2. Choose Edit-Copy.
3. If copying to a different repository, connect to the target repository.
4. In the Navigator, select the target repository, and choose Edit-Paste.
Tip: You can also drag and drop the folder into the target repository after connecting to
the repository.
The Copy Folder Wizard appears, displaying the folder name and target repository name.
5. The Copy Folder dialog box prompts you to select a mode:
♦ Typical. The wizard uses the defaults for shortcuts to local and global shared folders.
♦ Advanced. You can override the defaults for shortcuts to local and global shared
folders. You can choose the shared folder to associate shortcuts. The wizard might have
to determine how the folders are related before establishing shortcuts.
6. Click Next. The Copy Wizard prompts you for more information based on the content
of the folders and the copy mode you selected.
To stop the replacement, click Cancel. The wizard rolls back all changes.
Table 10-1 lists the dialog boxes and prompts that you may see when you copy a folder:
Latest Version Only Typical/Advanced Choose to copy the latest version of objects in the folder, or all
versions. If you are replacing a folder, copying the latest version
adds a new version to the existing objects in the target folder.
Replace Folder Typical/Advanced List existing copies of the folder or all folders in the repository
Folder Modified Typical/Advanced Specify if objects in the source folder have been created or
modified since the last copy.
Compare Folders Typical/Advanced If you specified that the source folder contains new or modified
objects, compare the folders to determine the similarities and
differences between the folders.
Sequence Generators and Typical/Advanced Choose to retain current values for Sequence Generator and
Normalizers Normalizer transformations.
Mapping Variables Typical/Advanced Copy persisted values for mapping variables if they exist.
Retain Mapping Variables Typical/Advanced If you are replacing a folder, choose to retain persisted values for
mapping variables.
Dependency Information Typical/Advanced Copy dependency information for objects in mappings, if it exists.
Copy Workflow Log Typical/Advanced Choose to copy workflow logs if they exist.
Retain Workflow Logs Typical/Advanced Choose to retain existing workflow logs in the target folder if you
choose not to copy workflow logs from the source folder.
Folder Exists Typical/Advanced Rename the target folder if a folder of the same name exists in the
target repository. Otherwise, it appends the date to the original
folder name.
Retain Server Settings Typical/Advanced Choose to retain the assigned PowerCenter Server information for
workflows and sessions configured to run on specific
PowerCenter Servers in a server grid.
Database Connections Typical/Advanced Lists all database connections in the folder, indicating the
connections for which you do not have read permission.
FTP Connections Typical/Advanced Lists all FTP connections in the folder, indicating the connections
for which you do not have read permission.
External Loaders Typical/Advanced Lists all external loader connections in the folder, indicating the
connections for which you do not have read permission.
Application Connections Typical/Advanced Lists all application connections in the folder, indicating the
connections for which you do not have read permission.
Plug-in Typical/Advanced Lists plug-in application information upon which the source folder
depends if the plug-in information does not exist in the target
repository.
Servers Typical/Advanced Allows you to select a PowerCenter Server to run all non-
associated workflows. If the target repository contains less than
two PowerCenter Servers, the wizard skips this step.
Local Shared Folders Typical Lists local shared folders in the target repository that you need to
copy first. To preserve shortcuts and prevent invalid mappings,
click Cancel and copy all listed local shared folders before
copying the folder.
Global Shared Folders Typical Lists global shared folders in the target repository that you need
to copy first. To preserve shortcuts and prevent invalid mappings,
click Cancel and copy all listed local shared folders before
copying the folder.
Outdated Shared Folders Typical Lists outdated folders in the target repository that you need to
copy first. To preserve shortcuts and prevent invalid mappings,
click Cancel and copy all listed local shared folders before
copying the folder.
Select Shared Folders Advanced Lists all dependent local and global shared folders. Also lists the
folder that contains shortcuts and the folder to which you can
establish shortcuts. You can choose to accept or override the
shared folder.
Override Shared Folder Advanced Lists folders you can select to establish shortcuts if you choose to
override the default folder selection in the Select Shared Folders
dialog box.
Compare Shared Folder Advanced Allows you to compare folders if the folders you choose in
Override Shared Folder dialog box are different.
Compare Results Advanced Lists the results from the folder compare. Displays objects that
exist in the local shared folder but not in the global shared folder.
Also displays objects that are older or newer than matching
objects in the global shared folder.
If there are differences between the folders, a message warns you
that shortcuts to missing objects will be removed. The wizard
takes you back to Select Shared Folders dialog box.
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. Shortcuts to folders in the same
repository are known as local shortcuts. Shortcuts to the global repository are called global
shortcuts.
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 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.
If the referenced object already exist in the target repository, the wizard verifies that the copy
is current. In typical mode, if you edit the original shared folder after you copy it to the target
repository, the wizard asks you to copy it again. If you do not copy the shared folders before
copying the deployment group, the wizard deletes all shortcuts and marks all affected
mappings invalid.
In advanced mode, you can compare the contents of the folders to see which contains the
most recent copies of referenced objects, and then decide to cancel and copy the shared folder
again or proceed with the copy operation. When you compare folders, the wizard compares
Global Shortcuts
If the deployment group contains global shortcuts, the wizard does not reestablish them when
you copy them to the target repository. If you copy a global shortcut alone, the wizard
completes the copy operation but does not copy the shortcut. If the global shortcut is part of
a composite object you want to copy, the copy operation fails.
To ensure that global shortcuts are preserved when you copy a composite object, verify that a
copy of the object, including the shortcut, exists in the target repository. If you are copying
the object for the first time, consider copying the entire folder. You can then use a deployment
group to copy subsequent versions of the object.
Object Naming
Different versions of an object may have different names. As a result, you might add an object
to a deployment group that has an existing copy in the target folder, but the copy has a
different name. In this situation, the wizard detects the relationship between the two objects
and replaces the copy in the target folder with the deployment group object.
For example, you have the mapping m_Orders in the development repository. You add it to a
deployment group and copy it to the production repository. As you continue development,
you change the name of the mapping in the development repository to m_OrdersWeekly. You
add this new version of the mapping to a deployment group and copy it to the production
repository. The wizard determines that m_Orders is an older copy of m_OrdersWeekly, and
replaces it, creating a new version. The latest version of the mapping in the production
repository is now m_OrdersWeekly.
You might also have an object in the target repository that has the same name as a deployment
group object, but is not a copy of the object. The object may be of a different type. If this
happens, the naming conflict causes the copy operation to fail.
For example, you have a mapping that uses relational source src_Records in the development
repository. You add the mapping to a deployment group and copy it to the production
repository. Later, you delete src_Records from the production repository and create a new
XML source, also named src_Records. If you then use a deployment group to copy the
relational source src_Records to the target repository, the copy operation fails because the
XML source src_Records has the same name, but is a different object.
Object Status
When you copy an object in a deployment group, the status of the source object may change
if a copy of the object already exists in the target folder.
Table 10-2. Change In Object Status After Copying Deployment Group Objects
Status of
Deployment Wizard Status of Target Status of Target Repository
Deployment Group
Action Repository Object Object After Copying
Object
Select Deployment Folders Typical/Advanced Choose the folders you want to deploy objects to.
Override Deployment Typical/Advanced Override the default selections for deployment folders.
Folder
Select Compare Folders Typical/Advanced Select the folders you want to compare.
Select Labels Typical/Advanced Select a label in the source repository to apply to the copied
object versions, and select a label in the target repository to apply
to the newly created object versions.
Clear Source Deployment Typical/Advanced Choose to remove objects from the deployment group after the
Group wizard completes the deployment operation.
Sequence Generators and Typical/Advanced Choose to retain current values for Sequence Generator and
Normalizers Normalizer transformations.
Retain Mapping Variables Typical/Advanced Choose to retain persisted values for mapping variables.
Dependency Information Typical/Advanced Copy dependency information for objects in mappings, if they
exist.
Retain Workflow Logs Typical/Advanced Choose to retain existing workflow logs in the target folder if you
choose not to copy workflow logs from the source folder.
Retain Server Settings Typical/Advanced Choose to retain the assigned PowerCenter Server information for
workflows and sessions configured to run on specific
PowerCenter Servers in a server grid.
Database Connections Typical/Advanced Lists all database connections in the folder, indicating the
connections for which you do not have read permission.
FTP Connections Typical/Advanced Lists all FTP connections in the folder, indicating the connections
for which you do not have read permission.
External Loaders Typical/Advanced Lists all external loader connections in the folder, indicating the
connections for which you do not have read permission.
Application Connections Typical/Advanced Lists all application connections in the folder, indicating the
connections for which you do not have read permission.
Plug-in Typical/Advanced Lists plug-in application information upon which the source folder
depends if the plug-in information does not exist in the target
repository.
Servers Typical/Advanced Allows you to select a PowerCenter Server to run all non-
associated workflows. If the target repository contains less than
two PowerCenter Servers, the wizard skips this step.
Local Shared Folders Typical Lists local shared folders in the target repository that you need to
copy first. To preserve shortcuts and prevent invalid mappings,
click Cancel and copy all listed local shared folders before
copying the folder.
Outdated Shared Folders Typical Lists outdated folders in the target repository that you need to
copy first. To preserve shortcuts and prevent invalid mappings,
click Cancel and copy all listed local shared folders before
copying the folder.
Select Shared Folders Advanced Lists all dependent local and global shared folders. Also lists the
folder that contains shortcuts and the folder to which you can
establish shortcuts. You can choose to accept or override the
shared folder.
Override Shared Folder Advanced Lists folders you can select to establish shortcuts if you choose to
override the default folder selection in the Select Shared Folders
dialog box.
Compare Shared Folder Advanced Allows you to compare folders if the folders you choose in
Override Shared Folder dialog box are different.
Compare Results Advanced Lists the results from the folder compare. Displays objects that
exist in the local shared folder but not in the global shared folder.
Also displays objects that are older or newer than matching
objects in the global shared folder.
If there are differences between the folders, a message warns you
that shortcuts to missing objects will be removed. The wizard
takes you back to Select Shared Folders dialog box.
263
Overview
In the PowerCenter Client, you can export repository objects to an XML file and then import
repository objects from the XML file. You can use the following client applications to export
and import repository objects:
♦ Repository Manager. You can export and import both Designer and Workflow Manager
objects.
♦ Designer. You can export and import only Designer objects.
♦ Workflow Manager. You can export and import only Workflow Manager objects.
♦ pmrep. You can export and import both Designer and Workflow Manager objects. You
might use pmrep to automate exporting objects on a daily or weekly basis. For more
information on using pmrep to export and import objects, see “Exporting Objects
(ObjectExport)” on page 432 and “Importing Objects (ObjectImport)” on page 433.
Exporting and importing an object is similar to copying an object from one folder or
repository to another. For example, when you copy an object between folders or export and
import that object, you can resolve object name conflicts. However, when you copy objects
between folders or repositories, you must be connected to both repositories. When you export
an object from one repository and import the object into another repository, you do not need
to be connected to both repositories.
You can export and import repository objects to accomplish the following tasks:
♦ Deploy metadata into production. After you test a mapping in a development repository,
you can export it to an XML file and then import it from the XML file into a production
repository. You might export and import objects to incrementally deploy metadata by
exporting and importing part of a composite object.
♦ Archive metadata. You can export objects to an XML file that you no longer need before
removing them from the repository.
♦ Share metadata. You can share metadata with a third party. For example, you want to send
a mapping to someone else for testing or analysis, but you do not want to disclose
repository connection information for security reasons. You can export the mapping to an
XML file and edit the repository connection information before sending the XML file.
The third party can import the mapping from the XML file and analyze the metadata.
♦ Search and replace property names in an entire repository object. You can search for a
property name and replace all occurrences of it with a different name. For example, you
have a mapping with an unconnected Lookup transformation. You want to change the
name of a port in the unconnected Lookup transformation. Several other transformations
call the lookup port through an expression, so you want to make sure you change the port
name in all other expressions. You can export the mapping to an XML file and open it in a
text editor. Search for the old port name and replace all references to it with the new port
name. Then import the mapping into the repository.
♦ Copy metadata between repositories. You can copy objects between repositories that you
cannot connect to from the same client. Export the object and transfer the XML file to the
target machine. Then import the object from the XML file into the target repository.
Overview 265
When you import an object exported from an earlier repository version, the repository
updates the object metadata to conform with the current repository version. For example, you
export an Advanced External Procedure transformation from an earlier repository version.
You import the transformation in the current repository version. The PowerCenter Client
imports the transformation and changes it to a Custom transformation.
For more information on changes the upgrade process makes on repository metadata, see
“Upgrading Repository Metadata” in the Installation and Configuration Guide.
Code Pages
To ensure no data is lost when you import an object, the PowerCenter Client only allows you
to export and import objects between repositories with compatible code pages. The code page
of the originating repository must be a subset of the destination repository code page. If the
two repository code pages are not compatible, the PowerCenter Client displays an error
message and does not import any object.
For details on code page compatibility, see “Globalization Overview” and “Code Pages” in the
Installation and Configuration Guide.
CRCVALUE Codes
Informatica restricts which elements you can modify in the XML file. When you export a
Designer object, the PowerCenter Client might include a CRCVALUE (Cyclic Redundancy
Checking) code in one or more elements in the XML file. The CRCVALUE code is another
attribute in an element.
When the PowerCenter Client includes a CRCVALUE code in the exported XML file, you
can only modify some attributes and elements before importing the object into a repository.
For example, VSAM source objects always contain a CRCVALUE code, so you can only
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.
PowerCenter Client
Options for Exporting Options for Importing
Application
Repository Manager - Multiple objects from one folder - Multiple objects from multiple folders
- Multiple object types from one folder - Multiple object types from multiple folders
For example, you can export multiple When you import objects from multiple
mappings to the same file. folders, you can choose which folders to
import into.
pmrep - Multiple objects from multiple folders - Multiple objects from multiple folders
- Multiple object types from multiple folders - Multiple object types from multiple folders
For example, you can export reusable When you import objects from multiple
transformations and reusable worklets to folders, you can choose which folders to
the same file. import into using the control file.
Designer - Multiple sources, targets, or reusable - Multiple objects from one folder
transformations from one folder - Multiple object types from one folder
For example, you cannot export both You can import Designer objects only.
sources and targets from the Navigator. You
cannot export multiple mappings or
mapplets.
You cannot export multiple object types.
Workflow Manager - Multiple reusable Email, Session, and - Multiple objects from one folder
Command tasks from one folder - Multiple object types from one folder
- Multiple worklets from one folder You can import Workflow Manager objects
- Multiple workflows from one folder only.
For example, you can export a reusable
Email task and a reusable Session task.
Note: You can export different object types from all PowerCenter Client tools by exporting the results of an object query.
Source with foreign key Source definition containing the primary key.
Target with foreign key Target definition containing the primary key.
Shortcut The object the shortcut references. For information on exporting and importing shortcuts,
see “Working with Shortcuts” on page 274.
Any repository object Any reusable or non-reusable metadata extension associated with the object.*
Session Session configuration and reusable and non-reusable tasks when you export from any
client application.
Mapping used by the session when you export from the Repository Manager or pmrep.
Workflow Scheduler and reusable and non-reusable tasks, sessions, and worklets.
*The PowerCenter Client always exports metadata extensions. 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. If the plug-in is not registered, the PowerCenter Client
imports the object without the metadata extension. For more information on registering plug-ins, see your PowerCenter Connect
documentation.
When you export and import objects, you can export and import any of the following
combination of objects:
♦ Parent object with dependent child objects. The XML file contains metadata for parent
and child objects. The PowerCenter Client exports the dependent child objects listed in
Table 11-3 by default. For more information, see “Exporting and Importing Parent
Objects” on page 271.
♦ Parent object without dependent child objects. The XML file contains metadata for the
parent object, but not the child object. For more information, see “Exporting and
Importing Parent Objects” on page 271.
Table 11-4 describes the options in the Export Options dialog box:
Export primary key tables when exporting When you export a source or target containing a foreign key, the
sources/targets with foreign keys. PowerCenter Client exports the source or target containing the primary
key.
Export original object referred by the When you export a shortcut, the PowerCenter Client exports the actual
shortcut when exporting shortcuts. object referenced by the shortcut.
Export reusable objects used by objects When you export a mapping, mapplet, worklet, or workflow, the
being exported. PowerCenter Client exports all reusable objects used by the parent
object.
For example, the PowerCenter Client exports all sources, targets, and
reusable transformations when you export a mapping.
Export non-reusable objects used by When you export a mapping, mapplet, worklet, or workflow, the
objects being exported. PowerCenter Client exports all non-reusable objects used by the parent
object.
For example, the PowerCenter Client exports all non-reusable
transformations for a mapping or mapplet, and all non-reusable tasks for
a worklet or workflow.
To access the Export Options dialog box, click the Advanced Options link in the Export
dialog box when you export objects.
When you export an object with its dependent child objects, the PowerCenter Client exports
the metadata for the parent object and the dependent objects. When you export an object
without its dependent objects, the PowerCenter Client exports the metadata for the object,
For information on versioned objects, see “Working with Versioned Objects” on page 199.
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. When both the shortcut
and referenced object exist in the same repository, the PowerCenter Client creates a local
shortcut. When the shortcut exists in a local repository, and the referenced object exists in a
global repository in the same domain, the PowerCenter Client creates a global shortcut. The
type of shortcut the PowerCenter Client creates does not depend on the shortcut type
specified in the XML file.
- Shortcut_to_Source1 from the Orders folder The Designer exports the saved version of Source1 because you do
- Target1 from the Sales folder not export any object from the same folder that contains the
referenced object, Source1.
- Shortcut_to_Source1 from the Orders folder The Designer exports the version of Source1 you have open in the
- Mapping1 from the Items folder Designer because you export an object, Mapping1, from the same
folder that contains the referenced object, Source1. Therefore, the
Designer exports the latest versions of all objects in the Items
folder, including changes you made to them since you last saved
the repository.
Modifiable Objects
You can modify some attributes and elements in an XML file. Table 11-5 on page 278 lists
the repository objects you can modify. The Modifiable Attributes column lists the attributes
You can create multiple rules. Use the buttons in the Import Wizard to move the rules up and
down. The PowerCenter Client applies the rules to objects in order. If multiple rules apply to
one object, the PowerCenter Client applies the uppermost rule only.
Table 11-6 describes the different columns you define for each rule:
Column Description
Select Criteria Choose the set of objects the rule applies to. You can choose the following sets of
objects:
- Objects with label. Applies to all objects with the label you choose. You can select this
option when you import objects into a versioned repository.
- Objects in query. Applies to all objects that result from the object query you choose.
You can select this option when you import objects into a versioned repository.
- Objects of type. Applies to objects of the type you choose.
- All objects. Applies to all objects you import.
Column Description
Select Value Choose a value that modifies the first column. For example, if you select Objects with
label in the first column, choose the label name in this column.
Select Choose how to resolve the object conflicts. You can resolve conflicts using the following
Resolution methods:
- Replace. Replaces the existing object in the destination folder.
- Reuse. Uses the existing object in the destination folder.
- Rename. Creates a new object in the destination folder with a new name. When you
choose Rename, you can specify a different name in the Conflict Resolution Wizard.
For more information on the Conflict Resolution Wizard, see “Resolving Specific
Object Conflicts” on page 283.
- Prompt User. Allows you to choose a resolution on an object by object basis. When
you choose Prompt User, you can define the specific conflict resolutions in the Conflict
Resolution Wizard. For more information on the Conflict Resolution Wizard, see
“Resolving Specific Object Conflicts” on page 283.
After you create general object resolution rules, you can resolve specific object conflicts using
the Import Wizard.
The Conflict Resolution Wizard is similar to the Copy Wizard. The user interface is similar
and you resolve the same type of object conflicts in both. For information on resolving
conflicts in the Copy Wizard, see “Copying Objects” on page 297.
After you resolve object conflicts in the Conflict Resolution Wizard, you return to the Import
Wizard.
1. Open the folder that contains the objects you want to export.
2. In the Navigator or workspace, select the objects to export.
3. Choose Repository-Export Objects.
5. In the Export Options dialog box, choose which dependent objects to export and click
OK. For more information, see “Working with Dependent Objects” on page 270.
6. In the Export dialog box, navigate to the directory where you want to save the XML file.
Enter a name for the XML file and click Save.
You can click View File to view the XML file the PowerCenter Client creates.
7. Click Close in the Exported Objects dialog box.
To import an object:
3. In the Import Wizard, click Browse to locate the XML file. Navigate to the directory
where the XML file is located. Select the XML file and click OK.
Open Button
This step of the Import Wizard appears when you import objects using the Repository
Manager, or when you import a shortcut object in the Designer. You can match folders
listed in the XML file to folders in the destination repository.
7. Click the Open button for a folder listed in the Import Wizard.
The Folder Selection dialog box appears.
This step of the Import Wizard appears when you use the Repository Manager to import
objects into a versioned repository. You can check in the objects and apply labels to the
them after importing.
10. To check in all objects after importing them, select Check In and enter comments in the
comment field.
11. To apply a label to all objects you import, select Apply Label and click Select Label. In
the Label Browser dialog box, choose the label and click OK.
You can only apply a label to the objects if you choose to check them in.
This step of the Import Wizard appears when you import objects using the Repository
Manager. You can create rules to resolve general object conflicts. You can apply rules to
objects with a certain label, objects listed in an object query, objects of the same type, or
all objects.
13. To create a new rule, click New Rule. Choose to which objects to apply the rule and
select a resolution.
For more information on resolving object conflicts, see “Resolving Object Conflicts” on
page 281.
14. Click Next.
The Conflict Resolution Wizard is similar to the Copy Wizard. Use the Conflict
Resolution Wizard to resolve specific object conflicts. For information on resolving
conflicts in the Copy Wizard, see “Copying Objects” on page 297.
15. Click Compare Conflict to compare conflicting objects in the XML file and target
repository.
The Diff Tool window appears.
16. Resolve object conflicts as they appear in the Conflict Resolution Wizard. Click Next to
proceed through the Conflict Resolution Wizard.
17. Click Close when you resolve all the conflicts for this folder.
You can click View/Edit to view or edit the object conflicts for the objects in that folder.
Note: If you cancel the Conflict Resolution Wizard for a folder, the Import Wizard
displays the status of that folder as unresolved. Click Resolve in the Action column for
that folder to open the Conflict Resolution Wizard and resolve the object conflicts.
The Output window displays the results of the import process. Errors and warnings are
designated by colored text.
19. Click Done.
When I tried to import a shortcut to an object, the Designer imported the actual object
instead of the shortcut.
To import a shortcut to an object into a repository, the Designer must be able to connect to
the source repository to re-establish the shortcut. When it cannot connect to the source
repository, it imports the object the shortcut references using the metadata in the XML file.
I imported a mapping from an XML file I modified, but the Designer marked it invalid.
Make sure that the metadata you define in the XML file is valid. You must be able to create
the object you define in the Designer or Workflow Manager. For example, if you edit the
metadata for a mapplet, make sure the source is not a VSAM source. The Designer marks
mapplets with VSAM sources as invalid.
Copying Objects
297
Overview
The Workflow Manager, Designer, and Repository Manager provide a Copy Wizard that
allows you to copy repository objects. You can copy repository objects such as workflows,
worklets, tasks, sessions, mappings, mapplets, sources, targets, and transformations. You can
also copy segments of workflows or mappings.
You can copy objects within the same folder, to a different folder, or to a different repository.
If you want to copy an object to another folder, you must first open the target folder.
The Copy Wizard checks for conflicts in the target folder and provides choices to resolve the
conflicts. For example, if an item exists in the target folder, a description of the conflict
displays in the Conflict Message section of the screen. The Copy Wizard displays possible
resolutions in the Resolution area of the screen. For a duplicate object you can rename, reuse,
replace, or skip copying the object.
Figure 12-1 shows the Copy Wizard:
Copy From/
Copy To
Conflict Message
Edit name.
Compare
Conflict Link
Apply resolution
to other conflicts.
Next Conflict/
Option
Area Description
Copy From/Copy To Displays the original repository and folder name and the target repository and folder
name.
Overview Area Displays the items to copy, existing conflicts, original instance name, target instance
name, and action taken to resolve the conflict.It displays a red icon next to each object
with a conflict, and a green icon next to each object without a conflict.
Conflict Message Identifies the current conflict and the name of the object with the conflict, if any. After
you choose a resolution, the message describes the resolution.
Resolution Displays the elected resolution or a list of choices for resolution. Choices might be
different, depending on the conflict.
Edit Enables you to edit the object name if you choose to rename the object.
ApplyThisResolution to Applies the resolution to all unresolved conflicts or just the conflicts for the same object
Other Conflicts type.
Compare Conflict Compares duplicate objects in the target folder to the objects you are copying. For more
information, see “Comparing Repository Objects” on page 45.
Next Conflict/Option Allows you to choose additional options for session and workflow resolutions, such as
applying default connections or retaining server connections during the copy. Next
Conflict/Option displays only with session or workflow conflicts that you resolve by
renaming or replacing the target.
View Object Dependencies Displays object dependencies for the current object. For more information, see “Viewing
Object Dependencies” on page 305.
You can configure display settings and functions of the Copy Wizard by choosing Tools-
Options in the Designer or Workflow Manager.
Overview 299
Resolving Copy Conflicts
When the Copy Wizard encounters a conflict, it prompts you to resolve the conflict before
continuing the copy process. The Copy Wizard provides you with the resolutions depending
on the type of conflict.
Table 12-2 describes the Copy Wizard resolutions:
Copy Copy a connection object. When the Copy Wizard cannot find a
connection object in the target repository.
Browse Click Browse to choose a server, When the Copy Wizard cannot find a server,
connection, or mapping. You must select connection, or mapping in the target folder it
a valid object in the target folder for the displays the Browse button.
copy process to succeed.
Rename Change the object name when copying it When an object with the same name exists in
to the target folder. the target folder.
Replace Replace the existing object in the target When copying to another folder in the same
folder. repository or another folder in a different
repository and an object with the same name
exists in the target folder.
Reuse Use the existing object in the target When a reusable object exists in the target
folder. folder.
Skip Skips copying the object. When an object with the same name exists in
the target folder.
If the target folder has duplicate objects, you can compare them to the objects you are copying
to determine the differences. Click the Compare Conflict link on the Copy Wizard to display
source and target views of the objects. For more information about comparing repository
objects, see “Comparing Repository Objects” on page 45.
The wizard prompts you to select a resolution for each unresolved object in your copy.
Optionally, you can apply the resolution to all unresolved objects of the same type, or to all
conflicts in your copy. To apply the resolution to more objects, click Apply This Resolution
To and choose either All Conflicts or conflicts for just the specified object type.
The Copy Wizard appears. The Copy Wizard displays objects by type. For example, the
sessions display under the Sessions node, and mappings display under the Mappings
node.
The Copy Wizard displays a red icon on objects with conflicts. It displays conflicts one
object type at a time.
5. Click Next if you do not encounter a conflict.
If you encounter a conflict, choose a resolution from the Resolution options. For
example, Figure 12-3 shows the first of two unresolved mapping conflicts to resolve. The
Copy Conflict
1. Select the object from the Overview area of the Copy Wizard.
2. Click the View Object Dependencies button.
The Dependency dialog box appears.
Object You Selected
In the Overview Area
Dependent Objects
Copying Sessions
When you copy a Session task, the Copy Wizard looks for the database connections and
associated mappings in the target folder. If the mapping or connection does not exist, you can
select a new mapping or connection. If the target folder has no mappings, you must first copy
a mapping to the target folder in the Designer before you can copy the session.
When you copy a session, you might encounter the following copy conflicts:
♦ Duplicate name. A session with the same name exists in the target folder. You can rename
the existing session, reuse the session in the target folder or replace it. If you rename or
replace the session you can use default mappings and connections. Otherwise, you may
need to choose the connections and mappings after you copy the session.
♦ Cannot find server connection. The server connection for this session does not exist in the
target.
Mapping Conflicts
When you copy a session, the Copy Wizard verifies that the associated mapping exists in the
target folder. If the mapping does not exist, you can choose a different mapping from the
target folder.
To find available mappings in the target folder, click Browse. If the target folder does not have
any mapping in it, the Copy Wizard prompts you to create one:
There are no mappings in this folder. Please create a mapping in the
Mapping Designer.
You must cancel the copy process to create a mapping. When you cancel, the Copy Wizard
does not copy any object. To avoid this problem you can copy the mapping to the target
folder in the Designer before copying the session. If you replace a mapping with an invalid
mapping, the associated sessions become invalid.
Mapping Variables
When you copy a session that uses mapping variable values, the Copy Wizard either copies
the variables to the target folder or retains the saved variable values already in the folder.
Exchanging Metadata
313
Overview
You can use the Repository Manager to share source and target metadata with other business
intelligence (BI) and data modeling tools, such as Business Objects Designer. PowerCenter
uses the Meta Integration® Model Bridge (MIMB) from Meta Integration Technology, Inc.
to exchange metadata with other BI and data modeling tools. MIMB uses the specifications in
powrmart.dtd to exchange metadata with PowerCenter.
The Repository Manager uses a wizard to guide you through the export or import process.
The wizard prompts you for different options, depending on the BI or data modeling tool.
When the Metadata Import Wizard detects object conflicts during import, it opens the
Conflict Resolution Wizard. The Conflict Resolution Wizard is similar to the Copy Wizard.
For information on resolving conflicts in the Copy Wizard, see “Copying Objects” on
page 297.
To exchange metadata you export the metadata from the source tool and import the metadata
into the target tool. PowerCenter can be the source or target tool. To exchange metadata
between PowerCenter and another tool, you can use one of the follow methods:
♦ Use PowerCenter as the source tool. In PowerCenter, export metadata to a file recognized
by the target tool, and then use the target BI or data modeling tool to import metadata
from the file.
♦ Use the BI or data modeling tool as the source tool. In the source BI or data modeling
tool, export metadata to a file recognized by the source tool, and then use PowerCenter to
import metadata from the file.
To export metadata, select an object and choose Repository-Export Metadata. To import
metadata, select a folder and choose Repository-Import Metadata. For more information on
exporting metadata, see “Steps for Exporting Metadata” on page 316. For more information
on importing metadata, see “Steps for Importing Metadata” on page 319.
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
You can import from the following BI tool:
♦ Cognos Impromptu
Note: You can also exchange metadata with BI and data modeling tools by using the Export
Objects and Import Objects menu commands. You do not need a PowerCenter Metadata
Exchange option license key, but you must be able to export or import XML files that
conform to powrmart.dtd. For more information on exporting and importing objects, see
“Exporting and Importing Objects” on page 263.
Overview 315
Steps for Exporting Metadata
Use the following procedure to export metadata from PowerCenter to a file recognized by the
target BI or data modeling tool.
To export metadata:
1. In the Repository Manager Navigator, select the object or objects you want to export, and
choose Repository-Export Metadata.
The Metadata Export Wizard appears.
2. Choose the target tool you want to export the object to. You can click More Info to read
about the tool requirements.
6. Enter the options specific for the tool to which you are exporting.
You can click Show Details to view detailed messages about the metadata conversion.
You can click Save Log to save the message log to a text file.
8. Click Finish to close the wizard.
To import metadata:
1. In the Repository Manager, select the folder into which you want to import metadata,
and choose Repository-Import Metadata.
The Metadata Import Wizard appears.
2. Choose the target tool from which you want to import the object. You can click More
Info to read about the tool requirements.
The Metadata Import Wizard displays options specific to the tool you select, such as IBM
DB2 Cube Views.
4. Enter the options specific for the tool from which you are importing.
5. Click Next.
The PowerCenter Options page of the wizard appears.
Require/
Option Description
Optional
Table Type Required The type of repository objects to create. You can create source or
target definitions. Default is source.
Database Type Required Choose the database type for the source or target definitions the
wizard creates.
The wizard can define the object definition database type based on
the metadata defined in the file, or you can override the database
type by choosing a database type here. Default is auto detect.
Database Name Optional The DBD under which you want to group the repository objects in
the Navigator. If you do not specify a DBD, the Metadata Import
Wizard groups all objects under a DBD based on the source or
target database.
Codepage Required The code page of the repository you import the metadata into.
Default is MS1252.
Indentation Optional The number of spaces used to indent the file you import.
Default is no indentation.
Retain Physical Optional Indicates whether or not to retain the column properties when you
Properties replace an existing object.
Default is False.
7. Click Next.
The Metadata Import Wizard converts the metadata in the file to a format recognized by
PowerCenter.
The Metadata Import Wizard adds the objects to the folder in the repository. If the folder
contains objects with the same name as those you import, the Metadata Import Wizard
opens the Conflict Resolution Wizard.
The Conflict Resolution Wizard is similar to the Copy Wizard. Use the Conflict
Resolution Wizard to resolve specific object conflicts. For information on resolving
conflicts in the Copy Wizard, see “Copying Objects” on page 297.
Metadata Extensions
325
Overview
Informatica allows end users and partners to extend the metadata stored in the repository by
associating information with individual objects in the repository. For example, when you
create a mapping, you can store your contact information with the mapping. You associate
information with repository metadata using metadata extensions.
PowerCenter Client applications can contain the following types of metadata extensions:
♦ Vendor-defined. Third-party application vendors create vendor-defined metadata
extensions. You can view and change the values of vendor-defined metadata extensions,
but you cannot create, delete, or redefine them.
♦ User-defined. You create user-defined metadata extensions using PowerCenter. You can
create, edit, delete, and view user-defined metadata extensions. You can also change the
values of user-defined extensions.
All metadata extensions exist within a domain. You see the domains when you create, edit, or
view metadata extensions. Vendor-defined metadata extensions exist within a particular
vendor domain. If you are using third-party applications or other Informatica products, you
may see domains such as Ariba or PowerCenter Connect for Siebel. You cannot edit vendor-
defined domains or change the metadata extensions in them.
User-defined metadata extensions exist within the User Defined Metadata Domain. When
you create metadata extensions for repository objects, you add them to this domain.
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
User-Defined
Metadata
Extensions
This dialog box lists the existing user-defined and vendor-defined metadata extensions.
User-defined metadata extensions appear in the User Defined Metadata Domain. If
vendor-defined metadata extensions exist, they appear in their own domains.
3. Open the User Defined Metadata Domain.
4. Click Add.
Required/
Field Description
Optional
Extension Name Required Name of the metadata extension. Metadata extension names must
be unique for each type of object in a domain.
Metadata extension names cannot contain any special character
except underscore, and they cannot begin with a number.
Object Type Required The type of repository object to which the metadata extension is
associated. This can be a source definition, target definition,
transformation, mapping, mapplet, session, workflow, worklet, or
all of these objects.
You associate metadata extensions with specific types of
transformations. For example, if you create a metadata extension
for Expression transformations, it is available only for Expression
transformations.
Database Type Required for The database type. The database type is required for source and
source and target target definition objects. You can select a single database type or
definition objects all database types.
Required/
Field Description
Optional
Maximum Length Required for string The maximum length for string metadata extensions.
objects
Client Editable Optional Specifies whether the value of the metadata extension is editable
in PowerCenter. If you select this option, the Repository Manager
grants Client Visible permission as well.
Share Read Optional Specifies whether the metadata extension is visible in vendor
domains.
Share Write Optional Specifies whether the value of the metadata extension is editable
across vendor domains. If you enable Share Write permission, the
Repository Manager grants Share Read permission as well.
Private Optional Specifies whether the metadata extension is private to the domain
in which it is created. The Repository Manager enables this option
when third-party application vendors create vendor-defined
metadata extensions only.
6. Click Create.
7. Click Done.
To edit a reusable metadata extension, select the appropriate metadata extension in the
Metadata Extensions dialog box, and then click Edit.
You can modify the following fields:
♦ Default Value
♦ Permissions
♦ Description
To delete a reusable metadata extension, select the appropriate extension in the Metadata
Extensions dialog box, and click Delete.
333
Viewing the Repository Metadata
Informatica Metadata Exchange (MX) provides a set of relational views that allow easy SQL
access to the Informatica metadata repository. The Repository Manager generates these views
when you create or upgrade a repository.
Warning: The PowerCenter repository tables have an open architecture. Although you can view
the repository tables, 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. Therefore, do not directly access the actual
repository tables. Instead, use MX to access the repository.
MX View Categories
MX views provide information to help you analyze metadata stored in the repository. Table
15-1 lists the available MX views by category:
Category Description
Database Provides a list of database definitions in the repository. For more information,
see “Database Definition View” on page 338.
Sources Provides a list of source definitions by folder. For more information, see “Source
Views” on page 339.
Targets Provides a list of target definitions by folder. For more information, see “Target
Views” on page 347.
Mappings and Mapplets Provides a list of sources, targets, and transformations used in mappings and
mapplets by folder. For more information, see “Mapping and Mapplet Views” on
page 353.
Metadata Extensions Provides details of metadata extensions defined for objects. For more
information, see “Metadata Extension Views” on page 364.
Transformations Provides details of transformation instances by folder. For more information, see
“Transformation Views” on page 366.
Workflows, Worklets, and Tasks Provides static and run time details for workflows and worklets by folder. For
more information, see “Workflow, Worklet, and Task Views” on page 371.
Security Provides user and group information. For more information, see “Security
Views” on page 390.
Deployment Provides deployment details such as deployment groups and objects that were
deployed from one repository to another. For more information, see
“Deployment Views” on page 392.
Repository Provides repository details such as repository name and connection information.
For more information, see “Repository View” on page 395.
PowerCenter Server Provides details such as server name and host name. For more information, see
“PowerCenter Server Views” on page 396.
Category Description
Changed Management Provide version history of object and label details. For more information, see
“Change Management Views” on page 398.
Folders Provides details such as folder name and description. For more information, see
“Folder View” on page 401.
For example, if a source table changes, and you need to re-import the source definition into
your repository, you could use the REP_SRC_MAPPING view to see how many mappings
include this source. Likewise, if you want to view source and target dependencies for a
mapping, you could use REP_TBL_MAPPING.
Almost all views support access to comment information. You can add comments to any
object within PowerCenter through the Designer and Workflow Manager. You can access
comments about individual tables, table relationships, data fields, and data transformations.
You can use these views to create reports using third-party reporting tools, such as Crystal
Reports.
MX facilitates the integration of decision support metadata between the PowerCenter
repository and popular Decision Support System (DSS) tools, data modeling tools, and any
other metadata resources. MX allows you to drill down to the operational metadata level and
expose information needed to support decisions. MX also helps you make precise information
requests that draw from data models, mappings, and transformation data. For IS
professionals, the MX architecture provides the following benefits:
♦ Improves warehouse maintenance and management capability.
♦ Reduces time and resources required to support end-user requests.
♦ Expands the ability to provide information resources in a controlled manner.
Note: The Designer includes an option to Save MX Data, which is enabled by default.
Creating MX Views
Each time you create or upgrade a repository, the Repository Server executes a SQL script,
that creates the MX views.
Table 15-2 lists the SQL scripts to create MX views:
DB2 db2mxbld.sq_
Informix infmxbld.sq_
Oracle oramxbld.sq_
Sybase sybmxbld.sq_
Teradata termxbld.sq_
These SQL scripts are stored in the PowerCenter Repository Server installation directory.
Dropping MX Views
If you delete a repository, the Repository Server executes a SQL script that drops the MX
views. You can run these SQL scripts (*mxdrp.sq_) in the Designer.
Table 15-3 lists the SQL scripts to drop MX views:
DB2 db2mxdrp.sq_
Informix infmxdrp.sq_
Oracle oramxdrp.sq_
Sybase sybmxdrp.sq_
Teradata termxdrp.sq_
These SQL scripts are stored in the PowerCenter Repository Server installation directory.
REP_DATABASE_DEFS
Table 15-4 lists database definition details:
View Description
REP_ALL_SOURCES This view provides a list of the latest version of sources defined in each folder of a
repository. For more information, see “REP_ALL_SOURCES” on page 339.
REP_ALL_SOURCE_FLDS This view provides all the fields and field properties for all sources defined in
REP_ALL_SOURCES MX View. For more information, see
“REP_ALL_SOURCE_FLDS” on page 341.
REP_SRC_FILES This view provides a list of all file definitions in the repository. For more information,
see “REP_SRC_FILES” on page 343.
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. For more information, see “REP_SRC_TBLS” on page 344.
REP_SRC_FILE_FLDS These views provide access to the fields in a non-relational source. For more
REP_SEG_FLDS information, see “REP_SRC_FILE_FLDS and REP_SEG_FLDS” on page 345.
REP_SRC_TBL_FLDS This view provides access to the fields in relational sources. You can use the source
name to retrieve all the fields belonging to the source. For more information, see
“REP_SRC_TBL_FLDS” on page 346.
REP_ALL_SOURCES
This view provides a list of the latest version of sources defined in each folder of a repository.
Sources include both relational sources and non-relational sources such as XML files and flat
files.
Table 15-6 lists source information in the REP_ALL_SOURCES view:
PARENT_SOURCE_UTC_LAST_SAVED NUMBER UTC time when the parent source was last
modified.
PARENT_SOURCE_CREATION_TIME VARCHAR2 (30) Time when the parent source was last
modified.
SOURCE_UTC_LAST_SAVED NUMBER UTC time when the source display was last
saved.
REP_ALL_SOURCE_FLDS
This view provides all the fields and field properties for all sources defined in
REP_ALL_SOURCES MX View. For global shortcuts, the name of the shortcut displays. For
local shortcuts, the names of shortcut and the parent targets display.
Table 15-7 lists source field information in the REP_ALL_SOURCE_FLDS view:
PARENT_SOURCE_UTC_LAST_SAVED NUMBER UTC time when the parent source was last
saved.
PARENT_SOURCE_CREATION_TIME VARCHAR2 (30) Time when the parent source was last
modified.
SOURCE_LAST_SAVED VARCHAR2 (30) Time when the source was last saved.
REP_SRC_FILES
This view provides a list of all file definitions in the repository. 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. Any flat file imported through the Source Analyzer
has an entry.
Table 15-8 lists file information in the REP_SRC_FILES view:
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.
Table 15-9 lists relational database table information in the REP_SRC_TBLS view:
LAST_SAVED VARCHAR2 (240) Last time the source table was saved.
View Description
REP_ALL_TARGETS This view provides a list of the latest version of all targets defined in each folder of a
repository. For more information, see “REP_ALL_TARGETS” on page 347.
REP_ALL_TARGET_FIELDS This view provides all the fields and field properties for targets defined in
REP_ALL_TARGETS view. For more information, see “REP_ALL_TARGET_FIELDS”
on page 349.
REP_TARG_TBLS This view provides a list of targets in the repository. FIRST_COLUMN_ID is a link to
the set of columns for this table. For more information, see “REP_TARG_TBLS” on
page 350.
REP_TARG_TBL_COLS This view provides the properties of columns defined for the target tables in a data
warehouse or data mart. For more information, see “REP_TARG_TBL_COLS” on
page 351.
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. For global shortcuts, the name of the shortcut displays. For local shortcuts, the
names of shortcut and the parent targets display.
Table 15-13 lists target details in the REP_ALL_TARGETS view:
PARENT_TARGET_UTC_LAST_SAVED NUMBER UTC time when the target was last saved.
PARENT_TARGET_CREATION_TIME VARCHAR2 (30) Time when the target was last modified.
TARGET_UTC_LAST_SAVED NUMBER UTC time when the target was last saved.
PARENT_TARGET_UTC_LAST_SAVED NUMBER UTC time when the parent target was last
saved.
TARGET_UTC_CHECKIN NUMBER UTC time when the target was last checked
in.
TARGET_UTC_LAST_SAVED NUMBER UTC time when the target was last saved.
REP_TARG_TBLS
This view provides a list of targets in the repository. FIRST_COLUMN_ID is a link to the set
of columns for this table. All tables contained in the target table model are part of this view. It
is the primary table list used to delineate a PowerCenter data model. The tables are virtual,
not physically created. Therefore, verify that the table exists before using this view.
REP_TARG_TBL_COLS
This view provides the properties of columns defined for the target tables in a data warehouse
or data mart.
Table 15-16 lists target table column properties for the REP_TARG_TBL_COLS view:
COLUMN_KEYTYPE VARCHAR2 (240) Primary Key, Not a Key, Foreign Key, Primary and
Foreign Key.
View Description
REP_ALL_MAPPINGS This view provides a list of the latest version of all mappings defined in each
folder of a repository. For more information, see “REP_ALL_MAPPINGS” on
page 354.
REP_ALL_MAPPLETS This view provides a list of the latest version of all mapplets defined in each
folder of a repository. For more information, see “REP_ALL_MAPPLETS” on
page 355.
REP_FLD_MAPPING This view shows the source fields used by the target fields in a mapping.
This is the companion view for the REP_TBL_MAPPING view. For more
information, see “REP_FLD_MAPPING” on page 358.
REP_SRC_MAPPING This view shows all sources used in a mapping. For more information, see
“REP_SRC_MAPPING” on page 359.
REP_SRC_FLD_MAP This view shows all of the source fields used in a mapping. For more
information, see “REP_SRC_FLD_MAP” on page 359.
REP_TBL_MAPPING This view shows all of the target tables used in a mapping and provides
source to target mapping information. For more information, see
“REP_TBL_MAPPING” on page 360.
REP_TARG_TBL_JOINS This view contains join information between target tables. For more
information, see “REP_TARG_TBL_JOINS” on page 361.
REP_MAPPING_UNCONN_PORTS This view displays the unconnected ports in sources, targets, and
transformations in a mapping. For more information, see
“REP_MAPPING_UNCONN_PORTS” on page 362.
REP_MAPPING_PORT_CONN This view displays the port-level connections between the objects of a
mapping. For more information, see “REP_MAPPING_PORT_CONN” on
page 363.
PARENT_MAPPING_UTC_LAST_SAVED NUMBER The UTC time when mapping was last saved.
PARENT_MAPPING_LAST_SAVED NUMBER Date and time when parent mapping was last
saved.
MAPPING_UTC_CHECKIN NUMBER UTC time when the mapping was checked in.
MAPPING_UTC_LAST_SAVED NUMBER UTC time when the mapping was last saved.
REP_ALL_MAPPLETS
This view provides a list of the latest version of all mapplets defined in each folder of a
repository. For local shortcuts, the names of the shortcut and the parent mapplets display. For
global shortcuts, the name of the shortcut displays.
Table 15-19 lists mapplet metadata in the REP_ALL_MAPPLETS view:
PARENT_MAPPLET_UTC_LAST_SAVED NUMBER The UTC time when mapplet was last saved.
PARENT_MAPPLET_LAST_SAVED NUMBER The date and time when parent mapplet was
last saved.
MAPPLET_UTC_CHECKIN NUMBER UTC time when the mapplet was checked in.
MAPPLET_UTC_LAST_SAVED NUMBER UTC time when the mapplet was last saved.
REP_TARG_MAPPING
This view provides access to the compound table-level transformation expressions for each
target table. This view pulls information from all the transformation objects that contribute
to the target table in a valid mapping. This view contains information about mappings
defined for target tables only. It does not contain information about sources.
Note: Use the REP_TBL_MAPPING view to analyze source and target relationships. Join
REP_TBL_MAPPING and REP_TARG_MAPPING by MAPPING_NAME to include
column-level mapping information in the REP_FLD_MAPPING view.
Table 15-20 lists expression information in the REP_TARG_MAPPING view:
REP_TARG_FLD_MAP
This view shows compound field-level transformation expressions associated with a target.
This view pulls information from all transformation objects that contribute to the target table
in a valid mapping. There might be many mappings for a set of fields, each distinguished by
the MAPPING_NAME field. The field-level expression contains all the source fields (both
file definition/non-relational source) that make up the value of the target field. For details on
the syntax of the transformation expression, see the Transformation Language Reference.
Table 15-21 lists expression metadata that you find in the REP_TARG_FLD_MAP view:
REP_SRC_FLD_MAP
This view shows all of the source fields used in a mapping. The transformation expression
corresponds to the target fields that get data from a particular source field. This view creates
these expressions by pulling information from all transformation objects that contribute to
the target table in a valid mapping.
Table 15-24 lists mapping source fields:
REP_TBL_MAPPING
This view shows all of the target tables used in a mapping and provides source to target
mapping information. This view pulls information from all transformation objects that
contribute to the target table in a valid mapping to provide the table-level expressions.
Table 15-25 lists mapping target metadata in the REP_TBL_MAPPING view:
REP_TARG_TBL_JOINS
This view contains join information between target tables. Use this view to query the
PowerCenter defined joins for a target table model. It is populated when you link fields in the
Warehouse Designer, or through primary key-foreign key relationships.
Table 15-26 lists target table join metadata in the REP_TARG_TBL_JOINS view:
REP_MAPPING_UNCONN_PORTS
This view displays the unconnected ports in sources, targets, and transformations in a
mapping.
Table 15-27 lists unconnected port metadata in the REP_MAPPING_UNCONN_PORTS
view:
REP_MAPPING_PORT_CONN
This view displays the port-level connections between the objects of a mapping. Objects
include sources, targets, transformations, and mapplets. Unconnected transformations are not
included.
Table 15-28 lists port-level connection metadata in the REP_MAPPING_PORT_CONN
view:
View Description
REP_METADATA_EXTNS This view displays the details of all metadata extensions in the repository. For
more information, see “REP_METADATA_EXTNS” on page 364.
REP_METADATA_EXTN_DEFINES This view displays reusable metadata extensions defined for objects in
metadata extension domains. For more information, see
“REP_METADATA_EXTN_DEFINES” on page 365.
REP_METADATA_EXTNS
This view displays the details of all metadata extensions in the repository.
Table 15-30 lists metadata extension information in the REP_METADATA_EXTNS view:
LINE_NO NUMBER Line number of the text when there are multiple
lines of text.
REP_METADATA_EXTN_DEFINES
This view displays reusable metadata extensions defined for objects in metadata extension
domains.
Table 15-31 lists information in the REP_METADATA_EXTN_DEFINES view:
View Description
REP_ALL_TRANSFORMS This view provides a list of the latest version of all transformations and their properties
in each folder of a repository. For more information, see “REP_ALL_TRANSFORMS”
on page 366.
REP_WIDGET_INST This view displays the details of all transformation instances. For more information,
see “REP_WIDGET_INST” on page 368.
REP_WIDGET_DEP This view displays the details of dependencies between transformation instances in a
mapping. For more information, see “REP_WIDGET_DEP” on page 368.
REP_WIDGET_ATTR This view displays attribute details for transformations, instances, and sessions. For
more information, see “REP_WIDGET_ATTR” on page 369.
REP_WIDGET_FIELD This view displays field level details for transformations. For more information, see
“REP_WIDGET_FIELD” on page 369.
REP_ALL_TRANSFORMS
This view provides a list of the latest version of all transformations and their properties in
each folder of a repository. This view displays both reusable transformations defined in the
Transformation Designer and transformation instances defined in mapping and mapplets. It
also shows all shortcut transformations in a folder. For local shortcuts, the names of the
shortcut and the parent transformation display. For global shortcuts, the name of the shortcut
displays.
Table 15-33 lists transformation metadata in the REP_ALL_TRANFORMS view:
PARENT_WIDGET_LAST_SAVED VARCHAR2 (30) Date and time when transformation was last
saved.
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:
REP_WIDGET_FIELD
This view displays field level details for transformations.
Table 15-37 lists transformation field information in the REP_WIDGET_FIELD view:
View Description
REP_WORKFLOWS This view contains information about individual workflows and workflow scheduling.
For more information, see “REP_WORKFLOWS” on page 372.
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. For more information, see “REP_ALL_TASKS” on page 374.
REP_ALL_SCHEDULERS This view displays a list of schedulers by folder. For more information, see
“REP_ALL_SCHEDULERS” on page 374.
REP_WFLOW_VAR This view displays a list of all variables declared within a workflow or worklet. For
more information, see “REP_WFLOW_VAR” on page 375.
REP_EVENT This view displays the details of events created at the workflow or worklet level.
For more information, see “REP_EVENT” on page 376.
REP_TASK_INST This view displays all task instances within workflows and worklets. For more
information, see “REP_TASK_INST” on page 377.
REP_WORKFLOW_DEP This view shows how individual tasks and worklets are connected within a worklet or
a workflow. For more information, see “REP_WORKFLOW_DEP” on page 377.
REP_TASK_INST_RUN This view displays the run statistics and folder reference for tasks within a workflow
or worklet. For more information, see “REP_TASK_INST_RUN” on page 378.
REP_WFLOW_RUN This view displays the run statistics for all workflows by folder. For more information,
see “REP_WFLOW_RUN” on page 379.
REP_LOAD_SESSIONS This view provides information about reusable sessions in the repository. For more
information, see “REP_LOAD_SESSIONS” on page 380.
REP_SESSION_CNXS This view contains information about connections associated with reusable sessions.
For more information, see “REP_SESSION_CNXS” on page 381.
View Description
REP_SESSION_INSTANCES This view contains connection information for session instances. For more
information, see “REP_SESSION_INSTANCES” on page 381.
REP_SESSION_FILES This view contains file connections associated with reusable sessions. For more
information, see “REP_SESSION_FILES” on page 382.
REP_SESSION_INSTANCE_F This view contains file connections associated with reusable sessions. For more
ILES information, see “REP_SESSION_INSTANCE_FILES” on page 383.
REP_SESS_WIDGET_CNXS This view contains information about the sources and targets used in a session. For
more information, see “REP_SESS_WIDGET_CNXS” on page 383.
REP_COMPONENT This view displays the list of tasks such as a command or an email for each session.
For more information, see “REP_COMPONENT” on page 384.
REP_SESS_PARTITION_DEF This view provides partition details of the sources, targets, and transformations in a
session. For more information, see “REP_SESS_PARTITION_DEF” on page 385.
REP_SESS_CONFIG_PARM This view displays session configuration parameter details. If the session overrides a
parameter in the configured object, the view displays two rows. For more information,
see “REP_SESS_CONFIG_PARM” on page 385.
REP_TASK_ATTR This view displays the attribute values and overridden values for session and
workflow tasks. For more information, see “REP_TASK_ATTR” on page 386
REP_SESS_LOG This view provides log information about sessions. For more information, see
“REP_SESS_LOG” on page 387.
REP_SESS_TBL_LOG This view contains information about the status of an individual session run against a
target. For more information, see “REP_SESS_TBL_LOG” on page 388.
REP_WORKFLOWS
This view contains information about individual workflows and workflow scheduling.
Table 15-39 lists workflow and scheduling information in the REP_WORKFLOWS view:
IS_RUN_ON_LIMIT NUMBER
WORKFLOW_LAST_SAVED VARCHAR2 (30) Date and time when the workflow was last saved.
UTC_LAST_SAVED VARCHAR2 (30) UTC time when task was last saved.
REP_ALL_SCHEDULERS
This view displays a list of schedulers by folder.
Table 15-41 lists information in the REP_ALL_SCHEDULERS view:
START_TIME VARCHAR2 (30) Start time configured for the object associated with
the scheduler.
END_TIME VARCHAR2 (30) End time configured for the object associated with
the scheduler.
LAST_SAVED NUMBER Date and time when this task was last saved.
REP_WFLOW_VAR
This view displays a list of all variables declared within a workflow or worklet.
Figure 15-42 lists variable information in the REP_WFLOW_VAR view:
LAST_SAVED VARCHAR2 (30) Date and time that this task was last saved.
REP_EVENT
This view displays the details of events created at the workflow or worklet level.
Table 15-43 lists event information in the REP_EVENT view:
LAST_SAVED VARCHAR2 (30) Date and time that this event was last saved.
REP_TASK_INST
This view displays all task instances within workflows and worklets.
Table 15-44 lists task instance information in the REP_TASK_INST view:
REP_WORKFLOW_DEP
This view shows how individual tasks and worklets are connected within a worklet or a
workflow.
Table 15-45 lists task and worklet connection information in the REP_WORKFLOW_DEP
view:
CONDITION VARCHAR2 (2000) The value that identifies the condition associated
with the link.
Informatica recommends using the fields in bold to join views.
REP_TASK_INST_RUN
This view displays the run statistics and folder reference for tasks within a workflow or
worklet.
Table 15-46 lists run statistics and folder reference information in the
REP_TASK_INST_RUN view:
REP_WFLOW_RUN
This view displays the run statistics for all workflows by folder.
Table 15-47 lists workflow run statistic information in the REP_WFLOW_RUN view:
LOG_FILE VARCHAR2 (2000) Full path and name of the log file.
USER_NAME VARCHAR2 (240) Name of the user who ran the workflow.
REP_LOAD_SESSIONS
This view provides information about reusable sessions in the repository.
Table 15-48 lists reusable session information in the REP_LOAD_SESSIONS view:
REP_SESSION_CNXS
This view contains information about connections associated with reusable sessions.
Table 15-49 lists reusable session connection information in the REP_SESSION_CNXS
view:
REP_SESSION_INSTANCES
This view contains connection information for session instances. If a session instance
overrides the connection information in a reusable session, this view shows the connection in
the session instance and the connection information in the reusable session. This view does
not show connection information for reusable sessions that are not associated with any
workflows.
REP_SESSION_FILES
This view contains file connections associated with reusable sessions.
Table 15-51 lists reusable session file connection information in the REP_SESSION_FILES
view:
DIR_NAME VARCHAR2 (240) Directory where the source or target file is stored.
CODE_PAGE VARCHAR2 (240) Code page associated with the source or target file.
Informatica recommends using the fields in bold to join views.
REP_SESSION_INSTANCE_FILES
This view contains file connection information for session instances associated with
workflows. If a reusable session is not associated with a workflow, this view does not show file
connection information for the session.
Table 15-52 lists session instance file connection information in the
REP_SESSION_INSTANCE_FILES view:
WORKFLOW_NAME VARCHAR2 (240) Name of the workflow to which the session instance
belongs.
DIR_NAME VARCHAR2 (240) Directory where the source or target file is stored.
CODE_PAGE VARCHAR2 (240) Code page associated with the source or target file.
Informatica recommends using the fields in bold to join views.
REP_SESS_WIDGET_CNXS
This view contains information about the sources and targets used in a session. The reader
and writer types and the connection name also display.
Table 15-53 lists connection information in the REP_SESS_WIDGET_CNXS view:
REP_COMPONENT
This view displays the list of tasks such as a command or an email for each session.
Figure 15-54 lists session component information in the REP_COMPONENT view:
LAST_SAVED VARCHAR2 (30) Time when the partition was last modified.
REP_SESS_CONFIG_PARM
This view displays session configuration parameter details. If the session overrides a parameter
in the configured object, the view displays two rows. Select the row which contains the session
ID reference.
Table 15-56 lists session configuration information in the REP_SESS_CONFIG_PARM
view:
REP_TASK_ATTR
This view displays the attribute values and overridden values for session and workflow tasks.
Table 15-57 lists attribute information in the REP_TASK_ATTR view:
LINE_NO NUMBER Line number of attribute values. Used for storing multiple
lines of attribute values.
WORKFLOW_NAME VARCHAR2 (240) Name of the workflow that contains the session
instance.
REP_SESS_TBL_LOG
This view contains information about the status of an individual session run against a target.
It provides the last update time, row counts, and error status based on a last update timestamp
on a per target basis.
Table 15-59 lists individual session information in the REP_SESS_TBL_LOG view:
TABLE_INSTANCE _NAME VARCHAR2 (240) Target instance name for the session.
View Description
REP_USERS This view provides a list of all PowerCenter users along with details on user privileges
and contact information. For more information, see “REP_USERS” on page 390.
REP_USER_GROUPS This view provides association details between PowerCenter users and the group to
which they belong. For more information, see “REP_USER_GROUPS” on page 391.
REP_GROUPS This view provides a list of PowerCenter groups along with details on group privileges
and contact information. For more information, see “REP_GROUPS” on page 391.
REP_USERS
This view provides a list of all PowerCenter users along with details on user privileges and
contact information.
Table 15-61 lists user information in the REP_USERS view:
USER_ISENABLED NUMBER Specifies whether user can log in. 1 = enabled; 0 = disabled.
REP_GROUPS
This view provides a list of PowerCenter groups along with details on group privileges and
contact information.
Table 15-63 lists group information in the REP_GROUPS view:
View Description
REP_DEPLOY_GROUP_DETAIL This view provides Change Management deployment details. For more
information, see “REP_DEPLOY_GROUP_DETAIL” on page 393.
REP_DEPLOY_GROUP
This view provides information on deployment groups.
Table 15-65 lists deployment group information in the REP_DEPLOY_GROUP view:
CREATED_BY VARCHAR2 (240) Name of user who created the deployment group.
REP_DEPLOY_GROUP_DETAIL
This view provides deployment details.
Table 15-66 lists deployment information in the REP_DEPLOY_GROUP_DETAIL view:
REP_REPOSIT_INFO
This view provides repository information such as repository name and type, domain name,
and database type.
Table 15-67 lists repository information in the REP_REPOSIT_INFO view:
DATABASE_USER VARCHAR2 (240) Database user name used to connect to the repository.
HOSTNAME VARCHAR2 (240) Name of the machine hosting the Repository Server.
View Description
REP_SERVER_INFO This view provides information about PowerCenter Server name, host name, IP
address, and timeout. For more information, see “REP_REPOSIT_INFO” on
page 395.
REP_SERVER_NET This view provides information on PowerCenter Server description, location, and
usage. For more information, see “REP_SERVER_NET” on page 397.
REP_SERVER_NET_REF This view provides information about PowerCenter Server identification and
usage. For more information, see “REP_SERVER_NET_REF” on page 397.
REP_SERVER_INFO
This view provides PowerCenter Server information such as server name, host name, IP
address, and timeout.
Table 15-69 lists PowerCenter Server information in the REP_SERVER_INFO view:
HOST_INFO VARCHAR2 (240) Information on the machine hosting the PowerCenter Server.
HOSTNAME VARCHAR2 (240) Name of the machine hosting the PowerCenter Server.
LAST_SAVED VARCHAR2 (30) Time when the server was last saved.
Informatica recommends using the fields in bold to join views.
REP_SERVER_NET_REF
This view provides PowerCenter Server identification within the grid and usage information.
Table 15-71 lists PowerCenter Server identification and usage information within the grid in
the REP_SERVER_NET_REF view:
View Description
REP_VERSION_PROPS Provides information on the version history of all objects in a PowerCenter repository.
For more information, see “REP_VERSION_PROPS” on page 398.
REP_CM_LABEL Provides information on labels in Change Management. For more information, see
“REP_CM_LABEL” on page 399.
REP_CM_LABEL_REF Provides information on label details in Change Management. For more information,
see “REP_CM_LABEL_REF” on page 399.
REP_VERSION_PROPS
This view provides the version history of all objects in a PowerCenter repository.
Table 15-73 lists label information in the REP_VERSION_PROPS view:
USER_ID NUMBER User who last modified this version of the object.
UTC_LAST_SAVED NUMBER UTC time when the object was last modified.
SAVED_FROM VARCHAR2(240) Host machine name from which the version of the object is
saved.
PURGED_BY_USERID NUMBER User ID who purged the object from the repository.
Informatica recommends using the fields in bold to join views.
REP_CM_LABEL
This view provides label information.
Table 15-74 lists label information in the REP_CM_LABEL view:
REP_CM_LABEL_REF
This view provides information on label details.
Table 15-75 lists label information in the REP_CM_LABEL_REF view:
APPLY_TIME VARCHAR2 (30) Time when label was applied to the object.
Informatica recommends using the fields in bold to join views.
REP_SUBJECT
This view displays folder information such as folder name and description.
Table 15-76 lists folder information in the REP_SUBJECT view:
403
Overview
pmrep and pmrepagent are command line programs that you use to update repository
information and perform repository functions. pmrep and pmrepagent install in the Repository
Server installation directory and also in the PowerCenter Client installation directory.
When you use pmrep and pmrepagent, you can enter commands in interactive mode or
command line mode. For more information on running commands in these modes, see
“Running Commands” on page 406.
Using pmrep
Use pmrep to update session-related parameters and security information in the Informatica
PowerCenter repository. You can use pmrep in either command line mode or interactive mode.
pmrep uses the following types of commands to perform repository tasks:
♦ System commands. Connect to the repository, get help information, clean up persistent
resources, and exit pmrep. Use system commands when you work with pmrep repository
and security commands. For more information on system commands, see “pmrep System
Commands” on page 410.
♦ Repository commands. Back up a repository, create relational connections, change
connection names, update session notification email addresses, and update server variables.
For more information on repository commands, see “pmrep Repository Commands” on
page 412.
♦ Security commands. Add or remove users and groups. Edit user profiles and password
information. Add or remove user and group privileges. For more details on security
commands, see “pmrep Security Commands” on page 449.
♦ Change management commands. Add, copy, or delete deployment groups. Check in
objects. Add or delete labels. Import or export objects. Execute queries. For more details
on change management commands, see “pmrep Change Management Commands” on
page 460.
Using pmrepagent
Use pmrepagent to perform repository functions, such as restoring repositories. pmrepagent
runs in command line mode only.
For more information on pmrepagent commands, see “pmrepagent Commands” on page 477.
Overview 405
Running Commands
When you use pmrep and pmrepagent, you can enter commands in interactive mode or
command line mode.
♦ Interactive mode. You can issue pmrep commands from an interactive prompt. pmrep does
not exit after it completes a command. You cannot use pmrepagent in interactive mode.
♦ Command line mode. You can issue pmrep and pmrepagent commands directly from the
system command line. You can use command line mode to script pmrep and pmrepagent
commands.
The Command syntax contains options and arguments you use when you specify commands.
1. At the command prompt, switch to the directory where the pmrep executable is located.
2. Enter pmrep followed by the command name and its required options and arguments.
3. At the command prompt, type the following command to run pmrep:
pmrep command_name [-option1] argument_1 [-option2] argument_2...
1. At the command prompt, switch to the directory where the pmrepagent executable is
located.
2. Enter pmrepagent followed by the command name and its required options and
arguments.
3. At the command prompt, type the following command to run pmrepagent:
pmrepagent command_name [-option1] argument_1 [-option2] argument_2...
pmrep runs the command and displays the pmrep> prompt again.
3. Type exit to end an interactive session.
Options
Use the following rules when you specify command options and arguments:
♦ Specify options by typing a minus sign followed by a letter, as shown using the Connect
command:
connect -r
♦ Most options require arguments. For example, you must provide the name of the
repository when using the connect command:
connect -r production
♦ Specify options in any order. For example, 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, such as -x and -X.
Option Arguments
Use the following rules to specify arguments:
♦ The first word after the option letter is considered the argument. An option and its
argument do not have to be separated by a space. 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, you must
enclose the argument in double quotes. Back quotes (‘) are not allowed. pmrep and
pmrepagent ignore quotes that do not enclose an argument.
♦ Commands fail and display an error message if any required option or argument is missing
or not specified.
To encrypt a password:
This command runs the encryption utility pmpasswd located in the PowerCenter Server
installation directory. The encryption utility generates and displays your encrypted
password. The following is sample output. In this example, the password entered was
“monday.”
Encrypted string -->bX34dqq<--
Will decrypt to -->monday<--
export PASSWORD
You can assign the environment variable any valid UNIX name.
To encrypt a password:
The encryption utility generates and displays your encrypted password. The following is
sample output. In this example, the password entered was “monday.”
Encrypted string -->bX34dqq<--
Connect Connects to the repository. See “Connecting to a Repository (Connect)” on page 410.
Help Displays help for all commands or for a specified command. See “Getting Help (Help)” on
page 411.
Cleanup Cleans up persistent resources created by pmrep during a session. See “Cleaning up Persistent
Resources (Cleanup)” on page 411.
Required/
Option Argument Name Argument Description
Optional
-h Required repserver_host_name The host name of the machine running the Repository
Server.
-o Required repserver_port_number The port number the Repository Server uses for connections.
Addserver Adds a PowerCenter Server. See “Adding a Server (Addserver)” on page 413.
Addrepository Adds a repository configuration to the Repository Server. See “Adding Repository
Configurations (Addrepository)” on page 414.
ListObjects Lists objects in the repository. See “Listing Repository Objects (ListObjects)” on
page 423.
ObjectImport Imports objects from an XML file. See “Importing Objects (ObjectImport)” on
page 433.
Register Registers local repositories with global repositories. See “Registering Local
Repositories (Register)” on page 434.
Removerepository Removes a repository from the Repository Server cache entry list. See “Removing
Repositories From the Cache (Removerepository)” on page 435.
Run Displays messages stating whether a run has completed or failed. See “Running
Script Files (Run)” on page 436.
ShowConnectioninfo Shows repository name, server, port and user information for the current
connection. See “Showing Connection Information (ShowConnectioninfo)” on
page 437.
StopRepository Stops the repository you last connected to using pmrep. See “Stopping a
Repository (StopRepository)” on page 437.
SwitchConnection Changes the name of an existing connection. See “Changing the Connection
Name (SwitchConnection)” on page 438.
Truncatelog Truncates log details from repository level, folder level, or workflow level. See
“Truncating Workflow and Session Logs (Truncatelog)” on page 439.
Unregister Unregisters local repositories from global repositories. See “Unregistering Local
Repositories (Unregister)” on page 440.
UpdateConnection Changes user name, password, and connect string for a connection. See
“Updating a Database Connection (UpdateConnection)” on page 441.
Updateemailaddr Updates the session notification email addresses. See “Updating the Notification
Email Addresses (Updateemailaddr)” on page 442.
Updateserver Edit server details. See “Updating Server Details (Updateserver)” on page 443.
Updatesrcprefix Updates source table owner names. See “Updating the Source Table Owner
Name (Updatesrcprefix)” on page 445.
UpdateStatistics Updates statistics for repository tables and indexes. See “Updating Repository
Statistics (UpdateStatistics)” on page 447.
Updatetargprefix Updates target table name prefixes. See “Updating the Target Table Name Prefix
(Updatetargprefix)” on page 447.
Required/
Option Argument Name Argument Description
Optional
-v Required server_name The name of the PowerCenter Server you want to change.
-h Required new_host_name The server host name or IP address of the server machine.
-t Optional new_timeout_value The number of seconds the Workflow Manager waits for a
response from the server.
-l Optional new_codepage_name 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.
Required/
Option Argument Name Argument Description
Optional
-h Required repserver_host_name The host name of the Repository Server that manages the
repository.
-o Required repserver_port_number The port number of the Repository Server that manages
the repository.
-u Required database_user_name The account for the database containing the repository.
Set up this account using the appropriate database client
tools.
-c Required database_connect_string 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.
-d Optional code_page 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.
Required/
Option Argument Name Argument Description
Optional
-e Optional DB2_tablespace_name 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.
Required/
Option Argument Name Argument Description
Optional
-o Required output_file_name The name and path of the file for the repository backup.
-d Optional description Creates a description of the backup file based on the string that
follows the option. The backup process truncates any character
beyond 2,000.
-b Optional skip_workflow/ Specify this option if you want to skip tables related to workflow
session_logs and session logs during backup.
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.
Required/
Option Argument Name Argument Description
Optional
-a Required data_source_name The Teradata ODBC data source name. Valid for Teradata
connections only.
-s Required database_type The type of relational connection. For a list of valid database
types, see Table 16-9 on page 418.
-u Required username The user name used for authentication when you connect to
the relational database.
-p Required/ password The password used for authentication when you connect to
Optional the relational database.
Use the -p or -P option, but not both.
-c Required connect_string 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.
-l Required code_page The code page associated with the connection. For a list of
valid code page IDs, see Table 16-10 on page 419.
-r Optional rollback_segment Valid for Oracle connections only. The name of the rollback
segment. A rollback segment records database transactions
that allow you to undo the transaction.
Required/
Option Argument Name Argument Description
Optional
-e Optional environment_sql Enter SQL commands to set the database environment when
you connect to the database.
-z Optional packet_size Valid for Sybase and Microsoft SQL Server connections only.
Optimizes the ODBC connection to Sybase and Microsoft SQL
Server.
-b Optional database_name The name of the database. Valid for Sybase and Microsoft
SQL Server connections only.
-v Optional server_name The name of the database server. Valid for Sybase and
Microsoft SQL Server connections only.
-d Optional domain_name Valid for Microsoft SQL Server connections only. The name of
the domain. Used for Microsoft SQL Server on Windows.
-t Optional trusted_connection 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.
-x Optional n/a 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.
Informix Informix
ODBC ODBC
Oracle Oracle
Sybase Sybase
Teradata Teradata
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
Do not use the -f option if the object type you list is not associated with a folder. The
deploymentgroup, folder, label, and query object types are not associated with folders. All
other object types require the -f option.
Required/
Option Argument Name Argument Description
Optional
-t Optional object_subtype The type of transformation or task to list. When you specify
transformation or task for the object type, you can include
this option to return a specific type.
For a list of subtypes to use with ListObjects, see Table 16-
16 on page 426.
-f Required folder_name The folder to search. Use this option for all object types
except deploymentgroup, folder, label, and query.
-r Optional end_of_record_separator The character or set of characters used to specify the end
of the object metadata. Use a character or set of
characters that is not used in repository object names.
The default is newline /n.
-l Optional end_of_listing_indicator The character or set of characters used to specify the end
of the object list. Specify a character or set of characters
that is not used in repository object names.
If you omit this option, pmrep uses a period.
-b Optional verbose Print more than the minimum information about the
objects. If you omit this option, you print a shorter format
including the object type, the word reusable or non-
reusable, the object name and path. Verbose format
includes the object status, version number, folder name,
and checked out information.
The short format for versioning objects, such as label,
query, deployment group, and connection, includes the
object type and object name. Verbose format includes the
label type, query type, deployment group type, creator
name and creation time.
Listing Folders
You can use ListObjects to return each folder in the repository. When you specify folder for
the object type, pmrep ignores the subtype and folder name.
For example, to list all folders in the repository, enter the following text at the pmrep> prompt:
listobjects -o folder
Or, you can specify a different column separator and end of listing indicator:
listobjects -o folder -c “**” -l #
Listing Objects
You can use ListObjects to list reusable and non-reusable objects in the repository or in a
folder. pmrep does not include instances of reusable objects. When you list objects, you must
include the folder name for all objects that are associated with a folder.
pmrep returns the name of the object with the path when applicable. For example, when a
transformation is in a mapping or mapplet, pmrep returns
mapping_name.transformation_name or mapplet_name.transformation_name.
For a list of transformation or task return values, see Table 16-16 on page 426.
For example, to list all transformation types in a folder, enter the following text at the pmrep>
prompt:
listobjects -o transformation -f myfolder
Or, to list all Stored Procedure transformations in a folder, enter the following text at the
pmrep> prompt:
To list all sessions in a folder, enter the following text at the pmrep> prompt:
listobjects -o session -f myfolder
Required/
Option Argument Name Argument Description
Optional
-s Required session_name The name of the session containing the sources or targets. You can
specify a reusable or non-reusable session. However, you cannot
specify an instance of a reusable session.
To specify a non-reusable session in a workflow, enter the workflow
name and the session name as workflow_name.session_name.
-t Required table_type Specify source to list sources, or specify target to list targets.
mapplet1.ORDERS
Shortcut_To_ITEM_ID
Note: When the mapping contains a mapplet with a source, pmrep includes the mapplet name
with the source, such as mapplet1.ORDERS.
For example, you can list all targets in a non-reusable session in a workflow:
listtablesbysess -f myfolder -s wf_workkflow1.s_nrsess1 -t target
ORDERS_BY_CUSTID
Shortcut_To_tgt2_inst
Required/
Option Argument Name Argument Description
Optional
-o Required object_type_name The object type to list dependencies for. You can specify
source, target, transformation, mapping, session, worklet,
workflow, scheduler, session, session config, task, cube,
and dimension.
-t Required/ object_subtype The type of transformation or task. Ignored for other object
Optional types. For valid subtypes, see Table 16-16 on page 426.
-v Optional version_number List dependent objects for an object version other than the
latest version.
-d Optional dependency_object_t The type of dependent objects to list. You can specify ALL
ype or one or more object types. The default is ALL.
If ALL, then pmrep lists all supported dependent objects. If
you choose one or more objects, then pmrep lists
dependent objects only for these types. To specify multiple
objects, separate them by commas without spaces.
-p Required/ dependency_direction The parents or children dependent objects to list. You can
Optional specify parents, children, or both. Required if you do not
use the -s option.
-u Optional persistent_output_file Send the dependency result to a text file. You can use the
_name text file as input to the ApplyLabel, AddToDeployment
Group, or Validate pmrep commands. The default sends
the query result to stdout.
-a Optional append Append the result to the persistent output file name file
instead of overwriting it.
Required/
Option Argument Name Argument Description
Optional
-r Optional end-of- The character or set of characters used to specify the end
record_separator of the object metadata. Use a character or set of
characters that is not used in repository object names.
The default is newline /n.
-l Optional end-of- The character or set of characters used to specify the end
listing_indicator of the object list. Specify a character or set of characters
that is not used in repository object names.
If you omit this option, pmrep uses a period.
-b Optional verbose Print more than the minimum information about the
objects. If you omit this option, pmrep prints a shorter
format including the object type, the word reusable or non-
reusable, the object name and path. Verbose format
includes the version number and folder name.
The short format for versioning objects, such as label,
query, deployment group, and connection, includes the
object type and object name. Verbose format includes the
creator name and creation time.
Required/
Option Argument Name Argument Description
Optional
-o Required port_number The number of the port where the Repository Server is
running.
Required/
Option Argument Name Argument Description
Optional
-r Required repository_name The name of the repository whose users you want to
notify.
-t Required notify | broadcast The type of message you want to send to user. Notify
sends a message to users connected to the repository.
Broadcast sends a message to users connected to all
repositories managed by the given Repository Server.
The command returns “notify successfully completed” or returns “failed to execute notify”
message. The notification might fail for the following reasons:
♦ The message type you entered is invalid.
♦ You failed to connect to the Repository Server.
♦ The Repository Server failed to notify users.
Required/
Option Argument Name Argument Description
Optional
-o Required/ object_type The object type of the object name. You can specify
Optional source, target, transformation, mapping, session,
worklet, workflow, scheduler, session config, task.
-v Optional version_number Export a version other than the latest version of the
object.
-f Required folder_name The name of the folder containing the object to export.
If you do not specify an object name, then all the
objects in this folder export. If you do specify an object
name, then you must specify the folder containing the
object.
-u Required xml_output_file_name The name of the XML file to contain the object
information.
-l Optional log_file_name Specifies a log file to collect all the export files.
Required/
Option Argument Name Argument Description
Optional
-c Required control_file_name The name of the control file that defines import
options. See “Using the Object Import Control File” on
page 496.
Note: The ObjectImport command does not automatically create a folder if the folder you
specify does not exist in the repository.
Required/
Option Argument Name Argument Description
Optional
-x Required/ repository_password The login password for the local target repository.
Optional Use the -x or -X option, but not both.
-X Required/ repository_password_ The login password environment variable for the local
Optional environment_variable target repository.
Use the -x or -X option, but not both.
Required/
Option Argument Name Argument Description
Optional
-h Optional local_repository_host_name The hostname of the local repository. Use this option
when the local repository is managed by a different
Repository Server. If you use this option, you must use
the -o option as well.
-o Optional local_repository_port_numb The number of the port where the Repository Server is
er running. Use this option when the local repository is
managed by a different Repository Server. If you use
this option, you must use the -h option as well.
The command returns “register successfully completed” or returns “failed to execute register”
message. The registration might fail for the following reasons:
♦ You do not have Administer Repository privilege.
♦ You failed to connect to the Repository Server.
♦ The Repository Server failed to initialize information about the global repository.
♦ The Repository Server failed to register the local repository with the global repository.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-o Optional output_file_name The name of the output file. This option writes all
messages generated by the commands in the script
file into the output file.
The command returns “run successfully completed” or returns “run failed” message. The run
might fail if the Repository Server cannot open the script file or output file.
Note: If you use the -h, -o, and -r options, the named repository stops. Otherwise, the
repository that you last connected to stops.
Required/
Option Argument Name Argument Description
Optional
-o Optional port_number The Repository Server port number. When you use this
option, you must also use the -h and -r options.
-r Optional repository_name The name of the repository to stop. When you use this
option, you must also use the -h and -o options.
To replace connections with pmrep, you must have Super User privilege.
Table 16-26 lists pmrep SwitchConnection options and arguments:
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-t Required all | endtime Use “all” or “endtime.” Use “all” to delete all the
logs. Otherwise, use endtime and specify a time
with a format of: MM/DD/YYYY HH24:MI:SS.
pmrep deletes all logs older than the endtime.
Required/
Option Argument Name Argument Description
Optional
-x Required/ repository_password The login password for the local target repository.
Optional Use the -x or -X option, but not both.
-X Required/ repository_password_ The login password environment variable for the local
Optional environment_variable target repository.
Use the -x or -X option, but not both.
Required/
Option Argument Name Argument Description
Optional
-h Optional local_repository_host_name The hostname of the local repository. Use this option
when the local repository is managed by a different
Repository Server. If you use this option, you must use
the -o option as well.
-o Optional local_repository_port_number The number of the port where the Repository Server is
running. Use this option when the local repository is
managed by a different Repository Server. If you use
this option, you must use the -h option as well.
Required/
Option Argument Name Argument Description
Optional
-u Required new_user_name The user name used for authentication when you connect
to the relational database.
-p Required/ new_database_password The password used for authentication when you connect
Optional to the relational database.
Use the -p or -P option, but not both.
-v Optional new_attribute_value The new attribute value of the connection. Enter “yes” or
“no” for attributes you enable through a checkbox.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-v Required server_name The name of the PowerCenter Server you want to change.
-h Optional new_host_name The server host name or IP address of the server machine.
-t Optional new_timeout_value The number of seconds the Workflow Manager waits for a
response from the PowerCenter Server.
-l Optional new_codepage_name 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.
Required/
Option Argument Name Argument Description
Optional
-m Required/ mapping_name The mapping name. When you update values for a non-
Optional reusable Sequence Generator transformation, you must
include the mapping name.
Required/
Option Argument Name Argument Description
Optional
-s Optional start_value 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 select
Cycle in the transformation properties, the PowerCenter
Server cycles back to this value when it reaches the end
value.
If you designate an invalid value, pmrep gives an error
message and does not update the Sequence Generator
transformation.
-i Optional increment_by The difference between two consecutive values from the
NEXTVAL port.
If you designate an invalid value, pmrep gives an error
message and does not update the Sequence Generator
transformation.
-c Optional current_value The current value of the sequence. Enter the value you
want the PowerCenter Server to use as the first value in
the sequence. If you want to cycle through a series of
values, the current value must be greater than or equal
to the start value and less than the end value.
If you designate an invalid value, pmrep gives an error
message and does not update the Sequence Generator
transformation.
Required/
Option Argument Name Argument Description
Optional
-s Required session_name The name of the session containing the sources to update.
For reusable sessions, specify session_name.
For non-reusable sessions, you must also specify the session
path, such as worklet_name.session_name or
workflow_name.session_name.
-p Required prefix_name The owner name you want to update in the source table.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-s Required session_name The name of the session containing the targets to update.
For reusable sessions, specify session_name.
For non-reusable sessions, you must also specify the session
path, such as worklet_name.session_name or
workflow_name.session_name.
-p Required prefix_name The table name prefix you want to update in the target table.
Changepasswd Changes the password for the user currently connected to the repository.
See “Changing the Repository Password (Changepasswd)” on page 450.
CreateFolder Creates a new folder. See “Creating a Folder (CreateFolder)” on page 451.
Edituser Edits the profile of a user. See “Editing a User (Edituser)” on page 454.
Listallgroups Lists all groups registered with the repository. See “Listing All Groups
(Listallgroups)” on page 455.
Listallprivileges Lists all privileges that you can assign to a user or group. See “Listing All
Privileges (Listallprivileges)” on page 455.
Listallusers Lists all users registered with the repository. See “Listing All Users
(Listallusers)” on page 455.
Registeruser Registers a user from an external directory service to access the Repository.
See “Registering a User (Registeruser)” on page 457.
Rmgroup Removes a group from the repository. See “Removing a Group (Rmgroup)”
on page 457.
Rmuser Removes a user from the repository. See “Removing a User (Rmuser)” on
page 458.
Rmuserfromgroup Removes a user from a group. See “Removing a User from a Group
(Rmuserfromgroup)” on page 459.
You must have the Administer Repository privilege to use pmrep repository security
commands.
Required/
Option Argument Name Argument Description
Optional
-p Required privilege The privilege you want to add. If the privilege contains spaces,
you must enclose this argument in quotes, such as “Administer
Repository.”
-u Required username The name of the user to whom you want to add the privilege. If
you use this option, you cannot use the -g option.
-g Required group_name The name of the group to which you want to add the privilege. If
you use this option, you cannot use the -u option.
Required/
Option Argument Name Argument Description
Optional
-u Required username The user name of the user to add to the group.
-g Required group_name The name of the group to which you want to add the user.
Required/
Option Argument Name Argument Description
Optional
-p Required/ new_password The password that replaces the existing password for the
Optional current user. When you use this option, you must use the -c
option.
Use the -p or -P option, but not both.
-P Required/ new_password_environ The password environment variable that replaces the existing
Optional ment_variable password for the current user. When you use this option, do
not use the -c option.
Use the -p or -P option, but not both.
Required/
Option Argument Name Argument Description
Optional
-d Optional folder_description Description of the folder that appears in the Repository Manager.
-o Optional owner_name The owner of the folder. Any user in the repository can be the
folder owner. The default owner is the user creating the folder.
-p Optional permissions Access rights for the folder. If not specified, Repository Server
assigns default permissions.
This gives the folder owner read, write, and execute permissions (7 = 4+2+1). The owner’s
group has read and write permissions (6 = 4+2). All others have read permission.
The command returns “createfolder successfully completed” or returns “createfolder failed”
message. The creation might fail for the following reasons:
♦ You do not have Administer Repository privilege.
♦ The folder already exists.
♦ The owner does not exist or does not belong to the group.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-u Required username User name of the new user. The user name is case-sensitive
and cannot contain spaces.
-p Required/ password The password of the new user. The password is case-sensitive
Optional and cannot contain spaces. When you use this option, you must
use the -c option.
Use the -p or -P option, but not both.
-c Required/ confirm_password This option ensures you enter the correct password. The
Optional confirm_password argument must match the password
argument. You must use this option when you use the -p option.
-P Required/ new_password_en The password environment variable of the new user. The
Optional vironment_variable password is case-sensitive and cannot contain spaces. When
you use this option, do not use the -c option.
Use the -p or -P option, but not both.
-g Optional group_name The group assigned to the new user. The new user inherits all
permissions and privileges granted to the group. If you do not
specify a group, you add the user to the Public group.
If you specify a group that does not exist, pmrep returns an error and does not carry out the
command. If you do not specify a group for the new user, pmrep assigns the new user to the
Public group.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-u Required username Replace the user name of the user currently connected to
the repository.
-c Required/ confirm_new_password This option ensures you enter the correct password. The
Optional confirm_new_password argument must match the
new_password argument.
If you use the -p option with this command, you must also
use the -c option.
Required/
Option Argument Name Argument Description
Optional
-l Optional login_name Specifies a login to which to map the user name. You can
use this option only with an external directory service.
For example, if you use LDAP to authenticate users in the repository, you could use the
following pmrep command to enable a user called JSmith.
edituser -u JSmith -l JohnS -e yes
The command associates his repository user name, JSmith with the external login name of
JohnS and enables him to use the repository.
Required/
Option Argument Name Argument Description
Optional
-o Optional owner_name The current owner of the folder. Any user in the
repository can be the folder owner. The default
owner is the current user.
Assigning Permissions
You can assign owner, group, and repository permissions by giving three digits when you use
the -p option. The first digit corresponds to owner permissions, the second corresponds to the
permissions of the group that the user belongs to, and the third corresponds to all other
permissions.
Specify one number for each set of permissions. Each permission is associated with a number.
Designate 4 for read permission, 2 for write permission, and 1 for execute permission. To
assign permissions, you specify 4, 2, 1, or the sum of any of those numbers.
For example, if you want to assign default permissions, use the following command syntax:
-p 764
This gives the folder owner read, write, and execute permissions (7 = 4+2+1). The owner’s
group has read and write permissions (6 = 4+2). All others have read permission.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-p Required privilege The privilege you want to remove. If the privilege contains spaces,
you must enclose this argument in quotes, such as “Administer
Repository.”
-u Required username The name of the user from whom you want to remove the privilege.
If you use this option, you cannot use the -g option.
-g Required group_name The name of the group from which you want to remove the
privilege. If you use this option, you cannot use the -u option.
Required/
Option Argument Name Argument Description
Optional
-u Required username User name you want to remove from the repository.
Required/
Option Argument Name Argument Description
Optional
-g Required group_name The name of the group from which to remove the user.
ApplyLabel Applies a label to an object or set of objects in a folder. See “Labeling (ApplyLabel)”
on page 462.
ClearDeploymentGroup Clears all objects from a deployment group. See “Clearing a Deployment Group
(ClearDeploymentGroup)” on page 465.
CreateLabel Creates a label object. See “Creating a Label (CreateLabel)” on page 466.
DeleteLabel Deletes a label object and all object references to the label. See “Deleting a Label
(DeleteLabel)” on page 467.
FindCheckout Prints a list of checked out objects in the repository. See “Listing Checked Out Items
(FindCheckout)” on page 472.
UndoCheckout Undoes an object check out, release the lock and revert to the last checked in
version. See “Undoing a Checkout (UndoCheckout)” on page 473.
Required/
Option Argument Name Argument Description
Optional
-p Required deployment_group_name The name of the deployment group to add objects to.
-n Required/ object_name The name of the object you are adding to the
Optional deployment group. You must use this parameter when
you add a specific object. You cannot specify a
checked out object. You cannot specify an object if
you use the -i option.
-o Required/ object_type The type of object you are adding. You can specify
Optional source, target, transformation, mapping, session,
worklet, workflow, scheduler, session configuration,
task, cube, and dimension. Required when adding a
specific object.
-t Required/ object_subtype The type of task or transformation you are adding. For
Optional valid subtypes, see Table 16-16 on page 426.
Required/
Option Argument Name Argument Description
Optional
-v Optional version_number The version of the object to add. The default is to add
the latest version of the object to the deployment
group.
-f Required/ folder_name The folder that contains the object you are adding. You
Optional must specify the folder if you specify an object name.
Labeling (ApplyLabel)
Use the ApplyLabel command to apply a label to an object or a set of objects in a folder. If
you specify a folder, all the objects in the folder receive the label. You can apply the label to
dependent objects. If you use the dependent_object_type option, pmrep labels all dependent
objects. To apply a label to selected dependent objects, separate each object type name by a
comma with no spaces between them on the command line.
Use ApplyLabel to label reusable input objects. If you want to label non-reusable input
objects, you must use a persistent input file that contains encoded object IDs. For more
information on using a persistent input file, see “Using the Persistent Input File” on page 494.
If ApplyLabel succeeds, pmrep displays either no status information or a list of objects that
already have the label. If the command fails, pmrep displays the failure reason.
For more information on applying labels, see “Applying Labels” on page 221.
To label objects, you must have the following privileges and permissions:
♦ Use Repository Manager privilege
♦ Read permission on the folder
♦ Execute permission on the label
Required/
Option Argument Name Argument Description
Optional
-n Required/ object_name The name of the object to receive the label. If you are
Optional updating a specific object, then this parameter is
required. You cannot specify objects if you use the -i
option.
-o Required/ object_type The type of object to apply the label to. You can
Optional specify source, target, transformation, mapping,
session, worklet, workflow, scheduler, session config,
task, cube, or dimension. Required when applying a
label to a specific object.
-v Optional version_number The version of the object to apply the label to. The
command fails if the version is checked out. Applies
the label to the latest version of the object by default.
-f Optional folder_name The folder that contains the object(s). If you specify a
folder, but no object name, pmrep applies the label to
all objects in the folder. If you specify a folder with an
object name, pmrep searches the folder for the object.
You cannot specify a folder if you use the -i option.
-d Required dependent_object_type The dependent objects to label. Use this option with
option -p. If you specify an object type, then the label
applies to dependent objects of that object type.
Required/
Option Argument Name Argument Description
Optional
-m Optional move_label Move a label from the current version to the latest
version of an object. You can use this argument only
when the label type is one_per_object. See “Creating
a Label (CreateLabel)” on page 466.
Users with Administer Repository privilege can check in objects for other users.
Table 16-55 lists pmrep Checkin options and arguments:
Required/
Option Argument Name Argument Description
Optional
-o Required object_type The type of object you are checking in: source, target,
transformation, mapping, session, worklet, workflow,
scheduler, session config, task, cube, or dimension.
-n Required object_name The name of the object that you are checking in.
Required/
Option Argument Name Argument Description
Optional
-p Required deployment_group_name The name of the deployment group that you want to
clear.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-t Optional label_type Allows multiple versions to have this label. If you omit
this option, you can apply the label to only one
version.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-f Optional force_delete Delete the label without confirmation. If you omit this
argument, the command prompts you for a
confirmation before it deletes the label.
Required/
Option Argument Name Argument Description
Optional
-c Required control_file_name The name of the XML file containing the Copy Wizard
specifications. The control file is required. For more
information on using the control file, see “Using the
Deployment Control File” on page 504.
-r Required target_repository_name The repository you are deploying the group to.
-u Required/ target_repository_user_name The login user name for the target repository. Not
Optional required if you are copying the deployment group to
the same repository.
-x Required/ target_repository_user_passwo The login password for the target repository. Not
Optional rd required if you copy the deployment group to the same
repository.
Use the -x or -X option, but not both.
-X Required/ target_repository_password_en The login password environment variable for the target
Optional vironment_variable repository. Not required if you copy the deployment
group to the same repository.
Use the -x or -X option, but not both.
-h Required/ target_repository_server_host_ The host name of the Repository Server managing the
Optional name target repository. Not required if you copy the
deployment group to the same repository.
Required/
Option Argument Name Argument Description
Optional
-l Optional log_file_name The log file that records each deployment step. If you
omit this option, it outputs to the screen.
Required/
Option Argument Name Argument Description
Optional
-c Required control_file_name The name of the XML file containing the copy wizard
specifications. For more information on the control file,
see “Using the Deployment Control File” on page 504.
-r Optional target_repository_name The repository name to deploy the group to. Not
required if the target repository is the same as the
source.
-u Optional target_repository_user_name The login user name for the target repository. Not
required if you are copying the deployment group to
the same repository.
-x Required/ target_repository_user_passwo The login password for the target repository. Not
Optional rd required if you are copying the deployment group to
the same repository.
Use the -x or -X option, but not both.
Required/
Option Argument Name Argument Description
Optional
-X Required/ target_repository_password_en The login password environment variable for the target
Optional vironment_variable repository. Not required if you are copying the
deployment group to the same repository.
Use the -x or -X option, but not both.
-h Optional target_repository_server_host_ The host name of the Repository Server managing the
name target repository. Not required if you copy the
deployment group to the same repository.
-l Optional log_file_name The log file that records each deployment step. If you
omit this option, it outputs to the screen.
Required/
Option Argument Name Argument Description
Optional
-t Optional query_type The type of query to run. You can specify public or
private. If not specified, pmrep searches all the private
queries first to find the matching query name. Then it
searches the public queries.
Required/
Option Argument Name Argument Description
Optional
-u Optional persistent_output_file_name Send the query result to a text file. If you do not
specify a file name, the query result goes to stdout.
-b Optional verbose Print more than the minimum information about the
objects. If you omit this option, pmrep prints a shorter
format including the object type, the word reusable or
non-reusable, the object name and path. Verbose
format includes the object status, version number,
folder name, and checked out information.
The short format for versioning objects such as label,
query, deployment group, and connection, includes
the object type and object name. Verbose format
includes the label type, query type, deployment group
type, creator name, and creation time.
For more information about finding checked out objects, see “Checking Out and Checking
In Objects” on page 211.
To list checked out items, 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
Required/
Option Argument Name Argument Description
Optional
-o Optional object_type The object type you want to list. You can specify
source, target, transformation, mapping, session,
worklet, workflow, scheduler, session config, task,
cube, or dimension. If you omit object type, pmrep
ignores the -f and -u options and the command returns
all checked-out objects in the repository.
-f Optional folder_name Return a list of checked out objects for the object type
in the specified folder. The default is to list objects for
the object type across folders. Folder name is optional
if you specify an object type.
-u Optional all_users List the checked out objects by all users. The default
is to list only checked out objects by the current user.
Required/
Option Argument Name Argument Description
Optional
-b Optional verbose Print more than the minimum information about the
objects. If you omit this option, pmrep prints a shorter
format including the object type, the word reusable or
non-reusable, the object name and path. Verbose
format includes the version number and folder name.
The short format for versioning objects such as label,
query, deployment group, and connection, includes
the object type and object name. Verbose format
includes the creator name and creation time.
Required/
Option Argument Name Argument Description
Optional
-o Required object_type The type of object. You can specify source, target, transformation,
mapping, session, worklet, workflow, scheduler, session config,
task, cube, dimension.
-t Required/ object_subtype The type of transformation or task. Ignored for other object types.
Optional For valid subtypes, see Table 16-16 on page 426.
When you run Validate, you can choose to output information about object status:
♦ valid. Objects successfully validated.
♦ saved. Objects saved after validation.
♦ skipped. Shortcuts and object types that do not require validation.
♦ save_failed. Objects that did not save because of lock conflicts or they were checked out by
another user.
♦ invalid_before. Objects invalid before the validation check.
♦ invalid_after. Objects invalid after the validation check.
Required/
Option Argument Name Argument Description
Optional
-n Required object_name The name of the object to validate. Do not use this
option if you are using the -i argument.
-o Required/ object_type The type of object to validate. You can specify source,
Optional target, transformation, mapping, session, worklet,
workflow, scheduler, session config, task, cube,
dimension. Required if you are not using a persistent
input file.
-v Optional version_number The version of the object to validate. The default is the
latest or checked out version of the object.
-s Optional save_upon_valid Save objects that change from invalid to valid to the
repository.
-p Optional output_options The kind of object you want to output to the persistent
output file or stdout after validation. You can specify
valid, saved, skipped, save_failed, invalid_before, or
invalid_after. To specify one or more options, separate
them by commas. You should specify output_options
when you use the persistent_output_file_name.
Required/
Option Argument Name Argument Description
Optional
-u Optional persistent_output_file_name The name of an output text file. If you specify a file
name, the query writes the results to a file. You should
also specify output_options.
-a Optional append Append the results to the persistent output file instead
of overwriting it.
-b Optional verbose Print more than the minimum information about the
objects. If you omit this option, pmrep prints a shorter
format including the object type, the word reusable or
non-reusable, the object name and path. Verbose
format includes the version number and folder name.
The short format for versioning objects such as label,
query, deployment group, and connection, includes
the object type and object name. Verbose format
includes the creator name and creation time.
Bulkrestore Restores a Teradata repository from a repository backup file using Fastload. See
“Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479.
Create Creates repository tables in the database. See “Creating a Repository (Create)”
on page 480.
Delete Deletes the repository tables from the database. See “Deleting a Repository
(Delete)” on page 481.
Registerplugin Registers a new external module to the repository. See “Registering a Plug-in
(Registerplugin)” on page 482.
Restore Restores a repository from a repository backup file. See “Restoring a Repository
(Restore)” on page 485.
Unregisterplugin Unregisters a plug-in module from the repository. See “Unregistering Plug-ins
(Unregisterplugin)” on page 487.
Required/
Option Argument Name Argument Description
Optional
-r Required repository_name The name of the repository you want to back up.
-o Required output_file_name The name and path of the file for the repository
backup.
-f Optional n/a This option has no argument. Include this option if you
want to overwrite any existing file with the same name.
Note: pmrep also allows you to back up a repository. You can use the pmrep Backup command
when the repository is running. For details, see “Backing up a Repository (Backup)” on
page 416.
Required/
Option Argument Name Argument Description
Optional
-c Required database_connect_string The connect string the Repository Agent uses to connect
to the repository database.
For a list of connect string syntax, see Table 16-1 on
page 405.
-h Required host_name The host name of the Repository Server that manages
the repository.
-o Required port_number The port number of the Repository Server that manages
the repository.
-g Optional n/a This option has no argument. Use this option if you want
to promote the repository to a global repository.
Required/
Option Argument Name Argument Description
Optional
-b Optional skip_workflow/session_log Skips tables related to workflow and session logs during
backup.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-h Required host_name The host name of the Repository Server that manages
the repository.
-g Optional n/a This option has no argument. Include this option if you
want to promote the repository to a global repository.
-z Optional repository_creation_parameters Use this option to specify the tablespace name for IBM
DB2 EEE databases.
Use the following format to specify the tablespace
name:
“%tablespace=<tablespace_name>”
Do not include spaces around the equals sign.
pmrepagent interprets the spaces as part of the
tablespace name.
-v Optional n/a This option has no argument. Include this option if you
want to enables object versioning for the repository.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-c Required database_connect_string The connect string the Repository Agent uses to connect
to the repository database.
For a list of connect string syntax, see Table 16-1 on
page 405.
-f Required/ n/a Use this option to delete a global repository. All registered
Optional local repositories must be running. This option
unregisters local repositories.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-c Required database_connect_string The connect string the Repository Agent uses to connect
to the repository database.
For a list of connect string syntax, see Table 16-1 on
page 405.
-i Required input_xml_file_name The name of the XML file describing the plug-in.
-l Required if login_name The NIS login of the user registering an external security
registering module. If the plug-in contains an authentication module
security you must supply the external login name, or the
module registration fails. This login becomes the administrator
components user name in the repository. Do not use this option for
other plug-ins.
Required/
Option Argument Name Argument Description
Optional
-k Optional n/a Stores the CRC of the plug-in library in the repository.
When the Repository Agent loads the module, it checks
the library against the CRC.
Example
An administrator administers PowerCenter for a company that has a centralized LDAP NIS
for user authentication. When he upgrades PowerCenter, he decides to use the LDAP for
repository user authentication. The upgrade installs the LDAP security module in the
repository security folder. 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.xml -l adminuser -w admnpass
The -l login name and -w login password options contain the valid NIS login information for
the user running the pmrepagent command. After registration, the administrator user must
use this login name and password to access the repository.
Note: The login name and password must be valid in the external directory, or the
administrator cannot access the repository using LDAP.
The -i option contains the XML file name that describes the security module. For more
information about this XML file, see “Registering and Unregistering LDAP Security
Modules” on page 88.
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-z Optional repository_creation_parameters Use this option to specify the tablespace name for
IBM DB2 EEE databases.
Use the following format to specify the tablespace
name:
“%tablespace=<tablespace_name>”
Do not include spaces around the equals sign.
pmrepagent interprets the spaces as part of the
tablespace name.
Required/
Option Argument Name Argument Description
Optional
Note: You can also restore Teradata repositories using Fastload. For more information, see
“Restoring Teradata Repositories using Fastload (Bulkrestore)” on page 479.
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.
restore -r repository1 -t oracle -u admin-ora -p admin-passwd-ora -c
oracle-server001 -h solaris001 -o 5001 -v adminuser -x adminpass
-i repository1_backup.rep
Required/
Option Argument Name Argument Description
Optional
Required/
Option Argument Name Argument Description
Optional
-w Required/ new_password Specifies a new password for the user running the
Optional unregister command. When you unregister an
external authentication module, 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.
Use the -w or -W option, but not both.
Example
As an administrator, you decide to switch from the LDAP security module back to repository
authentication. You remove the user name-login mapping. Any users that you added to the
system under repository authentication can log in with their old user names and passwords.
Any users you added to the repository under the LDAP security cannot log in until you
enable their user names.
Note: The Administrator must provide his LDAP NIS login and password to use the
Unregisterplugin command. He must also provide a new password to use after he switches
back to repository user authentication.
Required/
Option Argument Name Argument Description
Optional
REM This batch file uses pmrep to connect to and back up the repository
Production on the server Central
@echo off
You can run script files from the command interface. You cannot run pmrep batch files while
in pmrep interactive mode.
pmrep and pmrepagent indicate the success or failure of a command with a return code. Return
code (0) indicates that the command succeeded. Return code (1) indicates the command
failed.
Tip: When you create script files using pmrep commands, Informatica recommends that you
include a connect command as the first command called by the script file. This helps ensure
you are performing tasks on the correct repository.
Use the -n option when you use the Updatesrcprefix or Updatetargprefix commands.
When you include the -n option, you must enter the name of the source or target instance for
the -t option. The source or target instance name must match the name displayed in the
session properties or the name output by the Listtablesbysess command.
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.
Also, use the -n option to update a source even if the session uses a shortcut to a mapping.
When using ListObjects, specify a character or set of characters that is not used in
repository object names for the column separator, end of record indicator, and end of listing
indicator.
Use characters that are not used in repository object names when you specify characters to
separate records and columns, and to indicate the end of the listing. This helps you use a shell
script to parse the object metadata.
Use the -v option when restoring a repository that uses an external directory service for user
management.
When you include the -v option with Restore, 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, the restored repository defaults to repository authentication mode.
You lose the login name-user name mappings.
493
Using the Persistent Input File
When you run pmrep with some tasks, you can use a persistent input file to specify repository
objects that you want to process. The persistent input file represents objects already in your
repository. You can create a persistent input file manually or by using pmrep.
You can use a persistent input file with the following pmrep commands:
♦ AddToDeploymentGroup. Add objects to a Deployment Group.
♦ ApplyLabel. Label objects.
♦ ExecuteQuery. Run a query to create a persistent input file. You can use the file for other
pmrep commands.
♦ ListObjectDependencies. List dependency objects. This command can use a persistent
input file for processing, and it can create one.
♦ ObjectExport. Export objects to an XML file.
♦ Validate. Validate objects. This command can use a persistent input file for processing,
and it can create one.
The persistent input file has the following format:
encoded ID, foldername, object_name, object_type, object_subtype,
version_number, resusable|non-reusable
Example
You can use the ExecuteQuery command to create a persistent input file of objects to process
in another pmrep command. For example, suppose you want to export all logically deleted
objects from the repository. You might create a query called “find_deleted_objects.” When
you run the query with pmrep, it finds all the deleted objects in the repository and outputs the
results to a persistent input file.
ExecuteQuery -q find_deleted_objects -t private -u deletes_workfile
You can use deletes_workfile as the persistent input file to ObjectExport. ObjectExport
exports all the referenced objects to an XML file called exported_del_file.
ObjectExport -i deletes_workfile -u exported_del_file
The object is a source object. It includes the database definition as a prefix. The record has the
word “none” in place of the encoded ID, and the record does not require the reusable
argument.
<!--IMPORTPARAMS This inputs the options and inputs required for import operation -->
<!--CHECKIN_AFTER_IMPORT Check in objects on successful import operation -->
<!--CHECKIN_COMMENTS Check in comments -->
<!--APPLY_LABEL_NAME Apply the given label name on imported objects -->
<!--RETAIN_GENERATED_VALUE Retain existing sequence generator, normalizer and XML DSQ
current values in the destination -->
<!--COPY_SAP_PROGRAM Copy SAP program information into the target repository -->
<!--APPLY_DEFAULT_CONNECTION Apply the default connection when a connection used by a
session does not exist in the target repository -->
<!ELEMENT IMPORTPARAMS (FOLDERMAP*, TYPEFILTER*, RESOLVECONFLICT?)>
<!ATTLIST IMPORTPARAMS
CHECKIN_AFTER_IMPORT (YES | NO) "NO"
CHECKIN_COMMENTS CDATA #IMPLIED
APPLY_LABEL_NAME CDATA #IMPLIED
RETAIN_GENERATED_VALUE (YES | NO) "NO"
COPY_SAP_PROGRAM (YES | NO) "YES"
APPLY_DEFAULT_CONNECTION (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
SOURCEREPOSITORYNAME CDATA #REQUIRED
TARGETFOLDERNAME CDATA #REQUIRED
TARGETREPOSITORYNAME CDATA #REQUIRED
>
<!--Import will only import the objects in the selected types in TYPEFILTER node -->
<!--TYPENAME type name to import. This should comforming to the element name in
powermart.dtd, e.g. SOURCE, TARGET and etc.-->
<!ELEMENT TYPEFILTER EMPTY>
<!ATTLIST TYPEFILTER
<!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. 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
RESOLUTION(REPLACE | REUSE | RENAME) #REQUIRED
>
<!--QUERYOBJECT allows objects result from a query to apply replace/reuse upon conflict -->
<!ELEMENT QUERYOBJECT EMPTY>
<!ATTLIST QUERYOBJECT
QUERYNAMECDATA #REQUIRED
RESOLUTION(REPLACE | REUSE | RENAME) #REQUIRED
>
Table A-1. Object Import Control File Elements and Attributes (pmrep)
TYPEFILTER TYPENAME Imports just the objects from a specific node, such as
sources, targets, or mappings.
RESOLVECONFLICT (see the following elements) Allows you to specify conflict resolutions for objects.
QUERYOBJECT QUERYNAME Identifies objects from this query result for conflict
resolution specification.
<RESOLVECONFLICT>
<LABELOBJECT LABELNAME ="Monthend"
RESOLUTION = "REPLACE"/>
</IMPORTPARAMS>
<!--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. This should conforming to the element name in
powermart.dtd, e.g. SOURCE, TARGET and etc.-->
<TYPEFILTER TYPENAME="SOURCE"/>
<TYPEFILTER TYPENAME="TARGET"/>
<TYPEFILTER TYPENAME="MAPPLET"/>
<TYPEFILTER TYPENAME="MAPPING"/>
<TYPEFILTER TYPENAME="TRANSFORMATION"/>
<TYPEFILTER TYPENAME="SHORTCUT"/>
<TYPEFILTER TYPENAME="CONFIG"/>
<TYPEFILTER TYPENAME="TASK"/>
<TYPEFILTER TYPENAME="SESSION"/>
<TYPEFILTER TYPENAME="SCHEDULER"/>
<TYPEFILTER TYPENAME="WORKFLOW"/>
<TYPEFILTER TYPENAME="SCHEDULER"/>
<TYPEFILTER TYPENAME="WORKLET"/>
<!--RESOLVECONFLICT allows to specify resolution for conflicting objects during import. 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"/>
OVERRIDEFOLDER SOURCEFOLDERNAME Specifies the current folder that shortcuts point to.
APPLYLABEL SOURCELABELNAME Applies a label to all the objects in the source group.
SOURCEMOVELABEL Moves the label from a different version of the object in the
source group to the deployment group version of the object.
If the Repository Agent detects the label is applied to
another version of the same object, you can choose to
move the label to the selected version of the object.
TARGETMOVELABEL Moves the label from a different version of the object in the
target group to the deployment group version of the object.
If the Repository Agent detects the label is applied to
another version of the same object, you can choose to
move the label to the latest version of the object.
Example
Suppose you want to deploy the latest version of a folder and include all dependencies. You
need to retain the current values in a Sequence Generator transformation, and you need to
point the shortcuts from the sc_folder to the new_sc_folder. After you copy the folder, you
want to rename it to “new_year.”
You might create a control file with following attributes:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE DEPLOYPARAMS SYSTEM "depcntl.dtd">
<DEPLOYPARAMS DEFAULTSERVERNAME ="info7261"
COPYPROGRAMINFO ="NO"
COPYWFLOWVARPERVALS ="NO"
COPYWFLOWSESSLOGS ="NO"
COPYDEPENDENCY ="YES"
LATESTVERSIONONLY = "NO">
<REPLACEFOLDER FOLDERNAME ="NEW_YEAR"
RETAINVARPERVALS ="YES"/>
</DEPLOYPARAMS>
REM This batch file uses pmrep to connect to and back up the repository
Production on the server Central
@echo off
You can run script files from the command interface. You cannot run pmrep batch files while
in pmrep interactive mode.
pmrep and pmrepagent indicate the success or failure of a command with a return code. Return
code (0) indicates that the command succeeded. Return code (-1) indicates the command
failed.
Tip: When you create script files using pmrep commands, Informatica recommends that you
include a connect command as the first command called by the script file. This helps ensure
you are performing tasks on the correct repository.
Permissions and
Privileges by Task
This appendix summarizes the available tasks in the PowerCenter Client tools. It then lists the
repository privileges and folder permissions required to perform each task in these tools:
♦ Designer Tasks, 510
♦ Workflow Manager Tasks, 511
♦ Workflow Monitor Tasks, 513
♦ pmcmd Tasks, 515
♦ Repository Manager Tasks, 516
♦ pmrep Tasks, 519
♦ pmrepagent Tasks, 520
509
Designer Tasks
To perform the following Designer tasks, you must have one of the listed sets of privileges and
permissions.
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:
Create shortcuts from a shared folder Use Designer Read permission in the shared folder.
Read and write permission in the
destination folder.
Copy object from one folder to Use Designer Read permission in the originating
another folder. Read and write permission for
the destination folder.
Table B-2. Required Privileges and Permissions for Workflow Manager Tasks
Connection
Repository
Workflow Manager Task Folder Permission Object
Privilege
Permission
Connect to the repository using the Use Workflow None required None required
Workflow Manager Manager
Connection
Repository
Workflow Manager Task Folder Permission Object
Privilege
Permission
Stop the PowerCenter Server Use Workflow None required None required
Manager and
Administer Server
Configure database, FTP, and Use Workflow None required None required
external loader connections in the Manager
Workflow Manager
Edit database, FTP, and external Use Workflow None required Read, Write
loader connections in the Workflow Manager
Manager
Register PowerCenter Servers and Administer Server None required None required
configure server variable directories
Table B-3. Required Privileges and Permissions for Workflow Monitor Tasks
View session details and session Use Workflow Read None required
performance details Manager
Ping the PowerCenter Server None required None required None required
Stop the PowerCenter Server Administer Server None required None required
Table B-5. Required Permissions and Privileges for Repository Manager Tasks
Check in/undo check out for Administer Repository Write None required
other users
Check out/undo check out Use Repository Manager Write None required
Connect to the repository using Browse Repository None required None required
the Repository Manager
Copy a folder within the same Administer Repository Read permission on the Read
repository original folder
Delete a folder Browse Repository Folder owner and read None required
permission
Delete from Deployment Group Use Repository Manager N/A Write on deployment
group
Edit folder Browse Repository Folder owner and read None required
permission
Edit folder properties Browse Repository Folder owner and read None required
permission
Freeze folder Browse Repository Folder owner and read None required
permission
Import, export, or remove the Browse Repository None required None required
registry
Manage users, groups, and Administer Repository None required None required
privileges
Receive user and group Super User None required None required
notifications
Terminate other users and Super User None required None required
unlock objects
Unlock any locked object or Super User None required None required
folder in the repository
Connection Object
pmrep Task Repository Privilege Folder Permission
Permission
Update source table owner Use Workflow Manager Write None required
names (Updatesrcprefix)
Update target table name Use Workflow Manager Write None required
prefixes (Updatetargprefix)
521
ApplyLabel exporting objects 266
description 462 global repository 117
associating importing objects 266
server with sessions 245 local repository 75
audit trails 208 repository 51, 192
configuration setting 110 command line program
creating 153 See pmrep
authenticating users See also pmrepagent
description 131 comments
authentication accessing metadata 335
switching methods 133 comparing
using LDAP 131 See also Designer Guide
See also Workflow Administration Guide
folders 174
B Repository objects 45
Workflow Manager objects 21, 45
backing up conflicts
repositories 66 copying Designer objects 310
repositories with pmrep 416 copying workflow segments 308
repositories with pmrepagent 477 database connections 307
Backup command mapping 307
pmrep 416 resolving when importing 281
pmrepagent 477 connect string
Bulkrestore command examples 405
description 479 syntax 405
connecting
to repositories 30, 31
C connection objects
See also Workflow Administration Guide
Changepassword definition 10
description 450 permissions and privileges 245
Checkin connections
description 464 terminating 83
CheckinCommentsRequired viewing 79
repository configuration 110 connectivity
checking in connect string examples 405
description 213 connectivity license keys
non-reusable objects 213 overview 119
when importing objects 280 ConnectString
checking out setting for repository configuration 107
description 211 Console Tree
non-reusable objects 211 Administration Console 52
undoing a checkout 213 control file
checkouts deployment 504
searching for checked out objects 211 object import 496
viewing 211 ObjectImport XML example 500
Cleanup Copy Wizard
description 411 copying objects 302
ClearDeploymentGroup resolving conflicts 300
description 465 viewing object dependencies 305
code pages
See also Installation and Configuration Guide
522 Index
copying repository users 134
See also copying deployment groups 254 user groups 128
See also copying folders 248 users under an external directory 137
Copy Wizard procedure 302
deployment groups 254
Designer objects 310 D
folders 250
in Workflow Manager 306 database connections
mapping segments 310 See also Workflow Administration Guide
mapping variables 307 during folder or deployment group copy 245
mapplet segments 310 permissions and privileges 245
repositories 62 database definitions
resolving conflicts 300 MX view 338
sessions 306 DatabaseArrayOperationSize
shortcuts 195 configuration setting 110
workflow segments 308 setting for repository configuration 110
workflows 306 DatabaseConnectionTimeout
worklets 306 setting for repository configuration 110
copying deployment groups DatabasePoolSize
copying composite objects 255 setting for repository configuration 110
copying shortcuts 256 DatabaseType
in advanced mode 244 setting for repository configuration 107
in typical mode 244 DateDisplayFormat
steps 258 setting for repository configuration 109
copying folders DB2
from local to global repositories 250 See IBM DB2
in advanced mode 244 DBPassword
in typical mode 244 setting for repository configuration 107
shortcuts in folders 249 DBUser
within a repository 250 setting for repository configuration 107
CRCVALUE codes Decision Support Systems (DSS)
overview 267 working with Informatica metadata 335
Create command default groups
description 480 security 127
CreateConnection default users
description 417 editing 131
CreateDeploymentGroup Delete command
description 465 description 481
Creategroup Deleteconnection
description 452 description 420
CreateLabel DeleteDeploymentGroup
description 466 description 466
Createuser DeleteFolder
description 452 description 453
creating DeleteLabel
global shortcuts 190 description 467
local shortcuts 187 Deleteserver
metadata extensions 328 description 421
MX views 336 deleting
repositories 116 folders 173
repositories using pmrepagent 480 metadata extensions 332
Index 523
recovering deleted objects 215 dynamic deployment groups
repositories 64 associating with a query 240
repositories using pmrepagent 481 definition 236
user groups 129 editing 240
versioned objects 215 DynamicConfigRefreshInterval
depcntl.dtd setting for repository configuration 110
listing 504
dependencies
source-target 27
viewing 27, 37
E
dependent objects editing
exporting and importing 270 folder permissions 149
DeployDeploymentGroup folders 173
description 467 metadata extensions 331
DeployFolder repository users 138
description 469 user 138
deploying objects user groups 129
depcntl.dtd 504 Edituser
rolling back a deployment 238 description 454
deployment groups Enablerepository
copying 254, 258 description 422
copying composite objects 255 enabling a user
copying shortcuts 256 description 139
creating 237 environment variables
definition 218 repository username and password 408
dynamic 240 Error Severity Level
editing 237 Repository Agent messages 101
rolling back a deployment 238 Repository Server messages 98
static 239 setting for repository configuration 109
Designer exchanging
See also Designer Guide metadata 314
copying objects 310 execute lock
permissions 510 description (repository) 154
development license key ExecuteQuery
overview 119 description 470
Disablerepository Exit
description 421 description 411
documentation exiting
conventions xxxvii pmrep 411
description xxxvi exporting
domains metadata 314
building 13 registries 32
configuring for global shortcuts 192 repository configurations 115
connectivity 75 sources and targets 314
reusing data 15 exporting objects
dropping code pages 266
MX views 336 dependent objects 270
DTD file multiple objects 269
exporting and importing objects 267 overview 264, 276
plug-in template 484 parent objects 271
permissions 266
524 Index
powrmart.dtd 267 properties 168, 171
privileges 266 renaming 173
sessions 272 Repository Manager uses 166
shortcuts 270 shared 15, 169
steps for 285 shortcuts 249
versioned objects 273 Workflow Manager uses 166
external loader connections FTP connections
during folder or deployment group copy 245 during folder or deployment group copy 245
permissions and privileges 245 permissions and privileges 245
external security module
registering 484
unregistering 489 G
global objects
F See Workflow Administration Guide
global repositories
FindCheckout code page 117, 192
description 472 creating 14
flat files promoting 112, 117
MX view of repository file definitions 343 purpose 13
view of fields 345 shared folders 170
folder permissions global shortcuts
description 126 behavior when copying folders 250
editing 149 creating 190
overview 148, 168 definition 182, 249
security levels 148 environment 192
user groups 128 repository usernames 193
folder status server username 193
changing 207 tips 197
description 207 updating 194
folders updating views 194
comparing 174 groups
copying 245, 249 creating user 128
copying between local repositories 250 default security 127
copying global shortcuts 250 editing description 129
copying local shortcuts 249
copying or replacing 250
copying shortcuts 249
creating 171
H
deleting 173, 453 HTML view
deploying 469 Administration Console 53
Designer uses 166
editing 173
editing permissions 149 I
locking during folder copy 249
maintaining connections during copy 245 IBM DB2
modifying 456 connect string example 405
naming copies 249 setting tablespace name 107
organizing 166 Import Wizard
overview 166 importing objects 287
owner and owner’s group 169 resolving object conflicts 281
Index 525
importing creating 219, 466
metadata 314 definition 218
objects 280 deleting 467
ODBC data sources 33 editing 219
registries 32 launching
repository configurations 115 Administration Console 52
sources and target 314 LDAP authentication
importing objects description 131
code pages 266 LDAP authentication module
CRCVALUE codes 267 configuring 92
dependent objects 270 LDAP security module
DTD file 267 registering 88
impcntl.dtd 496 unregistering 95
Import Wizard 287 license files
multiple objects 269 compatibility between files 122
ObjectImport XML example 500 overview 120
overview 264 PowerCenter Server 122
parent objects 271 repository 120
permissions 266 license key types
powrmart.dtd 267 development 119
privileges 266 production 119
resolving conflicts 281 license keys
sessions 272 connectivity 119
shortcuts 274 option 119
steps for 287 overview 119
validating objects 281 product 119
validating XML file 280 repository types 119
XML file 267 licenses
Informatica See also license files 119
documentation xxxvi See also license keys 119
Webzine xxxviii overview 119
Informix rules and guidelines 123
connect string syntax 405 updating 111
interactive mode List view
pmrep 406 Administration Console 53
in-use lock Listallgroups
description (repository) 154 description 455
Listallprivileges
description 455
K Listallusers
description 455
KeepAliveTimeout ListObjectDependencies
setting for repository configuration 110 description 429
keywords Listobjects
searching for target definitions 34 description 423
listing folders 427
listing transformations 427
L transformation types 426
Listtablesbysess
labels description 428
applying 221, 462
applying when importing 280
526 Index
local repositories view of target tables 360
See also repositories mapplet segments
code page 75, 192 copying 310
promoting to global 112 mapplets
registering 75 See also Designer Guide
local shortcuts description 9
behavior when copying folders 249 metadata extensions in 326
creating 187 MaximumConnections
definition 182, 249 setting for repository configuration 109
tips 197 MaximumLocks
updating 194 setting for repository configuration 110
updating views 194 MessageReceiveTimeOut
locking setting for repository configuration 108
description 126 MessageSendTimeout
during deployment group copy 254 setting for repository configuration 108
during folder copy 249 metadata
locks adding to repository 9
releasing 83 analyzing 335
viewing 80, 157 definition 2
log entries exchanging 314
truncating 48 exporting 314
log files importing 314
codes 97 multi-dimensional 9
Repository Agent 100 protection levels within folders 168
Repository Server 98 reusing 14
LogFileName reusing across folders 182
setting for repository configuration 110 sharing 14
logs viewing 334
deleting 439 metadata exchange
Repository Agent 100 See MX (Metadata Exchange)
Repository Server 98 metadata extensions
copying 246
creating 328
M deleting 332
description 326
main window editing 331
Administration Console 53 non-reusable 327
sorting and organizing 25 overview 326
mapping segments reusable 327
copying 310 Microsoft Management Console
mappings See MMC
See also Designer Guide Microsoft SQL Server
conflicts 307 connect string syntax 405
copying mapping variables 307 MMC
copying segments 310 Administration Console 52
dependencies 27 Modifyfolder
description 9 description 456
metadata extensions in 326 MQ connections
view of source fields 359 See PowerCenter Connect for IBM MQSeries User and
view of source fields used by targets 358 Administrator Guide
view of sources 359
Index 527
MX (Metadata Exchange) REP_SERVER_INFO 396
Change Management views 398 REP_SERVER_NET 397
database definition views 338 REP_SERVER_NET_REF 397
deployment views 392, 396 REP_SESS_CONFIG_PARM 385
folder view 401 REP_SESS_LOG 387
integrating views with third-party software 337 REP_SESS_PARTITION_DEP 385
label views 398 REP_SESS_TBL_LOG 388
mapping views 353 REP_SESS_WIDGET_CNXS 383
mapplet views 353 REP_SESSION_CNXS 381
metadata extension views 364 REP_SESSION_FILES 382
overview 334 REP_SESSION_INSTANCE_FILES 383
PowerCenter Server views 396 REP_SESSION_INSTANCES 381
repository view 395 REP_SRC_FILE_FLDS 345
security views 390 REP_SRC_FILES 343
source views 339 REP_SRC_FLD_MAP 359
target views 347 REP_SRC_MAPPING 359
task views 371 REP_SRC_TBL_FLDS 346
transformation views 366 REP_SRC_TBLS 344
workflow views 371 REP_SUBJECT 401
worklet views 371 REP_TARG_FLD_MAP 357
MX views REP_TARG_MAPPING 356
categories 334 REP_TARG_TBL_COLS 351
creating 336 REP_TARG_TBL_JOINS 361
dropping 336 REP_TARG_TBLS 350
field-level summary 338 REP_TASK_ATTR 386
integrating with third-party software 337 REP_TASK_INST 377
REP_ALL_MAPPINGS 354 REP_TASK_INST_RUN 378
REP_ALL_MAPPLETS 355 REP_TBL_MAPPING 360
REP_ALL_SCHEDULERS 374 REP_USER_GROUPS 391
REP_ALL_SOURCE_FLDS 341 REP_USERS 390
REP_ALL_SOURCES 339 REP_VERSION_PROPS 398
REP_ALL_TARGET_FIELDS 349 REP_WFLOW_RUN 379
REP_ALL_TARGETS 347 REP_WFLOW_VAR 375
REP_ALL_TASKS 374 REP_WIDGET_ATTR 369
REP_ALL_TRANSFORMS 366 REP_WIDGET_DEP 368
REP_CM_LABEL 399 REP_WIDGET_FIELD 369
REP_CM_LABEL_REF 399 REP_WIDGET_INST 368
REP_COMPONENT 384 REP_WORKFLOW_DEP 377
REP_DATABASE_DEFS 338 REP_WORKFLOWS 372
REP_DEPLOY_GROUP 392 SQL scripts 336
REP_DEPLOY_GROUP_DETAIL 393
REP_EVENT 376
REP_FLD_MAPPING 358 N
REP_GROUPS 391
REP_LOAD_SESSIONS 380 naming
REP_MAPPING_PORT_CONN 363 copied folders 249
REP_MAPPING_UNCONN_PORTS 362 replaced folders 249
REP_METADATA_EXTN_DEFINES 365 native connect string
REP_METADATA_EXTNS 364 See connect string
REP_REPOSIT_INFO 395 Navigator
REP_SEG_FLDS 345 Administration Console 52
528 Index
Repository Manager 23 Owner’s Group security level
notifications description (folder) 148
receiving in Designer 6
receiving in Repository Manager 6
notify
sending 74 P
description 431 parent objects
exporting and importing 271
password
O editing user 136
permissions
object dependencies Administration Console tasks 50
viewing from the Copy Wizard 305 configuring for folders 148
object locks configuring for versioning objects 149
See also locks Designer tasks 510
overview 155 editing folder 149
object queries exporting objects 266
associating with a deployment group 240 folder types 168
configuring multiple conditions 225 importing objects 266
configuring query conditions 225 pmcmd 515
definition 218 pmrep tasks 519
running 232 pmrepagent tasks 520
searching for dependent objects 225 Repository Manager tasks 516
validating 231 security levels (folder) 169
object status troubleshooting 163
changing 206 Workflow Manager tasks 511
description 206 Workflow Monitor tasks 513
ObjectExport persistent input file
description 432 creating with pmrep 494
ObjectImport persistent resources
description 433 cleaning up with pmrep 411
objects plug-ins
checking in 464 See also repository plug-ins
copying 302 XML templates 484
exporting 276, 432 pmcmd
importing 280, 433 permissions 515
modifying in XML file 277 See also Workflow Administration Guide
validating for import 281 pmrep
validating multiple 42 adding a privilege 450
viewing dependencies 37 adding a user to a group 450
ODBC data sources adding to a deployment group 461
See also Installation and Configuration Guide applying a label 462
importing 33 backing up a repository 416
option license keys Change Management commands 460
overview 119 changing the connection name 438
Oracle changing the repository password 450
connect string syntax 405 checking in an object 464
Output window cleaning persistent resources 411
Repository Manager 28 clearing deployment group 465
Owner security level command arguments 407
description (folder) 148 command line modes 406
Index 529
command options 407 updating email addresses 442
command tips 492 updating notification email addresses 442
commands 410 updating repository statistics 447
connecting to a repository 410 updating sequence values 444
creating a deployment group 465 updating server details 443
creating a group 452 updating server variables 446
creating a label 466 updating table owner name 445
creating a persistent input file 494 updating target table name prefix 447
creating a user 452 using script files 507
deleting a deployment group 466 using scripts 491
deleting a folder 453 validating objects 474
deleting a label 467 pmrepagent
deleting a server 421 backing up repositories 477
deploying a deployment group 467 command tips 492
deploying a folder 469 commands 477
deployment control parameters 505 creating repositories 480
disabling a repository 421 deleting repositories 481
editing a user 454 permissions 520
enabling a repository 422 registering a plug-in 482
executing a query 470 restoring repositories 485
exiting 411 restoring Teradata repositories 479
exporting objects 432 unregistering plug-ins 487
importing objects 433 upgrading repositories 490
interactive mode 406 using script files 507
listing all groups 455 using scripts 491
listing all privileges 455 post-session email
listing all users 455 updating addresses with pmrep 442
listing checked-out objects 472 PowerCenter
listing object dependencies 429 building domains 13
listing objects 423 copy from local to global repositories 250
listings tables by session 428 security, overview 126
modifying folder properties 456 shared folders 170
object import control parameters 498 PowerCenter Client
overview 404 security 126
permissions 519 PowerCenter Metadata Reporter
registering a user 457 using 335
registering local repositories 434 PowerCenter Server
removing a group 457 See also Workflow Administration Guide
removing a privilege 458 during folder copy 245
removing a user 458 licenses 122
removing a user from a group 459 security 126
removing repositories 435 server variables 245
repository commands 412 starting 193
running script files 436 PowerCenter Server license files
security commands 449 overview 122
sending notification messages 431 powrmart.dtd
showing connection information 437 overview 267
stopping a repository 437 privileges
undoing check-out 473 See also permissions
unregistering local repositories 440 See also repository privileges
updating a database connection 441 Administration Console tasks 50
530 Index
Designer tasks 510 reports
exporting objects 266 metadata 335
importing objects 266 repositories
limiting 160 adding 29
removing 458 adding metadata 9
Repository Manager tasks 516 administration overview 11
repository, overview 142 architecture 3
troubleshooting 163 avoiding shared accounts 160
Workflow Manager tasks 511 backing up 66
product license keys backing up with pmrepagent 477
overview 119 changing a code page 117
promoting checking status 54
repositories 117 code pages 51, 75, 117, 192
purging connecting to 30
description 216 connecting to multiple 31
objects 216 connecting with pmrep 410
connectivity 4
copying 62
Q copying folders between local 250
creating 116
queries creating relational connections 417
See also object queries creating users 134
executing 470 database definition views 338
default privileges 143
deleting 64
R disabling 73, 421
enabling 71
recovering enabling version control 118
deleted objects 215 exporting/importing registries 32
register licenses 120
description 434 limiting access 161
registering locks 154
a user 457 log file codes 97
plug-in using pmrepagent 482 log files 97
security module using pmrepagent 484 managing 52
Registerplugin moving to a different Repository Server 77
description 482 object locking, overview 155
Registeruser overview 2, 50
description 457 promoting 117
registry propagating domain information 78
exporting 32 referencing objects with shortcuts 183
importing 32 registering 434
releasing registering local repositories 75
repository locks 83, 158 removing 29, 435
removerepsitory requirements 116
description 435 restoring 67
removing restricted characters for repository name 106
repositories 29 security 126, 160
users 141 security log file 153
replacing security, troubleshooting 163
folders 248, 250 starting 71
Index 531
stopping 71 setting ThreadWaitTimeout 110
stopping with pmrep 437 repository connections
types of 50 terminating 83, 152
unregistering 440 viewing 79, 151
version control 16 repository license files
view of associated target tables 350 overview 120
view of target table properties 351 repository license key
viewing details 26 overview 120
viewing locks 157 repository locks
viewing metadata 334 overview 154
repository releasing 158
deleting details from 439 types of 154
enabling 422 viewing 157
Repository Agent Repository Manager
architecture 3 components 22
checking status 54 dependency window 27
connectivity 4 folder maintenance overview 166
disabling 73 folders 23
enabling 71 main window 25
identifying process ID 97 Navigator 23
log file codes 97 Output window 28
logging 100 overview 20
starting 71 permissions 516
stopping 71 repository details 26
repository configuration sessions node details 26
CheckinCommentsRequired 110 windows 23
creating 104 repository notifications
dynamically updating 113 overview 6
editing 113 receiving in PowerCenter Server 7
exporting 115 receiving in Workflow Manager 7
importing 115 receiving in Workflow Monitor 7
removing 114 sending 74
setting CodePage 107 repository objects
setting ConnectString 107 description 10
setting DatabaseArrayOperationSize 110 metadata extensions in 326
setting DatabaseConnectionTimeout 110 repository plug-ins
setting DatabasePoolSize 110 registering 85
setting DatabaseType 107 removing 85
setting DateDisplayFormat 109 updating 86
setting DBPassword 107 repository privileges
setting DBUser 107 See also permissions
setting DynamicConfigRefreshInterval 110 assigning 146
setting Error Severity Level 109 description 126
setting KeepAliveTimeout 110 overview 142
setting LogFileName 110 revoking 146, 147
setting MaximumConnections 109 repository security level
setting MaximumLocks 110 description (folder) 148
setting MessageReceiveTimeOut 108 Repository Server
setting MessageSendTimeOut 108 Administration Console 50
setting SecurityAuditTrail 110 architecture 3
setting TablespaceName 107 client connections 3
532 Index
configuring system environment 5 search
connecting 58 See also Designer Guide
connectivity 4 keyword 34
identifying process ID 97 security
log file codes 97 creating an audit trail 153
logging 98 overview 126
managing individual repositories 52 pmrep commands 449
moving repositories 77 repository users 131
notifications 6 tips 160
Propagate command 78 troubleshooting 163
repository type security module
license keys 119 restoring repositories with 67
repository users SecurityAuditTrail
creating 134 logging activities 153
creating global shortcuts 193 setting for repository configuration 110
creating with default security 134 server variables
default privileges 143 during folder copy 245
default repository privileges 143 updating with pmrep 446
description 126 Servers
editing 138 adding 413
editing password 136 session directories
overview 131 See server variables 245
resolving object conflicts session logs
importing objects 281 truncating 48
Restore command Session Operator privilege
description 485 limiting 162
restoring sessions
repositories 67 copying 306
repositories using pmrepagent Bulkrestore 479 copying mapping variables 307
repositories using pmrepagent Restore 485 database connection conflicts 307
reusable transformations description 10
description 9 exporting 272
Rmgroup importing 272
description 457 metadata extensions in 326
Rmprivilege view of current logs 387
description 458 view of current scheduled 380
Rmuser view of individual session 388
description 458 sessions nodes details
Rmuserfromgroup viewing 26
description 459 shared accounts
Run avoiding 160
description 436 shared folders
See also folders
description 15
S shortcuts
See also Designer Guide
script files advantages 183
running 436 behavior when copying folders 249, 250
scripts copying 195
using 491 default names 184
dependencies 27
Index 533
description 9 stopRepository command
descriptions inherited 184 pmrep 437
exporting 270 Super User privilege
global 182, 190, 192 limiting 161
importing 274 SwitchConnection
local 182, 187 description 438
overview 182
properties 184
referenced objects 183, 185
refreshing properties 194
T
renaming source qualifiers 196 table owner name
tips 197 updating with pmrep 445
to folders 249 TablespaceName
troubleshooting 198 setting for repository configuration 107
updating 194 target definitions
updating views 194 description 9
using 194 keyword searches 34
using queries to locate 230 metadata extensions in 326
Showconnectioninfo view of associated transformations 357
description 437 view of joins between target tables 361
source databases view of table-level transformations 356
view of analyzed or imported sources 344 targets
view of fields 346 exporting to BI tools 314
source definitions importing from BI tools 314
description 9 tasks
metadata extensions in 326 metadata extensions in 326
source file connections node Teradata
viewing details 26 connect string example 405
sources restoring repositories using pmrepagent 479
exporting to BI tools 314 ThreadWaitTimeout
importing from BI tools 314 setting for repository configuration 110
source-target dependencies tips
description 27 pmrep commands 492
SQL scripts pmrepagent commands 492
for creating/dropping MX views 336 repository security 160
starting shortcuts 197
Administration Console 52 transformations
repositories 71 description 9
static deployment groups metadata extensions in 326
definition 236 troubleshooting
editing 239 exporting objects 296
statistics importing objects 296
updating repository 447 repository security 163
status shortcuts 198
user statuses with LDAP 131 Truncatelog
status bar description 439
progress indicator 22 typical mode
stopping copying folders 244
repositories 71
repositories with pmrep 437
534 Index
U users
adding to repositories 134
UndoCheckout adding under an external directory 137
description 473 authentication 131
unregister customizing privileges 161
description 440 default users 131
unregistering editing 138
plug-ins using pmrepagent 487 enabling 139
security module using pmrepagent 489 LDAP authentication 131
Unregisterplugin removing 141
description 487 valid statuses with LDAP 131
UpdateConnection
description 441
Updateemailaddr V
description 442
Updateseqgenvals validating
description 444 objects 42
Updateserver validating objects
description 443 with pmrep Validate 474
Updatesrcprefix variables
description 445 copying mapping variables 307
updating non-reusable sessions 446 updating with pmrep 446
Updatesrvvar version control
description 446 enabling for repositories 118
Updatestatistics version history
description 447 viewing 208
Updatetargetprefix versioned objects
description 447 checking in 211
updating non-reusable sessions 448 checking out 211
updating deleting 215
repository license files 111 exporting 273
shortcuts 194 object status 205
Upgrade overview 200
description 490 purging 216
upgrading recovering a deleted object 215
repositories using pmrepagent 490 sample scenario 201
user connections tracking changes 208
description 126 viewing applied labels 205
terminating 83, 152 viewing history 208
viewing 79, 151 viewing object properties 203
user groups viewing properties 203
creating 128 viewing version properties 204
default repository privileges 143 versioning object permissions
defaults 127 description 126
deleting 129 versioning objects
description 126 configuring permissions 149
editing 129 definition 218
folder permissions 128 deployment groups 236
limiting privileges 160 labels 219
overview 127 object queries 224
Index 535
versions validating for object import 280
purging 216 validating objects 281
tracking changes 208
viewing object version history 208
viewing properties 203
viewing
repository locks 80
user connections 79
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