Services Integration Framework Guide

10.3 HotFix 1
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3

Back Next

Tokenize

The

Tokenize

API generates the match keys that the match engine and the

SearchMatch

request use when performing fuzzy matches. The

Merge

request does not use these match keys.

Tokenize

can also regenerate match tokens for a record that was previously tokenized.

In Informatica MDM Hub, you can also manually generate match tokens or configure the Hub to generate match tokens after the load process completes. For more information, see the Batch Jobs Reference in the

Multidomain MDM Configuration Guide

If you request

Tokenize

to regenerate tokens for a record that has not changed since the previous Tokenize, the request succeeds and reports that it tokenized zero records.

Transaction Support

When executed within an EJB context,

Tokenize

can follow a

Put

CleansePut

request in a single transaction. If there is a failure in any of the requests within a transaction, the entire transaction is rolled back.

Required Parameters

The following table describes the required

Tokenize

parameters.

Parameter	Description
setRecordKey(RecordKey)	Indicates the key of the record to be tokenized.
setActionType(String)	Action type returned from a previous Put or CleansePut request. Insert indicates that the record has not been tokenized. Update and Update xref indicate that the record has been previously tokenized and the tokens need regenerated.
SiperianObjectUid	The name of the package or base object.

Use Cases

The following scenarios are the common uses for the

Tokenize

request:

Use

Put

to insert or update the record in the package. Then call

Tokenize

to generate match keys.

Call

CleansePut

to cleanse the data and insert or update the record in the package. Then call

Tokenize

to generate match keys.

Tokenize Request Usage Example

The following example shows how to generate match tokens for a record with ROWID_OBJECT 782 using the ADDRESS_UPDATE package. This record is being tokenized for the first time, so an ActionType of

Insert

is used. The

Put

response provides the value of ActionType.

 TokenizeRequest request = new TokenizeRequest();
 request.setSiperianObjectUid( SiperianObjectType.PACKAGE.makeUid( "ADDRESS_UPDATE" ) );
 RecordKey recordKey = new RecordKey();
 recordKey.setRowid("782");
 request.setRecordKey( recordKey );
 request.setActionType("Insert");
 TokenizeResponse response = (TokenizeResponse) sipClient.process(request);