Metadata Manager Guide

Metadata Manager User Guide
Informatica PowerCenter
(Version 8.1.1)
Informatica PowerCenter Metadata Manager User Guide
Version 8.1.1
February 2008
Copyright (c) 20032008 Informatica Corporation.

All rights reserved. Printed in the USA.
This software, including the Metadata Manager Configuration Console, 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.
The information in this product or documentation is subject to change without notice. If you find any problems in the software or documentation, please report
them to us in writing. Informatica Corporation does not warrant that this product or documentation is error free.
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. U.S. Patent Pending.
BEA and WebLogic are registered trademarks of BEA Systems, Inc.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright Sun Microsystems. All
Rights Reserved. Copyright 2001 BEA Systems. All Rights Reserved. Copyright IBM Corp. 2000, 2001. All rights reserved. Copyright 1991-2002
DataDirect Technologies. All Rights Reserved. Isomorphic SmartClient presentation layer 2002 Isomorphic Software, Inc. All Rights Reserved. Copyright
Palm, Inc. All Rights Reserved. Copyright Research In Motion Limited. All Rights Reserved. Copyright Unisys. All Rights Reserved. Copyright
GoAmerica Communications Corp. All Rights Reserved. Copyright Microsoft Corp. All Rights Reserved. Copyright (c) 1998-1999 Aandacht c.v. All Rights
Reserved. ACE (TM) software 1993-2002 by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine. All
Rights Reserved. 2004 Yaletown Technology Group. All Rights Reserved. Copyright 2001-2004 Panscopic Corporation, Inc. All rights reserved. Copyright
2005 Zero G Software, Inc. All Rights Reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software is Copyright 1999-2005 The
Apache Software Foundation. All rights reserved.
The Qexo software included with this software is Copyright 1996-1999 Per Bothner. All Rights Reserved. Your right to use such software is set forth in a
modified GNU Public License, which may be found at http://www.gnu.org/software/kawa/License.html. The software is 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 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.
The edtFTPj library included with this software is Copyright 2000-2004 Enterprise Distributed Technologies. All Rights Reserved. Your right to use such library
is set forth in the GNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/ licenses/lgpl.html. The library is 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. Meta Integration Technology, Inc. powers Metadata connectors to Business Objects Repository, CA ERwin, Cognos Impromptu, Cognos
ReportNet Repository, Embarcadero ERStudio, Hyperion EIS, IBM DB2 Cube Views, IBM Rational Rose, Microsoft Visio, MicroStrategy, Oracle Designer,
and Sybase PowerDesigner.
This Software is protected by U.S. Patent Number 7,117,215, 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . . xiii
Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . xiii
Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1: Metadata Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Metadata Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Data Lineage and Where-Used Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Where-Used Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Metadata Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Metadata Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Metadata Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Alerts Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Metadata Directory on the Find Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Information Directory on the Find Tab . . . . . . . . . . . . . . . . . . . . . . . . . .9
Analyze Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Administration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Create Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Manage Account Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Logging in to Metadata Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table of Contents iii

Chapter 2: Accessing Source Repository Metadata . . . . . . . . . . . . . 13
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Browsing Source Repository Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Metadata Tree Task Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Results Task Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Details Task Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Viewing Versions of Metadata Objects . . . . . . . . . . . . . . . . . . . . . . . . . 17
Viewing Deleted Metadata Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring the Number of Objects in a Subgroup . . . . . . . . . . . . . . . . 18
Running Queries on Source Repository Metadata . . . . . . . . . . . . . . . . . . . . 20
Viewing Metadata Object Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring the Display Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Rules for Displaying Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Applying Property Configuration Changes . . . . . . . . . . . . . . . . . . . . . . 27
Emailing Metadata Object Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 3: Working with Metadata Objects . . . . . . . . . . . . . . . . . . . . 33

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Adding Metadata Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Editing Metadata Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Deleting Metadata Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Exporting Metadata Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 4: Working with Object Properties . . . . . . . . . . . . . . . . . . . . 43

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Viewing Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Viewing General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Viewing Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Adding Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Editing Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Deleting Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 5: Working with Object Associations . . . . . . . . . . . . . . . . . . 55

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Viewing Object Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Adding Object Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Deleting Object Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
iv Table of Contents
Chapter 6: Working with Object Links . . . . . . . . . . . . . . . . . . . . . . . . 63
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Viewing Object Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Adding Object Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting Object Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Chapter 7: Working with Report Links . . . . . . . . . . . . . . . . . . . . . . . . 69

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Viewing Report Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Adding Report Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Editing Report Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Deleting Report Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 8: Working with Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . 79

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Analyzing Data Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Troubleshooting Data Transformation Errors . . . . . . . . . . . . . . . . . . . . 81
Viewing Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Types of Objects in Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Object Handling in Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Viewing Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Viewing the Lineage Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Viewing Field-Level Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Viewing Data Lineage History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Running Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Filtering Data Lineage Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Working with Object Properties in Data Lineage . . . . . . . . . . . . . . . . . . . . . 95
Viewing Object Properties in Data Lineage . . . . . . . . . . . . . . . . . . . . . . 95
Configuring Object Properties in Data Lineage . . . . . . . . . . . . . . . . . . . 95
Setting Up Remote Access to Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . 97
Chapter 9: Working with Where-Used Analysis . . . . . . . . . . . . . . . . . 99

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Viewing Where-Used Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Viewing the Tree Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Viewing the Tabular Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Viewing Where-Used Analysis History . . . . . . . . . . . . . . . . . . . . . . . . 105
Table of Contents v
Running Where-Used Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Chapter 10: Sharing Data Lineage and Where-Used Analysis

Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Exporting Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Emailing Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Chapter 11: Working with Metadata Manager Reports . . . . . . . . . . 113

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Business Intelligence Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Data Modeling Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Data Integration Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Database Management Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Metamodel Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Running Metadata Manager Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Running Metadata Manager Reports from the Information Directory . . 116
Running Metadata Manager Reports from the Metadata Directory . . . . 117
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
vi Table of Contents
List of Figures
Figure 1-1. Metadata Directory Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 8
Figure 1-2. Information Directory Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 9
Figure 1-3. Administration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 2-1. Source Repository Metadata in the Metadata Tree . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 2-2. Multiple Selections in a Metadata Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 2-3. Query Task Area on the Metadata Directory Page . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 2-4. Results and Details Task Areas on the Metadata Directory Page . . . . . . . . . . . . . . 24
Figure 2-5. Default Object Properties Displayed in the Results Task Area . . . . . . . . . . . . . . . 26
Figure 2-6. Multiple Classes of Objects in the Results Task Area . . . . . . . . . . . . . . . . . . . . . . 28
Figure 2-7. Configure Favorite Properties for Multiple Classes of Objects . . . . . . . . . . . . . . . 28
Figure 2-8. Configure Favorite Properties Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 8-1. Data Lineage Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 8-2. Lineage Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 8-3. Field-Level Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 8-4. Lineage Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 8-5. Configured Display Properties for Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 9-1. Where-Used Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Figure 9-2. Where-Used Analysis: Tree View Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Figure 9-3. Where-Used Analysis: Tabular View Format . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Figure 9-4. Where-Used Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Figure 11-1. Report Access from the Metadata Directory Page . . . . . . . . . . . . . . . . . . . . . . . .118
List of Figures vii

viii List of Figures
List of Tables
Table 2-1. Query Options in the Query Task Area of the Metadata Browser . . . . . . . . . . . . . . 22
Table 2-2. Options on the Configure Favorite Properties Page . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 3-1. Default Properties of Objects Created on the Metadata Directory Page . . . . . . . . . . 35
Table 3-2. Attributes on the Create New Objects Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 3-3. Export Options for Exporting Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 4-1. General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 4-2. Attributes on the Property Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 4-3. Attributes on the Add New Property Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 5-1. Attributes on the Object Association Details Page . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 6-1. Attributes on the Object Link Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 7-1. Attributes on the Report Link Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Table 7-2. Report Filter Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 11-1. Metadata Manager Report Location on the Information Directory Page . . . . . . . .116
List of Figures ix
x List of Figures
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.
xi
About This Book
The Metadata Manager User Guide provides information about using Metadata Manager,
such as viewing repository metadata and reports, and configuring the metadata properties that
display. It also discusses how to add additional metadata objects and properties to the
Metadata Directory.
The Metadata Manager User Guide is written for business analysts who use Metadata Manager
for metadata management and analysis. This book assumes the business analysts have
knowledge of Data Analyzer.
The material in this book is available for online use.
Document Conventions
This guide uses the following formatting conventions:
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.
xii Preface
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 xiii
Use the following email addresses to contact Informatica Technical Support:
support@informatica.com for technical inquiries
support_admin@informatica.com 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.
North America / South America Europe / Middle East / Africa Asia / Australia
Informatica Corporation Informatica Software Ltd. Informatica Business Solutions

Headquarters 6 Waltham Park Pvt. Ltd.
100 Cardinal Way Waltham Road, White Waltham Diamond District
Redwood City, California Maidenhead, Berkshire Tower B, 3rd Floor
94063 SL6 3TN 150 Airport Road
United States United Kingdom Bangalore 560 008
India
Toll Free Toll Free Toll Free

877 463 2435 00 800 4632 4357 Australia: 00 11 800 4632 4357
Singapore: 001 800 4632 4357
Standard Rate Standard Rate Standard Rate

United States: 650 385 5800 Belgium: +32 15 281 702 India: +91 80 4112 5738
France: +33 1 41 38 92 26
Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511 445
xiv Preface
Chapter 1
Metadata Manager Overview
This chapter includes the following topics:

Introduction, 2
Metadata Browsing, 3
Data Lineage and Where-Used Analysis, 4
Metadata Reporting, 5
Metadata Documentation, 6
Metadata Manager Interface, 7
Logging in to Metadata Manager, 12
1
Introduction
Informatica Metadata Manager is a metadata management tool that you can use to browse
and analyze metadata from disparate metadata repositories. Metadata Manager helps you
understand and manage how information and processes are derived, the fundamental
relationships between them, and how they are used.
Metadata Manager embeds Informatica Data Analyzer functionality. Data Analyzer is a tool
that you can use to analyze information about business processes within the enterprise and
share business insight with other users. You can use Data Analyzer features to design, develop,
and deploy metadata reports and dashboards. For more information about Data Analyzer, see
the Data Analyzer documentation.
Metadata Manager provides the following key features:
Metadata browsing
Data lineage and where-used analysis
Metadata reporting
Metadata documentation
2 Chapter 1: Metadata Manager Overview

Metadata Browsing
You can use the Metadata Browser to browse metadata stored in the Metadata Manager
Warehouse. The Metadata Browser provides visibility into and across source repositories. The
Metadata Browser organizes metadata by repository. You can set up roles to personalize the
information that displays in the Metadata Browser for each Metadata Manager user.
You can use the Metadata Browser to increase your understanding of the content in each
source system and application. The Metadata Browser displays descriptive information about
each metadata object. For example, the Metadata Browser displays the following properties
about a database table:
Alias name
Display label
Type of database object
Whether the table is partitioned
Name of the table
You can also use the Metadata Browser to create and audit existing database queries, data
integration logic, and business intelligence logic to ensure accurate information. For example,
the Metadata Browser displays the code used to transform data in a PowerCenter mapping.
For more information, see Accessing Source Repository Metadata on page 13.
Metadata Browsing 3
Data Lineage and Where-Used Analysis
Metadata Manager packages the following interactive metadata analysis tools:
Data Lineage
Where-Used Analysis
Data Lineage
Data lineage shows the data flow from the data source, through various systems and staging
areas, to the data destination. You can use this tool to determine where data comes from, how
it is transformed, and where it is going. The report displays details at the field level. For
example, data lineage shows how data in a database table column eventually feeds a metric in
a business intelligence report.
You can use this tool to audit results of data integration and business intelligence systems. For
example, you can run data lineage on the Quarterly Sales metric to determine where the
information comes from and the method used to calculate the result. If you find an error in
the calculation, you can run data lineage on the metric again to see what other applications
use the incorrectly calculated metric.
For more information, see Working with Data Lineage on page 79.
Where-Used Analysis
Where-used analysis shows all instances where an object is used within and across repositories.
You can use where-used analysis to perform impact analysis before making changes to source
repositories, such as business intelligence, data integration, or database repositories. For
example, if you want to drop a database table, you can use where-used analysis to determine
what other objects in any repository use the information provided by the database table.
For more information, see Working with Where-Used Analysis on page 99.

Metadata Reporting
Metadata Manager provides packaged reports and tools to create your own reports. The
Metadata Manager provides web-based dashboards and reports that are powered by
Informatica Data Analyzer. You can use the dashboards and reports to monitor and analyze
system performance and data quality, content, and usage. You can use Metadata Manager to
quickly and cost-effectively deploy solutions customized to address a broad range of metadata
management requirements.
For example, instead of viewing each application log to identify errors, you can use the
Metadata Manager operational metadata dashboards and reports to highlight issues, such as
failed PowerCenter workflows and sessions. You can also analyze data transformation
processes to ensure compliance with government or organization regulations.
Metadata Manager packages the following types of reports:
Metadata analysis reports. Metadata Manager provides the following metadata analysis
reports to help you analyze source repository metadata:
Business intelligence reports. Use to analyze business intelligence metadata, such as
reports information, user activity, and how long it takes to run reports.
Data integration reports. Use to analyze data integration operations. You can use the
reports to identify data integration problems and analyze data integration processes.
Database management reports. Use to explore database objects, such as schemas,
structures, methods, triggers, and indexes, and the relationships among them.
Metamodel reports. Administrators can use these reports to explore the metamodels
defined in Metadata Manager. They can use the reports to understand how Metadata
Manager classifies metadata for each repository. For more information about metamodels,
see, Exchanging Metamodels in the Metadata Manager Administrator Guide.
For more information about viewing reports, see Working with Metadata Manager Reports
on page 113.
Metadata Manager also packages dashboards. You can access the dashboards from the View
tab. For more information about working with dashboards, see Creating a Dashboard in the
Data Analyzer User Guide.
Metadata Reporting 5
Metadata Documentation
Many organizations use different applications that perform similar functions. Each
application repository has unique descriptions, calculations, or usages for its metadata. You
can use Metadata Manager to create a single, enterprise-wide data dictionary. A single data
dictionary can reduce redundancy and inconsistency in metadata information within and
across repositories.
To increase your understanding of all metadata, Metadata Manager provides a way to
document metadata. You can load different types of information about each metadata object,
such as calculations, descriptions, and usages. You can also use the Metadata Manager
interface to input additional information about particular metadata objects that are not
loaded from source systems or applications. For more information about using the Metadata
Manager interface to add new metadata or more information about existing metadata, see
Overview on page 34.

