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:

The description cannot exceed 765 characters.

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 object that allows use of the service.

Node in the Informatica domain that the Metadata Manager Service runs on.

PowerCenter Integration Service used by Metadata Manage to load metadata into the Metadata Manager warehouse.

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.

Password for the PowerCenter repository user.

Name of the security domain to which the PowerCenter repository user belongs.

Type of database for the Metadata Manager repository.

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.

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.

User account for the Metadata Manager repository database. Set up this account with the appropriate database client tools.

Password for the Metadata Manager repository database user. Must be in 7-bit ASCII.

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.

Host name for the Metadata Manager repository database.

Port number for the Metadata Manager repository database.

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

Full service name or SID for Oracle databases. Service name for IBM DB2 databases. Database name for Microsoft SQL Server databases.

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 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.
If the Metadata Manager repository database is Azure Microsoft SQL Server database, you must configure the JDBC parameters for the secure database.

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

Port number the Metadata Manager application runs on. Default is 10250.

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.

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.

Password for the keystore file. Required if you select Enable Secured Socket Layer.