websphere (WebSphere Monitoring) Release Notes

The WebSphere Monitoring (websphere) probe monitors the IBM WebSphere Application Servers (WAS) and stores the monitoring information at specified intervals. You can define alarms that are generated when the specified thresholds are breached.
Revision History
This section describes the history of the revisions for the websphere probe.
 Support case(s) may not be viewable to all customers.
What's New:
  • Added the following new metrics:
    • GC Count
    • GC Time
    • GC Interval Time
  • The MCS Enhanced profiles now support the above new metrics.
October 2019
What's New:
  • Added the following new metrics:
    • J2EE Application State
    • Servlet Sessions Live Count
    • Bean Module Method Response Time
    • Thread Pool Declared Thread Hung Count
    • Thread Pool Size
    • Connection Pool Wait Time
    • Connection Pool Used
    • Connection Pool Free Size
    • Connection Pool Use Time
    • Connection Pool Waiting Thread Count
    • JVM Runtime Heap Size
    • JVM Runtime Process CPU Usage
    • JVM Runtime Used Memory
  • Enhanced profiles that enable you to configure metrics, baselines, alarm thresholds, alarms - including Time Over Threshold alarms - and custom alarm and close alarm messages, all within a single MCS profile.
March 2019
What's New:
  • Added support for monitoring IBM WebSphere 9.0.
Fixed Defects:
  • The probe did not work when TLS v1.2 was enabled on the Websphere server and the Java JRE version was 6 (Java version 6 is still the minimum version required). 
    Support case number 00972305 and 00875294.
  • The probe did not allow the use of wildcards in templates which restricted the creation of templates on large environments.
     Support case number 00847306.
  • The mysql server did not update the QoS data from the Websphere probe. 
    Support case number 690389
  • The probe did not start on WebSphere Application Server, AIX 7.1. 
    Support case number 00533968
December 2018
Fixed Defect:
  • The probe did not display any data on the probe Unified Dashboard on the AIX system. 
    Support case number 70002617
March 2016
Fixed Defect
  • The log size kept on increasing even after setting the log size key value. 
    Salesforce case 00164635
June 2015
Fixed Defects
  • Probe did not handle a period (.) in the deployed application name and did not generate metrics for the application. 
    Salesforce case 00151138
  • The probe kept restarting and eventually crashed if different credentials were provided to connect to the same server and port. 
    Salesforce case 00157088
  • The probe took time to load checkpoints for J2EE applications.
     Salesforce case 00157088
  • The probe was not generating alerts with the Advanced Alarming feature. 
    Salesforce case 00158147
  • In probe version 1.70, a new resource could not be added to the probe configuration. 
    Salesforce cases: 00145653, 00149026, 00148816
  • The probe did not display metrics under automonitor node when applied through auto-configuration.
     Salesforce case 00149110
  • The user credentials are no longer stored in the probe logs. 
    Salesforce case 00151834
April 2015
Provided an option on the probe GUI to configure IBM WebSphere 8.5
November 2014
Added support for zLinux Operating System.
June 2014
  • Fixed the defect where the probe displays an error in the Portuguese environment while adding resource information or fails to launch the probe GUI if a resource is already added.
  • Fixed the defect where the probe is generating two device id for one resource.
  • Fixed the defect where the TNT2 data does not match with the Metric Definition table data.
April 2014
  • Added support for JRE 1.7x.
  • Fixed an issue where 
    No Entities Found
     error was being thrown while creating a profile for a valid resource with incorrect details.
March 2014
  • Fixed server name change on auto scan of profiles.
  • Fixed GUI error in multiple groups.
  • Fixed template functionality for template from different profiles.
October 2013
Added Probe Defaults template.
November 2012
  • Dragging issue for wild-card scenario and template to auto-configuration.
  • Fixed issues of Monitor: Browse, Activation/Deactivation, Updating no. of monitors after deletion, Disappearing of monitors after editing profile.
  • Default group is no longer visible if there is no resource under it.
  • Fixed the Issue of QoS Definition issue in automonitor.
September 2012
  • Added support for WAS version 8.0 & 8.5.
  • Added features for Auto Configurations, Auto Monitors, and Templates.
  • Added monitoring capability for application up/down status.
  • Added support for AIX.
  • Added Low threshold for monitors in GUI.
  • Added Memory Threshold tab in General Setup dialog.
August 2012
  • Added support for automatic scanning of newly added servers.
  • Fixed the issues that are related to Scanning.
  • Changed the probe startup mechanism to start up java.
  • Changed the cfg structure. Monitors are now part of the profile section.
December 2010
Added support for extended NIS database information.
June 2010
  • Added support for WebSphere Application Server version 7.0.
  • Added support for AIX.
  • Added an option to turn off the usage of SSL.
  • Changed message subsystem to 2.3.4.x (only new installations).
April 2009
  • Upgrade libraries.
  • Added security file.
December 2007
  • Better handling of clusters.
  • Fixed GUI issues.
