Share This:

Now that you have the WebSphere Application Server (WAS) KM configured, what do all these parameters mean? Why am I seeing some parameters and not others?

 

Server & Application Availability:

 

In the screenshot below, WebSphere is monitored with IBM WebSphere’s Performance Monitoring Infrastructure (PMI) disabled altogether. PMI is ‘0’ or None. But you can see that a lot parameters are still displayed such as NodeAgentAvailability, ServerAvailability, AplicationStatus and DMgrAvaiability.
Proxy Servers are identified so you can use them for more advanced features of BPPM such as Root Cause Analysis and Event Management.
And the WAS KM can identify Clusters as shown below.
WAS KM keeps track of how much time it takes to discover WebSphere. The ConfigurationDiscoveryTime parameter is populated with this information. And users can double-click on the DiscoveredInformation text parameter to get a report showing the entire WebSphere cell.

was1.png

 

General Health Monitoring:

 

 

If you select General Health monitoring then you will not only see JMX based parameters such as NodeSync and ServerAvailability but also high-level general information is delivered including ServerResources, FreeMemory, PercentMemoryUsed, TotalMemory and UsedMemory parameters.
If IBM Profiler is enabled then we will automatically display all available Garbage Collection parameters.

was2.png

 

Full Monitoring of Web Application:

 

In the screenshot below we see a URL monitor is discovered. This gives us the ability to monitor an activity and the performance of a specific URL within an application.
ApplicationStatus represents the JMX general availability of that application.
Everything is organized hierarchically per the same name of the instance; you have an archive, then the war, and inside that war you may have several servlets; each servlet may have one or many URLs, and the data is reported accordingly.
As you can see, you can have a very detailed view of each and every one of those applications.

was3.png

 

Monitoring Level - Sample Server (PMI=All)

 

The screenshot below shows we can monitor not only an application but also the entire cell. The PMI Level is ‘4’ or All.
Here the server bpm-01.AppTargtet.v1-hou-ngp-dv01NodeBPM.0 is expanded to display all of the data categories.
The names expanded under the bpm-01.AppTargtet.v1-hou-ngp-dv01NodeBPM.0 server are the names you would see exactly as if you were viewing them from the IBM WebSphere Console. This helps users to correlate the view displayed in the PATROL Console with the view displayed in the IBM WebSphere Console.
You can see the server shows up under the cluster since that’s how it was configured on the IBM WebSphere side.
Below it you can see DMgrAvailability and ConfigurationDiscoveryTime. And below that you have
MsgReadTimeFromJavaCollector which tells you how large the message is that’s being sent from the java admin client into PATROL. And MsgSizeFromJavaCollector is how long it takes to process the data.

was4.png

 

Monitoring Level - Node Agent (PMI=All)

 

Here is another example of monitoring a node where the PMI Level is ‘4’ or All.

was5.png


BMC PATROL for IBM WebSphere Application Server

 

BMC PATROL for IBM WebSphere Application Server 3.0.00 was GA March 2013. A maintenance release is coming soon! Be the first to know when it is released. Sign up for Proactive Notification here

 

BPM for IBM Web Application Servers – “The Suite”


Let us know what else we can do to improve the Web Application Server KMs. Post your Ideas here. We would love to hear from you!

 

p1.png

 

Popular Knowledge Articles:

 

KA411135 - WebSphere Application Server KM - GarbageCollections and GarbageCollectionDuration parameters are missing

KA408165 - After upgrading from 2.20.00.01 to 3.0.00, unable to see menu option to configure HTTPTransportConnState parameter

KA408166 - WebSphere Application Server KM - Unable to configure JDBCConnectState after upgrading to WAS KM 3.0

KA398574 - WebSphere Application Server KM - Question about NodeSync parameter

KA405070 - WebSphere Application Server KM is unable to discover IHS service

 

 

 

 

p2.png

 

Was this helpful?  Are there related topics I missed? Please add comments to share your experience.

 

To see more like this, BMC ProactiveNet Pulse Blogs.