IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Debugging monitor models
Sending events to the debugger
You can send events to the monitor model debugger as you would normally send events to be monitored. You do not need to generate Java EE projects or add the projects to the server.
Initially, the status of the monitor model in the debugger (shown in the upper left pane) is waiting for inbound event. After an event is sent, the status changes to <model name>(running).
The following tools are just a few of the numerous tools that you can use to send events:
- Integrated Test Client
- The Integrated Test Client is intended for creating and sending events to your monitor model. See Using the Integrated Test Client to send events.
- Business Process Choreographer Explorer
- The Business Process Choreographer Explorer is a web application that implements a generic web user interface for interacting with business processes and human tasks. For additional information, see "Launching the Business Process Choreographer Explorer".
- Common Base Event emission tools
- There are many types of applications that emit events. You can use any Common Base Event emission tool that emits the expected events.
- Applications that emit events
- You can use any application that can emit the expected events.
To use the Integrated Test Client to send events:
Procedure
- Click the Integrated Test
Client tab behind the Debug Source view. (If the tab is not there, switch to the Business Monitoring perspective, right-click
the monitor model in the Project Explorer view, and click Launch
Integrated Test Client.)
- Add test events and commands to the script as required. The Integrated Test Client panel has two sections, the Add Values to Events section and the Create Test Script section. In the Add Values to Events section, you can select, modify, and add events from the monitor model to the test script. (A script is a series of commands that perform a particular function and are interpreted as they are run.) In the Create Test Script section, you can add and edit commands, rearrange events and commands, and import events.
- To create new events in the Integrated Test Client, see Create sample events for testing.
- To import events when the script runs, either from an existing file or from the Common Event Infrastructure database, or from previously recorded events, see Importing events for testing.
- To add other commands to the test script, see Create or modifying the test script.
- To run the script and send the events, click Run Script
.
Results
Initially, the status of the monitor model in the debugger (shown in the upper left pane) is waiting for inbound event. After an event is sent, the status changes to <model name>(running). When the debugger stops at the first breakpoint, the status changes to <model name>(suspended).Incoming events are put into the input queue and processed by the debugger one at a time. See "Working with event queues" for more information.