sap_basis probe fails to connect to configured resource

Document ID : KB000111031
Last Modified Date : 14/08/2018
Show Technical Document Details
Issue:
After following all of the prerequisites specified on the sap_basis Preconfiguration Requirements Wikl page, the probe still fails to connect to the configured resource with the following errors in the log:

Unexpected fatal error occurred during data collection against DataCollector for <configured resource>
java.lang.NoClassDefFoundError: com/sap/conn/jco/ext/DestinationDataProvider at com.nimsoft.probe.common.ctd.SapSession.login(SapSession.java:503)

User name and password are valid in the resource configuration.
Environment:
UIM 8.51
sap_basis: 2.01
Cause:
Incorrect Windows system environment variable and sap_basis.cfg settings related to the installed Sap Java Connector files required by the sap_basis probe.
Resolution:

After installing the SAP Java Connector (JCO) to enable SAP ABAP monitoring the PATH and CLASSPATH variables have to be set to the absolute path where the JCO was installed.  For example, if the JCO was installed in the C:\SAPJCO3 directory, these system environment variables need to be set to the following:

PATH=%PATH%;C:\SAPJCO3
CLASSPATH=%CLASSPATH%;C:\SAPJCO3

After making these changes to the Windows system environment variables, stop then start the Nimsoft Robot Watcher service so that the robot picks up the system environment variable changes.

When you configure the sap_basis probe and specify the JCO location, the probe should set the "-cp" switch in the startup->options key value to the following:

-cp "./*;C:/SAPJCO3/*"

If this does not occur, modify this key value using the sap_basis probe's Raw Configure GUI.
Select the startup folder from the left-hand pane, then modify the options value in the right-hand pane to correct the argument to the "-cp" switch.