Connecting data to IBM Match 360

Create your connection assets:

• Source database connection: A connection to the source database using any connection supported by Cloud Pak for Data
• Target connection: An IBM Match 360 connection
• Write mode: Define whether to load the data in bulk (Load) or in small chunks on an ongoing basis (Ongoing synchronization). The ongoing synchronization option is useful for Delta-load scenarios.

For details about creating these connections, see Connectors and its subtopics.

Set up a DataStage flow to move data into IBM Match 360. For example: [Source database connection] node -> COPY stage -> [IBM Match 360 connection] node.

Link all three nodes together.

Set up source properties such as connection, schema name, and table name.

Select the data columns you want to move.

a. In the source database node's detail panel, click Edit > Import data, and select the columns you want to move into IBM Match 360. You can optionally select a subset of the columns.

b. For any LONGVARCHAR data types, change them to the VARCHAR data type and change the length to 200.

c. Click Apply.

Map columns to the IBM Match 360 data model.

a. Select the COPY stage.

b. Go to the Input tab and confirm that it lists the columns you selected in the previous step.

c. Go to the Output tab, then click Edit.

d. Map the current data column names to your IBM Match 360 data model.

• Select and delete all of the output columns. Click Import data, then find the corresponding data columns from within the IBM Match 360 connection.
• Click Import to save the changes.
• Back on the Output tab, click Edit again, then use the Map from input column column to map the IBM Match 360 column names to the source column names.
• Click Apply and return.

Set up target properties.

a. Click the IBM Match 360 connection tab.

b. Choose the IBM Match 360 connection, and then define the data category, data type (record type), and entity type, such as record, person, and person_record. Use names that exactly match your IBM Match 360 data model.

c. Click Save.

Save, compile, and run the DataStage flow. After you see a success notification, the data is loaded into IBM Match 360 and is now ready to match.

Create your connection assets:

• Source connection: An IBM Match 360 connection
• Target database connection: A connection to the source database using any connection supported by Cloud Pak for Data
• Export job ID (optional): The job ID of a completed IBM Match 360 export job that you want to extract data from. If a value is provided for this field, the other input fields are ignored and the service exports the data associated with the provided export ID.
• Filter rule (optional): JSON-formatted search criteria that defines which record or entity data is included in the export. If no filter rule is provided, all of the data gets exported. Filter rules can contain a nested combination of expressions. Each expression contains a property, a condition, and a value. For example, use the following JSON payload to define a filter that exports record or entity data that includes a value for personal email and the Legal Given Name starts with an S or the Legal Last Name starts with an M. Additionally, as defined by the includeDeletes flag, this example export includes information about any entity data that was deleted after the defined last updated date (entity_last_updated):

{
"query": {
  "expressions": [
    {
      "operation": "or",
      "expressions": [
        {
          "property": "legal_name.given_name",
          "condition": "starts_with",
          "value": "S"
        },
        {
          "property": "legal_name.last_name",
          "condition": "starts_with",
          "value": "M"
        }
      ]
    },
    {
      "property": "personal_email.email_id",
      "condition": "has_value",
      "value": null
    },
    {
      "property": "entity_last_updated",
      "condition": "greater_than_equal",
      "value": "0",
      "expressions": []
    }
  ],
  "operation": "and"
},
"includeDeletes": true
}

For more information about creating these connections, see Connectors and its subtopics.

Set up a DataStage flow, such as [IBM Match 360 connection] node -> [Target database connection] node. Unlike with an import flow, you don't need a COPY stage because mapping data columns is not necessary.

Set up your source properties.

a. Select the IBM Match 360 connection node.

b. In the Stage tab, configure the IBM Match 360 database properties, define the data category, data type (record type), and entity type for the data that you want to export, such as record, person, and person_record, using names that exactly match your IBM Match 360 data model.

c. Click Save. In the Output tab, browse and select the columns you want to move. Select the IBM Match 360 connection, then select the necessary data from the data model.

Set up your target properties.

a. In the target database node, define how you want the data to be applied to the database, such as insert, update, or merge. Then define the schema name and table name.

b. Click Save.

Save, compile, and run the DataStage flow. After you see a success notification, the data is loaded into the target database.

Create an IBM Match 360 connection.

a. In the Project > Assets action bar, click New asset > Connection.

b. Choose the IBM Match 360 connection.

c. Provide a name a description for this connection, then provide the remaining connection details of of the IBM Match 360 service instance that you want to connect to. For more information about creating a connection, see IBM Match 360 connection.

Create an IBM Match 360 connected data asset.

a. In the Project > Assets action bar, click New asset.

b. Select Connected data.

c. Click Select source, then choose a connection source from the available databases.

d. Choose your IBM Match 360 connection, then select the data from the data model that you want to include in this connected data asset.

e. Provide a name and description for your connected data asset, then click Create. You can now see the new connected data asset in your project's Assets tab.

Publish the data asset to a catalog.

a. From the project's Assets tab, find your data asset, then select Publish to catalog from the asset's overflow menu.

b. Choose the catalog that you want to publish to, give the job a description, and configure duplicate action behavior and privacy.

c. Optionally, add tags to help you organize and find your data, then click Publish. The data is now available in the catalog. For more information about working with catalog assets, see Catalog asssets.