Business event processing with WebSphere Business Events V6.1

An end-to-end example using Design and Design Data components

This article uses an end-to-end scenario to explain how IBM® WebSphere® Business Events supports application development based on business event processing to solve a business problem. In the process, you will see how to use the Design and Design Data components of WebSphere Business Events to define touchpoints, result events, intermediate objects, data sources, filters, interaction sets, and event flows to implement event correlation as a business user. You will see how to deploy these assets to a repository, run the application, and test the whole scenario. This content is part of the IBM Business Process Management Journal.

Share:

He Wen (hewwen@cn.ibm.com), Software Engineer, IBM

He Wen is a software engineer at IBM China Development Lab in Beijing, China. She works on developing business event processing applications with IBM WebSphere Business Events in an insurance reference implementation project. Her interests include Event-Driven Architecture, Domain Analysis, and SOA tooling development. You can reach her at hewwen@cn.ibm.com.



Huang Ruo Bo (huangrb@cn.ibm.com), Software Engineer and Manager, SOA Design Center, IBM

Huang Ruo Bo is a manager at IBM China Development Lab in Beijing, China. He has rich experience in J2EE projects, including e-Commerce, Grid, cluster management and SOA.



04 December 2008

Also available in Chinese

Introduction

IBM WebSphere Business Events provides easy-to-use graphical authoring tools that you can use for defining business policies and logic that respond to business events and patterns, and that initiate appropriate business actions. Business policies describe how your system will react to events occurring or not occurring in certain combinations or at certain times. They also enable you to detect, analyze, and dynamically react to simple and complex relationships between people, events, and information. In WebSphere Business Events, business policies are very readable for non-technical users and closely follow the rules as described in plain language.

Business events can come from a variety of systems and applications, which may or may not be connected. WebSphere Business Events can correlate and identify patterns from all different sources, and then either generate actions that are consumed by external systems, or generate new events that are sent to WebSphere Business Events.

Figure 1 illustrates the WebSphere Business Events run time architecture. The WebSphere Business Events run time server manages the real-time business event coordination defined during application development:

  • When an event occurs in a touchpoint (a complex pattern of events and actions, such as an e-mail connection, SOAP connection, and so on) that potentially requires one or more actions in another touchpoint, the relevant data is passed via the touchpoint’s connector to the JMS message queue.
  • The run time server retrieves the message from the JMS queue and populates the appropriate intermediate objects with the values contained in the event payload.
  • The run time server’s interaction set processor parses the event, identifies the interaction sets that reference the event, determines whether filters exist, and evaluates which action to take for further evaluation.
  • The run time server passes the relevant data associated with the action from the intermediate object as an action payload to the outbound JMS message queue.
  • The history for events, actions, and filters used in the interaction set evaluation are stored in a history DBMS.
Figure 1. WebSphere Business Event run time architecture
Figure 1. WebSphere Business Event run time architecture

Sample scenario

To illustrate how to develop a business event processing application using WebSphere Business Events, let’s look at a sample insurance company scenario. Here, you want to leverage SOA technologies to analyze the business modeling so you can streamline and optimize the business process. We’ll take the Modify Customer Information business process in the Customer Relationship Management system as example (Figure 2). This business process is implemented by the IBM FileNet® P8 process engine for enterprise content management, which is primarily applied in the finance industry.

Figure 2. Modify Customer Information business process
Figure 2. Modify Customer Information business process

At a high level, the business process is modeled in this way:

  • A customer submits a request to modify their customer information in the Customer Relationship Management system.
  • The administrator reviews the information to determine whether the modification information provided by customer is sufficient.
  • If the information is sufficient, the administrator approves the request and modifies the information.
  • If the information is deficient, a message is sent to initiate another business process, called Notify Customer, which sends a notification to the customer using the customer’s preferred method of contact.
  • Upon receiving the notification request, the customer launches the process to provide the additional information.
  • The administrator reviews the information again. The process is repeated to confirm and finalize this process until the information is sufficient.

