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.5.2
- 10.5.5
- 10.5.3
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0

Back Next

Linking for Cloudera Entities

Metadata Manager can display data lineage links between entities in a Cloudera Navigator resource and data objects in other resources. To link Hive tables with data objects in other packaged resources or in universal resources, use connection assignments. To link HDFS files with data objects in other packaged resources, in custom resources, or in universal resources, use a linking rules file.

Metadata Manager links Hive tables in a Cloudera Navigator resource with data objects in another resource when you configure connection assignments between the metadata sources. For example, a PowerCenter session loads data to a Hive target table that exists in your Cloudera distribution. Before you can view data lineage between the PowerCenter target and the Hive table, you must configure a connection assignment between the PowerCenter repository and the Cloudera distribution.

Metadata Manager does not use connection assignments to link HDFS files in a Cloudera Navigator resource with data objects in other resources. To link HDFS files with data objects in other resources, use a linking rules file.

For example, your Cloudera distribution contains the HDFS file big-customer.csv. You use the data in this file to populate the CUST flat file data object in the Developer tool. The CUST flat file data object is used as a source in an HDFS mapping.

Create a linking rules file to link the big-customer.csv HDFS file to the CUST flat file data object. Add a link condition that creates links from the HDFS file to the columns in the output group of the flat file data object.

In Metadata Manager, the CUST flat file data object belongs to the HDFS Data Object class. The output group belongs to the Data Object Read class. The columns in the output group belong to the Attribute class.

Use the following file to create the links:

<?xml version="1.0" encoding="UTF-8"?>

<ruleSet name="Link HDFS files to Informatica Platform FF Data Objects">

  <sourceResource name="Cloudera01"/>
  <targetResource name="InfaPlatform01"/>

  <rule name="Link HDFS big-customer.csv to Informatica Platform CUST FF columns" direction="SourceToTarget">
    <sourceFilter >
      <element class="HDFS File"/>
    </sourceFilter>

    <targetFilter>
      <!-- We must link to features. If we link to structures only, Metadata Manager will not find upstream links to the HDFS file. -->
      <element class="HDFS Data Object">
        <element class="Data Object Read">
          <element class="Attribute"/>
        </element>
      </element>
    </targetFilter>

    <link condition="source.Name = 'big-customer.csv' AND target.parent.Name = 'output' AND target.parent.parent.Name = 'CUST'"/>

  </rule>

</ruleSet>

In this example, the

target.parent.Name = 'output'

clause in the link condition identifies the output group. The

target.parent.parent.Name = 'CUST'

clause identifies the flat file data object.

To upload the linking rules file, edit the Cloudera Navigator resource. After you upload the linking rules file and reload the resource, Metadata Manager creates the lineage links. Metadata Manager creates a link from the big-customer.csv HDFS file to each column in the output group of the CUST flat file data object.

For more information about rule-based links, see the

Metadata Manager Custom Metadata Integration Guide

Reference

Configure Connection Assignments

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal