Installation for PowerCenter and Data Quality

10.5.7
- 10.5.6
- 10.5.5.1
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0

Back Next

Domain Configuration Repository

After you configure domain security, you can configure domain repository details.

Select the database to use for the domain configuration repository details.

The following table lists the databases you can use for the domain configuration repository:

Prompt	Description
Database type	Type of database for the domain configuration repository. Select from the following options: 1 - Oracle 2 - Microsoft SQL Server 3 - IBM DB2 4 - Sybase ASE 5 - PostgreSQL

The Informatica domain configuration repository stores metadata for domain operations and user authentication. The domain configuration repository must be accessible to all gateway nodes in the domain.

Enter the properties for the database user account.

The following table lists the properties for the database user account:

Property	Description
Database user ID	Name for the domain configuration database user account.
User password	Password for the domain configuration database user account.

Select whether to create a secure domain configuration repository.

You can create a domain configuration repository in a database secured with the SSL protocol. To create a domain configuration repository in a secure database, press 1 and skip to step to create a domain configuration repository.

To create a domain configuration repository in an unsecure database, press 2.

If you do not create a secure domain configuration repository, enter the parameters for the database.

If you select IBM DB2, select whether to configure a tablespace and enter the tablespace name.

The following table describes the properties that you must configure for the IBM DB2 database:

Property	Description
Configure tablespace	In a single-partition database, if you select No, the installer creates the tables in the default tablespace. In a multi-partition database, you must select Yes. Select whether to specify a tablespace: 1 - No 2 - Yes
Tablespace	Name of the tablespace in which to create the tables. Specify a tablespace that meets the pageSize requirement of 32768 bytes. In a single-partition database, enter the name of the tablespace in which to create the tables. In a multipartition database, specify the name of the non-partitioned tablespace that resides in the catalog partition of the database.

If you select Microsoft SQL Server or PostgreSQL, enter the schema name for the database.

The following table describes the properties that you must configure for the database:

Property	Description
Schema name	Name of the schema that will contain domain configuration tables. If this parameter is blank, the installer creates the tables in the default schema.

To enter the JDBC connection information using the JDBC URL information, press

. To enter the JDBC connection information using a custom JDBC connection string, press

Enter the JDBC connection information.

To enter the connection information using the JDBC URL information, specify the JDBC URL properties.

The following table describes the database connection information:

Prompt	Description
Database host name	Host name for the database.
Database port number	Port number for the database.
Database service name	Service or database name: Oracle: Enter the service name. Microsoft SQL Server: Enter the database name. IBM DB2: Enter the service name. Sybase ASE: Enter the database name. PostgreSQL: Enter the database name.
Configure JDBC Parameters	Select whether to add additional JDBC parameters to the connection string: 1 - Yes 2 - No If you select Yes, enter the parameters or press Enter to accept the default. If you select No, the installer creates the JDBC connection string without parameters.

To enter the connection information using a custom JDBC connection string, type the connection string.

Use the following syntax in the JDBC connection string:

IBM DB2: jdbc:Informatica:db2://<host name>:<port number>;DatabaseName=
Oracle: jdbc:Informatica:oracle://<host name>:<port number>;ServiceName=; Use the following connection string to connect to the Oracle database through the Oracle Connection Manager:

jdbc:Informatica:oracle:TNSNamesFile=<fully qualified path to the tnsnames.ora file>;TNSServerName=<TNS name>;
Microsoft SQL Server: jdbc:Informatica:sqlserver://<host name>:<port number>;SelectMethod=cursor;DatabaseName=
Microsoft SQL Server with Windows NT credentials: If you specified the Windows NT credentials for the Model repository database on Microsoft SQL Server, specify the connection string syntax to include the authentication method as NTLM.

Microsoft SQL Server that uses the default instance with Windows NT credentials:

"jdbc:informatica:sqlserver://<host name>:<port number>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"

Microsoft SQL Server that uses a named instance with Windows NT credentials:

"jdbc:informatica:sqlserver://<host name>\<named instance name>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"
Microsoft Azure SQL: jdbc:Informatica:sqlserver://<host name>:<port number>;SelectMethod=cursor;DatabaseName=<database name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.database.windows.net;ValidateServerCertificate=false
Azure SQL Database with Active Directory authentication: jdbc:informatica: sqlserver://<host_name>:<port_number>;database=<database_name>;encrypt=true;AuthenticationMethod=ActiveDirectoryPassword;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=<seconds>
PostgreSQL: jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=
Azure PostgreSQL: jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=<database name>;EncryptionMethod=SSL;ValidateServerCertificate=true;CryptoProtocolVersion=TLSv1.2;
Sybase: jdbc:Informatica:sybase://<host name>:<port number>;DatabaseName=

Verify that the connection string contains all the connection parameters required by your database system.

If you create a secure domain configuration repository, enter the parameters for the secure database.

If you create the domain configuration repository on a secure database, you must provide the truststore information for the database.

The following table describes the options available to create a secure domain configuration repository database:

Property	Description
Database truststore file	Path and file name of the truststore file for the secure database.
Database truststore password	Password for the truststore file.
Custom JDBC Connection String	JDBC connection string to connect to the secure database, including the host name and port number and the security parameters for the database.

In addition to the host name and port number for the database server, you must include the following secure database parameters:

EncryptionMethod: Required. Indicates whether data is encrypted when transmitted over the network. This parameter must be set to
SSL.
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

Default is True.
HostNameInCertificate: Optional. Host name of the machine that hosts the secure database. If you specify a host name, Informatica validates the host name included in the connection string against the host name in the SSL certificate.
cryptoProtocolVersion: Required. Specifies the cryptographic protocol to use to connect to a secure database. You can set the parameter to
cryptoProtocolVersion=TLSv1.1
or
cryptoProtocolVersion=TLSv1.2
based on the cryptographic protocol used by the database server.

You must also provide a JDBC connection string that includes the security parameters for the database. You can use the following syntax for the connection strings:

Oracle:

jdbc:Informatica:oracle://<host name>:<port number>;ServiceName=<service name>;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>

IBM DB2:

jdbc:Informatica:db2://<host name>:<port number>;DatabaseName=<database name>;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>

Microsoft SQL Server:

jdbc:Informatica:sqlserver://<host name>:<port number>;SelectMethod=cursor;DatabaseName=<database name>;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>

Microsoft Azure SQL:

jdbc:Informatica:sqlserver://<host name:port number>;SelectMethod=cursor;DatabaseName=<database name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>

PostgreSQL:

jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=<database name>;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>

The installer does not validate the connection string. Verify that the connection string contains all the connection parameters and security parameters required by your database.

If the database contains a domain configuration repository for a previous domain, select to overwrite the data or set up another database.

Press 1 for OK to enter the connection information for a new database.

Press 2 for Continue for the installer to overwrite the data in the database with new domain configuration.

The

Domain Security - Encryption Key

section appears.

Create a Domain

Download Guide

Watch

Comments

Communities

Knowledge Base