Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Relate 360
  3. Linking Batch Data
  4. Tokenizing Batch Data
  5. Processing Streaming Data
  6. Creating Relationship Graph
  7. Loading Linked and Consolidated Data into Hive
  8. Searching Data
  9. Monitoring the Batch Jobs
  10. Troubleshooting
  11. Glossary

User Guide

User Guide

INGEST Web Service

INGEST Web Service

The INGEST web service reads the input data and then links or tokenizes the input data based on the value that you set for the
ALTERNATETABLEFORGROUPINFO
parameter in the configuration file. The INGEST web service then loads the linked or tokenized data into the repository.
When you deploy
Relate 360
on Spark or Storm, if you have specified the consolidation rules file, the INGEST web service consolidates the linked data and creates preferred records in the repository. If any input record is an update to an existing record, the INGEST web service updates the record in the repository.
During the linking process, when an input record matches with a record in the repository, the linking process links the input record to the cluster of the matching record. The linking process does not further match the input record with other records.
When you link the input data, ensure that you do not configure the
MaxCandidateSet
parameter in the configuration file. The
MaxCandidateSet
parameter value impacts the maximum number of records that the INGEST web service can add to a cluster.
Before you run the INGEST web service, run the GETINGESTLAYOUT web service to get the layout for the input data in the JSON format based on the configuration file. Based on the layout, you can specify the input data for the INGEST web service.

Request URL

Use the POST method to run the INGEST web service.
To run the INGEST web service, use the following URL format:
http://<Host>:<Port>/<WAR File Name>/<Version Number>/<Configuration File Identifier>/INGEST
For example:
http://localhost:8080/MDMBDRMSYS/
v5.0
/SYS/INGEST

Request Header

Use the request header to specify the following headers:
Token
Required if you secure the RESTful web services. Authentication token that the Authenticate web service returns. If the token is not valid or you do not specify the
Token
header, the web service request uses the
Authorization
header.
Authorization
Required if you have secured the RESTful web services, but optional if you specify the
Token
header.
Type of authentication and the user credentials in the Base64 format. The RESTful web services use the HTTP basic authentication. Use the following format to specify the value for the
Authorization
header:
Basic <Encoded User Credentials>
Basic
indicates the HTTP basic authentication, and
Encoded User Credentials
indicates the Base64 format of the user name and password separated by a colon. For example,
Authorization: Basic dGVzdDpUZXN0
Accept
Format of the response. The supported response format is JSON. Specify
application/json
as the header value.
Content-Type
Format of the request body. The supported format is JSON. Specify
application/json
as the header value.

Request Body

Use the request body to specify the input data for the INGEST web service based on the layout that the GETINGESTLAYOUT web service returns.
The following sample body contains a record for the INGEST web service to process:
{ "input":{ "SOURCE":"AML", "PERSON":"Susan Shaw", "ADDRESS":"Castle Boulevard", "POSTCODE":"94061", "CITY":"Redwood City", "ROWID":"0000300002" }, "resultCount":0, "messages":{ }

Sample Response

The following sample response shows a record that the INGEST web service submits for processing:
{ "input":{ "SOURCE":"AML", "PERSON":"Susan Shaw", "ADDRESS":"Castle Boulevard", "POSTCODE":"94061", "CITY":"Redwood City", "ROWID":"0000300002" }, "resultCount":1, "messages":{ "Message.1":"Record submitted for Processing" } }

0 COMMENTS

We’d like to hear from you!