MySQL Connector > MySQL connections > MySQL connection properties
  

MySQL connection properties

When you set up a MySQL connection, configure the connection properties.
The following table describes the MySQL connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
For information about how to configure and use a secrets manager, see Secrets manager configuration.
Runtime Environment
The name of the runtime environment where you want to run the tasks.
Specify a Secure Agent, Hosted Agent, serverless, or elastic runtime environment.
For more information about how to configure an elastic runtime environment, see Configure the elastic runtime environment.
User Name
User name for the database login. The user name can't contain a semicolon.
Password
Password for the database login. The password can't contain a semicolon.
Host
Name of the machine that hosts the database server.
Port
Network port number used to connect to the database server.
Default is 3306.
Database Name
Name of the MySQL database that you want to connect to.
Note: The database name is case-sensitive.
Maximum length is 64 characters. Database name can contain alphanumeric and underscore characters.
Code Page
The code page of the database server.
Metadata Advanced Connection Properties
Additional properties for the JDBC driver to fetch the metadata. Enter properties in the following format:
<parameter name>=<parameter value>
If you enter more than one property, separate each key-value pair with an ampersand (&).
For example, enter the following property to configure the connection timeout when you test a connection:
connectTimeout=<milliseconds>
Note: The default connection timeout is 270000 miliseconds.
Runtime Advanced Connection Properties
Additional properties for the ODBC driver to run mappings.
If you specify more than one property, separate each key-value pair with a semicolon.

SSL properties

You can configure a MySQL connection to use SSL to securely communicate with the MySQL database.
Note: You can enable SSL for a MySQL connection only when you use the 8.x MySQL JDBC and ODBC drivers. Ensure that both the MySQL JDBC and ODBC drivers are of 8.x version.
To configure SSL, you must first download and install the MySQL ODBC and JDBC drivers, version 8.x. For information about installing the MySQL ODBC and JDBC drivers, version 8.x, see the Knowledge Base article: 561573
After you install the drivers, in the MySQL connection properties, enable SSL and specify the TLS protocols that you want to use for the secure communication.
When you enable SSL for the MySQL connection, you must configure the SSL properties for both the MySQL JDBC and ODBC drivers. Configure the required SSL properties for the JDBC driver, so that the Secure Agent can access metadata securely from MySQL. Also, configure the required SSL properties for the ODBC driver, so that the Secure Agent runs mappings to securely read from or write data to MySQL.
Note: SSL is not applicable when you use the Hosted Agent. You can configure SSL when you use the Secure Agent or the serverless runtime environment.
The following table describes the MySQL connection SSL properties:
Connection property
Description
Use SSL
Determines whether the Secure Agent establishes a secure connection to the MySQL database.
When you select this option and the database server supports SSL, the Secure Agent establishes an encrypted connection. If the MySQL database server cannot configure SSL, the connection either fails or the Secure Agent establishes an unencrypted connection depending on whether you enable or disable the Require SSL checkbox.
If you do not select the Use SSL checkbox, the Secure Agent attempts to establish an unencrypted connection.
Verify Server Certificate
If you select Use SSL and select this option, the client validates the server certificate that is sent by the database server.
Require SSL
Applicable only if you select Use SSL.
If you select the Require SSL checkbox, and the MySQL database supports SSL, the Secure Agent establishes an SSL connection.
If you select the Require SSL checkbox, and the MySQL database cannot configure SSL, the Secure Agent attempts to establish an SSL connection but fails.
If you clear the Require SSL checkbox, and the MySQL database cannot configure SSL, the Secure Agent establishes an unencrypted connection.
TLS Protocols
The TLS protocols used for the secure communication when you select Use SSL.
You can select from the following protocols:
  • - TLSv1
  • - TLSv1.1
  • - TLSv1.2
