The Trillium Quality client/server architecture allows multiple matching rules to be used for different objects. For example, one set of match rules may exist for Duplicate Check and a second set for Fuzzy/Rough Search. The specific server that is used for processing the matching rules is defined for each object type.
The table given below describes the parameters for the Matcher server (TRILLIUM/MCHPAR). All figures given below show the Matcher server Parameter Overview windows.
|
Setting |
Values |
Description |
|
Match func |
Text |
Application table logical name that corresponds to the object that is being displayed. |
|
Applic. table |
Text |
Key field name for the corresponding object that is being displayed. |
|
Field |
Text |
Identifier for the TS Connector Matcher processor for that object. |
|
Server Suffix |
Text |
Server ID. For example, RMatcher (Duplicate Check) or RMatc001 (Fuzzy/Rough Search). |
|
Comp name |
Text |
TS Connector component root name; for example, REF_MATCH. |
|
FM name |
Text |
Function Module name of the logic that performs matching. You are not required to make any changes to this field. n/TRILLIUM/DO_MATCHING = Duplicate Check |
|
RFC Dest |
Text |
Name of an RFC destination. Default to TRILLIUM_CONNECTOR. |
|
MchPkgSize |
Num |
Match package size. The number of records to be passed over at the same time to the Trillium Quality Matcher. Default is 500. |
|
Srvr sfx B |
Text |
Server ID for batch matching; for example, RMatcher (duplicate Check) or RMatc001 (Fuzzy/Rough Search). |
|
Cmp name B |
Text |
Mapping component name for batch matching. You are not required to make any changes to this field. nBATCH_MATCH = Duplicate Check |
|
FM Name B |
Text |
Function Module name of the logic that performs batch matching. You are not required to make any changes to this field. n/TRILLIUM/DO_BATCH_MATCHING = Batch Duplicate Check |