Metadata Manager Interface
The Metadata Manager documentation refers to the Metadata Manager interface as
Metadata Manager. In Metadata Manager, you use a web browser to complete tasks.
Metadata Manager groups related tasks within tabbed pages on the web browser interface. You
navigate through the different tabs to complete different tasks.
Metadata Manager contains the following tabs:
Alerts
View
Find
Analyze
Administration
Create
Manage Account
The Find tab provides access to the following pages:
Metadata Directory
Information Directory
When you log in, Metadata Manager determines your privileges according to your user
profile, and then displays the tabs to which you have access privileges. Metadata Manager
system administrators have access to all tabs and can control access of other users.
For more information about Metadata Manager roles and permissions, see Setting Privileges
and Access Permissions in the Metadata Manager Administrator Guide.
Alerts Tab
You can view and modify your alerts on the Alerts tab. You can also register other alert
delivery devices to have Metadata Manager send alerts to those devices. You can suspend the
delivery of alerts to registered alert devices during certain hours of the day or for an indefinite
period of time. For more information about the Alerts tab, see Managing Alerts and Alert
Delivery in the Data Analyzer User Guide.
View Tab
When you log in, Metadata Manager displays the View tab. For each user, Metadata Manager
displays personalized information on the View tab. If you click the View tab from any other
tab, the View tab always displays the last report or dashboard you viewed.
From the Subscription menu on the View tab, you can perform the following tasks:
Display a report to which you subscribe.
Display a personal dashboard or a dashboard to which you subscribe.
Metadata Manager Interface 7

Subscribe to a report or dashboard.
Manage your subscription list.
For more information about the View tab and displaying and subscribing to reports and
dashboards, see Publishing a Report or Dashboard in the Data Analyzer User Guide.
Metadata Directory on the Find Tab

Use the Metadata Directory page to access the Metadata Browser. Use the Metadata Browser
to view information about metadata stored in the Metadata Manager Warehouse. The
Metadata Browser provides the following information about each metadata object:
Properties about the metadata object, such as the source repository to which the object
belongs, class containing the object, dates the object was created and last modified
Associations between the object other objects
Objects to which the object is related
Reports to which the object is assigned
Figure 1-1 shows the Metadata Directory page on the Find tab:
Figure 1-1. Metadata Directory Page
Shows Metadata Directory

or Information Directory
Query Task Area
Results Task Area
Metadata Tree Task Area Details Task Area
The Metadata Directory page consists of the following areas:

Query task area. Use to search for metadata objects stored in the Metadata Manager
Warehouse.
Metadata Tree task area. Use to navigate to a metadata object in a particular repository.

Results task area. Displays metadata objects based on an object search in the Query task
area or based on the object selected in the Metadata Tree task area.
Details task area. Displays properties about the selected object. You can also view
associations between the object and other objects, and run related reports from the Details
task area.
For more information about the Metadata Directory page, see Accessing Source Repository
Metadata on page 13.
Information Directory on the Find Tab

You can use the Information Directory page to run and view details about Metadata Manager
reports. For more information about Metadata Manager reports, see Working with Metadata
Manager Reports on page 113.
Figure 1-2 shows the Information Directory page on the Find tab:
Figure 1-2. Information Directory Page

Shows Information Directory
or Metadata Directory Query Task Area Results Task Area
Folders Task Area Details Task Area
The Metadata Directory page consists of the following areas:

Query task area. Use to search for reports. The resulting reports from a query display in
the Results task area.

Folders task area. Use to navigate to a Metadata Manager report. The reports are
categorized in folders by domain. When you select a folder, all reports contained in that
folder appear in the Results task area. When you select a report, the details about the
report appear in the Details task area.
Results task area. Displays reports based on a report search in the Query task area or based
on the folder selected in the Folders task area.
Details task area. Displays properties about the selected report or folder. In the Details
task area, you can also add a report to a dashboard, and run, edit, and subscribe to reports.
For more information about adding reports to dashboards, running, editing, and
subscribing to reports, see the Data Analyzer User Guide.
Analyze Tab
When you run a report from the Find tab, the report appears on the Analyze tab. For more
information about the Analyze tab, see Data Analyzer Interface in the Data Analyzer User
Guide.
Administration Tab
System administrators can access the Administration tab to complete the following Data
Analyzer tasks:
Design the schema.
Import and export schema objects through XML files.
Manage system settings.
Configure real-time message streams.
Set up schedules for reports.
Manage user and group access.
For more information about the Data Analyzer tasks on the Administration tab, see Data
Analyzer Interface in the Data Analyzer User Guide.
System administrators can also access the Administration tab to complete the following
Metadata Manager tasks:
Manage metamodels
Manage source repositories
For more information about managing metamodels and source repositories, see Exchanging
Metamodels in the Metadata Manager Administrator Guide.

Figure 1-3 shows the Administration tab:
Figure 1-3. Administration Tab
Data Analyzer
Tasks
Metadata
Manager Tasks
Create Tab
You can create reports and dashboards on the Create tab. For more information about the
Create tab, see the Data Analyzer User Guide.
Manage Account Tab

You can configure your Metadata Manager account and set up alert delivery options on the
Manage Account tab. For more information about the Manage Account tab, see Managing
Account Information in the Data Analyzer User Guide.

Logging in to Metadata Manager
You can log in to Metadata Manager using a Microsoft Internet Explorer web browser.
Note: Metadata Manager Server must be running before you can log in to Metadata Manager.
For more information about starting Metadata Manager Server, see the PowerCenter
Installation and Configuration Guide.
To log in to Metadata Manager:
1. Launch a Microsoft Internet Explorer web browser.

2. In the address bar, enter the Metadata Manager URL:
http://<host name>:<port number>/imm
For example:
http://s161004:8080/imm
The following table describes the elements of the Metadata Manager URL:
Required/
URL Element Description
Optional
host name Required Host name typically consists of a domain name and the machine name where
Metadata Manager is installed. You can also use the IP address.
port number Required Port number of Metadata Manager Server. You defined this port number when
you installed the application server. The default port numbers are:
- 7001 for BEA WebLogic Server
- 9080 for WebSphere Application Server
- 8080 for JBoss Application Server
Note: If you configured Metadata Manager to use the default port 80 for HTTP requests
and port 443 for HTTPS requests, you do not have to include the port number in the
URL.
The Metadata Manager Login page appears on the browser.
3. To log in to Metadata Manager, use the Metadata Manager user name and password that
you set up during Metadata Manager installation.
The default Metadata Manager user name and password are both admin.

Chapter 2
Accessing Source Repository

Metadata
Overview, 14
Browsing Source Repository Metadata, 15
Running Queries on Source Repository Metadata, 20
Viewing Metadata Object Details, 24
Configuring the Display Properties, 26
Emailing Metadata Object Details, 31
13
Overview
You can browse source repository metadata stored in the Metadata Manager Warehouse using
the Metadata Browser on the Metadata Directory page. You can also view different versions of
source repository objects and deleted objects.
You can perform the following tasks:
Browse source repository metadata stored in the Metadata Manager Warehouse. You can
use the Metadata tree to browse the source repository metadata. For more information, see
Browsing Source Repository Metadata on page 15.
Search for source repository metadata stored in the Metadata Manager Warehouse. You
can use the Query option in the Metadata Browser to search for particular source
repository metadata. For more information, see Running Queries on Source Repository
Metadata on page 20.
View metadata details. You can use the Details task area to view other information about a
metadata object, such as properties, associations, object links, and report links. For more
information, see Viewing Metadata Object Details on page 24.
Configure the display properties. You can configure the default properties that appear on
the Metadata Directory page for each type of metadata. For more information, see
Configuring the Display Properties on page 26.
14 Chapter 2: Accessing Source Repository Metadata

Browsing Source Repository Metadata
You can use the Metadata Browser on the Metadata Directory page to browse metadata stored
in the Metadata Manager Warehouse.
The Metadata Browser contains the following task areas:
Metadata Tree
Results
Details
Metadata Tree Task Area

The Metadata Browser contains the Metadata Tree task area. The Metadata tree is a
hierarchical structure that displays groups defined in Metadata Manager and source repository
objects stored in the Metadata Manager Warehouse.
The Metadata tree displays the following types of objects:
Metadata repository. All source repositories appear under the metadata repository node.
Source repository. Metadata from a source repository appear under the source repository
node.
Source repository folder. Folder defined in the source repository that stores source
repository metadata.
Groups. Groups defined in Metadata Manager. Displays as a folder in the Metadata tree,
categorizing source repository metadata. For more information about groups, see the
Metadata Manager Custom Metadata Integration Guide.
Source repository metadata. Metadata from a source repository.
The Metadata Repository node is the top-level node in the Metadata tree. Each source
repository that is loaded into the Metadata Manager Warehouse appears under the Metadata
Repository node. Folders defined in a source repository appear under the corresponding
source repository node. Source repository subfolders appear under their parent folders.
Groups defined in Metadata Manager also appear under their parent folders.
The Metadata tree shows the most recent version of each source repository object. It does not
show objects deleted from the source repository. However, you can run a query in the
Metadata Browser to search for deleted objects. For more information about viewing deleted
objects, see Viewing Deleted Metadata Objects on page 18.
Browsing Source Repository Metadata 15

Figure 2-1 shows an example of source repository metadata in the Metadata tree:
Figure 2-1. Source Repository Metadata in the Metadata Tree

Metadata Repository
Metadata Manager Group
Metadata Manager Subgroup
Source Repository
Source Repository Folder
Source Repository Object
The Metadata tree displays up to 100 objects under each folder by default. If a folder contains
more than 100 objects, the Metadata tree groups the objects into subgroups. The Metadata
tree organizes the subgroups alphabetically, storing 100 objects for each subgroup. You can
change the number of objects in each subgroup. For more information about configuring
subgroups, see Configuring the Number of Objects in a Subgroup on page 18.
The subgroups use the following naming convention:
<parent folder>(<first object in subgroup> - <last object in subgroup>)
Note: There is one exception. If the folder is a data structure and at least one of its child
objects is a field, the Metadata tree does not create subfolders. Instead, the Metadata tree
displays all objects under the folder. For more information about data structures and fields,
see Working with Data Lineage on page 79.
The Metadata tree displays icons to the left of the names of the groups and source repository
objects. For more information about the icons that display for each type of repository object,
see Metadata Manager Framework in the Metadata Manager Administrator Guide.
When you select an object in the Metadata tree, Metadata Manager highlights the selected
object, displays its children objects in the Results task area, and displays properties about the
selected object in the Details task area.
To view an object in the Metadata tree, you must have read permission on the parent of the
object. A parent is an object that contains another object. The Metadata Repository is the
parent of all the source repositories in the Metadata Manager Warehouse. Each source
repository is the parent of the top-level source repository folders. A folder is the parent of any
subfolders or repository objects it contains.
Results Task Area

When you select an object in the Metadata tree, the child objects of the selected object appear
in the Results task area. The associations between the classes of two related objects determine

which object is the child and which is the parent. For more information about classes and
associations, see the Metadata Manager Administrator Guide.
If you search for objects using the Metadata Browser, the Results task area displays the
matching results. By default, the Results task area displays a maximum of 200 objects. If the
number of objects exceeds the maximum, Metadata Manager displays a message, stating that
the Results task area cannot display all objects.
If the Results task area does not display all objects, complete one of the following tasks to
view all objects:
Use the Result Limit option to change the maximum number of objects that display. For
more information about the Result Limit option, see Table 2-1 on page 22.
Refine your search using filters to limit the number of resulting objects. For more
information about searching source repository metadata, see Running Queries on Source
Repository Metadata on page 20.
When you select an object in the Results task area, Metadata Manager highlights the selected
object and displays the properties of the selected object in the Details task area.
Details Task Area

When you select a source repository object in the Metadata Tree task area or in the Results
task area, the Details task area displays properties about the selected object. When you select a
group in the Metadata tree, no details appear in the Details task area since groups are not
source repository objects.
Viewing Versions of Metadata Objects

If the source repository stores versions of objects, Metadata Manager also stores versions of
the objects in the Metadata Manager Warehouse. You can use Metadata Manager to view
different versions of objects stored in the Metadata Manager Warehouse.
Metadata Manager lists the versions of object by date, followed by a number in parentheses.
The date shown is the date when the object became valid. The latest version of an object
displays the latest date. The number in parenthesis is the version number, which increments
by 1 with each new version of the object: the lower the number, the older the version. (1) is
the oldest version because it is the first version. When you add, edit, or delete properties of an
object, Metadata Manager creates a new version of the object.
By default, Metadata Manager displays the latest version of each metadata object.
To view a version of a metadata object:
1. On the Find tab, select Metadata Directory.

2. Select the metadata object.

3. In the Details task area, select the version in the Version field.
Select the version of the

object you want to view.
The Details task area displays properties about the selected version of the object.
Viewing Deleted Metadata Objects

You can also view the details of deleted objects. The Metadata tree does not show deleted
objects. When you use Metadata Manager to delete a metadata object, Metadata Manager
marks all versions of the object as deleted, but the object still remains in the Metadata
Manager Warehouse.
Metadata Manager does not show objects in the Metadata tree that are marked for deletion.
However, you can search for deleted objects to view them and their properties. You can search
for a deleted object using the Query task area. For more information about searching for
objects in the Metadata Manager Warehouse using a query, see Running Queries on Source
Repository Metadata on page 20.
Note: If you run the WF_DELETE workflow to delete all objects in a source repository, all
objects are purged from the Metadata Manager Warehouse. You cannot view these metadata
objects using the search feature. For more information about purging objects in a source
repository, see the Metadata Manager Administrator Guide.
To view metadata objects marked for deletion:

2. In the Query task area, select Yes for the Include Deleted Objects option.
3. Optionally, insert query criteria in the Query task area to limit the query results.
4. Click the Go button to retrieve the query results.
The Results task area displays the resulting metadata objects, which include deleted
objects.
Configuring the Number of Objects in a Subgroup

The Metadata tree displays up to 100 objects under any folder by default. If a folder contains
more than 100 objects, the Metadata tree groups the objects into subgroups. For more
information about subgroups in the Metadata tree, see Metadata Tree Task Area on page 15.
You can change the maximum number of objects that display under each subfolder. The fewer
number of objects that display under a subfolder, the faster the Metadata tree displays the
results.

To configure the number of objects in a subgroup:
1. Stop the Metadata Manager Server.

2. Open the imm.properties file.
You can find the file in the following directory:
For JBoss:
<JBoss_home>\bin
For WebLogic:
<WebLogic_home>\user_projects\domains\informatica
For WebSphere:
<WebSphere_home>\DeploymentManager
3. Search for the following text in the file:

MetadataTree.MaxFolderChilds=
4. Replace the value with the new number of objects.

5. Save and close the file.
6. Restart the Metadata Manager Server.

