EAI Transaction Commit and JMS Receiver
(Doc ID 1460919.1)
Last updated on MARCH 01, 2018
Applies to:Siebel CRM - Version 188.8.131.52  and later
Information in this document applies to any platform.
We are implementing a Siebel 8.1 environment including an integration platform communicating via JMS queues.
In our scenario, we have a sales order and do an update on the sales order status via an integration object message placed in the queue. This message is computed by a workflow that calls EAI Siebel Adapter to write the data to the database.
Now we have the impression that although the success message is in the response queue, the data is not committed immediately to the database.
We could prove this by developing a testcase in SoapUI that places a message in a JMS queue (containing the update operation), and then straight after doing a query against the database. After placing the message in the queue, a response message is placed into a response queue, indicating that the operation is finished. But an sql query straight after receiving the response message shows that the database still holds the old value. Another sql query a little while after shows the uptodate value, whereas it was necessary to wait about 130ms.
We experimented with ObjectLevelTransaction and StatusObjects being used, but this also did not help. Furthermore we introduced the EAI Transaction Service, also with no change.
We tried for example with updates on Order Status, and also on product name in another testcase, in both cases we have the same result, it seems the data is not written into the DB immediately, although the queue transaction is finished. This is occurring on a clustered production-like environment with a DB RAC, but also on development environment whichout RAC.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document