Data Engineering Integration
- Data Engineering Integration 10.4.1
- All Products
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:
` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
|
Description
| Description of the service. 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 service after you create it.
|
License
| License object that allows use of the service.
|
Node
| Node on which the service runs.
|
Property
| Description
|
---|---|
Associated Integration Service
| Select the PowerCenter Integration Service used by Metadata Manager to load metadata into the Metadata Manager warehouse.
|
Repository User Name
| User name that the service uses to access the PowerCenter Repository Service. Enter the PowerCenter repository user that you created. Required when you associate a PowerCenter Repository Service with the service.
Not available for a domain with Kerberos authentication.
|
Repository Password
| Password associated with the PowerCenter repository user.
Not available for a domain with Kerberos authentication.
|
Security Domain
| LDAP security domain for the PowerCenter repository user. The
Security Domain
field appears when the Informatica domain contains an LDAP security domain. Required when you associate a PowerCenter Repository Service with the service.
Not available for a domain with Kerberos authentication.
|
Property
| Description
|
---|---|
Database Type
| The type of the repository database.
|
Code Page
| Metadata Manager repository code page. The Metadata Manager Service and the Metadata Manager application use the character set encoded in the repository code page when writing data to the Metadata Manager repository.
You can enable the Metadata Manager Service only after you specify the code page.
|
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.
Use the following native connect string syntax for each supported database:
|
Database User
| The database user name for the repository.
|
Database Password
| Password for the Metadata Manager repository database user. Must be in 7-bit ASCII.
|
Tablespace Name
| Name of the tablespace in which to create all the repository database tables. You cannot use spaces in the tablespace name.
Available for IBM DB2 databases.
To improve repository performance on IBM DB2 EEE repositories, specify a tablespace name with one node.
|
Database Hostname
| The name of the machine that hosts the database server.
|
Database Port
| The port number on which you configure the database server listener service.
|
SID/Service Name
| For Oracle databases. Indicates whether to use the SID or service name in the JDBC connection string. For Oracle RAC databases, select from Oracle SID or Oracle service name. For other Oracle databases, select Oracle SID.
|
Database Name
| The name of the database server.
Specify the full service name or SID for Oracle databases, service name for IBM DB2 databases, and database name for Microsoft SQL Server databases.
|
Parameter
| Description
|
---|---|
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:
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
| To authenticate the user credentials with Windows authentication and establish a trusted connection to a Microsoft SQL Server repository, enter the following text:
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 Database Parameter
| Description
|
---|---|
EncryptionMethod
| Required. Indicates whether data is encrypted when transmitted over the network. This parameter must be set to
SSL .
|
TrustStore
| Required. Path and file name of the truststore file that contains the SSL certificate of the database server.
|
TrustStorePassword
| Required. 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 SSL certificate.
|
ValidateServerCertificate
| Optional. Indicates whether Informatica validates the certificate that the database server sends.
If this parameter is set to True, Informatica validates the certificate that the database server sends. If you specify the HostNameInCertificate parameter, Informatica also validates the host name in the certificate.
If this parameter is set to False, Informatica does not validate the certificate that the database server sends. Informatica ignores any truststore information that you specify.
|
KeyStore
| Path and file name of the keystore file that contains the SSL certificates that the Metadata Manager Service sends to the database server.
|
KeyStorePassword
| Password used to access the keystore file.
|
Property
| Description
|
---|---|
HTTPS Port
| Port number to use for a secure connection to the service. Use a different port number than the HTTP port number.
|
Keystore File
| Path and file name of the keystore file that contains the private or public key pairs and associated certificates. Required if you use HTTPS connections for the service.
|
Keystore Password
| Plain-text password for the keystore file.
|