executeMatchUpdate

Like executeMatch, executeMatchUpdate processes the system object based on the configuration defined for the Manager Service and associated runtime components. It is configured by the same runtime components as executeMatch. One of these two execute match methods should be used for inserting or updating a record in the database.

The primary difference between these two methods is that when executeMatchUpdate finds that an incoming record matches an existing record, only the changed data is updated. With executeMatch, the entire existing record is replaced by the incoming record. The executeMatchUpdate method differs from executeMatch in the following ways:

• If a partial record is received, executeMatchUpdate only updates fields whose values are different in the incoming record. Unless the clearFieldIndicator field is used, empty or null fields in the incoming record do not update existing values.

• The clearFieldIndicator field can be used to null out specific fields.

• Child objects in the existing record are not deleted if they are not present in the incoming record.

• Child objects in the existing record are updated if the same key field value is found in both the incoming and existing records.

• To allow a child object to be removed from the parent object when using executeMatchUpdate, a new “delete” method is added to each child object bean.

Syntax

MatchColResult executeMatchUpdate(SystemObjectbean systemObject)

Parameters

Returns

A match result object containing the results of the matching process.

Throws

• RemoteException

• ProcessingException

• UserException