Recovering from failed asynchronous SCA service invocations on WebSphere Process Server

From the developerWorks archives

Ivan Smirnov and Neha Dhawale

Date archived: May 14, 2019 | First published: January 16, 2008

Imagine this common scenario. You have a mission-critical Service Component Architecture (SCA) application running on IBM WebSphere Process Server. A message is sent to this application to invoke an asynchronous service, however, service invocation fails. What happens to the original message? What new messages are sent? How can the system recover from the failure? This article describes potential message routes and recovery scenarios. It explains how to configure the system to set up recovery, and it covers a wide range of SCA messaging options, including both WebSphere Default Messaging (JMS provider) and WebSphere MQ.

This article is primarily intended for administrators, operations personnel, and advanced support personnel involved in setting up and troubleshooting applications running under WebSphere Process Server. To get the most out of this article, you need intermediate to advanced skills in WebSphere MQ and WebSphere messaging, and intermediate skills in SCA and Enterprise Service Bus (ESB).

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

Zone=Business process management, WebSphere
ArticleTitle=Recovering from failed asynchronous SCA service invocations on WebSphere Process Server