Example of a Parent Node Using an Update Operation

This example demonstrates the effects of records after an update operation is performed. the following table is a high level representation of a parent node using the update operation of the Execute method.

Note: The examples represented by the following table, second table in this topic and the fourth table in this topic basically have the same result. However, as reflected in the third table in this topic, the children do not automatically inherit Update if it is only set for the root.

Record in Database	Integration Object Instance	Record After Execute Operation
Account1 Contact0 Contact1	Account1 operation=update Contact1 Contact2	Account1 Contact1 Contact2

In this case, if a record matching Account1 exists in the database, then the EAI Siebel Adapter updates that specific record. If no matching account exists, then the result of the EAI Siebel Adapter is an error with this message:

Insert operation on integration component 'Account' failed because a matching record 
in business component 'Account' with search specification '[Name] = "GenComm" AND 
[Location] = "San Francisco, CA"' was found (SBL-EAI-04383)

For all the matching child contacts, the update operation is inherited. Therefore, if the child exists, then it will be updated. If the child does not exist, then it is inserted. For child contacts that exist in the database but do not match the integration object instance, they will be deleted. These might be child contacts created or associated with the Account by default.

This is very similar to the previous example, except that the record must exist in the database.