WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Application recovery

Application recovery refers to the recovery and resolution of inflight business transactions.

If your system suffers a failure, (a power outage for example), there would be many active transactions impacted, and all of them at various stages of the process flow. We have describe how the system handles these transactions as part of its recovery process.

In order to have a completely successful application recovery, the applications themselves must observe the preventive practices provided.

If the applications are not developed with best practices, with recovery and transaction scope in mind, then application recovery will likely not be completely successful.

A poorly designed or "untuned" system or application will inevitably leave a percentage of inflight transactions or processes that remain unresolved after the rest of the application starts processing new events. This statement is true for not only WebSphere® ESB but for all J2EE applications and application servers.
Note: The phrase "untuned" refers to a solution that uses default settings for all components without regard to performance considerations or error handling practices.

Unresolved events can come in different forms such as processes that stay in a running state or failed events that cannot be resubmitted. A post recovery analysis of these events is required to determine what changes are necessary within the application for a full recovery. These changes should be found during the execution of the comprehensive functional and system test plan.


concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/crec_application_recovery.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).