Default is TLSv1.2. The TLSv1 and TLSv1.1 protocols are not applicable.
The following table describes the MySQL connection properties for the JDBC driver version 8.x when you enable Use SSL:
Connection property
Description
Trust Certificate Key Store
The path and file name of the truststore file. You must prefix the file path with file colon (file:).
For example, file:C:\SSL\mysql_new\truststore
For the serverless runtime environment, specify the following certificate path in the serverless agent directory:
/home/cldagnt/SystemAgent/serverless/configurations/ssl_store/<TrustStore_filename>
Trust Certificate Key Store Password
The password for the truststore file.
Client Certificate Key Store
The path and file name of the keystore file. You must prefix the file path with file colon (file:).
For example, file:C:\SSL\mysql_new\keystore
For the serverless runtime environment, specify the following certificate path in the serverless agent directory:
/home/cldagnt/SystemAgent/serverless/configurations/ssl_store/<KeyStore_filename>
Client Certificate Key Store Password
The password to access the keystore file.
JDBC Cipher Suites
Colon-separated cipher suite values in RFC format.
For example:
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256:
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
The following table describes the MySQL connection properties for the ODBC driver version 8.x when you enable Use SSL:
Connection property
Description
SSL Certificate Authority
The path and name of the CA certificate.
For example, C:\SSL\mysql_new\ca.pem
SSL Certificate
The path and name of the client certificate.
For example, C:\SSL\mysql_new\client-cert.pem
SSL Key
The path and the name of the private key of the client.
For example, C:\SSL\mysql_new\client-key.pem
SSL Cipher
Colon-separated cipher-suite values in OpenSSL format.
For example:
ECDHE-ECDSA-AES128-GCM-SHA256:
ECDHE-ECDSA-AES256-GCM-SHA384:
ECDHE-RSA-AES128-GCM-SHA256:
Verify Server's Identity
Verifies the host name in the certificate while verifying the server CA certificate.
This property is applicable only when you enable Verify Server Certificate in the SSL properties.

Configure the elastic runtime environment

You can configure a MySQL connection to use an elastic runtime environment to securely communicate with the MySQL database.
Before you configure a MySQL connection using the elastic runtime environment, perform the following tasks:
  1. 1Deploy the elastic runtime environment on AWS to make the Kubernetes cluster available to process data from Informatica Intelligent Cloud Services.
  2. For more information about deploying an elastic runtime environment, see Deploy an elastic runtime environment.
  3. 2Ensure that the elastic agent is up and running and enable the required connectors.
  4. To enable connectors in the elastic agent, perform the following steps:
    1. aIn Administrator, select Runtime Environments.
    2. bRight-click the Secure Agent group and select Enable or Disable Services and Connectors.
    3. A dialog box listing all the services and connectors for the Secure Agent group is displayed.
    4. cOn the Connectors tab, enable the required connectors.
    5. dClick OK.
  5. 3Create a data disk in the same environment where the elastic runtime cluster is running to store the custom binaries.
  6. 4On the master node, create a directory and mount the EFS or data disk to that directory.
  7. 5Place the custom binaries on the mounted disk and copy the exact path to the binaries.
  8. This path is used in POST API calls.
  9. 6Log in to Informatica Intelligent Cloud Services and obtain the session ID and runtime environment ID.
  10. 7Make a POST call to the REST API, passing the session ID, runtime environment ID, and the binary file path to register the binaries.
  11. For more about information about making the POST calls, see Supplementary files in the REST API Reference guide.
    The following is an example of the POST request:
    POST <base URL>/api/v3/RuntimeEnvironment/<runtime environment ID>/ElasticConfig
    Content-Type: application/json
    Accept: application/json
    INFA-SESSION-ID: <SessionId>
    {
    "rteId": "rte-12345",
    "specification": {
    "agent": {
    "dataIntegrationServer": },
    "mysql": {
    "jdbcDrivers": [{"sourcePath": "/<path to binaries>/jdbc1.jar"}],
    "odbcDrivers": [{"sourcePath": "/<path to binaries>/odbc1.so"}],
    "version": "8.0"
    }
    The POST call triggers a restart of the Data Integration Server.
  12. 8Verify that the elastic runtime environment is running by checking the status of the Data Integration Server in Administrator.
  13. 9Test a connection or run a mapping to confirm that the elastic runtime environment can access and use the custom binaries.
For more information about how to configure and use the elastic runtime environment, see Elastic runtime environment.