Type of database for the Metadata Manager repository. To apply changes, restart the Metadata Manager Service.

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.

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.

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.

Password for the Metadata Manager repository database user. Must be in 7-bit ASCII. To apply changes, restart the Metadata Manager Service.

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.

Host name for the Metadata Manager repository database. To apply changes, restart the Metadata Manager Service.

Port number for the Metadata Manager repository database. To apply changes, restart the Metadata Manager Service.

Indicates whether the Database Name property contains an Oracle full service name or an SID.

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 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

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.
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 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