IBM Match 360 connection

Use the IBM Match 360 connection to connect to data that you can transform, refine, or analyze before you bring it into the IBM Match 360 with Watson service.

IBM Match 360 with Watson is a master data management service that helps you to resolve data across different sources and gain a clearer view of each customer, supplier, or partner. Load record data from systems across your enterprise into IBM Match 360 and run matching algorithms to consolidate that data into master data entities. A master data entity is a collection of records that provides a 360-degree view of a person, organization, or other entity. One or many member records can contribute to the master data entity view.

Prerequisite

You need an instance of IBM Match 360 with Watson on Cloud Pak for Data. For instructions, see Installing IBM Match 360 with Watson.

Create a connection to IBM Match 360

  • Route host: Path to the IBM Match 360 service on Cloud Pak for Data. You can get this information from Cloud Pak for Data instance namespace where the IBM Match 360 service is running. For example, in an OpenShift environment, run this command:

    oc get routes -n <namespace>

  • Match 360 instance ID: From the Cloud Pak for Data home page, go to Services > Instances. Click the link for the Match 360 with Watson instance that you want to connect to. Copy the value after mdm- in the URL. For example, if the end of the URL is mdm-1234567891123456, the instance ID is: 1234567891123456.

  • API key: If you do not know the value of your API key, you can generate a new platform API key for your Cloud Pak for Data account. Log in to the web client, click your avatar in the toolbar, and then click Profile and settings. Click API key > Generate new key.

    Note: If you generate a new API key, your current API key becomes invalid. You must either modify the existing connection to use the new API key or delete the existing connection and create a new connection that uses the new API key. You must also update any scripts or applications to use the new API key.

  • Username: Username of the Cloud Pak for Data user who is creating the connection.

    The username must have permission to create storage volumes. This is normally an Administrator level permission. Creating storage volumes is required for jobs that import data to a target IBM Match 360 connection. For information, see Managing storage volumes and Managing persistent volume instances with the Volumes API.

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.

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

Where you can use this connection

You can use the IBM Match 360 connection in the following workspaces and tools:

Projects

Catalogs

  • Platform assets catalog

  • Other catalogs (Watson Knowledge Catalog)

    Note:

    Preview, profile, and masking do not work for this connection in Watson Knowledge Catalog.

Federal Information Processing Standards (FIPS) compliance

The IBM Match 360 connection is compliant with FIPS.

Limitations and known issues

  • The number of records that are included in previews for entity type data assets is limited to 100 records.

  • A single user cannot run two bulk load jobs at the same time.

  • When you use IBM Match 360 as a target connection, do not map these system attributes:

    • collection_id
    • created_date
    • created_user
    • entity_id
    • entity_last_updated
    • last_updated_date
    • last_updated_user
    • record_last_updated
    • record_number

In some cases, such as if a user stops an Import job before it completes, the storage volume might not get cleaned up correctly. This causes future attempts to run the Import job to fail with the message, Persistent storage value already exists. To resolve this issue:

  1. Make sure no Import jobs are currently running.
  2. Manually delete the storage volume.

Learn more

Parent topic: Supported connections