Update the business process to emit monitor events

Before you create the monitor model, you must select the events that WebSphere^® Process Server will generate. WebSphere Business Monitor will use the generated events to monitor the process. Events need to emitted for decisions and invocation actions in the process. The process representation in WebSphere Integration Developer is BPEL. WebSphere Business Modeler decisions become BPEL links in WebSphere Integration Developer. You need to configure to emit events for the parallel activity BPEL element (OrderHandlingFuture1_Flow) to emit events for the links.

The business object date (order form data) can be accessed from several events including SCA ENTRY events, receive activity (EXIT) events, or invoke activity (ENTRY) events. You could use the SCA events, but then the auto-generated monitor model would not have a trigger to terminate monitoring that process instance; thus, this option requires you to add the termination trigger. You could also use the receive activity EXIT event. In this tutorial you will use the first invoke activity (ENTRY) in the process to access the order form data.

In the Business Integration view, select ClipsAndTacksF1 > Business Logic > Processes > processes\orderhandlingfuture1 and then double-click OrderHandlingFuture1 to open the BPEL editor.
Click the white background of the process. Ensure that you click outside of the parallel activity (OrderHandlingFuture1_Flow) element, which is the large rectangle that contains elements such as receive, human tasks, and invoke elements.
Click the Properties tab under the BPEL diagram, and then click the Event Monitor tab (if you have to scroll down, you must scroll from the left side, not the right side). For a production application, you would want to select the individual events to emit, but for simplicity in this tutorial, select All.
Click inside the OrderHandlingFuture1_Flow parallel activity element, and then click All on the Event Monitor tab.
Similarly, select All events for each of the four invoke activities and the two human tasks. You will select each of these activities in the BPEL diagram and then update the Event Monitor tab. Update the following activities to emit All events:
- Check Order Handling Policy for Automatic Approval
- Check Customer Account Status
- Review Order
- Ship Order to Customer
- Cancel Order and Send Notification
- Update Order Database
Save your work. Review each of the four invoke activities, the two human tasks, the flow, and the process to ensure the Event Monitor is set to All. Events that are not being emitted can be difficult to detect and debug.

The following screen capture shows the yellow flag icons that indicate the events that are selected to be emitted for the components. There are flags on each of the six activities. The flag in the upper left is for the flow. The flag in the upper right is for the process. There are eight flags in total.