Running Queries on Source Repository Metadata
You can run queries to search for objects in the Metadata Manager Warehouse using the
Query task area in the Metadata Browser.
Metadata Manager searches for objects by matching the value you enter with an object
property, such as the Object Name or Description property. For example, if you search for
Customers, Metadata Manager may search for all objects whose Object Name property and
Description property contain Customers.
You can use the following wildcard characters in your query:
Wildcard Description
* or % Use to represent a string of characters. For example, you get the following results
when you search for C* or C%:
Customer
Camera
C Group
CA
_ Use to represent a single character. For example, you get the following results when
you search for C_:
CA
CN
You can escape the wildcard characters with \. For example, if you want to search for
Customer_Name string, then enter the following string in your search:
Customer\_Name
Metadata Manager uses different search criteria depending on the filters you select. For
example, if you search a specific class of objects in a repository for Customer, Metadata
Manager searches for all objects in the class that have Customer in any of its properties, not
just the Object Name property.
Use the following table to determine which properties Metadata Manager uses for metadata
searches:
If you choose... Metadata Manager searches the following object properties:
All repositories All properties, including the Object Name property
A repository and all classes All properties, including the Object Name property
One or all repositories, all classes, all properties All properties, including the Object Name property
A repository and multiple or all classes All properties, including the Object Name property
A repository and class All properties, including Object Name property
A repository, class, and property Selected property

You can run a simple query to search for objects based on the following criteria:
Source repositories to which the objects belong
Classes of which the object is a member
Properties the objects contain
Name of an object or property
You can search for metadata objects within a single source repository, or run your query across
multiple source repositories.
Figure 2-2 shows multiple repository selections in a metadata search:
Figure 2-2. Multiple Selections in a Metadata Search

Expand Button
Multiple Repository Search
You can also run an advanced query to refine your search.
To run a query on source repository metadata:

2. In the Query task area, click the Expand button to view the advanced query options.
Figure 2-3 shows the Query task area with the simple and advanced search options:
Figure 2-3. Query Task Area on the Metadata Directory Page

Search Pattern List Value Option
Go Button Collapse Button
Running Queries on Source Repository Metadata 21

3. In the Query task area, select the following query options:
Table 2-1. Query Options in the Query Task Area of the Metadata Browser
Required/ Simple Query/

Options Description
Optional Advanced Query
Select Required Both Source repositories used to refine the search. Metadata
Repositories Manager returns objects that belong to the selected
source repositories.
Select Optional Both Classes of objects used to refine the search. By default,
Classes the option displays All Classes. Select one source
repository to select a class. If you select more than one
repository, you cannot select any classes, but you can
select properties.
Select Optional Both Class properties used to refine the search. If you select
Properties multiple repositories or one repository and multiple
classes, you can search based on all properties or the
object name. If you one repository and one classes, you
can search based on a specific class property.
Containing Optional Both Select one of the following options:

- Containing. Search for values that contain the characters
entered in the Value option.
- Starts With. Search for values that start with the
characters entered in the Value option.
- Ends With. Search for values that end with the
characters entered in the Value option.
- Equal To. Search for values that match the characters
entered in the Value option.
Value Optional Both Value for which you are searching. The Value option is
case sensitive if you select Match Case.
If you include an underscore (_) in a query, escape the
underscore with a backslash (\). For example, if you want
to search for objects that begin with LKP_ERP, enter the
following value in the query:
LKP\_ERP
Match Case Optional Both Returns results that match the case of the text entered in
the Value option. Default is No.
Updated Optional Advanced Returns objects updated on or after the date you specify.
After
Effective On Optional Advanced Returns objects that are valid on or after the date you
specify.
Only Latest Optional Advanced Returns the latest version of the object in the Metadata
Manager Warehouse. Default is No.
Include Optional Advanced Returns metadata objects that are marked for deletion in
Deleted the Metadata Manager Warehouse. Metadata Manager
Objects marks objects for deletion when you delete them using
Metadata Manager. Default is No.
Result Limit Optional Advanced Limits the number of search results. Default is 200.

To select multiple repositories, click each applicable repository in the Select a Repository
option. A check mark appears next to all repositories that are included in the search. To
remove a repository from the search, click the repository name again to clear the check
mark.
4. Click Go to run the query.
When you run a query, the results appear in the Results task area. To view more
information about one of the resulting objects, select the object and view the details in
the Details task area.
Running Queries on Source Repository Metadata 23

Viewing Metadata Object Details
You can view details about source repository objects in the Metadata Manager Warehouse.
You can view details about multiple versions of the object. You can also run reports on the
objects.
To view details about an object, select the object in the Metadata Tree task area or Results task
area. The details appear in the Details task area. You must have read permission for the object
to view the object details.
Figure 2-4 shows the Results and Details task areas on the Metadata Directory page:
Figure 2-4. Results and Details Task Areas on the Metadata Directory Page
Results Task Area
Versions List
Details Task Area
Run Report Buttons
Users with the Manage Object and Object Association privilege can create run report buttons
that you can click to run reports on an object. The buttons appear in the top, right corner of
the Details task area when you select the object in the Results task area. In
Figure 2-4, Data Lineage and Where-used are run report buttons that run data lineage and
where-used analysis, respectively on a selected object MM_CUSTOMERS.
You can select a version from the Version list to view the details about a different version of
the selected object. The versions are listed by date, followed by a number in parentheses: the
lower the number, the older the version. The oldest version of an object is (1).
System administrators can configure source repository objects, object properties, associations,
object links, and report links from the Details task area.

The Details task area contains the following tabs:
General Properties tab. Shows properties that apply to any metadata object, regardless of
the class to which it belongs. For more information about general properties, see Working
with Object Properties on page 43.
Object Properties tab. Shows properties that are specific to the object. For more
information about object properties, see Working with Object Properties on page 43.
Associations tab. Displays all associations defined between an object and other objects.
For more information about object associations, see Working with Object Associations
on page 55.
Object Links tab. Displays all links defined between an object and other objects. For more
information about object links, see Working with Object Links on page 63.
Report Links tab. Displays all links defined between an object and Metadata Manager
reports. For more information about report links, see Working with Report Links on
page 69.
Viewing Metadata Object Details 25

Configuring the Display Properties
When you select a folder in the Metadata tree, Metadata Manager displays all child objects,
including subfolders, associated with the selected folder in the Results task area. Metadata
Manager displays a set of default properties for all items in the Results task area. The default
properties are generic properties that apply to all metadata objects stored in the Metadata
Manager Warehouse. You can rearrange, add, and remove the properties that appear for your
Metadata Manager user account.
For example, you can remove the default Class and Source Update Date properties, move the
Repository Name property before the Label property, and display a different property, such as
the Warehouse Insertion Date.
You can add other properties that are specific to the class of the selected object. For example,
you can add the View Definition property to the display when you view an Oracle View class
object in the Results task area. The View Definition property displays the definition of the
view as defined in the Oracle source repository.
By default, Metadata Manager displays the following properties in the Results task area for
each source repository object:
Class. Displays an icon that represents the class of the selected object. The class name
appears when you place the pointer over the icon.
Label. Label of the object.
Source Update Date. Date the object was last updated in the source repository.
Repository Name. Name of the source repository from which the object originates.
Description. Description of the object.
Figure 2-5 shows the default properties that appear in the Results task area:
Figure 2-5. Default Object Properties Displayed in the Results Task Area
Column header of Results task area that displays the default object properties
Rules for Displaying Properties

The Results task area displays objects when you complete one of the following tasks:
Search for an object using the Query task area.
Select an object in the Metadata Tree task area.
After you select an object in the Metadata tree, Metadata Manager displays objects in the
Results task area. If the objects in the Results task area all belong to the same class, a list of
properties that are applicable to that class appears.

If the objects in the Results task area belong to multiple classes, a list of properties that are
applicable to each class appears. Duplicate properties appear once. For example, the objects
displayed in the Results task area belong to Classes A and B. Classes A and B have the
following properties:
Properties of Class A Properties of Class B
Property_A1 Property_B1
Property_A2 Property_B2
Property_A3 Property_Common
Property_Common
When you add properties to the Results task area, the following properties will be available:
Property_Common
Property_A1
Property_A2
Property_A3
Property_B1
Property_B2
Notice that Property_Common appears once.
If you add Property_A1 to the Results task area, then objects from Class B will not have
values for this property. When you display a property in the Results task area that does not
apply to one of the objects, Metadata Manager displays a blank field.
You can remove all default properties, except Label. You can select up to 10 properties to
display in the Results task area. Metadata Manager displays them in the order you specify.
If there are more than 10 properties to display, Metadata Manager displays the first 10
properties. It first displays common properties in the order you specify, and then displays all
remaining properties in alphabetical order based on the property display label.
Applying Property Configuration Changes

To configure the properties, select an object in the Metadata tree. You cannot configure the
default properties if the Results task area displays objects based on a metadata search.
After you change property display settings, you can apply the modified property display
settings to any class of objects displayed in the Results task area. When you select an object in
the Metadata tree, multiple classes of objects may appear in the Results task area.
Configuring the Display Properties 27

Figure 2-6 shows an example where multiple classes of objects appear in the Results task area:
Figure 2-6. Multiple Classes of Objects in the Results Task Area
Class 1
Class 2
Class 3
Figure 2-7 shows how you can apply the modified display settings for each class of objects in
the Results task area:
Figure 2-7. Configure Favorite Properties for Multiple Classes of Objects
Include properties
in display.
Apply settings to
other classes of
objects.
Apply settings to
other users.

First, select the properties that you want to display. Next, apply the settings to other classes of
objects that currently display in the Results task area. If you do not apply the settings to other
classes, the settings apply to objects of the same class as the object selected in the Metadata
tree.
If you apply the settings to other classes, the modified display settings apply to objects of
those classes if those classes are associated with the parent class of the object selected in the
Metadata tree. Classes are related through associations. For more information about
associations, see the Metadata Manager Administrator Guide.
After you save the modified display settings, each time you select objects of a class to which
you applied the changes, the Results task area displays the modified set of properties.
To configure how properties display, you must have one of the following privileges or
permissions:
Access Find Tab privilege
Read permission
Users with the System Administrator or Schema Designer role can apply the changed settings
to all users who use the default settings for this class. If the user modifies their display
settings, the user-modified settings override the system administrator settings.
To change the properties displayed in the Results task area:
1. In the Metadata tree, select an object.

The Results task area displays all child objects associated with the selected object.
Configure Link
Column Header
Multiple classes of
child objects display.
2. Click Configure.
Tip: You can also right-click the column header of the Results task area, and then select
Configure Favorite Properties.
The Configure Favorite Properties page appears.
Configuring the Display Properties 29

Figure 2-8 shows the Configure Favorite Properties page:
Figure 2-8. Configure Favorite Properties Page
Move Up and Move Down arrows
3. Select the properties you want to display.

The available properties are prefixed with their associated class. For example, Figure 2-8
highlights the Mapplet Port -> Initial Value property. Function is a property of the
Mapplet Port class. If a property is not prefixed with a class, then it is a common property
that applies to more than one class. Common properties are properties that multiple
classes share.
4. Click Include >> or << Exclude to add or remove properties.
5. Use the move up and move down arrows to rearrange the order in which the properties
appear in the Results task area.
6. Select the applicable options.
Table 2-2 describes the options on the Configure Favorite Properties page:
Table 2-2. Options on the Configure Favorite Properties Page
Required/
Option Description
Optional
Use as my favorite properties Optional Sets the selected settings as the default settings for the specified
view for objects of <class class. This option displays once for each class of objects in the
label>. Results task area.
Apply this to all users who have Optional Applies the property display settings to all users who have not
not customized favorite configured their display settings for the applicable classes. You
properties for this class. must be a System Administrator or have the Schema Designer
role to configure this option.
7. Select OK to save the changes in Metadata Manager.

Emailing Metadata Object Details
You can email metadata object details. You might email this information to share object
properties and object associations with others.
When you email metadata object details, the email contains the following information:
General properties. General properties captured for any type of object in the Metadata
Manager Warehouse. For more information about general properties, see Viewing
General Properties on page 45.
Object properties. Object-specific properties. For more information about object
properties, see Viewing Object Properties on page 46.
Object associations. Associations defined specifically for the object. For more information
about object associations, see Overview on page 56.
You can email the metadata object details in the following formats:
PDF Document. Metadata Manager emails a PDF file containing the metadata object
details.
Embedded HTML. Metadata Manager embeds the results in the email in HTML format.
Microsoft Excel. Metadata Manager emails a Microsoft Excel file containing the metadata
object details.
XML Document. Metadata Manager emails an XML file containing the metadata object
details. The recipient can import the object and its details in the XML file into another
Metadata Manager instance. For more information about importing metadata objects, see
the Metadata Manager Administrator Guide.
You must set up the mail server before you can email report results. The mail server provides
outbound email access for Metadata Manager and users. For more information about
configuring the mail server, see Managing System Settings in the Data Analyzer
Administrator Guide.
When you email a report, Metadata Manager asks you to provide your email address if your
Metadata Manager user account does not already have one defined for you. For more
information about specifying an email address, see Managing Alerts and Delivery in the
Data Analyzer User Guide.
To email metadata object details:
1. In the Metadata Directory, select an object in the Metadata tree or Results task area.
2. Click the Email link in the upper right corner.
Emailing Metadata Object Details 31

The Email Metadata Objects page appears.
3. Enter the email addresses of the email recipients, subject of the email, and the email
message text.
4. Select one of the following formats:
PDF Document
Embedded HTML
Microsoft Excel
XML Document
5. Click Attachments to attach additional files in the email.
6. Click Send.

Chapter 3
Working with Metadata Objects

Overview, 34
Adding Metadata Objects, 35
Editing Metadata Objects, 38
Deleting Metadata Objects, 40
Exporting Metadata Objects, 41
33
Overview
You can view metadata objects and their properties stored in the Metadata Manager
Warehouse from the Metadata Directory page. You can also create new metadata objects using
Metadata Manager. You may need to create additional metadata objects in the Metadata
Manager Warehouse that do not exist in the source repository.
You can perform the following tasks on metadata objects:
Add metadata objects. For more information, see Adding Metadata Objects on page 35.
Edit metadata objects. For more information, see Editing Metadata Objects on page 38.
Delete metadata objects. For more information, see Deleting Metadata Objects on
page 40.
Export metadata objects, and their properties and associations, to an external file. For
more information, see Exporting Metadata Objects on page 41.
To add, create, or delete metadata objects, you must have one of the following roles:
Advanced Provider
Schema Designer
System Administrator
For more information about roles, see Setting Privileges and Access Permissions in the
Metadata Manager Administrator Guide.
34 Chapter 3: Working with Metadata Objects

