Creating, modifying, or removing a connection from SQL DI to Db2 with web UI

After successful installation and configuration, connect your SQL Data Insights (SQL DI) application to your Db2 system or data sharing group. This secure JDBC connection is required for SQL DI to access your Db2 user tables or views. You can create and activate a connection on the Connections page of the SQL DI web UI.

Before you begin

Make sure that you have the authorization that is required for a specific task in SQL DI. See Managing SQL DI user permissions and Configuring setup user ID for SQL DI for details.

Procedure

  1. Sign in your SQL DI web UI with a valid RACF® user ID at the following address:


    https://<SQLDI-IPAddress>:<SQLDI-PortNumber>

    SQL DI uses a login group to identify and authorize users. The default group name is SQLDIGRP. Make sure that the user ID that you specify is defined in your SQL DI login group.

  2. On the Connections page, click Add connection.
  3. On the Add connection page, specify a name and details for the connection, including the hostname or IP address, port number, location, JDBC properties (optional), and special registers (optional) of your Db2 system or data sharing group.
  4. Optionally, check Port enabled for SSL connections and enter the SSL certificate content in the input field.

    If your Db2 system or data sharing group uses SSL for network communications, you must configure the new connection with the required SSL certificate information. You can provide your SSL certificate information in one of the following ways:

    • Option 1: Check the box for Port enabled for SSL connections and provide the required SSL certificate information. Your SSL certificate must use Base64 ASCII encoding in PEM (.pem) format. Make sure that the certificate content is bound by the -----BEGIN CERTIFICATE----- header and the -----END CERTIFICATE----- footer.
    • Option 2: Specify the following value in the JDBC properties field in the previous step:
      sslConnection=true;sslCertLocation=<path_to_trusted_certificate>

      Where <path_to_trusted_certificate> is the full path and the file name of your SSL certificate on the system where your SQL DI runs. The certificate must use Base64 ASCII or binary encoding in ARM (.arm), PEM (.pem), CERT (.cert), CRT (.crt), or DER (.der) format. If the certificate file uses Base64 ASCII encoding, make sure that the certificate content is bound by the plain-text -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines.

  5. Enter your Db2 username and password.

    Make sure that your username or ID has sufficient privileges to access the Db2 system or the Db2 data sharing group.

  6. Click Add to create the new connection.
  7. Back on the Connections page, verify that the new connection shows up.
  8. Optionally, activate the new connection.

    A new connection is activated (green-checked) when it is created. If necessary, you can deactivate the connection by selecting Disconnect from the Action selection menu action menu of the connection. To re-activate the connection:

    1. Click the action menu Action selection menu and select Connect.
    2. Enter your Db2 username and password.
    3. Click Connect to activate the connection.

      The connection is successfully activated when it's green-checked.

    If necessary, you can deactivate, edit, or remove the connection.