IBM Data Virtualization connection

To access your data in Data Virtualization, create a connection asset for it. A Data Virtualization connection is created automatically in a catalog or project when you publish a virtual object to a catalog or assign it to a project. The IBM Data Virtualization connection was formerly know as the Watson Query connection.

Data Virtualization integrates data sources across multiple types and locations and turns all this data into one logical data view. This virtual data view makes the job of getting value out of your data easy.

Supported versions

IBM Data Virtualization 1.1.

Create a Data Virtualization connection

To create the connection asset, you need these connection details:

Credentials

Use one of these methods to authenticate to a Data Virtualization instance:

Connecting to a Data Virtualization instance in Cloud Pak for Data

  • User credentials: Enter your Cloud Pak for Data username and password.
  • API key: Enter an API key value with your Cloud Pak for Data username and a Cloud Pak for Data API key. Use this syntax: user_name:api_key
  • Use my platform login credentials. This option is available If you select Personal credentials and the User credentials authentication method. The Data Virtualization service must be deployed on the same instance of Cloud Pak for Data where you are creating the connection. With platform credentials, the connection to Data Virtualization is established by using your current session JSON Web Token (JWT).

Connecting to a Data Virtualization instance in IBM Cloud

  • API key: Enter an IAM API key. Prerequisites:
    1. Add the user ID as an IAM user or as a service ID to your IBM Cloud account. For instructions, see the Console user experience section of the Identity and access management (IAM) on IBM Cloud topic.
    2. The Data Virtualization Manager of the Data Virtualization instance must add IAM users by selecting Data > Data Virtualization > Administration > User management from the IBM watsonx navigation menu.

For Credentials and Certificates, 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.

Restriction

You can use this connection only for source data. You cannot write to data with this connection.

Learn more