Adding Metadata Objects
You create objects in Metadata Manager when you want to represent metadata that does not
exist in the source system. When you add an object, Metadata Manager creates the first
version of the object with the default properties.
Table 3-1 describes the default properties of an object:
Table 3-1. Default Properties of Objects Created on the Metadata Directory Page
Property Description
Version Date on which you created the object followed by the version number 1, such as: June 01,
2004 (1).
Source Creation Date Date and time you created the object in Metadata Manager.
Warehouse Insertion Date Date and time you inserted the object into Metadata Manager. Since you create the object
in Metadata Manager, the Source Creation Date and Warehouse Insertion Date are the
same.
Effective From Date Date and time from which the object is valid. The object is valid immediately after you
create the object in Metadata Manager.
Effective To Date Date to which the object is valid. By default, this value is January 01, 3714 12:00 a.m. The
default date changes each time you create a newer version of the object.
Properties Object properties based on its class. You specify the class when you create the object in
Metadata Manager.
Associations Association between the object with its parent object. For example, if you add an object
under a folder, Metadata Manager associates the object with the folder.
When you add an object, you receive the same permissions that you have on the parent of the
object. All other users receive read-only permission.
Use the following guidelines to add a repository object:
You must have write permission on the repository or repository folder to which you
want to add the object. For more information about Metadata Manager permissions, see
Setting Privileges and Access Permissions in the Metadata Manager Administrator Guide.
The class of the object must have the New Objects Can Be Created option enabled. For
more information about this option, see Implementing a Metamodel in the Metadata
Manager Custom Metadata Integration Guide.
To add a metadata object:
1. Click the Find tab.

The Metadata Directory page appears.
2. Select a repository or folder in the Metadata tree.
The folder under which you add the object becomes the parent of the object.
Adding Metadata Objects 35

The Create New Object button appears in the Details task area.
3. Click Create New Object.
The Select Class window appears.
4. Select a class for the object, and then click OK.

Tip: You can select a repository type and package name to limit the list of classes that
appear.
The Create New Object page appears.
These properties
vary depending on
the class of the
object.

5. Enter the following information:
Table 3-2. Attributes on the Create New Objects Page
Required/
Attribute Description
Optional
Class Name Read-only Name of the object class.
Repository Read-only Name of the repository for the object.

Name
Name Required Name for the object. Maximum length is 255 characters. The name can
include any character except the following characters:
\/:*?<>|&
The name must be unique within the class of the object and the parent of the
child object cannot have another object with the same name.
Label Optional Display label for the object.
Object ID Required ID for the object.
Object Version Optional Version number for the object. The version is for informational purposes.
Valid Object Optional Indicates whether the object is valid. Clear this option if the metadata is
invalid.
Disabled Object Optional Enable to indicate that the object is not in use in the source repository. For
example, if the object represents metadata for a report in a business
intelligence tool, and the report is not in use, you can select the Disabled
Object option to reflect its status. This option is for informational purposes.
Properties Conditional Metadata Manager displays different properties depending on the class of the
object. If a property name is bold, you must enter a value for the property. If
the property name is not bold, entering a value is optional.
6. Click OK.
Adding Metadata Objects 37

Editing Metadata Objects
You can edit an object to change the object name, attributes, and property values. When you
edit an object, Metadata Manager creates a new version of the object. For more information
about object versions, see Viewing Versions of Metadata Objects on page 17.
To edit a repository object, ensure the following conditions are true:
You have write permission for the repository or repository folder containing the object.
For more information about Metadata Manager permissions, see Setting Privileges and
Access Permissions in the Metadata Manager Administrator Guide.
The class of the object has the Objects Can Be Edited option enabled. For more
information about this option, see Implementing a Metamodel in the Metadata Manager
Custom Metadata Integration Guide.
To edit a metadata object:

2. Select an object in the Metadata Tree task area or Results task area.
The Edit Object button appears at the top of the Details task area.
3. Click Edit Object.

The Edit Object page appears.
4. Modify all applicable attributes.

For a description of each attribute, see Table 3-2 on page 37.
5. Click OK.
Editing Metadata Objects 39

Deleting Metadata Objects
When you delete an object from the source repository, the following actions occur in
Metadata Manager:
The object remains in the Metadata Manager Warehouse, but Metadata Manager marks all
versions of the object as deleted.
The Effective To Date of the latest version of the object changes to the date you deleted
the object.
The object does not appear in the Metadata tree.
Tip: Although deleted objects do not appear in the Metadata tree, you can search for deleted
objects using the Query task area. For more information about searching for deleted objects,
see Viewing Deleted Metadata Objects on page 18.
Use the following guidelines to delete a metadata object:
You must have delete permission on the object. For more information about Metadata
Manager permissions, see the Metadata Manager Administrator Guide.
The class of the object must have the Objects Can Be Deleted option enabled. For more
information about this option, see the Metadata Manager Custom Metadata Integration
Guide.
To delete a metadata object:

2. Select the object in the Metadata Tree task area or Results task area.
The Delete button shows in the Details task area.
3. Click Delete.

Exporting Metadata Objects
When you view metadata objects on the Metadata Directory page, you can export objects to a
file. You can export objects you select in the Metadata Browser or objects that result from a
query. When you export an object, you export its object properties and associations.
You can export objects to HTML, Microsoft Excel, PDF, or XML. You might export objects
to an HTML, a Microsoft Excel, or a PDF file to save or share the properties of objects.
When you export the objects to a Microsoft Excel file, Metadata Manager exports up to 25
objects for each Excel worksheet. Metadata Manager creates unique names for each worksheet
such as (1-25) Result List Details and (26-50) Result List Details.
You export objects to an XML file to import the objects into another Metadata Manager
instance. When you export objects to an XML file, Metadata Manager also exports lineage
information. For more information about exporting and importing metadata objects, see the
To export metadata objects:

2. Select an object in the Metadata tree or perform a search so that Metadata Manager
displays metadata in the Results task area.
3. Click the Export link on the Metadata Directory page.
Export Link
Select export options.
4. Select the results and properties to export.
Exporting Metadata Objects 41

Table 3-3 lists the results and options you can export:
Table 3-3. Export Options for Exporting Object Properties
Export Option Description
Export Object List Exports all objects displayed in the Results task area. When you clear this option and
select an object in the Results task area, Metadata Manager exports only the object you
select. If you do not select objects in the Results task area, Metadata Manager exports all
objects in the Results task area.
By default, Metadata Manager exports all objects in the Results task area.
Details for Object Items to export for the metadata object selected in the Metadata tree:
Selected in - General properties
Metadata Tree - Object properties
- Associations
Note: This option is disabled if you select a group in the Metadata tree. Groups are not
metadata objects. For more information about groups and metadata objects, see the
Details for Objects Items to export for the metadata objects in the Results task area:
in Results Task - General properties
Area - Object properties
- Associations
For more information about associations, see Working with Object Associations on
page 55.
5. Select the type of file to which you want to export the results:
HTML. Metadata Manager creates and displays and HTML file containing the objects
and properties you choose. Choose whether or not to include Metadata Manager icons
in the HTML file.
Microsoft Excel. Metadata Manager creates a spreadsheet containing the objects and
properties you choose.
PDF. Metadata Manager creates a PDF file containing the objects and properties you
choose.
XML. Metadata Manager creates an XML file of the objects and properties you
choose. When you export to an XML file, Metadata Manager exports all object
properties and objects in the results list. Metadata Manager also exports the lineage
information.
6. Click Export.
7. If you export the metadata objects to an Excel, PDF, or XML file, select one of the
following options:
Save the file. To save, specify a file name and location.
Open the file. Metadata Manager opens the file in the appropriate application.

Chapter 4
Working with Object Properties

Overview, 44
Viewing Object Properties, 45
Adding Object Properties, 49
Editing Object Properties, 52
Deleting Object Properties, 53
43
Overview
Object properties are details about a metadata object. Properties may include a description of
the object, contact information for a repository administrator, or a hyperlink to a document.
For more information about properties, see Metadata Manager Concepts in the Metadata
Manager Administrator Guide.
You can perform the following tasks on object properties:
View object properties. For more information, see Viewing Object Properties on
page 45.
Add object properties. For more information, see Adding Object Properties on page 49.
Edit object properties. For more information, see Editing Object Properties on page 52.
Delete object properties. For more information, see Deleting Object Properties on
page 53.
When you add, edit, or delete properties from an object, Metadata Manager creates a new
version of the object. For more information about object versions and deleted objects, see
Viewing Versions of Metadata Objects on page 17.
When you create a new property for an object, the new property appears in Object Properties
tab on the Metadata Directory page.
44 Chapter 4: Working with Object Properties

Viewing Object Properties
Metadata Manager displays the following types of properties for each source repository object:
General properties
Object properties
Viewing General Properties

You can view general properties of objects on the General Properties tab on the Metadata
Directory page. You can view general details about any source repository object. General
properties apply to all types of source repository objects stored in the Metadata Manager
Warehouse, regardless of the class to which they belong.
Note: You cannot change the properties that appear on the General Properties tab.
To view general properties:

2. Select the metadata object about which you want to view properties.
3. Click the General Properties tab.
The General Properties tab displays general properties for the selected object.
Table 4-1 describes the general properties:
Table 4-1. General Properties
Object Name Name of the source repository object in the Metadata Manager Warehouse.
Class Type Type of class. Class type allows you to categorize similar types of classes. For
example, you can categorize Oracle database table class, Teradata database table
class, and Sybase database table class under a database-independent class type
called Table.
Viewing Object Properties 45

Table 4-1. General Properties
Class Name of the class of the object. Source repositories are members of the class IMM
Repository.
Repository Name Name of the source repository to which the object belongs. If the object is a source
repository, the value for Repository Name is Metadata Repository.
Object ID ID of the object.
Source Creation Date Date the object was created in the source repository or the Metadata Manager
Warehouse. You can create user-defined properties in Metadata Manager. For
more information about adding user-defined properties, see Adding Object
Properties on page 49.
Source Update Date Date the object was updated in the source repository or the Metadata Manager
Warehouse. You can add user-defined properties in Metadata Manager to update
the object. For more information about adding user-defined properties, see Adding
Object Properties on page 49.
If the object has not been updated since it was created, the Source Creation Date
and the Source Update Date are the same.
Warehouse Insertion Date Date the object was loaded into the Metadata Manager Warehouse. If the object
was created in the Metadata Manager Warehouse, the Warehouse Insertion Date
and Source Creation Date are the same.
Warehouse Update Date Date the object was updated in the Metadata Manager Warehouse. If the object has
never been updated, the Warehouse Insertion Date and the Warehouse Update
Date are the same.
Effective From Date Date from which the object is valid.
Effective To Date Date to which the object is valid.
Version Number Version of the object.
Deleted Object Indicator that specifies if the object is deleted in the source repository.
Valid Object Indicator that specifies if the object is valid in the source repository.
Disabled Object Indicator that specifies if the object is disabled in the source repository.
Viewing Object Properties

You can view object properties on the Object Properties tab on the Metadata Directory page.
Object properties are details that are specific to an object and its class. For any object, the
Object Properties tab displays the object name, class, and the name of the source repository to
which the object belongs. If the object is a source repository, the repository name is Metadata
Repository.
The Object Properties tab also displays other properties that are specific to the class of the
object. You can filter the type of properties that display.

To view object properties:

2. Select the metadata object for which you want to view properties.
You can select an object in the Metadata tree or Results task areas.
3. Click the Object Properties tab.
The Object Properties tab displays the object properties.
Select an option to
filter the properties
you want to appear.
4. To filter the properties, select one of the following options in the Show field:
Required/
Option Description
Optional
Properties With Values Optional Select to display properties that have values. Sometimes, source
repositories do not store property values for particular metadata
objects.
Class Level Properties Optional Select to display properties that apply to the class of the selected
object. For more information about class properties, see
Metadata Manager Concepts in the Metadata Manager
All Properties Optional Select to display all properties.
5. To view information about a property, click the name of a property on the Object
Properties tab.
If the property is user-defined, the details appear on the Edit Property page. For more
information about properties on this page, see Editing Object Properties on page 52.
If the property is predefined, the property details appear on the Property Details page.
Viewing Object Properties 47

The Property Details page displays information about predefined properties.
Table 4-2 describes the attributes that appear on the Property Details page:
Table 4-2. Attributes on the Property Details Page
Property Attribute Description
Name Name of the property.
Object Name Name of the object about which you are viewing property details.
Class Name Name of the class of the object about which you are viewing property details.
Repository Name Name of the source repository to which the object belongs.
Datatype Datatype of the property.
Display Label Name of the property as it appears on the Object Properties tab.
Description Description of the property.
Value Value of the property. This value replaces the default value.
Default Value Default value of the property. The default value appears for all objects that do not
have values for this property.
Usage Description Description of how to use the property.
Editable Indicator that specifies whether you can edit the property for an object. For more
information about editing object properties, see Editing Object Properties on
page 52.
User-defined Indicator that specifies whether the property is created by a user. All other
properties are predefined in Metadata Manager.

Adding Object Properties
You add properties to an object or class to describe characteristics about an object or a set of
objects in a class. Each time you add a property, you create a new version of each object to
which the property applies.
To add a property, the class must have the Extendable option enabled. For more information
about this option, see the Metadata Manager Custom Metadata Integration Guide.
After you add the property, the property appears in the list of properties for the object on the
Object Properties tab. If you applied the property to all objects of the class, the property
appears for all objects of the class.
To add, create, or delete object properties, you must have one of the following roles:
Advanced Provider
Schema Designer
For more information about roles, see the Metadata Manager Administrator Guide.
To add an object property:

3. On the Details task area, click the Object Properties tab.
Note: The Add New Property button displays only if the Extendable option is enabled for
the class.
4. Click Add New Property.
Adding Object Properties 49

The Add New Property page appears.
5. Enter the following information:
Table 4-3. Attributes on the Add New Property Page
Required/
Option Description
Optional
Name Required Name for the property.
Object Name Read-only Name of the object.
Class Name Read-only Class to which the object belongs.
Repository Name Read-only Name of the repository.
Datatype Required Datatype for the property. When you select a URL for the datatype, the
datatype is a hyperlink.
Display Label Required Label for the property. This label displays as the property name on the
Object Properties tab.
Description Optional Description of the property.
Value Required Value for the property. The value appears on the Object Properties tab.

