IBM WebSphere Process Server Best Practices in Error Prevention Strategies and Solution Recovery

An IBM Redpaper publication

Note: This is publication is now archived. For reference only.

Published 29 December 2008

cover image

IBM Form #: REDP-4466-00
(92 pages)

More options


Rate and comment

Authors: Kent Below, Jeff Brent, Eric Herness

Abstract

IBM® WebSphere® Process Server and IBM WebSphere Enterprise Service Bus (ESB) are middleware servers that are optimized to enable the execution and management of business process management (BPM) and service-oriented architecture (SOA) solutions. They are built on the foundational capabilities of IBM WebSphere Application Server. Middleware systems execute under various conditions, not all of which are traditionally "good path" conditions. Many of the key features within these products are in place to deal with the uncertainty that can arise through what might appear to be normal operations.

The topic of system analysis and recovery is a broad topic, for which entire books have been written. This IBM Redpaper publication provides basic guidance on how to handle ordinary and extraordinary conditions that might arise. We base this paper on the assumption that you are familiar with the WebSphere Process Server and WebSphere ESB products, the basic architectural principles upon which they build, and the basic kinds of applications that they execute. We also assume that you have a base understanding of integration projects, planning, and implementations.

Unless otherwise specified, the information is relevant to all versions of WebSphere Process Server and WebSphere ESB starting with V6.1.0. Although you will find that most of the information is applicable to the V6.0.2 product line, the internal validation of IBM was conducted on a V6.1.0 WebSphere Process Server cell with the standard golden topology. Results and actions might vary slightly on releases prior to V6.1.0.

Table of contents

Chapter 1. WebSphere Process Server solution recovery
Chapter 2. Recovery patterns, anti-patterns, rules, and helpful ideas
Chapter 3. Preventive practices
Chapter 4. Where data goes when failures occur
Chapter 5. Recovery scenarios
Appendix A. Troubleshooting tips
Appendix B. Additional material

Others who read this publication also read

Follow IBM Redbooks

Follow IBM Redbooks