Carefully review the prerequisites section in the Help doc.
A Java Virtual Machine (JVM) of the required type and version must be downloaded from IBM?s web site and installed on the computer running the WebSphere probe, and the PATH has to contain the java executable. The version must match the JVM version used to run WAS. You can also copy the Java folder from the WebSphere directory of the Windows WebSphere server to the remote Windows computer in which probe needs to be installed.
Ensure that a version of java.exe exists in the path as described below. This is a prerequisite for dropping the probe, the version of java.exe is at this point not critical.
Later (during the installation wizard launched when double-clicking the probe) you will be asked to select the java.exe version matching the JVM version used to run WAS.
and there are further notes in the Help doc and below...
WebSphere Release Notes do not contain the same information as the websphere probe Help documentation.
Install IBM's JRE v1.7 + WAS runtimes/plugins folder on to the robot and probe should connect and test resource successfully.
The WebSphere probe can be installed on either a server running WebSphere or on a remote computer.
If installed on a server running WebSphere, all environment files needed by the probe are present on the server.
If installed on a remote computer, the environment files needed by the probe must be copied to this computer.
For WebSphere Ver 5 and 6.0, copy the following folders from the WebSphere directory of the WebSphere server.
For WebSphere Ver 6.1, 7.0, 8.0 and 8.5 copy the following folders from the WebSphere directory of the WebSphere server:
Note: If the probe is installed on a remote computer running an OS different from the server running the WebSphere software (For example, if the remote computer runs Windows and the server running WebSphere is a Solaris computer), you can copy the etc and lib folders as described above.
If the websphere probe is running on Windows OS, the AppServer directory for Windows should be used. Similarly, if the probe is running on Linux or Solaris, the AppServer directory from the respective environment should be used.
A Java Virtual Machine (JVM) of version 1.6 or higher ***FROM IBM*** must be installed on the computer running the WebSphere probe and the PATH has to contain the java executable. You can also copy the Java folder from the WebSphere directory of the Windows WebSphere server to the remote Windows computer in which probe needs to be installed.
Ensure that a version of java.exe exists in the path as described below. This is a prerequisite for dropping the probe. The version of java.exe is at this point not critical. Later (when the installation wizard is launched on double-clicking the probe) you will be asked to select the java.exe.
Note: JVM version 1.6 and above is available along with WAS 7.0 and above and you can use the same path for java_home.
Performance Monitoring Infrastructure (PMI) needs to be ENABLED on the WebSphere Application Server in order for the probe to gather performance data.
Read more about PMI in the following link:
Some versions of the WebSphere Application Server (WAS) contain an internal error that prevents external PMI clients, like the websphere probe, to obtain correct PMI values from the server.
For both WAS 5 and 6, the error is corrected in fix number PK20342.
For WAS 5, the error is fixed in version 184.108.40.206.
For WAS 6, the error is fixed in version 220.127.116.11, older versions like 18.104.22.168 and 22.214.171.124 contains the error.
When installing the probe, a wizard will assist you through the initial probe configuration.
The WebSphere probe requires the following software environment:
Nimsoft Monitor Server version 5.1.1 or later
Nimsoft Robot version 5.23 or later
***Java Virtual Machine 1.6 or later FROM IBM
Note: For SOC (Service Oriented Configuration) functionality, NMS Server 5.6 or later and UMP 2.5.2 or later is required.
Monitoring System RequirementsThe probe supports IBM WebSphere Application Server versions 5.1, 6.0, 6.1,7.0, 8.0 and 8.5
If all else fails try deploying the Nimsoft java_jre from your archive to the websphere machine where the probe is installed (when installed locally), then deploy the probe again and make sure you get a port and a PID.