Overview

Before getting started with the sample, here is some brief general information about events. There is more detailed information about events available in the IBM InfoCenter for IBM Business Process Manager v751.

The events (timer, message, exception events):
You can include the following types of events in your IBM BPM Business Process Definitions (BPDs):

• Start event - Use to model the start of a process or a linked process. A Start event is automatically included each time you create a business process definition (BPD). A BPD can include multiple Start events (one Start event with a implementation of None and multiple Start events with an implementation of Message) if you need to be able to start the process more than one way.
• Intermediate event - Intermediate events can be attached to activities within your BPDs or they can be included in the process flow, connected with sequence lines.
• End event - Use to model the end of a process. An End event is automatically included each time you create a BPD.

The event gateway:

An event gateway represents a branching point in a process where the alternative paths that follow the gateway are based on events that occur, rather than the evaluation of expressions using process data (as with an exclusive or inclusive gateway). A specific event, usually the receipt of a message, determines the path that will be taken. An event gateway represents a single point of behavior that is spread out across multiple process components connected by sequence flow. The components that can directly follow an event gateway (connected by a single sequence flow) include the following types of events:

• Intermediate message event (receiving)
• Intermediate timer event

When creating an event gateway, you must connect at least two intermediate events to the gateway. And, when connected to an event gateway, an intermediate event is not allowed to have additional incoming sequence flow.

The event subprocess:
Event subprocesses are subprocesses that are triggered by an event that occurs in the parent process. Event subprocesses are like other subprocesses in that they are contained within a parent process, and are not reusable outside of that process. They are unlike other subprocesses in that they are not connected to other activities in the process by incoming or outgoing connections, and are only triggered by events that occur in the process or its subprocesses.

In this sample we will exploit all these new events, as shown here:




The Run the sample section will describe what to do to see these various events in action.