Metadata Manager
- Metadata Manager 10.5.5
- All Products
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:
|
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:
|
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:
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:
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:
|
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.
|