In order to decouple the relationship between business processes while keeping them correlated with each other, you can integrate the FileNet P8 platform with WebSphere Business Events to implement a business event-driven architecture that improves flexibility and extensibility. FileNet is responsible for implementing highly agile and content-centric business processes, while WebSphere Business Events is responsible for analyzing and managing business events initiated from business processes, providing an easy-to-use user interface to define business rules. The architecture overview is shown in Figure 3, in which you can see that FileNet and WebSphere Business Events are integrated with each other through messaging middleware.

Figure 3. Architectural design overview
Figure 3. Architectural design overview

When the administrator determines that the information is deficient in the sample scenario, the business process goes to the Send Message branch of the process. In this step, FileNet will invoke a Java™ component to send a JMS message using IBM WebSphere MQ V6.0 to initiate a business event. WebSphere Business Events receives this business event and processes the additional information request notification to the customer based on business rules. The notification request might be sent by e-mail, a short message service, or another method as indicated by the customer preferences. Ultimately, WebSphere Business Events determines which action to perform.

Integrating FileNet with WebSphere Business Events for implementing a business event driven application enables separating business process logic from different kinds of business event processing, and improves enterprise agility.

Requirement analysis

When the process initiates a business event by sending a JMS message, WebSphere Business Events automatically detects the arrival of the JMS message and identifies it as a kind of business event that was defined at design time. At run time, WebSphere Business Events evaluates and determines which action should be performed based on business rules.

WebSphere Business Events can also delay some actions. In this scenario, WebSphere Business Events rechecks the status of the customer after 7 days to see if the customer has received and responded to the notification. If the customer has not responded in the scheduled time, WebSphere Business Events will notify the administrator.

The worksheet and result of the requirements analysis is shown in Listing 1.

Listing 1. Design worksheet and analysis results
Touchpoint
-	Customer Relationship Management
-	Notify system.
Business event
-	Request Additional Info (Message queue connection): include customer’s basic 
	information, such as CustomerID.
Action
-	Notify customer by e-mail (E-mail connection): include customer’s e-mail 
	information, such as Sender, Receiver, SMTP server, and so on.
-	Notify customer by phone (SOAP connection): include customer’s phone information, 
	such as phone number.
-	Notify customer manager (File system connection).
-	Recheck status after 7 days (Connector): include customer’s basic information.
Result event
-	Recheck: Result of action “Recheck status after 7 days.”
Filter
-	Contact Preference is E-mail
-	Contact Preference is Phone
-	Contact Preference is Empty
-	Customer has no response
Interaction Sets
-	Respond to Request Additional Info
·	If customer’s preferred contact method is e-mail, then run the action Notify 
	customer by e-mail.
·  If customer’s preferred contact method is phone, then run the action Notify 
   customer by phone.
·  If customer’s preferred contact method is empty, run the action Notify 
   customer manager.
   ·  Always run the action “Recheck status after 7 days.”

The short message service interface is described as shown in Figure 4.

Figure 4. Interface definition for SMS Web service
Figure 4. Interface definition for SMS Web service

Using WebSphere Business Event: Design Data

This section explains how you can build a data model for business event processing using the WebSphere Business Event: Design Data tool. Design Data is a Windows®-based client/server application, designed to be used by IT technicians, that supports the definition of the metadata layer required for business event processing. Here, you will use the Design Data tool to create the building blocks for the sample application, which include touchpoints, events, actions, intermediate objects, and data sources.

1. Define touchpoint

Touchpoints represent business systems that send events and receive actions. WebSphere Business Events enables real-time event coordination between touchpoints.

To define a touchpoint called "Customer Relationship Management:"

  1. From the Windows start menu, select Programs => IBM WebSphere Business Events v6.1 => Design Data.
  2. Create a new project named Notify Customer Project.
  3. From the menu, select Insert =>Touchpoint.... Enter the name Customer Relationship Management, and click OK.
  4. Repeat step 3 to create a touchpoint called Notify System.

When you are finished, you should have two touchpoints, as shown in Figure 5.

Figure 5. Define touchpoints
Figure 5. Define touchpoints

2. Define message queue event connection

An event identifies an activity in a touchpoint that initiates an activity within WebSphere Business Events. An event is composed of one or more event objects, which are sets of defined data fields.

