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.
This section describes the history of the revisions for the websphere probe.
Support case(s) may not be viewable to all customers.
Provided an option on the probe GUI to configure IBM WebSphere 8.5
Added support for zLinux Operating System.
Added Probe Defaults template.
Added support for extended NIS database information.
Changed start-up script on Solaris.
Fixed data collection in websphere cluster.
Optimized data collection
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.
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 version7.0,8.0,and8.5,copy theruntimesandpluginsfolders from the WebSphere directory of the WAS.
- If the OS on the remote computer with the probe and the WAS are different, copy theetcandlibfolders 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:
- 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
- Ensure that the PATH variable includes $JAVA_HOME. For example,export PATH=$JAVA_HOME:$PATH
- Open a shell as a root user and run the commandjava - version.
The output shows the IBM JVM version installed.
You can configure the JVM and Java Home settings to install the probe on a Windows OS.
Follow these steps:
- To set the Java path, right-clickMy Computerand selectProperties.
- In theAdvancedtab, clickEnvironment variables.
- Alter thePathvariable so that it also contains the path to the IBM Java executable.
- Open a DOS window and use the commandjava - 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
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 22.214.171.124.
- For WAS 6, the error is fixed in version 126.96.36.199, older versions like 188.8.131.52 and 184.108.40.206 contain the error.
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 invalidJava Homepath orLibrariespath.
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.