Connection String to a Secure Database
If you create a repository on a secure database, you must provide the truststore information for the database and a JDBC connection string that includes the security parameters for the database.
During installation, you can create the domain configuration repository in a secure database. You can also create the Model repository in a secure database.
You can configure a secure connection to the following databases:
- •IBM DB2 UDB
- •Microsoft SQL Server
- •Oracle
Note: You cannot configure a secure connection to a Sybase database.
When you configure the connection to the secure database, you must specify the connection information in a JDBC connection string. In addition to the host name and port number for the database server, the connection string must include security parameters.
The following table describes the security parameters that you must include in the JDBC connection string:
Parameter | Description |
---|
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 is sent by the database server. If this parameter is set to True, Informatica validates the certificate that is sent by the database server. 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 is sent by the database server. Informatica ignores any truststore information that you specify. |
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. If SSL encryption and validation is enabled and this property is not specified, the driver uses the server name specified in the connection URL or data source of the connection to validate the 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 can use the following syntax in the JDBC connection string to connect to a secure database:
- IBM DB2
- jdbc:Informatica:db2://host_name:port_no;DatabaseName=database_name;EncryptionMethod=SSL;HostNameInCertificate=DB_host_name;ValidateServerCertificate=true_or_false
- Oracle
- jdbc:Informatica:oracle://host_name:port_no;ServiceName=service_name;EncryptionMethod=SSL;HostNameInCertificate=DB_host_name;ValidateServerCertificate=true_or_false
- Microsoft SQL Server
- jdbc:Informatica:sqlserver://host_name:port_no;SelectMethod=cursor;DatabaseName=database_name;EncryptionMethod=SSL;HostNameInCertificate=DB_host_name;ValidateServerCertificate=true_or_false
Note: 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.