To define an event called "Request Additional Info" under the Customer Relationship Management touchpoint:

  1. Click the Touchpoints section to expand it. Right-click the Customer Relationship Management touchpoint, and select Insert Event => Normal.
  2. Enter the name Request Additional Info, and click OK.
  3. To configure the embedded connector for this event:
    1. Right-click the Request Additional Info event, and select Event Properties....
    2. Click the Connection tab, select Message Queue Connection and click Configuration.
    3. In the Message Queue Event Connection dialog (Figure 6), select Connector Packet for Format and JMS Queue for queue Type, and then enter SendQueue for queue Name. In this scenario, adopt WebSphere MQ V6.1 as the JMS provider for applications and configure related resources in WebSphere MQ as shown in Table 1.
      Figure 6. Message Queue Event Connection dialog
      Figure 6. Message Queue Event Connection dialog

      Table 1. JMS provider configuration in WebSphere MQ

      Field nameValue
      JNDI initial context factorycom.sun.jndi.fscontext.RefFSContextFactory
      JNDI provider URLfile:///C:/JNDI-Directory
      Queue typeJMS queue
      Queue nameSendQueue
      Queue managerInsuranceQM
      Queue connection factoryQueueConnectionFactory
    4. Click the Provider... button. Enter or select the information in Table 1 on the Provider dialog (Figure 7).
      Figure 7. Provider Configuration dialog
      Figure 7. Provider Configuration dialog
  4. Right-click the Request Additional Info event, and select Insert Event Object => Blank....
  5. Enter the name Request Additional Info, and click OK.
  6. To define the data fields for the event object, right-click the Request Additional Info event object, then select Insert Event Object Field... to insert a new data field.
  7. When the Insert Field dialog opens, enter the information in Figure 8, then click OK.
    Figure 8. Event object field definition
    Figure 8. Event object field definition

3. Define e-mail action connection

An action identifies an activity that will occur in a touchpoint when one or more interaction blocks within WebSphere Business Events evaluate to true.

To define an action called "Notify Customer by e-mail:"

  1. Click the Touchpoints section to expand it. Right-click the Notify System touchpoint, and select Insert Action => Normal.
  2. Enter the name Notify Customer by e-mail, and click OK.
  3. To configure the embedded connector for this action:
    1. Right-click the Notify Customer by e-mail action, and select Action Properties....
    2. Click the Connection tab, select Email Connection, and click Configuration.
    3. On the Email Action Connection dialog (Figure 9), select Text Email for Format. Enter the appropriate e-mail information, such as Subject, To, From, and so on. Click OK.
      Figure 9. Email Action Connection dialog
      Figure 9. Email Action Connection dialog
  4. Right-click the Notify Customer by e-mail action, and select Insert Action Object => Template....
  5. On the file selection dialog that displays, select the %WBE_root%/DirectorData/Template/ActionObject/emailConnection folder and then select the _Email.xml file. The predefined _Email action object will be imported into the project (Figure 10).
    Figure 10. _Email action object fields

    The detailed information of each action object field is shown in Table 2.

    Table 2. Email Action Object Fields

    NameData type
    ToString
    FromString
    ReplyString
    CCString
    BCCString
    SubjectString
    BodyString

4. Define SOAP action connection

To define an action called Notify Customer by Phone:

  1. Select Insert => WSDL => From File.... On the file selection dialog. Select the WSDL file that describes the short message service. The WSDL file will then be transformed to touchpoint, action, and result events in the Touchpoint section, as shown in Figure 11.
    Figure 11. SMS Web service import
    Figure 11. SMS Web service import
  2. To configure the embedded connector for this action:
    1. Right-click the sendXML action, and select Action Properties....
    2. Click the Connection tab, select SOAP Connection, then click Configure....
    3. On the SOAP Connections dialog (Figure 12), click the Configure... button. Enter the configure server information shown in Figure 13.
      Figure 12. SOAP Action Connection dialog
      Figure 12. SOAP Action Connection dialog
      Figure 13. Server configuration
      Figure 13. Server configuration

5. Define file system action connection

To define an action called "Notify Customer by Customer Manager:"

  1. Click the Touchpoints section to expand it. Right-click the Notify System touchpoint, and click Insert Action => Normal.
  2. Enter the name Notify Customer by Customer Manager, and click OK.
  3. To configure the embedded connector for this action:
    1. Right-click the Notify Customer by Customer Manager action, and click Action Properties.
    2. Click the Connection tab, select File System Connection, and click Configuration.
    3. On the File System Connection dialog, select Connector Packet for Format.
    4. In the Server section, click the Configure button. Enter the directory and file pattern data as shown in Figure 15. The generated file will be placed in the specific directory.
      Figure 14. File Action Connection dialog
      Figure 14. File Action Connection dialog
      Figure 15. Server configuration
      Figure 15. Server configuration

6. Define result event

A result event is a set of objects that can be returned from a touchpoint by a connector as the result of an action that is sent to that touchpoint. Results can be used to sequence actions. An action sent to a touchpoint will return a result that can be evaluated as a result event. This event will in turn generate one or more actions that will return their own results, which can then be evaluated by other results.

To define a result event called "Recheck status after 7 days:"

  1. Define an action called Recheck status after 7 days under the Customer Relationship Management touchpoint. Follow the instructions above to Define e-mail action connection.
  2. Right-click the Recheck status after 7 days action and select Insert Event => Result of this Action.
  3. On the Insert Result dialog, click OK. The result event will be generated automatically.
  4. Rename this result event Recheck.

Figure 16 shows shows a high level overview of the Touchpoints section after all events, actions, and touchpoints have been defined.

Figure 16. Touchpoints section overview
Figure 16. Touchpoints section overview

7. Define data source

WebSphere Business Events uses data from two primary sources. The data can either come from the touchpoint systems, or it can be retrieved from outside sources, like relational databases, as needed. Data that is to be retrieved from an outside source is defined to WebSphere Business Events: Design Data as a data source.

Before you insert metadata from a data source into WebSphere Business Events: Design Data, you need to configure a connection to the source using the Windows ODBC Data Source Administrator (see Resources). Figure 17 shows how to insert a hosted database as a data source.

Figure 17. Insert hosted database
Figure 17. Insert hosted database

After adding the data source into your workspace, all tables referenced by the ODBC source will be pulled into the project. Figure 18 shows the Customer table that will be used to define an intermediate object.

Figure 18. Customer table in the data source
Figure 18. Customer table in the data source

8. Define intermediate object

An intermediate object is a conceptual representation of a business object.

