Question & Answer
Question
What is the Commit boundary of Integration Servers?
Answer
Consider a
scenario with a service definition as follows:
JMS Component (A) -> Business Logic -> JMS Component
(B)
The attempt is to answer
the question: What is the commit boundary of the transaction in such a service
definition, be it a standalone service or a service with an Action/On Success
event with “Time to Live” set to
“0”
Q: When does the
transaction normally commit after reading a
message?
A: The JMS message will
be committed after execution of any business logic. A message to be reprocessed
will be persisted in the database for manual verification, if the business
logic throws an exception. One can correct and reprocess such messages from the
Exception Console. The message will then be committed and removed from the JMS
Queue. The message will be rolled back to JMS queue only if - Business logic
throws an exception AND the Sterling application fails to persist the message
in database for any reasons like Lost Connection/No space in tablespace
etc..
Q: When does the
transaction normally commit while posting a
message?
A: The application
behavior is dependent on the exposed configuration “Commit of this
message depends on the Parent Transaction’ checkbox.
This checkbox ensures
that the message is ‘Rolled back’ correctly if parent transaction
fails.
E.g.: On Create
Order > Before Create Order user exist message is posted to JMS
queue.
However, Create
Order process fails at the end. (Maybe the configured ON_SUCCESS event
fails)
This checkbox will ensure
that the message is not committed. In other words message will be committed
only if parent transaction (Create Order in this example) is successful.
In the same example, if
this flag is not checked then the message will be committed even if Create
Order -> ON_ SUCCESS event fails.
[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Historical Number
FAQ4070
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21518680