My Oracle Support Banner

BEHAVIOUR OF MQ RECEIVER (Doc ID 1064547.1)

Last updated on MARCH 01, 2018

Applies to:

Siebel Financial Services CRM - Version 8.0.0.2 SIA [20412] to 8.0.0.2 SIA [20412] [Release V8]
Siebel CRM - Version 8.0.0.1 SIA [20408] and later
Information in this document applies to any platform.


Goal

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?

Solution

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
Goal
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.