Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Select a language:

  • Close [x]
  • Close [x]

Managing failed flows using the Failed Event Manager API in WebSphere Process Server

Phani Madgula (mabalaji@in.ibm.com), Software Engineer, IBM
author image
Phani Madgula is currently working for WebSphere Process Server Support at the India Software Labs (ISL). He has 7 years of experience at IBM. He worked in various product teams, including WebSphere Application Server Community Edition, WebSphere Business Integration Adapters, and DB2. He has experience in developing JEE applications, product support, and database administration. He is an Oracle9i certified professional.
(An IBM developerWorks Contributing Author)
Ashok Poralu (asporalu@in.ibm.com), Software Engineer, IBM
Photo of Ashok Poralu
Ashok Poralu works for WebSphere Application Server Community Edition Support at the IBM India Software Lab (ISL). Prior to his current role, Ashok worked for the WebSphere Process Server and WebSphere Application Server support teams and handled many customer cases. He has 5 years of experience in the IT industry and worked on various application development and WebSphere product stack support teams.

Summary:  The Recovery component is an intriguing subject in WebSphere® Process Server because it provides a fundamental service that helps administrators re-initiate their failed flows. To provide this service, the Recovery component captures the request data and embeds it in a failed event and stores it inside the common database tables. The Failed Event Manager application in the administration console can be used to resubmit the failed events. However, developers or administrators prefer to have scripts or programs to automatically resubmit the failed events. This tutorial helps administrators of WebSphere Process Server to develop programs by selecting the specific list of failed events, modifying the respective business data, and resubmitting the modified failed events. The tutorial provides a sample application that uses the Failed Event Manager API.

Date:  02 Mar 2011
Level:  Intermediate
PDF:  A4 and Letter (524 KB | 22 pages)Get Adobe® Reader®

Activity:  13548 views
Comments:  

Introduction

The Recovery component in WebSphere Process Server (hereafter called Process Server) provides a useful service that stores the information about the failed flows in the system and helps administrators to reinitiate them once the problems are resolved. Whenever there is a ServiceRuntimeException in the request process flow, the Recovery component comes into play. At that time, the transaction is rolled back until the last asynchronous point. The request data is wrapped inside a failed event and saved inside the common database. Along with the request data, the failed event also contains more information about when and where the failed event was created. If the failed flow needs to be re-initiated, this information helps to start processing again from the point where it failed earlier.

You can use the Failed Event Manager application that comes out-of-the-box when Process Server is installed to view, modify request data, and resubmit the failed events. This application runs on the application cluster and is accessed through the admin console. However, administrators prefer to have the capability to write clients to retrieve specific failed events, view the data, modify the data, and then resubmit them. To write these custom clients, administrators have to use the Failed Event Manager API. In fact, the admin console uses the same API to provide the functionality.

In this tutorial

This tutorial discusses how to develop the custom Java™ applications to work with the failed events. It uses a sample application that contains a mediation flow and SCA components to illustrate generating the failed events and to use Java Server Pages to work with these failed events.

The tutorial is divided into the following sections:

Back to top

Prerequisites

  • You need a good understanding of Java and Java EE concepts.
  • You need hands-on experience with SCA programming, mediations, and WebSphere Process Server administration concepts and tools.

Back to top

System requirements

  • IBM® WebSphere Integration Developer V7.0.0.0 with Fixpack 3 and the Unit Test Environment

Back to top

Duration

3 hours

1 of 8 | Next

Comments

Back to top

Close [x]

Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Close [x]

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=629958
TutorialTitle=Managing failed flows using the Failed Event Manager API in WebSphere Process Server
publish-date=03022011
author1-email=mabalaji@in.ibm.com
author1-email-cc=dwu@us.ibm.com
author2-email=asporalu@in.ibm.com
author2-email-cc=dwu@us.ibm.com

Table of contents

1 of 8 | Next

Local resources

Tags

Help
Use the search field to find all types of content in My developerWorks with that tag.

Use the slider bar to see more or fewer tags.

Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere).

My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).

Use the search field to find all types of content in My developerWorks with that tag. Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere). My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).

 

Dig deeper into WebSphere on developerWorks

Try IBM PureSystems. No charge.

IBM PureSystems on a kaleideoscope background

Experience today!

Get started with the cloud-based trial and pattern development kit.

Share this page:

  • Close [x]

Follow developerWorks:

  • Close [x]