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.0
- 10.5.5
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1

Back Next

JDBC Configuration Properties

Update the configuration properties when you create or edit a JDBC resource.

The following table describes the JDBC configuration properties:

Property	Description
Agent URL	Host name and port number of the Metadata Manager Agent. You can use the Metadata Manager Agent installed on any machine. For example: http://localhost:19980
Source system version	Name and version of the metadata source.
Driver location	Path to the JDBC driver JAR file. Separate multiple values with a semicolon (;). If required, copy the JAR file to the Windows machine on which the Metadata Manager Agent is installed. The driver path is relative to the Metadata Manager Agent location. If you specify the file name without specifying the path, verify that the JAR file is in the classpath of the machine that runs the Metadata Manager Agent. For example, the data driver for IBM DB2/iSeries is in the following directory: <Informatica installation directory>\services\MetadataManagerService\utilities\mmcmd\lib
Driver class	Name of the Java class that implements the JDBC driver interface. Specify the full name including the package name. For example: com.informatica.jdbc.db2.DB2Driver
URL	JDBC URL to connect to the database. Metadata Manager uses this URL to verify connection information to the database. The value that you specify depends on the database and the driver that you use. For example: jdbc:informatica:db2://host_name:port;LocationName=<location name>;PackageCollection=<package collection> The default port number of the IBM DB2/iSeries server is 446.
User	Name of the user account used to connect to the database.
Password	Password for the user account used to connect to the database.
Catalog	Catalog name that Metadata Manager uses to filter metadata. The catalog is a container for schemas and global objects. The catalog is not relevant for all relational databases. For example, IBM DB2/iSeries does not use a catalog.
Schema	Schema name that Metadata Manager uses to filter metadata. Separate multiple values with a semicolon (;). If you do not specify a schema name, Metadata Manager loads the first schema in the list of available schemas sorted in ascending alphabetic order.
Case sensitivity	Case sensitivity setting for the metadata source database. Select one of the following options: Auto. The Metadata Manager Agent uses the JDBC driver that you specify in the Driver path property to determine whether the database is case sensitive. If the driver cannot check case sensitivity, the Metadata Manager Agent assumes that the database is not case sensitive. Case sensitive Case insensitive Default is Auto.
View definition extracting SQL	Database-specific SQL query to extract the view definitions. The query must return results with a single column that contains the view definition text. If you do not enter a query, data lineage between views and their source tables is not built. For example, you can enter the following query for IBM DB2/iSeries: SELECT TABLE_SCHEMA, TABLE_NAME, VIEW_DEFINITION FROM QSYS2.SYSVIEWS WHERE TABLE_SCHEMA IN (?)
Synonyms lineage SQL	Database-specific SQL query to extract the synonym information for tables and views. This property is reserved for future use.
Optional scope	Optional data structures to import such as keys, indexes, and stored procedures. To import optional data structures, click Select and choose the data structures to import. You must specify the connection information for the JDBC source before you can select the optional data structures to import.

Rename Saved Search

Table of Contents

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

JDBC Configuration Properties

JDBC Configuration Properties