Application Service Guide > Metadata Manager Service > Creating a Metadata Manager Service
  

Creating a Metadata Manager Service

Use the Administrator tool to create the Metadata Manager Service. After you create the Metadata Manager Service, create the Metadata Manager repository contents and PowerCenter repository contents to enable the service.
    1. In the Administrator tool, click the Manage tab.
    2. Click the Services and Nodes view.
    3. Click Actions > New Metadata Manager Service.
    The New Metadata Manager Service dialog box appears.
    4. Enter values for the Metadata Manager Service general properties, and click Next.
    5. Enter values for the Metadata Manager Service database properties, and click Next.
    6. Enter values for the Metadata Manager Service security properties, and click Finish.

Metadata Manager Service Properties

The following table describes the properties that you configure for the Metadata Manager Service:
Property
Description
Name
Name of the Metadata Manager 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:
` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
Description
The description cannot exceed 765 characters.
Location
Domain and folder where the service is created. Click Browse to choose a different folder. You can move the Metadata Manager Service after you create it.
License
License object that allows use of the service.
Node
Node in the Informatica domain that the Metadata Manager Service runs on.
Associated Integration Service
PowerCenter Integration Service used by Metadata Manage to load metadata into the Metadata Manager warehouse.
Repository User Name
User account for the PowerCenter repository. Use the repository user account you configured for the PowerCenter Repository Service. For a list of the required privileges for this user, see Privileges for the Associated PowerCenter Integration Service User.
Repository Password
Password for the PowerCenter repository user.
Security Domain
Name of the security domain to which the PowerCenter repository user belongs.
Database Type
Type of database for the Metadata Manager repository.
Code Page
Metadata Manager repository code page. The Metadata Manager Service and Metadata Manager application use the character set encoded in the repository code page when writing data to the Metadata Manager repository.
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 connect string to create a connection object to the Metadata Manager repository in the PowerCenter repository.
Database User
User account for the Metadata Manager repository database. Set up this account with the appropriate database client tools.
Database Password
Password for the Metadata Manager repository database user. Must be in 7-bit ASCII.
Tablespace Name
Tablespace name for Metadata Manager repositories 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 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.
Database Port
Port number for the Metadata Manager repository database.
SID/Service Name
Indicates whether the Database Name property contains an Oracle full service name or SID.
Database Name
Full service name or SID for Oracle databases. Service name for IBM DB2 databases. Database name for Microsoft SQL Server databases.
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 with 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 with a trusted connection, configure the Windows service properties to log on with 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.
Port Number
Port number the Metadata Manager application runs on. Default is 10250.
Enable Secured Socket Layer
Indicates that you want to configure a secure connection for the Metadata Manager web application. If you enable this option, you must create a keystore file that contains the required keys and certificates.
You can create a keystore file with keytool. keytool is a utility that generates and stores private or public key pairs and associated certificates in a keystore file. When you generate a public or private key pair, keytool wraps the public key into a self-signed certificate. You can use the self-signed certificate or use a certificate signed by a certificate authority.
Keystore File
Keystore file that contains the keys and certificates required if you configure a secure connection for the Metadata Manager web application. Required if you select Enable Secured Socket Layer.
Keystore Password
Password for the keystore file. Required if you select Enable Secured Socket Layer.

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.

Database Connect Strings

When you create a database connection, specify a connect string for that connection. The Metadata Manager Service uses the connect string to create a connection object to the Metadata Manager repository database in the PowerCenter repository.
The following table lists the native connect string syntax for each supported database:
Database
Connect String Syntax
Example
IBM DB2
dbname
mydatabase
Microsoft SQL Server
servername@dbname
sqlserver@mydatabase
Note: If you do not specify the connect string in the syntax specified, you must specify the ODBC entry specified for the data source.
Oracle
dbname.world (same as TNSNAMES entry)
oracle.world
Note: The Metadata Manager Service uses the DataDirect drivers included with the Informatica installation. Informatica does not support the use of any other database driver.

Overriding the Repository Database Code Page

You can override the default database code page for the Metadata Manager repository database when you create or configure the Metadata Manager Service. Override the code page if the Metadata Manager repository contains characters that the database code page does not support.
To override the code page, add the CODEPAGEOVERRIDE parameter to the Additional JDBC Options property. Specify a code page that is compatible with the default repository database code page.
For example, use the following parameter to override the default Shift-JIS code page with MS932:
CODEPAGEOVERRIDE=MS932;