Skip to main content

Development

Transaction usage in Oracle Service Bus

Scenario: As we all know transaction concept in DB means several operations commit together, one step failed, it will roll back all the changes in DB. So this kind of technology could be used in Oracle Service Bus too.

 OSB service has request pipeline and response pipeline, When an OSB  proxy service consume a file from a folder path or consume a message from queue, if we enable the transaction settings for a proxy, OSB will make sure the whole workflow (request pipeline and response pipeline) successfully finished, if any of step failed during the workflow process, then the file/message will not be consumed by OSB server, it will be always there try and try again. Definitely you can set the retry count or delivery failed limit settings to prevent the server try to process instances over and over again. But Transaction settings provided you a reliable delivery solution for your business.

You could just enable “Transaction Required” options in OSB proxy if you needed.

10

Tags

Thoughts on “Transaction usage in Oracle Service Bus”

  1. Hi,I have a service which is atomic transaction, So when we are invoking atomic transactional service over proxy service, we are getting the error “Transaction context is required”, As for same we added policy file of AT in business and proxy service but again we are getting same error.
    please help me

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Categories
Follow Us
TwitterLinkedinFacebookYoutubeInstagram