Manually creating a Data Virtualization connection in a catalog or project

IBM® Knowledge Catalog includes a connector that is specific to Data Virtualization.

Before you begin

Ensure that Data Virtualization and IBM Knowledge Catalog are installed in the same OpenShift® project (namespace).

About this task

A connection is automatically created for your Data Virtualization instance in the Platform assets catalog when the Data Virtualization service instance is installed.

You can also create a connection to Data Virtualization in IBM Knowledge Catalog manually by using the Data Virtualization platform connector.

Also, when you publish a Data Virtualization object to a catalog or project that does not yet have a Data Virtualization connection, a Data Virtualization connection is added automatically to the target catalog or project.

Procedure

To manually create a Data Virtualization connection in a catalog, follow these steps.

  1. Click Catalogs > All catalogs.
  2. Select your catalog and click Add to catalog > Connection.
  3. Click From platform and select the Data Virtualization platform connection.
  4. Choose an Authentication method and enter your credentials as an API key or a username and password.
  5. Click Create.
    The connection appears on the Assets page. To edit the connection, follow these steps.
    1. Click the connection name on the Assets page.
    2. Click the Assets tab.
    3. Click Edit the connection in the preview.
      Important: Define the connection to Data Virtualization with an internal cluster hostname that ends with ".svc.cluster.local", such as c-db2u-dv-db2u-engn-svc.dv1.svc.cluster.local, and an instance ID that matches the Data Virtualization instance ID from the Data Virtualization Administration > Configure connection page. These settings enable profiling and metadata enrichment to retrieve raw data from Data Virtualization.

    The IBM Knowledge Catalog service uses the DV_SYSID functional role to connect to Data Virtualization. The DV_SYSID role is defined automatically in Data Virtualization and is required for profiling virtual assets. This role is intended for internal service use only, you must not use this role for any other purposes.