108 Business Service Management Best Practices
Figure 4-15 Event setting
You also need to enable the forwarding setting. Either forward to IBM Tivoli
Enterprise Console or to IBM Tivoli Business Systems Manager directly using
Common Listener. We decided to use the interface to IBM Tivoli Enterprise
Console.
4.4.2 Detailed profile setting
In this section, we show the detailed settings of the Resource Models in our
Tmw2kProfiles objects. The settings are selected based on the monitoring need.
All these events are sent to IBM Tivoli Enterprise Console.
Apache Web Server monitoring
Apache Web Server monitoring provides the following functions:
򐂰 Makes sure that the process is always running; the operator needs to be
notified when the process is not running and cannot be started automatically.
򐂰 Counts the hit rate for reporting, then reports any exceptionally high hit rate.
򐂰 Reports excessive numbers of error requests, perhaps resulting from a Denial
of Service attack.
Chapter 4. Business Service Management sample implementation 109
We create the profile ITM_Apache_Pr with the content shown in Table 4-4.
Table 4-4 Monitoring resource models
WebSphere Application Server monitoring
WebSphere Application Server is a critical piece of the application. All the
transactions are handled there. The monitoring aim is to maximize the availability
and performance of the Web transaction. Therefore, the following monitoring is
performed:
򐂰 Monitor and log the status of the WebSphere Application Server
򐂰 Monitor and log the JVM memory usage to ensure that there is enough
storage available for the application
򐂰 Monitoring for DB2 connection contention
򐂰 Monitoring for number of HTTP sessions
The ITM_WAS_Pr profile that we define to address the WebSphere component
is summarized in Table 4-5 on page 110.
Note: Depending on the setup of your environment, you may want to have the
authentication fail if it is performed by the Web server; a typical
implementation performs authentication outside of the Web server itself.
Resouce model Indication and threshold Logging attribute
Apache_
Performance
Apache_THR_FailedLoginPerSec
5.000000
Apache_THR_ServerFailuresPerSec
5.000000
Apache_THR_FailedPagesPerSec
20.000000
Apache_THR_KBytesPerSec 70.000000
Apache_THR_RequestsPerSec
50.000000
Server.ServerName,WebSiteName
GWA_Server_failures_count
GWA_Failed_pages
GWA_Failed_connections_count
GWA_Hit_count
GWA_Requests_rate
GWA_Successful_login_count
GWA_Failed_login_count
GWA_Kbytes_rate
Apache_
WebSiteAvailability
N/A Server.ServerName,WebSiteName
GWA_Website_running
GWA_Website_stopped
Note: Our application runs as servlets, without EJB; therefore, we only use
the WebApplication monitor, without the EJB monitor or transaction
monitor.
110 Business Service Management Best Practices
Table 4-5 Monitoring resource models
DB2 monitoring
The database monitoring needs to ensure the performance of the database to
fulfill requests from the WebSphere Application Server. This result in the
following monitoring:
򐂰 Monitoring and logging of the availability of the DB2 instance
򐂰 Monitoring of the Buffer Pool hit ratio, one of the most important parameters
of DB2 performance
򐂰 Monitoring of the DB2 subsystem connection and tablespaces status
򐂰 Monitoring of locks and deadlocks
The DB2 monitoring details are shown in Table 4-6 on page 111.
Resouce model Indication and threshold Logging attributes
WebSphereAS_
ApplicationServer
_ 10
N/A Name,AdminServerName:
WebSphere_server_state_up
WebSphere_server_state_down
WebSphere_server_state_initializing
WebSphere_server_state_unknown
WebSphereAS_
JVMRuntime_10
WebSphereAS_high_JVMRuntime_
usedMemory 95.000000
Name,ApplicationServer.Name,Admin
Server.Name
Total_JVM_memory
Used_JVM_memory
WebSphereAS_
ThreadPool_10
WebSphereAS_high_ThreadPool_
activeThreads 95.000000
Name,AdminServer.Name,ApplicationS
erver.Name
Active_threads_to_pool_size_ratio
WebSphereAS_
WebApps_10
WebSphereAS_high_Servlet_errors
0.000000
WebSphereAS_high_Servlet_response
_time 750.000000
"Name,AdminServer.Name,Application
Server.Name,WebApplication.Name
Name,AdminServer.Name:
Servlet_request_rate
Average_servlet_response_time
Concurrent_servlet_requests
Servlet_error_rate
WebSphereAS_
HTTP_Sessions_
10
WebSphereAS_high_HTTPSessions_
liveSessions 1000
Name,ApplicationServer.Name,Admin
Server.Name
Live_servlet_sessions
Chapter 4. Business Service Management sample implementation 111
Table 4-6 Monitoring resource models
Windows server monitoring
For Windows server, we monitor the following attributes:
򐂰 CPU utilization
򐂰 Memory usage
򐂰 Free disk space
򐂰 Network card activity
The contents of the ITM_WinOS_Pr profile are shown in Table 4-7 on page 112.
Resouce model Indication and Threshold Parameters
DB2 Buffer Pools High_AvgPoolReadTime 200
High_AvgPoolWriteTime 200
Low_PctBufferPoolHits 90
High_AvgSyncReadTime 200
Low_AvgAsyncWritesPerPoolWrite 30
Low_PctIndexHits 90
High_AvgSyncWriteTime 200
High_AvgPoolIOTime 200
Low_AvgAsyncReadsPerPoolRead 50
High_AvgSyncIOTime 200
High_AvgPoolWritesPerPoolRead 100
N/A
DB2 Activity Old_LastBackupTimestamp 2
High_PctConnectionsUsed 80
High_ConnectionErrors 100
High_CurrentConnections 50
High_SpaceUsedDMSTablespace 85
High_SpaceUsedSMSTablespace 0
High_MostRecentConnectResponse 5
High_ConnWaitingForHost 30
N/A
DB2 Instance
Status
High_PctConnectionsExecuting 75
DB2 locks and
Deadlocks
High_AppPctLockListUsed 50
High_AvgLockEscalationConn 5
High_AvgLocksHeld 5
High_AppDeadlocks 6
High_DeadlocksDelta 4
High_AppLockEscalations 6
High_PctIntDeadlockedRollbacks 80
High_DBPctLockListUsed 50
High_PctDeadlockRollbacks 80
High_LockEscalationsDelta 3
High_LockTimeoutsDelta 10
N/A

Get Business Service Management Best Practices now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.