Table 4-3. Attributes on the Add New Property Page
Required/
Option Description
Optional
Default Value Optional Default value for this property. The value appears on the Object Properties
tab if one is not provided.
Usage Description Optional Description about how the source repository uses the property.
Apply to all objects Optional Applies this property to all objects of the class.
of this class
Mandatory Optional Indicator that specifies whether you must provide a value for the property
for each applicable object. The option must be disabled to delete the
property for an object. For more information about deleting object
properties, see Deleting Object Properties on page 53.
Editable Optional Indicator that specifies whether you can edit the property values. For more
information about editing object properties, see Editing Object Properties
on page 52.
6. Click OK.
Adding Object Properties 51

Editing Object Properties
You can edit a user-defined object property to change its attributes. If the property you want
to edit is an object-specific property, you can change several attributes. If the property you
want to edit is a class property, you can change the value of the property. Each time you edit a
property, you create a new version of all objects to which the property applies.
To edit a property, the property must have the Editable option enabled. For more information
about this option, see the Metadata Manager Custom Metadata Integration Guide.
Advanced Provider
Schema Designer
To edit an object property:

2. Select the object in the Metadata Tree task area or Results task area to which the property
applies.
4. Click the property label.
The Edit Property dialog box appears.
5. Modify the applicable attributes defined for the property.
For a description of the attributes, see Table 4-3 on page 50.
6. Click OK.

Deleting Object Properties
You can delete a property if the property no longer applies to the object. Each time you delete
a property, you create a new version of the object. You can delete user-defined properties. To
delete a user-defined property, click Delete on the Edit Property page.
When you delete a property for an object, the property no longer appears on the list of
properties for the object. When you delete a property that applies to all objects of a class,
Metadata Manager deletes the property for the object you are viewing.
To delete a property for an object, the property must have the Mandatory option disabled.
For more information about these options, see the Metadata Manager Custom Metadata
Integration Guide.
Advanced Provider
Schema Designer
To delete an object property:

4. Click the property name.
The Edit Property page appears.
5. Click the Delete button.
Deleting Object Properties 53

Chapter 5
Working with Object Associations

Overview, 56
Viewing Object Associations, 57
Adding Object Associations, 60
Deleting Object Associations, 62
55
Overview
You can view object associations on the Associations tab on the Metadata Directory page.
Object associations are explicit relationships between metadata objects. For example, a
database table, CUSTOMERS, contains the columns CUST_NAME and CUST_ADDRESS.
Metadata Manager defines a class association between database tables and database table
columns. Each particular database table has an object association with each of its columns.
Therefore, the CUSTOMERS database table has an object association with the
CUST_NAME column and another object association with the CUST_ADDRESS column.
You can perform the following tasks on object associations:
View object associations. For more information, see Viewing Object Associations on
page 57.
Add object associations. For more information, see Adding Object Associations on
page 60.
Delete object associations. For more information, see Deleting Object Associations on
page 62.
You can add an association between the latest versions of two objects to define a relationship
between them. You cannot add or delete associations between older versions of objects. For
more information about associations, see the Metadata Manager Administrator Guide.
56 Chapter 5: Working with Object Associations

Viewing Object Associations
The Associations tab displays associations between the selected object and other objects that
are loaded into the Metadata Manager Warehouse. If an association does not appear for two
objects that are related, you can add a new association for those objects using the predefined
class associations. If you do not find an association that represents the relationship you want
to establish between two objects, ask the Metadata Manager administrator to create the class
association. For more information about class associations, see the Metadata Manager
To view object associations:

2. Select the object for which you want to view associations.
3. Click the Associations tab.
The Associations tab displays the associations to which the selected object is assigned.
4. Click the name of the object, in the Object Name column, to display details about the
associated object.
5. Click the name of the association, in the Name column, to view details about the
association.
Viewing Object Associations 57

The Object Association Details page displays the association details.
Table 5-1 lists the association details that appear on the Object Associations Details page:
Table 5-1. Attributes on the Object Association Details Page
Attributes Description
Association Name Name of the association.
From Object Name Name of the object associated with the To Object.
From Object Class Name Name of the class to which the From Object belongs.
From Object Repository Name Name of the source repository containing the From Object.
To Object Name Name of the object associated with the From Object.
To Object Class Name Name of the class to which the To Object belongs.
To Object Repository Name Name of the source repository containing the To Object.
From End Label Label that Metadata Manager uses to represent the role of the From Object in
the association.
To End Label Label that Metadata Manager uses to represent the role of the To Object in the
association.
From Cardinality Cardinality of the From Object in relation to the To Object.
To Cardinality Cardinality of the To Object in relation to the From Object.
Effective From Date Date from which the association is valid.
Effective To Date Date to which the association is valid.

Table 5-1. Attributes on the Object Association Details Page
Warehouse Insertion Date Date when the association was loaded into the Metadata Manager Warehouse.
Warehouse Update Date Date when the association was last updated in the Metadata Manager
Warehouse. If the association has not been updated, the Warehouse Update
Date and the Warehouse Insertion Date are the same.
Viewing Object Associations 59

Adding Object Associations
If an association does not exist between two objects, you can add the association using
Metadata Manager.
Use the following guidelines to add associations between two objects:
You must have the Schema Designer role and Write permissions on the repository in
which you want to create the association. If you do not, the Add Association button does
not appear. By default, all users, except the System Administrator, have read-only
permissions. For more information about Metadata Manager permissions, see Setting
Privileges and Access Permissions in the Metadata Manager Administrator Guide.
An association must exist between the classes of the objects. If a class association does not
exist, ask the system administrator to create a class association. For more information
about creating class associations, see the Metadata Manager Custom Metadata Integration
Guide.
The class association must have the Objects Can Be Associated option enabled. For more
information about this option, see the Metadata Manager Custom Metadata Integration
Guide.
To add or delete object associations, you must have one of the following roles:
Advanced Provider
Schema Designer
To add an object association:

2. Select the object for which you want to create an association.
3. On the Details task area, click the Associations tab.
4. Click Add New Association.

The Select Association page appears.
Note: The Add New Association button appears if you have the Schema Designer role and
have Write permissions on the repository in which you want to create the association. For
more information about roles, see Setting Privileges and Access Permissions in the
5. Select the repository type to which the association belongs.
6. Select the package to which the association belongs.
7. Select an association.
8. Click OK.
The Select Object page appears.
9. Select the To Object for which you want to create the association.
When you select a folder in the left task area of the Select Object page, the objects display
in the right task area.
Click the Select button next to the object you want to use.
10. Click OK.
Adding Object Associations 61

Deleting Object Associations
You can delete associations between objects. When you delete an association, the association
no longer appears in the list of associations for the object.
To delete associations between objects, the class association must have the Object Associations
Can Be Deleted option enabled. For more information about this option, see the Metadata
Manager Custom Metadata Integration Guide.
To add or delete object associations, you must have one of the following roles:
Advanced Provider
Schema Designer
To delete an object association:

3. On the Details task area, click the Associations tab.
4. Click the association name.
The Object Associations page appears.

Chapter 6
Working with Object Links

Overview, 64
Viewing Object Links, 65
Adding Object Links, 66
Deleting Object Links, 68
63
Overview
You can view object links on the Object Links tab on the Metadata Directory page. Object
links allow you to link related objects without navigating the Metadata tree or searching for
the object. For example, you add a data dictionary in Metadata Manager that defines
corporate-wide financial reporting terms. The data dictionary includes a definition for the
term Gross Margin. You can link the Gross Margin metadata object to each business
intelligence report that uses this object. Auditors can use the definition in the data dictionary
to validate the calculation used to determine the Gross Margin metrics in each business
intelligence system.
You can perform the following tasks on object links:
View object links. For more information, see Viewing Object Links on page 65.
Add object links. For more information, see Adding Object Links on page 66.
Delete object links. For more information, see Deleting Object Links on page 68.
64 Chapter 6: Working with Object Links

Viewing Object Links
You can view object links from the Object Links tab.
To view an object link:

2. Select the metadata object for which you want to view object links.
3. Click the Object Links tab.
The Object Links tab displays all object links defined for the selected object.
4. Click an object name to view the details about the object.

5. Click the link name to view the details about the link.
The Object Link Details page displays the details for the object link.
Table 6-1 discusses the object link details that appear on the Object Link Details page:
Table 6-1. Attributes on the Object Link Details Page
Object Link Label Label of the object link.
From Object Name Name of the From Object in the link.
To Object Name Name of the To Object in the link.
Description Description of the object link.
Viewing Object Links 65

Adding Object Links
You can add an object link to an object. After you create the object link, whenever you select
the object in the Metadata Tree task area or Results task area on the Metadata Directory page,
the new link appears on the Objects Link tab.
To add or delete object links, you must have one of the following roles:
Advanced Provider
Schema Designer
To add an object link:

2. Select an object on the Metadata Directory page.
3. In the Details task area, click the Object Links tab.
4. Click Add New Link.

The Create New Object Link page appears.

5. Click Select.
The Select To Object page appears.
Go Button
To display objects in the right-side task area, complete one of the following tasks:
Select an object in the left-side task area.
In the Query task area, select the repository and class of the To Object, and click the
Go button.
6. Click Select next to the object that you want to use as the To Object in the link.
The Create New Object Link page appears again, displaying the To Object you selected.
7. Optionally, enter a new name for the link in the Object Link Label attribute.
8. Optionally, enter a description of the link.
9. Click OK.
Adding Object Links 67

Deleting Object Links
You can delete links between two objects. When you delete a link, the link no longer appears
in the list of links on the Object Links tab.
To add or delete object links, you must have one of the following roles:
Advanced Provider
Schema Designer
To delete an object link:

3. On the Details task area, click the Object Links tab.
4. Click the link name.
The Object Link Details page appears.
5. Click Delete.

Chapter 7
Working with Report Links

Overview, 70
Viewing Report Links, 71
Adding Report Links, 73
Editing Report Links, 77
Deleting Report Links, 78
69
Overview
You can view report links on the Report Links tab on the Metadata Directory page. You can
use report links to run reports on a particular metadata object. You assign a Metadata
Manager report to a specific object when you create a report link.
You can perform the following tasks on report links:
View report links. For more information, see Viewing Report Links on page 71.
Add report links. For more information, see Adding Report Links on page 73.
Edit report links. For more information, see Editing Report Links on page 77.
Delete report links. For more information, see Deleting Report Links on page 78.
When you add or modify a report link, you can create a run report button to run the
associated report. The run report button appears in the Details task area. If you create a run
report button and apply it to all objects associated with a particular class, the button appears
when you select any object of the class. You can add a maximum of three run report buttons
for each object.
When you add or modify a report link, you can add filters to the report based on a metric or
attribute. When you run the report from the report link or run report button, Metadata
Manager runs the report using the filters you specify.
Links to data lineage must contain filters. If you do not specify a filter, when you try to run
the report from a report link, Metadata Manager displays the following error:
Report link to Lineage report must have exactly one filter which has
'Object Key' as the 'Filter Value'. Edit the report link definition in
Metadata Directory to correct the problem.
After you create the report link, when you select an object to which the report link is assigned,
the new link appears on the Report Links tab.
To add, edit, or delete report links, you must have one of the following roles:
Advanced Provider
Schema Designer
70 Chapter 7: Working with Report Links

Viewing Report Links
You can view report links from the Report Links tab. When you click the report name link on
the Report Links tab, Metadata Manager runs the report on the selected object. By default,
Metadata Manager provides report links for the following reports:
Data Lineage
Where-Used Analysis
Note: Metadata Manager does not provide report links or run report buttons for custom
metadata objects. You can add a report link and run report button for Metadata Manager
Data Lineage for a custom object after you load the object into the Metadata Manager
Warehouse.
To view a report link:

2. Select an object for which you want to view report links.
3. Click the Report Links tab.
The Report Links tab shows the report links for the selected object.
4. Click a report name to run the report defined in the report link.
5. Click a report link name to view details about the report link.
Viewing Report Links 71

The Report Link Details page displays all report links for the selected object.
Table 7-1 describes the attributes that appear on the View Report Link page:
Table 7-1. Attributes on the Report Link Details Page
Required/
Attribute Description
Optional
From Object Name Read-only Object for which the report link was created.
Report Name Read-only Name of the report.
Report Label Required Name of the report link.
Run Report Button Name Optional Name of the run report button.
Description Optional Description of the report.
Apply to all objects of this class Optional Indicates whether the report link applies to all objects of the
class.
Filter Type Conditional Filter type is set to Metric or Attribute. Required if you want to
create a report filter.
Attribute/Metric Conditional Name of metric or attribute used in the filter. Required if you
want to create a report filter.
Select Object Property Optional Value of the object property for the filter if you do not enter a
custom value.
Enter Custom Value Optional User-defined value for the filter if you do not enter an object
property value.

Adding Report Links
You might add a report link when you are loading custom metadata into the Metadata
Manager Warehouse. For example, you can run data lineage on custom metadata. To make it
easier to run the report, you can create a report link that links a particular custom metadata
object to data lineage.
To add a report link:

3. On the Details task area, click the Report Links tab.
4. Click Add New Link.
Adding Report Links 73

The Create New Report Link page appears.
5. Click the Select button next to Report Name to select a report for the report link.
The Select Report page appears.
6. Click a folder to display a list of reports.
7. Click the Select button next to the report to which you want to link the object.

The Create New Report Link page appears again, showing the report name you selected.
8. Enter a value for Report Label to name the report link.

By default, the report label is the report name.
9. Optionally, add a run report button by entering a name for the button or clicking Select
to use an existing name.
If you do not want to add a run report button, go to step 13.
10. Click Select next to the Run Report Button Name field.
The Select Run Report Button page appears.
11. Select a name for the run report button.

12. Click OK.
Adding Report Links 75

The Create New Report Link page appears.
13. Optionally, enter a description of the report.
14. Optionally, select the Apply to All Objects of This Class option to add the report link to
all objects of the class.
15. Enter the following information to add report filters:
Table 7-2. Report Filter Options
Required/
Report Filter Attribute Description
Optional
Filter Type Required Filter type. Options include Metric and Attribute.
Attribute/Metric Required Name of the attribute or metric used for the filter.
Select Object Property Conditional Name of the object property used for the filter. For example, if you
want to run the Workflow Trend QTD by Month report for a
particular workflow, select the object ID of the workflow. When
Metadata Manager runs the report, it provides a report for the
workflow.
If you do not select an object property, you must enter a custom
value.
Enter Custom Value Conditional Custom value used to filter the report data. If you do not enter a
custom value, you must select an object property.
Note: If you select Data Lineage, you must add a filter.
For more information about data lineage, see Working with Data Lineage on page 79.
16. Click Add to add the filter.
17. Click the Delete button to remove a filter.
18. Click OK to add the report link.

Editing Report Links
When you edit a report link, you can make the following changes:
Select a different report for the report link.
Change the link name and description.
Change the filter options for the report.
To edit a report link:

