WebSphere Server Monitoring
Create a New Monitor
The supported versions of WebSphere Servers are 5.x, 6.x, 7.x, 8.x and 9.x
Prerequisites for Websphere Monitoring:
For Applications Manager to collect data from WebSphere Application Server, configurations are required at the Performance Monitoring Infrastructure (PMI) specification level. Refer Prerequisites Section for configuration details.
To create a WebSphere Server Monitor
- Click on New Monitor link.
- Select WebSphere Server.
- Select the Deployment Mode as Base or Network Deployment.
- For Base Mode, Enter the Host name/IP Address of the host in which websphere application server is running.
For Network Deployment, enter the Host name/IP Address of the websphere application server in which the perf servlet is installed. This will automatically discover all the WebSphere servers in Network Deployment.
- Enter the SubNetMask of the network.
- Enter the HTTP Transport Port (9080 by default).
- Enter the polling interval time in minutes.
- If you are adding a new monitor from an Admin Server, select a Managed Server.
- Select the version of the WebSphere to be monitored - 5.x, 6.x, 7.x, 8.x and 9.x
- Enter the port number of the SOAP Connector (8880 by default).
- If you want to monitor WebSphere through SSL mode, select the SSL is enabled checkbox.
- Enter the User Name and Password, if Global Security is enabled.
- In Network Deployment Mode, Enter the Network Deployer's Host and SOAP Port (Default : 8879).
- Choose the Monitor Group from the combo box with which you want to associate WebSphere Server Monitor (optional). You can choose multiple groups to associate your monitor.
- Click Add Monitor(s). This discovers WebSphere server from the network and starts monitoring them.
Note:
Applications Manager has been tested for WebSphere versions of English, German, Japanese and Chinese languages. In the Network Deployment mode, the child monitors which are automatically discovered cannot be deleted from the list view. If a user tries to delete a child monitor, it will get added again in next poll of the Parent monitor. Child monitors will be deleted only if the parent monitor is deleted. If they want to stop data collection(don't want to monitor) for child monitors, they need to mention those child monitors in Exclude list of the parent monitor in edit monitor page. If they mentioned it in exclude list of parent monitor page, then those child monitors will be unmanaged and data collection stops for those monitors.
Monitored Parameters
The Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives the Health Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin configurations. Click on the individual monitors listed, to view the following information
WebSphere servers are monitored based on the attributes listed under the following tabs:
The monitoring details of the server are represented graphically that helps to understand the parameters with ease. You can also configure thresholds to the attributes monitored by the server based on these details.
Note: Please note that the attributes of the tabs marked with * are not available in the WebSphere Application server v5.x.
Monitor Details
| Parameters | Description |
|---|
| Deployment Mode |
The deployment mode of the WebSphere server. You can choose either Base or Network Deployment.If you select:
- Base Mode, enter the Host Name/IP Address of the host in which the WebSphere application server is running.
- Network Deployment, enter the Host name/IP Address of the WebSphere Application server in which the perf servlet is installed. This will automatically discover all the WebSphere servers in Network Deployment.
|
| WebSphere Version |
Denotes the version of the WebSphere server monitor. |
| Port |
Refers to HTTP Transport port. |
| Subnet Mask |
The subNetMask of the WebSphere server. |
| Do not resolve DNS name |
If you have multiple system IP addresses configured with a single DNS name, select the ‘Do not resolve DNS name’ option under‘Advanced’ section. |
| Network Deployer Host, Network Deployer SOAP Port |
If you have chosen the ‘Network Deployment’ mode, specify the Network Deployer Host and Network Deployer SOAP Port values. The default SOAP port is 8879. |
| SSL is enabled |
If you want to monitor WebSphere through SSL mode, select the ‘SSL is enabled’ checkbox. |
| App Servers to Monitor |
If you want to monitor selected app servers running in the WebSphere server, select the ‘Advanced Options’ checkbox and specify the app servers in the ‘App Servers to Monitor’ field. If you want to monitor all the app servers in the WebSphere server, leave this field empty. |
Overview
| Parameters | Description |
|---|
| State |
Refers to different states of the Websphere server such as running and down. |
| HTTP Port |
Refers to HTTP Transport port. |
| Transaction Details |
Specifies Global Commit Duration, Committed Transactions, Transactions Rolled Back and Transactions Optimized. |
| Server Response Time |
Specifies Minimum, Maximum, Average and Current Response Time. |
| Availability |
Specifies the status of the WebSphere server - available or not available. |
| JVM Memory Usage |
Specifies the total memory in JVM run time. |
| CPU Utilization |
Specifies the average system CPU utilization taken over the time interval since the last reading. |
| Free Memory |
Specifies the amount of real free memory available on the system. |
| Average CPU Utilization |
Specifies the average percent CPU Usage that is busy after the server is started |
Session Details of Web Applications
| Parameters | Description |
|---|
| Invalidated Sessions |
Specifies the total number of sessions that were invalidated. |
| Session Creation Rate/Min |
The rate per minute at which session objects were created by the server. |
| Affinity Breaks/Min |
The total number of requests received for sessions that were last accessed from other Web applications. This value can indicate failover processing or a corrupt plug-in configuration. |
| Live Sessions |
The number of local sessions that are currently cached in memory |
| Total Requests/Min |
The total number of requests that a web application processed |
| Error Count/Min |
Total number of errors in a servlets or JavaServer Page (JSP). |
| Concurrent Requests |
The number of requests that are concurrently processed. |
EJB Details
| Parameters | Description |
|---|
| Name |
Mentions the names of the different EJB present in the WebSphere server with JAR and EAR name. Move the mouse pointer over the EJB name to view the JAR and EAR name. |
| Type |
Denotes the different types of the bean such as entity, stateless session, stateful session, and message driven. |
| Concurrent Lives |
Specifies the number of concurrent live beans. |
| Total Method Calls |
Specifies the total number of method calls. |
| Average Method Response Time |
Specifies the average time required to respond to the method calls. |
| Pool Size |
Specifies the number of objects in the pool (entity and stateless). |
| Activation Time |
Specifies the average time in milliseconds that the total bean is activated for that particular Bean container, including the time at the database, if any. |
| Passivation Time |
Specifies the average time in milliseconds that the total bean is passivated for that particular Bean container, including the time at the database, if any. |
Current JDBC Connection Pool Details
| Parameters | Description |
|---|
| Name |
The name of the current JDBC Connection pool. |
| Pool Type |
The type of the connection pool. |
| Create Count |
The total number of connections created. |
| Pool Size |
The size of the connection pool. |
| Concurrent Waiters |
The number of threads that are currently waiting for a connection. |
| Faults |
The total number of faults in the connection pool such as timeouts. |
| Average Wait Time |
The average waiting time, in milliseconds, until a connection is granted. |
| Percent Maxed |
The average percent of the time that all connections are in use. |
JMS Queues
| Parameters | Description |
|---|
| Queue Depth |
The number of messages available for a queue's consumption |
| Uncommitted Transactions |
The number of messages locked or uncommitted. This means messages that have been added or removed but the transaction has not yet been committed. |
| Produced Count/Sec |
The total number of messages produced per second to this queue. |
| Consumed Count/Sec |
The total number of messages consumed per second from this queue |
| Number of Producers |
The number of currently attached local producers. |
| Number of Consumers |
The number of currently attached local consumers. |
| Message Wait Time(sec) |
Maximum time spent by messages on this queue at consumption in seconds. |
| Oldest Message Age(sec) |
The longest time any message has spent on this queue in seconds. |
JMS Topics
| Parameters | Description |
|---|
| Durable Subscriptions |
The number of subscriptions that can be used to preserve messages published on a topic while the subscriber is not active. |
| Non-durable Subscriptions |
The number of non-durable subscriptions. |
| Incomplete Publications |
The number of publications not yet received by all current subscribers. |
| Oldest Publication Age |
The longest time any publication has spent on this topic space. |
| Number of Publishers |
The number of local publishers to topics in this topic space. |
| Number of Subscriptions |
The number of local subscriptions to topics in this topic space. |
| Number of Publications |
The total number of publications to this topic space. |
Thread Pool Details
| Parameters | Description |
|---|
| Name |
Mentions the name of the thread pool. |
| Thread Creates |
Specifies the total number of threads created. |
| Thread Destroys |
Specifies the total number of threads destroyed. |
| Active Threads |
Specifies the number of concurrently active threads. |
| Pool Size |
Specifies the average number of threads in pool. |
| Percent Used |
The average percentage of the pool in use. |
| Free Pool Size |
The number of free connections in the pool. |
| Percent Maxed |
Specifies the average percent of the time that all threads are in use. |
Servlet Details*
| Parameters | Description |
|---|
| Name |
Name of the Servlet. |
| Web Module |
Web module/Web app to which the servlet belongs. |
| Total Requests |
Total number of requests processed by the servlet. |
| Concurrent Requests |
Total number of concurent requests processed by the servlet. |
| Num Errors |
Total number of errors in the particular Servlet. |
| Response Time |
Average response time of the servlet. |
JCA Adapters*
| Parameters | Description |
|---|
| Name |
Name of the JCA adapter. |
| Create Count |
Total number of JCA connection threads/processes created in the adapter. |
| Close Count |
Total number of JCA connection threads closed in the adapter. |
| Pool Size |
Overall pool size of the active pools in the adapter. |
| Free Pool Size |
Overall number of free pools available in the adapter. |
| Use Time |
Total use time of the processes in the adapter. |
| Wait Time |
Total wait time of the processes in the adapter. |
| Waiting Thread Count |
Total number of waiting JCA connector threads/processes in the adapter. |
JCA Connection Pools*
| Parameters | Description |
|---|
| Name |
Name of the JCA Connection Pool. |
| Adapter |
JCA adapter to which the JCA Connection pool belongs. |
| Create Count |
Total number of JCA Connection threads/processes created in the particular pool. |
| Close Count |
Total number of JCA Connection threads/processes created in the particular pool. |
| Pool Size |
Overall pool size of the JCA connection pool. |
| Free Pool Size |
Total number of free connections available in the JCA Connection Pool. |
| Use Time |
Total use time of the processes in the current pool. |
| Wait Time |
Total wait time of the processes in the current pool. |
| Waiting Thread Count |
Total number of waiting JCA connector threads/processes in the current JCA Connection Pool. |
Note:
In Network Deployment mode, Network Deployer will be listed in the WebSphere Monitors list. Clicking on it, will give server information and the custom attributes. Further, the individual WebSpheres within the Network Deployment would also be listed. Clicking on those servers would bring up each of those server's details.
