For monitoring performance, you can use the administrative console to select service
components for monitoring and view performance measurements. This example shows the use of the
console to monitor performance statistics.
About this task
You will use the business rules sample application for this scenario, where you will
monitor all three of the performance statistics: successes, failures, and response times. You should
have the web page containing this application already open; keep it open, because you will be
running the sample several times after you begin monitoring. Ensure that you have already run the
sample at least once, which causes it to appear in the list of functions that you can select to
monitor.
Procedure
-
Open the administrative console.
-
Select the cluster or server to monitor.
- To monitor a cluster, click .
- To monitor a single server, click .
-
Click the Runtime tab.
-
Under Performance, click Performance Monitoring Infrastructure.
-
Select Custom.
-
Expand .
-
Select _calculateDiscount.
-
Select the check boxes next to BadRequests, GoodRequests, and ResponseTime.
-
Click Enable.
-
In the navigation pane, click .
-
Select the check box next to server_name, then click Start
Monitoring.
-
Click server_name.
-
Expand .
-
Select the check box next to _calculateDiscount.
Results
You should now see a blank graph, and underneath that the names and values for the three
statistics. Select the check boxes next to the statistic names, if they are not already checked. The
PMI is now ready to publish performance data for the selected event, and the Tivoli® Performance Viewer is ready to present the results. Run the
business rules sample application several times, and then watch the performance viewer as it
periodically refreshes. Notice that there are now lines on the graph, representing the cumulative
number of successful requests and the average response time for each successful request. You can
also see the values next to the name for each statistic. The line for the number of successes should
continue to rise as you perform additional invocations of the sample, while the response time line
should level off after a few refreshes.
After you have completed this example, you should
understand how IBM® Business Automation Workflow implements
performance monitoring of service components. You should know how to select service components for
monitoring, and how the performance statistics are calculated. You will also be able to start the
performance monitors, and view the performance measurements for your applications as they are being
used.
What to do next
Performance monitoring can tax system resources; therefore, after you have completed this
task you should stop the monitors. To do this, click the Tivoli Performance Viewer link, select both the node and the server, and press Stop
Monitoring.