3. Click a report link name.
The Edit Report Link page appears.
4. Modify the applicable report link attributes.
For a description of each attribute, see Table 7-2 on page 76.
5. Click OK.
Editing Report Links 77

Deleting Report Links
You can delete report links. When you delete a link, Metadata Manager also deletes the run
report button associated with the report link.
To delete a report link:

4. Click the link name.
The Edit Report Link page appears.

Chapter 8
Working with Data Lineage

Overview, 80
Viewing Data Lineage, 82
Running Data Lineage, 91
Filtering Data Lineage Results, 93
Working with Object Properties in Data Lineage, 95
Setting Up Remote Access to Data Lineage, 97
79
Overview
Data lineage refers to the path through which data flows. Data lineage describes the origin of
data and the process by which it arrived in a target location. Data lineage can span multiple
repositories.
Many applications generate data that other applications use. Each application transforms the
data and sometimes passes the transformed data to other applications. It gets progressively
more difficult to trace data lineage when you have a growing network of applications sharing
and transforming the same set of data.
Applications use procedures to move or transform data. The applications store the procedures
as metadata. To display data lineage, Metadata Manager uses the metadata to determine how
each application moves or transforms data.
You can use data lineage to perform the following tasks:
Analyze the data flow within a single source repository or across multiple source
repositories
Troubleshoot data transformation errors
You can run data lineage on metadata loaded into the Metadata Manager Warehouse,
including custom metadata. For more information about setting up custom metadata to
display in data lineage, see the Metadata Manager Custom Metadata Integration Guide.
You can export data lineage results to a file, such as a PDF file. For more information about
exporting, see Exporting Results on page 109. You can also email the results. For more
information about emailing results, see Emailing Results on page 111.
Analyzing Data Flows

You can use data lineage to analyze data flow. You can trace data from the source to the target
destination. Data lineage can provide the following data flow information:
Origin of data
Data transformation
Target destination
Data lineage can also show the data flow across multiple repositories if you set up the
connection assignments between the source repositories. For more information about setting
up connection assignments, see the Metadata Manager Administrator Guide.
For example, you can analyze how data is transformed in PowerCenter and how the output
data in PowerCenter is used in Business Objects. You can analyze the data flow at the table
level to determine which PowerCenter sources, both relational and flat file, are used to
populate data in particular PowerCenter targets. You can drill into the table-level results to
determine how PowerCenter transforms data at the port level. You can then analyze how and
where data in the PowerCenter target ports is used in Business Objects reports.
80 Chapter 8: Working with Data Lineage

PowerCenter and Business Objects do not physically store the data that gets transformed.
Instead, the data resides in a database. For example, the PowerCenter source definitions and
target definitions might be built on database tables. Data lineage includes the underlying
databases.
The following figure displays a possible data lineage diagram:
Microsoft
SQLServer PowerCenter Oracle Business Objects
Database Repository Database Repository
Connection Connection Connection

Assignment 1 Assignment 2 Assignment 3
Troubleshooting Data Transformation Errors

You can also use data lineage to troubleshoot data transformation errors. If you suspect
incorrect data in a particular field, you can determine where the data came from and view the
expressions used to transform it.
Overview 81
Viewing Data Lineage
Data lineage shows the following information:
Lineage diagram. Shows a visual representation of the data flow.
Details. Shows the expressions used to transform data.
You can also filter the results of data lineage to focus on particular areas of the data flow.
Figure 8-1 shows the task areas in data lineage:
Figure 8-1. Data Lineage Layout
Limit Lineage To
Task Area
Lineage View
Task Area
Detailer View
Task Area
Data lineage contains the following task areas:

Limit Lineage To task area. Use to filter objects in the lineage diagram to focus on
particular areas of the data flow. For more information about filtering objects, see
Filtering Data Lineage Results on page 93.
Lineage View task area. Use to view the lineage diagram. For more information about the
lineage diagram, see Viewing the Lineage Diagram on page 85.
Detailer View task area. Use to display field-level details, such as the expression used to
transform data. For more information about field-level details, see Viewing Field-Level
Details on page 87.
Types of Objects in Data Lineage

Metadata Manager shows the following types of objects in data lineage:
Source repositories. Source repositories contain metadata objects. Examples include
database instances, data modeling tools, business intelligence tools, data integration tools,
and Online Analytical Processing (OLAP) tools.
Tasks. A task represents a use of a transformation to move data between data structures.
For example a PowerCenter mapping may be used by multiple sessions. In this case, each
session is a task and the mapping is the transformation for a task.

Transformations. Transformations determine how data flows between data structures in a
single repository. Transformations can be reusable or non-reusable. A transformation is
reusable if multiple tasks use the transformation. Examples of transformations include:
PowerCenter mappings (reusable transformation)
Database views (non-reusable transformation)
Data structures. Data structures contain fields, that contain data. Examples of data
structures include:
PowerCenter source definitions, target definitions, or Source Qualifier transformations
Database tables and views
Data Analyzer reports, dimensions, and schema tables
Fields. Fields are components of data structures. Fields contain or represent data. A
database column contains data. A database view column represents data contained in a
database table column. Examples of fields include:
Columns of database tables and views
Ports of PowerCenter transformations
Metrics and attributes in business intelligence reports
Object Handling in Data Lineage

The following sections describe how data lineage handles source repository objects.
Parent Objects
The lineage diagram displays the parent of each object. If the container of the object is not the
parent, the lineage diagram displays the parent in parentheses next to the object.
Container of V_DEALERSHIP
Parent of V_DEALERSHIP
Parent of MM_DEALERSHIP
Container of MM_DEALERSHIP
Stored Procedures
Stored procedures display as data structures. Data lineage treats database stored procedures as
transformations, source, or target structures in the diagram.
Public Synonyms
Public synonyms display for all database tables.
PowerCenter Connections
Metadata Manager can display data lineage between PowerCenter source repositories and flat
file or database sources and targets. If the relational connection is defined in PowerCenter,
Viewing Data Lineage 83

Metadata Manager can extract the connection information to create lineage between
PowerCenter and the database.
If the relational connection is defined in a parameter file, Metadata Manager can extract the
connection information from the parameter file and load it into the Metadata Manager
Warehouse. To extract connection information from a parameter file, configure the
connection parameter file in the Metadata Manager Console. For more information about
using connection parameter files, see Working with XConnects in the Metadata Manager
Reusable Transformations
Since a reusable transformation can be used multiple times in the source repository, Metadata
Manager displays each reusable transformation with its corresponding task. Metadata
Manager displays the task to show the context in which the transformation is used.
For example, Metadata Manager shows a PowerCenter mapping (transformation) with its
corresponding session (task).
S_PROMOTIONS_LOAD is a task.
M_PROMOTIONS_DM_LOAD is a
transformation. They both are enclosed in
a box in the lineage diagram.
Metadata Manager does not show the task for non-reusable transformations.
Viewing Data Lineage

You can perform the following tasks in data lineage:
Focus on field-level details or data structure-level details.
Show properties of objects that display in data lineage.
Export or email data lineage results.
To view data lineage:
1. Run data lineage on an object.

For more information about running data lineage, see Running Data Lineage on
page 91.

The task area buttons appear.
Detailer View Button
Lineage View Button
Default View Button
2. Select one of the following buttons:

Default View. Click to show the Limit Lineage To, Lineage View, and Detailer View
task areas.
Lineage View. Click to show the Limit Lineage To and Lineage View task areas.
Detailer View. Click to show the Limit Lineage To and Detailer View task areas.
3. Place the pointer over the object in the lineage diagram to view the object properties.
For more information about object properties in the lineage diagram, see Working with
Object Properties in Data Lineage on page 95.
4. Click a field in the Detailer View task area to view field-level details.
For more information about field-level details, see Viewing Field-Level Details on
page 87.
5. Click Export to export the data lineage results to a file.
For more information about exporting results, see Exporting Results on page 109.
6. Click Email to email the lineage results.
For more information about emailing results, see Emailing Results on page 111.
Viewing the Lineage Diagram

The Lineage View task area displays the lineage diagram. The lineage diagram displays
repositories, tasks, transformations, and data structures included in the data flow.

Figure 8-2 shows a lineage diagram in the Lineage View task area:
Figure 8-2. Lineage Diagram
Lineage View task

area displays the
lineage diagram.
The Lineage View task area in Figure 8-2 shows that the M_F_PROMOTIONS_EXTRACT
mapping in the Mersche Motors PowerCenter repository contains the following data
structures:
FILE_PROMOTIONS. A flat file source definition for the mapping.
SQ_PROMOTIONS. The Source Qualifier transformation in the mapping.
EXP_PROMOTIONS. The Expression transformation in the mapping.
TF_PROMOTIONS. The target definition for the mapping.
The task area also shows that the TF_PROMOTIONS target definition in PowerCenter is a
table in the Mersche Motors Oracle database.
If the lineage diagram for the selected object has more than 600 data structures, Metadata
Manager collapses the lineage diagram and displays lineage at the repository level. It shows
the following objects:
The object on which you ran data lineage
The parent transformation of the object
Data structures that belong to the parent transformation of the object
It does not show other data structures, transformations, or fields.
To view the lineage diagram:

page 91.
2. Select the Default View or Lineage View button to display the Lineage View task area.
3. Specify a filter to limit the number of objects that display in the lineage diagram.
For more information about filtering objects, see Filtering Data Lineage Results on
page 93.
4. Place the pointer over an object to view properties about the object.
For more information about object properties, see Working with Object Properties in
Data Lineage on page 95.

Viewing Field-Level Details
The Detailer View task area displays field-level details about the field highlighted in this task
area.
The following figure shows the field-level details for the CHANGED_BY_ID field:
Participating Input Fields Output Fields Field Expression Data Lineage

Fields section section section section For section
This task area contains the following sections:

Data Lineage For. This section displays the name of the data structure. If you select a field
as the subject for lineage, the Data Lineage For section displays the name of the data
structure containing the subject field.
Participating Fields. A participating field is a field in the data structure that is listed in the
Data Lineage For section. If you select a field as the subject for lineage, the Participating
Fields section displays the name of the field. If you select a data structure as the subject for
lineage, this section displays all fields contained in the data structure.
Input Fields. An input field provides input data to the selected participating field. The
Input Fields section displays the following information about each input field:
Name of the parent data structure containing the input field
Name of the input field
Repository to which the input field and corresponding parent data structure belong
Output Fields. An output field receives output data from the selected participating field.
The Output Fields section displays the following information about each output field:
Name of the parent data structure containing the output field
Name of the output field
Repository to which the output field and corresponding parent data structure belong
Field Expression. The Field Expression section displays the expression used to transform
the data from each input field into the data contained in the selected participating field.
The equals expression (=) means that the input field passes the value to the participating
field without any transformation.

Figure 8-3 shows field-level details for the CHANGED_BY_ID port in the
EXP_PROMOTIONS PowerCenter Expression transformation:
Figure 8-3. Field-Level Details
Participating Fields section
The following table summarizes the field-level details:
Input Field Field Participating Field Output Field

(Data Structure) Expression (Data Structure) (Data Structure)
CHANGED_BY_ID = CHANGED_BY_ID CHANGED_BY_ID

(SQ_PROMOTIONS) (EXP_PROMOTIONS) (TF_PROMOTIONS)
The field expression is an equal sign (=). This means that the input port in the
SQ_PROMOTIONS Source Qualifier transformation passes the same value to the port in the
EXP_PROMOTIONS Expression transformation. The source data is not transformed. These
fields are called pass-through fields. Fields that transform the source data are called
transformation fields.
The Participating Fields section distinguishes pass-through fields from transformation fields.
The names of pass-through fields appear in light blue. The names of transformation fields
appear in Burgundy.

The following figure shows transformation fields and pass-through fields:
Pass-through field
Transformation field
To view field-level details:

page 91.
2. Select the Default View or Detailer View button to display the Detailer View task area.
3. Complete one of the following tasks:
In the Lineage View task area, select a data structure in the lineage diagram to display
field-level details about the data structure.
-or-
In the Detailer View task area, select a field, parent data structure, or repository in the
Detailer View task area to display field-level details about the selected object.
4. Select a participating field in the Detailer View task area.
The Detailer View task area displays field-level details for the selected participating field.
Viewing Data Lineage History

Each time you run data lineage on a new object, Metadata Manager appends the object name
to the Lineage trail. The Lineage trail displays the sequence of objects on which you ran data
lineage. The Lineage trail tracks the last nine objects on which you ran data lineage. Metadata
Manager clears the Lineage trail when you close the window that displays data lineage and
where-used analysis.

Figure 8-4 displays a Lineage trail:
Figure 8-4. Lineage Trail

The Lineage trail
shows the
sequence of objects
on which you ran
data lineage.
To view data lineage history:

page 91.
2. Run data lineage on another object.
The Lineage trail appears above the lineage diagram after you run lineage on a second
object.
3. Click an object in the Lineage trail to run data lineage on that object again.

Running Data Lineage
Use the following guidelines to run data lineage:
If you want to display connections between databases and other repository types, load
the database metadata first, and then load the metadata from the other repository types.
After you complete the first metadata loads, you can load the metadata in any order.
The metadata in the Metadata Manager Warehouse must be synchronized with the
metadata in the source repositories. The Metadata Manager Warehouse must have the
latest metadata. If the Metadata Manager Warehouse does not have the latest metadata,
lineage may not display properly. For example, if you create a new database table, create a
new PowerCenter source definition, and you only load the PowerCenter source definition,
Metadata Manager cannot display lineage from the PowerCenter source definition to the
database table.
The connection assignments must be current. For more information about updating the
connection assignments, see the Metadata Manager Administrator Guide.
You can run data lineage iteratively. To run data lineage on a different object, right-click the
object in the lineage diagram or the name of a participating field in the Detailer View task
area, and then click Metadata Manager Data Lineage. The lineage diagram tracks the history
of each object on which you run data lineage for the current session. For more information
about data lineage history, see Viewing Data Lineage History on page 89.
You can run data lineage from the following areas:
Metadata Directory
Where-used analysis
For more information about running data lineage from the Metadata Directory or
Information Directory, see Running Metadata Manager Reports on page 116.
Running Data Lineage 91

You must install Adobe SVG Viewer 3.0 on the machine that displays the lineage diagram.
Without SVG Viewer, you cannot see the lineage diagram. If you run data lineage and you do
not have SVG Viewer installed, you receive the following message:
Click Accept to install SVG Viewer.

You must have read permission on the Data Lineage report to run the report. If you do not
have permission, you cannot run data lineage on any object. For more information on setting
permissions, see Setting Privileges and Access Permissions in the Metadata Manager
To run data lineage from where-used analysis:
1. In where-used analysis, click Tree View.

