Last updated on MARCH 02, 2017
Applies to:Siebel Financial Services CRM - Version 22.214.171.124 SIA  to 126.96.36.199 SIA  [Release V8]
Siebel CRM - Version 188.8.131.52 SIA  and later
Information in this document applies to any platform.
1) What is the expected behaviour from Siebel MQ Receiver if the parameter 'SiebelTransactions' set to 'True' and 'RollbackOnDispatchError' to 'False'?
To add to my initial question, how would Siebel behave if SiebelTransaction = false and rollbackondispatcherror = true?
2) If we set the rollbackondispatcherror = true and siebeltransaction = false, what would be the implications of this setting in case the w/f fails.
- Would the message be put back into queue if there is an error after the commit ? this could result in multiple inserts once the message is picked up again.
- at exactly what step of the w/f is the commit done by Siebel? Lets say i have a few update steps in a w/f along with a sub process which has an insert step. Is the commit done by Siebel w/f after each update or insert step or after each w/f completes or after the parent workflow completes?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms