EAI Siebel Adapter - Handling Each Record as a Transction

The EAI Siebel Adapter business service is probably the most important (and most widely adopted) EAI business service. It is well documented and most of the EAI professionals know how to handle it.

One thing you come across early is how EAI Siebel Adapter handles the input SiebelMessage objects. Let's consider an example with a SiebelMessage which includes 10 accounts. If we execute for example the upsert method and account number 8 has an invalid value in the status field (picklist errror) then no record is inserted or updated at all.

In other terms, a SiebelMessage is considered a "transaction" and EAI Siebel Adapter "rolls back" all changes made to records when some error occurs during processing of the SiebelMessage.

Sometimes this behaviour is not desirable. For example, you want to send in a batch of updates to Siebel and just want to be notified which records where processed and which not.

The ObjectLevelTransactions input argument is the solution to that problem. If we set it to "True" (and do the same with the StatusObject parameter), EAI Siebel Adapter will treat each single object in the SiebelMessage as a transaction.

It will also return the status object which we can parse in order to find out whether there were any problematic records. They will have an accompanying ErrorMessage property with the error message received during the operation.

Have a nice day