watsonx.data connection

Connection details

To create the connection asset, you need these details for the watsonx.data instance:

• Hostname or IP address: Find this information in the URL of the watsonx.data web console. https://<hostname-or-IPaddress>/watsonx-data/#/home?instanceId=<instance-id>

• Port: Find this number in the URL of the watsonx.data web console. On IBM Cloud, the default port number is 443.

• watsonx.data instance ID:

  • Cloud Pak for Data or stand-alone watsonx.data: Find this information in the URL of the watsonx.data web console in the instanceId field.
  • IBM Cloud: Find this value in the {instance_id} segment of the CRN. For example:
    crn:v1:{cname}:{ctype}:{service_id}:{region_id}:a/{account_id}:{instance_id}::

• watsonx.data instance name:

  • Cloud Pak for Data: Find the instance name in the Cloud Pak for Data web client home page at Overview > Instances.
  • IBM Cloud or stand-alone watsonx.data: The default value is lh-default.

• CRN: Cloud resource name: This field is needed only for connections to IBM Cloud. Find this information in the IBM Cloud resource list for the watsonx.data service.

Select Connect to watsonx.data on Cloud Pak for Data, if you are connecting to an instance on Cloud Pak for Data.

Credentials

Username and password for the watsonx.data instance. The same credentials are used for the engine. For watsonx.data that is deployed on IBM Cloud, the default username is ibmlhapikey_<cloud-account-email-address>. For example: ibmlhapikey_username@example.com.

For Credentials, you can use secrets if a vault is configured for the platform and the service supports vaults. For information, see Using secrets from vaults in connections.

Engine connection details

• Engine's hostname or IP address: Find this information in the watsonx.data web console. Go to the Infrastructure manager and click the engine's name.
• Engine ID: Find this information in the watsonx.data web console. Go to the Infrastructure manager and click the engine's name.
• Engine's port: Find this number in the watsonx.data web console. Go to the Infrastructure manager and click the engine's name.

Certificates

By default, Engine is SSL-enabled is selected. This setting is recommended for increased security. If you do not use SSL, the data might be subject to vulnerabilities such as data leakage.

Although the database that is hosted in watsonx.data can also have an SSL certificate, the connection goes through the engine.

For a connection to IBM Cloud, select Validate the SSL certificate. Do not select this option for a connection to Cloud Pak for Data or stand-alone watsonx.data.

Choose the method for creating a connection based on where you are in the platform

In a project

Click Assets > New asset > Data access tools > Connection. See Adding a connection to a project.

In a catalog

Click Add to catalog > Connection. See Adding a connection asset to a catalog.

In the Platform assets catalog

Click New connection. See Adding platform connections.

Next step: Add data assets from the connection

• See Add data from a connection in a project.
• See Add data from a connection in a catalog.

Protect sensitive data in watsonx.data

You can import watsonx.data data into Watson Knowledge Catalog and mask that source data inside watsonx.data with data protection rules.
Follow these instructions:

1. Enable Watson Knowledge Catalog integration in Cloud Pak for Data.
2. Set up the integration with Watson Knowledge Catalog in the watsonx.data console.
3. Mask the data assets with data protection rules in Watson Knowledge Catalog.

Federal Information Processing Standards (FIPS) compliance

The watsonx.data connection is compliant with FIPS. However, SSL certificates that you paste into the SSL certificate field are not supported. As a workaround, you can add the certificate to the OpenShift secret named connection-ca-certs. See Using a CA certificate to connect to internal servers from the platform for the procedure.