2. Select an object in the Where-Used Analysis tree.
3. Click the Lineage tab or the Data Lineage button.
Metadata Manager displays data lineage on the selected object.

Filtering Data Lineage Results
Use the Limit Lineage To task area to filter data lineage results. You can filter based on the
following criteria:
Domain
Repository
Upstream or downstream
A domain is a category for repository types. For example, Metadata Manager packages a
repository type for Oracle, IBM DB2, and Microsoft SQL Server databases. All databases
belong to the Database Management domain.
Metadata Manager provides the following domains:
Business Intelligence
Data Integration
Data Modeling
Database Management
You can filter the results based on particular domains. You can select any domain that applies
to data lineage for the selected object. For example, if you run data lineage on a Data Analyzer
object and the data lineage include objects from an Oracle and a Data Analyzer source
repository, you can select the Database Management or Business Intelligence domain.
If you select No Domains, Metadata Manager displays lineage at the repository level, showing
the following objects:
The object on which you ran data lineage
The parent transformation of the object on which you ran data lineage
Data structures that belong to the same parent transformation
Metadata Manager does not show other data structures, transformations, or fields. For more
information about transformations, see Types of Objects in Data Lineage on page 82.
You can filter the results based on particular source repositories. For example, you can view
data lineage within a specific Data Analyzer source repository. You can also filter the results
upstream, downstream, or both. If you select upstream, data lineage shows all objects involved
in the lineage up to the repository containing the object selected for lineage. It will not show
any objects that are affected after the selected object. If you select downstream, the report
shows all objects affected after the selected object, including the repository containing the
selected object. It does not show any objects involved in the lineage before the repository
containing the selected object.
Filtering Data Lineage Results 93

The following figure shows downstream and upstream for an object selected in repository B:
Data Flow
A B C
Upstream Downstream
To filter data lineage results:
1. Run data lineage.

page 91.
The Limit Lineage To task area displays.
Limit Lineage To task area

Go button
2. In the Limit Lineage To task area, enter the following criteria in the Limit Lineage To
task area:
Required/
Option Description
Optional
Domain Optional Domains that display in the data lineage.
Repository Optional Source repositories that display in the data lineage.
Upstream/Downstream Optional Direction of the data lineage.
3. Click the Go button to filter the data lineage results.

Working with Object Properties in Data Lineage
You can view object properties in data lineage. Data lineage displays a default set of properties
for all metadata objects. However, you can configure the properties that display for each type
of object.
Viewing Object Properties in Data Lineage

By default, Metadata Manager displays the following properties for all metadata objects:
Class
Label
Source Update Date
Repository Name
Description
For descriptions of the default properties, see Configuring the Display Properties on
page 26.
You can configure the default properties that display. For more information, see Configuring
Object Properties in Data Lineage.
To view object properties in data lineage:

page 91.
2. Place the pointer over the object for which you want to view the properties.
Configuring Object Properties in Data Lineage

Users with the System Administrator or Schema Designer role can change the properties that
display in data lineage for all users. For more information about the default properties and
how to configure them, see Configuring the Display Properties on page 26.
Working with Object Properties in Data Lineage 95

Figure 8-5 shows the Object ID property that is configured to display for objects in the
Oracle Column class:
Figure 8-5. Configured Display Properties for Data Lineage
The object belongs to the Oracle Column class. The Object ID property appears for the object of the
Oracle Column class when you place the pointer over it.

Setting Up Remote Access to Data Lineage
You can launch data lineage from another application such as:
Data Analyzer
PowerCenter Designer
Third-party applications
You may want to launch data lineage while working with the other products. For example,
you need to update a mapplet in PowerCenter Designer. Before making the change, you want
to determine what other objects use the output of this mapplet. You launch Metadata
Manager data lineage on the mapplet from PowerCenter Designer.
When you access data lineage from an application other than Metadata Manager, the external
application makes a call to the Metadata Manager Server to run the data lineage on the
selected object. The Metadata Manager Server searches the Metadata Manager Warehouse for
the specified metadata object, determines the lineage between the object and other objects,
and then displays data lineage for the object.
Metadata Manager uniquely identifies PowerCenter and Data Analyzer objects. However,
Metadata Manager may not be able to uniquely identify other types of metadata objects on
which you run data lineage. If Metadata Manager cannot uniquely identify the object
selected, Metadata Manager returns all objects that match the provided input. You must select
the object on which to run data lineage.
Note: When accessing data lineage from an application other than Metadata Manager, the
types of objects on which you can run data lineage may be limited.
For more information about using third-party applications to launch data lineage, see the
PowerCenter and Data Analyzer are configured to work with Metadata Manager. However,
you must perform a few configuration tasks to enable data lineage from PowerCenter and
Data Analyzer.
To set up data lineage for access from Data Analyzer or PowerCenter, complete the following
steps:
1. Load the latest Data Analyzer or PowerCenter metadata into the Metadata Manager
Warehouse. The metadata in the Metadata Manager Warehouse must be consistent with
the metadata in the Data Analyzer or PowerCenter repository. Otherwise, data lineage
might not provide accurate results. Run the appropriate XConnect to load the Data
Analyzer or PowerCenter metadata. For more information about running XConnects, see
the Metadata Manager Administrator Guide.
2. Set up Data Analyzer or PowerCenter to access the Metadata Manager Server. For more
information about setting up data lineage in Data Analyzer or PowerCenter, see the Data
Analyzer Administrator Guide or PowerCenter Designer Guide respectively.
3. Ensure the Metadata Manager Server is running. The Metadata Manager Server must be
running to launch data lineage from any application.
Setting Up Remote Access to Data Lineage 97

Chapter 9
Working with Where-Used

Analysis
Overview, 100
Viewing Where-Used Analysis, 102
Running Where-Used Analysis, 106
99
Overview
Over time, you may need to modify metadata to support changes in applications. For
example, you may have a business intelligence application that calculates metric A based on a
given rule. Report M requires a new definition for metric A. Before you change the metric
definition, you need to determine the impact on all objects in the business intelligence
application that use metric A. Multiple reports may use metric A, where some of the reports
require the old metric calculation.
You can use where-used analysis to determine where an object is used in one or more source
repositories. An object may be used more than once in a single repository or in multiple
repositories. The object on which you run where-used analysis is the subject. Objects that use
the subject or objects the subject uses are referred to as related objects.
For example, if the subject for where-used analysis is a database table, the subject might have
the following related objects:
Database views. You might build database views based on the database table.
Database columns. The database table contains columns.
Database check constraints. You might define check constraints on the database table.
Database table indexes. You might create indexes on the database table.
PowerCenter mappings. PowerCenter might use the database table as a source or target
definition in a mapping.
Figure 9-1 shows where-used analysis on the column CUST_NAME of the Oracle database
table DM_MM_CUSTOMERS:
Figure 9-1. Where-Used Analysis
Where-used analysis shows where CUST_NAME is used in the Mersche Motors Oracle
database and Mersche Motors PowerCenter repository. The Details For task area shows the
properties for the object selected in the tree (CUST_NAME). The properties state that
CUST_NAME is a column of a database table in the Mersche Motors Oracle database.
100 Chapter 9: Working with Where-Used Analysis

You can export where-used analysis results to an external file, such as a PDF file. For more
information about exporting results, see Exporting Results on page 109.
You can also email the results. For more information about emailing results, see Emailing
Results on page 111.
To determine how a field is used and why it spans across repositories, analyze the field using
data lineage. For more information about data lineage, see Working with Data Lineage on
page 79.
Overview 101
Viewing Where-Used Analysis
You can display where-used analysis in the following formats:
Tree
Tabular
You can run where-used analysis iteratively from the tree format. You can email where-used
results or export them to a file from the Tabular View tab.
Viewing the Tree Format

You can display where-used analysis in a tree format. The tree format displays on the Tree
View tab.
The following figure shows where-used analysis on the Tree View tab:
Subject for
where-used
analysis
Where-Used Analysis Tree task area Details For task area
The Tree View tab contains the following task areas:

Where-Used Analysis Tree. View where the subject is used in each applicable repository.
Details For. View the properties of the object selected in the Where-Used Analysis tree.
The Where-Used Analysis tree highlights the subject in purple and related objects in light
blue. The Where-Used Analysis tree groups related objects by class and displays the classes of
objects in alphabetical order.
The Where-Used Analysis tree uses class associations to display objects hierarchically. Child
objects display under their parent objects. The class association determines the parent and
child objects. For more information about class associations, see the Metadata Manager
The Where-Used Analysis tree displays up to 2,000 objects. If there are more than 2,000
objects, Metadata Manager displays 2,000 objects and notifies you that it does not display all
objects.

The Details For task area displays all properties about the metadata object selected in the
Where-Used Analysis tree. If you select a group in the Where-Used Analysis tree, the Details
For task area does not show properties since groups are not metadata objects. For more
information about groups, see the Metadata Manager Administrator Guide.
To view where-used analysis in the tree format:
1. Run where-used analysis on an object.

You can run where-used analysis iteratively from the tree format. For more information
about running where-used analysis, see Running Where-Used Analysis on page 106.
2. Select Tree View.
The Tree View tab appears.
Figure 9-2. Where-Used Analysis: Tree View Format
3. You can expand and collapse levels to change the objects you see in the Where-Used
Analysis tree.
4. Select an object in the Where-Used Analysis tree to view its properties.
The properties appear in the Details For task area.
5. To run where-used analysis on a different object in the Where-Used Analysis tree, select
the object in the tree, and then click Where-Used.
If you run the where-used analysis on multiple objects in the Tree View tab, Metadata
Manager tracks where-used analysis history. For more information about where-used
analysis history, see Viewing Where-Used Analysis History on page 105.
6. Click Tabular View to change the format to a tabular view.
For more information about the Tabular View tab, see Viewing the Tabular Format on
page 104.
Viewing Where-Used Analysis 103

Viewing the Tabular Format
You can display where-used analysis in a tabular format.
The following figure shows where-used analysis on the Tabular View tab:
Figure 9-3. Where-Used Analysis: Tabular View Format
Subject
Domain
Source Repository
Object Name and
Location
The tabular format of where-used analysis displays the following information about each
object related to the subject:
Domain. Categorizes the repository containing the related object into one of the following
domains: Business Intelligence, Data Integration, Database Management, or Data
Modeling.
Source repository. Specifies the name of the source repository to which the related object
belongs.
Object name. Specifies the name of the related object.
Location. Specifies the location of the related object within the specified repository.
You can email where-used analysis results or export them to a file from the Tabular View tab.
To view where-used analysis in the tabular format:

For more information about running where-used analysis, see Running Where-Used
Analysis on page 106.
2. Select Tabular View.
The Tabular View tab appears.
3. Click Export to export the results.
For more information about exporting results, see Exporting Results on page 109.
4. Click Email to email the where-used analysis results.
For more information about emailing results, see Emailing Results on page 111.

5. Click Tree View to change the format to a tree view.
For more information about the Tree View tab, see Viewing the Tree Format on
page 102.
Viewing Where-Used Analysis History

You can run where-used analysis iteratively from the tree format. Each time you run where-
used analysis on a new subject, Metadata Manager appends the subject name to the Where-
Used trail. The Where-Used trail displays the sequence of subjects previously selected for
where-used analysis.
Figure 9-4 shows that you performed the where-used analysis on CUST_NAME first, and
then on DM_MM_CUSTOMERS next:
Figure 9-4. Where-Used Trail
Shows the sequence of subjects

selected for Where-Used Analysis.
The Where-Used trail tracks the last nine subjects you selected for where-used analysis.
Metadata Manager clears the Where-Used trail when you exit the page that displays where-
used analysis and data lineage.
To view where-used analysis history:

2. Click Tree View to change the format to a tree view.
3. Select another object in the Where-Used Analysis tree.
The Where-Used button appears when you select an object in the Where-Used Analysis
tree.
4. Click Where-Used.
The Where-Used trail displays all objects for which you ran where-used analysis.
5. Click a subject in the trail to run where-used analysis on that subject.
Viewing Where-Used Analysis 105

Running Where-Used Analysis
You can run where-used analysis from the following areas:
Metadata Directory
Data Lineage
For more information about running where-used analysis from the Metadata Directory or
Information Directory, see Running Metadata Manager Reports on page 116.
You can run where-used analysis iteratively from the Tree View tab. To run where-used
analysis on a different object, select the object in the Where-Used tree, and then click Where-
Used. The Where-Used trail tracks the history of each object on which you run where-used
analysis. For more information about where-used history, see Viewing Where-Used Analysis
History on page 105.
You must have read permission on the Where-Used Analysis report to run the report. If you
do not have permission, you cannot run data lineage on any object. For more information on
setting permissions, see Setting Privileges and Access Permissions in the Metadata Manager
To run where-used analysis from data lineage:

2. In Lineage View or Detailer View task area, select an object.
The Where-Used button appears.
3. Click the Where-Used tab or the Where-Used button.
Metadata Manager displays where-used analysis on the selected object.

Chapter 10
Sharing Data Lineage and

Where-Used Analysis Results
Overview, 108
Exporting Results, 109
Emailing Results, 111
107
Overview
You can share data lineage and where-used analysis results with other people using one of the
following methods:
Export. You can export the results to a PDF, HTML, or Microsoft Excel file. You can
archive the file or share the file with others. For more information about exporting results,
see Exporting Results on page 109.
Email. You can also email the results to others. For more information about emailing
results, see Emailing Results on page 111.
108 Chapter 10: Sharing Data Lineage and Where-Used Analysis Results
Exporting Results
You can export data lineage and where-used analysis results to a file in one of the following
formats:
HTML
Microsoft Excel
PDF
You might want to export the results to archive, print, or share the results.
When you export data lineage results to PDF, Metadata Manager displays the lineage diagram
in the PDF file. When you export data lineage results to HTML or Excel, Metadata Manager
creates a file with the following sections:
Participating Objects
Field Level Lineage
Field Level Lineage Ends
Properties
The exported file contains information on the objects that appear in data lineage in Metadata
Manager. For example, if you filter data lineage to display only upstream lineage in Metadata
Manager, the exported file only contains information on objects that are upstream. Likewise,
if you collapse the lineage diagram objects, the exported file only shows information on the
collapse objects.
If you run where-used analysis iteratively, the Where-Used Analysis trail shows all objects on
which you run where-used analysis. To export the results, select one of the following options:
Current Object. Metadata Manager exports where-used analysis results for the last object
on which you ran the report.
Trail Objects. Metadata Manager exports where-used analysis results based on all objects
in the Where-Used Analysis trail. The results show all locations where any of the objects in
the trail are used.
For more information about the Where-Used trail, see Viewing Where-Used Analysis
History on page 105.
To export results:
1. Click the Export link in the upper right corner of the report.
Export Link.
Select file type.
Note: Use the Tabular View tab to export where-used analysis results.
Exporting Results 109

2. Select the file type you want to create for the results.
3. For where-used analysis, in the Select option, select the Current Object or Trail Objects.
4. Click Export.
5. Open or save the file.
If you save the file, enter a file name and location. If you open the file, Metadata Manager
opens the file in the appropriate application.
Emailing Results
You can email data lineage and where-used analysis results in the following formats:
Link. Metadata Manager emails a link to the report in Metadata Manager. To view the
report, the email recipient clicks the link in the email, and then must log in to Metadata
Manager.
PDF document. Metadata Manager emails a PDF version of the report.
Embedded HTML. Metadata Manager embeds the report as HTML in the email.
Microsoft Excel. Metadata Manager emails a Microsoft Excel version of the report.
You must set up the mail server before you can email report results. The mail server provides
outbound email access for Metadata Manager and users. For more information about
configuring the mail server, see the Data Analyzer Administrator Guide.
When you email a report, you must enter an email address if your Metadata Manager user
account does not already have one defined for you. For more information about specifying an
email address, see the Data Analyzer Administrator Guide.
To email the results from a report:
1. Click the Email link in the upper right corner of the report.
Note: Use the Tabular View tab to email where-used analysis results.
If you did not configure a mail server, the following page appears:
Emailing Results 111

Configure the mail server. For more information about configuring a mail server, see the
Data Analyzer Administrator Guide.
2. Enter the email addresses of the email recipients, subject of the email, and the email
message text.
3. Select one of the following formats:
Link Only
PDF Document
Embedded HTML
Microsoft Excel
4. Select Send Link with Message to include a link to the report in the email.
5. Click Attachments to attach additional files to the email.
6. Click Send.
Chapter 11
Working with Metadata Manager

Reports
Overview, 114
Running Metadata Manager Reports, 116
113
Overview
Metadata Manager includes the following types of reports:
Primary reports. This is the top-level report in an analytic workflow. To access all lower-
level reports in the analytic workflow, first run this report on the Analyze tab.
Standalone reports. Unlike analytic workflow reports, you run these reports independently
of other reports.
Workflow reports. These are the lower-level reports in an analytic workflow. To access a
workflow report, first run the associated primary report and all workflow reports that
precede the given workflow report.
For more information about analytic workflows, see the Data Analyzer User Guide.
You can use these reports to perform several types of analysis on source repository metadata
stored in the Metadata Manager Warehouse. Metadata Manager prepackages reports for the
following areas:
Business intelligence
Data integration
Data modeling
Database management
Metamodel
Business Intelligence Reports

You can use the business intelligence reports to analyze business intelligence metadata, such as
report details, user activity, and the time it takes to run reports. You can use this information
to more effectively manage and develop business intelligence applications. You can also use
these reports to explore business intelligence objects, such as metrics, reports, dimensions, fact
tables, and users.
Data Modeling Reports

You can use the data modeling reports to analyze data modeling tool metadata, such
determining all tables, views, triggers, indexes, and procedures for each model.
Data Integration Reports

You can use the data integration reports to analyze data integration operations. The
information provided in the reports includes workflow activities, session failures, rejected row
information, and related statistical information that help you identify problems and take
corrective action. Using this information, you can more effectively monitor operations and
reduce downtime.
114 Chapter 11: Working with Metadata Manager Reports

Database Management Reports
Use the database management reports to explore database objects, such as constraints,
procedures, functions, synonyms, tables, views, triggers, and indexes, and the relationships
among them. You can use this information to determine the dependencies among database
objects.
Metamodel Reports
Metadata Manager administrators can use metamodel reports to explore the metamodels
defined in Metadata Manager, such as the number of objects in each class of a particular
repository and which associations and classes are not used in each repository instance. For
more information about metamodels, see the Metadata Manager Administrator Guide.
You can also use the metamodel reports to determine the types of objects each XConnect
extracts. For more information, see the Metadata Manager Administrator Guide.
Overview 115
Running Metadata Manager Reports
You can run Metadata Manager reports from the following pages:
Metadata Directory
Running Metadata Manager Reports from the Information Directory

You can run the following reports from the Information Directory:
Data Lineage
Business intelligence primary and standalone reports
Data integration primary and standalone reports
Database management primary and standalone reports
Data modeling primary and standalone reports
Metamodel primary and standalone reports
Where-Used Analysis
Note: Workflow reports do not display on the Information Directory page.
To run workflow reports in an analytic workflow, run the associated primary report on the
Analyze tab, click the Workflow tab, and then navigate through the analytic workflow until
you reach the workflow report. For more information about working with analytic workflows,
see the Data Analyzer User Guide.
Table 11-1 lists the location where you can find all reports that are accessible from the
Information Directory:
Table 11-1. Metadata Manager Report Location on the Information Directory Page
Report Type Location
Data Lineage Public Folders
Business Intelligence Public Folders > Business Intelligence

-or-
Public Folders > Business Intelligence > Operational & Administrative Reporting
Data Integration Public Folders > Data Integration

-or-
Public Folders > Data Integration > Operational & Administrative Reporting
Data Modeling Public Folders > Data Modeling
Database Management Public Folders > Database Management
Metamodel Reports Public Folders > Metamodel Reports > Metamodel Exploration
-or-
Public Folders > Metamodel Reports > Metamodel Usage
Where-Used Analysis Public Folders

When you run reports from the Information Directory, Metadata Manager may prompt you
to select the objects on which you want to run the report. The prompt limits the content of
the report by displaying the data that matches the prompted filter condition. For more
information about reports with prompts, see the Data Analyzer User Guide.
Use one of the following methods to run a report from the Information Directory:
Double-click the report in the Results task area. When you double-click the report,
Metadata Manager displays the report on the Analyze tab.
Click the View or Analyze button in the Details task area. Click the View button to
display the report on the View tab. Click the Analyze button to display the report on the
Analyze tab.
For more information about displaying reports on the View or Analyze tab, see the Data
Analyzer User Guide.
Note: To run data lineage and where-used analysis from the Details task area, click the Analyze
button.
To run a report from the Results task area:
1. On the Find tab, select Information Directory.

2. In the Folders task area, select the report folder that contains the report.
The reports contained in the selected folder appear in the Results task area.
3. Double-click the report in the Results task area.
To run a report from the Details task area:
1. On the Find tab, select Information Directory.

2. In the Folders task area, select the report folder that contains the report.
The reports contained in the selected folder appear in the Results task area.
3. Select the report in the Results task area.
4. In the Details task area, click View or Analyze to run the report.
Running Metadata Manager Reports from the Metadata Directory

You can run the following reports from the Metadata Directory:
Data Lineage
Where-Used Analysis
Other reports configured with a report link or run report button
Metadata Manager contains prepackaged run report buttons and report links for particular
types of objects. You can create new run report buttons and report links for objects that do
not have run report buttons and report links. For more information about report links and
run report buttons, see Working with Report Links on page 69.
Running Metadata Manager Reports 117

You can run reports from the Metadata Directory using one of the following methods:
Method Applicable Reports
Right-click the object in the Results task area. - Data Lineage

- Where-Used Analysis
Click the report link in the Details task area. - Data Lineage
- Other reports, if configured
Click the run report button in the Details task area. - Data Lineage
- Other reports, if configured
To locate the object on which you want to run the report, navigate through the Metadata tree
or use the search feature. For more information about using the search feature, see Running
Queries on Source Repository Metadata on page 20.
To run a report using the right-click method:

2. In the Metadata tree, select the folder containing the object on which you want to run
the report.
The object displays in the Results task area.
3. Right-click the object in the Results task area, and then select the appropriate report.
Figure 11-1 shows the report options when you right-click an object in the Results task
area:
Figure 11-1. Report Access from the Metadata Directory Page
Select the report to run the

report on the selected object.
To run a report using a report link or run report button method:

2. In the Metadata Tree task area or Results task area, select the object on which you want to
run a report.

3. Click the Report Links tab.
4. Click the report link or click the run report button.
Click the link to run the report. Click the run report
button to run the report.
Running Metadata Manager Reports 119

Index
A C
access permissions cardinality
adding an object 35 viewing on the Find tab 58
viewing an object on the Metadata tree 16 common properties
viewing object details 24 description 30
accessing
data lineage 80
object links 65 D
report links 71
data lineage
where-used analysis 100
accessing 80
adding
configuring 95
object associations 60
data structures 83
object links 66
description 80
object properties 49
Detailer View task area 87
report links 73
downstream filter 93
repository objects 35
emailing results 111
associations
exporting results 109
viewing cardinality details 58
fields 83
viewing effective dates on the Find tab 58
filtering results 93
Associations tab
Lineage View task area 85
in Details task area 56
object handling 83
running 91
B tasks 82
business intelligence reports transformations 83
description 114 upstream filter 93
data modeling reports
description 114
121
data structures
description 83
G
database management reports General Properties tab
description 115 in Details task area 45
delete permissions
adding an object 35
deleted objects I
working with 17 Informatica Metadata Manager
deleting overview 2
object associations 62 input field
object links 68 definition 87
report links 78
Detailer View task area
L
for data lineage 87 lineage diagram
Details task area collapsed 86
Associations tab 56 Lineage View task area
General Properties tab 45 for data lineage 85
Object Links tab 64 login
Object Properties tab 46 Metadata Manager 12
Report Links tab 70
displaying
default properties 26 M
downstream filter metadata
for data lineage 93 searching for 20
Metadata Browser
description 3
E Metadata Directory
editing Metadata Browser 3
object properties 52 viewing metadata details 24
report links 77 Metadata Manager
repository objects 38 logging in 12
Effective From date Metadata Manager Warehouse
adding repository objects 35 date when object added 46
Effective To date date when object updated 46
adding repository objects 35 Metadata tree
emailing description 15
object details 31 metamodel reports
exporting description 115
results 109
O
object associations
F adding 60
fields deleting 62
description 83 viewing 57
filters
for report links 70
122 Index
object handling
parent containers 83
R
parent objects 83 read permissions
public synonyms 83 adding an object 35
reusable transformations 84 report links
source repositories 83 accessing 71
source repository connections 83 adding 73
stored procedures 83 deleting 78
object links editing 77
accessing 65 filter 70
adding 66 Report Links tab
deleting 68 in Details task area 70
Object Links tab reports
in Details task area 64 running from Report Links tab 71
object properties running with run report button 24
adding 49 viewing 116
deleting 53 repositories
editing 52 See source repository
Object Properties tab repository objects
in Details task area 46 See objects
object versions Results task area
working with 17 configuring display 26
objects default property display 26
adding 35 rules
deleting 40 for configuring properties 26
displaying properties for 26 run report button
editing 38 description 70
emailing details 31 running reports 24
exporting 41 running
permissions when adding an object 35 standalone reports 114
searching for 20 workflow reports 114
viewing 24
viewing object versions 24
output field S
definition 87 searching
for repository metadata 20
source repositories
P date when object added 46
participating field date when object last updated 46
definition 87 standalone reports
primary reports running 114
description 114 subject
prompts definition 100
See also Data Analyzer documentation
viewing Metadata Manager metadata analysis reports
117 T
properties tasks
default display 26 description 82
displaying 27
displaying for objects 26
Index 123
transformations
description 83
reusable 84
U
upstream filter
for data lineage 93
V
viewing
metadata 24
object associations 57
objects 24
reports 116
versions of repository objects 24
W
where-used analysis
accessing 100
description 100
emailing results 111
exporting results 109
formatting 102
running 106
subject 100
workflow reports
description 114
write permissions
adding an object 35
124 Index
NOTICES
This Informatica product (the Software) includes certain drivers (the DataDirect Drivers) from DataDirect Technologies, an operating company of Progress
Software Corporation (DataDirect) which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS,
WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF
ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY,
MISREPRESENTATION AND OTHER TORTS.

Metadata Manager Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Metadata Manager Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Metadata Manager User Guide

Copyright (c) 20032008 Informatica Corporation.

BEA and WebLogic are registered trademarks of BEA Systems, Inc.

Chapter 1: Metadata Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . 1

Table of Contents iii

Chapter 3: Working with Metadata Objects . . . . . . . . . . . . . . . . . . . . 33

Chapter 4: Working with Object Properties . . . . . . . . . . . . . . . . . . . . 43

Chapter 5: Working with Object Associations . . . . . . . . . . . . . . . . . . 55

Chapter 7: Working with Report Links . . . . . . . . . . . . . . . . . . . . . . . . 69

Chapter 8: Working with Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 9: Working with Where-Used Analysis . . . . . . . . . . . . . . . . . 99

Chapter 10: Sharing Data Lineage and Where-Used Analysis

Chapter 11: Working with Metadata Manager Reports . . . . . . . . . . 113

List of Figures vii

If you see It means

italicized text The word or set of words are especially emphasized.

boldfaced text Emphasized subjects.

Note: The following paragraph provides additional facts.

Tip: The following paragraph provides suggested uses.

monospaced text This is a code example.

Visiting Informatica Customer Portal

Visiting the Informatica Web Site

Visiting the Informatica Developer Network

Visiting the Informatica Knowledge Base

Obtaining Technical Support

Informatica Corporation Informatica Software Ltd. Informatica Business Solutions

Toll Free Toll Free Toll Free

Standard Rate Standard Rate Standard Rate

Metadata Manager Overview

This chapter includes the following topics:

2 Chapter 1: Metadata Manager Overview

4 Chapter 1: Metadata Manager Overview

6 Chapter 1: Metadata Manager Overview

Metadata Manager Interface 7

Metadata Directory on the Find Tab

Figure 1-1. Metadata Directory Page

Shows Metadata Directory

Results Task Area

Metadata Tree Task Area Details Task Area

The Metadata Directory page consists of the following areas:

8 Chapter 1: Metadata Manager Overview

Information Directory on the Find Tab

Figure 1-2. Information Directory Page

Folders Task Area Details Task Area

The Metadata Directory page consists of the following areas:

Metadata Manager Interface 9

10 Chapter 1: Metadata Manager Overview

Figure 1-3. Administration Tab

Manage Account Tab

Metadata Manager Interface 11

To log in to Metadata Manager:

1. Launch a Microsoft Internet Explorer web browser.

12 Chapter 1: Metadata Manager Overview

Accessing Source Repository

14 Chapter 2: Accessing Source Repository Metadata

Metadata Tree Task Area

Browsing Source Repository Metadata 15

Figure 2-1. Source Repository Metadata in the Metadata Tree

Metadata Manager Group

Metadata Manager Subgroup

Source Repository Folder

Source Repository Object

Results Task Area

16 Chapter 2: Accessing Source Repository Metadata