http://<Host>:<Port>/<WAR File Name>/<Version Number>/<Identifier for Configuration and Matching Rules Files>/Multisearch

http://localhost:8080/MDMBDRMSYS/
v5.0/SYS/Multisearch

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.

{
   "searchType":"Football",
   "resultlimit":200,
   "scoreThreshold":0,
   "ignoreMatch":false,
   "searchinput":{
      "NAME":"Smith"
   },
   "searchlayout":{

   },
   "searchResults":[
      {
         "COMPANY":"INFA",
         "MatchRuleID":"match.rule",
         "NAME":"John Smith",
         "AGE":"30",
         "ADDRESS":"Bagmane Tech Park",
         "score":"094",
         "LMT_MATCHED_SCORE":"100",
         "DOJ":"2012",
         "LMT_MATCHED_RECORD_SOURCE":"SAP",
         "match_decision":"ACCEPT",
         "PHONE":"08040201001",
         "CLUSTERNUMBER":"00df1d63-44d2-4a73-9658-e5a5e47ed99c",
         "SOURCE":"Baan",
         "SALARY":"10000",
         "ID":"14",
         "PINCODE":"560101",
         "LMT_MATCHED_PK":"1",
         "CITY":"Bangalore",
         "MatchedIndex":"00",
         "LMT_SOURCE_NAME":"Baan"
      },
      {
         "COMPANY":"INFA",
         "MatchRuleID":"match.rule",
         "NAME":"John Smith",
         "AGE":"30",
         "ADDRESS":"Bagmane Tech Park",
         "score":"094",
         "LMT_MATCHED_SCORE":"100",
         "DOJ":"2013",
         "LMT_MATCHED_RECORD_SOURCE":"SAP",
         "match_decision":"ACCEPT",
         "PHONE":"08040201001",
         "CLUSTERNUMBER":"00df1d63-44d2-4a73-9658-e5a5e47ed99c",
         "SOURCE":"Baan",
         "SALARY":"10000",
         "ID":"18",
         "PINCODE":"560101",
         "LMT_MATCHED_PK":"1",
         "CITY":"Bangalore",
         "MatchedIndex":"00",
         "LMT_SOURCE_NAME":"Baan"
      }
   ],
   "searchToken":1994262671816343800,
   "pageLimit":10,
   "pageOffset":0,
   "totalCount":2,
   "debug":false,
   "resultCount":2,
   "messages":{
      "Message.0": "Fresh Token generated",
      "Response Time":"111 ms"
   }
}

match_decision

Indicates whether the match is accepted or rejected based on the match level and the search level that you configure.

Fields

Column values of all the index fields, the match fields, and the partition field, if defined.

score

Matching score for the record.

LMT_MATCHED_PK

Primary key column value of a record in the repository that matches with the matched record. The value 0 indicates that the matched record does not match with another record in the repository.

For example, a search returns record A as the matching record. If record A matches with record B,

LMT_MATCHED_PK

displays the primary key column value of record B.

LMT_MATCHED_SCORE

Matching score between the matched record and the record that matches with the matched record.

For example, a search returns record A as the matching record. If record A matches with record B,

LMT_MATCHED_SCORE

displays the matching score between record A and record B.

LMT_SOURCE_NAME

Source name of the matched record.

GROUPNO

Cluster identifier of the matched record.

<Primary Key Column Name>

Primary key column value of the matched record.

searchToken

Token that you can use in the subsequent search requests to retrieve the results from cache to avoid performing the search again. The token expires after the validity time that you configure in the

SearchTokenValidity

parameter of the configuration file. By default, the token is valid for 600 seconds. A search token value of -1 indicates that the pagination is disabled.

If you use search tokens to retrieve search results from cache, the other parameters in the search layout do not affect the search results.

totalCount

Number of matching search results.

resultCount

Number of search results that the search request returns. The number of results depends on the value of the

pageLimit

parameter.