Preface
Using Metadata Manager
- Using Metadata Manager Overview
  - Resource Types
- Metadata Manager Architecture
- Metadata Integration Process
- Working with Metadata Manager
- Metadata Manager Interface
  - Load Tab
  - Permissions Tab
Configuring Metadata Manager
- Configuring Metadata Manager Overview
- Step 1. Create and Configure the Metadata Manager Service
- Step 2. Install the Metadata Manager Agent
Application Resources
- SAP R/3 Resource Overview
- Configuring SAP R/3
- Creating an SAP R/3 Resource
  - SAP R/3 Configuration Properties
- Configuring the Component Inclusion List
- Reference
Business Glossary Resources
- Business Glossary Resources Overview
- Application Services Verification
- Creating a Business Glossary Resource
  - Business Glossary Connection Properties
- Business Glossary Objects Extracted
- Business Glossary Objects Not Extracted
Business Intelligence Resources
- Business Objects
- Cognos
- Microsoft Analysis and Reporting Services
- Microstrategy
- Oracle Business Intelligence Enterprise Edition
- Tableau
- Incremental Metadata Load
- Adding or Removing Metadata Files for a Resource
Custom Resources
- Configuring Custom Metadata Sources
- Creating a Custom Resource
- Configuring the Template Name
- Adding or Removing Metadata Files for a Resource
Data Integration Resources
- Informatica Platform Resources
- Microsoft SQL Server Integration Services Resources
- PowerCenter Resources
Data Modeling Resources
- Embarcadero ERStudio
- ERwin
- SAP PowerDesigner
- Adding or Removing Metadata Files for a Resource
- Reference for Data Modeling Resources
Database Management Resources
- Cloudera Navigator
- IBM DB2 for LUW
- IBM Db2 for z/OS
- IBM Informix
- JDBC
- Microsoft SQL Server
- Netezza
- Oracle
- Sybase ASE
- Teradata
- Configuring the Schema Inclusion List
- Data Lineage for Database Management Resources
  - Tables in Join Statements
  - SQL Inline Views
Universal Resources
- Universal Resources Overview
- Available Metadata Sources
- XConnect Creation
- Resource Creation
  - Step 1. Configure the Metadata Source
  - Step 2. Create the Resource
    - Metadata Extraction from a Source File
Managing Resources
- Managing Resources Overview
- Configure Connection Assignments
- Upload Rule Sets
  - Linking Rules Files
  - Uploading a Rule Set
- Purging Metadata
- Refreshing the Resources Panel
- Updating the Search Index
- Customizing the List of Words to Ignore in Searches
Loading and Monitoring Resources
- Loading and Monitoring Resources Overview
- Loading Resources
- Linking Objects Across Resources
- Monitoring Resources
- Logs and Log Files
- Troubleshooting Resource Loads
- Scheduling Resource Loads
Managing Permissions
- Managing Permissions Overview
- Configuring Permissions for Users and Groups
- Configuring Permissions on the Metadata Catalog
Resource Migration
- Resource Migration Overview
- Resource Migration Steps
- Step 1. Copy the Plug-in for a Universal XConnect
- Step 2. Migrate the Model
  - Exporting a Packaged or Universal Model
  - Importing a Packaged or Universal Model
- Step 3. Migrate the Resource Configuration
  - Exporting a Resource Configuration
  - Importing a Resource Configuration
- Step 4. Load the Resource
- Step 5. Migrate Resource Metadata
  - Exporting Resource Metadata
  - Importing Resource Metadata
Repository Migration
- Repository Migration Overview
- Migrating the Repository when Domain Names and Encryption Keys are the Same
- Migrating the Repository when Domain Names or Encryption Keys Differ
Appendix A: Metadata Manager Login
- Metadata Manager Login Overview
- Cookies
- Logging in to Metadata Manager
- Changing a Password
Appendix B: Metadata Manager Properties Files
- imm.properties
  - Metadata Manager Application Properties
  - Data Lineage Properties
- searchpriorities.xml
  - Search Result Configuration
  - Sample searchpriorities.xml File
Appendix C: Resource Configuration Files
- Resource Configuration Files Overview
- Resource Configuration File Format
- Passwords in Resource Configuration Files
- Secure JDBC Parameters in Resource Configuration Files
- Sample Resource Configuration File
Appendix D: Glossary
- Glossary of Terms

Metadata Manager Administrator Guide

10.4.1
- 10.5.5
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.0

Back Next

Data Lineage Properties

The following table describes the data lineage properties in imm.properties:

Property	Description
Lineage.Debug.ShowPerformanceDebugMessages	Writes the data lineage performance information to the mm.log file. If set to true, writes the following information to the log file: Time taken to display the data lineage diagram. Number of features and structures with connections in the diagram. Number of objects displayed in the diagram. Metadata Manager prefixes the name of the object for which you ran the data lineage analysis to each performance message. Default is false.
Lineage.Flow.DefaultDownstreamGenerationLimit	Number of generations to display downstream from the source object in a data lineage diagram.
Lineage.Flow.DefaultNumberOfGenerationsToContinueLineage	Number of generations that appear when you use the arrow buttons to navigate the data lineage diagram.
Lineage.Flow.DefaultUpstreamGenerationLimit	Number of generations to display upstream from the source object in a data lineage diagram.
Lineage.PreCompute.ElementsInSingleTransaction	Maximum number of graph elements, including edges and vertices, that the Metadata Manager Service can process in a single transaction during lineage graph creation. When the number of elements reaches this limit, the Metadata Manager Service pages some information to disk instead of storing it in physical memory. Increase this value to reduce paging for large, complex data lineage diagrams. If you increase this value, verify that the machine that stores the graph database files has enough physical memory to support the increased transaction size. Default is 50,000.
Lineage.PreCompute.FetchBlockSize	Number of records that the Metadata Manager Service processes in one block when it retrieves data lineage linking information from the Metadata Manager warehouse to populate the graph database. If you increase this value, you might also need to increase the value of the Lineage.PreCompute.ElementsInSingleTransaction property because each block of records will contain additional graph elements. Default is 5000.

Rename Saved Search

Table of Contents

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

Data Lineage Properties

Data Lineage Properties