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
- 10.5.6
- 10.5.5
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0

Back Next

Data Integration Service Connection Properties

If you create a resource from an application that is deployed to a Data Integration Service, you must provide connection information for the Data Integration Service.

The following table describes the connection properties:

Property	Description
Source system version	Name and version of the metadata source. Select one of the following options based on the application version: Informatica Platform 10.4.1 (Repository) Informatica Platform 10.4.0 (Repository) Informatica Platform 10.2.2 HotFix1 (Repository) Informatica Platform 10.2.2 (Repository) Informatica Platform 10.2.1 (Repository) Informatica Platform 10.2.0 HotFix1 (Repository) Informatica Platform 10.2.0 HotFix2 (Repository) Informatica Platform 10.2 (Repository) Informatica Platform 10.1.1 HotFix 2 (Repository) Informatica Platform 10.1.1 HotFix 1 (Repository) Informatica Platform 10.1.1 (Repository) Informatica Platform 10.1 (Repository) Informatica Platform 10.0 (Repository) Informatica Platform 9.5.1 - 9.6.x (Repository)
Host	Name of the gateway node in the Informatica domain.
Port	Port number for the gateway node.
Security domain	Security domain for the Administrator tool user. If the domain uses LDAP authentication or Kerberos authentication, enter the security domain name. Otherwise, enter Native .
User name	Name of the Administrator tool user. The user must have the Manage Applications privilege on the Data Integration Service.
Password	Password for the Administrator tool user.
DIS service name	Name of the Data Integration Service where the application is deployed.
10.4.1 Command Line Utilities Directory	File path to version 10.4.1 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.4.1 (Repository) . The value must be an absolute path that the 10.4.1 Metadata Manager Service can access, for example, C:\Informatica\1041_CLU .
10.4.0 Command Line Utilities Directory	File path to version 10.4.0 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.4.0 (Repository) . The value must be an absolute path that the 10.4.0 Metadata Manager Service can access, for example, C:\Informatica\1040_CLU .
10.2.2 HotFix1 Command Line Utilities Directory	File path to version 10.2.2 HotFix1 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.2.2 HotFix1 (Repository) . The value must be an absolute path that the 10.2.2 HotFix1 Metadata Manager Service can access, for example, C:\Informatica\1022HF1_CLU .
10.2.2 Command Line Utilities Directory	File path to version 10.2.2 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.2.2 (Repository) . The value must be an absolute path that the 10.2.2 Metadata Manager Service can access, for example, C:\Informatica\1022_CLU .
10.2.1 Command Line Utilities Directory	File path to version 10.2.1 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.2.1 (Repository) . The value must be an absolute path that the 10.2.1 Metadata Manager Service can access, for example, C:\Informatica\1021_CLU .
10.2.0 HotFix 2 Command Line Utilities Directory	File path to version 10.2.0 HotFix 2 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.2.0 HotFix 2 (Repository) . The value must be an absolute path that the 10.2.0 HotFix 2 Metadata Manager Service can access, for example, C:\Informatica\1020HF2_CLU .
10.2.0 HotFix1 Command Line Utilities Directory	File path to version 10.2.0 HotFix 1 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.2.0 HotFix 1 (Repository) . The value must be an absolute path that the 10.2.0 HotFix 1 Metadata Manager Service can access, for example, C:\Informatica\1020HF1_CLU .
10.2.0 Command Line Utilities Directory	File path to version 10.2.0 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.2 (Repository) . The value must be an absolute path that the 10.2.0 Metadata Manager Service can access, for example, C:\Informatica\102_CLU .
10.1.1 HotFix2 Command Line Utilities Directory	File path to version10.1.1 HotFix 2 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.1.1 HotFix 2 (Repository) . The value must be an absolute path that the 10.1.1 HotFix 2 Metadata Manager Service can access, for example, C:\Informatica\1011HF2_CLU .
10.1.1 HotFix1 Command Line Utilities Directory	File path to version10.1.1 HotFix 1 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.1.1 HotFix 1 (Repository) . The value must be an absolute path that the 10.1.1 HotFix 1 Metadata Manager Service can access, for example, C:\Informatica\1011HF1_CLU .
10.1.1 Command Line Utilities Directory	File path to version 10.1.1 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.1.1 (Repository) . The value must be an absolute path that the 10.1.1 Metadata Manager Service can access, for example, C:\Informatica\1011_CLU .
10.1 Command Line Utilities Directory	File path to version 10.1 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.1 (Repository) . The value must be an absolute path that the 10.1 Metadata Manager Service can access, for example, C:\Informatica\101_CLU .
10.0 Command Line Utilities Directory	File path to version 10.0 Informatica Command Line Utilities installation directory. This property appears when you select source system version Informatica Platform 10.0 (Repository) . The value must be an absolute path that the 10.0 Metadata Manager Service can access, for example, C:\Informatica\100_CLU .
Auto assign connections	Metadata Manager configures connection assignments to relational database resource types during the resource load. If you disable this option, configure connection assignments in the resource properties after you create the resource.

To extract metadata from Informatica version 10.2.1 ServicePack1, select

Informatica Platform 10.2.1 (Repository)

source system version option and enter the file path for version 10.2.1 ServicePack1 Informatica Command Line Utilities installation directory.

Rename Saved Search

Table of Contents

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

Data Integration Service Connection Properties

Data Integration Service Connection Properties