Troubleshooting the sensor

This topic describes common problems that occur with the SAP CCMS server sensor and presents solutions for those problems.

Sensor fails in remote server

Problem

The following errors occur, which means that the class path does not contain the path for the sapjco.jar file:

Sensor failed in remote server: com/sap/mw/jco/JCO
MSG_ERROR: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO

Solution

The sapjco.jar file should be in the $COLLATION_HOME/lib/JCo/lib directory, this file path should be in the class path.

Look for the following message in the DiscoverManager.log file:

adding this jar file to the list: {jar-file-path}

The jar-file-path should be $COLLATION_HOME/lib/JCo/lib/sapjco.jar.

Sensor cannot find library file

Problem

The following errors occur, which means that the sensor cannot find the libsapjcorfc.so library file in sun.boot.library.path or in java.library.path:

Sensor failed in remote server:
JCO.classInitialize (): Could not load middleware layer
'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit (): Could not initialize dynamic link library sapjcorfc
[Can't find library sapjcorfc (libsapjcorfc.so) in sun.boot.library.path
or java.library.path sun.boot.library.path={full-path-list}

Solution

Ensure that the libsapjcorfc.so library file is in the $COLLATION_HOME/lib/JCo/operating system path.

This library file must be of the 64-bit version, because the Agile Service Manager servers, or anchors, or both, in the Agile Service Manager environment are running a 64-bit operating system.

Also ensure that this path is present in the full-path-list for sun.boot.library.path that is mentioned in the error message. If the path is present, the problem might be due to library dependencies that have not been met. Run the ldd command against the libsapjcorfc.so library file to get a list of the library dependencies, and verify that your environment supports these dependencies.

No CCMS access list is provided for an IP address

Problem

The following error occurs:

ERROR collation. AnchorClient - No CCMS access list provided for:
{ip-address}

This error can occur for one of the following reasons:

No access list is provided for the sensor.
The sensor cannot successfully connect to the IP address using the access list information that is provided by the user.

Solution

If you provided the necessary access list credentials, verify the following items:

Ensure that the user ID meets the specified minimum authorization requirements.
Ensure that the SAP ABAP server is accessible.
Look for the following message in the local-anchor*.log, and ensure that the username and client-id that are specified are the ones that you set:
```
Checking connection with username: {username} and clientID: {client- id} 
```

You can also provide SAP_ALL authorization to the user and try to connect to the SAP ABAP server directly through the SAP GUI, if it is available.