Pc 811 Repository Guide
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Pc 811 Repository Guide as PDF for free.
More details
- Words: 111,319
- Pages: 416
Repository Guide
Informatica PowerCenter® (Version 8.1.1)
Informatica PowerCenter Repository Guide Version 8.1.1 September 2006 Copyright (c) 1998–2006 Informatica Corporation. All rights reserved. Printed in the USA. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are 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 and 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. Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerMart, SuperGlue, Metadata Manager, Informatica Data Quality and Informatica Data Explorer are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies, 1999-2002. All rights reserved. Copyright © Sun Microsystems. All Rights Reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All Rights Reserved. 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-2005 The Apache Software Foundation. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit and redistribution of this software is subject to terms available at http://www.openssl.org. Copyright 1998-2003 The OpenSSL Project. All Rights Reserved. The zlib library included with this software is Copyright (c) 1995-2003 Jean-loup Gailly and Mark Adler. The Curl license provided with this Software is Copyright 1996-2004, Daniel Stenberg,. All Rights Reserved. The PCRE library included with this software is Copyright (c) 1997-2001 University of Cambridge Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel. The source for this library may be found at ftp://ftp.csx.cam.ac.uk/pub/software/programming/ pcre. InstallAnywhere is Copyright 2005 Zero G Software, Inc. All Rights Reserved. Portions of the Software are Copyright (c) 1998-2005 The OpenLDAP Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License, available at http://www.openldap.org/software/release/license.html. This Software is protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775 and other U.S. Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.
Table of Contents List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . .xxiii Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . .xxiii Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . .xxiii Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii
Chapter 1: Understanding the Repository . . . . . . . . . . . . . . . . . . . . . . 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Repository Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Repository Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Understanding Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Objects Created in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Objects Created in the Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . 7 Objects Created in the Repository Manager . . . . . . . . . . . . . . . . . . . . . . 7 Global Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Modifying Dependent Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Administering Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 PowerCenter Repository Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Reusing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Reusing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
iii
Chapter 2: Using the Repository Manager . . . . . . . . . . . . . . . . . . . . . 17 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Repository Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Understanding the Repository Manager Windows . . . . . . . . . . . . . . . . . . . . 20 Displaying Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Navigator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Using Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Configuring Repository Manager Options . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Connecting to Domains and Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Configuring a Domain Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Adding a Repository to the Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Connecting to a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Reconnecting to a Repository and Canceling Auto-Reconnect . . . . . . . . 33 Managing Domain and Repository Connections . . . . . . . . . . . . . . . . . . . . . 35 Editing a Domain Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Removing a Domain Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Connecting to Multiple Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Exporting and Importing Repository Connection Information . . . . . . . . 37 Removing a Repository from the Navigator . . . . . . . . . . . . . . . . . . . . . . 37 Searching for Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Performing Keyword Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Searching All Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Validating Multiple Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Comparing Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Truncating Workflow and Session Log Entries . . . . . . . . . . . . . . . . . . . . . . . 53 Managing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Understanding Repository Object Locks . . . . . . . . . . . . . . . . . . . . . . . . 55 Viewing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Closing User Connections and Releasing Locks . . . . . . . . . . . . . . . . . . . 60
Chapter 3: Managing Users and Groups . . . . . . . . . . . . . . . . . . . . . . 63 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 iv
Table of Contents
User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Default Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Owner’s Group Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Creating a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Editing a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Deleting a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Using Default Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Using LDAP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Creating and Editing Repository Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Creating a User Under Default Authentication . . . . . . . . . . . . . . . . . . . 71 Editing a User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Creating a Repository User Under an External Directory Service . . . . . . 74 Editing a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Enabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Disabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Removing a Repository User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Default Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Extended Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Assigning and Revoking a Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring Permissions on Global Objects . . . . . . . . . . . . . . . . . . . . . 86 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 4: Working with Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Using Folders in the Repository Manager . . . . . . . . . . . . . . . . . . . . . . . 94 Using Folders in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Using Folders in the Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . 94 Organizing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Folder Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Folder Owner and Owner's Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Shared Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table of Contents
v
Configuring a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Editing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Deleting a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Comparing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Compared Attributes and Object Differentiation . . . . . . . . . . . . . . . . . 102 One-Way and Two-Way Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . 104 Editing and Saving Results Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Steps to Compare Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Chapter 5: Local and Global Shortcuts . . . . . . . . . . . . . . . . . . . . . . 109 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Shortcuts Versus Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Understanding Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Default Shortcut Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Describing the Object and the Shortcut . . . . . . . . . . . . . . . . . . . . . . . 112 Locating the Referenced Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Creating a Local Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Creating a Global Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Configuring the Global Shortcut Environment . . . . . . . . . . . . . . . . . . 121 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Refreshing Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Copying a Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Renaming Source Qualifiers to Shortcut Sources . . . . . . . . . . . . . . . . . 125 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Chapter 6: Working with Versioned Objects . . . . . . . . . . . . . . . . . . 129 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Sample Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Viewing Results View Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Customizing Results View Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Working with Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Viewing Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Labels Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
vi
Table of Contents
Object Status Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Changing Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Changing Folder Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Tracking Changes to Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Viewing Object History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Comparing Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Checking Out and Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Checking Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Viewing Checked-Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Undoing a Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Checking Out and Checking In Composite Objects . . . . . . . . . . . . . . 147 Working with Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Creating and Editing Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Applying Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Working with Deployment Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Creating a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Editing a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Viewing the Objects in a Deployment Group . . . . . . . . . . . . . . . . . . . 158 Adding or Removing Objects in Static Deployment Groups . . . . . . . . . 158 Using Queries in Dynamic Deployment Groups . . . . . . . . . . . . . . . . . 159 Viewing Deployment History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Rolling Back a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Deleting and Recovering Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . 163 Deleting a Versioned Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Recovering a Deleted Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Purging Versions of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Purging Individual Object Versions . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Purging Versions Based on Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Purging Composite Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Rules and Guidelines for Purging Versions of Objects . . . . . . . . . . . . . 171
Chapter 7: Working with Object Queries . . . . . . . . . . . . . . . . . . . . . 173 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Using the Query Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Configuring Query Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Query Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Table of Contents
vii
Validating and Saving a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Running a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Viewing Query Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Sample Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Finding Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Finding Impacted Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Finding Invalid Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Finding the Used Status of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Finding Recently Deployed Versioned Objects . . . . . . . . . . . . . . . . . . . 188 Finding Recently Checked-Out Objects . . . . . . . . . . . . . . . . . . . . . . . 188 Finding Older Versions of Versioned Objects . . . . . . . . . . . . . . . . . . . . 188 Finding Versioned Objects Older than a Specified Date . . . . . . . . . . . . 189 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Chapter 8: Copying Folders and Deployment Groups . . . . . . . . . . . 191 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Copying or Replacing Running Workflows, Sessions, and Tasks . . . . . . 192 Using the Copy Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Copy Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Associated Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Copying Plug-in Application Information . . . . . . . . . . . . . . . . . . . . . . 196 Copying or Replacing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Copying Within a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Copying Folders Between Versioned and Non-Versioned Repositories . . 201 Copying from Local Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Steps to Copy or Replace a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Copying a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Copying Composite Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Copying Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Object Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
viii
Table of Contents
Steps to Copy a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Chapter 9: Exporting and Importing Objects . . . . . . . . . . . . . . . . . . 215 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Working with Objects and Object Types . . . . . . . . . . . . . . . . . . . . . . . 217 Working with Different Repository Versions . . . . . . . . . . . . . . . . . . . . 217 Permissions and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 The XML and DTD Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 CRCVALUE Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Exporting and Importing Multiple Objects and Object Types . . . . . . . . . . 221 Working with Dependent Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Exporting and Importing Parent Objects . . . . . . . . . . . . . . . . . . . . . . 223 Working with Object Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Shortcut Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Importing Shortcuts to Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Modifying an Exported XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Modifiable Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Validating XML Files Against the DTD . . . . . . . . . . . . . . . . . . . . . . . 233 Validating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Resolving Object Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Steps to Export Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Steps to Import Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Chapter 10: Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Copy Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Resolving Copy Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Steps to Copy Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Copying Workflow Manager Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Table of Contents
ix
Copying Workflows and Worklets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Copying Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Copying Workflow Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Copying Designer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Copying Mapping and Mapplets Segments . . . . . . . . . . . . . . . . . . . . . 265
Chapter 11: Exchanging Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Working with Column Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Working with Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Working with Star Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Steps to Export Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Steps to Import Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Exchanging Metadata with Business Objects Designer . . . . . . . . . . . . . . . . 281 Metadata and Datatype Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Exporting Metadata to Business Objects Designer . . . . . . . . . . . . . . . . 282 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Chapter 12: Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Working with Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Creating Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Editing Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Deleting Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Chapter 13: Using Metadata Exchange (MX) Views . . . . . . . . . . . . . 295 Viewing the Repository Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 MX View Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Using PowerCenter Repository Reports . . . . . . . . . . . . . . . . . . . . . . . . 297 SQL Definition of Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Integrating MX Views with Third-Party Software . . . . . . . . . . . . . . . . 299 Database Definition View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 REP_DATABASE_DEFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Source Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 REP_ALL_SOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 REP_ALL_SOURCE_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 x
Table of Contents
REP_SRC_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 REP_SRC_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 REP_SRC_FILE_FLDS and REP_SEG_FLDS . . . . . . . . . . . . . . . . . . 307 REP_SRC_TBL_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Target Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 REP_ALL_TARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 REP_ALL_TARGET_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 REP_TARG_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 REP_TARG_TBL_COLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Mapping and Mapplet Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 REP_ALL_MAPPINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 REP_ALL_MAPPLETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 REP_TARG_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 REP_TARG_FLD_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 REP_FLD_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 REP_SRC_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 REP_SRC_FLD_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 REP_TBL_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 REP_TARG_TBL_JOINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 REP_MAPPING_CONN_PORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 REP_MAPPING_UNCONN_PORTS . . . . . . . . . . . . . . . . . . . . . . . . 325 Metadata Extension Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 REP_METADATA_EXTNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 REP_METADATA_EXTN_DEFINES . . . . . . . . . . . . . . . . . . . . . . . . 328 Transformation Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 REP_ALL_TRANSFORMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 REP_WIDGET_INST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 REP_WIDGET_DEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 REP_WIDGET_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 REP_WIDGET_FIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Workflow, Worklet, and Task Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 REP_WORKFLOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 REP_ALL_TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 REP_ALL_SCHEDULERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 REP_WFLOW_VAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 REP_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 REP_TASK_INST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 REP_WORKFLOW_DEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Table of Contents
xi
REP_TASK_INST_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 REP_WFLOW_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 REP_LOAD_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 REP_SESSION_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 REP_SESSION_INSTANCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 REP_SESSION_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 REP_SESSION_INST_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 REP_SESS_WIDGET_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 REP_COMPONENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 REP_SESS_PARTITION_DEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 REP_SESS_CONFIG_PARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 REP_TASK_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 REP_SESS_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 REP_SESS_TBL_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Security Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 REP_USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 REP_USER_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 REP_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Deployment Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 REP_DEPLOY_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 REP_DEPLOY_GROUP_DETAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Repository View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 REP_REPOSIT_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Integration Service Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 REP_SERVER_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 REP_SERVER_NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 REP_SERVER_NET_REF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Change Management Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 REP_VERSION_PROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 REP_LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 REP_LABEL_REF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Folder View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 REP_SUBJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Appendix A: Permissions and Privileges by Task . . . . . . . . . . . . . . 367 Designer Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Workflow Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
xii
Table of Contents
Workflow Monitor Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 pmcmd Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Repository Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 pmrep Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Table of Contents
xiii
xiv
Table of Contents
List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure
1-1. PowerCenter Repository Connectivity . . . . . . . . . . 1-2. Invalid and Impacted Objects . . . . . . . . . . . . . . . . 2-1. Repository Manager Components . . . . . . . . . . . . . 2-2. Repository Manager Navigator . . . . . . . . . . . . . . . 2-3. Source Definition Object Properties . . . . . . . . . . . 2-4. Dependency Window . . . . . . . . . . . . . . . . . . . . . . 2-5. Output Window . . . . . . . . . . . . . . . . . . . . . . . . . 2-6. Options Dialog Box of the Repository Manager . . . 2-7. Dependencies Dialog Box . . . . . . . . . . . . . . . . . . . 2-8. View Dependencies Window . . . . . . . . . . . . . . . . 2-9. Object Dependencies Saved as HTML . . . . . . . . . 2-10. Validate Objects Results . . . . . . . . . . . . . . . . . . . 3-1. Repository User Names and External Login Names 4-1. One-Way and Two-Way Comparisons . . . . . . . . . 5-1. Object and Shortcut Description . . . . . . . . . . . . . 5-2. Referenced Shortcut Object . . . . . . . . . . . . . . . . . 5-3. Flat File Source Shortcut Icon . . . . . . . . . . . . . . . 5-4. Create a Global Shortcut . . . . . . . . . . . . . . . . . . . 6-1. List of Results View Windows . . . . . . . . . . . . . . . 6-2. Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . 6-3. Version Properties . . . . . . . . . . . . . . . . . . . . . . . . 6-4. Labels Properties . . . . . . . . . . . . . . . . . . . . . . . . . 6-5. Object Status Properties . . . . . . . . . . . . . . . . . . . . 6-6. View History Window . . . . . . . . . . . . . . . . . . . . . 6-7. Label Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8. Label Editor Options . . . . . . . . . . . . . . . . . . . . . . 6-9. Apply Label Dialog Box . . . . . . . . . . . . . . . . . . . . 6-10. Apply Label Wizard . . . . . . . . . . . . . . . . . . . . . . 6-11. Deployment Groups Node in the Navigator . . . . . 6-12. Dependency for Deployment Group Dialog Box . 6-13. Advanced Purge Window . . . . . . . . . . . . . . . . . . 6-14. Preview Window - Summary . . . . . . . . . . . . . . . . 6-15. Preview Window - Detail . . . . . . . . . . . . . . . . . . 6-16. Version History of Mapping m_Payroll . . . . . . . . 6-17. Version History of Mapping m_PhoneList . . . . . . 7-1. Query Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2. Query Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3. Query with Multiple Conditions . . . . . . . . . . . . . . 7-4. Sample Query Results . . . . . . . . . . . . . . . . . . . . . 9-1. CRCVALUE Code in an Exported XML File . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. 4 .. 9 . 20 . 22 . 23 . 25 . 26 . 28 . 44 . 45 . 46 . 48 . 69 105 113 114 116 119 133 136 136 137 138 141 150 150 151 153 157 159 167 169 169 170 171 175 175 177 185 220
List of Figures
xv
Figure Figure Figure Figure Figure Figure Figure
xvi
9-2. Export Options Dialog Box . . . . . . . . . . . . . . . . 9-3. Import Wizard - Resolve General Object Conflicts 9-4. Import Wizard - Resolve Specific Object Conflicts 9-5. Conflict Resolution Wizard . . . . . . . . . . . . . . . . 10-1. The Copy Wizard . . . . . . . . . . . . . . . . . . . . . . 10-2. Copy Wizard Resolutions . . . . . . . . . . . . . . . . . 10-3. Copy Wizard Mapping Conflicts . . . . . . . . . . .
List of Figures
.. . . .. .. .. ..
.. .. .. .. .. .. ..
. . . . . . .
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
.223 .235 .236 .237 .253 .256 .258
List of Tables Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
1-1. Object Validation States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2. Repository Administration Tasks by Tool . . . . . . . . . . . . . . . . . . . . 2-1. Object Details Displayed in Main Window of Repository Manager . . 2-2. General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3. Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4. Dependencies Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5. Object Properties in View Dependencies Window . . . . . . . . . . . . . . 2-6. Validate Objects Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7. Repository Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8. Repository User Connection Details . . . . . . . . . . . . . . . . . . . . . . . . 2-9. Object Lock Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1. User Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2. Default Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3. Extended Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4. Folder Object Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5. Global Object Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1. Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2. Compared Object Types and Attributes . . . . . . . . . . . . . . . . . . . . . . 4-3. Compared Objects in Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1. Copying Global or Local Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . 6-1. Tasks Available in View History Window . . . . . . . . . . . . . . . . . . . . 6-2. Tasks Available in View Checkouts Window . . . . . . . . . . . . . . . . . . 6-3. Label Options and Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4. Methods of Purging Object Versions . . . . . . . . . . . . . . . . . . . . . . . . 6-5. Advanced Purge Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1. Query Parameters and Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2. Tasks Available in Query Results Window . . . . . . . . . . . . . . . . . . . . 8-1. Copy Folder Wizard Prompts (Copying a Folder) . . . . . . . . . . . . . . 8-2. Change in Object Status After Copying Deployment Group Objects . 8-3. Copy Deployment Group Wizard Prompts . . . . . . . . . . . . . . . . . . . 9-1. Exporting and Importing Objects Permissions and Privileges . . . . . . 9-2. Options for Exporting and Importing Multiple Objects . . . . . . . . . . 9-3. Dependent Objects Exported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4. Options for Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5. Modifiable Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6. Resolving General Conflicts During Import. . . . . . . . . . . . . . . . . . . 10-1. Copy Wizard Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2. Copy Wizard Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1. Dimensional Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . 11-2. Metadata Import Wizard - PowerCenter Options . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. 9 . 11 . 24 . 28 . 42 . 44 . 45 . 48 . 56 . 58 . 59 . 70 . 80 . 82 . 85 . 86 . 97 102 103 124 141 146 152 165 167 178 185 202 209 210 218 221 222 223 230 235 253 255 272 278
List of Tables
xvii
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
xviii
11-3. PowerCenter to Business Objects Designer Metadata Conversion 11-4. PowerCenter to Business Objects Datatype Conversion . . . . . . . 11-5. Business Objects Designer Metadata Export Options . . . . . . . . . 12-1. Options for Creating Reusable Metadata Extensions . . . . . . . . . 13-1. MX View Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2. SQL Script to Create MX Views . . . . . . . . . . . . . . . . . . . . . . . . 13-3. SQL Script to Drop MX Views . . . . . . . . . . . . . . . . . . . . . . . . . 13-4. REP_DATABASE_DEFS MX View . . . . . . . . . . . . . . . . . . . . . 13-5. Source Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6. REP_ALL_SOURCES MX View . . . . . . . . . . . . . . . . . . . . . . . . 13-7. REP_ALL_SOURCE_FLDS MX View . . . . . . . . . . . . . . . . . . . 13-8. REP_SRC_FILES MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9. REP_SRC_TBLS MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10. REP_SRC_FILE_FLDS and REP_SEG_FLDS MX Views . . . . 13-11. REP_SRC_TBL_FLDS MX Views . . . . . . . . . . . . . . . . . . . . . 13-12. Target Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13. REP_ALL_TARGETS MX View . . . . . . . . . . . . . . . . . . . . . . . 13-14. REP_ALL_TARGET_FLDS MX View . . . . . . . . . . . . . . . . . . 13-15. REP_TARG_TBLS MX View . . . . . . . . . . . . . . . . . . . . . . . . . 13-16. REP_TARG_TBL_COLS MX View . . . . . . . . . . . . . . . . . . . . 13-17. Mapping and Mapplet Views . . . . . . . . . . . . . . . . . . . . . . . . . 13-18. REP_ALL_MAPPINGS MX View . . . . . . . . . . . . . . . . . . . . . . 13-19. REP_ALL_MAPPLETS MX View . . . . . . . . . . . . . . . . . . . . . . 13-20. REP_TARG_MAPPING MX View . . . . . . . . . . . . . . . . . . . . . 13-21. REP_TARG_FLD_MAP MX View . . . . . . . . . . . . . . . . . . . . . 13-22. REP_FLD_MAPPING MX View . . . . . . . . . . . . . . . . . . . . . . 13-23. REP_SRC_MAPPING MX View . . . . . . . . . . . . . . . . . . . . . . 13-24. Mapping Source Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25. REP_TBL_MAPPING MX View . . . . . . . . . . . . . . . . . . . . . . 13-26. REP_TARG_TBL_JOINS MX View . . . . . . . . . . . . . . . . . . . . 13-27. REP_MAPPING_CONN_PORTS MX View . . . . . . . . . . . . . 13-28. REP_MAPPING_UNCONN_PORTS MX View . . . . . . . . . . . 13-29. Metadata Extension Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-30. REP_METADATA_EXTNS MX View . . . . . . . . . . . . . . . . . . 13-31. REP_METADATA_EXTN_DEFINES MX View . . . . . . . . . . . 13-32. Transformation Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33. REP_ALL_TRANSFORMS MX View . . . . . . . . . . . . . . . . . . . 13-34. REP_WIDGET_INST MX View . . . . . . . . . . . . . . . . . . . . . . 13-35. REP_WIDGET_DEP MX View . . . . . . . . . . . . . . . . . . . . . . . 13-36. REP_WIDGET_ATTR MX View . . . . . . . . . . . . . . . . . . . . . . 13-37. REP_WIDGET_FIELD MX View . . . . . . . . . . . . . . . . . . . . . 13-38. Workflow, Worklet, and Task Views . . . . . . . . . . . . . . . . . . . . 13-39. REP_WORKFLOWS MX View . . . . . . . . . . . . . . . . . . . . . . .
List of Tables
............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............
.282 .282 .283 .291 .296 .298 .298 .300 .301 .301 .303 .305 .306 .307 .308 .309 .309 .311 .313 .313 .315 .316 .317 .318 .319 .320 .321 .322 .323 .324 .325 .326 .327 .327 .328 .329 .329 .331 .331 .332 .332 .334 .335
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
13-40. REP_ALL_TASKS MX View . . . . . . . . . . . . . . . . . . . . . . . . . . 13-41. REP_ALL_SCHEDULERS MX View . . . . . . . . . . . . . . . . . . . . 13-42. REP_WFLOW_VAR MX View . . . . . . . . . . . . . . . . . . . . . . . . . 13-43. REP_EVENT MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44. REP_TASK_INST MX View . . . . . . . . . . . . . . . . . . . . . . . . . . 13-45. REP_WORKFLOW_DEP MX View . . . . . . . . . . . . . . . . . . . . . 13-46. REP_TASK_INST_RUN MX View . . . . . . . . . . . . . . . . . . . . . 13-47. REP_WFLOW_RUN MX View . . . . . . . . . . . . . . . . . . . . . . . . 13-48. REP_LOAD_SESSIONS MX View . . . . . . . . . . . . . . . . . . . . . . 13-49. REP_SESSION_CNXS MX View . . . . . . . . . . . . . . . . . . . . . . . 13-50. REP_SESSION_INSTANCES MX View . . . . . . . . . . . . . . . . . . 13-51. REP_SESSION_FILES MX View . . . . . . . . . . . . . . . . . . . . . . . 13-52. REP_SESSION_INST_FILES MX View . . . . . . . . . . . . . . . . . . 13-53. REP_SESS_WIDGET_CNXS MX View . . . . . . . . . . . . . . . . . . 13-54. REP_COMPONENT MX View . . . . . . . . . . . . . . . . . . . . . . . . 13-55. REP_SESS_PARTITION_DEF MX View . . . . . . . . . . . . . . . . . 13-56. REP_SESS_CONFIG_PARM MX View . . . . . . . . . . . . . . . . . . 13-57. REP_TASK_ATTR MX View . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58. REP_SESS_LOG MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-59. REP_SESS_TBL_LOG MX View . . . . . . . . . . . . . . . . . . . . . . . 13-60. Security Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-61. REP_USERS MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-62. REP_USER_GROUPS MX View . . . . . . . . . . . . . . . . . . . . . . . 13-63. REP_GROUPS MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-64. Deployment Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-65. REP_DEPLOY_GROUP MX View . . . . . . . . . . . . . . . . . . . . . . 13-66. REP_DEPLOY_GROUP_DETAIL MX View . . . . . . . . . . . . . . 13-67. REP_REPOSIT_INFO MX View . . . . . . . . . . . . . . . . . . . . . . . 13-68. Integration Service Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69. REP_SERVER_INFO MX View . . . . . . . . . . . . . . . . . . . . . . . . 13-70. REP_SERVER_NET MX View . . . . . . . . . . . . . . . . . . . . . . . . . 13-71. REP_SERVER_NET_REF MX View. . . . . . . . . . . . . . . . . . . . . 13-72. Change Management Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73. REP_VERSION_PROPS MX View . . . . . . . . . . . . . . . . . . . . . . 13-74. REP_LABEL MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75. REP_LABEL_REF MX View . . . . . . . . . . . . . . . . . . . . . . . . . . 13-76. REP_SUBJECT MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1. Required Privileges and Permissions for Designer Tasks . . . . . . . . . A-2. Required Privileges and Permissions for Workflow Manager Tasks . A-3. Required Privileges and Permissions for Workflow Monitor Tasks . A-4. Required Privileges and Permissions for pmcmd Tasks . . . . . . . . . . A-5. Required Permissions and Privileges for Repository Manager Tasks A-6. Required Permissions and Privileges for pmrep Tasks. . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
337 338 339 340 340 341 341 343 344 345 346 346 347 348 348 349 350 350 351 353 355 355 356 356 357 357 358 360 361 361 362 362 363 363 364 364 366 368 369 371 372 373 376
List of Tables
xix
xx
List of Tables
Preface
Welcome to PowerCenter, the Informatica software product that delivers an open, scalable data integration solution addressing the complete life cycle for all data integration projects including data warehouses, 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 repository coordinates and drives a variety of core functions, including extracting, transforming, loading, and managing data. The Integration Service 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 building a comprehensive data warehouse from disparate data sources.
xxi
About This Book The Repository Guide is written for database administrators and developers who manage 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 also available online.
Document Conventions This guide uses the following formatting conventions:
xxii
Preface
If you see…
It means…
italicized text
The word or set of words are especially emphasized.
boldfaced text
Emphasized subjects.
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.
Note:
The following paragraph provides additional facts.
Tip:
The following paragraph provides suggested uses.
Warning:
The following paragraph notes situations where you can overwrite or corrupt data, unless you follow the specified procedure.
monospaced text
This is a code example.
bold monospaced text
This is an operating system command you enter from a prompt to run a task.
Other Informatica Resources In addition to the product manuals, Informatica provides these other resources: ♦
Informatica Customer Portal
♦
Informatica web site
♦
Informatica Developer Network
♦
Informatica Knowledge Base
♦
Informatica Technical Support
Visiting Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.
Visiting the Informatica Web Site You can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.
Visiting the Informatica Developer Network You can access the Informatica Developer Network at http://devnet.informatica.com. The Informatica Developer Network is a web-based forum for third-party software developers. The site contains information about how to create, market, and support customer-oriented add-on solutions based on interoperability interfaces for Informatica products.
Visiting the Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips.
Obtaining Technical Support There are many ways to access Informatica Technical Support. You can contact a Technical Support Center by using the telephone numbers listed the following table, you can send email, or you can use the WebSupport Service. Preface
xxiii
Use the following email addresses to contact Informatica Technical Support: ♦
[email protected] for technical inquiries
♦
[email protected] for general customer service requests
WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.
xxiv
Preface
North America / South America
Europe / Middle East / Africa
Asia / Australia
Informatica Corporation Headquarters 100 Cardinal Way Redwood City, California 94063 United States
Informatica Software Ltd. 6 Waltham Park Waltham Road, White Waltham Maidenhead, Berkshire SL6 3TN United Kingdom
Informatica Business Solutions Pvt. Ltd. Diamond District Tower B, 3rd Floor 150 Airport Road Bangalore 560 008 India
Toll Free 877 463 2435
Toll Free 00 800 4632 4357
Toll Free Australia: 00 11 800 4632 4357 Singapore: 001 800 4632 4357
Standard Rate United States: 650 385 5800
Standard Rate Belgium: +32 15 281 702 France: +33 1 41 38 92 26 Germany: +49 1805 702 702 Netherlands: +31 306 022 797 United Kingdom: +44 1628 511 445
Standard Rate India: +91 80 4112 5738
Chapter 1
Understanding the Repository This chapter includes the following topics: ♦
Overview, 2
♦
Repository Architecture, 3
♦
Repository Connectivity, 4
♦
Understanding Metadata, 6
♦
Administering Repositories, 11
♦
PowerCenter Repository Domains, 13
♦
Version Control, 15
1
Overview The PowerCenter repository is a relational database managed by the Repository Service. The repository consists of database tables that store metadata. Metadata describes different types of objects, such as mappings and transformations, that you can create or modify using the PowerCenter Client tools. The Integration Service 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 Service. The Repository Service protects metadata in the repository by managing repository connections and using object-locking to ensure object consistency. The Repository Service also notifies you when another user modifies or deletes repository objects you are using. Each Repository Service manages a single repository database. You can configure a Repository Service to run on multiple machines, or nodes, in the domain. Each instance running on a node is called a Repository Service process. This process accesses the database tables and performs most repository-related tasks. The Repository Service uses native drivers to communicate with the repository database. PowerCenter Client tools and the Integration Service communicate with the Repository Service over TCP/IP. When a client application connects to the repository, it connects directly to the Repository Service process. You administer the repository using the Repository Manager client tool, the PowerCenter Administration Console, and the pmrep and infacmd command line programs. You can connect to and manage multiple repositories. A repository domain is a group of repositories that you can connect to simultaneously in the PowerCenter Client. They share metadata through a special type of repository called a global repository. When you configure shared folders in a repository, you can share the objects in the folder with other repositories in the repository domain. You share objects to reuse metadata. Note: A repository domain is different from a PowerCenter domain, which is the primary unit
of administration for the PowerCenter environment. For more information about repository domains, see “PowerCenter Repository Domains” on page 13. For more information about PowerCenter domains, see “Understanding Domains” in the Administrator Guide. If you have the team-based development option, you can enable the repository for version control. You can store multiple versions of objects in a versioned repository. You can also perform change-management tasks such as version comparison, change tracking, labeling, and deployment.
2
Chapter 1: Understanding the Repository
Repository Architecture The PowerCenter repository resides in a relational database. The repository database tables contain the instructions required to extract, transform, and load data. Repository client applications access the repository database tables through the Repository Service. The Repository Service manages repository metadata transaction requests from client applications. Each Repository Service manages a single repository. The Repository Service uses object-locking to ensure the consistency of metadata in the repository. A Repository Service process is a multi-threaded process that fetches, inserts, and updates metadata in the repository database tables. A Repository Service process is an instance of the Repository Service that runs on a particular machine, or node. The Repository Service accepts client metadata transaction requests from the following PowerCenter applications: ♦
PowerCenter Client tools. Use the Designer to create and store mapping metadata in the repository. Use the Workflow Manager to store workflow metadata and connection object information in the repository. Use the Workflow Monitor to retrieve workflow run status information and session logs written by the Integration Service. Use the Repository Manager to organize and secure metadata by creating folders, users, and groups. You can manage Repository Services and repository database connections and content from the PowerCenter Administration Console.
♦
pmrep and infacmd. Use pmrep to perform repository metadata administration tasks, such as listing repository objects or creating and editing users and groups. Use infacmd to perform service-related functions, such as creating or removing a Repository Service.
♦
Integration Service. When you start the Integration Service, it connects to the repository to schedule workflows. When you run a workflow, the Integration Service retrieves workflow task and mapping metadata from the repository. During the workflow run, the Integration Service writes workflow status information to the repository.
♦
Other Repository Services. Use multiple Repository Services to manage repositories in a repository domain. The Repository Service managing a local repository communicates as a client application with the Repository Service managing the global repository.
Repository Architecture
3
Repository Connectivity PowerCenter applications such as the PowerCenter Client, the Integration Service, pmrep, and infacmd connect to the repository through the Repository Service. PowerCenter applications communicate with the Repository Service through a specified port over a TCP/IP connection. You configure the TCP/IP port number when you install the Repository Service. Because PowerCenter services can reside on multiple nodes in the domain, the Repository Service relies on another service called the Service Manager to direct client requests to the appropriate Repository Service process. Figure 1-1 shows the path of a request when you use a repository client application, such as the Repository Manager or the Integration Service, to update the repository database. Figure 1-1. PowerCenter Repository Connectivity Repository Client Application
1 Node A
Node B (Gateway)
Service Manager
Service Manager
2
3
Application Services Repository Service
Application Services
4
Repository Database
The following process describes how a repository client application connects to the repository database:
4
1.
The repository client application sends a repository connection request to the master gateway node, which is the entry point to the domain. This is node B in the diagram.
2.
The Service Manager sends back the host name and port number of the node running the Repository Service. In the diagram, the Repository Service is running on node A. If you
Chapter 1: Understanding the Repository
have the high availability option, you can configure the Repository Service to run on a backup node. 3.
The repository client application establishes a link with the Repository Service process on node A. This communication occurs over TCP/IP.
4.
The Repository Service process communicates with the repository database and performs repository metadata transactions for the client application. This communication typically occurs over TCP/IP. It may use other protocols, depending on the database driver.
Repository Connectivity
5
Understanding Metadata The repository stores metadata that describes how to extract, transform, and load source and target data. PowerCenter metadata describes several different kinds of repository objects. You use different PowerCenter Client tools to develop each kind of object. If you enable version control, you can store multiple versions of metadata objects in the repository. For more information about version control and change management, see “Version Control” on page 15. You can also extend the metadata stored in the repository by associating information with repository objects. For example, when someone in your organization creates a source definition, you may want to store the name of that person with the source definition. You associate information with repository metadata using metadata extensions. For more information about using metadata extensions, see “Metadata Extensions” on page 287.
Objects Created in the Designer Use the Designer to create and edit the following repository objects:
6
♦
Source definitions. Detailed descriptions of database objects (tables, views, and synonyms), flat files, XML files, or COBOL files that provide source data. For example, a source definition might be the complete structure of the EMPLOYEES table, including the table name, column names and datatypes, and any constraints applied to these columns, such as NOT NULL or PRIMARY KEY. Use the Source Analyzer tool in the Designer to import and create source definitions.
♦
Target definitions. Detailed descriptions for database objects, flat files, or XML files to receive transformed data. During a session, the Integration Service writes the transformed data to targets. Use the Target Designer tool in the Designer to import or create target definitions.
♦
Transformations. A transformation generates, modifies, or passes data through ports that you connect in a mapping or mapplet. When you build a mapping or mapplet, you add transformations and configure them to handle data according to your business purpose.
♦
Reusable transformations. You can design a transformation that you can reuse in multiple mappings or mapplets within a folder, a repository, or a repository domain. Rather than recreate the same transformation each time, you can make the transformation reusable and add instances of the transformation to individual mappings or mapplets. Use the Transformation Developer tool in the Designer to create reusable transformations.
♦
Mappings. A mapping specifies how to move and transform data from sources to targets. Mappings include source and target definitions and transformations. Transformations describe how the Integration Service transforms data. Mappings can also include shortcuts, reusable transformations, and mapplets. Use the Mapping Designer tool in the Designer to create mappings.
♦
Mapplets. You can design a mapplet to contain sets of transformation logic to be reused in multiple mappings within a folder, a repository, or a repository domain. Rather than recreate the same set of transformations each time, you can create a mapplet containing the
Chapter 1: Understanding the Repository
transformations and then add instances of the mapplet to individual mappings. Use the Mapplet Designer tool in the Designer to create mapplets. ♦
Multi-dimensional metadata. Multi-dimensional metadata refers to the logical organization of data used for analysis in OLAP applications. Dimensions and cubes are most often used by end users of OLAP applications. Use the Target Designer tool to create dimensions and cubes.
You can also create shortcuts to metadata in shared folders. Use shortcuts to repository objects in shared folders. You can create local shortcuts to shared folders within the same repository and global shortcuts to shared folders in the global repository of the repository domain. Use the Designer to create shortcuts. For more information about using the Designer to work with repository objects, see the Designer Guide and the Transformation Guide.
Objects Created in the Workflow Manager Use the Workflow Manager to create and edit the following repository objects: ♦
Database connections. The Integration Service uses database connections to connect to the source and target databases.
♦
Sessions. Sessions are workflow tasks that contain information about how the Integration Service 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 Integration Service uses to extract, transform, and load data.
♦
Workflow tasks. Workflow tasks are instructions the Integration Service 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 more information about working with repository objects using the Workflow Manager, see the Workflow Administration Guide.
Objects Created in the Repository Manager 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. Understanding Metadata
7
♦
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.
Global Objects Most objects exist within folders in the repository. You can create global objects at the repository level. While the scope of most objects is within their folders, the scope of a global object is the entire repository. When you edit a global object, the Repository Service applies the changes at the repository level. You use different PowerCenter Client tools to develop each kind of global object. You can create the following global objects: ♦
Labels. You can associate labels with any versioned object or group of versioned objects in a repository. 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. Use the Repository Manager to create and edit labels.
♦
Deployment groups. A deployment group is a set of versioned objects that you deploy to a repository. You can create a deployment group that contains references to versioned 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. Use the Repository Manager to create and edit deployment groups.
♦
Object queries. Use an object query to search for versioned and non-versioned objects in the repository that meet specified conditions. You can save object queries for later use. You can create a private object query, or you can share it with all users in the repository. Use the Designer, Workflow Manager, or Repository Manager to create and run an object query.
♦
Connection objects. You create connection objects in the repository when you define database, FTP, and external loader connections in the Workflow Manager. You can configure and manage permissions within each connection object. Use the Workflow Manager to create and edit connection objects.
Labels, deployment groups, and object queries help you perform version control by grouping versioned objects. For more information about version control, see “Version Control” on page 15.
Modifying Dependent Objects When you modify a child object, it may cause a parent object to become invalid. For example, if you modify a mapping by changing a port datatype to an incompatible datatype, the session may become invalid. A repository object can have a valid, invalid, or impacted state. The Repository Service assigns valid and invalid states when you save an object or when you validate an object. The Repository Service assigns an impacted state when it fetches a parent object of a child object modified in a way that may cause invalidation. The impacted state is an indeterminate state that is resolved when you validate or save an object. When you modify repository objects, the Repository Service assigns one of three states to the modified object and dependent parent object.
8
Chapter 1: Understanding the Repository
Table 1-1 describes the object validation states. Table 1-1. Object Validation States Object State
Assigned
Running the Workflow
Valid
When you save or validate an object.
The object is valid, and workflows run. You do not need to modify the state.
Invalid
When you save or validate an object.
The object is invalid, and workflows will not run. Use the message displayed by the PowerCenter Client to determine the cause of the invalidation. Modify and validate the object again.
Impacted
If you modify a child object in such a way that it may cause the parent object to become invalid, the Repository Service marks parent objects as impacted. The Repository Service marks the object as impacted when it fetches the parent object.
The object is impacted, and you can perform validation or configure the Integration Service to run the impacted session.
The Repository Service marks dependent objects and shortcuts to parent objects in other folders with warnings to denote the impacted status. A question mark icon denotes impacted status in the Navigator. The Repository Service marks the most immediate parent object as impacted, but it does not mark all related objects as impacted. For example, if you modify a mapping, the Repository Service marks the session as impacted, but it does not mark the workflow as impacted. Figure 1-2 shows invalid and impacted objects: Figure 1-2. Invalid and Impacted Objects
Invalid Object
Impacted Object
You can validate impacted sessions, or you can choose to ignore the warning and run the session. To ignore the warning, you must configure the Integration Service to run impacted sessions. At run time, the Integration Service validates the session and determines if the session is valid or invalid. The Integration Service will not run an impacted session if it detects that the session is invalid. Understanding Metadata
9
Example For example, you have a mapping in Folder A that contains a shortcut to an Expression transformation in Folder B. In Folder B, you update the Expression transformation in a way that causes invalidation. The Repository Service marks the parent mappings in Folder B that use the Expression transformation. The Repository Service also marks the mappings in Folder A that use the shortcut to the Expression transformation with a warning. When you run a session that uses the impacted mappings, the Integration Service validates the mappings. If the mappings are valid, the Integration Service runs the session. If the mappings are invalid, the Integration Service marks the session as invalid and it does not run the session.
Rules and Guidelines for Object Compatibility The Repository Service treats modified dependent objects as compatible when you perform the following tasks: ♦
Change datatypes in a source, target, or transformation to a compatible datatype. The Repository Service marks objects as impacted only when you change the datatypes to incompatible datatypes.
♦
Rename ports in a reusable transformation.
♦
Add a port in a source, target, or transformation.
♦
Replace objects such as sources, targets, mapplets, and mappings with compatible objects.
When you replace a repository object with another object, the following conditions must be true for the Repository Service to treat the objects as compatible:
10
Repository Object
Compatibility Requirements
Source, Target, Transformation
- Name of the replacement object must match the original object. - All port names in the original object must be represented in the replacement object. - Datatypes must be compatible.
Mapping
Name and number of the following objects must match the original object: - Targets - Mapplets - Sources - Source Qualifiers - Joiner transformations - Update Strategy transformations - Custom transformations
Mapplet
Name and number of the following objects must match the original object: - Sources - Source Qualifiers - Joiner transformations - Update Strategy transformations - Custom transformations
Chapter 1: Understanding the Repository
Administering Repositories You use the PowerCenter Administration Console, the Repository Manager, and the pmrep and infacmd command line programs to administer repositories. Table 1-2 lists some of the common repository administration tasks and the corresponding tools you can use to perform them: Table 1-2. Repository Administration Tasks by Tool Repository Manager
Admin Console
pmrep
Back up repository to a binary file
X
X
Restore repository from a binary file
X
X
Copy repository database tables
X
X
Delete repository database tables
X
X
Create a Repository Service
X
X
Remove a Repository Service
X
X
Create folders to organize metadata
X
X
Add repository users and groups
X
X
Configure repository security
X
X
infacmd
X
The Repository Service creates and updates the repository tables. These tables store metadata in a particular format that the Integration Service and the PowerCenter Client tools use. Warning: The PowerCenter repository tables have an open architecture. Although you can view the repository tables, never manually edit them through other utilities. Informatica is not responsible for corrupted data that is caused by customer alteration of the repository tables or data within those tables.
You use the PowerCenter Administration Console to copy, back up, and restore repository content. You can back up the repository to a binary file. You can restore the entire repository from a binary file. You can also copy all the repository tables from another database.
Creating the Repository Before you create a repository, you need a database for the repository tables. You use the database management system client to create the database. The repository database name must be unique. After you create a database for the repository, you can use the Administration Console to create a Repository Service to manage the repository. When you create the Repository Service, you can create the database tables for the repository. Alternatively, you can create the Repository Service without creating any database tables. You can create the repository tables
Administering Repositories
11
later or use existing database tables for the repository. The repository name is the same as the name of the Repository Service. For more information about creating and managing repositories, see “Creating and Configuring the Repository Service” and “Managing the Repository” in the Administrator Guide.
Creating Folders After you create the repository, you can add folders to it in the Repository Manager. Use folders to organize repository objects. You can separate different types of metadata and projects into easily identifiable areas. You can configure a folder to be shared so that its content is available to all other folders in the same repository. If you plan to use the same object in several projects, store it in a shared folder. For example, you use a shared folder to store a definition of the CUSTOMERS table, which provides data for a variety of projects. You make shortcuts to the table in other folders in the same repository. If you are working in a repository domain, you can also make shortcuts to the CUSTOMER table in folders in local repositories that are registered with the repository domain. For more information about repository domains, see “PowerCenter Repository Domains” on page 13. For more information about folders, see “Working with Folders” on page 93.
Security To secure data in the repository, the repository provides a system of users, user groups, repository privileges, folder permissions, and object locking. After you create a repository, use the Repository Manager to set up repository users and groups and to specify the repository privileges that they have. When you create a folder, 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. Privileges control users’ ability to perform tasks such as creating mappings, running sessions, or deploying folders. Permissions control access to folders and objects in the repository. For more information about configuring repository security, see “Managing Users and Groups” on page 63.
12
Chapter 1: Understanding the Repository
PowerCenter Repository Domains You can organize, simplify, and manage the process of developing and maintaining multiple data warehouses and other integration projects by using a repository domain. You connect repositories within the repository domain. A repository domain consists of a single global repository and any number of local repositories. The global repository is the hub of the system. It serves the following purposes: ♦
Opening connections between repositories. To preserve system security and to simplify the task of connecting from one repository to another, the global repository stores information needed to connect to each repository. If you are connected to a local repository, you can navigate to the global repository without connecting to it separately. If you are connected to a global repository, you can navigate to any local repository in the repository domain.
♦
Storing and reusing shared metadata. You can save any metadata that you plan to share across repositories in the global repository. Local repositories can then use shortcuts to objects in the global repository shared folders, or you can create copies of objects in unshared folders. You can also copy objects in shared folders.
You can share data and metadata between global and local repositories by copying individual repository objects and entire folders within and between repositories. You can also use the Designer to create shortcuts to reference objects in other repositories. For more information about creating a repository domain, see “Managing the Repository” in the Administrator Guide.
Reusing Metadata In a repository 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 complex. It is based on variables such as production costs and marketing expenses. Because profitability is important information when investing in product development and building a sales strategy, you need everyone in the organization to use the same calculation. If you share the profitability calculation, you ensure that everyone views the value of each product 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 production, marketing, and accounting divisions might also need to use the same calculation in mappings in their repositories.
PowerCenter Repository Domains
13
Shared Folders You can configure folders in global and local repositories to be shared. After you designate a folder as shared, you can create shortcuts to objects in that folder. Use shortcuts in any other folder in the repository. If the shared folder is in a global repository, use shortcuts to that folder in any repository in the repository domain. If a folder is not shared, you cannot create shortcuts to objects in the folder. However, you can still create copies of objects in non-shared folders. Shared folders are useful when you want to use the same repository objects in several projects within the same repository. For example, each folder within a repository might represent a different development project. However, every project in the repository needs to store bug reports in a consistent format, so you might put the source definition for the BUG_REPORTS table in a shared folder. For more information about folders, see “Working with Folders” on page 93.
Reusing Data The need to share data is just as important 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 is 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 the inserts, deletes, and updates that have occurred in the PRODUCTS table since the last time you updated the central data store. You can format data in a standard fashion with the central data store. For example, you can filter employee data that should remain confidential. You can also 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.
14
Chapter 1: Understanding the Repository
Version Control If you have the team-based development option, you can enable version control for the repository. A versioned repository stores multiple 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 perform the following change management tasks 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. You can see the changes made to an object over time.
♦
Delete or purge a version. You can delete an object so that it no long appears in the PowerCenter Client. However, you continue to store deleted objects in the repository. If you decide later that you need a deleted object, you can recover it from the repository. When you purge an object version, you permanently remove it from the repository.
♦
Use global objects such as queries, deployment groups, and labels to group versioned objects. Object queries, deployment groups, and labels are global objects that exist at the repository level. When you group versioned objects, you can associate multiple objects into logical categories. For example, you can create a deployment group that contains references to objects from multiple folders across the repository.
For more information about global objects, see “Global Objects” on page 8. For more information about version control, see “Working with Versioned Objects” on page 129.
Version Control
15
16
Chapter 1: Understanding the Repository
Chapter 2
Using the Repository Manager This chapter includes the following topics: ♦
Overview, 18
♦
Understanding the Repository Manager Windows, 20
♦
Configuring Repository Manager Options, 28
♦
Connecting to Domains and Repositories, 30
♦
Managing Domain and Repository Connections, 35
♦
Searching for Repository Objects, 39
♦
Viewing Object Dependencies, 42
♦
Validating Multiple Objects, 47
♦
Comparing Repository Objects, 50
♦
Truncating Workflow and Session Log Entries, 53
♦
Managing User Connections and Locks, 55
17
Overview You can navigate through multiple folders and repositories and perform basic repository tasks with the Repository Manager.
Repository Manager Windows The Repository Manager can display four main windows: the Navigator window, the Main window, the Dependency window, and the Output window. You can dock and undock the Navigator, Dependency, and Output windows. You can also hide and display the Navigator, Dependency, and Output windows. In the Navigator window, you can connect to a repository, navigate through the folders, and browse repository objects. The Navigator window organizes the repository objects of the same type in each folder in groups called nodes. When you select an object in a node, you can view details for the object in the Main window. If you configure the Repository Manager to display object dependencies, the Dependency window displays the dependency details when you select an object in the Navigator window. You can view dependency information for sources, targets, mappings, and shortcuts. The Output window displays detailed information for complex repository operations, such as copying folders. The Output window also displays Repository Service notification messages. Note: Because the status of the repository changes as users access it, refresh the view of the
repository before performing tasks, such as deleting a folder or unlocking an object.
Repository Manager Tasks Use the Repository Manager to complete the following tasks:
18
♦
Add domain connection information. You can configure domain connection information. For more information, see “Configuring a Domain Connection” on page 30.
♦
Add and connect to a repository. You can add repositories to the Navigator window and client registry and then connect to the repositories. For more information, see “Connecting to a Repository” on page 32.
♦
Work with PowerCenter domain and repository connections. You can edit or remove domain connection information. You can connect to one repository or multiple repositories. You can export repository connection information from the client registry to a file. You can import the file on a different machine and add the repository connection information to the client registry. For more information, see “Managing Domain and Repository Connections” on page 35.
♦
Search for repository objects or keywords. You can search for repository objects containing specified text. If you add keywords to target definitions, use a keyword to search for a target definition. For more information, see “Searching for Repository Objects” on page 39.
Chapter 2: Using the Repository Manager
♦
View object dependencies. Before you remove or change an object, you can view dependencies to see the impact on other objects. For more information, see “Viewing Object Dependencies” on page 42.
♦
Compare repository objects. In the Repository Manager, you can compare two repository objects of the same type to identify differences between the objects. For more information, see “Comparing Repository Objects” on page 50.
♦
Truncate session and workflow log entries. You can truncate the list of session and workflow logs that the Integration Service writes to the repository. You can truncate all logs, or truncate all logs older than a specified date. For more information, see “Truncating Workflow and Session Log Entries” on page 53.
♦
View user connections. Use the Repository Manager to view and manage user connections. For more information, see “Managing User Connections and Locks” on page 55.
♦
Release locks. Use the Repository Manager to release residual locks left by residual connections. Releasing a valid lock can result in repository inconsistencies, so release a lock only if the locked object is not in use. For more information, see “Closing User Connections and Releasing Locks” on page 60.
♦
Exchange metadata with other business intelligence tools. You can export metadata to and import metadata from other business intelligence tools, such as Cognos ReportNet Framework Manager. For more information, see “Exchanging Metadata” on page 267.
Overview
19
Understanding the Repository Manager Windows The Repository Manager has a main window and a status bar for information about the operation you are performing. The Repository Manager can display the following windows: ♦
Navigator
♦
Main
♦
Dependency
♦
Output
Figure 2-1 shows the Repository Manager components: Figure 2-1. 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.
20
Chapter 2: Using the Repository Manager
Displaying Windows You can dock and undock the following windows in the Repository Manager: ♦
Navigator
♦
Dependency
♦
Output
To dock or undock a window: ♦
Double-click the title bar. -or-
♦
Drag the title bar toward the Main window.
The windows that the Repository Manager displays depend on the tasks you perform. When you launch the Repository Manager, the Navigator and the Main windows appear. The Dependency window appears when you want to view dependencies, and the Output window appears when the Repository Manager displays status messages. You can configure the Repository Manager to display or hide any window. To display a window: 1.
Double-click the title bar.
2.
From the menu, choose View. Then select the window you want to open.
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 types of objects: ♦
Repositories. PowerCenter repositories can be standalone, local, or global.
♦
Deployment groups. Deployment groups contain collections of objects for deployment to another repository in the repository domain.
♦
Folders. Folders can be shared or not shared.
♦
Nodes. Nodes contain 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.
Understanding the Repository Manager Windows
21
Figure 2-2 shows the Navigator components: Figure 2-2. Repository Manager Navigator
Repositories
Deployment Groups
Shared Folder
Node for Sources Mappings
Workflows Node for Session Configurations
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 135. Note: If you enable versioning when you create the repository, you can view all tabs on the
Properties dialog box.
22
Chapter 2: Using the Repository Manager
Figure 2-3 shows the object properties for a source definition: Figure 2-3. Source Definition Object Properties
Main Window The Main window of the Repository Manager displays information 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.
Sorting and Organizing You can sort items in the Main window by each of the columns. For example, to sort mappings by validity, select the mappings node, and then click the Valid column heading. Click the heading again to reverse the order in which the mappings are sorted. You can also change the order in which the columns appear. For example, you might want the Valid column to appear first, on the left side of the Main window. To do this, drag the Valid column heading to the location. The Repository Manager displays the columns in the new order until you change the display. Note: You can double-click an object in the Main window to view its properties.
Viewing Object Details To view information about repository objects, select a node in the Navigator. Or, to view detailed information about a particular repository object, drill down on a node and select the object.
Understanding the Repository Manager Windows
23
Table 2-1 describes the object details displayed in the Main window: Table 2-1. Object Details Displayed in Main Window of Repository Manager
24
Node
Information Displayed
Repository Node
Displays properties for each folder in the selected repository.
Deployment Groups Node
Displays properties for each deployment group in the selected repository. Select a static 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 within the selected node. Select a target definition to view details for each target definition port.
Transformations Node
Displays the properties for each reusable transformation in the selected node. Select a 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 Transformations 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 Node
Displays workflow log information for the selected workflow. The Workflow Logs node appears under each workflow in the Workflows node.
Session Logs Node
Displays session log information for the selected session. The Session Logs node appears under each session in the Sessions node.
Source Connections Node
Displays connection properties for each source connection associated with the session. The Source Connections node appears under each session in the Sessions node and under each session associated with a workflow under the Workflows node.
Source File Connections Node
Displays properties for each source file associated with the session. The Source File Connections node appears under each session in the Sessions node and under each session associated with a workflow under the Workflows node.
Target Connections Node
Displays connection properties for each target connection associated with the session. The Target Connections node appears under each session in the Sessions node and under each session associated with a workflow under the Workflows node.
Chapter 2: Using the Repository Manager
Table 2-1. Object Details Displayed in Main Window of Repository Manager Node
Information Displayed
Target File Connections Node
Displays properties for each target file associated with the session. The Target File Connections node appears under each session in the Sessions node and under each session associated with a workflow under the Workflows node.
Transformation Logs Node
Displays log details for each transformation in the session when you select the Transformation 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 more information about using the Dependency dialog box, see “Viewing Object Dependencies” on page 42. When you view dependencies, the left pane of the Dependency window lists the object that has dependency information, and the dependency information appears in the right pane. Figure 2-4 shows the Dependency window: Figure 2-4. Dependency Window
Selected Object
Dependencies
The Dependency window can display the following types of dependencies: ♦
Source-target dependencies. When you view source-target dependencies, the Dependency window lists all sources or targets related to the selected object, including relevant information about those sources or targets. For example, if you select a target, you view all sources that provide data for that target, along with information about each source.
♦
Mapping dependencies. When you view mapping dependencies, the Dependency window lists all mappings containing the selected object, and relevant information about those mappings. For example, if you select a reusable transformation, you view all mappings using that transformation and information about each mapping.
♦
Shortcut dependencies. When you view shortcut dependencies, the Dependency window lists all shortcuts to the selected object and relevant details, such as the repository and folder in which the shortcut exists. When you edit an object referenced by shortcuts, use the Repository Manager to see which folders contain the shortcut.
Understanding the Repository Manager Windows
25
When you open the Dependency window, it displays dependencies for the object selected in the Navigator. You can also view mapping object dependencies in the Designer. You can view dependencies for sources, targets, transformations, mappings, mapplets, and shortcuts in the Designer. For more information, see “Using the Designer” in the Designer Guide.
Output Window The Repository Manager displays status messages in the status bar. For complex operations, 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...
After you connect to the repository, the status bar displays the word Ready. When you perform a complex operation, such as copying a folder, the Repository Manager displays details about the operation in the Output window. Figure 2-5 shows the Output window: Figure 2-5. Output Window
The Repository Manager receives notifications when the following objects are created, modified, or deleted: ♦
Folders
♦
Users
♦
Groups
You must be connected to the repository to receive notifications about folders. You need the Super User privilege to receive notifications about users and groups. For more information about privileges for Repository Manager tasks, see “Permissions and Privileges by Task” on page 367. You can change the font type and size displayed in the output window by right-clicking the window and selecting Change Font.
26
Chapter 2: Using the Repository Manager
Using Toolbars The Repository Manager displays the following toolbars by default: ♦
Standard. Contains buttons to connect to and disconnect from repositories, view dependencies for selected objects, search by keyword, view object properties, close the Dependency window, and toggle the Navigator and Output windows.
♦
Tools. Contain buttons to connect to the other PowerCenter Client application. When you use a Tools button to open another PowerCenter Client application, PowerCenter uses the same repository connection to connect to the repository and opens the same folder.
Understanding the Repository Manager Windows
27
Configuring Repository Manager Options Use the Options dialog box of the Repository Manager to configure general options. Click Tools > Options to access the general options, which relate to saving Metadata Exchange (MX) data and adding to deployment groups. Figure 2-6 shows the Options dialog box: Figure 2-6. Options Dialog Box of the Repository Manager
Table 2-2 describes the general options: Table 2-2. General Options Option
Description
Prompt User While Adding to Deployment Group
Displays the Dependency for Deployment Group dialog box when you add objects to a static deployment group. If you clear this check box, the Repository Manager adds all child objects when you add an object to a static deployment group. For more information about adding to static deployment groups, see “Adding or Removing Objects in Static Deployment Groups” on page 158.
Save All MX Data
Saves all MX data when you use the Repository Manager to import mappings. You can then access the data in MX views to analyze repository metadata or to integrate with third-party repository tools. Default is disabled. For more information about MX views, see “Using Metadata Exchange (MX) Views” on page 295.
Save Only Source/Target Dependencies
Saves only the MX data related to source/target dependencies when you use the Repository Manager to import mappings. Select this option if you use the Repository Manager to view source/target dependencies, but you do not need to view expressions of fields in MX views. Default is disabled.
Note: Saving MX data can impact performance. Select this option only if you intend to use
MX views. You can also configure the Designer to save MX data when you save mappings in the Designer. The MX data option in the Repository Manager controls the behavior of mapping imports in the Repository Manager only. It does not affect the behavior of the Designer. For more information about configuring the Designer, see “Using the Designer” in the Designer Guide.
28
Chapter 2: Using the Repository Manager
When you save MX data for mappings, PowerCenter creates a field expression for each target field in the mappings. The field expression describes the source definition and transformation expression corresponding to the target field. In addition to viewing the MX data in MX views, you can view the field expressions in the Main window of the Repository Manager when you analyze source-target dependencies.
Configuring Repository Manager Options
29
Connecting to Domains and Repositories Each repository belongs to a PowerCenter domain. You connect to a repository through the domain. Before you can initially connect to a repository, you must provide connection information for the domain. You also need to add the repository to the Navigator in the PowerCenter Client. Complete the following tasks before initially connecting to a repository: ♦
Configure the domain connection information first, and then add a repository. For more information, see “Configuring a Domain Connection” on page 30. -or-
♦
Add a repository to the Navigator, and then configure the domain connection information when you connect to the repository. For more information, see “Adding a Repository to the Navigator” on page 32.
Configure the domain connection information first if you need to add multiple repositories to the Navigator. After you create a domain connection, you may need to update or remove it. For information about updating domain connections, see “Editing a Domain Connection” on page 35. For information about deleting domain connections, see “Removing a Domain Connection” on page 36. You manage PowerCenter domains and repositories in the PowerCenter Administration Console. For more information about managing domains and repositories, see the PowerCenter Administrator Guide.
Configuring a Domain Connection You add domain connection information to the PowerCenter Client so that you can connect to repositories in the domain. After you add a domain connection, you can select from a list of associated repositories to add to the Navigator. Note: You can also enter domain connection information when you connect to a repository.
For more information, see “Connecting to a Repository” on page 32. To configure a domain connection and add repositories to the Navigator: 1.
30
In a PowerCenter Client tool, select the Repositories node in the Navigator.
Chapter 2: Using the Repository Manager
2.
Click Repository > Configure Domains to open the Configure Domains dialog box. Add a domain. Remove a domain. Edit domain connection information. Update the list of repositories with any changes made in the Administration Console.
3.
Click the Add button. The Add Domain dialog box appears.
4.
Enter the domain name, gateway host name, and gateway port number.
5.
Click OK to add the domain connection. After you add a domain connection, you can add repositories to the Navigator by selecting them in the list of associated repositories. Note: The list of associated repositories might change if a domain user adds or deletes a
Repository Service in the Administration Console while you are working in the PowerCenter Client. You refresh the list of associated repositories each time you click a domain other than the currently selected domain in the left panel. Click Refresh to update the list of associated repositories for the currently selected domain. 6.
If you need to add repositories to the Navigator, complete the following steps: ♦
Click a domain name in the left panel of the Configure Domains dialog box.
♦
In the right panel, select the repositories to add to the Navigator.
♦
Click OK.
Connecting to Domains and Repositories
31
Adding a Repository to the Navigator Add a repository when a repository already exists but does not appear in the Navigator. You can add a repository in the Repository Manager, the Designer, the Workflow Manager, or the Workflow Monitor. After you add a repository in one of the PowerCenter Client tools, it appears in the Navigator window of all the tools. To add a repository to the Navigator: 1.
In any of the PowerCenter Client tools, click Repository > Add.
2.
Enter the name of the repository and a valid repository user name.
3.
Click OK.
The repository appears in the Navigator of the PowerCenter Client tools. Before you can connect to the repository for the first time, you must configure the connection information for the domain that the repository belongs to.
Connecting to a Repository Before you can connect to a repository, you must first add the repository to the Navigator. For more information about adding a repository, see “Adding a Repository to the Navigator” on page 32. To connect to a repository: 1.
Launch a PowerCenter Client tool.
2.
Select the repository in the Navigator and click Repository > Connect, or double-click the repository. The Connect to Repository dialog box appears.
3.
32
Enter a valid repository user name and password.
Chapter 2: Using the Repository Manager
4.
If you are connecting to a repository that you have connected to before, go to step 11. -orIf you want to select an existing domain connection for the repository, go to step 9. If you need to enter the domain connection information for the repository, complete steps 5 through 8.
5.
If the Connect to Repository dialog box is not expanded, click More to view the connection settings.
6.
Click Add. The Add Domain dialog box appears.
7.
Enter the domain name, gateway host name, and gateway port number.
8.
Click OK.
9.
If the connection settings of the Connect to Repository dialog box are hidden, click More to view the connection settings.
10.
In the connection settings, select the appropriate domain connection from the list.
11.
Click Connect.
Reconnecting to a Repository and Canceling Auto-Reconnect After you connect to a repository, the PowerCenter Client can maintain the connection when a temporary network or hardware failure occurs. The ability to maintain the connection is called resilience. If you perform a PowerCenter Client action that requires a connection to the repository while the PowerCenter Client is trying to reestablish the connection, the PowerCenter Client prompts you to try the operation again after it reestablishes the connection. If the Connecting to Domains and Repositories
33
PowerCenter Client is unable to reestablish the connection during the resilience timeout period, the PowerCenter Client prompts you to reconnect to the repository manually. The PowerCenter Client resilience timeout controls how long the client attempts to reconnect to the repository after the connection is interrupted. The PowerCenter Client resilience timeout is 180 seconds and is not configurable. In the Designer, Workflow Manager, and Repository Manager, you can temporarily disable PowerCenter Client resilience to prevent the client from attempting to reestablish a repository connection during the resilience timeout period. If you do not want to wait for the resilience timeout to expire, cancel the automatic reconnection. Then, you need to manually connect to the repository again. For more information, see “Connecting to a Repository” on page 32. After the resilience timeout expires or you cancel the automatic reconnection, you must reconnect to the repository to save changes that you made before the repository connection failed. To cancel automatic reconnection: 1.
Verify that the PowerCenter Client is attempting to reestablish the repository connection. Execute an operation that requires a repository connection. If the resilience timeout has not expired, the PowerCenter Client prompts you to retry the operation after the connection is reestablished.
2.
Click Repository > Cancel Auto-Reconnect.
The PowerCenter Client stops attempting to reconnect. To perform actions that require a repository connection, you must manually connect to the repository.
34
Chapter 2: Using the Repository Manager
Managing Domain and Repository Connections You may need to modify or remove domain connection information that is outdated. Similarly, you may need to manage connections to individual repositories. You can perform the following tasks to manage domain and repository connections: ♦
Edit domain connection information.
♦
Remove domain connection information.
♦
Connect to multiple repositories.
♦
Export and import repository connection information.
♦
Remove a repository from the Navigator.
Editing a Domain Connection Edit domain connection information when you need to change a gateway host name or gateway port number for a domain connection. To edit a domain connection: 1.
Click Repository > Configure Domains.
2.
In the Configure Domains dialog box, select a domain and click the Edit button. The Edit Domain dialog box appears.
3.
Enter a new gateway host name and gateway port number, if necessary.
4.
Click OK.
Note: You can also edit a domain connection when you connect to a repository.
Managing Domain and Repository Connections
35
Removing a Domain Connection You can remove a domain connection from the PowerCenter Client. To remove a domain connection: 1.
Click Repository > Configure Domain.
2.
In the Configure Domains dialog box, select the domain connection that you want to delete.
3.
Click the Remove button.
4.
In the warning message that appears, click Yes.
Note: When you remove a domain connection, you terminate connectivity between the
PowerCenter Client and all services in the domain. To restore connectivity, you need to add the domain connection and then add repositories.
Connecting to Multiple Repositories You can connect to multiple repositories and work in multiple folders at one time. You can also connect from a local repository to a global repository and from a global repository to any local repository. To make these connections, you must have identical logins in both repositories. To create a global shortcut, connect from the local repository to the global repository. To connect to multiple repositories separately: 1.
In the Navigator, select a repository and click Repository > Connect. Existing folders in the repository now appear beneath the repository.
2.
Select another repository, and click Repository > Connect.
To connect from a local repository to the global repository: 1.
Connect to the local repository. If the repository is part of a repository domain, an icon for the global repository appears beneath the local repository icon and folders in the local repository.
2.
Double-click the icon for the global repository. A connection to the global repository opens, and you can see the folders within the global repository and the local repository. Double-click a folder in either repository to access its contents.
To connect from the global repository to a local repository: 1.
Connect to the global repository. Icons for all the local repositories in the repository domain appear beneath the global repository.
36
Chapter 2: Using the Repository Manager
2.
Double-click the icon for the local repository you want to access. The contents of the local repository appear.
Exporting and Importing Repository Connection Information The Repository Manager saves repository connection information in the registry. To simplify the process of setting up client machines, you can export that information and then import it to a different client machine. Both machines must use the same operating system. The section of the registry you can import and export contains the following repository connection information: ♦
Repository name
♦
Repository user name and 7-bit ASCII password
♦
Gateway host name and port number
To export the repository connection information from the registry: 1.
In the Repository Manager, click Tools > Export Registry.
2.
Enter the name of the export file. To identify the file, use a file name with the extension.reg, such as MySources.reg.
3.
Click OK. A dialog box appears, informing you that the Repository Manager successfully exported the repository registry file.
You can now distribute this file for import on other client machines with the same operating systems. To import the repository connection information to the registry: 1.
In the Repository Manager, click Tools > Import Registry.
2.
Navigate to the directory containing the import file and select it.
3.
Click Open. A dialog box appears, informing you that the Repository Manager successfully merged the repository connection information into the registry.
Removing a Repository from the Navigator You can remove a repository from the Navigator of the PowerCenter Client. You might need to remove a repository from the Navigator if the repository no longer exists or if you no longer use the repository.
Managing Domain and Repository Connections
37
To remove a repository from the Navigator: 1.
In the Navigator of a PowerCenter Client tool, 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 remove a repository from the PowerCenter Client registry:
38
1.
In the Navigator of the Repository Manager, click Tools > Remove Repository.
2.
Select the repository you want to remove from the registry, and click Delete.
3.
In the message box that appears, click OK to remove the repository.
Chapter 2: Using the Repository Manager
Searching for Repository Objects In the Repository Manager, you can search for repository objects using the following methods: ♦
Keyword search
♦
Search text
Perform a keyword search when you have associated a keyword with a target definition. Use Search All when you want to search through text in object names, comments, group names, and owner names associated with the repository object.
Performing Keyword Searches After you add keywords to target definitions, use them to perform searches in the Repository Manager. To search for targets containing a keyword: 1.
In the Repository Manager, connect to a repository.
2.
Click Analyze > Search by Target Keyword. The Search Target Tables For Keyword dialog box appears.
You can enter a keyword, or you can select one from the list of all keywords applied to target definitions in the repository. 3.
If you want to select a keyword, click List Keywords, select a keyword, and then click OK. -orEnter a keyword in the Keyword field.
Searching for Repository Objects
39
4.
5.
Select the options you want to use in the search: Option
Description
Exact Match
If selected, the Repository Manager looks for the entire keyword entered. If cleared, 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.
Click OK. The Repository Manager searches for matching keywords in all target definitions in the repository. A list of matching keywords appears at the bottom of the Repository Manager window.
Searching All Repository Objects Use Search All to search for text in the object name, comments, group name, and owner name associated with repository objects. You can search for text in the repository objects such as transformations, source and target fields, and tasks. To search for text in all repositor y objects:
40
1.
In the Repository Manager, connect to the repository.
2.
Click Analyze > Search All.
Chapter 2: Using the Repository Manager
The Search All dialog box appears.
3.
Enter the text you want to find.
4.
Select Match Case if you want to perform a case-sensitive search.
5.
In the item list, select the repository objects in which you want to search for the text. The Repository Manager selects all objects by default.
6.
Select the repository object attributes in which you want to search for the text. The Repository Manager selects all attributes by default.
7.
Click Find Next. The Repository Manager displays the first repository object matching the search text in the Main window.
8.
Click Find Next to find the next repository object matching the search text.
9.
Click Close to close the Search All dialog box.
Searching for Repository Objects
41
Viewing Object Dependencies Before you change or delete repository objects, you can view dependencies to see the impact on other objects. For example, before you remove a session, you can find out which workflows use the session. You can view dependencies for repository objects in the Repository Manager, Workflow Manager, and Designer tools. In the Repository Manager, Workflow Manager, and Designer, you can view dependencies when you perform the following tasks: ♦
View object history. You can view dependencies from the View History window when you view the history of an object.
♦
View checkouts. You can view dependencies from the View Checkouts window when you search for persistent checkouts.
♦
View query results. You can view dependencies from the Query Results window when you search for object dependencies or run an object query.
Note: You can check in objects from the View Dependencies dialog box, but you cannot check
in original objects for global shortcuts. In addition, you can view dependencies from the tools in the Workflow Manager and Designer. Table 2-3 lists the Workflow Manager and Designer tools used to display dependencies, and the objects that View Dependencies displays when you view dependencies: Table 2-3. Viewing Object Dependencies
42
Parent Object
Tool
Types of Child Objects Displayed
Mappings
Mapping Designer
- Global and local shortcuts to the mapping. - Sources the mapping uses. - Targets the mapping uses. - Transformations the mapping uses.
Mapplets
Mapping Designer Mapplet Designer
- Global and local shortcuts to the mapplet. - Sources the mapplet uses. - Targets the mapplet uses. - Transformations the mapplet uses.
Sources
Mapplet Designer Mapping Designer Source Analyzer
- Sources within the same folder that reference or are referenced by the source through a foreign key relationship. - Global and local shortcuts to the source.
Targets
Mapping Designer Target Designer
- Targets within the same folder that reference or are referenced by the target through a foreign key relationship. - Global and local shortcuts to the target.
Transformations
Mapplet Designer Mapping Designer Transformation Developer
- Global and local shortcuts to the transformation.
Chapter 2: Using the Repository Manager
Table 2-3. Viewing Object Dependencies Parent Object
Tool
Types of Child Objects Displayed
Sessions
Task Developer Worklet Designer Workflow Designer
- Sources the session uses. - Targets the session uses. - Mappings the session uses. - Mapplets the session uses. - Transformations the session uses. - Tasks the session uses. - Mapping the session uses. - Session configuration the session uses.
Workflows
Workflow Designer
- Sources the workflow uses. - Targets the workflow uses. - Mappings the workflow uses. - Mapplets the workflow uses. - Transformations the workflow uses. - Sessions the workflow uses. - Tasks the workflow uses. - Schedulers the workflow uses. - Session configuration the workflow uses. - Worklet the workflow uses.
Worklets
Worklet Designer Workflow Designer
- Sources the worklet uses. - Targets the worklet uses. - Mappings the worklet uses. - Mapplets the worklet uses. - Transformations the worklet uses. - Sessions the worklet uses. - Tasks the worklet uses. - Schedulers the worklet uses. - Session configuration the worklet uses.
Note: You can perform all searches in this table from the Repository Manager.
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, the object type, and a list of dependent objects and their properties.
Viewing Object Dependencies
43
Figure 2-7 shows the Dependencies dialog box: Figure 2-7. Dependencies Dialog Box
Search for dependencies.
Select options.
Filter by object type when you search for parent or child dependencies.
When you search for dependencies, you can filter the results by selecting options and object types. Table 2-4 shows the options you can select when you search for dependencies: Table 2-4. Dependencies Options Option
Description
Primary/Foreign Key Dependencies
View primary and source object dependencies where there is a primary key-foreign key relationship.
Global Shortcut Dependencies
View global shortcuts across repositories. You can select this option when you search for parents, children, or primary key-foreign key dependencies.
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.
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.
When you search for dependencies, the View Dependencies window displays the properties for each dependent object.
44
Chapter 2: Using the Repository Manager
Figure 2-8 shows the View Dependencies window: Figure 2-8. View Dependencies Window
Object Properties
Output Window Comments Window
Labels Window
Table 2-5 describes the object properties that appear in the View Dependencies window: Table 2-5. Object Properties in View Dependencies Window Properties
Description
Object Name
Name of the dependent object.
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
Version
Version number of the dependent object.
Time Stamp
Time the object was created or saved.
Status
Status of the object, Active or Deleted.
Version Comments
Comments associated with the dependent object.
Folder Name
Folder name where the dependent object resides.
Viewing Object Dependencies
45
Table 2-5. Object Properties in View Dependencies Window Properties
Description
User Name
User who created the object.
Host Name
Host name for the machine hosting the object.
Checkout Type
Type of checkout for object, Persistent or Non-Persistent.
Purged by User
Name of the user who purged the object.
Is Reusable
Status of object as reusable, Yes or No.
Is Deleted
Status of object deletion, Yes or No.
Repository
Repository 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, click File > Save to File. Figure 2-9 shows an example of the HTML file saved from a View Dependencies window: Figure 2-9. Object Dependencies Saved as HTML
46
Chapter 2: Using the Repository Manager
Validating 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. For more information about mapping validation, see the Designer Guide. For more information about validating sessions and workflows, see the Workflow Administration Guide. You can select objects to validate from the Navigator window of the Repository Manager. You can also select objects from query results or an object dependencies list. If you select objects from the Navigator, you must select objects of the same type in the same folder. If you select objects from query results or an object dependencies list, you can choose different types of objects to validate, and you can select them from within the Repository Manager, Designer, or Workflow Manager. To validate multiple objects: 1.
Select the objects you want to validate.
2.
Initiate the validation. If you select objects from query results or a list view, you must right-click one of the selected objects and select Validate. If you are selecting objects from the Navigator, you can also click Tools > Validate to initiate a validation. The Validate Objects dialog box appears.
3.
4.
Select validation options from the Validate Objects dialog box: ♦
Save validated objects. If you do not choose to save the objects in the repository, the validation just provides a report.
♦
Choose whether to check in validated objects. You can check in valid objects. You can select this option if you have selected the Save Objects that Are Successfully Made Valid option and versioning is enabled in the repository.
♦
Check in comments. If you are checking in validated objects, you must enter check-in comments. Otherwise, this option is disabled.
Click Validate.
Validating Multiple Objects
47
The validation displays status in a progress dialog box. The output window shows the status of each object being validated. You can cancel the validation from the progress dialog box. If you cancel, you do not cancel the current operation, but you cancel the remaining operations in the validation. Figure 2-10 shows the Validate Objects results box. The results box appears when validation completes. Use the results box to determine how many objects were validated and saved. To view the objects in each total, click the link. Figure 2-10. Validate Objects Results
Links to view the objects in the group.
Table 2-6 describes the information that appears in the Validate Objects window: Table 2-6. Validate Objects Properties
48
Properties
Description
Objects Provided for Validation
Total number of objects that you selected to validate. The total includes skipped objects.
Skipped Objects
Number of the following types of objects: - Objects that do not require validation, such as sources, targets, transformations, and shortcuts. - Objects that cannot be fetched, such as a deleted mapping associated with a session being validated.
Objects that Were Invalid Before the Validation
Number of invalid objects provided for validation.
Objects Successfully Validated
Number of selected objects that are valid.
Objects Still Invalid
Number of objects that require fixing or editing.
Saved/Checked In
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 to Lock Conflict
Number of validated objects you cannot save because someone has them locked.
Chapter 2: Using the Repository Manager
5.
Click a link to view the objects in the results group. Validation results that include objects provide links to the object details. When you click the link, a dialog box displays each object in the results group you select.
Validating Multiple Objects
49
Comparing Repository Objects You can compare two repository objects of the same type to identify differences between the objects. For example, you can compare two sessions to check for differences. When you compare two objects, the Repository Manager displays their attributes. You can compare objects across folders and repositories. To do this, you must have both the folders open. You can compare a reusable object with a non-reusable object. You can also compare different versions of the same object. For more information about versioned objects, see “Comparing Versions” on page 143. To compare objects, you must have Read permission on each folder that contains the objects you want to compare. You can compare the following types of objects: ♦
Designer objects. You can compare Designer objects, such as sources, targets, transformations, mapplets and mappings. For more information about comparing objects in the Designer, see the Designer Guide.
♦
Workflow Manager objects. You can compare Workflow Manager objects, such as tasks, sessions, worklets, and workflows. You can compare schedulers and session configuration objects in the Repository Manager, but not in the Workflow Manager. For more information about comparing objects in the Workflow Manager, see the Workflow Administration Guide.
You can compare instances of the same type in detail. For example, if the workflows you compare contain worklet instances with the same name, you can compare the instances to see if they differ. You can compare instances of sessions and tasks in a workflow or worklet comparison. You can compare instances of mappings and transformations in a session comparison. Further, you can compare instances of the same type within a mapping or mapplet comparison. You cannot compare objects of different types. For example, you cannot compare a source definition with a target definition. To compare repository objects: 1.
In the Repository Manager, connect to the repository.
2.
In the Navigator, select the object you want to compare. Tip: To compare the first two objects in a node, select the node.
3.
50
Click Edit > Compare Objects.
Chapter 2: Using the Repository Manager
A dialog box similar to the following one appears:
4.
Click Compare. If you choose a Designer object, a window shows the result of comparing the objects. For example, the Sources window shows the result of comparing two sources:
View object differences.
Comparing Repository Objects
51
If you choose a Workflow Manager object, such as a session, the Diff Tool window shows the result of comparing two sessions: Filter nodes that have same attribute values. Compare object instances.
Differences between objects are highlighted and the nodes are flagged. Differences between object properties are marked. Displays the properties of the node you select.
52
Chapter 2: Using the Repository Manager
Truncating Workflow and Session Log Entries When you configure a session or workflow to archive session logs or workflow logs, the Integration Service saves those logs in local directories. The repository also creates an entry for each saved workflow log and session log. If you move or delete a session log or workflow log from the workflow log directory or session log directory, you can remove the entries from the repository. Use the Repository Manager to truncate the list of workflow logs for workflows that have completed. You can also use the pmrep TruncateLog command to truncate workflow logs. For more information about the pmrep TruncateLog command, see “pmrep Command Reference” in the Command Line Reference. You can truncate all log entries for a workflow or log entries that were created before a specified date. You cannot truncate a workflow log for a workflow that is still running. The Repository Service truncates the workflow log list and the session log list at the same time. When the Repository Service truncates log entries for sessions and workflows, it also deletes the following run-time information for the sessions and workflows: ♦
Workflow details
♦
Session statistics
♦
Task details
♦
Source and target statistics
♦
Partition details
♦
Performance details
Tip: You can truncate log entries to reduce the size of the repository in the database. The log
entries can use a significant amount of space in the repository. For more information on details and statistics, see “Monitoring Workflows” in the Workflow Administration Guide. To truncate workflow and session log entries: 1.
In the Repository Manager, select the workflow in the Navigator window or in the Main window.
2.
Choose Edit > Truncate Log.
Truncating Workflow and Session Log Entries
53
The Truncate Workflow Log dialog box appears.
3.
Choose to delete all workflow and session log entries or to delete all workflow and session log entries with an end time before a particular date.
4.
If you want to delete all entries older than a certain date, enter the date and time.
5.
Click OK. The Repository Service deletes the workflow and session log entries from the repository.
54
Chapter 2: Using the Repository Manager
Managing User Connections and Locks Use the Repository Manager or the Administration Console to manage user connections and locks. In the Repository Manager, you can view and manage the following items: ♦
Repository object locks. The repository locks repository objects and folders by user. The repository creates different types of locks depending on the task. The Repository Service 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.
♦
User connections. Use the Repository Manager to monitor user connections to the repository. You can end connections when necessary. To avoid repository inconsistencies, you need to determine if the user has an active connection before closing the connection.
For more information about using the Administration Console to manage user connections and locks, see “Managing the Repository” in the Administrator Guide.
Understanding Repository Object Locks The repository uses locks to prevent users from duplicating or overwriting work. The Repository Service creates the following types of locks on repository objects when you view, edit, or run them in a workflow: ♦
In-use lock. Placed on objects you want to view.
♦
Write-intent lock. Placed on objects you want to modify.
♦
Execute lock. Locks objects you want to run, such as workflows and sessions.
The Repository Service creates and releases locks on repository objects. The repository allows multiple users to obtain in-use locks on an object. The repository allows one write-intent lock per object. This keeps multiple users from editing the object at one time, thus preventing repository inconsistencies. If you attempt to modify an object that already has a write-intent lock, the repository displays a message box: The [object_type] [object_name] is already locked by [user name].
The repository then issues an in-use lock for the object, allowing you to view the object. The repository allows one execute lock per object. This keeps you from starting a workflow that is already running, which can cause the Integration Service to load duplicate or inaccurate data.
Managing User Connections and Locks
55
Table 2-7 lists each repository lock and the conditions that create it: Table 2-7. Repository Locks Repository Lock
Created When
Maximum per Object
In-use
- Viewing an object in a folder for which you do not have write permission. - Viewing an object that is already write-locked. - Exporting an object.
Unlimited
Write-intent
- Viewing an object in a folder for which you have write permission. - Editing an object in a folder for which you have write permission. - Importing an object.
1
Execute
- Starting, aborting, or recovering a workflow.
1
Locking the Same Object The repository permits multiple in-use locks, one write-intent lock, and one execute lock simultaneously on each repository object. This means that you can edit a session while the Integration Service runs the session and another user views the session. For example, if you obtain a write-intent lock on a workflow before the Integration Service starts the workflow, the Integration Service runs the version of the workflow existing in the repository when the workflow starts. If you save changes to the repository before the workflow starts, the Integration Service runs the newly-edited workflow. If you save changes after the workflow starts, the Integration Service runs the original workflow and the repository updates the changes after the workflow completes. When the workflow starts, the Integration Service obtains an execute lock on the workflow and tasks in the workflow. If you try to start the workflow, the repository displays a message stating that the workflow is already running. If you try to edit the workflow or task when another user has a write-intent lock, you receive a in-use lock.
Locking Within Objects Some repository objects contain other repository objects. For example, workflows contain sessions and tasks, sessions contain mappings, and mappings contain at least one source and target definition. You obtain an in-use lock on an object when you view it. You can view an object used by another object without affecting the other object. However, if you save changes to an object used by other objects, the repository might mark the other objects invalid. Before using invalidated objects, you must validate them. For example, you open a mapping used by a session, delete a transformation, and save the changes. When you save the mapping, the repository notes the mapping has been changed, and marks the session and every other session using the mapping invalid. The change might invalidate any workflow containing the session. For more information about validating objects, see “Validating Multiple Objects” on page 47.
56
Chapter 2: Using the Repository Manager
For more information about validating the workflow, see “Working with Workflows” in the Workflow Administration Guide.
Locking with Cubes and Dimensions Editing or deleting cubes and dimensions can affect many objects in the repository. When you edit a property of a cube or dimension, the Repository Service creates a write-intent lock on all related objects until you save the changes or cancel the edit. Therefore, if an object is a part of a cube or dimension being edited, you might notice the object is locked even when no one is working with it. For example, if you use the Dimension Editor to change a Level Property field, the Repository Service locks all related dimension tables until you save the changes. Any user who tries to edit a related dimension table receives an in-use lock on the table.
Locking Business Components To maintain the integrity of the repository data, the Repository Service locks the business component tree while its contents are being edited. This prevents you from copying or editing the business component. Locking occurs at the root directory of the business component tree. For example, if Finance is the root directory of the tree, with General Ledger and Accounts Receivable as subdirectories, the Repository Service locks the Finance directory while you make changes to the Accounts Receivable or General Ledger subdirectories. The Repository Service releases a lock when you click Repository > Save. Use the Show Locks feature to see if the business component or objects it points to are locked.
Acquiring Locks During Deployment When you copy a folder or deployment group to another repository, you must acquire locks on the objects in the target repository. If the object locks are not immediately available, by default the deployment operation waits until either you cancel the deployment or the object locks are acquired. For more information about deploying objects, see “Copying Folders and Deployment Groups” on page 191. If you use pmrep to copy folders or deployment groups, you can specify a timeout for the deployment operation. If pmrep does not acquire object locks in the target repository during the timeout period, the deployment fails. For more information about using pmrep for deployment, see “pmrep Command Reference” in the Command Line Reference.
Viewing User Connections and Locks In the Repository Manager, you can monitor and close user connections, and you can view and release locks. You can also perform these tasks in the Administration Console. For more information about managing user connections and locks in the Administration Console, see “Managing the Repository” in the Administrator Guide.
Managing User Connections and Locks
57
Viewing User Connections Use the Repository Manager to view connection details for users and applications connected to the repository. Table 2-8 describes the repository user connection details: Table 2-8. Repository User Connection Details Property
Description
User
User name associated with the connection.
Connection ID
Identification number assigned to the repository connection.
Application
Repository client application associated with the connection.
Host Name
Name of the machine running the application.
Host Address
TCP/IP address of the machine associated with the connection.
Host Port
Port number the machine hosting the repository client application uses to communicate with the repository.
Login Time
Time the user connected to the repository.
Last Active Time
Time of the last metadata transaction between the repository client application and the repository.
To view user connection details: 1.
Launch the Repository Manager and connect to the repository.
2.
Click Edit > Show User Connections. The Repository Connections dialog box appears.
3.
58
To sort the connections by column, click the column name.
Chapter 2: Using the Repository Manager
Viewing Locks You can view locks and identify residual locks in the Repository Manager or in the Administration Console. Table 2-9 describes the object lock information in both the Repository Manager and the Administration Console: Table 2-9. Object Lock Properties Column Name
Description
User
User name locking the object.
Connection ID
Identification number assigned to the repository connection.
Folder
Folder in which the locked object is saved.
Object Type
Type of object, such as folder, version, mapping, or source.
Object Name
Name of the locked object.
Lock Type
Type of lock: in-use, write-intent, or execute.
Lock Time
Time the lock was created.
Hostname
Name of the machine locking the object.
Application
Application locking the object, such as Designer, Workflow Manager, Repository Manager, or Integration Service.
To show all repository locks: 1.
In the Repository Manager, connect to a repository.
2.
To view all locks in the repository, click Edit > Show locks. The Object Locks dialog box appears.
3.
To sort the view of the locks by column, click the column name.
4.
To view updated lock information, click Refresh.
Managing User Connections and Locks
59
Closing User Connections and Releasing Locks Sometimes, the Repository Service does not immediately disconnect a user from the repository. The repository has a residual connection when the repository client application or machine is shut down but the connection remains in the repository. This can happen in the following situations: ♦
Network problems occur.
♦
A PowerCenter Client, Integration Service, repository, or database machine shuts down improperly.
A residual repository connection also retains all repository locks associated with the connection. If an object or folder is locked when one of these events occurs, the repository does not release the lock. This is called a residual lock. If a system or network problem causes a repository client application to lose connectivity to the repository, the Repository Service detects and closes the residual connection. When the Repository Service closes the connection, it also releases all repository locks associated with the connection. When possible, allow the Repository Service to detect and release residual locks. You can also use the Repository Manager or Administration Console to manually close residual user connections and release residual locks in the repository. The Integration Service opens additional connections to the repository for each Integration Service process and DTM process. If you close a repository connection to an Integration Service, the Repository Service also closes all other connections to the same Integration Service. You do not need special privileges to terminate connections associated with a repository user name. For more information about the privileges and permissions to terminate other user connections and unlock objects, see “Repository Manager Tasks” on page 373. Warning: Closing an active connection may cause repository inconsistencies. Close residual connections only. To manually close a connection in the Repository Manager: 1.
Launch the Repository Manager and connect to the repository.
2.
Click Edit > Show User Connections.
3.
In the Repository Connections dialog box, select the connection you want to terminate.
4.
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” on page 59.
5.
Verify that the user is not connected to the repository.
6.
Click End Connection. The Repository Service closes the user connection and releases all locks associated with the connection.
60
Chapter 2: Using the Repository Manager
7.
Click Close to return to the Repository Manager.
Tip: To avoid repository inconsistencies, before unlocking an object or folder, determine who
owns the lock and make sure the owner is not using the object. Before unlocking multiple objects or closing multiple user connections, ask all users to exit the repository.
Managing User Connections and Locks
61
62
Chapter 2: Using the Repository Manager
Chapter 3
Managing Users and Groups This chapter includes the following topics: ♦
Overview, 64
♦
User Groups, 65
♦
User Authentication, 68
♦
Creating and Editing Repository Users, 71
♦
Repository Privileges, 79
♦
Permissions, 85
♦
Tips, 88
♦
Troubleshooting, 91
63
Overview PowerCenter offers several features that enable you to manage users and groups: ♦
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 names 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. Use an external directory service to manage user names and passwords.
♦
Repository privileges. Ability to perform actions within the repository and to run the Integration Service. 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 particular folder.
♦
Folder permissions. 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. Most tasks also require the appropriate repository privileges.
♦
Permissions on global objects. Ability to use global objects. Global objects include labels, deployment groups, queries, and connection objects. You can grant global object permissions to users and groups.
Take time to plan an overall strategy so that you can implement appropriate user groups and security measures for the repository.
64
Chapter 3: Managing Users and Groups
User Groups You create custom user groups to manage users and repository privileges efficiently. After creating a new user group, you assign that group a set of privileges. Each repository user must be assigned to at least one user group. When you assign a user to a group, the user: ♦
Receives all group privileges.
♦
Inherits any change to group privileges.
♦
Loses and gains privileges if you change the user group membership.
You can also assign users to multiple groups. This grants the user the privileges of each group. Note: When you revoke a privilege from a group, you revoke the privilege from each user in
the group. However, if a user has been granted the privilege individually (as with default privileges), you must revoke the privilege individually to restrict that user. For more information, see “Repository Privileges” on page 79. Use the Repository Manager to create and edit repository user groups. For more information about the privileges and permissions to administer repository user groups see “Repository Manager Tasks” on page 373.
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 create additional groups and assign privileges and permissions to those groups. There are two default repository user groups: ♦
Administrators. This group initially contains two users that are created by default. The default users are Administrator and the database user that created the repository. You cannot delete these users from the repository or remove them from the Administrators group.
♦
Public. The Repository Manager does not create any default users in the Public group.
You cannot delete these groups from the repository or change the default privileges. For more information about default privileges, see “Default Privileges” on page 80.
Owner’s Group Permissions You can define Owner’s Group permissions when you create or edit a folder. You can grant Owner’s Group permissions to one of the groups to which the folder owner belongs. If the owner belongs to more than one group, you must select one of the listed groups to receive Owner’s Group permissions. For example, if the owner of a folder belongs to one group, Developer, the Developer group receives Owner’s Group permissions on the folder. If you assign read and write folder User Groups
65
permissions to the Owner’s Group, then every user in the Developer group has read and write permission for the folder. If the owner of the folder belongs to both the Developer group and the Production group, you must choose one of those groups to receive Owner’s Group permissions. If you select the Production group, the Production group receives read and write permissions on the folder.
Creating a User Group Complete the following steps to create a user group. To create a user group: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Click the Groups tab.
4.
Click Add.
5.
Enter the name of the group.
6.
Click OK. The new group now appears in the list of all groups defined for the repository.
66
Chapter 3: Managing Users and Groups
7.
Click OK to return to the Repository Manager.
You can now assign privileges and users to the group.
Editing a User Group You can edit the description of an existing user group at any time. However, you cannot edit the default groups, Public and Administrators. To edit a user group: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select a group on the Groups tab and click Edit.
4.
Edit the description and click OK. You can enter up to 2,000 characters. The first 256 characters appear in the Manage Users and Privileges window.
5.
Click OK again to save the changes.
Deleting a User Group You can delete any user group in the repository except the default repository user groups, Public and Administrators. Note: If you delete a group that contains users, the Repository Manager reassigns those users to
the Public group. To delete a user group: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select the group in the Groups tab that you want to delete.
4.
Click Remove. A message appears stating all users in the group will be assigned to the Public group.
5.
Click OK.
6.
Click OK to save the changes.
User Groups
67
User Authentication Each repository user needs a user name and password to access the repository. PowerCenter uses one of the following methods to authenticate users: ♦
PowerCenter default authentication
♦
Lightweight Directory Access Protocol (LDAP) authentication
When you install PowerCenter, the PowerCenter installation program configures each repository to use repository authentication. If you want to use LDAP authentication for a repository, you must change the authentication method after you complete the PowerCenter installation. You can create users and maintain passwords in the repository with PowerCenter default authentication. The security module verifies users against these user names and passwords. LDAP defines a network protocol for accessing a directory service. If you use LDAP to authenticate users, the repository security module passes a user login to the external directory for authentication. To accomplish this, the repository maintains an association between repository user names and external login names. The repository administrator maintains the user-name/login associations, but it does not maintain user passwords in the repository. If you use an external directory service, you must ensure that the Administrator has a valid external login name when you register the authentication module with the repository. For more information about registering a plug-in, see “Managing the Repository” in the Administrator Guide. Tip: If you use default authentication, change the Administrator password immediately after
creating the repository to protect the metadata. For information about the privileges and permissions to administer repository users, see “Repository Manager Tasks” on page 373.
Using Default Authentication By default, each repository in a domain uses repository authentication to authenticate users that log in to the repository. Users log in to the repository through the PowerCenter Clients. When a user logs in, the Repository Service authenticates the user name and password against the user accounts created for the repository. The repository administrator uses the Repository Manager to create users and set user permissions for the repository. If you use default authentication, repository users can have one of the following statuses:
68
♦
Enabled. The user name is valid for accessing the repository. New users receive the enabled status.
♦
Disabled. The user cannot access the repository. A user receives this status if the repository administrator disables the user.
Chapter 3: Managing Users and Groups
Using LDAP Authentication You can use LDAP authentication on one or more repositories in a domain. LDAP defines a network protocol for accessing a directory service. If you use LDAP to authenticate users, the repository security module passes a user login to the external directory for authentication. If you use LDAP authentication for repository users, the repository maintains an association between repository user names and external login names. When you create a user, you can select the login name from the external directory. If you know the directory login name, use the pmrep Registeruser command to create the user name and associated login name. For more information about Registeruser, see “pmrep Command Reference” in the Command Line Reference. For example, you might deploy a repository to a production server. A repository user called JSmith might have a directory login name JohnS on the production server. You must associate JSmith with the directory login name JohnS for the user to access the repository. For more information about associating a user name with a login name, see “Enabling a User” on page 76. When you view users in the repository, you can see the repository user names and the directory login names. Figure 3-1 shows the repository user names and associated login names: Figure 3-1. Repository User Names and External Login Names
User Status Login Name Repository User Name
The user status indicates if a user can access the repository.
User Authentication
69
Table 3-1 describes the user statuses: Table 3-1. User Statuses Status
Description
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. A repository administrator must explicitly enable the user by linking the user name to the login name.
Suggested
The user name is in the repository, but is not linked to a login name (as above) in the external directory. This status is similar to “no login assigned” except that the security module finds a possible matching login name that you can enable.
Account Removed
The user name is no longer on the external directory, and the user cannot access the repository. For example, if the login changes in the external directory, the security module cannot find the login name. The status changes to “account removed.” The repository administrator must explicitly enable you by linking a repository user name to a new login name in the external directory.
User status changes for the following reasons:
70
♦
The system administrator enables or disables it.
♦
The login changes in the LDAP directory.
♦
The user authentication mode changes between LDAP and default authentication.
Chapter 3: Managing Users and Groups
Creating and Editing Repository Users In the Repository Manager, you create a user name for each user accessing the repository. Each user belongs to at least one user group. When you create a user, the Repository Manager assigns the user to the Public group. To change the group, you must first add the user to another group and then remove the user from the Public group. Tip: Before creating repository users, create user groups, and assign the appropriate privileges
to those groups. For more information about groups, see “User Groups” on page 65. To manage repository users, you must have the Admin Repository privilege.
Creating a User Under Default Authentication If you use default user authentication, you enter user names in the repository and assign a password for each user name you create. To create a user under default authentication: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges. The Manage Users and Privileges dialog box appears.
3.
Click Add. The New User dialog box appears.
Creating and Editing Repository Users
71
4.
Enter a user name and password between 1 and 75 characters long, with no leading or trailing spaces. Use the optional Description and Contact Info fields to further identify the user.
5.
Click Group Memberships.
The Member Of list displays the groups that the user belongs to. 6.
72
To add the user to a group, select the group in the Not Member Of list, and click Add.
Chapter 3: Managing Users and Groups
The group appears in the Member Of list.
7.
To remove the user from a group, select the group in the Member Of list, and click Remove. Note: You cannot remove a user from a group when the user belongs to one group.
8.
Click OK.
Editing a User Password If you use default authentication, you can edit the user password. Note: If you change the password for the repository administrator, you must update
environment variables and pmcmd commands that use the repository administrator password. Replace the existing repository password with the new password. For information about the privileges and permissions to edit a password see “Repository Manager Tasks” on page 373. To edit a password: 1.
In the Repository Manager, connect to the repository.
2.
Click Security > Change Current Password.
Creating and Editing Repository Users
73
3.
Enter the old password.
4.
Enter the new password twice to confirm it.
5.
Click OK.
Creating a Repository User Under an External Directory Service If you use an external directory service for maintaining repository users, you add repository users from a list of login names from the external directory. You do not create repository user passwords. To add users with an external directory service: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Click Add. The Add Users dialog box displays a list of names from the external directory service.
4.
Select a login name from the external directory list and click Add.
The login name appears at the bottom of the dialog box. If you select more than one name, the names appear at the bottom separated by semicolons. Note: You can type a name at the bottom of the dialog box, but it must match a valid
login name in the directory. To check the spelling, click Check Names.
74
Chapter 3: Managing Users and Groups
5.
If any of the names you enter do not match a valid directory service login, you must correct the name or remove it from the selections on the Invalid Name dialog box. Click OK.
6.
Click OK in the Add Names dialog box to add the selections to the user-name/loginname association. The Manage Users and Privileges window displays the user name, login name, and enabled status.
For more information about adding a user to a group or editing a user description, see “Editing a User” on page 75.
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. The following exceptions apply when you edit users: ♦
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: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select a user and click Edit. The Edit User dialog box appears. If you use default authentication, you can change the password.
4.
To change the password, enter the new password twice. The password can be between 1 and 75 characters long, with no leading or trailing spaces. Passwords must be in 7-bit ASCII. Creating and Editing Repository Users
75
5.
To edit the description, enter up to 2,000 characters. The first 256 characters appear in the Manage Users window.
6.
To edit group memberships, click Group Memberships. If the user belongs to one group, you must add the user to another group before removing the user from the original group.
7.
To add a group membership, select the group in the Not Member Of list, and click Add. The group appears in the Member Of list.
8.
To remove the user from a group, select the group in the Member Of list, and click Remove. The selected group appears in the Not Member Of list.
9.
To save the changes, click OK.
10.
Click OK again.
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 the repository user name with the directory login name. When you enable a user under default authentication, the status changes. To enable a user: 1.
Click Security > Manage Users and Privileges. The Manage Users and Privileges dialog box appears.
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 appears. This dialog box displays a list of valid login names from the external directory service. It appears if you use an external directory service.
If a user has a suggested login name, you enable the association immediately when you click Enable. To associate the user name with a different login name, you can disable and then enable the user. You can also use the pmrep Edituser command. For more
76
Chapter 3: Managing Users and Groups
information about Edituser, see “pmrep Command Reference” in the Command Line Reference.
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 appears 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. To disable a repository user: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select the users you want to disable. You can select multiple users at a time.
4.
Click Disable. The user status changes to disabled.
You can also use the pmrep Edituser command to disable users from the command line. For more information about disabling users from the command line, see “pmrep Command Reference” the Command Line Reference.
Removing a Repository User When you remove a user from a repository that uses an external directory service, you remove the user name in the user-name/login association. If the repository uses default authentication, you remove the user name from the repository. Creating and Editing Repository Users
77
Note: If a repository user has an execute lock on a workflow, you cannot remove the user. To
remove the user, you must stop the workflow or wait until the execute lock is released. To remove a repository user:
78
1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select a user and click Remove.
4.
Click Yes to confirm that you want to remove the user.
Chapter 3: Managing Users and Groups
Repository Privileges The Repository Manager grants a default set of repository privileges to each new user and group. You can add or remove privileges from any user or group except: ♦
Administrators and Public groups (the default read-only repository groups)
♦
Administrator user and database user who created the repository (the users created in the Administrators group)
You can grant privileges to groups or to individual users. A privilege granted to an individual user remains with the user until you remove it. For example, if you move a user from a group that has the Admin Repository privilege into a group that does not, the user loses the Admin Repository privilege. However, if you grant the Admin Repository privilege to the user, the user retains this privilege regardless of changes in group membership. You can perform some repository tasks, such as creating user groups, with repository privileges only. Folder related tasks, however, generally require one or more folder permissions in addition to the related repository privilege to perform the task. Global objects have separate read, write, and execute permissions. For more information about global object permissions, see “Configuring Permissions on Global Objects” on page 86. For tighter security, grant the Super User privilege to an individual user, not an entire group. This limits the number of users with the Super User privilege and ensures that the user retains the privilege even if you remove the user from a group. For a list of common repository tasks and the permissions and privileges necessary to perform those tasks, see “Permissions and Privileges by Task” on page 367.
Repository Privileges
79
Default Privileges The Repository Manager grants each new user and new group the default privileges. Table 3-2 lists the default repository privileges: Table 3-2. Default Repository Privileges Default Privilege
Permission
Permission Object
Grants You the Ability to
Browse Repository
n/a
n/a
- Add and remove reports. - Change a user password. - Connect to the repository using the Repository Manager. - Import, export, or remove the registry. - Search by keywords.
Read
Folder
- Browse repository. - Copy a folder. You must also have Admin Repository or Super User privilege in the target repository. - Compare folders. - Edit folder properties for folders you own. - Freeze folders you own. - Unlock objects and folders locked by a user name. - View dependencies.
Read
Query
- View query.
Execute
Query
- Run query.
Write
Query
- Create or edit query.
n/a
n/a
- Configure connection information. - Connect to the repository using the Designer. - Perform Use Repository Manager tasks in the Designer.
Read
Folder
- Copy objects from the folder. - Create shortcuts to objects in the folder. - Export objects. - View objects in the folder.
Read/Write
Folder
- Copy objects into the folder. - Create or edit metadata. - Create shortcuts from shared folders. - Import objects.
n/a
n/a
- Remove label references.
Write
Deployment group
- Delete from deployment group.
Use Designer*
Use Repository Manager
80
Chapter 3: Managing Users and Groups
Table 3-2. Default Repository Privileges Default Privilege
Use Workflow Manager*
Permission
Permission Object
Grants You the Ability to
Write
Folder
- Change object version comments if not the owner. - Change status of the object. - Check in. - Check out/undo check-out. - Delete objects from folder. - Mass validation (Needs write permission if options selected.) - Recover after delete.
Read
Folder
- Export objects.
Read Write
Folder Deployment group
- Add to deployment group.
Read Write
Original folders Target folder
- Copy objects. - Import objects.
Read Write/ Execute
Folder Label
- Apply label.
n/a
n/a
- Connect to the repository using the Workflow 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.
Read/Write
Connection
- Edit database, FTP, and external loader connections in the Workflow Manager.
Execute
Folder
- Abort workflow. - Restart workflow. - Recover suspended workflow. - Stop workflow.
Read
Folder
- Export objects. - View session details and session performance details. - View sessions. - View tasks. - View workflows.
Read
Folder
- View session log. - View workflow log.
Read/ Execute
Connection
- Schedule or unschedule workflows. - Start workflows immediately.
Read/Write
Folder
- Create and edit workflows and tasks. - Import objects. - Validate workflows and tasks.
Repository Privileges
81
Table 3-2. Default Repository Privileges Default Privilege
Permission
Permission Object
Grants You the Ability to
Read/Write Read
Folder Connection
- Create and edit sessions.
* The Use Designer and Use Workflow Manager privileges enable you to perform many of the tasks that you can perform in the Repository Manager with the Use Repository Manager privilege.
Extended Privileges In addition to the default privileges, the Repository Manager provides extended privileges that you can assign to users and groups. The Repository Manager grants extended privileges to the Administrators group by default. Table 3-3 lists the extended repository privileges: Table 3-3. Extended Repository Privileges Extended Privilege
Permission
Permission Object
n/a
n/a
- Create, upgrade, backup, delete, and restore the repository. - Manage passwords, users, groups, and privileges. - Start, stop, enable, disable, and check the status of the repository.
Write
Folder
- Check in or undo check out for other users. - Purge (in version-enabled repository).
Admin Integration Service
n/a
n/a
- Disable the Integration Service using the infacmd program. - Connect to the Integration Service from PowerCenter client applications when running the Integration Service in safe mode.
Super User
n/a
n/a
- Perform all tasks, across all folders in the repository. - Manage connection object permissions. - Manage global object permissions. - Perform mass validate.
Workflow Operator
n/a
n/a
- Connect to the Integration Service.
Read
Folder
- View the session log. - View the workflow log. View session details and performance details.
Execute
Folder
- Abort workflow. - Restart workflow. - Resume workflow. - Stop workflow. - Schedule and unschedule workflows.
Read Execute
Folder Connection
- Start workflows immediately.
Admin Repository
82
Chapter 3: Managing Users and Groups
Grants You the Ability to
Table 3-3. Extended Repository Privileges Permission
Permission Object
Grants You the Ability to
Execute Execute
Folder Connection
- Use pmcmd to start workflows in folders for which you have execute permission.
Manage Connection
n/a
n/a
- Create and edit connection objects. - Delete connection objects. - Manage connection object permissions.
Manage Label
n/a
n/a
- Create labels. - Delete labels.
Read/Write
Label
- Edit labels. - Manage label permissions.
n/a
n/a
- Create folders. - Delete folders.
Read
Folder
- Edit folder properties. - Freeze folders.
Read
Folder
- Copy folders.
Read/ Execute
Deployment group
- Deploy deployment groups. - Roll back deployment groups.
Read/ Execute
Deployment group
- Create and edit deployment groups. - Delete deployment groups. - Manage deployment group permissions.
Extended Privilege
Manage Folder
Deploy
Manage Deployment Group
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. Reserve extended privileges for individual users and grant default privileges to groups.
Assigning and Revoking a Privilege You can assign and revoke repository privileges of a user or group. When you change privileges for a group, you change the privileges granted to every user in the group. However, users retain individually granted privileges until you revoke them. For information about the privileges and permissions to assign or revoke privileges, see “Repository Manager Tasks” on page 373. Note: You cannot change the privileges of the default user groups or the default repository
users. To assign a privilege to a user or group: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Click Privileges. Repository Privileges
83
4.
Select the privileges you want to assign to each user or group.
5.
Click OK to save the changes.
Note: If you assign Super User privileges to a user, you cannot change the other privileges for
that user. Super User privilege enables all privileges for the user. To revoke a privilege from a user or group:
84
1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Clear the privileges you want to revoke.
4.
Click OK to save the changes.
Chapter 3: Managing Users and Groups
Permissions You can maintain user and group permissions for access to folders and global objects. Global objects are labels, deployment groups, queries, and connections. You can maintain the following permissions for each type of object: ♦
Read permission. You can view the folders and objects.
♦
Write permission. You can create or edit objects in a folder, maintain queries or labels, add or delete objects from deployment groups.
♦
Execute permission. You can run or schedule a workflow in the folder, run queries, apply labels, or copy deployment groups.
To perform a task you must have the privilege to perform the task and the applicable permission. For example, you might have the Use Designer privilege to connect to the repository through the Designer, but you must also have folder read and write permission to open and edit a mapping in a folder. If you do not have both the privilege and permissions, you cannot open or edit mappings in that folder.
Configuring Folder Permissions Some tasks require fewer folder permissions with an extended repository privilege than with a default repository privilege. For example, if you have the Use Workflow Manager default privilege, you must have both read and execute permission to start a workflow in a folder. If you have the Workflow Operator extended privilege, you can start a workflow if you have read permission. The Super User privilege is not restricted by any folder permissions. If you have the Super User privilege, you do not require any permissions. You can grant folder permissions at three levels. Table 3-4 lists the folder security levels: Table 3-4. Folder Object Security Levels Level
Includes
Owner
The owner of the folder, as listed in the owner menu.
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.
Repository
All groups and users in the repository.
Each permission level includes the members of the level above it. For example, if you grant 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. You can edit folder permissions and properties at any time. To create, edit, and delete folders, you must have the Manage Folder privilege.
Permissions
85
For more information about the privileges and permissions to edit folder properties, see “Repository Manager Tasks” on page 373. To edit folder permissions and properties: 1.
In the Repository Manager, connect to a repository.
2.
Select the folder in the Navigator. If the folder does not appear in the Navigator, you do not have read permission for the folder.
3.
Click Folder > Edit.
4.
If necessary, select a new owner from the Owner menu.
5.
If the owner belongs to more than one group, select a group from the Group menu.
6.
Edit the folder permissions.
7.
Click OK to save the changes.
Configuring Permissions on Global Objects To configure and manage permissions on a global object, you must be the owner of the global object or you must have the relevant extended privilege. For example, you must have the Manage Connection privilege to manage a connection object, or you must be the owner of the connection object. The initial owner of a global object is the user who creates the object. The Super User privilege gives a user all extended privileges. For more information about configuring connection object permissions, see “Managing Connection Objects” in the Workflow Administration Guide. You cannot assign permissions on a private query. To enable others to use it, change the query type to public. When you assign permissions on global objects, you can assign them on three levels. Table 3-5 lists global object security levels: Table 3-5. Global Object Security Levels Level
Includes
World
All repository users.
Users
Object owner and other users that have been added to the permissions list. By default, the owner is the creator of the object.
Groups
Owner’s group and other groups that have been added to the permissions list. If a group receives permissions, every user in a group receives the permissions.
Each global 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.
86
Chapter 3: Managing Users and Groups
When you configure permissions on a global object, 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 the Super User privilege receive all permissions by default.
For information about tasks you can perform with user privileges, permissions on folders, and permissions on global objects, see “Repository Privileges” on page 79. To configure permissions on global objects, select a global object in a global objects browser such as the Label Browser, and click Permissions.
Click to define permissions.
The Permissions dialog box appears.
Change owner. Change group. Add a new group or user. You cannot change permissions of users with Super User privilege and users belonging to the Administrators group.
Permissions
87
Tips When setting up repository users, groups, and security, keep it simple. Securing the environment involves the following basic principles: ♦
Limiting users
♦
Restricting privileges
♦
Defining permissions
Before implementing security measures, answer the following questions: ♦
Who needs access to the repository? What do they need the ability to do?
♦
Where can I limit repository privileges by granting folder permissions instead?
♦
Who creates transformations and mappings? Do they need access to all folders?
♦
Who schedules workflows?
♦
Who needs to start workflows manually? Do they need to access all workflows in the repository?
♦
Who administers the repository?
♦
Who starts and stops the Integration Service?
♦
Who needs the ability to perform all functions within the repository, across all folders?
After you evaluate the needs of the repository users, you can create appropriate user groups, limit privileges, and limit folder permissions. Create groups with limited privileges. The simplest way to prevent security breaches is to limit the number of users accessing the repository. Then, limit the ability of other repository users to perform unnecessary actions, such as running sessions or administering the repository. To do this, determine how many types of users access the repository. Then create separate user groups for each type. The more distinct the user groups, the tighter the repository security. After you establish separate groups, assign the appropriate privileges to those groups and design folder permissions to allow their access to particular folders. Do not use shared accounts. Using shared accounts negates the usefulness of the repository locking feature. The repository creates locks on objects in use. Breaking a valid lock can cause repository and inconsistencies. For more information about locking, see “Managing User Connections and Locks” on page 55. Limit user and group access to multiple repositories. When working in a multiple repository environment (PowerCenter only), limit the number of users and groups accessing more than one repository. This becomes more important when repositories contain folders with the same or similar names. Restricting the number of 88
Chapter 3: Managing Users and Groups
crossover users limits the possibility of a user connecting to the wrong repository and editing objects in the wrong folder. Customize user privileges. If a single user requires more privileges than those assigned to the user's group, and you need to keep the user in that group for the purpose of folder permissions, you can add individual privileges to that user. For example, if you have a user working in the Developers group, but this user also needs to deploy folders and deployment groups, you can add the Deploy privilege to the individual user. Limit the Super User privilege. The Super User privilege permits you to perform any task despite folder-level restrictions. This includes starting any workflow, and unlocking other user's locks. To protect the repository and target data, restrict the number of users who need this all-encompassing privilege. You can allow users a limited ability to run workflows by granting the Use Workflow Manager privilege with read and execute permission. You can allow users a limited ability to unlock locks by granting them the Browse Repository or Admin Repository privilege. Users with either the Browse Repository or Admin Repository privilege can unlock any object or folder locked by their own user name. All members of the Administrators group have the Super User privilege. Therefore, you must limit the number of users you assign to the Administrators group. Limit the Deploy privilege. The Deploy privilege permits a user to copy a folder from one repository to another. Because this feature is used to deploy folders into production, you should limit this privilege in production repositories. Restrict the Workflow Operator privilege. With the Workflow Operator privilege, 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 the 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 execute permission for the folder.
Tips
89
Grant the Manage Connection privilege to repository administrators. You need the Manage Connection privilege to create and edit connection objects. If a repository administrator performs these tasks and does not have the Super User privilege, grant the privilege either to the individual user or to the Administrators group. If you grant the Manage Connection privilege to the Public group, all users can create and edit connection objects.
90
Chapter 3: Managing Users and Groups
Troubleshooting The following solutions might help you with managing users and groups: After creating users and user groups, and granting different sets of privileges, I find that none of the repository users can perform certain tasks, not 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 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 Admin Repository privilege, but I cannot access a repository using the Repository Manager. To perform tasks in the Repository Manager with the Admin 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
91
92
Chapter 3: Managing Users and Groups
Chapter 4
Working with Folders
This chapter includes the following topics: ♦
Overview, 94
♦
Folder Properties, 96
♦
Configuring a Folder, 99
♦
Comparing Folders, 102
93
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 and to help you logically organize the repository. Each folder has a set of configurable properties that enable 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.
Using Folders in the Repository Manager You create and maintain folders in the Repository Manager. In the Repository Manager, you can view the users accessing folders and the objects within each folder. You can also copy and replace folders within the repository or across repositories.
Using Folders in the Designer In the Designer, you use folders to store sources, transformations, cubes, dimensions, mapplets, business components, targets, and mappings. When you create a mapping in a folder, you can include any object in the folder, and you can create shortcuts to objects in shared folders. You can copy objects from one folder to another. If you want to use an object in a non-shared folder, you can copy it into the working folder. If you work with multiple repositories, you can also copy objects across repositories.
Using Folders in the Workflow Manager In the Workflow Manager, you use folders to store workflows, tasks, and sessions. When you create a workflow, you can include any session or task in the folder. Use the Copy Wizard to copy individual workflows to other folders. To copy all workflows within a folder to a different location, you can copy the entire folder. Use any mapping in a folder to create a session in that folder. You can copy a session within a folder or to another folder.
Organizing Folders Folders are designed to be flexible. They enable you to organize the repository logically. Keep in mind that any mapping in a folder can use those objects that are stored in the same folder or that are stored in a shared folder and accessed through a shortcut.
94
Chapter 4: Working with Folders
In a repository, you might create folders for each development project, subject area, user, or type of metadata. For example: ♦
You might create a single folder for each type of data. To organize accounting data, you might create one folder for accounts payable and another for accounts receivable.
♦
You can create a folder for each repository user, designed to store work for that user. If users work on separate projects, this technique avoids any problems that might occur if two people attempt to edit the same metadata at the same time.
♦
You might create a different folder for each type of metadata (source definitions, target definitions, mappings, schemas, and reusable transformations) that you create through the Designer.
Before creating a system of folder organization, you need to understand the security measures associated with folders so you can best protect repository objects.
Overview
95
Folder Properties Each folder has several configurable properties on the folder property sheet. 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 about changing the status of all objects in a folder, see “Working with Version Properties” on page 135.
Permissions Permissions allow repository users to perform tasks within a folder. With folder permissions, you control user access to the folder, and you control the tasks that users can 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. You can view the folder and objects in the folder.
♦
Write permission. You can create or edit objects in the folder.
♦
Execute permission. You can 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 more information about how folder permissions interact with repository privileges, see “Managing Users and Groups” on page 63. For more information about permission and privilege combinations that allow you to perform each task, see “Permissions and Privileges by Task” on page 367.
96
Chapter 4: Working with Folders
Permission Levels You can grant three levels of security when you use folder permissions. Table 4-1 lists the users included in each permission level: Table 4-1. Folder Permissions Permission Level
Includes
Owner
Owner of the folder.
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.
Repository
All users and groups in the repository.
Each permission level includes the members in the level above it. If you restrict a permission from Owner or Owner’s Group and then grant the same permission to Repository, 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.
Folder Owner and Owner's Group Because you grant permissions to Owner and Owner’s Group, the choices for these settings affect how repository users access objects within the folder. When you create a folder, you can select any user in the repository to be the folder owner. If the folder owner belongs to more than one repository group, you can also choose a repository group as the Owner’s Group. If the owner belongs to one group, that group becomes the Owner’s Group. For example, the repository contains users in two user groups. You want a folder allowing full access to one group while limiting access to the other. To do this, you make a user in the fullaccess group the owner of the folder, grant all folder permissions to Owner and Owner’s Group, and then restrict Repository permissions. As long as a group does not have the Super User privilege, restricting Repository permission limits that group’s folder permissions. The owner of the folder has an additional ability to edit the folders properties as long as the owner has the Browse Repository privilege and read permission on the folder. Any other user must have Admin Repository and read permission, or the Super User privilege to edit folder properties.
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, such as an Expression transformation that calculates sales commissions, you can place the object in a shared folder. You can then access the object from other folders by creating shortcuts to the object.
Folder Properties
97
Shortcuts inherit changes to the original object. So if, for example, you change the way an organization calculates sales commissions, you can change the Expression transformation in the shared folder. Then all shortcuts to the Expression transformation inherit the changes. If you want to use an object in a shared folder without inheriting any future changes, you can copy the existing object. Note: After you make a folder shared, you cannot reverse it.
Shared Folders in Global Repositories Shared folders in global repositories can be used by any folder in the domain. For example, if you are working in a folder in a local repository, you can connect to the global repository and create a shortcut to a shared folder for the official sales commission Expression transformation. As with local shared folders, if changes are made to the original object, the repository updates all shortcuts in the domain to reflect those changes.
98
Chapter 4: Working with Folders
Configuring a Folder Each folder in the repository must have the following information configured in the folder properties dialog box: ♦
Folder name. The name of the folder in the repository.
♦
Folder owner. The owner can have a different level of permissions within the folder, separate from general users, and the ability to administer the folder.
♦
Owner’s group. The group selected can also have a different level of permissions in the folder.
♦
Folder status. Specifies a status applied to all objects in the folder. Each status defines the ability of users to check out and edit objects in the folder and whether copy deployment group operations can create new versions of objects in the folder.
♦
Folder permissions. Defines the ability of users and groups to access the folder.
♦
Allows shortcuts. Determines whether the folder is shared.
You can optionally enter a description of the folder. You can then view these comments in the Repository Manager. Warning: Do not include the period character ( . ) in folder names. Folder names with periods can cause errors when you run sessions.
Creating a Folder For information about the privileges and permissions to create a folder, see “Repository Manager Tasks” on page 373.
Configuring a Folder
99
To create a folder: 1.
In the Repository Manager, connect to the repository.
2.
Click Folder > Create.
3.
Enter the following information:
4.
100
Folder Properties
Required/ Optional
Name
Required
Folder name. Do not use the period character ( . ) in folder names. Folder names with periods can cause errors when you run sessions.
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. Groups to which the owner belongs can be selected.
Allow Shortcut
Optional
If selected, makes the folder shared.
Status
Required
Status applied to all objects in the folder. This option applies to versioned repositories. For more information about object status, see “Working with Version Properties” on page 135.
Permissions
Required
Folder permissions for users in the repository. For more information, see “Permissions” on page 96.
Click OK.
Chapter 4: Working with Folders
Description
The folder appears in the Navigator. If the folder is shared, the folder displays an open hand icon.
Editing a Folder For information about the privileges and permissions to edit a folder, see “Repository Manager Tasks” on page 373. Note: The Repository Service updates changes in folder properties immediately. To avoid
repository inconsistencies due to changes in folder properties, make sure no users are accessing the folder when you edit the folder. To edit a folder: 1.
In the Repository Manager, connect to a repository and select a folder.
2.
Click Folder > Edit.
3.
Enter the changes, and click OK.
Deleting a Folder If a folder becomes obsolete, you can delete that folder from the repository. For information about the privileges and permissions to delete a folder, see “Repository Manager Tasks” on page 373. To delete a folder: 1.
In the Repository Manager, connect to a repository and select a folder.
2.
Click Folder > Delete.
3.
In the confirmation message that appears, click OK.
Configuring a Folder
101
Comparing Folders Before you copy or replace a folder in a repository, you might want to verify the contents of a folder or compare it with other folders. The Repository Manager lets you quickly and accurately compare the objects in different folders using the Compare Folders Wizard. If you use a versioned repository, the Repository Manager uses the latest checked in version of an object for comparison. In the Compare Folders Wizard, you can complete the following comparisons: ♦
Compare objects between two folders in the same repository.
♦
Compare objects between two folders in different repositories.
You can specify the following comparison criteria for each comparison: ♦
Object types to compare. You can specify the object types to compare and display between folders. The wizard compares objects based on specific object attributes. See Table 4-2 on page 102 for a list of compared attributes for object types.
♦
Direction of comparison. The wizard performs directional comparisons. A directional comparison checks the contents of one folder against the contents of the other. You can specify either one-way or two-way comparisons.
The wizard displays the following information: ♦
Similarities between objects
♦
Differences between objects
♦
Outdated objects
You can edit and save the result of the comparison. You must have read permission for each folder you want to compare. You must also have privileges to access the repositories containing the folders. You can also compare two objects of the same type using Compare Objects. For more information about Compare Objects, see “Comparing Objects” in the Designer Guide.
Compared Attributes and Object Differentiation The Compare Folders Wizard compares objects based on specific object attributes. Table 4-2 lists the object types and attributes you can compare: Table 4-2. Compared Object Types and Attributes
102
Object Type
Compared Attribute
Sources
Source name and database name
Targets
Target name and database name
Reusable transformations
Transformation name and type
Chapter 4: Working with Folders
Table 4-2. Compared Object Types and Attributes Object Type
Compared Attribute
Mappings
Mapping name
Mapplets
Mapplet name
Source fields
Column names
Target fields
Column names
Reusable transformation fields
Port names
Sessions
Session name
Session components
Component value
Tasks
Task name
Task instances
Task instance name
Workflows
Workflow name
Workflow events
Workflow event name
Workflow variables
Workflow variable name
Worklets
Worklet name
Shortcuts
Shortcut name and object type
Transformation instances
Transformation instance name and type
Mapping variables
Mapping variable name
External procedure initialization properties
Property name
Schedulers
Scheduler name
Configurations
Configuration name
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 4-3 lists objects the wizard compares by default when you select certain objects to compare: Table 4-3. Compared Objects in Compare Selected Object
Compared Object
Source field
Source
Target field
Target
Reusable transformation field
Reusable transformation
Mapping variable
Mapping
External procedure initialization properties
Transformation instance
Session component
Session
Comparing Folders
103
Table 4-3. Compared Objects in Compare Selected Object
Compared Object
Task Instance
Workflow and worklet
Workflow event
Workflow and worklet
Workflow variable
Workflow and worklet
The wizard compares the attribute of each object in the source folder with the attribute of each object in the target folder. 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.
One-Way and Two-Way Comparisons Comparison results depend on the direction of the comparison. One-way comparisons check the selected objects of Folder1 against the objects in Folder2. Two-way comparisons check objects in Folder1 against those in Folder2 and also check objects in Folder2 against those in Folder1. A two-way comparison can sometimes reveal information a one-way comparison cannot. A one-way comparison does not note a difference if an object is present in the target folder but not in the source folder. Figure 4-1 shows two folders, ADS1 and ADS2, in the same repository. If you compare the folders using a one-way comparison, the source definition ORDER_ITEMS, present in ADS2
104
Chapter 4: Working with Folders
but not in ADS1, is not noted as a comparison. If you compare the folders using a two-way comparison, the absence of ORDER_ITEMS in ADS1 is noted as a difference. Figure 4-1. One-Way and Two-Way Comparisons
A one-way comparison does not note the presence of ORDER_ITEMS in ADS2 as a difference.
A two-way comparison notes the absence of ORDER_ITEMS in ADS1 as a difference.
Editing and Saving Results Files You can edit and save the result of a folder comparison. The Compare Folders wizard displays similar objects in green text, unmatched objects denoting a difference in red text, and outdated objects in blue text. The Compare Folders Wizard always displays the total number of differences, similarities, and outdated objects found during the comparison, even if you do not choose to display differences or similarities in the edit field. You can save the results of the comparison in the edit field to an .rtf or a .txt file. To retain the color and font attributes of the result, save it as an .rtf file. By default the results file is saved in the My Documents directory.
Steps to Compare Folders Before comparing folders, verify that you have Read permission for each folder you want to compare. Connect to the repositories containing the folders in the wizard. To compare folders: 1.
In the Repository Manager, click Folder > Compare.
2.
Click Next.
Comparing Folders
105
3.
Connect to the repositories containing the folders you want to compare and select the folders for comparison.
Connect to repository.
106
4.
Click Next.
5.
Select the object types you want to compare.
6.
Click Next.
Chapter 4: Working with Folders
7.
Select the display options.
8.
Click Next. The wizard always displays the number of differences, similarities, and outdated objects.
9.
View the results of the comparison.
Save the compare results to a file.
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.
Comparing Folders
107
108
Chapter 4: Working with Folders
Chapter 5
Local and Global Shortcuts This chapter includes the following topics: ♦
Overview, 110
♦
Shortcuts Versus Copies, 111
♦
Understanding Shortcut Properties, 112
♦
Creating a Local Shortcut, 115
♦
Creating a Global Shortcut, 119
♦
Working with Shortcuts, 123
♦
Tips, 126
♦
Troubleshooting, 127
109
Overview Shortcuts allow you to use metadata across folders without making copies. The helps to ensure uniform metadata. A shortcut inherits all properties of the object to which it points. After you create a shortcut, you can configure the shortcut name and description. When the original object 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 an object in 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:
110
♦
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.
Chapter 5: Local and Global Shortcuts
Shortcuts Versus Copies One of the primary advantages of using a shortcut is maintenance. If you need to change all instances of an object, you can edit the original repository object. All shortcuts accessing the object inherit the changes. In contrast, if you have multiple copies of an object, you need to edit each copy of the object, or recopy the object, to obtain the same results. However, some changes can invalidate mappings and sessions. For example, if you use a shortcut to a reusable transformation and then change a port datatype, you can invalidate all mappings with shortcuts to the transformation and all sessions using those mappings. Therefore, if you want the object to inherit changes immediately, create a shortcut. Otherwise, create a copy. Shortcuts have the following advantages over copied repository objects: ♦
You can maintain a common repository object in a single location. If you need to edit the object, all shortcuts immediately inherit the changes you make.
♦
You can restrict repository users to a set of predefined metadata by asking users to incorporate the shortcuts into their work instead of developing repository objects independently.
♦
You can develop complex mappings, mapplets, or reusable transformations and then reuse them easily in other folders.
♦
You can save space in the repository by keeping a single repository object and using shortcuts to that object, instead of creating copies of the object in multiple folders or multiple repositories.
For information about exporting and importing objects to makes copies, see “Exporting and Importing Objects” on page 215.
Shortcuts Versus Copies
111
Understanding Shortcut Properties When you create a shortcut to a repository object, the shortcut inherits the attributes of the object. The shortcut inherits the following properties that cannot be edited in the shortcut object: ♦
Object business name and owner name
♦
Port attributes, including datatype, precision, scale, default value, and port description
♦
Object properties (such as tracing level)
The shortcut also inherits a name and description which you can edit in the shortcut.
Default Shortcut Name The Designer names a shortcut after the original object based on the original object name as it appears in the Navigator when you create the shortcut. The Designer uses the following naming convention: Shortcut_To_DisplayedName. By default, the Designer displays all objects in the Navigator by object name. If you create a shortcut while using the default display option, the Designer names the shortcut Shortcut_To_ObjectName. Alternatively, you can enable the Designer tools to display sources and targets by business name. When you enable this option, the Designer displays sources and targets by business names if they exist. If you create a shortcut to a source or target when this option is enabled, the Designer names the shortcut Shortcut_To_BusinessName. Note: If the business name contains characters that are not allowed as in the object name, the
Designer replaces the character with an underscore (_). You can edit the default shortcut name at any time.
Describing the Object and the Shortcut Shortcuts inherit the description associated with the referenced object when you first create the shortcut. Afterwards, you can add object descriptions for each shortcut. Since the description is unique to the shortcut, if the description of the referenced object subsequently changes, shortcuts do not inherit those changes.
112
Chapter 5: Local and Global Shortcuts
Figure 5-1 shows the shortcut with a description inherited from the original object: Figure 5-1. Object and Shortcut Description
Description from the original object Description added to the shortcut
Shortcuts do not inherit edits to the description of the referenced object. However, any shortcuts created after the change contain the latest description.
Locating the Referenced Object Each shortcut tracks the location of the object it references and displays it in the transformation property sheet. The shortcut object displays the following details about the referenced object: ♦
Repository name
♦
Folder name
♦
Table or transformation name
Understanding Shortcut Properties
113
Figure 5-2 shows the transformation property sheet with the referenced shortcut objects: Figure 5-2. Referenced Shortcut Object
Original Object Location
Note: If you move or delete an object referenced by a shortcut, the shortcut becomes invalid.
114
Chapter 5: Local and Global Shortcuts
Creating a Local Shortcut You can reuse metadata within a single repository by creating a local shortcut. You can create a local shortcut to objects in a shared folder in the same repository. If an object is in a nonshared folder, you can make a copy of the object. You can create a local shortcut in any folder in the repository. After you create a local shortcut, you can reuse it within the same folder. After you create a shortcut, it appears in the Navigator as an available repository object with the shortcut icon. When you drag the resulting shortcut into the workspace, the same shortcut icon appears. The Designer names shortcuts after the original object by default, Shortcut_To_ObjectName. For example, when you create a shortcut to the DetectChanges reusable Expression transformation, the shortcut, named Shortcut_To_DetectChanges appears in the Transformations node of the folder. When you drag it into the workspace, the shortcut icon indicates the transformation is a shortcut.
Creating a Local Shortcut
115
Figure 5-3 shows shortcut icons in the Navigator and Workspace windows: Figure 5-3. Flat File Source Shortcut Icon
Shared Folder
Original Object
Shortcut
Shortcut Icon
Note: When you drag an object from a shared folder to a business component directory, the
Designer creates a shortcut if the object does not already exist in the destination folder. For more information, see “Managing Business Components” in the Designer Guide. To create a local shortcut, you must have one of the following sets of privileges and permissions for the shared folder containing the original object:
116
♦
Use Designer privilege with read permission on the folder
♦
Super User privilege
Chapter 5: Local and Global Shortcuts
You must have the one of the following sets of privileges and permissions on the destination folder: ♦
Use Designer privilege with read and write permission on the folder
♦
Super User privilege
You can create a local shortcut in the Navigator or in the workspace. To create a local shortcut in the Navigator: 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
Informatica PowerCenter® (Version 8.1.1)
Informatica PowerCenter Repository Guide Version 8.1.1 September 2006 Copyright (c) 1998–2006 Informatica Corporation. All rights reserved. Printed in the USA. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are 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 and 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. Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerMart, SuperGlue, Metadata Manager, Informatica Data Quality and Informatica Data Explorer are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies, 1999-2002. All rights reserved. Copyright © Sun Microsystems. All Rights Reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All Rights Reserved. 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-2005 The Apache Software Foundation. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit and redistribution of this software is subject to terms available at http://www.openssl.org. Copyright 1998-2003 The OpenSSL Project. All Rights Reserved. The zlib library included with this software is Copyright (c) 1995-2003 Jean-loup Gailly and Mark Adler. The Curl license provided with this Software is Copyright 1996-2004, Daniel Stenberg,
Table of Contents List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . .xxiii Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . .xxiii Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . .xxiii Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiii
Chapter 1: Understanding the Repository . . . . . . . . . . . . . . . . . . . . . . 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Repository Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Repository Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Understanding Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Objects Created in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Objects Created in the Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . 7 Objects Created in the Repository Manager . . . . . . . . . . . . . . . . . . . . . . 7 Global Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Modifying Dependent Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Administering Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 PowerCenter Repository Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Reusing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Reusing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
iii
Chapter 2: Using the Repository Manager . . . . . . . . . . . . . . . . . . . . . 17 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Repository Manager Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Repository Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Understanding the Repository Manager Windows . . . . . . . . . . . . . . . . . . . . 20 Displaying Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Navigator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Using Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Configuring Repository Manager Options . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Connecting to Domains and Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Configuring a Domain Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Adding a Repository to the Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Connecting to a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Reconnecting to a Repository and Canceling Auto-Reconnect . . . . . . . . 33 Managing Domain and Repository Connections . . . . . . . . . . . . . . . . . . . . . 35 Editing a Domain Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Removing a Domain Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Connecting to Multiple Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Exporting and Importing Repository Connection Information . . . . . . . . 37 Removing a Repository from the Navigator . . . . . . . . . . . . . . . . . . . . . . 37 Searching for Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Performing Keyword Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Searching All Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Validating Multiple Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Comparing Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Truncating Workflow and Session Log Entries . . . . . . . . . . . . . . . . . . . . . . . 53 Managing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Understanding Repository Object Locks . . . . . . . . . . . . . . . . . . . . . . . . 55 Viewing User Connections and Locks . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Closing User Connections and Releasing Locks . . . . . . . . . . . . . . . . . . . 60
Chapter 3: Managing Users and Groups . . . . . . . . . . . . . . . . . . . . . . 63 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 iv
Table of Contents
User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Default Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Owner’s Group Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Creating a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Editing a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Deleting a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Using Default Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Using LDAP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Creating and Editing Repository Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Creating a User Under Default Authentication . . . . . . . . . . . . . . . . . . . 71 Editing a User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Creating a Repository User Under an External Directory Service . . . . . . 74 Editing a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Enabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Disabling a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Removing a Repository User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Default Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Extended Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Assigning and Revoking a Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring Permissions on Global Objects . . . . . . . . . . . . . . . . . . . . . 86 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 4: Working with Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Using Folders in the Repository Manager . . . . . . . . . . . . . . . . . . . . . . . 94 Using Folders in the Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Using Folders in the Workflow Manager . . . . . . . . . . . . . . . . . . . . . . . . 94 Organizing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Folder Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Folder Owner and Owner's Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Shared Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table of Contents
v
Configuring a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Editing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Deleting a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Comparing Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Compared Attributes and Object Differentiation . . . . . . . . . . . . . . . . . 102 One-Way and Two-Way Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . 104 Editing and Saving Results Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Steps to Compare Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Chapter 5: Local and Global Shortcuts . . . . . . . . . . . . . . . . . . . . . . 109 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Shortcuts Versus Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Understanding Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Default Shortcut Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Describing the Object and the Shortcut . . . . . . . . . . . . . . . . . . . . . . . 112 Locating the Referenced Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Creating a Local Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Creating a Global Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Configuring the Global Shortcut Environment . . . . . . . . . . . . . . . . . . 121 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Refreshing Shortcut Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Copying a Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Renaming Source Qualifiers to Shortcut Sources . . . . . . . . . . . . . . . . . 125 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Chapter 6: Working with Versioned Objects . . . . . . . . . . . . . . . . . . 129 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Sample Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Viewing Results View Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Customizing Results View Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Working with Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Viewing Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Version Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Labels Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
vi
Table of Contents
Object Status Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Changing Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Changing Folder Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Tracking Changes to Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Viewing Object History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Comparing Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Checking Out and Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Checking Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Viewing Checked-Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Undoing a Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Checking In Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Checking Out and Checking In Composite Objects . . . . . . . . . . . . . . 147 Working with Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Creating and Editing Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Applying Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Working with Deployment Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Creating a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Editing a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Viewing the Objects in a Deployment Group . . . . . . . . . . . . . . . . . . . 158 Adding or Removing Objects in Static Deployment Groups . . . . . . . . . 158 Using Queries in Dynamic Deployment Groups . . . . . . . . . . . . . . . . . 159 Viewing Deployment History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Rolling Back a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Deleting and Recovering Versioned Objects . . . . . . . . . . . . . . . . . . . . . . . 163 Deleting a Versioned Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Recovering a Deleted Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Purging Versions of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Purging Individual Object Versions . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Purging Versions Based on Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Purging Composite Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Rules and Guidelines for Purging Versions of Objects . . . . . . . . . . . . . 171
Chapter 7: Working with Object Queries . . . . . . . . . . . . . . . . . . . . . 173 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Using the Query Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Configuring Query Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Query Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Table of Contents
vii
Validating and Saving a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Running a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Viewing Query Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Sample Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Finding Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Finding Impacted Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Finding Invalid Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Finding the Used Status of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Finding Recently Deployed Versioned Objects . . . . . . . . . . . . . . . . . . . 188 Finding Recently Checked-Out Objects . . . . . . . . . . . . . . . . . . . . . . . 188 Finding Older Versions of Versioned Objects . . . . . . . . . . . . . . . . . . . . 188 Finding Versioned Objects Older than a Specified Date . . . . . . . . . . . . 189 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Chapter 8: Copying Folders and Deployment Groups . . . . . . . . . . . 191 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Copying or Replacing Running Workflows, Sessions, and Tasks . . . . . . 192 Using the Copy Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Copy Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Associated Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Copying Plug-in Application Information . . . . . . . . . . . . . . . . . . . . . . 196 Copying or Replacing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Copying Within a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Copying Folders Between Versioned and Non-Versioned Repositories . . 201 Copying from Local Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Steps to Copy or Replace a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Copying a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Locking and Checkouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Copying Composite Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Copying Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Object Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Object Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
viii
Table of Contents
Steps to Copy a Deployment Group . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Chapter 9: Exporting and Importing Objects . . . . . . . . . . . . . . . . . . 215 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Working with Objects and Object Types . . . . . . . . . . . . . . . . . . . . . . . 217 Working with Different Repository Versions . . . . . . . . . . . . . . . . . . . . 217 Permissions and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 The XML and DTD Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 CRCVALUE Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Exporting and Importing Multiple Objects and Object Types . . . . . . . . . . 221 Working with Dependent Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Exporting and Importing Parent Objects . . . . . . . . . . . . . . . . . . . . . . 223 Working with Object Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Working with Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Shortcut Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Importing Shortcuts to Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Modifying an Exported XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Modifiable Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Validating XML Files Against the DTD . . . . . . . . . . . . . . . . . . . . . . . 233 Validating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Resolving Object Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Steps to Export Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Steps to Import Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Chapter 10: Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Code Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Copy Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Resolving Copy Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Steps to Copy Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Copying Workflow Manager Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Table of Contents
ix
Copying Workflows and Worklets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Copying Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Copying Workflow Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Copying Designer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Copying Mapping and Mapplets Segments . . . . . . . . . . . . . . . . . . . . . 265
Chapter 11: Exchanging Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Working with Column Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Working with Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Working with Star Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Steps to Export Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Steps to Import Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Exchanging Metadata with Business Objects Designer . . . . . . . . . . . . . . . . 281 Metadata and Datatype Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Exporting Metadata to Business Objects Designer . . . . . . . . . . . . . . . . 282 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Chapter 12: Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Working with Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Creating Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Editing Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Deleting Reusable Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Chapter 13: Using Metadata Exchange (MX) Views . . . . . . . . . . . . . 295 Viewing the Repository Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 MX View Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Using PowerCenter Repository Reports . . . . . . . . . . . . . . . . . . . . . . . . 297 SQL Definition of Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Integrating MX Views with Third-Party Software . . . . . . . . . . . . . . . . 299 Database Definition View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 REP_DATABASE_DEFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Source Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 REP_ALL_SOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 REP_ALL_SOURCE_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 x
Table of Contents
REP_SRC_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 REP_SRC_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 REP_SRC_FILE_FLDS and REP_SEG_FLDS . . . . . . . . . . . . . . . . . . 307 REP_SRC_TBL_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Target Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 REP_ALL_TARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 REP_ALL_TARGET_FLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 REP_TARG_TBLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 REP_TARG_TBL_COLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Mapping and Mapplet Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 REP_ALL_MAPPINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 REP_ALL_MAPPLETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 REP_TARG_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 REP_TARG_FLD_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 REP_FLD_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 REP_SRC_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 REP_SRC_FLD_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 REP_TBL_MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 REP_TARG_TBL_JOINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 REP_MAPPING_CONN_PORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 REP_MAPPING_UNCONN_PORTS . . . . . . . . . . . . . . . . . . . . . . . . 325 Metadata Extension Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 REP_METADATA_EXTNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 REP_METADATA_EXTN_DEFINES . . . . . . . . . . . . . . . . . . . . . . . . 328 Transformation Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 REP_ALL_TRANSFORMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 REP_WIDGET_INST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 REP_WIDGET_DEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 REP_WIDGET_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 REP_WIDGET_FIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Workflow, Worklet, and Task Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 REP_WORKFLOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 REP_ALL_TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 REP_ALL_SCHEDULERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 REP_WFLOW_VAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 REP_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 REP_TASK_INST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 REP_WORKFLOW_DEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Table of Contents
xi
REP_TASK_INST_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 REP_WFLOW_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 REP_LOAD_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 REP_SESSION_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 REP_SESSION_INSTANCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 REP_SESSION_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 REP_SESSION_INST_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 REP_SESS_WIDGET_CNXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 REP_COMPONENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 REP_SESS_PARTITION_DEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 REP_SESS_CONFIG_PARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 REP_TASK_ATTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 REP_SESS_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 REP_SESS_TBL_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Security Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 REP_USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 REP_USER_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 REP_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Deployment Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 REP_DEPLOY_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 REP_DEPLOY_GROUP_DETAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Repository View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 REP_REPOSIT_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Integration Service Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 REP_SERVER_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 REP_SERVER_NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 REP_SERVER_NET_REF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Change Management Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 REP_VERSION_PROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 REP_LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 REP_LABEL_REF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Folder View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 REP_SUBJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Appendix A: Permissions and Privileges by Task . . . . . . . . . . . . . . 367 Designer Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Workflow Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
xii
Table of Contents
Workflow Monitor Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 pmcmd Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Repository Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 pmrep Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Table of Contents
xiii
xiv
Table of Contents
List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure
1-1. PowerCenter Repository Connectivity . . . . . . . . . . 1-2. Invalid and Impacted Objects . . . . . . . . . . . . . . . . 2-1. Repository Manager Components . . . . . . . . . . . . . 2-2. Repository Manager Navigator . . . . . . . . . . . . . . . 2-3. Source Definition Object Properties . . . . . . . . . . . 2-4. Dependency Window . . . . . . . . . . . . . . . . . . . . . . 2-5. Output Window . . . . . . . . . . . . . . . . . . . . . . . . . 2-6. Options Dialog Box of the Repository Manager . . . 2-7. Dependencies Dialog Box . . . . . . . . . . . . . . . . . . . 2-8. View Dependencies Window . . . . . . . . . . . . . . . . 2-9. Object Dependencies Saved as HTML . . . . . . . . . 2-10. Validate Objects Results . . . . . . . . . . . . . . . . . . . 3-1. Repository User Names and External Login Names 4-1. One-Way and Two-Way Comparisons . . . . . . . . . 5-1. Object and Shortcut Description . . . . . . . . . . . . . 5-2. Referenced Shortcut Object . . . . . . . . . . . . . . . . . 5-3. Flat File Source Shortcut Icon . . . . . . . . . . . . . . . 5-4. Create a Global Shortcut . . . . . . . . . . . . . . . . . . . 6-1. List of Results View Windows . . . . . . . . . . . . . . . 6-2. Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . 6-3. Version Properties . . . . . . . . . . . . . . . . . . . . . . . . 6-4. Labels Properties . . . . . . . . . . . . . . . . . . . . . . . . . 6-5. Object Status Properties . . . . . . . . . . . . . . . . . . . . 6-6. View History Window . . . . . . . . . . . . . . . . . . . . . 6-7. Label Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8. Label Editor Options . . . . . . . . . . . . . . . . . . . . . . 6-9. Apply Label Dialog Box . . . . . . . . . . . . . . . . . . . . 6-10. Apply Label Wizard . . . . . . . . . . . . . . . . . . . . . . 6-11. Deployment Groups Node in the Navigator . . . . . 6-12. Dependency for Deployment Group Dialog Box . 6-13. Advanced Purge Window . . . . . . . . . . . . . . . . . . 6-14. Preview Window - Summary . . . . . . . . . . . . . . . . 6-15. Preview Window - Detail . . . . . . . . . . . . . . . . . . 6-16. Version History of Mapping m_Payroll . . . . . . . . 6-17. Version History of Mapping m_PhoneList . . . . . . 7-1. Query Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2. Query Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3. Query with Multiple Conditions . . . . . . . . . . . . . . 7-4. Sample Query Results . . . . . . . . . . . . . . . . . . . . . 9-1. CRCVALUE Code in an Exported XML File . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. 4 .. 9 . 20 . 22 . 23 . 25 . 26 . 28 . 44 . 45 . 46 . 48 . 69 105 113 114 116 119 133 136 136 137 138 141 150 150 151 153 157 159 167 169 169 170 171 175 175 177 185 220
List of Figures
xv
Figure Figure Figure Figure Figure Figure Figure
xvi
9-2. Export Options Dialog Box . . . . . . . . . . . . . . . . 9-3. Import Wizard - Resolve General Object Conflicts 9-4. Import Wizard - Resolve Specific Object Conflicts 9-5. Conflict Resolution Wizard . . . . . . . . . . . . . . . . 10-1. The Copy Wizard . . . . . . . . . . . . . . . . . . . . . . 10-2. Copy Wizard Resolutions . . . . . . . . . . . . . . . . . 10-3. Copy Wizard Mapping Conflicts . . . . . . . . . . .
List of Figures
.. . . .. .. .. ..
.. .. .. .. .. .. ..
. . . . . . .
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
.. .. .. .. .. .. ..
. . . . . . .
.223 .235 .236 .237 .253 .256 .258
List of Tables Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
1-1. Object Validation States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2. Repository Administration Tasks by Tool . . . . . . . . . . . . . . . . . . . . 2-1. Object Details Displayed in Main Window of Repository Manager . . 2-2. General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3. Viewing Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4. Dependencies Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5. Object Properties in View Dependencies Window . . . . . . . . . . . . . . 2-6. Validate Objects Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7. Repository Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8. Repository User Connection Details . . . . . . . . . . . . . . . . . . . . . . . . 2-9. Object Lock Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1. User Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2. Default Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3. Extended Repository Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4. Folder Object Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5. Global Object Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1. Folder Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2. Compared Object Types and Attributes . . . . . . . . . . . . . . . . . . . . . . 4-3. Compared Objects in Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1. Copying Global or Local Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . 6-1. Tasks Available in View History Window . . . . . . . . . . . . . . . . . . . . 6-2. Tasks Available in View Checkouts Window . . . . . . . . . . . . . . . . . . 6-3. Label Options and Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4. Methods of Purging Object Versions . . . . . . . . . . . . . . . . . . . . . . . . 6-5. Advanced Purge Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1. Query Parameters and Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2. Tasks Available in Query Results Window . . . . . . . . . . . . . . . . . . . . 8-1. Copy Folder Wizard Prompts (Copying a Folder) . . . . . . . . . . . . . . 8-2. Change in Object Status After Copying Deployment Group Objects . 8-3. Copy Deployment Group Wizard Prompts . . . . . . . . . . . . . . . . . . . 9-1. Exporting and Importing Objects Permissions and Privileges . . . . . . 9-2. Options for Exporting and Importing Multiple Objects . . . . . . . . . . 9-3. Dependent Objects Exported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4. Options for Exporting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5. Modifiable Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6. Resolving General Conflicts During Import. . . . . . . . . . . . . . . . . . . 10-1. Copy Wizard Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2. Copy Wizard Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1. Dimensional Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . 11-2. Metadata Import Wizard - PowerCenter Options . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. 9 . 11 . 24 . 28 . 42 . 44 . 45 . 48 . 56 . 58 . 59 . 70 . 80 . 82 . 85 . 86 . 97 102 103 124 141 146 152 165 167 178 185 202 209 210 218 221 222 223 230 235 253 255 272 278
List of Tables
xvii
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
xviii
11-3. PowerCenter to Business Objects Designer Metadata Conversion 11-4. PowerCenter to Business Objects Datatype Conversion . . . . . . . 11-5. Business Objects Designer Metadata Export Options . . . . . . . . . 12-1. Options for Creating Reusable Metadata Extensions . . . . . . . . . 13-1. MX View Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2. SQL Script to Create MX Views . . . . . . . . . . . . . . . . . . . . . . . . 13-3. SQL Script to Drop MX Views . . . . . . . . . . . . . . . . . . . . . . . . . 13-4. REP_DATABASE_DEFS MX View . . . . . . . . . . . . . . . . . . . . . 13-5. Source Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6. REP_ALL_SOURCES MX View . . . . . . . . . . . . . . . . . . . . . . . . 13-7. REP_ALL_SOURCE_FLDS MX View . . . . . . . . . . . . . . . . . . . 13-8. REP_SRC_FILES MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9. REP_SRC_TBLS MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10. REP_SRC_FILE_FLDS and REP_SEG_FLDS MX Views . . . . 13-11. REP_SRC_TBL_FLDS MX Views . . . . . . . . . . . . . . . . . . . . . 13-12. Target Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13. REP_ALL_TARGETS MX View . . . . . . . . . . . . . . . . . . . . . . . 13-14. REP_ALL_TARGET_FLDS MX View . . . . . . . . . . . . . . . . . . 13-15. REP_TARG_TBLS MX View . . . . . . . . . . . . . . . . . . . . . . . . . 13-16. REP_TARG_TBL_COLS MX View . . . . . . . . . . . . . . . . . . . . 13-17. Mapping and Mapplet Views . . . . . . . . . . . . . . . . . . . . . . . . . 13-18. REP_ALL_MAPPINGS MX View . . . . . . . . . . . . . . . . . . . . . . 13-19. REP_ALL_MAPPLETS MX View . . . . . . . . . . . . . . . . . . . . . . 13-20. REP_TARG_MAPPING MX View . . . . . . . . . . . . . . . . . . . . . 13-21. REP_TARG_FLD_MAP MX View . . . . . . . . . . . . . . . . . . . . . 13-22. REP_FLD_MAPPING MX View . . . . . . . . . . . . . . . . . . . . . . 13-23. REP_SRC_MAPPING MX View . . . . . . . . . . . . . . . . . . . . . . 13-24. Mapping Source Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25. REP_TBL_MAPPING MX View . . . . . . . . . . . . . . . . . . . . . . 13-26. REP_TARG_TBL_JOINS MX View . . . . . . . . . . . . . . . . . . . . 13-27. REP_MAPPING_CONN_PORTS MX View . . . . . . . . . . . . . 13-28. REP_MAPPING_UNCONN_PORTS MX View . . . . . . . . . . . 13-29. Metadata Extension Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-30. REP_METADATA_EXTNS MX View . . . . . . . . . . . . . . . . . . 13-31. REP_METADATA_EXTN_DEFINES MX View . . . . . . . . . . . 13-32. Transformation Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33. REP_ALL_TRANSFORMS MX View . . . . . . . . . . . . . . . . . . . 13-34. REP_WIDGET_INST MX View . . . . . . . . . . . . . . . . . . . . . . 13-35. REP_WIDGET_DEP MX View . . . . . . . . . . . . . . . . . . . . . . . 13-36. REP_WIDGET_ATTR MX View . . . . . . . . . . . . . . . . . . . . . . 13-37. REP_WIDGET_FIELD MX View . . . . . . . . . . . . . . . . . . . . . 13-38. Workflow, Worklet, and Task Views . . . . . . . . . . . . . . . . . . . . 13-39. REP_WORKFLOWS MX View . . . . . . . . . . . . . . . . . . . . . . .
List of Tables
............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............
.282 .282 .283 .291 .296 .298 .298 .300 .301 .301 .303 .305 .306 .307 .308 .309 .309 .311 .313 .313 .315 .316 .317 .318 .319 .320 .321 .322 .323 .324 .325 .326 .327 .327 .328 .329 .329 .331 .331 .332 .332 .334 .335
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
13-40. REP_ALL_TASKS MX View . . . . . . . . . . . . . . . . . . . . . . . . . . 13-41. REP_ALL_SCHEDULERS MX View . . . . . . . . . . . . . . . . . . . . 13-42. REP_WFLOW_VAR MX View . . . . . . . . . . . . . . . . . . . . . . . . . 13-43. REP_EVENT MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44. REP_TASK_INST MX View . . . . . . . . . . . . . . . . . . . . . . . . . . 13-45. REP_WORKFLOW_DEP MX View . . . . . . . . . . . . . . . . . . . . . 13-46. REP_TASK_INST_RUN MX View . . . . . . . . . . . . . . . . . . . . . 13-47. REP_WFLOW_RUN MX View . . . . . . . . . . . . . . . . . . . . . . . . 13-48. REP_LOAD_SESSIONS MX View . . . . . . . . . . . . . . . . . . . . . . 13-49. REP_SESSION_CNXS MX View . . . . . . . . . . . . . . . . . . . . . . . 13-50. REP_SESSION_INSTANCES MX View . . . . . . . . . . . . . . . . . . 13-51. REP_SESSION_FILES MX View . . . . . . . . . . . . . . . . . . . . . . . 13-52. REP_SESSION_INST_FILES MX View . . . . . . . . . . . . . . . . . . 13-53. REP_SESS_WIDGET_CNXS MX View . . . . . . . . . . . . . . . . . . 13-54. REP_COMPONENT MX View . . . . . . . . . . . . . . . . . . . . . . . . 13-55. REP_SESS_PARTITION_DEF MX View . . . . . . . . . . . . . . . . . 13-56. REP_SESS_CONFIG_PARM MX View . . . . . . . . . . . . . . . . . . 13-57. REP_TASK_ATTR MX View . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58. REP_SESS_LOG MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-59. REP_SESS_TBL_LOG MX View . . . . . . . . . . . . . . . . . . . . . . . 13-60. Security Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-61. REP_USERS MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-62. REP_USER_GROUPS MX View . . . . . . . . . . . . . . . . . . . . . . . 13-63. REP_GROUPS MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-64. Deployment Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-65. REP_DEPLOY_GROUP MX View . . . . . . . . . . . . . . . . . . . . . . 13-66. REP_DEPLOY_GROUP_DETAIL MX View . . . . . . . . . . . . . . 13-67. REP_REPOSIT_INFO MX View . . . . . . . . . . . . . . . . . . . . . . . 13-68. Integration Service Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69. REP_SERVER_INFO MX View . . . . . . . . . . . . . . . . . . . . . . . . 13-70. REP_SERVER_NET MX View . . . . . . . . . . . . . . . . . . . . . . . . . 13-71. REP_SERVER_NET_REF MX View. . . . . . . . . . . . . . . . . . . . . 13-72. Change Management Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73. REP_VERSION_PROPS MX View . . . . . . . . . . . . . . . . . . . . . . 13-74. REP_LABEL MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75. REP_LABEL_REF MX View . . . . . . . . . . . . . . . . . . . . . . . . . . 13-76. REP_SUBJECT MX View . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1. Required Privileges and Permissions for Designer Tasks . . . . . . . . . A-2. Required Privileges and Permissions for Workflow Manager Tasks . A-3. Required Privileges and Permissions for Workflow Monitor Tasks . A-4. Required Privileges and Permissions for pmcmd Tasks . . . . . . . . . . A-5. Required Permissions and Privileges for Repository Manager Tasks A-6. Required Permissions and Privileges for pmrep Tasks. . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
337 338 339 340 340 341 341 343 344 345 346 346 347 348 348 349 350 350 351 353 355 355 356 356 357 357 358 360 361 361 362 362 363 363 364 364 366 368 369 371 372 373 376
List of Tables
xix
xx
List of Tables
Preface
Welcome to PowerCenter, the Informatica software product that delivers an open, scalable data integration solution addressing the complete life cycle for all data integration projects including data warehouses, 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 repository coordinates and drives a variety of core functions, including extracting, transforming, loading, and managing data. The Integration Service 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 building a comprehensive data warehouse from disparate data sources.
xxi
About This Book The Repository Guide is written for database administrators and developers who manage 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 also available online.
Document Conventions This guide uses the following formatting conventions:
xxii
Preface
If you see…
It means…
italicized text
The word or set of words are especially emphasized.
boldfaced text
Emphasized subjects.
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.
Note:
The following paragraph provides additional facts.
Tip:
The following paragraph provides suggested uses.
Warning:
The following paragraph notes situations where you can overwrite or corrupt data, unless you follow the specified procedure.
monospaced text
This is a code example.
bold monospaced text
This is an operating system command you enter from a prompt to run a task.
Other Informatica Resources In addition to the product manuals, Informatica provides these other resources: ♦
Informatica Customer Portal
♦
Informatica web site
♦
Informatica Developer Network
♦
Informatica Knowledge Base
♦
Informatica Technical Support
Visiting Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.
Visiting the Informatica Web Site You can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.
Visiting the Informatica Developer Network You can access the Informatica Developer Network at http://devnet.informatica.com. The Informatica Developer Network is a web-based forum for third-party software developers. The site contains information about how to create, market, and support customer-oriented add-on solutions based on interoperability interfaces for Informatica products.
Visiting the Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips.
Obtaining Technical Support There are many ways to access Informatica Technical Support. You can contact a Technical Support Center by using the telephone numbers listed the following table, you can send email, or you can use the WebSupport Service. Preface
xxiii
Use the following email addresses to contact Informatica Technical Support: ♦
[email protected] for technical inquiries
♦
[email protected] for general customer service requests
WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.
xxiv
Preface
North America / South America
Europe / Middle East / Africa
Asia / Australia
Informatica Corporation Headquarters 100 Cardinal Way Redwood City, California 94063 United States
Informatica Software Ltd. 6 Waltham Park Waltham Road, White Waltham Maidenhead, Berkshire SL6 3TN United Kingdom
Informatica Business Solutions Pvt. Ltd. Diamond District Tower B, 3rd Floor 150 Airport Road Bangalore 560 008 India
Toll Free 877 463 2435
Toll Free 00 800 4632 4357
Toll Free Australia: 00 11 800 4632 4357 Singapore: 001 800 4632 4357
Standard Rate United States: 650 385 5800
Standard Rate Belgium: +32 15 281 702 France: +33 1 41 38 92 26 Germany: +49 1805 702 702 Netherlands: +31 306 022 797 United Kingdom: +44 1628 511 445
Standard Rate India: +91 80 4112 5738
Chapter 1
Understanding the Repository This chapter includes the following topics: ♦
Overview, 2
♦
Repository Architecture, 3
♦
Repository Connectivity, 4
♦
Understanding Metadata, 6
♦
Administering Repositories, 11
♦
PowerCenter Repository Domains, 13
♦
Version Control, 15
1
Overview The PowerCenter repository is a relational database managed by the Repository Service. The repository consists of database tables that store metadata. Metadata describes different types of objects, such as mappings and transformations, that you can create or modify using the PowerCenter Client tools. The Integration Service 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 Service. The Repository Service protects metadata in the repository by managing repository connections and using object-locking to ensure object consistency. The Repository Service also notifies you when another user modifies or deletes repository objects you are using. Each Repository Service manages a single repository database. You can configure a Repository Service to run on multiple machines, or nodes, in the domain. Each instance running on a node is called a Repository Service process. This process accesses the database tables and performs most repository-related tasks. The Repository Service uses native drivers to communicate with the repository database. PowerCenter Client tools and the Integration Service communicate with the Repository Service over TCP/IP. When a client application connects to the repository, it connects directly to the Repository Service process. You administer the repository using the Repository Manager client tool, the PowerCenter Administration Console, and the pmrep and infacmd command line programs. You can connect to and manage multiple repositories. A repository domain is a group of repositories that you can connect to simultaneously in the PowerCenter Client. They share metadata through a special type of repository called a global repository. When you configure shared folders in a repository, you can share the objects in the folder with other repositories in the repository domain. You share objects to reuse metadata. Note: A repository domain is different from a PowerCenter domain, which is the primary unit
of administration for the PowerCenter environment. For more information about repository domains, see “PowerCenter Repository Domains” on page 13. For more information about PowerCenter domains, see “Understanding Domains” in the Administrator Guide. If you have the team-based development option, you can enable the repository for version control. You can store multiple versions of objects in a versioned repository. You can also perform change-management tasks such as version comparison, change tracking, labeling, and deployment.
2
Chapter 1: Understanding the Repository
Repository Architecture The PowerCenter repository resides in a relational database. The repository database tables contain the instructions required to extract, transform, and load data. Repository client applications access the repository database tables through the Repository Service. The Repository Service manages repository metadata transaction requests from client applications. Each Repository Service manages a single repository. The Repository Service uses object-locking to ensure the consistency of metadata in the repository. A Repository Service process is a multi-threaded process that fetches, inserts, and updates metadata in the repository database tables. A Repository Service process is an instance of the Repository Service that runs on a particular machine, or node. The Repository Service accepts client metadata transaction requests from the following PowerCenter applications: ♦
PowerCenter Client tools. Use the Designer to create and store mapping metadata in the repository. Use the Workflow Manager to store workflow metadata and connection object information in the repository. Use the Workflow Monitor to retrieve workflow run status information and session logs written by the Integration Service. Use the Repository Manager to organize and secure metadata by creating folders, users, and groups. You can manage Repository Services and repository database connections and content from the PowerCenter Administration Console.
♦
pmrep and infacmd. Use pmrep to perform repository metadata administration tasks, such as listing repository objects or creating and editing users and groups. Use infacmd to perform service-related functions, such as creating or removing a Repository Service.
♦
Integration Service. When you start the Integration Service, it connects to the repository to schedule workflows. When you run a workflow, the Integration Service retrieves workflow task and mapping metadata from the repository. During the workflow run, the Integration Service writes workflow status information to the repository.
♦
Other Repository Services. Use multiple Repository Services to manage repositories in a repository domain. The Repository Service managing a local repository communicates as a client application with the Repository Service managing the global repository.
Repository Architecture
3
Repository Connectivity PowerCenter applications such as the PowerCenter Client, the Integration Service, pmrep, and infacmd connect to the repository through the Repository Service. PowerCenter applications communicate with the Repository Service through a specified port over a TCP/IP connection. You configure the TCP/IP port number when you install the Repository Service. Because PowerCenter services can reside on multiple nodes in the domain, the Repository Service relies on another service called the Service Manager to direct client requests to the appropriate Repository Service process. Figure 1-1 shows the path of a request when you use a repository client application, such as the Repository Manager or the Integration Service, to update the repository database. Figure 1-1. PowerCenter Repository Connectivity Repository Client Application
1 Node A
Node B (Gateway)
Service Manager
Service Manager
2
3
Application Services Repository Service
Application Services
4
Repository Database
The following process describes how a repository client application connects to the repository database:
4
1.
The repository client application sends a repository connection request to the master gateway node, which is the entry point to the domain. This is node B in the diagram.
2.
The Service Manager sends back the host name and port number of the node running the Repository Service. In the diagram, the Repository Service is running on node A. If you
Chapter 1: Understanding the Repository
have the high availability option, you can configure the Repository Service to run on a backup node. 3.
The repository client application establishes a link with the Repository Service process on node A. This communication occurs over TCP/IP.
4.
The Repository Service process communicates with the repository database and performs repository metadata transactions for the client application. This communication typically occurs over TCP/IP. It may use other protocols, depending on the database driver.
Repository Connectivity
5
Understanding Metadata The repository stores metadata that describes how to extract, transform, and load source and target data. PowerCenter metadata describes several different kinds of repository objects. You use different PowerCenter Client tools to develop each kind of object. If you enable version control, you can store multiple versions of metadata objects in the repository. For more information about version control and change management, see “Version Control” on page 15. You can also extend the metadata stored in the repository by associating information with repository objects. For example, when someone in your organization creates a source definition, you may want to store the name of that person with the source definition. You associate information with repository metadata using metadata extensions. For more information about using metadata extensions, see “Metadata Extensions” on page 287.
Objects Created in the Designer Use the Designer to create and edit the following repository objects:
6
♦
Source definitions. Detailed descriptions of database objects (tables, views, and synonyms), flat files, XML files, or COBOL files that provide source data. For example, a source definition might be the complete structure of the EMPLOYEES table, including the table name, column names and datatypes, and any constraints applied to these columns, such as NOT NULL or PRIMARY KEY. Use the Source Analyzer tool in the Designer to import and create source definitions.
♦
Target definitions. Detailed descriptions for database objects, flat files, or XML files to receive transformed data. During a session, the Integration Service writes the transformed data to targets. Use the Target Designer tool in the Designer to import or create target definitions.
♦
Transformations. A transformation generates, modifies, or passes data through ports that you connect in a mapping or mapplet. When you build a mapping or mapplet, you add transformations and configure them to handle data according to your business purpose.
♦
Reusable transformations. You can design a transformation that you can reuse in multiple mappings or mapplets within a folder, a repository, or a repository domain. Rather than recreate the same transformation each time, you can make the transformation reusable and add instances of the transformation to individual mappings or mapplets. Use the Transformation Developer tool in the Designer to create reusable transformations.
♦
Mappings. A mapping specifies how to move and transform data from sources to targets. Mappings include source and target definitions and transformations. Transformations describe how the Integration Service transforms data. Mappings can also include shortcuts, reusable transformations, and mapplets. Use the Mapping Designer tool in the Designer to create mappings.
♦
Mapplets. You can design a mapplet to contain sets of transformation logic to be reused in multiple mappings within a folder, a repository, or a repository domain. Rather than recreate the same set of transformations each time, you can create a mapplet containing the
Chapter 1: Understanding the Repository
transformations and then add instances of the mapplet to individual mappings. Use the Mapplet Designer tool in the Designer to create mapplets. ♦
Multi-dimensional metadata. Multi-dimensional metadata refers to the logical organization of data used for analysis in OLAP applications. Dimensions and cubes are most often used by end users of OLAP applications. Use the Target Designer tool to create dimensions and cubes.
You can also create shortcuts to metadata in shared folders. Use shortcuts to repository objects in shared folders. You can create local shortcuts to shared folders within the same repository and global shortcuts to shared folders in the global repository of the repository domain. Use the Designer to create shortcuts. For more information about using the Designer to work with repository objects, see the Designer Guide and the Transformation Guide.
Objects Created in the Workflow Manager Use the Workflow Manager to create and edit the following repository objects: ♦
Database connections. The Integration Service uses database connections to connect to the source and target databases.
♦
Sessions. Sessions are workflow tasks that contain information about how the Integration Service 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 Integration Service uses to extract, transform, and load data.
♦
Workflow tasks. Workflow tasks are instructions the Integration Service 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 more information about working with repository objects using the Workflow Manager, see the Workflow Administration Guide.
Objects Created in the Repository Manager 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. Understanding Metadata
7
♦
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.
Global Objects Most objects exist within folders in the repository. You can create global objects at the repository level. While the scope of most objects is within their folders, the scope of a global object is the entire repository. When you edit a global object, the Repository Service applies the changes at the repository level. You use different PowerCenter Client tools to develop each kind of global object. You can create the following global objects: ♦
Labels. You can associate labels with any versioned object or group of versioned objects in a repository. 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. Use the Repository Manager to create and edit labels.
♦
Deployment groups. A deployment group is a set of versioned objects that you deploy to a repository. You can create a deployment group that contains references to versioned 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. Use the Repository Manager to create and edit deployment groups.
♦
Object queries. Use an object query to search for versioned and non-versioned objects in the repository that meet specified conditions. You can save object queries for later use. You can create a private object query, or you can share it with all users in the repository. Use the Designer, Workflow Manager, or Repository Manager to create and run an object query.
♦
Connection objects. You create connection objects in the repository when you define database, FTP, and external loader connections in the Workflow Manager. You can configure and manage permissions within each connection object. Use the Workflow Manager to create and edit connection objects.
Labels, deployment groups, and object queries help you perform version control by grouping versioned objects. For more information about version control, see “Version Control” on page 15.
Modifying Dependent Objects When you modify a child object, it may cause a parent object to become invalid. For example, if you modify a mapping by changing a port datatype to an incompatible datatype, the session may become invalid. A repository object can have a valid, invalid, or impacted state. The Repository Service assigns valid and invalid states when you save an object or when you validate an object. The Repository Service assigns an impacted state when it fetches a parent object of a child object modified in a way that may cause invalidation. The impacted state is an indeterminate state that is resolved when you validate or save an object. When you modify repository objects, the Repository Service assigns one of three states to the modified object and dependent parent object.
8
Chapter 1: Understanding the Repository
Table 1-1 describes the object validation states. Table 1-1. Object Validation States Object State
Assigned
Running the Workflow
Valid
When you save or validate an object.
The object is valid, and workflows run. You do not need to modify the state.
Invalid
When you save or validate an object.
The object is invalid, and workflows will not run. Use the message displayed by the PowerCenter Client to determine the cause of the invalidation. Modify and validate the object again.
Impacted
If you modify a child object in such a way that it may cause the parent object to become invalid, the Repository Service marks parent objects as impacted. The Repository Service marks the object as impacted when it fetches the parent object.
The object is impacted, and you can perform validation or configure the Integration Service to run the impacted session.
The Repository Service marks dependent objects and shortcuts to parent objects in other folders with warnings to denote the impacted status. A question mark icon denotes impacted status in the Navigator. The Repository Service marks the most immediate parent object as impacted, but it does not mark all related objects as impacted. For example, if you modify a mapping, the Repository Service marks the session as impacted, but it does not mark the workflow as impacted. Figure 1-2 shows invalid and impacted objects: Figure 1-2. Invalid and Impacted Objects
Invalid Object
Impacted Object
You can validate impacted sessions, or you can choose to ignore the warning and run the session. To ignore the warning, you must configure the Integration Service to run impacted sessions. At run time, the Integration Service validates the session and determines if the session is valid or invalid. The Integration Service will not run an impacted session if it detects that the session is invalid. Understanding Metadata
9
Example For example, you have a mapping in Folder A that contains a shortcut to an Expression transformation in Folder B. In Folder B, you update the Expression transformation in a way that causes invalidation. The Repository Service marks the parent mappings in Folder B that use the Expression transformation. The Repository Service also marks the mappings in Folder A that use the shortcut to the Expression transformation with a warning. When you run a session that uses the impacted mappings, the Integration Service validates the mappings. If the mappings are valid, the Integration Service runs the session. If the mappings are invalid, the Integration Service marks the session as invalid and it does not run the session.
Rules and Guidelines for Object Compatibility The Repository Service treats modified dependent objects as compatible when you perform the following tasks: ♦
Change datatypes in a source, target, or transformation to a compatible datatype. The Repository Service marks objects as impacted only when you change the datatypes to incompatible datatypes.
♦
Rename ports in a reusable transformation.
♦
Add a port in a source, target, or transformation.
♦
Replace objects such as sources, targets, mapplets, and mappings with compatible objects.
When you replace a repository object with another object, the following conditions must be true for the Repository Service to treat the objects as compatible:
10
Repository Object
Compatibility Requirements
Source, Target, Transformation
- Name of the replacement object must match the original object. - All port names in the original object must be represented in the replacement object. - Datatypes must be compatible.
Mapping
Name and number of the following objects must match the original object: - Targets - Mapplets - Sources - Source Qualifiers - Joiner transformations - Update Strategy transformations - Custom transformations
Mapplet
Name and number of the following objects must match the original object: - Sources - Source Qualifiers - Joiner transformations - Update Strategy transformations - Custom transformations
Chapter 1: Understanding the Repository
Administering Repositories You use the PowerCenter Administration Console, the Repository Manager, and the pmrep and infacmd command line programs to administer repositories. Table 1-2 lists some of the common repository administration tasks and the corresponding tools you can use to perform them: Table 1-2. Repository Administration Tasks by Tool Repository Manager
Admin Console
pmrep
Back up repository to a binary file
X
X
Restore repository from a binary file
X
X
Copy repository database tables
X
X
Delete repository database tables
X
X
Create a Repository Service
X
X
Remove a Repository Service
X
X
Create folders to organize metadata
X
X
Add repository users and groups
X
X
Configure repository security
X
X
infacmd
X
The Repository Service creates and updates the repository tables. These tables store metadata in a particular format that the Integration Service and the PowerCenter Client tools use. Warning: The PowerCenter repository tables have an open architecture. Although you can view the repository tables, never manually edit them through other utilities. Informatica is not responsible for corrupted data that is caused by customer alteration of the repository tables or data within those tables.
You use the PowerCenter Administration Console to copy, back up, and restore repository content. You can back up the repository to a binary file. You can restore the entire repository from a binary file. You can also copy all the repository tables from another database.
Creating the Repository Before you create a repository, you need a database for the repository tables. You use the database management system client to create the database. The repository database name must be unique. After you create a database for the repository, you can use the Administration Console to create a Repository Service to manage the repository. When you create the Repository Service, you can create the database tables for the repository. Alternatively, you can create the Repository Service without creating any database tables. You can create the repository tables
Administering Repositories
11
later or use existing database tables for the repository. The repository name is the same as the name of the Repository Service. For more information about creating and managing repositories, see “Creating and Configuring the Repository Service” and “Managing the Repository” in the Administrator Guide.
Creating Folders After you create the repository, you can add folders to it in the Repository Manager. Use folders to organize repository objects. You can separate different types of metadata and projects into easily identifiable areas. You can configure a folder to be shared so that its content is available to all other folders in the same repository. If you plan to use the same object in several projects, store it in a shared folder. For example, you use a shared folder to store a definition of the CUSTOMERS table, which provides data for a variety of projects. You make shortcuts to the table in other folders in the same repository. If you are working in a repository domain, you can also make shortcuts to the CUSTOMER table in folders in local repositories that are registered with the repository domain. For more information about repository domains, see “PowerCenter Repository Domains” on page 13. For more information about folders, see “Working with Folders” on page 93.
Security To secure data in the repository, the repository provides a system of users, user groups, repository privileges, folder permissions, and object locking. After you create a repository, use the Repository Manager to set up repository users and groups and to specify the repository privileges that they have. When you create a folder, 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. Privileges control users’ ability to perform tasks such as creating mappings, running sessions, or deploying folders. Permissions control access to folders and objects in the repository. For more information about configuring repository security, see “Managing Users and Groups” on page 63.
12
Chapter 1: Understanding the Repository
PowerCenter Repository Domains You can organize, simplify, and manage the process of developing and maintaining multiple data warehouses and other integration projects by using a repository domain. You connect repositories within the repository domain. A repository domain consists of a single global repository and any number of local repositories. The global repository is the hub of the system. It serves the following purposes: ♦
Opening connections between repositories. To preserve system security and to simplify the task of connecting from one repository to another, the global repository stores information needed to connect to each repository. If you are connected to a local repository, you can navigate to the global repository without connecting to it separately. If you are connected to a global repository, you can navigate to any local repository in the repository domain.
♦
Storing and reusing shared metadata. You can save any metadata that you plan to share across repositories in the global repository. Local repositories can then use shortcuts to objects in the global repository shared folders, or you can create copies of objects in unshared folders. You can also copy objects in shared folders.
You can share data and metadata between global and local repositories by copying individual repository objects and entire folders within and between repositories. You can also use the Designer to create shortcuts to reference objects in other repositories. For more information about creating a repository domain, see “Managing the Repository” in the Administrator Guide.
Reusing Metadata In a repository 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 complex. It is based on variables such as production costs and marketing expenses. Because profitability is important information when investing in product development and building a sales strategy, you need everyone in the organization to use the same calculation. If you share the profitability calculation, you ensure that everyone views the value of each product 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 production, marketing, and accounting divisions might also need to use the same calculation in mappings in their repositories.
PowerCenter Repository Domains
13
Shared Folders You can configure folders in global and local repositories to be shared. After you designate a folder as shared, you can create shortcuts to objects in that folder. Use shortcuts in any other folder in the repository. If the shared folder is in a global repository, use shortcuts to that folder in any repository in the repository domain. If a folder is not shared, you cannot create shortcuts to objects in the folder. However, you can still create copies of objects in non-shared folders. Shared folders are useful when you want to use the same repository objects in several projects within the same repository. For example, each folder within a repository might represent a different development project. However, every project in the repository needs to store bug reports in a consistent format, so you might put the source definition for the BUG_REPORTS table in a shared folder. For more information about folders, see “Working with Folders” on page 93.
Reusing Data The need to share data is just as important 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 is 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 the inserts, deletes, and updates that have occurred in the PRODUCTS table since the last time you updated the central data store. You can format data in a standard fashion with the central data store. For example, you can filter employee data that should remain confidential. You can also 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.
14
Chapter 1: Understanding the Repository
Version Control If you have the team-based development option, you can enable version control for the repository. A versioned repository stores multiple 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 perform the following change management tasks 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. You can see the changes made to an object over time.
♦
Delete or purge a version. You can delete an object so that it no long appears in the PowerCenter Client. However, you continue to store deleted objects in the repository. If you decide later that you need a deleted object, you can recover it from the repository. When you purge an object version, you permanently remove it from the repository.
♦
Use global objects such as queries, deployment groups, and labels to group versioned objects. Object queries, deployment groups, and labels are global objects that exist at the repository level. When you group versioned objects, you can associate multiple objects into logical categories. For example, you can create a deployment group that contains references to objects from multiple folders across the repository.
For more information about global objects, see “Global Objects” on page 8. For more information about version control, see “Working with Versioned Objects” on page 129.
Version Control
15
16
Chapter 1: Understanding the Repository
Chapter 2
Using the Repository Manager This chapter includes the following topics: ♦
Overview, 18
♦
Understanding the Repository Manager Windows, 20
♦
Configuring Repository Manager Options, 28
♦
Connecting to Domains and Repositories, 30
♦
Managing Domain and Repository Connections, 35
♦
Searching for Repository Objects, 39
♦
Viewing Object Dependencies, 42
♦
Validating Multiple Objects, 47
♦
Comparing Repository Objects, 50
♦
Truncating Workflow and Session Log Entries, 53
♦
Managing User Connections and Locks, 55
17
Overview You can navigate through multiple folders and repositories and perform basic repository tasks with the Repository Manager.
Repository Manager Windows The Repository Manager can display four main windows: the Navigator window, the Main window, the Dependency window, and the Output window. You can dock and undock the Navigator, Dependency, and Output windows. You can also hide and display the Navigator, Dependency, and Output windows. In the Navigator window, you can connect to a repository, navigate through the folders, and browse repository objects. The Navigator window organizes the repository objects of the same type in each folder in groups called nodes. When you select an object in a node, you can view details for the object in the Main window. If you configure the Repository Manager to display object dependencies, the Dependency window displays the dependency details when you select an object in the Navigator window. You can view dependency information for sources, targets, mappings, and shortcuts. The Output window displays detailed information for complex repository operations, such as copying folders. The Output window also displays Repository Service notification messages. Note: Because the status of the repository changes as users access it, refresh the view of the
repository before performing tasks, such as deleting a folder or unlocking an object.
Repository Manager Tasks Use the Repository Manager to complete the following tasks:
18
♦
Add domain connection information. You can configure domain connection information. For more information, see “Configuring a Domain Connection” on page 30.
♦
Add and connect to a repository. You can add repositories to the Navigator window and client registry and then connect to the repositories. For more information, see “Connecting to a Repository” on page 32.
♦
Work with PowerCenter domain and repository connections. You can edit or remove domain connection information. You can connect to one repository or multiple repositories. You can export repository connection information from the client registry to a file. You can import the file on a different machine and add the repository connection information to the client registry. For more information, see “Managing Domain and Repository Connections” on page 35.
♦
Search for repository objects or keywords. You can search for repository objects containing specified text. If you add keywords to target definitions, use a keyword to search for a target definition. For more information, see “Searching for Repository Objects” on page 39.
Chapter 2: Using the Repository Manager
♦
View object dependencies. Before you remove or change an object, you can view dependencies to see the impact on other objects. For more information, see “Viewing Object Dependencies” on page 42.
♦
Compare repository objects. In the Repository Manager, you can compare two repository objects of the same type to identify differences between the objects. For more information, see “Comparing Repository Objects” on page 50.
♦
Truncate session and workflow log entries. You can truncate the list of session and workflow logs that the Integration Service writes to the repository. You can truncate all logs, or truncate all logs older than a specified date. For more information, see “Truncating Workflow and Session Log Entries” on page 53.
♦
View user connections. Use the Repository Manager to view and manage user connections. For more information, see “Managing User Connections and Locks” on page 55.
♦
Release locks. Use the Repository Manager to release residual locks left by residual connections. Releasing a valid lock can result in repository inconsistencies, so release a lock only if the locked object is not in use. For more information, see “Closing User Connections and Releasing Locks” on page 60.
♦
Exchange metadata with other business intelligence tools. You can export metadata to and import metadata from other business intelligence tools, such as Cognos ReportNet Framework Manager. For more information, see “Exchanging Metadata” on page 267.
Overview
19
Understanding the Repository Manager Windows The Repository Manager has a main window and a status bar for information about the operation you are performing. The Repository Manager can display the following windows: ♦
Navigator
♦
Main
♦
Dependency
♦
Output
Figure 2-1 shows the Repository Manager components: Figure 2-1. 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.
20
Chapter 2: Using the Repository Manager
Displaying Windows You can dock and undock the following windows in the Repository Manager: ♦
Navigator
♦
Dependency
♦
Output
To dock or undock a window: ♦
Double-click the title bar. -or-
♦
Drag the title bar toward the Main window.
The windows that the Repository Manager displays depend on the tasks you perform. When you launch the Repository Manager, the Navigator and the Main windows appear. The Dependency window appears when you want to view dependencies, and the Output window appears when the Repository Manager displays status messages. You can configure the Repository Manager to display or hide any window. To display a window: 1.
Double-click the title bar.
2.
From the menu, choose View. Then select the window you want to open.
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 types of objects: ♦
Repositories. PowerCenter repositories can be standalone, local, or global.
♦
Deployment groups. Deployment groups contain collections of objects for deployment to another repository in the repository domain.
♦
Folders. Folders can be shared or not shared.
♦
Nodes. Nodes contain 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.
Understanding the Repository Manager Windows
21
Figure 2-2 shows the Navigator components: Figure 2-2. Repository Manager Navigator
Repositories
Deployment Groups
Shared Folder
Node for Sources Mappings
Workflows Node for Session Configurations
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 135. Note: If you enable versioning when you create the repository, you can view all tabs on the
Properties dialog box.
22
Chapter 2: Using the Repository Manager
Figure 2-3 shows the object properties for a source definition: Figure 2-3. Source Definition Object Properties
Main Window The Main window of the Repository Manager displays information 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.
Sorting and Organizing You can sort items in the Main window by each of the columns. For example, to sort mappings by validity, select the mappings node, and then click the Valid column heading. Click the heading again to reverse the order in which the mappings are sorted. You can also change the order in which the columns appear. For example, you might want the Valid column to appear first, on the left side of the Main window. To do this, drag the Valid column heading to the location. The Repository Manager displays the columns in the new order until you change the display. Note: You can double-click an object in the Main window to view its properties.
Viewing Object Details To view information about repository objects, select a node in the Navigator. Or, to view detailed information about a particular repository object, drill down on a node and select the object.
Understanding the Repository Manager Windows
23
Table 2-1 describes the object details displayed in the Main window: Table 2-1. Object Details Displayed in Main Window of Repository Manager
24
Node
Information Displayed
Repository Node
Displays properties for each folder in the selected repository.
Deployment Groups Node
Displays properties for each deployment group in the selected repository. Select a static 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 within the selected node. Select a target definition to view details for each target definition port.
Transformations Node
Displays the properties for each reusable transformation in the selected node. Select a 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 Transformations 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 Node
Displays workflow log information for the selected workflow. The Workflow Logs node appears under each workflow in the Workflows node.
Session Logs Node
Displays session log information for the selected session. The Session Logs node appears under each session in the Sessions node.
Source Connections Node
Displays connection properties for each source connection associated with the session. The Source Connections node appears under each session in the Sessions node and under each session associated with a workflow under the Workflows node.
Source File Connections Node
Displays properties for each source file associated with the session. The Source File Connections node appears under each session in the Sessions node and under each session associated with a workflow under the Workflows node.
Target Connections Node
Displays connection properties for each target connection associated with the session. The Target Connections node appears under each session in the Sessions node and under each session associated with a workflow under the Workflows node.
Chapter 2: Using the Repository Manager
Table 2-1. Object Details Displayed in Main Window of Repository Manager Node
Information Displayed
Target File Connections Node
Displays properties for each target file associated with the session. The Target File Connections node appears under each session in the Sessions node and under each session associated with a workflow under the Workflows node.
Transformation Logs Node
Displays log details for each transformation in the session when you select the Transformation 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 more information about using the Dependency dialog box, see “Viewing Object Dependencies” on page 42. When you view dependencies, the left pane of the Dependency window lists the object that has dependency information, and the dependency information appears in the right pane. Figure 2-4 shows the Dependency window: Figure 2-4. Dependency Window
Selected Object
Dependencies
The Dependency window can display the following types of dependencies: ♦
Source-target dependencies. When you view source-target dependencies, the Dependency window lists all sources or targets related to the selected object, including relevant information about those sources or targets. For example, if you select a target, you view all sources that provide data for that target, along with information about each source.
♦
Mapping dependencies. When you view mapping dependencies, the Dependency window lists all mappings containing the selected object, and relevant information about those mappings. For example, if you select a reusable transformation, you view all mappings using that transformation and information about each mapping.
♦
Shortcut dependencies. When you view shortcut dependencies, the Dependency window lists all shortcuts to the selected object and relevant details, such as the repository and folder in which the shortcut exists. When you edit an object referenced by shortcuts, use the Repository Manager to see which folders contain the shortcut.
Understanding the Repository Manager Windows
25
When you open the Dependency window, it displays dependencies for the object selected in the Navigator. You can also view mapping object dependencies in the Designer. You can view dependencies for sources, targets, transformations, mappings, mapplets, and shortcuts in the Designer. For more information, see “Using the Designer” in the Designer Guide.
Output Window The Repository Manager displays status messages in the status bar. For complex operations, 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...
After you connect to the repository, the status bar displays the word Ready. When you perform a complex operation, such as copying a folder, the Repository Manager displays details about the operation in the Output window. Figure 2-5 shows the Output window: Figure 2-5. Output Window
The Repository Manager receives notifications when the following objects are created, modified, or deleted: ♦
Folders
♦
Users
♦
Groups
You must be connected to the repository to receive notifications about folders. You need the Super User privilege to receive notifications about users and groups. For more information about privileges for Repository Manager tasks, see “Permissions and Privileges by Task” on page 367. You can change the font type and size displayed in the output window by right-clicking the window and selecting Change Font.
26
Chapter 2: Using the Repository Manager
Using Toolbars The Repository Manager displays the following toolbars by default: ♦
Standard. Contains buttons to connect to and disconnect from repositories, view dependencies for selected objects, search by keyword, view object properties, close the Dependency window, and toggle the Navigator and Output windows.
♦
Tools. Contain buttons to connect to the other PowerCenter Client application. When you use a Tools button to open another PowerCenter Client application, PowerCenter uses the same repository connection to connect to the repository and opens the same folder.
Understanding the Repository Manager Windows
27
Configuring Repository Manager Options Use the Options dialog box of the Repository Manager to configure general options. Click Tools > Options to access the general options, which relate to saving Metadata Exchange (MX) data and adding to deployment groups. Figure 2-6 shows the Options dialog box: Figure 2-6. Options Dialog Box of the Repository Manager
Table 2-2 describes the general options: Table 2-2. General Options Option
Description
Prompt User While Adding to Deployment Group
Displays the Dependency for Deployment Group dialog box when you add objects to a static deployment group. If you clear this check box, the Repository Manager adds all child objects when you add an object to a static deployment group. For more information about adding to static deployment groups, see “Adding or Removing Objects in Static Deployment Groups” on page 158.
Save All MX Data
Saves all MX data when you use the Repository Manager to import mappings. You can then access the data in MX views to analyze repository metadata or to integrate with third-party repository tools. Default is disabled. For more information about MX views, see “Using Metadata Exchange (MX) Views” on page 295.
Save Only Source/Target Dependencies
Saves only the MX data related to source/target dependencies when you use the Repository Manager to import mappings. Select this option if you use the Repository Manager to view source/target dependencies, but you do not need to view expressions of fields in MX views. Default is disabled.
Note: Saving MX data can impact performance. Select this option only if you intend to use
MX views. You can also configure the Designer to save MX data when you save mappings in the Designer. The MX data option in the Repository Manager controls the behavior of mapping imports in the Repository Manager only. It does not affect the behavior of the Designer. For more information about configuring the Designer, see “Using the Designer” in the Designer Guide.
28
Chapter 2: Using the Repository Manager
When you save MX data for mappings, PowerCenter creates a field expression for each target field in the mappings. The field expression describes the source definition and transformation expression corresponding to the target field. In addition to viewing the MX data in MX views, you can view the field expressions in the Main window of the Repository Manager when you analyze source-target dependencies.
Configuring Repository Manager Options
29
Connecting to Domains and Repositories Each repository belongs to a PowerCenter domain. You connect to a repository through the domain. Before you can initially connect to a repository, you must provide connection information for the domain. You also need to add the repository to the Navigator in the PowerCenter Client. Complete the following tasks before initially connecting to a repository: ♦
Configure the domain connection information first, and then add a repository. For more information, see “Configuring a Domain Connection” on page 30. -or-
♦
Add a repository to the Navigator, and then configure the domain connection information when you connect to the repository. For more information, see “Adding a Repository to the Navigator” on page 32.
Configure the domain connection information first if you need to add multiple repositories to the Navigator. After you create a domain connection, you may need to update or remove it. For information about updating domain connections, see “Editing a Domain Connection” on page 35. For information about deleting domain connections, see “Removing a Domain Connection” on page 36. You manage PowerCenter domains and repositories in the PowerCenter Administration Console. For more information about managing domains and repositories, see the PowerCenter Administrator Guide.
Configuring a Domain Connection You add domain connection information to the PowerCenter Client so that you can connect to repositories in the domain. After you add a domain connection, you can select from a list of associated repositories to add to the Navigator. Note: You can also enter domain connection information when you connect to a repository.
For more information, see “Connecting to a Repository” on page 32. To configure a domain connection and add repositories to the Navigator: 1.
30
In a PowerCenter Client tool, select the Repositories node in the Navigator.
Chapter 2: Using the Repository Manager
2.
Click Repository > Configure Domains to open the Configure Domains dialog box. Add a domain. Remove a domain. Edit domain connection information. Update the list of repositories with any changes made in the Administration Console.
3.
Click the Add button. The Add Domain dialog box appears.
4.
Enter the domain name, gateway host name, and gateway port number.
5.
Click OK to add the domain connection. After you add a domain connection, you can add repositories to the Navigator by selecting them in the list of associated repositories. Note: The list of associated repositories might change if a domain user adds or deletes a
Repository Service in the Administration Console while you are working in the PowerCenter Client. You refresh the list of associated repositories each time you click a domain other than the currently selected domain in the left panel. Click Refresh to update the list of associated repositories for the currently selected domain. 6.
If you need to add repositories to the Navigator, complete the following steps: ♦
Click a domain name in the left panel of the Configure Domains dialog box.
♦
In the right panel, select the repositories to add to the Navigator.
♦
Click OK.
Connecting to Domains and Repositories
31
Adding a Repository to the Navigator Add a repository when a repository already exists but does not appear in the Navigator. You can add a repository in the Repository Manager, the Designer, the Workflow Manager, or the Workflow Monitor. After you add a repository in one of the PowerCenter Client tools, it appears in the Navigator window of all the tools. To add a repository to the Navigator: 1.
In any of the PowerCenter Client tools, click Repository > Add.
2.
Enter the name of the repository and a valid repository user name.
3.
Click OK.
The repository appears in the Navigator of the PowerCenter Client tools. Before you can connect to the repository for the first time, you must configure the connection information for the domain that the repository belongs to.
Connecting to a Repository Before you can connect to a repository, you must first add the repository to the Navigator. For more information about adding a repository, see “Adding a Repository to the Navigator” on page 32. To connect to a repository: 1.
Launch a PowerCenter Client tool.
2.
Select the repository in the Navigator and click Repository > Connect, or double-click the repository. The Connect to Repository dialog box appears.
3.
32
Enter a valid repository user name and password.
Chapter 2: Using the Repository Manager
4.
If you are connecting to a repository that you have connected to before, go to step 11. -orIf you want to select an existing domain connection for the repository, go to step 9. If you need to enter the domain connection information for the repository, complete steps 5 through 8.
5.
If the Connect to Repository dialog box is not expanded, click More to view the connection settings.
6.
Click Add. The Add Domain dialog box appears.
7.
Enter the domain name, gateway host name, and gateway port number.
8.
Click OK.
9.
If the connection settings of the Connect to Repository dialog box are hidden, click More to view the connection settings.
10.
In the connection settings, select the appropriate domain connection from the list.
11.
Click Connect.
Reconnecting to a Repository and Canceling Auto-Reconnect After you connect to a repository, the PowerCenter Client can maintain the connection when a temporary network or hardware failure occurs. The ability to maintain the connection is called resilience. If you perform a PowerCenter Client action that requires a connection to the repository while the PowerCenter Client is trying to reestablish the connection, the PowerCenter Client prompts you to try the operation again after it reestablishes the connection. If the Connecting to Domains and Repositories
33
PowerCenter Client is unable to reestablish the connection during the resilience timeout period, the PowerCenter Client prompts you to reconnect to the repository manually. The PowerCenter Client resilience timeout controls how long the client attempts to reconnect to the repository after the connection is interrupted. The PowerCenter Client resilience timeout is 180 seconds and is not configurable. In the Designer, Workflow Manager, and Repository Manager, you can temporarily disable PowerCenter Client resilience to prevent the client from attempting to reestablish a repository connection during the resilience timeout period. If you do not want to wait for the resilience timeout to expire, cancel the automatic reconnection. Then, you need to manually connect to the repository again. For more information, see “Connecting to a Repository” on page 32. After the resilience timeout expires or you cancel the automatic reconnection, you must reconnect to the repository to save changes that you made before the repository connection failed. To cancel automatic reconnection: 1.
Verify that the PowerCenter Client is attempting to reestablish the repository connection. Execute an operation that requires a repository connection. If the resilience timeout has not expired, the PowerCenter Client prompts you to retry the operation after the connection is reestablished.
2.
Click Repository > Cancel Auto-Reconnect.
The PowerCenter Client stops attempting to reconnect. To perform actions that require a repository connection, you must manually connect to the repository.
34
Chapter 2: Using the Repository Manager
Managing Domain and Repository Connections You may need to modify or remove domain connection information that is outdated. Similarly, you may need to manage connections to individual repositories. You can perform the following tasks to manage domain and repository connections: ♦
Edit domain connection information.
♦
Remove domain connection information.
♦
Connect to multiple repositories.
♦
Export and import repository connection information.
♦
Remove a repository from the Navigator.
Editing a Domain Connection Edit domain connection information when you need to change a gateway host name or gateway port number for a domain connection. To edit a domain connection: 1.
Click Repository > Configure Domains.
2.
In the Configure Domains dialog box, select a domain and click the Edit button. The Edit Domain dialog box appears.
3.
Enter a new gateway host name and gateway port number, if necessary.
4.
Click OK.
Note: You can also edit a domain connection when you connect to a repository.
Managing Domain and Repository Connections
35
Removing a Domain Connection You can remove a domain connection from the PowerCenter Client. To remove a domain connection: 1.
Click Repository > Configure Domain.
2.
In the Configure Domains dialog box, select the domain connection that you want to delete.
3.
Click the Remove button.
4.
In the warning message that appears, click Yes.
Note: When you remove a domain connection, you terminate connectivity between the
PowerCenter Client and all services in the domain. To restore connectivity, you need to add the domain connection and then add repositories.
Connecting to Multiple Repositories You can connect to multiple repositories and work in multiple folders at one time. You can also connect from a local repository to a global repository and from a global repository to any local repository. To make these connections, you must have identical logins in both repositories. To create a global shortcut, connect from the local repository to the global repository. To connect to multiple repositories separately: 1.
In the Navigator, select a repository and click Repository > Connect. Existing folders in the repository now appear beneath the repository.
2.
Select another repository, and click Repository > Connect.
To connect from a local repository to the global repository: 1.
Connect to the local repository. If the repository is part of a repository domain, an icon for the global repository appears beneath the local repository icon and folders in the local repository.
2.
Double-click the icon for the global repository. A connection to the global repository opens, and you can see the folders within the global repository and the local repository. Double-click a folder in either repository to access its contents.
To connect from the global repository to a local repository: 1.
Connect to the global repository. Icons for all the local repositories in the repository domain appear beneath the global repository.
36
Chapter 2: Using the Repository Manager
2.
Double-click the icon for the local repository you want to access. The contents of the local repository appear.
Exporting and Importing Repository Connection Information The Repository Manager saves repository connection information in the registry. To simplify the process of setting up client machines, you can export that information and then import it to a different client machine. Both machines must use the same operating system. The section of the registry you can import and export contains the following repository connection information: ♦
Repository name
♦
Repository user name and 7-bit ASCII password
♦
Gateway host name and port number
To export the repository connection information from the registry: 1.
In the Repository Manager, click Tools > Export Registry.
2.
Enter the name of the export file. To identify the file, use a file name with the extension.reg, such as MySources.reg.
3.
Click OK. A dialog box appears, informing you that the Repository Manager successfully exported the repository registry file.
You can now distribute this file for import on other client machines with the same operating systems. To import the repository connection information to the registry: 1.
In the Repository Manager, click Tools > Import Registry.
2.
Navigate to the directory containing the import file and select it.
3.
Click Open. A dialog box appears, informing you that the Repository Manager successfully merged the repository connection information into the registry.
Removing a Repository from the Navigator You can remove a repository from the Navigator of the PowerCenter Client. You might need to remove a repository from the Navigator if the repository no longer exists or if you no longer use the repository.
Managing Domain and Repository Connections
37
To remove a repository from the Navigator: 1.
In the Navigator of a PowerCenter Client tool, 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 remove a repository from the PowerCenter Client registry:
38
1.
In the Navigator of the Repository Manager, click Tools > Remove Repository.
2.
Select the repository you want to remove from the registry, and click Delete.
3.
In the message box that appears, click OK to remove the repository.
Chapter 2: Using the Repository Manager
Searching for Repository Objects In the Repository Manager, you can search for repository objects using the following methods: ♦
Keyword search
♦
Search text
Perform a keyword search when you have associated a keyword with a target definition. Use Search All when you want to search through text in object names, comments, group names, and owner names associated with the repository object.
Performing Keyword Searches After you add keywords to target definitions, use them to perform searches in the Repository Manager. To search for targets containing a keyword: 1.
In the Repository Manager, connect to a repository.
2.
Click Analyze > Search by Target Keyword. The Search Target Tables For Keyword dialog box appears.
You can enter a keyword, or you can select one from the list of all keywords applied to target definitions in the repository. 3.
If you want to select a keyword, click List Keywords, select a keyword, and then click OK. -orEnter a keyword in the Keyword field.
Searching for Repository Objects
39
4.
5.
Select the options you want to use in the search: Option
Description
Exact Match
If selected, the Repository Manager looks for the entire keyword entered. If cleared, 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.
Click OK. The Repository Manager searches for matching keywords in all target definitions in the repository. A list of matching keywords appears at the bottom of the Repository Manager window.
Searching All Repository Objects Use Search All to search for text in the object name, comments, group name, and owner name associated with repository objects. You can search for text in the repository objects such as transformations, source and target fields, and tasks. To search for text in all repositor y objects:
40
1.
In the Repository Manager, connect to the repository.
2.
Click Analyze > Search All.
Chapter 2: Using the Repository Manager
The Search All dialog box appears.
3.
Enter the text you want to find.
4.
Select Match Case if you want to perform a case-sensitive search.
5.
In the item list, select the repository objects in which you want to search for the text. The Repository Manager selects all objects by default.
6.
Select the repository object attributes in which you want to search for the text. The Repository Manager selects all attributes by default.
7.
Click Find Next. The Repository Manager displays the first repository object matching the search text in the Main window.
8.
Click Find Next to find the next repository object matching the search text.
9.
Click Close to close the Search All dialog box.
Searching for Repository Objects
41
Viewing Object Dependencies Before you change or delete repository objects, you can view dependencies to see the impact on other objects. For example, before you remove a session, you can find out which workflows use the session. You can view dependencies for repository objects in the Repository Manager, Workflow Manager, and Designer tools. In the Repository Manager, Workflow Manager, and Designer, you can view dependencies when you perform the following tasks: ♦
View object history. You can view dependencies from the View History window when you view the history of an object.
♦
View checkouts. You can view dependencies from the View Checkouts window when you search for persistent checkouts.
♦
View query results. You can view dependencies from the Query Results window when you search for object dependencies or run an object query.
Note: You can check in objects from the View Dependencies dialog box, but you cannot check
in original objects for global shortcuts. In addition, you can view dependencies from the tools in the Workflow Manager and Designer. Table 2-3 lists the Workflow Manager and Designer tools used to display dependencies, and the objects that View Dependencies displays when you view dependencies: Table 2-3. Viewing Object Dependencies
42
Parent Object
Tool
Types of Child Objects Displayed
Mappings
Mapping Designer
- Global and local shortcuts to the mapping. - Sources the mapping uses. - Targets the mapping uses. - Transformations the mapping uses.
Mapplets
Mapping Designer Mapplet Designer
- Global and local shortcuts to the mapplet. - Sources the mapplet uses. - Targets the mapplet uses. - Transformations the mapplet uses.
Sources
Mapplet Designer Mapping Designer Source Analyzer
- Sources within the same folder that reference or are referenced by the source through a foreign key relationship. - Global and local shortcuts to the source.
Targets
Mapping Designer Target Designer
- Targets within the same folder that reference or are referenced by the target through a foreign key relationship. - Global and local shortcuts to the target.
Transformations
Mapplet Designer Mapping Designer Transformation Developer
- Global and local shortcuts to the transformation.
Chapter 2: Using the Repository Manager
Table 2-3. Viewing Object Dependencies Parent Object
Tool
Types of Child Objects Displayed
Sessions
Task Developer Worklet Designer Workflow Designer
- Sources the session uses. - Targets the session uses. - Mappings the session uses. - Mapplets the session uses. - Transformations the session uses. - Tasks the session uses. - Mapping the session uses. - Session configuration the session uses.
Workflows
Workflow Designer
- Sources the workflow uses. - Targets the workflow uses. - Mappings the workflow uses. - Mapplets the workflow uses. - Transformations the workflow uses. - Sessions the workflow uses. - Tasks the workflow uses. - Schedulers the workflow uses. - Session configuration the workflow uses. - Worklet the workflow uses.
Worklets
Worklet Designer Workflow Designer
- Sources the worklet uses. - Targets the worklet uses. - Mappings the worklet uses. - Mapplets the worklet uses. - Transformations the worklet uses. - Sessions the worklet uses. - Tasks the worklet uses. - Schedulers the worklet uses. - Session configuration the worklet uses.
Note: You can perform all searches in this table from the Repository Manager.
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, the object type, and a list of dependent objects and their properties.
Viewing Object Dependencies
43
Figure 2-7 shows the Dependencies dialog box: Figure 2-7. Dependencies Dialog Box
Search for dependencies.
Select options.
Filter by object type when you search for parent or child dependencies.
When you search for dependencies, you can filter the results by selecting options and object types. Table 2-4 shows the options you can select when you search for dependencies: Table 2-4. Dependencies Options Option
Description
Primary/Foreign Key Dependencies
View primary and source object dependencies where there is a primary key-foreign key relationship.
Global Shortcut Dependencies
View global shortcuts across repositories. You can select this option when you search for parents, children, or primary key-foreign key dependencies.
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.
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.
When you search for dependencies, the View Dependencies window displays the properties for each dependent object.
44
Chapter 2: Using the Repository Manager
Figure 2-8 shows the View Dependencies window: Figure 2-8. View Dependencies Window
Object Properties
Output Window Comments Window
Labels Window
Table 2-5 describes the object properties that appear in the View Dependencies window: Table 2-5. Object Properties in View Dependencies Window Properties
Description
Object Name
Name of the dependent object.
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
Version
Version number of the dependent object.
Time Stamp
Time the object was created or saved.
Status
Status of the object, Active or Deleted.
Version Comments
Comments associated with the dependent object.
Folder Name
Folder name where the dependent object resides.
Viewing Object Dependencies
45
Table 2-5. Object Properties in View Dependencies Window Properties
Description
User Name
User who created the object.
Host Name
Host name for the machine hosting the object.
Checkout Type
Type of checkout for object, Persistent or Non-Persistent.
Purged by User
Name of the user who purged the object.
Is Reusable
Status of object as reusable, Yes or No.
Is Deleted
Status of object deletion, Yes or No.
Repository
Repository 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, click File > Save to File. Figure 2-9 shows an example of the HTML file saved from a View Dependencies window: Figure 2-9. Object Dependencies Saved as HTML
46
Chapter 2: Using the Repository Manager
Validating 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. For more information about mapping validation, see the Designer Guide. For more information about validating sessions and workflows, see the Workflow Administration Guide. You can select objects to validate from the Navigator window of the Repository Manager. You can also select objects from query results or an object dependencies list. If you select objects from the Navigator, you must select objects of the same type in the same folder. If you select objects from query results or an object dependencies list, you can choose different types of objects to validate, and you can select them from within the Repository Manager, Designer, or Workflow Manager. To validate multiple objects: 1.
Select the objects you want to validate.
2.
Initiate the validation. If you select objects from query results or a list view, you must right-click one of the selected objects and select Validate. If you are selecting objects from the Navigator, you can also click Tools > Validate to initiate a validation. The Validate Objects dialog box appears.
3.
4.
Select validation options from the Validate Objects dialog box: ♦
Save validated objects. If you do not choose to save the objects in the repository, the validation just provides a report.
♦
Choose whether to check in validated objects. You can check in valid objects. You can select this option if you have selected the Save Objects that Are Successfully Made Valid option and versioning is enabled in the repository.
♦
Check in comments. If you are checking in validated objects, you must enter check-in comments. Otherwise, this option is disabled.
Click Validate.
Validating Multiple Objects
47
The validation displays status in a progress dialog box. The output window shows the status of each object being validated. You can cancel the validation from the progress dialog box. If you cancel, you do not cancel the current operation, but you cancel the remaining operations in the validation. Figure 2-10 shows the Validate Objects results box. The results box appears when validation completes. Use the results box to determine how many objects were validated and saved. To view the objects in each total, click the link. Figure 2-10. Validate Objects Results
Links to view the objects in the group.
Table 2-6 describes the information that appears in the Validate Objects window: Table 2-6. Validate Objects Properties
48
Properties
Description
Objects Provided for Validation
Total number of objects that you selected to validate. The total includes skipped objects.
Skipped Objects
Number of the following types of objects: - Objects that do not require validation, such as sources, targets, transformations, and shortcuts. - Objects that cannot be fetched, such as a deleted mapping associated with a session being validated.
Objects that Were Invalid Before the Validation
Number of invalid objects provided for validation.
Objects Successfully Validated
Number of selected objects that are valid.
Objects Still Invalid
Number of objects that require fixing or editing.
Saved/Checked In
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 to Lock Conflict
Number of validated objects you cannot save because someone has them locked.
Chapter 2: Using the Repository Manager
5.
Click a link to view the objects in the results group. Validation results that include objects provide links to the object details. When you click the link, a dialog box displays each object in the results group you select.
Validating Multiple Objects
49
Comparing Repository Objects You can compare two repository objects of the same type to identify differences between the objects. For example, you can compare two sessions to check for differences. When you compare two objects, the Repository Manager displays their attributes. You can compare objects across folders and repositories. To do this, you must have both the folders open. You can compare a reusable object with a non-reusable object. You can also compare different versions of the same object. For more information about versioned objects, see “Comparing Versions” on page 143. To compare objects, you must have Read permission on each folder that contains the objects you want to compare. You can compare the following types of objects: ♦
Designer objects. You can compare Designer objects, such as sources, targets, transformations, mapplets and mappings. For more information about comparing objects in the Designer, see the Designer Guide.
♦
Workflow Manager objects. You can compare Workflow Manager objects, such as tasks, sessions, worklets, and workflows. You can compare schedulers and session configuration objects in the Repository Manager, but not in the Workflow Manager. For more information about comparing objects in the Workflow Manager, see the Workflow Administration Guide.
You can compare instances of the same type in detail. For example, if the workflows you compare contain worklet instances with the same name, you can compare the instances to see if they differ. You can compare instances of sessions and tasks in a workflow or worklet comparison. You can compare instances of mappings and transformations in a session comparison. Further, you can compare instances of the same type within a mapping or mapplet comparison. You cannot compare objects of different types. For example, you cannot compare a source definition with a target definition. To compare repository objects: 1.
In the Repository Manager, connect to the repository.
2.
In the Navigator, select the object you want to compare. Tip: To compare the first two objects in a node, select the node.
3.
50
Click Edit > Compare Objects.
Chapter 2: Using the Repository Manager
A dialog box similar to the following one appears:
4.
Click Compare. If you choose a Designer object, a window shows the result of comparing the objects. For example, the Sources window shows the result of comparing two sources:
View object differences.
Comparing Repository Objects
51
If you choose a Workflow Manager object, such as a session, the Diff Tool window shows the result of comparing two sessions: Filter nodes that have same attribute values. Compare object instances.
Differences between objects are highlighted and the nodes are flagged. Differences between object properties are marked. Displays the properties of the node you select.
52
Chapter 2: Using the Repository Manager
Truncating Workflow and Session Log Entries When you configure a session or workflow to archive session logs or workflow logs, the Integration Service saves those logs in local directories. The repository also creates an entry for each saved workflow log and session log. If you move or delete a session log or workflow log from the workflow log directory or session log directory, you can remove the entries from the repository. Use the Repository Manager to truncate the list of workflow logs for workflows that have completed. You can also use the pmrep TruncateLog command to truncate workflow logs. For more information about the pmrep TruncateLog command, see “pmrep Command Reference” in the Command Line Reference. You can truncate all log entries for a workflow or log entries that were created before a specified date. You cannot truncate a workflow log for a workflow that is still running. The Repository Service truncates the workflow log list and the session log list at the same time. When the Repository Service truncates log entries for sessions and workflows, it also deletes the following run-time information for the sessions and workflows: ♦
Workflow details
♦
Session statistics
♦
Task details
♦
Source and target statistics
♦
Partition details
♦
Performance details
Tip: You can truncate log entries to reduce the size of the repository in the database. The log
entries can use a significant amount of space in the repository. For more information on details and statistics, see “Monitoring Workflows” in the Workflow Administration Guide. To truncate workflow and session log entries: 1.
In the Repository Manager, select the workflow in the Navigator window or in the Main window.
2.
Choose Edit > Truncate Log.
Truncating Workflow and Session Log Entries
53
The Truncate Workflow Log dialog box appears.
3.
Choose to delete all workflow and session log entries or to delete all workflow and session log entries with an end time before a particular date.
4.
If you want to delete all entries older than a certain date, enter the date and time.
5.
Click OK. The Repository Service deletes the workflow and session log entries from the repository.
54
Chapter 2: Using the Repository Manager
Managing User Connections and Locks Use the Repository Manager or the Administration Console to manage user connections and locks. In the Repository Manager, you can view and manage the following items: ♦
Repository object locks. The repository locks repository objects and folders by user. The repository creates different types of locks depending on the task. The Repository Service 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.
♦
User connections. Use the Repository Manager to monitor user connections to the repository. You can end connections when necessary. To avoid repository inconsistencies, you need to determine if the user has an active connection before closing the connection.
For more information about using the Administration Console to manage user connections and locks, see “Managing the Repository” in the Administrator Guide.
Understanding Repository Object Locks The repository uses locks to prevent users from duplicating or overwriting work. The Repository Service creates the following types of locks on repository objects when you view, edit, or run them in a workflow: ♦
In-use lock. Placed on objects you want to view.
♦
Write-intent lock. Placed on objects you want to modify.
♦
Execute lock. Locks objects you want to run, such as workflows and sessions.
The Repository Service creates and releases locks on repository objects. The repository allows multiple users to obtain in-use locks on an object. The repository allows one write-intent lock per object. This keeps multiple users from editing the object at one time, thus preventing repository inconsistencies. If you attempt to modify an object that already has a write-intent lock, the repository displays a message box: The [object_type] [object_name] is already locked by [user name].
The repository then issues an in-use lock for the object, allowing you to view the object. The repository allows one execute lock per object. This keeps you from starting a workflow that is already running, which can cause the Integration Service to load duplicate or inaccurate data.
Managing User Connections and Locks
55
Table 2-7 lists each repository lock and the conditions that create it: Table 2-7. Repository Locks Repository Lock
Created When
Maximum per Object
In-use
- Viewing an object in a folder for which you do not have write permission. - Viewing an object that is already write-locked. - Exporting an object.
Unlimited
Write-intent
- Viewing an object in a folder for which you have write permission. - Editing an object in a folder for which you have write permission. - Importing an object.
1
Execute
- Starting, aborting, or recovering a workflow.
1
Locking the Same Object The repository permits multiple in-use locks, one write-intent lock, and one execute lock simultaneously on each repository object. This means that you can edit a session while the Integration Service runs the session and another user views the session. For example, if you obtain a write-intent lock on a workflow before the Integration Service starts the workflow, the Integration Service runs the version of the workflow existing in the repository when the workflow starts. If you save changes to the repository before the workflow starts, the Integration Service runs the newly-edited workflow. If you save changes after the workflow starts, the Integration Service runs the original workflow and the repository updates the changes after the workflow completes. When the workflow starts, the Integration Service obtains an execute lock on the workflow and tasks in the workflow. If you try to start the workflow, the repository displays a message stating that the workflow is already running. If you try to edit the workflow or task when another user has a write-intent lock, you receive a in-use lock.
Locking Within Objects Some repository objects contain other repository objects. For example, workflows contain sessions and tasks, sessions contain mappings, and mappings contain at least one source and target definition. You obtain an in-use lock on an object when you view it. You can view an object used by another object without affecting the other object. However, if you save changes to an object used by other objects, the repository might mark the other objects invalid. Before using invalidated objects, you must validate them. For example, you open a mapping used by a session, delete a transformation, and save the changes. When you save the mapping, the repository notes the mapping has been changed, and marks the session and every other session using the mapping invalid. The change might invalidate any workflow containing the session. For more information about validating objects, see “Validating Multiple Objects” on page 47.
56
Chapter 2: Using the Repository Manager
For more information about validating the workflow, see “Working with Workflows” in the Workflow Administration Guide.
Locking with Cubes and Dimensions Editing or deleting cubes and dimensions can affect many objects in the repository. When you edit a property of a cube or dimension, the Repository Service creates a write-intent lock on all related objects until you save the changes or cancel the edit. Therefore, if an object is a part of a cube or dimension being edited, you might notice the object is locked even when no one is working with it. For example, if you use the Dimension Editor to change a Level Property field, the Repository Service locks all related dimension tables until you save the changes. Any user who tries to edit a related dimension table receives an in-use lock on the table.
Locking Business Components To maintain the integrity of the repository data, the Repository Service locks the business component tree while its contents are being edited. This prevents you from copying or editing the business component. Locking occurs at the root directory of the business component tree. For example, if Finance is the root directory of the tree, with General Ledger and Accounts Receivable as subdirectories, the Repository Service locks the Finance directory while you make changes to the Accounts Receivable or General Ledger subdirectories. The Repository Service releases a lock when you click Repository > Save. Use the Show Locks feature to see if the business component or objects it points to are locked.
Acquiring Locks During Deployment When you copy a folder or deployment group to another repository, you must acquire locks on the objects in the target repository. If the object locks are not immediately available, by default the deployment operation waits until either you cancel the deployment or the object locks are acquired. For more information about deploying objects, see “Copying Folders and Deployment Groups” on page 191. If you use pmrep to copy folders or deployment groups, you can specify a timeout for the deployment operation. If pmrep does not acquire object locks in the target repository during the timeout period, the deployment fails. For more information about using pmrep for deployment, see “pmrep Command Reference” in the Command Line Reference.
Viewing User Connections and Locks In the Repository Manager, you can monitor and close user connections, and you can view and release locks. You can also perform these tasks in the Administration Console. For more information about managing user connections and locks in the Administration Console, see “Managing the Repository” in the Administrator Guide.
Managing User Connections and Locks
57
Viewing User Connections Use the Repository Manager to view connection details for users and applications connected to the repository. Table 2-8 describes the repository user connection details: Table 2-8. Repository User Connection Details Property
Description
User
User name associated with the connection.
Connection ID
Identification number assigned to the repository connection.
Application
Repository client application associated with the connection.
Host Name
Name of the machine running the application.
Host Address
TCP/IP address of the machine associated with the connection.
Host Port
Port number the machine hosting the repository client application uses to communicate with the repository.
Login Time
Time the user connected to the repository.
Last Active Time
Time of the last metadata transaction between the repository client application and the repository.
To view user connection details: 1.
Launch the Repository Manager and connect to the repository.
2.
Click Edit > Show User Connections. The Repository Connections dialog box appears.
3.
58
To sort the connections by column, click the column name.
Chapter 2: Using the Repository Manager
Viewing Locks You can view locks and identify residual locks in the Repository Manager or in the Administration Console. Table 2-9 describes the object lock information in both the Repository Manager and the Administration Console: Table 2-9. Object Lock Properties Column Name
Description
User
User name locking the object.
Connection ID
Identification number assigned to the repository connection.
Folder
Folder in which the locked object is saved.
Object Type
Type of object, such as folder, version, mapping, or source.
Object Name
Name of the locked object.
Lock Type
Type of lock: in-use, write-intent, or execute.
Lock Time
Time the lock was created.
Hostname
Name of the machine locking the object.
Application
Application locking the object, such as Designer, Workflow Manager, Repository Manager, or Integration Service.
To show all repository locks: 1.
In the Repository Manager, connect to a repository.
2.
To view all locks in the repository, click Edit > Show locks. The Object Locks dialog box appears.
3.
To sort the view of the locks by column, click the column name.
4.
To view updated lock information, click Refresh.
Managing User Connections and Locks
59
Closing User Connections and Releasing Locks Sometimes, the Repository Service does not immediately disconnect a user from the repository. The repository has a residual connection when the repository client application or machine is shut down but the connection remains in the repository. This can happen in the following situations: ♦
Network problems occur.
♦
A PowerCenter Client, Integration Service, repository, or database machine shuts down improperly.
A residual repository connection also retains all repository locks associated with the connection. If an object or folder is locked when one of these events occurs, the repository does not release the lock. This is called a residual lock. If a system or network problem causes a repository client application to lose connectivity to the repository, the Repository Service detects and closes the residual connection. When the Repository Service closes the connection, it also releases all repository locks associated with the connection. When possible, allow the Repository Service to detect and release residual locks. You can also use the Repository Manager or Administration Console to manually close residual user connections and release residual locks in the repository. The Integration Service opens additional connections to the repository for each Integration Service process and DTM process. If you close a repository connection to an Integration Service, the Repository Service also closes all other connections to the same Integration Service. You do not need special privileges to terminate connections associated with a repository user name. For more information about the privileges and permissions to terminate other user connections and unlock objects, see “Repository Manager Tasks” on page 373. Warning: Closing an active connection may cause repository inconsistencies. Close residual connections only. To manually close a connection in the Repository Manager: 1.
Launch the Repository Manager and connect to the repository.
2.
Click Edit > Show User Connections.
3.
In the Repository Connections dialog box, select the connection you want to terminate.
4.
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” on page 59.
5.
Verify that the user is not connected to the repository.
6.
Click End Connection. The Repository Service closes the user connection and releases all locks associated with the connection.
60
Chapter 2: Using the Repository Manager
7.
Click Close to return to the Repository Manager.
Tip: To avoid repository inconsistencies, before unlocking an object or folder, determine who
owns the lock and make sure the owner is not using the object. Before unlocking multiple objects or closing multiple user connections, ask all users to exit the repository.
Managing User Connections and Locks
61
62
Chapter 2: Using the Repository Manager
Chapter 3
Managing Users and Groups This chapter includes the following topics: ♦
Overview, 64
♦
User Groups, 65
♦
User Authentication, 68
♦
Creating and Editing Repository Users, 71
♦
Repository Privileges, 79
♦
Permissions, 85
♦
Tips, 88
♦
Troubleshooting, 91
63
Overview PowerCenter offers several features that enable you to manage users and groups: ♦
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 names 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. Use an external directory service to manage user names and passwords.
♦
Repository privileges. Ability to perform actions within the repository and to run the Integration Service. 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 particular folder.
♦
Folder permissions. 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. Most tasks also require the appropriate repository privileges.
♦
Permissions on global objects. Ability to use global objects. Global objects include labels, deployment groups, queries, and connection objects. You can grant global object permissions to users and groups.
Take time to plan an overall strategy so that you can implement appropriate user groups and security measures for the repository.
64
Chapter 3: Managing Users and Groups
User Groups You create custom user groups to manage users and repository privileges efficiently. After creating a new user group, you assign that group a set of privileges. Each repository user must be assigned to at least one user group. When you assign a user to a group, the user: ♦
Receives all group privileges.
♦
Inherits any change to group privileges.
♦
Loses and gains privileges if you change the user group membership.
You can also assign users to multiple groups. This grants the user the privileges of each group. Note: When you revoke a privilege from a group, you revoke the privilege from each user in
the group. However, if a user has been granted the privilege individually (as with default privileges), you must revoke the privilege individually to restrict that user. For more information, see “Repository Privileges” on page 79. Use the Repository Manager to create and edit repository user groups. For more information about the privileges and permissions to administer repository user groups see “Repository Manager Tasks” on page 373.
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 create additional groups and assign privileges and permissions to those groups. There are two default repository user groups: ♦
Administrators. This group initially contains two users that are created by default. The default users are Administrator and the database user that created the repository. You cannot delete these users from the repository or remove them from the Administrators group.
♦
Public. The Repository Manager does not create any default users in the Public group.
You cannot delete these groups from the repository or change the default privileges. For more information about default privileges, see “Default Privileges” on page 80.
Owner’s Group Permissions You can define Owner’s Group permissions when you create or edit a folder. You can grant Owner’s Group permissions to one of the groups to which the folder owner belongs. If the owner belongs to more than one group, you must select one of the listed groups to receive Owner’s Group permissions. For example, if the owner of a folder belongs to one group, Developer, the Developer group receives Owner’s Group permissions on the folder. If you assign read and write folder User Groups
65
permissions to the Owner’s Group, then every user in the Developer group has read and write permission for the folder. If the owner of the folder belongs to both the Developer group and the Production group, you must choose one of those groups to receive Owner’s Group permissions. If you select the Production group, the Production group receives read and write permissions on the folder.
Creating a User Group Complete the following steps to create a user group. To create a user group: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Click the Groups tab.
4.
Click Add.
5.
Enter the name of the group.
6.
Click OK. The new group now appears in the list of all groups defined for the repository.
66
Chapter 3: Managing Users and Groups
7.
Click OK to return to the Repository Manager.
You can now assign privileges and users to the group.
Editing a User Group You can edit the description of an existing user group at any time. However, you cannot edit the default groups, Public and Administrators. To edit a user group: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select a group on the Groups tab and click Edit.
4.
Edit the description and click OK. You can enter up to 2,000 characters. The first 256 characters appear in the Manage Users and Privileges window.
5.
Click OK again to save the changes.
Deleting a User Group You can delete any user group in the repository except the default repository user groups, Public and Administrators. Note: If you delete a group that contains users, the Repository Manager reassigns those users to
the Public group. To delete a user group: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select the group in the Groups tab that you want to delete.
4.
Click Remove. A message appears stating all users in the group will be assigned to the Public group.
5.
Click OK.
6.
Click OK to save the changes.
User Groups
67
User Authentication Each repository user needs a user name and password to access the repository. PowerCenter uses one of the following methods to authenticate users: ♦
PowerCenter default authentication
♦
Lightweight Directory Access Protocol (LDAP) authentication
When you install PowerCenter, the PowerCenter installation program configures each repository to use repository authentication. If you want to use LDAP authentication for a repository, you must change the authentication method after you complete the PowerCenter installation. You can create users and maintain passwords in the repository with PowerCenter default authentication. The security module verifies users against these user names and passwords. LDAP defines a network protocol for accessing a directory service. If you use LDAP to authenticate users, the repository security module passes a user login to the external directory for authentication. To accomplish this, the repository maintains an association between repository user names and external login names. The repository administrator maintains the user-name/login associations, but it does not maintain user passwords in the repository. If you use an external directory service, you must ensure that the Administrator has a valid external login name when you register the authentication module with the repository. For more information about registering a plug-in, see “Managing the Repository” in the Administrator Guide. Tip: If you use default authentication, change the Administrator password immediately after
creating the repository to protect the metadata. For information about the privileges and permissions to administer repository users, see “Repository Manager Tasks” on page 373.
Using Default Authentication By default, each repository in a domain uses repository authentication to authenticate users that log in to the repository. Users log in to the repository through the PowerCenter Clients. When a user logs in, the Repository Service authenticates the user name and password against the user accounts created for the repository. The repository administrator uses the Repository Manager to create users and set user permissions for the repository. If you use default authentication, repository users can have one of the following statuses:
68
♦
Enabled. The user name is valid for accessing the repository. New users receive the enabled status.
♦
Disabled. The user cannot access the repository. A user receives this status if the repository administrator disables the user.
Chapter 3: Managing Users and Groups
Using LDAP Authentication You can use LDAP authentication on one or more repositories in a domain. LDAP defines a network protocol for accessing a directory service. If you use LDAP to authenticate users, the repository security module passes a user login to the external directory for authentication. If you use LDAP authentication for repository users, the repository maintains an association between repository user names and external login names. When you create a user, you can select the login name from the external directory. If you know the directory login name, use the pmrep Registeruser command to create the user name and associated login name. For more information about Registeruser, see “pmrep Command Reference” in the Command Line Reference. For example, you might deploy a repository to a production server. A repository user called JSmith might have a directory login name JohnS on the production server. You must associate JSmith with the directory login name JohnS for the user to access the repository. For more information about associating a user name with a login name, see “Enabling a User” on page 76. When you view users in the repository, you can see the repository user names and the directory login names. Figure 3-1 shows the repository user names and associated login names: Figure 3-1. Repository User Names and External Login Names
User Status Login Name Repository User Name
The user status indicates if a user can access the repository.
User Authentication
69
Table 3-1 describes the user statuses: Table 3-1. User Statuses Status
Description
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. A repository administrator must explicitly enable the user by linking the user name to the login name.
Suggested
The user name is in the repository, but is not linked to a login name (as above) in the external directory. This status is similar to “no login assigned” except that the security module finds a possible matching login name that you can enable.
Account Removed
The user name is no longer on the external directory, and the user cannot access the repository. For example, if the login changes in the external directory, the security module cannot find the login name. The status changes to “account removed.” The repository administrator must explicitly enable you by linking a repository user name to a new login name in the external directory.
User status changes for the following reasons:
70
♦
The system administrator enables or disables it.
♦
The login changes in the LDAP directory.
♦
The user authentication mode changes between LDAP and default authentication.
Chapter 3: Managing Users and Groups
Creating and Editing Repository Users In the Repository Manager, you create a user name for each user accessing the repository. Each user belongs to at least one user group. When you create a user, the Repository Manager assigns the user to the Public group. To change the group, you must first add the user to another group and then remove the user from the Public group. Tip: Before creating repository users, create user groups, and assign the appropriate privileges
to those groups. For more information about groups, see “User Groups” on page 65. To manage repository users, you must have the Admin Repository privilege.
Creating a User Under Default Authentication If you use default user authentication, you enter user names in the repository and assign a password for each user name you create. To create a user under default authentication: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges. The Manage Users and Privileges dialog box appears.
3.
Click Add. The New User dialog box appears.
Creating and Editing Repository Users
71
4.
Enter a user name and password between 1 and 75 characters long, with no leading or trailing spaces. Use the optional Description and Contact Info fields to further identify the user.
5.
Click Group Memberships.
The Member Of list displays the groups that the user belongs to. 6.
72
To add the user to a group, select the group in the Not Member Of list, and click Add.
Chapter 3: Managing Users and Groups
The group appears in the Member Of list.
7.
To remove the user from a group, select the group in the Member Of list, and click Remove. Note: You cannot remove a user from a group when the user belongs to one group.
8.
Click OK.
Editing a User Password If you use default authentication, you can edit the user password. Note: If you change the password for the repository administrator, you must update
environment variables and pmcmd commands that use the repository administrator password. Replace the existing repository password with the new password. For information about the privileges and permissions to edit a password see “Repository Manager Tasks” on page 373. To edit a password: 1.
In the Repository Manager, connect to the repository.
2.
Click Security > Change Current Password.
Creating and Editing Repository Users
73
3.
Enter the old password.
4.
Enter the new password twice to confirm it.
5.
Click OK.
Creating a Repository User Under an External Directory Service If you use an external directory service for maintaining repository users, you add repository users from a list of login names from the external directory. You do not create repository user passwords. To add users with an external directory service: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Click Add. The Add Users dialog box displays a list of names from the external directory service.
4.
Select a login name from the external directory list and click Add.
The login name appears at the bottom of the dialog box. If you select more than one name, the names appear at the bottom separated by semicolons. Note: You can type a name at the bottom of the dialog box, but it must match a valid
login name in the directory. To check the spelling, click Check Names.
74
Chapter 3: Managing Users and Groups
5.
If any of the names you enter do not match a valid directory service login, you must correct the name or remove it from the selections on the Invalid Name dialog box. Click OK.
6.
Click OK in the Add Names dialog box to add the selections to the user-name/loginname association. The Manage Users and Privileges window displays the user name, login name, and enabled status.
For more information about adding a user to a group or editing a user description, see “Editing a User” on page 75.
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. The following exceptions apply when you edit users: ♦
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: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select a user and click Edit. The Edit User dialog box appears. If you use default authentication, you can change the password.
4.
To change the password, enter the new password twice. The password can be between 1 and 75 characters long, with no leading or trailing spaces. Passwords must be in 7-bit ASCII. Creating and Editing Repository Users
75
5.
To edit the description, enter up to 2,000 characters. The first 256 characters appear in the Manage Users window.
6.
To edit group memberships, click Group Memberships. If the user belongs to one group, you must add the user to another group before removing the user from the original group.
7.
To add a group membership, select the group in the Not Member Of list, and click Add. The group appears in the Member Of list.
8.
To remove the user from a group, select the group in the Member Of list, and click Remove. The selected group appears in the Not Member Of list.
9.
To save the changes, click OK.
10.
Click OK again.
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 the repository user name with the directory login name. When you enable a user under default authentication, the status changes. To enable a user: 1.
Click Security > Manage Users and Privileges. The Manage Users and Privileges dialog box appears.
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 appears. This dialog box displays a list of valid login names from the external directory service. It appears if you use an external directory service.
If a user has a suggested login name, you enable the association immediately when you click Enable. To associate the user name with a different login name, you can disable and then enable the user. You can also use the pmrep Edituser command. For more
76
Chapter 3: Managing Users and Groups
information about Edituser, see “pmrep Command Reference” in the Command Line Reference.
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 appears 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. To disable a repository user: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select the users you want to disable. You can select multiple users at a time.
4.
Click Disable. The user status changes to disabled.
You can also use the pmrep Edituser command to disable users from the command line. For more information about disabling users from the command line, see “pmrep Command Reference” the Command Line Reference.
Removing a Repository User When you remove a user from a repository that uses an external directory service, you remove the user name in the user-name/login association. If the repository uses default authentication, you remove the user name from the repository. Creating and Editing Repository Users
77
Note: If a repository user has an execute lock on a workflow, you cannot remove the user. To
remove the user, you must stop the workflow or wait until the execute lock is released. To remove a repository user:
78
1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Select a user and click Remove.
4.
Click Yes to confirm that you want to remove the user.
Chapter 3: Managing Users and Groups
Repository Privileges The Repository Manager grants a default set of repository privileges to each new user and group. You can add or remove privileges from any user or group except: ♦
Administrators and Public groups (the default read-only repository groups)
♦
Administrator user and database user who created the repository (the users created in the Administrators group)
You can grant privileges to groups or to individual users. A privilege granted to an individual user remains with the user until you remove it. For example, if you move a user from a group that has the Admin Repository privilege into a group that does not, the user loses the Admin Repository privilege. However, if you grant the Admin Repository privilege to the user, the user retains this privilege regardless of changes in group membership. You can perform some repository tasks, such as creating user groups, with repository privileges only. Folder related tasks, however, generally require one or more folder permissions in addition to the related repository privilege to perform the task. Global objects have separate read, write, and execute permissions. For more information about global object permissions, see “Configuring Permissions on Global Objects” on page 86. For tighter security, grant the Super User privilege to an individual user, not an entire group. This limits the number of users with the Super User privilege and ensures that the user retains the privilege even if you remove the user from a group. For a list of common repository tasks and the permissions and privileges necessary to perform those tasks, see “Permissions and Privileges by Task” on page 367.
Repository Privileges
79
Default Privileges The Repository Manager grants each new user and new group the default privileges. Table 3-2 lists the default repository privileges: Table 3-2. Default Repository Privileges Default Privilege
Permission
Permission Object
Grants You the Ability to
Browse Repository
n/a
n/a
- Add and remove reports. - Change a user password. - Connect to the repository using the Repository Manager. - Import, export, or remove the registry. - Search by keywords.
Read
Folder
- Browse repository. - Copy a folder. You must also have Admin Repository or Super User privilege in the target repository. - Compare folders. - Edit folder properties for folders you own. - Freeze folders you own. - Unlock objects and folders locked by a user name. - View dependencies.
Read
Query
- View query.
Execute
Query
- Run query.
Write
Query
- Create or edit query.
n/a
n/a
- Configure connection information. - Connect to the repository using the Designer. - Perform Use Repository Manager tasks in the Designer.
Read
Folder
- Copy objects from the folder. - Create shortcuts to objects in the folder. - Export objects. - View objects in the folder.
Read/Write
Folder
- Copy objects into the folder. - Create or edit metadata. - Create shortcuts from shared folders. - Import objects.
n/a
n/a
- Remove label references.
Write
Deployment group
- Delete from deployment group.
Use Designer*
Use Repository Manager
80
Chapter 3: Managing Users and Groups
Table 3-2. Default Repository Privileges Default Privilege
Use Workflow Manager*
Permission
Permission Object
Grants You the Ability to
Write
Folder
- Change object version comments if not the owner. - Change status of the object. - Check in. - Check out/undo check-out. - Delete objects from folder. - Mass validation (Needs write permission if options selected.) - Recover after delete.
Read
Folder
- Export objects.
Read Write
Folder Deployment group
- Add to deployment group.
Read Write
Original folders Target folder
- Copy objects. - Import objects.
Read Write/ Execute
Folder Label
- Apply label.
n/a
n/a
- Connect to the repository using the Workflow 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.
Read/Write
Connection
- Edit database, FTP, and external loader connections in the Workflow Manager.
Execute
Folder
- Abort workflow. - Restart workflow. - Recover suspended workflow. - Stop workflow.
Read
Folder
- Export objects. - View session details and session performance details. - View sessions. - View tasks. - View workflows.
Read
Folder
- View session log. - View workflow log.
Read/ Execute
Connection
- Schedule or unschedule workflows. - Start workflows immediately.
Read/Write
Folder
- Create and edit workflows and tasks. - Import objects. - Validate workflows and tasks.
Repository Privileges
81
Table 3-2. Default Repository Privileges Default Privilege
Permission
Permission Object
Grants You the Ability to
Read/Write Read
Folder Connection
- Create and edit sessions.
* The Use Designer and Use Workflow Manager privileges enable you to perform many of the tasks that you can perform in the Repository Manager with the Use Repository Manager privilege.
Extended Privileges In addition to the default privileges, the Repository Manager provides extended privileges that you can assign to users and groups. The Repository Manager grants extended privileges to the Administrators group by default. Table 3-3 lists the extended repository privileges: Table 3-3. Extended Repository Privileges Extended Privilege
Permission
Permission Object
n/a
n/a
- Create, upgrade, backup, delete, and restore the repository. - Manage passwords, users, groups, and privileges. - Start, stop, enable, disable, and check the status of the repository.
Write
Folder
- Check in or undo check out for other users. - Purge (in version-enabled repository).
Admin Integration Service
n/a
n/a
- Disable the Integration Service using the infacmd program. - Connect to the Integration Service from PowerCenter client applications when running the Integration Service in safe mode.
Super User
n/a
n/a
- Perform all tasks, across all folders in the repository. - Manage connection object permissions. - Manage global object permissions. - Perform mass validate.
Workflow Operator
n/a
n/a
- Connect to the Integration Service.
Read
Folder
- View the session log. - View the workflow log. View session details and performance details.
Execute
Folder
- Abort workflow. - Restart workflow. - Resume workflow. - Stop workflow. - Schedule and unschedule workflows.
Read Execute
Folder Connection
- Start workflows immediately.
Admin Repository
82
Chapter 3: Managing Users and Groups
Grants You the Ability to
Table 3-3. Extended Repository Privileges Permission
Permission Object
Grants You the Ability to
Execute Execute
Folder Connection
- Use pmcmd to start workflows in folders for which you have execute permission.
Manage Connection
n/a
n/a
- Create and edit connection objects. - Delete connection objects. - Manage connection object permissions.
Manage Label
n/a
n/a
- Create labels. - Delete labels.
Read/Write
Label
- Edit labels. - Manage label permissions.
n/a
n/a
- Create folders. - Delete folders.
Read
Folder
- Edit folder properties. - Freeze folders.
Read
Folder
- Copy folders.
Read/ Execute
Deployment group
- Deploy deployment groups. - Roll back deployment groups.
Read/ Execute
Deployment group
- Create and edit deployment groups. - Delete deployment groups. - Manage deployment group permissions.
Extended Privilege
Manage Folder
Deploy
Manage Deployment Group
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. Reserve extended privileges for individual users and grant default privileges to groups.
Assigning and Revoking a Privilege You can assign and revoke repository privileges of a user or group. When you change privileges for a group, you change the privileges granted to every user in the group. However, users retain individually granted privileges until you revoke them. For information about the privileges and permissions to assign or revoke privileges, see “Repository Manager Tasks” on page 373. Note: You cannot change the privileges of the default user groups or the default repository
users. To assign a privilege to a user or group: 1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Click Privileges. Repository Privileges
83
4.
Select the privileges you want to assign to each user or group.
5.
Click OK to save the changes.
Note: If you assign Super User privileges to a user, you cannot change the other privileges for
that user. Super User privilege enables all privileges for the user. To revoke a privilege from a user or group:
84
1.
In the Repository Manager, connect to a repository.
2.
Click Security > Manage Users and Privileges.
3.
Clear the privileges you want to revoke.
4.
Click OK to save the changes.
Chapter 3: Managing Users and Groups
Permissions You can maintain user and group permissions for access to folders and global objects. Global objects are labels, deployment groups, queries, and connections. You can maintain the following permissions for each type of object: ♦
Read permission. You can view the folders and objects.
♦
Write permission. You can create or edit objects in a folder, maintain queries or labels, add or delete objects from deployment groups.
♦
Execute permission. You can run or schedule a workflow in the folder, run queries, apply labels, or copy deployment groups.
To perform a task you must have the privilege to perform the task and the applicable permission. For example, you might have the Use Designer privilege to connect to the repository through the Designer, but you must also have folder read and write permission to open and edit a mapping in a folder. If you do not have both the privilege and permissions, you cannot open or edit mappings in that folder.
Configuring Folder Permissions Some tasks require fewer folder permissions with an extended repository privilege than with a default repository privilege. For example, if you have the Use Workflow Manager default privilege, you must have both read and execute permission to start a workflow in a folder. If you have the Workflow Operator extended privilege, you can start a workflow if you have read permission. The Super User privilege is not restricted by any folder permissions. If you have the Super User privilege, you do not require any permissions. You can grant folder permissions at three levels. Table 3-4 lists the folder security levels: Table 3-4. Folder Object Security Levels Level
Includes
Owner
The owner of the folder, as listed in the owner menu.
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.
Repository
All groups and users in the repository.
Each permission level includes the members of the level above it. For example, if you grant 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. You can edit folder permissions and properties at any time. To create, edit, and delete folders, you must have the Manage Folder privilege.
Permissions
85
For more information about the privileges and permissions to edit folder properties, see “Repository Manager Tasks” on page 373. To edit folder permissions and properties: 1.
In the Repository Manager, connect to a repository.
2.
Select the folder in the Navigator. If the folder does not appear in the Navigator, you do not have read permission for the folder.
3.
Click Folder > Edit.
4.
If necessary, select a new owner from the Owner menu.
5.
If the owner belongs to more than one group, select a group from the Group menu.
6.
Edit the folder permissions.
7.
Click OK to save the changes.
Configuring Permissions on Global Objects To configure and manage permissions on a global object, you must be the owner of the global object or you must have the relevant extended privilege. For example, you must have the Manage Connection privilege to manage a connection object, or you must be the owner of the connection object. The initial owner of a global object is the user who creates the object. The Super User privilege gives a user all extended privileges. For more information about configuring connection object permissions, see “Managing Connection Objects” in the Workflow Administration Guide. You cannot assign permissions on a private query. To enable others to use it, change the query type to public. When you assign permissions on global objects, you can assign them on three levels. Table 3-5 lists global object security levels: Table 3-5. Global Object Security Levels Level
Includes
World
All repository users.
Users
Object owner and other users that have been added to the permissions list. By default, the owner is the creator of the object.
Groups
Owner’s group and other groups that have been added to the permissions list. If a group receives permissions, every user in a group receives the permissions.
Each global 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.
86
Chapter 3: Managing Users and Groups
When you configure permissions on a global object, 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 the Super User privilege receive all permissions by default.
For information about tasks you can perform with user privileges, permissions on folders, and permissions on global objects, see “Repository Privileges” on page 79. To configure permissions on global objects, select a global object in a global objects browser such as the Label Browser, and click Permissions.
Click to define permissions.
The Permissions dialog box appears.
Change owner. Change group. Add a new group or user. You cannot change permissions of users with Super User privilege and users belonging to the Administrators group.
Permissions
87
Tips When setting up repository users, groups, and security, keep it simple. Securing the environment involves the following basic principles: ♦
Limiting users
♦
Restricting privileges
♦
Defining permissions
Before implementing security measures, answer the following questions: ♦
Who needs access to the repository? What do they need the ability to do?
♦
Where can I limit repository privileges by granting folder permissions instead?
♦
Who creates transformations and mappings? Do they need access to all folders?
♦
Who schedules workflows?
♦
Who needs to start workflows manually? Do they need to access all workflows in the repository?
♦
Who administers the repository?
♦
Who starts and stops the Integration Service?
♦
Who needs the ability to perform all functions within the repository, across all folders?
After you evaluate the needs of the repository users, you can create appropriate user groups, limit privileges, and limit folder permissions. Create groups with limited privileges. The simplest way to prevent security breaches is to limit the number of users accessing the repository. Then, limit the ability of other repository users to perform unnecessary actions, such as running sessions or administering the repository. To do this, determine how many types of users access the repository. Then create separate user groups for each type. The more distinct the user groups, the tighter the repository security. After you establish separate groups, assign the appropriate privileges to those groups and design folder permissions to allow their access to particular folders. Do not use shared accounts. Using shared accounts negates the usefulness of the repository locking feature. The repository creates locks on objects in use. Breaking a valid lock can cause repository and inconsistencies. For more information about locking, see “Managing User Connections and Locks” on page 55. Limit user and group access to multiple repositories. When working in a multiple repository environment (PowerCenter only), limit the number of users and groups accessing more than one repository. This becomes more important when repositories contain folders with the same or similar names. Restricting the number of 88
Chapter 3: Managing Users and Groups
crossover users limits the possibility of a user connecting to the wrong repository and editing objects in the wrong folder. Customize user privileges. If a single user requires more privileges than those assigned to the user's group, and you need to keep the user in that group for the purpose of folder permissions, you can add individual privileges to that user. For example, if you have a user working in the Developers group, but this user also needs to deploy folders and deployment groups, you can add the Deploy privilege to the individual user. Limit the Super User privilege. The Super User privilege permits you to perform any task despite folder-level restrictions. This includes starting any workflow, and unlocking other user's locks. To protect the repository and target data, restrict the number of users who need this all-encompassing privilege. You can allow users a limited ability to run workflows by granting the Use Workflow Manager privilege with read and execute permission. You can allow users a limited ability to unlock locks by granting them the Browse Repository or Admin Repository privilege. Users with either the Browse Repository or Admin Repository privilege can unlock any object or folder locked by their own user name. All members of the Administrators group have the Super User privilege. Therefore, you must limit the number of users you assign to the Administrators group. Limit the Deploy privilege. The Deploy privilege permits a user to copy a folder from one repository to another. Because this feature is used to deploy folders into production, you should limit this privilege in production repositories. Restrict the Workflow Operator privilege. With the Workflow Operator privilege, 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 the 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 execute permission for the folder.
Tips
89
Grant the Manage Connection privilege to repository administrators. You need the Manage Connection privilege to create and edit connection objects. If a repository administrator performs these tasks and does not have the Super User privilege, grant the privilege either to the individual user or to the Administrators group. If you grant the Manage Connection privilege to the Public group, all users can create and edit connection objects.
90
Chapter 3: Managing Users and Groups
Troubleshooting The following solutions might help you with managing users and groups: After creating users and user groups, and granting different sets of privileges, I find that none of the repository users can perform certain tasks, not 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 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 Admin Repository privilege, but I cannot access a repository using the Repository Manager. To perform tasks in the Repository Manager with the Admin 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
91
92
Chapter 3: Managing Users and Groups
Chapter 4
Working with Folders
This chapter includes the following topics: ♦
Overview, 94
♦
Folder Properties, 96
♦
Configuring a Folder, 99
♦
Comparing Folders, 102
93
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 and to help you logically organize the repository. Each folder has a set of configurable properties that enable 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.
Using Folders in the Repository Manager You create and maintain folders in the Repository Manager. In the Repository Manager, you can view the users accessing folders and the objects within each folder. You can also copy and replace folders within the repository or across repositories.
Using Folders in the Designer In the Designer, you use folders to store sources, transformations, cubes, dimensions, mapplets, business components, targets, and mappings. When you create a mapping in a folder, you can include any object in the folder, and you can create shortcuts to objects in shared folders. You can copy objects from one folder to another. If you want to use an object in a non-shared folder, you can copy it into the working folder. If you work with multiple repositories, you can also copy objects across repositories.
Using Folders in the Workflow Manager In the Workflow Manager, you use folders to store workflows, tasks, and sessions. When you create a workflow, you can include any session or task in the folder. Use the Copy Wizard to copy individual workflows to other folders. To copy all workflows within a folder to a different location, you can copy the entire folder. Use any mapping in a folder to create a session in that folder. You can copy a session within a folder or to another folder.
Organizing Folders Folders are designed to be flexible. They enable you to organize the repository logically. Keep in mind that any mapping in a folder can use those objects that are stored in the same folder or that are stored in a shared folder and accessed through a shortcut.
94
Chapter 4: Working with Folders
In a repository, you might create folders for each development project, subject area, user, or type of metadata. For example: ♦
You might create a single folder for each type of data. To organize accounting data, you might create one folder for accounts payable and another for accounts receivable.
♦
You can create a folder for each repository user, designed to store work for that user. If users work on separate projects, this technique avoids any problems that might occur if two people attempt to edit the same metadata at the same time.
♦
You might create a different folder for each type of metadata (source definitions, target definitions, mappings, schemas, and reusable transformations) that you create through the Designer.
Before creating a system of folder organization, you need to understand the security measures associated with folders so you can best protect repository objects.
Overview
95
Folder Properties Each folder has several configurable properties on the folder property sheet. 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 about changing the status of all objects in a folder, see “Working with Version Properties” on page 135.
Permissions Permissions allow repository users to perform tasks within a folder. With folder permissions, you control user access to the folder, and you control the tasks that users can 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. You can view the folder and objects in the folder.
♦
Write permission. You can create or edit objects in the folder.
♦
Execute permission. You can 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 more information about how folder permissions interact with repository privileges, see “Managing Users and Groups” on page 63. For more information about permission and privilege combinations that allow you to perform each task, see “Permissions and Privileges by Task” on page 367.
96
Chapter 4: Working with Folders
Permission Levels You can grant three levels of security when you use folder permissions. Table 4-1 lists the users included in each permission level: Table 4-1. Folder Permissions Permission Level
Includes
Owner
Owner of the folder.
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.
Repository
All users and groups in the repository.
Each permission level includes the members in the level above it. If you restrict a permission from Owner or Owner’s Group and then grant the same permission to Repository, 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.
Folder Owner and Owner's Group Because you grant permissions to Owner and Owner’s Group, the choices for these settings affect how repository users access objects within the folder. When you create a folder, you can select any user in the repository to be the folder owner. If the folder owner belongs to more than one repository group, you can also choose a repository group as the Owner’s Group. If the owner belongs to one group, that group becomes the Owner’s Group. For example, the repository contains users in two user groups. You want a folder allowing full access to one group while limiting access to the other. To do this, you make a user in the fullaccess group the owner of the folder, grant all folder permissions to Owner and Owner’s Group, and then restrict Repository permissions. As long as a group does not have the Super User privilege, restricting Repository permission limits that group’s folder permissions. The owner of the folder has an additional ability to edit the folders properties as long as the owner has the Browse Repository privilege and read permission on the folder. Any other user must have Admin Repository and read permission, or the Super User privilege to edit folder properties.
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, such as an Expression transformation that calculates sales commissions, you can place the object in a shared folder. You can then access the object from other folders by creating shortcuts to the object.
Folder Properties
97
Shortcuts inherit changes to the original object. So if, for example, you change the way an organization calculates sales commissions, you can change the Expression transformation in the shared folder. Then all shortcuts to the Expression transformation inherit the changes. If you want to use an object in a shared folder without inheriting any future changes, you can copy the existing object. Note: After you make a folder shared, you cannot reverse it.
Shared Folders in Global Repositories Shared folders in global repositories can be used by any folder in the domain. For example, if you are working in a folder in a local repository, you can connect to the global repository and create a shortcut to a shared folder for the official sales commission Expression transformation. As with local shared folders, if changes are made to the original object, the repository updates all shortcuts in the domain to reflect those changes.
98
Chapter 4: Working with Folders
Configuring a Folder Each folder in the repository must have the following information configured in the folder properties dialog box: ♦
Folder name. The name of the folder in the repository.
♦
Folder owner. The owner can have a different level of permissions within the folder, separate from general users, and the ability to administer the folder.
♦
Owner’s group. The group selected can also have a different level of permissions in the folder.
♦
Folder status. Specifies a status applied to all objects in the folder. Each status defines the ability of users to check out and edit objects in the folder and whether copy deployment group operations can create new versions of objects in the folder.
♦
Folder permissions. Defines the ability of users and groups to access the folder.
♦
Allows shortcuts. Determines whether the folder is shared.
You can optionally enter a description of the folder. You can then view these comments in the Repository Manager. Warning: Do not include the period character ( . ) in folder names. Folder names with periods can cause errors when you run sessions.
Creating a Folder For information about the privileges and permissions to create a folder, see “Repository Manager Tasks” on page 373.
Configuring a Folder
99
To create a folder: 1.
In the Repository Manager, connect to the repository.
2.
Click Folder > Create.
3.
Enter the following information:
4.
100
Folder Properties
Required/ Optional
Name
Required
Folder name. Do not use the period character ( . ) in folder names. Folder names with periods can cause errors when you run sessions.
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. Groups to which the owner belongs can be selected.
Allow Shortcut
Optional
If selected, makes the folder shared.
Status
Required
Status applied to all objects in the folder. This option applies to versioned repositories. For more information about object status, see “Working with Version Properties” on page 135.
Permissions
Required
Folder permissions for users in the repository. For more information, see “Permissions” on page 96.
Click OK.
Chapter 4: Working with Folders
Description
The folder appears in the Navigator. If the folder is shared, the folder displays an open hand icon.
Editing a Folder For information about the privileges and permissions to edit a folder, see “Repository Manager Tasks” on page 373. Note: The Repository Service updates changes in folder properties immediately. To avoid
repository inconsistencies due to changes in folder properties, make sure no users are accessing the folder when you edit the folder. To edit a folder: 1.
In the Repository Manager, connect to a repository and select a folder.
2.
Click Folder > Edit.
3.
Enter the changes, and click OK.
Deleting a Folder If a folder becomes obsolete, you can delete that folder from the repository. For information about the privileges and permissions to delete a folder, see “Repository Manager Tasks” on page 373. To delete a folder: 1.
In the Repository Manager, connect to a repository and select a folder.
2.
Click Folder > Delete.
3.
In the confirmation message that appears, click OK.
Configuring a Folder
101
Comparing Folders Before you copy or replace a folder in a repository, you might want to verify the contents of a folder or compare it with other folders. The Repository Manager lets you quickly and accurately compare the objects in different folders using the Compare Folders Wizard. If you use a versioned repository, the Repository Manager uses the latest checked in version of an object for comparison. In the Compare Folders Wizard, you can complete the following comparisons: ♦
Compare objects between two folders in the same repository.
♦
Compare objects between two folders in different repositories.
You can specify the following comparison criteria for each comparison: ♦
Object types to compare. You can specify the object types to compare and display between folders. The wizard compares objects based on specific object attributes. See Table 4-2 on page 102 for a list of compared attributes for object types.
♦
Direction of comparison. The wizard performs directional comparisons. A directional comparison checks the contents of one folder against the contents of the other. You can specify either one-way or two-way comparisons.
The wizard displays the following information: ♦
Similarities between objects
♦
Differences between objects
♦
Outdated objects
You can edit and save the result of the comparison. You must have read permission for each folder you want to compare. You must also have privileges to access the repositories containing the folders. You can also compare two objects of the same type using Compare Objects. For more information about Compare Objects, see “Comparing Objects” in the Designer Guide.
Compared Attributes and Object Differentiation The Compare Folders Wizard compares objects based on specific object attributes. Table 4-2 lists the object types and attributes you can compare: Table 4-2. Compared Object Types and Attributes
102
Object Type
Compared Attribute
Sources
Source name and database name
Targets
Target name and database name
Reusable transformations
Transformation name and type
Chapter 4: Working with Folders
Table 4-2. Compared Object Types and Attributes Object Type
Compared Attribute
Mappings
Mapping name
Mapplets
Mapplet name
Source fields
Column names
Target fields
Column names
Reusable transformation fields
Port names
Sessions
Session name
Session components
Component value
Tasks
Task name
Task instances
Task instance name
Workflows
Workflow name
Workflow events
Workflow event name
Workflow variables
Workflow variable name
Worklets
Worklet name
Shortcuts
Shortcut name and object type
Transformation instances
Transformation instance name and type
Mapping variables
Mapping variable name
External procedure initialization properties
Property name
Schedulers
Scheduler name
Configurations
Configuration name
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 4-3 lists objects the wizard compares by default when you select certain objects to compare: Table 4-3. Compared Objects in Compare Selected Object
Compared Object
Source field
Source
Target field
Target
Reusable transformation field
Reusable transformation
Mapping variable
Mapping
External procedure initialization properties
Transformation instance
Session component
Session
Comparing Folders
103
Table 4-3. Compared Objects in Compare Selected Object
Compared Object
Task Instance
Workflow and worklet
Workflow event
Workflow and worklet
Workflow variable
Workflow and worklet
The wizard compares the attribute of each object in the source folder with the attribute of each object in the target folder. 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.
One-Way and Two-Way Comparisons Comparison results depend on the direction of the comparison. One-way comparisons check the selected objects of Folder1 against the objects in Folder2. Two-way comparisons check objects in Folder1 against those in Folder2 and also check objects in Folder2 against those in Folder1. A two-way comparison can sometimes reveal information a one-way comparison cannot. A one-way comparison does not note a difference if an object is present in the target folder but not in the source folder. Figure 4-1 shows two folders, ADS1 and ADS2, in the same repository. If you compare the folders using a one-way comparison, the source definition ORDER_ITEMS, present in ADS2
104
Chapter 4: Working with Folders
but not in ADS1, is not noted as a comparison. If you compare the folders using a two-way comparison, the absence of ORDER_ITEMS in ADS1 is noted as a difference. Figure 4-1. One-Way and Two-Way Comparisons
A one-way comparison does not note the presence of ORDER_ITEMS in ADS2 as a difference.
A two-way comparison notes the absence of ORDER_ITEMS in ADS1 as a difference.
Editing and Saving Results Files You can edit and save the result of a folder comparison. The Compare Folders wizard displays similar objects in green text, unmatched objects denoting a difference in red text, and outdated objects in blue text. The Compare Folders Wizard always displays the total number of differences, similarities, and outdated objects found during the comparison, even if you do not choose to display differences or similarities in the edit field. You can save the results of the comparison in the edit field to an .rtf or a .txt file. To retain the color and font attributes of the result, save it as an .rtf file. By default the results file is saved in the My Documents directory.
Steps to Compare Folders Before comparing folders, verify that you have Read permission for each folder you want to compare. Connect to the repositories containing the folders in the wizard. To compare folders: 1.
In the Repository Manager, click Folder > Compare.
2.
Click Next.
Comparing Folders
105
3.
Connect to the repositories containing the folders you want to compare and select the folders for comparison.
Connect to repository.
106
4.
Click Next.
5.
Select the object types you want to compare.
6.
Click Next.
Chapter 4: Working with Folders
7.
Select the display options.
8.
Click Next. The wizard always displays the number of differences, similarities, and outdated objects.
9.
View the results of the comparison.
Save the compare results to a file.
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.
Comparing Folders
107
108
Chapter 4: Working with Folders
Chapter 5
Local and Global Shortcuts This chapter includes the following topics: ♦
Overview, 110
♦
Shortcuts Versus Copies, 111
♦
Understanding Shortcut Properties, 112
♦
Creating a Local Shortcut, 115
♦
Creating a Global Shortcut, 119
♦
Working with Shortcuts, 123
♦
Tips, 126
♦
Troubleshooting, 127
109
Overview Shortcuts allow you to use metadata across folders without making copies. The helps to ensure uniform metadata. A shortcut inherits all properties of the object to which it points. After you create a shortcut, you can configure the shortcut name and description. When the original object 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 an object in 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:
110
♦
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.
Chapter 5: Local and Global Shortcuts
Shortcuts Versus Copies One of the primary advantages of using a shortcut is maintenance. If you need to change all instances of an object, you can edit the original repository object. All shortcuts accessing the object inherit the changes. In contrast, if you have multiple copies of an object, you need to edit each copy of the object, or recopy the object, to obtain the same results. However, some changes can invalidate mappings and sessions. For example, if you use a shortcut to a reusable transformation and then change a port datatype, you can invalidate all mappings with shortcuts to the transformation and all sessions using those mappings. Therefore, if you want the object to inherit changes immediately, create a shortcut. Otherwise, create a copy. Shortcuts have the following advantages over copied repository objects: ♦
You can maintain a common repository object in a single location. If you need to edit the object, all shortcuts immediately inherit the changes you make.
♦
You can restrict repository users to a set of predefined metadata by asking users to incorporate the shortcuts into their work instead of developing repository objects independently.
♦
You can develop complex mappings, mapplets, or reusable transformations and then reuse them easily in other folders.
♦
You can save space in the repository by keeping a single repository object and using shortcuts to that object, instead of creating copies of the object in multiple folders or multiple repositories.
For information about exporting and importing objects to makes copies, see “Exporting and Importing Objects” on page 215.
Shortcuts Versus Copies
111
Understanding Shortcut Properties When you create a shortcut to a repository object, the shortcut inherits the attributes of the object. The shortcut inherits the following properties that cannot be edited in the shortcut object: ♦
Object business name and owner name
♦
Port attributes, including datatype, precision, scale, default value, and port description
♦
Object properties (such as tracing level)
The shortcut also inherits a name and description which you can edit in the shortcut.
Default Shortcut Name The Designer names a shortcut after the original object based on the original object name as it appears in the Navigator when you create the shortcut. The Designer uses the following naming convention: Shortcut_To_DisplayedName. By default, the Designer displays all objects in the Navigator by object name. If you create a shortcut while using the default display option, the Designer names the shortcut Shortcut_To_ObjectName. Alternatively, you can enable the Designer tools to display sources and targets by business name. When you enable this option, the Designer displays sources and targets by business names if they exist. If you create a shortcut to a source or target when this option is enabled, the Designer names the shortcut Shortcut_To_BusinessName. Note: If the business name contains characters that are not allowed as in the object name, the
Designer replaces the character with an underscore (_). You can edit the default shortcut name at any time.
Describing the Object and the Shortcut Shortcuts inherit the description associated with the referenced object when you first create the shortcut. Afterwards, you can add object descriptions for each shortcut. Since the description is unique to the shortcut, if the description of the referenced object subsequently changes, shortcuts do not inherit those changes.
112
Chapter 5: Local and Global Shortcuts
Figure 5-1 shows the shortcut with a description inherited from the original object: Figure 5-1. Object and Shortcut Description
Description from the original object Description added to the shortcut
Shortcuts do not inherit edits to the description of the referenced object. However, any shortcuts created after the change contain the latest description.
Locating the Referenced Object Each shortcut tracks the location of the object it references and displays it in the transformation property sheet. The shortcut object displays the following details about the referenced object: ♦
Repository name
♦
Folder name
♦
Table or transformation name
Understanding Shortcut Properties
113
Figure 5-2 shows the transformation property sheet with the referenced shortcut objects: Figure 5-2. Referenced Shortcut Object
Original Object Location
Note: If you move or delete an object referenced by a shortcut, the shortcut becomes invalid.
114
Chapter 5: Local and Global Shortcuts
Creating a Local Shortcut You can reuse metadata within a single repository by creating a local shortcut. You can create a local shortcut to objects in a shared folder in the same repository. If an object is in a nonshared folder, you can make a copy of the object. You can create a local shortcut in any folder in the repository. After you create a local shortcut, you can reuse it within the same folder. After you create a shortcut, it appears in the Navigator as an available repository object with the shortcut icon. When you drag the resulting shortcut into the workspace, the same shortcut icon appears. The Designer names shortcuts after the original object by default, Shortcut_To_ObjectName. For example, when you create a shortcut to the DetectChanges reusable Expression transformation, the shortcut, named Shortcut_To_DetectChanges appears in the Transformations node of the folder. When you drag it into the workspace, the shortcut icon indicates the transformation is a shortcut.
Creating a Local Shortcut
115
Figure 5-3 shows shortcut icons in the Navigator and Workspace windows: Figure 5-3. Flat File Source Shortcut Icon
Shared Folder
Original Object
Shortcut
Shortcut Icon
Note: When you drag an object from a shared folder to a business component directory, the
Designer creates a shortcut if the object does not already exist in the destination folder. For more information, see “Managing Business Components” in the Designer Guide. To create a local shortcut, you must have one of the following sets of privileges and permissions for the shared folder containing the original object:
116
♦
Use Designer privilege with read permission on the folder
♦
Super User privilege
Chapter 5: Local and Global Shortcuts
You must have the one of the following sets of privileges and permissions on the destination folder: ♦
Use Designer privilege with read and write permission on the folder
♦
Super User privilege
You can create a local shortcut in the Navigator or in the workspace. To create a local shortcut in the Navigator: 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
Related Documents
Pc 811 Repository Guide
October 2019 23
Osi Guide To Repository Software
May 2020 5
Repository Description
December 2019 16
Virtual Pc Eval Guide
May 2020 3
Ad 811
November 2019 33