Application Service Guide > Metadata Manager Service > Metadata Manager Service Properties
  

Metadata Manager Service Properties

You can configure general, Metadata Manager Service, database, configuration, connection pool, advanced, and custom properties for the Metadata Manager Service.
After you create a Metadata Manager Service, you can configure it. After you configure Metadata Manager Service properties, you must disable and enable the Metadata Manager Service for the changes to take effect.
Use the Administrator tool to configure the following Metadata Manager Service properties:
If you update any of the properties, restart the Metadata Manager Service for the modifications to take effect.

General Properties

To edit the general properties, select the Metadata Manager Service in the Navigator, select the Properties view, and then click Edit in the General Properties section.
The following table describes the general properties for the service:
Property
Description
Name
Name of the service. The name is not case sensitive and must be unique within the domain. It cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special characters:
` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
You cannot change the name of the service after you create it.
Description
Description of the service. The description cannot exceed 765 characters.
License
License object that allows use of the service.
Node
Node on which the service runs. To assign the Metadata Manager Service to a different node, you must first disable the service.

Assigning the Metadata Manager Service to a Different Node

    1. Disable the Metadata Manager Service.
    2. Click Edit in the General Properties section.
    3. Select another node for the Node property, and then click OK.
    4. Click Edit in the Metadata Manager Service Properties section.
    5. Change the Metadata Manager File Location property to a location that is accessible from the new node, and then click OK.
    6. Copy the contents of the Metadata Manager file location directory on the original node to the location on the new node.
    7. If the Metadata Manager Service is running in HTTPS security mode, click Edit in the Configuration Properties section. Change the Keystore File location to a location that is accessible from the new node, and then click OK.
    8. Enable the Metadata Manager Service.

Metadata Manager Service Properties

To edit the Metadata Manager Service properties, select the Metadata Manager Service in the Navigator, select the Properties view, and then click Edit in the Metadata Manager Service Properties section.
The following table describes the Metadata Manager Service properties:
Property
Description
Port Number
Port number that the Metadata Manager application runs on. Default is 10250.
Agent Port
Port number for the Metadata Manager Agent when the Metadata Manager Service runs on Windows. The agent uses this port to communicate with metadata source repositories. Default is 10251.
If the Metadata Manager Service runs on UNIX, you must install the Metadata Manager Agent on a separate Windows machine.
Metadata Manager File Location
Location of the files used by the Metadata Manager application. Files include the following file types:
  • - Index files. Index files created by Metadata Manager required to search the Metadata Manager warehouse.
  • - Log files. Log files generated by Metadata Manager when you load resources.
  • - Parameter files. Files generated by Metadata Manager and used by PowerCenter workflows.
  • - Repository backup files. Metadata Manager repository backup files that are generated by the mmRepoCmd command line program.
By default, Metadata Manager stores the files in the following directory:
<Informatica services installation directory>\services\MetadataManagerService\mm_files\<Metadata Manager Service name>
Metadata Manager Lineage Graph Location
Location that Metadata Manager uses to store graph database files for data lineage.
By default, Metadata Manager stores the graph database files in the following directory:
<Informatica services installation directory>\services\MetadataManagerService\mm_files\<Metadata Manager Service name>

Metadata Manager File Location Rules and Guidelines

Use the following rules and guidelines when you configure the Metadata Manager file location:

Metadata Manager Lineage Graph Location Rules and Guidelines

Use the following rules and guidelines when you configure the Metadata Manager lineage graph location:

Database Properties

You can edit the Metadata Manager repository database properties. Select the Metadata Manager Service in the Navigator, select the Properties view, and then click Edit in the Database Properties section.
The following table describes the database properties for a Metadata Manager repository database:
Property
Description
Database Type
Type of database for the Metadata Manager repository. To apply changes, restart the Metadata Manager Service.
Code Page
Metadata Manager repository code page. The Metadata Manager Service and Metadata Manager use the character set encoded in the repository code page when writing data to the Metadata Manager repository. To apply changes, restart the Metadata Manager Service.
Note: The Metadata Manager repository code page, the code page on the machine where the associated PowerCenter Integration Service runs, and the code page for any database management and PowerCenter resources that you load into the Metadata Manager warehouse must be the same.
Connect String
Native connect string to the Metadata Manager repository database. The Metadata Manager Service uses the connection string to create a target connection to the Metadata Manager repository in the PowerCenter repository.
To apply changes, restart the Metadata Manager Service.
Database User
User account for the Metadata Manager repository database. Set up this account using the appropriate database client tools. To apply changes, restart the Metadata Manager Service.
Database Password
Password for the Metadata Manager repository database user. Must be in 7-bit ASCII. To apply changes, restart the Metadata Manager Service.
Tablespace Name
Tablespace name for the Metadata Manager repository on IBM DB2. When you specify the tablespace name, the Metadata Manager Service creates all repository tables in the same tablespace. You cannot use spaces in the tablespace name. To apply changes, restart the Metadata Manager Service.
To improve repository performance on IBM DB2 EEE repositories, specify a tablespace name with one node.
Database Hostname
Host name for the Metadata Manager repository database. To apply changes, restart the Metadata Manager Service.
Database Port
Port number for the Metadata Manager repository database. To apply changes, restart the Metadata Manager Service.
SID/Service Name
Indicates whether the Database Name property contains an Oracle full service name or an SID.
Database Name
Full service name or SID for Oracle databases. Service name for IBM DB2 databases. Database name for Microsoft SQL Server databases. To apply changes, restart the Metadata Manager Service.
Additional JDBC Parameters
Additional JDBC parameters that you want to append to the database connection URL. Enter the parameters as name=value pairs separated by semicolon characters (;). For example:
param1=value1;param2=value2
You can use this property to specify the following information:
  • - Backup server location. If you use a database server that is highly available such as Oracle RAC, enter the location of a backup server.
  • - Oracle Advanced Security Option (ASO) parameters. If the Metadata Manager repository database is an Oracle database that uses ASO, enter the following additional parameters:
    • EncryptionLevel=[encryption level];EncryptionTypes=[encryption types];DataIntegrityLevel=[data integrity level];DataIntegrityTypes=[data integrity types]
    The parameter values must match the values in the sqlnet.ora file on the machine where the Metadata Manager Service runs.
  • - Authentication information for Microsoft SQL Server.
    • Note: The Metadata Manager Service does not support the alternateID option for DB2.
    To authenticate the user credentials using Windows authentication and establish a trusted connection to a Microsoft SQL Server repository, enter the following text: AuthenticationMethod=ntlm;LoadLibraryPath=[directory containing DDJDBCx64Auth04.dll].
    jdbc:informatica:sqlserver://[host]:[port];DatabaseName=[DB name];AuthenticationMethod=ntlm;LoadLibraryPath=[directory containing DDJDBCx64Auth04.dll]
    When you use a trusted connection to connect to a Microsoft SQL Server database, the Metadata Manager Service connects to the repository with the credentials of the user logged in to the machine on which the service is running.
    To start the Metadata Manager Service as a Windows service using a trusted connection, configure the Windows service properties to log on using a trusted user account.
Secure JDBC Parameters
Secure JDBC parameters that you want to append to the database connection URL. Use this property to specify secure connection parameters such as passwords. The Administrator tool does not display secure parameters or parameter values in the Metadata Manager Service properties. Enter the parameters as name=value pairs separated by semicolon characters (;). For example:
param1=value1;param2=value2
If secure communication is enabled for the Metadata Manager repository database, enter the secure JDBC parameters in this property.
To update the secure JDBC parameters, click Modify Secure JDBC Parameters and enter the new values.

JDBC Parameters for Secure Databases

If secure communication is enabled for the Metadata Manager repository database, you must configure additional JDBC parameters in the Secure JDBC Parameters property.
Enter the following parameters in the Secure JDBC Parameters property:
EncryptionMethod=SSL;TrustStore=<truststore location>;TrustStorePassword=<password>;HostNameInCertificate=<host name>;ValidateServerCertificate=<true|false>;KeyStore=<keystore location>;keyStorePassword=<password>
Configure the parameters as follows:
EncryptionMethod
Encryption method for data transfer between Metadata Manager and the database server. Must be set to SSL.
TrustStore
Path and file name of the truststore file that contains the security certificate of the database server.
TrustStorePassword
Password used to access the truststore file.
HostNameInCertificate
Host name of the machine that hosts the secure database. If you specify a host name, the Metadata Manager Service validates the host name included in the connection string against the host name in the security certificate.
ValidateServerCertificate
Indicates whether the Metadata Manager Service validates the certificate that the database server presents. If you set this parameter to true, the Metadata Manager Service validates the certificate. If you specify the HostNameInCertificate parameter, the Metadata Manager Service also validates the host name in the certificate.
If you set this parameter to false, the Metadata Manager Service does not validate the certificate that the database server presents. The Metadata Manager Service ignores any truststore information that you specify.
KeyStore
Path and file name of the keystore file that contains the security certificates that the Metadata Manager Service presents to the database server.
KeyStorePassword
Password used to access the keystore file.

Configuration Properties

To edit the configuration properties, select the Metadata Manager Service in the Navigator, select the Properties view, and then click Edit in the Configuration Properties section.
The following table describes the configuration properties for a Metadata Manager Service:
Property
Description
URLScheme
Indicates the security protocol that you configure for the Metadata Manager application: HTTP or HTTPS.
Keystore File
Keystore file that contains the keys and certificates required if you configure a secure connection for the Metadata Manager web application. You must use the same security protocol for the Metadata Manager Agent if you install it on another machine.
Keystore Password
Password for the keystore file.
MaxConcurrentRequests
Maximum number of request processing threads available, which determines the maximum number of client requests that Metadata Manager can handle simultaneously. Default is 100.
MaxQueueLength
Maximum queue length for incoming connection requests when all possible request processing threads are in use by the Metadata Manager application. Metadata Manager refuses client requests when the queue is full. Default is 500.
You can use the MaxConcurrentRequests property to set the number of clients that can connect to Metadata Manager. You can use the MaxQueueLength property to set the number of client requests Metadata Manager can process at one time.
You can change the parameter values based on the number of clients that you expect to connect to Metadata Manager. For example, you can use smaller values in a test environment. In a production environment, you can increase the values. If you increase the values, more clients can connect to Metadata Manager, but the connections might use more system resources.

Connection Pool Properties

To edit the connection pool properties, select the Metadata Manager Service in the Navigator, select the Properties view, and then click Edit in the Connection Pool Properties section.
The following table describes the connection pool properties for a Metadata Manager Service:
Property
Description
Maximum Active Connections
Number of active connections to the Metadata Manager repository database available. The Metadata Manager application maintains a connection pool for connections to the repository database.
Increase the number of maximum active connections when you increase the number of maximum concurrent resource loads. For example, if you set the Max Concurrent Resource Load property to 10, Informatica recommends that you also set this property to 50 or more.
Default is 20.
Maximum Wait Time
Amount of time in seconds that Metadata Manager holds database connection requests in the connection pool. If Metadata Manager cannot process the connection request to the repository within the wait time, the connection fails.
Default is 180.

Advanced Properties

To edit the advanced properties, select the Metadata Manager Service in the Navigator, select the Properties view, and then click Edit in the Advanced Properties section.
The following table describes the advanced properties for a Metadata Manager Service:
Property
Description
Max Heap Size
Amount of RAM in megabytes allocated to the Java Virtual Manager (JVM) that runs Metadata Manager. Use this property to increase the performance of Metadata Manager.
For example, you can use this value to increase the performance of Metadata Manager during indexing.
Note: If you create Cloudera Navigator resources, set this property to at least 4096 MB (4 GB).
Default is 4096.
Maximum Catalog Child Objects
Number of child objects that appear in the Metadata Manager metadata catalog for any parent object. The child objects can include folders, logical groups, and metadata objects. Use this option to limit the number of child objects that appear in the metadata catalog for any parent object.
Default is 100.
Error Severity Level
Level of error messages written to the Metadata Manager Service log. Specify one of the following message levels:
  • - Fatal
  • - Error
  • - Warning
  • - Info
  • - Trace
  • - Debug
When you specify a severity level, the log includes all errors at that level and above. For example, if the severity level is Warning, the log includes fatal, error, and warning messages. Use Trace or Debug if Informatica Global Customer Support instructs you to use that logging level for troubleshooting purposes.
Default is Error.
Max Concurrent Resource Load
Maximum number of resources that Metadata Manager can load simultaneously. Maximum is 10.
Metadata Manager adds resource loads to the load queue in the order that you request the loads. If you simultaneously load more than the maximum, Metadata Manager adds the resource loads to the load queue in a random order. For example, you set the property to 5 and schedule eight resource loads to run at the same time. Metadata Manager adds the eight loads to the load queue in a random order. Metadata Manager simultaneously processes the first five resource loads in the queue. The last three resource loads wait in the load queue.
If a resource load succeeds, fails and cannot be resumed, or fails during the path building task and can be resumed, Metadata Manager removes the resource load from the queue. Metadata Manager starts processing the next load waiting in the queue.
If a resource load fails when the PowerCenter Integration Service runs the workflows and the workflows can be resumed, the resource load is resumable. Metadata Manager keeps the resumable load in the load queue until the timeout interval is exceeded or until you resume the failed load. Metadata Manager includes a resumable load due to a failure during workflow processing in the concurrent load count.
Default is 3.
Note: If you increase the number of maximum concurrent resource loads, increase the number of maximum active connections to the Metadata Manager repository database. For example, if you set this property to 10, Informatica recommends that you also set the Maximum Active Connections property to 50 or more.
Timeout Interval
Amount of time in minutes that Metadata Manager holds a resumable resource load in the load queue. You can resume a resource load within the timeout period if the load fails when PowerCenter runs the workflows and the workflows can be resumed. If you do not resume a failed load within the timeout period, Metadata Manager removes the resource from the load queue.
Default is 30.
Note: If a resource load fails during the path building task, you can resume the failed load at any time.

Custom Properties for the Metadata Manager Service

Configure custom properties that are unique to specific environments.
You might need to apply custom properties in special cases. When you define a custom property, enter the property name and an initial value. Define custom properties only at the request of Informatica Global Customer Support.