From DeveloperWorks, Error handling in WebSphere Process Server, Part 1: Developing an error handling strategy

With the emergence of service oriented solutions, we’ve seen a sharp rise in developer productivity. Developers are empowered with a new found freedom of service construction and reuse. However, with this freedom comes an increased exposure to inconsistent service definitions. These inconsistencies expose weaknesses in error handling and system recovery across the solution. Along with the proper governance controls, IT organizations need to define and enforce the proper error handling strategies tailored for solution recovery. Part 1 of this article series introduces the topic of error handling strategies and highlights key concepts and objectives for developing a strategy

This is an article written by my former colleagues at IBM. It goes into depth about the part of your process that you likely left until the last moment: What to do when something goes wrong. I recommend it as required reading for any WebSphere Integration Developer user.

Related Posts

• WebSphere Default Messaging (SIBus) and WebService Error Handling
• Handling unmodeled faults within WebSphere Process Server V6.1
• Asynchronous replication of WebSphere Process Server and WebSphere Enterprise Service Bus for disaster recovery environments
• WebSphere Integration Developer - Namespaces Cannot Span Projects
• Asynchronous SCA One-Way Operations And How To Recover

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.