To define the "Customer" intermediate object:

  1. Select Insert => Intermediate Object => Blank..., and enter the name Customer. Click OK.
  2. Right-click the Customer intermediate object, then select Insert Intermediate Object Field... to insert a new data field.
  3. On the Insert Field dialog, enter the information for the first field listed in Table 3 and click OK. Repeat for the remaining data fields.

    Table 3. Customer intermediate object fields

    NameData type
    CustomerIDString
    FirstNameString
    LastNameString
    PreferredContactMethodString
    EmailString
    AddressString
    PhoneNumberString
  4. To map a data field in the Request Additional Info event to a data field in the Customer intermediate object:
    1. Select the Intermediate Object section and expand it, then click the Customer intermediate object.
    2. Select the Touchpoints section and expand it, then click the Request Additional Info event object.
    3. Drag the CustomerID data field in the Customer intermediate object to the CustomerID data field in the Request Additional Info event object and drop it. The event object data field will be the field constructor of the intermediate object.

      Table 4. Change event object mapping to intermediate object fields

      Select Event Object fieldFor Intermediate Object field
      CustomerIDCustomerID
  5. To map a data field in the Customer Intermediate object to a data field in the _Email action object:
    1. Select the Intermediate Object section and expand it, then click the Customer intermediate object.
    2. Select the Touchpoints section and expand it, then click the _Email action object.
    3. Drag the Email data field in the Customer intermediate object to the To data field in the _Email action object and drop it. The intermediate object will be the field constructor of the action object, as shown in Figure 19.

      Table 5. Notify Customer by e-mail action mapping to intermediate object

      Select Action Object fieldFor Intermediate Object field
      EmailTo
      Figure 19. To data field configuration
      Figure 19. To data field configuration
  6. To define a data field in the _Email action object as a constant value:
    1. Select the Touchpoints section and expand it.
    2. Expand the Notify Customer by e-mail action under the Notify System touchpoint, and click the _Email action object.
    3. Click the Subject data field in the _Email section (Figure 20).
    4. Choose Constant Value from the Type definition checklist.
    5. Enter a value in the Expression text field. The Subject data field will be evaluated as the constant value.
      Figure 20. Subject data field configuration
      Figure 20. Subject data field configuration
  7. This is similar to defining a data field in the _Email action object as JavaScript. Figure 21 shows the Body data field configuration.
    Figure 21. Body data field configuration
    Figure 21. Body data field configuration

    This step maps the Notify Customer by phone and Notify Customer manager action objects to the Customer intermediate object.

    Table 6. Notify Customer by Phone action object mapping to intermediate object

    Select Action Object fieldFor Intermediate Object field
    PhoneNumberPhoneNumber

    Table 7. Notify Customer manager action object mapping to intermediate object

    Select Action Object fieldFor Intermediate Object field
    CustomerIDCustomerID
    PhoneNumberPhoneNumber
    EmailEmail
  8. To retrieve data from a data source using mapped keys for constructing an intermediate object:
    1. In the Intermediate Objects section, click Customer.
    2. In this scenario, the CustomerID intermediate object is defined as a mapped key referencing the CustomerID in the Customer table. The Key Option is Key Equal, which means that all rows in the Customer table where the value of CustomID equals the value of CustomerID (passed from an event object) will be retrieved when the fetch is performed. Figure 22 shows how to define key customerID.
      Figure 22. Define Key CustomerID
      Figure 22. Define Key CustomerID
    3. Repeat step b to define the other data fields that are retrieved by key customerID. Figure 23 shows how to define the other data fields.
      Figure 23. Define Other data fields
      Figure 23. Define Other data fields

Using WebSphere Business Event: Design

Recall the business logic that was defined in the Requirement Analysis section. When the administrator reviews the customer’s information and determines it is deficient for the Customer Relationship Management system, a business event to WebSphere Business Events is initiated through a message queue connection and evaluated as follows:

  1. If the customer’s preferred contact method is e-mail, then run the Notify customer by e-mail action.
  2. If the customer’s preferred contact method is phone, then run the Notify customer by phone action.
  3. If the customer’s preferred contact method is empty, then run the Notify customer manager action.
  4. Always run the Recheck status after 7 days action.

1. Define filter

To define the Contact Preference is Email filter:

  1. Select Start => Programs => IBM WebSphere Business Events v6.1 => Design to open the WebSphere Business Events: Design UI.
  2. Click the Filter button on the toolbar, and then rename the new filter to Contact Preference is Email.
  3. Right-click the filter and select Add a filter condition. The "and" condition will be generated.
  4. Click the operand? link on the left. Scroll down the list of available fields, then select PreferredContactMethod under Customer.
  5. Click operator?, click the StringOperator folder icon, and then select the Equals Ignoring Case operator.
  6. Click the edit icon next to the operand? on the right, and select Enter text. Type in the value Email.
  7. In the second filter condition, click the operand? link on the left and scroll down the list of available fields. Under Customer, click Email.
  8. Click operator? on the left side. Select the StringOperator folder icon, and select the Is Not Empty operator.

Figure 24 shows three filter definitions: Contact Preference is Email, Contact Preference is Phone, and Contact Preference is Empty.

Figure 24. Filter definition
Figure 24. Filter definition

2. Define interaction set

To define these interaction blocks in Respond to Request Additional Info:

  1. Click the Interaction Set button on the toolbar and rename it to Respond to Request Additional Info.
  2. Click event?, and select Request Additional Info event (Figure 25).
  3. Click action?, and select the Notify Customer by Email action (Figure 26).
  4. Click over the Request Additional Info interaction block to display the menu, then click Add a filter to display a new filter line.
  5. Click filter?, and choose Customer Preference is Email from the list of available filters.
  6. Click the interaction set to display a menu. Select Add an interaction block to define another two interaction blocks (Figure 27).

Figure 28 shows the overview of Respond to Request Additional Info and Respond to Recheck Interaction Sets.