September 2007
Changed start-up script on Solaris.
December 2006
Fixed data collection in websphere cluster.
November 2006
Optimized data collection
October 2006
  • Fixed deprecated messages in SystemOut.log (WAS 6.0).
  • Optimized data-collection.
September 2006
  • Fixed issues on UNIX platform.
  • Added support for "First probe port number".
  • Minor GUI changes.
July 2006
  • Fixed missing alarms.
  • Minor GUI Changes.
  • Fixed error in config file write when section contained '/'.
  • Java SDK changed - now sends the probe name with alarms. 
  • Fixed fetching of keys from WAS.
  • Initial version.
May 2006
Probe Specific Hardware Requirements
The websphere probe must be installed on systems with the following minimum resources:
  • Memory: 2-4GB of RAM. The OOB configuration of the probe requires 256MB of RAM.
  • CPU: 3-GHz dual-core processor, 32-bit, or 64-bit
Probe Specific Software Requirements
The websphere probe requires the following software environment:
  • Nimsoft Monitor Server 7.6 or CA Unified Infrastructure Management 8.0 or later
  • Robot 7.6 or later (recommended)
 For SOC functionality, Nimsoft Monitor Server 7.6 or CA UIM 8.0 or later and UMP 2.5.2 or later is required.
  •  Verify installation of Java JRE 6 or later.
  • WebSphere Application Server version 7.0 or later.
 WebSphere Community Edition (CE) is not supported.
Installation Considerations
The websphere probe can be installed on either a server running WAS or on a remote computer.
  • If installed on a server running WAS, install the relevant environment files on that server.
  • If installed on a remote computer, install the relevant environment files on that computer.
     Install WAS files/AppServer directory on the system where the probe is deployed for all WAS versions.
  • For WebSphere version 
     copy the 
    folders from the WebSphere directory of the WAS.
  • If the OS on the remote computer with the probe and the WAS are different, copy the 
     folders from the WebSphere server to the remote computer.
  • If the probe is running on Windows OS, use the AppServer directory for Windows. Similarly, if the probe is running on Linux or Solaris, use the AppServer directory of the respective environments.
Verify Java Installation
Install Java version 6 or higher from IBM on the computer running the probe and include the java executable in the probe path. You can also copy the Java folder from the WebSphere server directory to the remote Windows computer on which probe is installed.
 Java JRE 6 and above is available with WAS 7.0 and above and you can use the same path for java_home.
You can configure the JVM and Java Home settings to install the probe on a UNIX OS.
Follow these steps:
  1. Set the JAVA_HOME environment variable to the directory in which IBM JVM is installed and export JAVA_HOME. For example,
    export JAVA_HOME=/usr/lib/jvm/ibm-java2-i386-50/jre/bin
  2. Ensure that the PATH variable includes $JAVA_HOME. For example,
    export PATH=$JAVA_HOME:$PATH
  3. Open a shell as a root user and run the command 
    java - version
The output shows the IBM JVM version installed.
On Windows
You can configure the JVM and Java Home settings to install the probe on a Windows OS.
Follow these steps:
  1. To set the Java path, right-click 
    My Computer
     and select 
  2. In the 
     tab, click 
    Environment variables
  3. Alter the 
     variable so that it also contains the path to the IBM Java executable.
  4. Open a DOS window and use the command 
    java - version
    The output shows that IBM java version is installed. 
Enable Performance Monitoring Infrastructure (PMI) on the WAS for the probe to gather performance data. For more information about PMI, see http://www-01.ibm.com/support/knowledgecenter/SSTVLU_8.6.0/com.ibm.websphere.extremescale.doc/txsenablepmi.html?lang=en 
WAS Versions
Certain WAS versions prevent external PMI clients like the websphere probe to obtain correct PMI values from the server. The internal error is fixed in the following WAS versions:
  • For both WAS 5 and 6, the error is corrected.
  • For WAS 5, the error is fixed in version
  • For WAS 6, the error is fixed in version, older versions like and contain the error.
Known Issues
This section describes the known issues of the probe.
  • After deploying websphere version 1.81, you cannot edit or save the resource in the IM console, after deleting an existing profile which has advanced alarming configuration. As a workaround, manually update the advance alarming configuration in the cfg file by modifying the alarm_on_resource key.
  • The probe stops functioning if you save the probe configuration with an invalid 
    Java Home
     path or 
The Admin Console GUI of the probe has the following more limitations. 
  • The probe stops functioning if you do not refresh the web page after adding new resource.
  • The probe does not let you create Templates, Auto Monitor, and Auto Configuration. 
  • The probe does not support any other QoS except Default.
  • The probe does not support the Rescan for host option, which allows you to scan the profiles in the host server after a preconfigured interval of 15 minutes.
  • The probe displays the message "Controller: Max. Restarts reached for probe 'websphere' (command = )" and the probe fails to work. This is a known issue and occurs when multiple robots run on the same Linux machine. The probe works on one robot but fails on another robot. As a workaround, manually assign a value for the parameters -DNIM_SPOOLER_PORT and -DNIM_CONTROLLER_PORT using the Infrastructure Manager Raw Configure.