< Previous | Next >

Lesson 1.5: Testing the monitor model

Before you begin, you must complete Lesson 1.4: Deploying the monitor model.

Creating business monitoring spaces on Business Space

  1. On the Server tab, right-click on the monitor server, then click Business Space.
  2. Login to the Business Space using a valid dashboard user ID and password. The main page of Business Space opens.
  3. Click Create a new Business Space.
  4. From the prompt menu, enter MonitorLimousines Space as the name of the business space. Since you want a business monitoring space, select From a template, and make sure that Business Monitoring is the selected template, then click OK.

Creating Instances widgets in the business monitoring space

  1. From the main page of Business Space, locate the MonitorLimousines Space in the list of spaces. Click MonitorLimousines Space to open that business space.
  2. In the MonitorLimousines Space, click New Page. The New Page prompt menu opens. Enter Trips as the name of your new page. Select an empty layout, then click OK. The Trips page is then created and becomes your current page.
  3. Click the Add Widgets pull-down menu, then Select on the Instances widget. Drag the Instances widget towards the upper left corner of the Trips page. Release the mouse and there will be an instance of the Instances widget on the page.
  4. Configure the Instances widget by clicking the down arrow located to the upper right corner of the widget. Click Configure:
  5. In the Configuration page, expand the MonitorLimousines monitor model, then select the Trip monitoring context definition. The metrics defined for Trip appear in the Available list to the right.
  6. Select which metric definitions from the Available list you want to be displayed in your Instances widget. For every instance of Trip, you will see the values of your selected metrics. Select the following metrics: limousine, pickUpAddress, pickUpScheduledTime, pickUpActualTime, dropOffAddress, dropOffScheduledTime, dropOffActualTime. You can select them one at a time. As you select one, click the right arrow to move you selected to the Selected list.
  7. Click Set As Default, then click OK.

Submitting event sequences with the Integrated Test Client

  1. From the Project Explorer tab, right-click on the MonitorLimousines monitor model name, then click Launch Integrated Test Client.
  2. The first tab of ITC called “Events” opens. This page has two sections. On the right side is the Create Test Script section.
  3. Before proceeding, click the Target Server tab located at the bottom of the ITC page. Make sure that the ITC is pointing to the right test server when it emits events. Under the Target server configuration section, make sure that the WebSphere Business Monitor Server where you deployed your monitor model is selected as in the following diagram. After you have configured the target server, return to the Events tab.
  4. Return to the Create test script section, then click Open to load the ITC script that contains the six events. Go to your workspace directory then select the SampleResources folder. Within that folder, select the Events for Limousines Part 1.xml file. Click Open. Note that a pause is included after every emission of an event.
  5. To start sending events, click Run Script. A new ITC console opens. It shows the progress of the script. It sends the first carDispatched event. Since a Pause command follows, you will see “Pausing..” in the ITC console after the event is emitted. You can see the results for this first event being updated in real time in the Instances widget.
  6. Click Run Script again to send the next event. You can check the Instances widget again. You can force a refresh of the contents of the Instances widget by clicking on the arrow at the upper right side of the widget title bar, then click Refresh.
  7. Repeat the previous step until all six events are emitted. The ITC console displays a message informing you of the end of the script when the script is done.

Viewing results from the Instances widget

In this Business Space, there are two instances of the Trip monitoring context definition. For each instance, the values of the metrics you chose are also displayed. As you added your events, the monitor model consumed the events, created the instances, and mapped the values from the events to the metrics. The dashboard also shows that the events are filtered correctly and the instances were correlated with the events.
To retest your monitor model you must clear the instance data from your Instances view. You can do this by removing your monitor model from the monitor server, then publishing it again to the same monitor server. The steps for removing a monitor model are described in the next tutorial lesson.

Removing the monitor model from the server

  1. Click the Servers tab.
  2. Right-click the monitor test server where your monitor model is published, then click the Add and Remove Projects … option.
  3. From the Add and Remove Projects window, select MonitorLimousinesApplication, then click Remove.
  4. Click Finish. When a dialog informs you that the project is being removed from the server, click OK. The MonitorLimousinesApplication disappears from the Servers tab.

Lesson checkpoint

You have completed the tutorial. To review what you have learned, see the tutorial summary: Summary.