Figure 25. Select Request Additional Info from available events
Figure 25. Select Request Additional Info from available events
Figure 26. Select Notify Customer by Email from available actions
Figure 26. Select Notify Customer by Email from available actions
Figure 27. Add an interaction block
Figure 27. Add an interaction block
Figure 28. Interaction sets definition
Figure 28. Interaction sets definition

3. Create event flow

An event flow diagram consists of interaction sets and business steps. Complex event relationships and synthetic events are also represented in an event flow diagram. To build a new event flow:

  1. Click the Event Flow button on the toolbar. A new event flow is added to the asset tree under the Event Flows subfolder.
  2. Expand Interaction Sets in the asset tree and drag Respond to Request Additional Info and Respond to Recheck to the edit workspace in the right side. A new event flow is automatically built (Figure 29). The Recheck status after 7 days action in the Respond to Request Additional Info interaction set is a Recheck result event in the other interaction set, Respond to Recheck.
    Figure 29. Event flow
    Figure 29. Event flow

Using the repository

The repository is a shared, secured location that contains definitions of WebSphere Business Events assets. Assets defined in WebSphere Business Events: Design Data and WebSphere Business Events: Design must be stored in the Repository in order to be available to WebSphere Business Events at run time.

You can log in to the Repository (Figure 30) and submit all the definitions that you previously defined. Figure 31 shows that all of the assets have been loaded into the Repository.

Figure 30. Repository login panel
Figure 30. Repository login panel
Figure 31. Assets loaded into the Repository
Figure 31. Assets loaded into the Repository

Running the application

Because the application references an Apache Derby database, you must start the Derby Network Server before running the application.

Figure 32. Run command startNetworkServer.bat
Figure 32. Run command startNetworkServer.bat

To run the application:

  1. Restart the WBERuntimeEAR application in the WebSphere Application Server administrative console.
  2. Start the connectors according to connectors.bat in the %WBE_home%\director\bin directory.
  3. Use WebSphere Business Events: Administration to view system activity. The WebSphere Business Events: Administration user interface is a browser-based application that lets you monitor and manage the WebSphere Business Events run time environment. Open a browser window, and navigate to http://localhost:9080/wbe/common/login.jsp (Figure 33).
    Figure 33. WebSphere Business Events console login
    Figure 33. WebSphere Business Events console login

    When you login to the console successfully, you can see the detailed touchpoints and associated events and actions that you defined at design time and submitted to the Repository.

    Figure 34. WebSphere Business Events: Administration
    Figure 34. WebSphere Business Events: Administration
  4. Switch to the user console in the Web browser and click Send Events in the menu bar. You can use the console to simulate JMS message sending and initiate the Request Additional Info event in the touchpoint.
  5. Enter a value in the CustomerID field. The event will simulate sending a JMS message to the Customer Relationship Management touchpoint. The Request Additional Info event will be initiated and the run time server will determine which actions to run based on the interaction sets.
    Figure 35. WebSphere Business Events: User Console
    Figure 35. WebSphere Business Events: User Console
  6. You can see the detailed error information at run time and debug it by reviewing the system log and event log. You can log in to WebSphere Business Events: Administration and select Event Log from the Monitor Systems menu (Figure 36). The event log information will display in the console.
    Figure 36. WebSphere Business Events: Administration
    Figure 36. WebSphere Business Events: Administration

Conclusion

This article introduced business event processing with IBM WebSphere Business Events V6.1 with a scenario that explained how to build a sample application, including requirement analysis and architecture design, and how to use WebSphere Business Events tools to implement it. In this article, you learned how to use WebSphere Business Events: Design Data to define touchpoints, complex patterns of events and actions, intermediate objects, and data source. You also learned how to use WebSphere Business Events: Design to define filter, interaction sets, and event flow. Finally, with the runtime environment you were able to deploy and test the whole scenario to make sure it works correctly.


Download

DescriptionNameSize
Sample code0812_wen_BPESample.zip5 KB

Resources

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

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

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



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.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

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

 


All information submitted is secure.

Dig deeper into WebSphere on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=355681
ArticleTitle=Business event processing with WebSphere Business Events V6.1
publish-date=12042008