SAP-CallAPI: After upgrade from V10.07 to V12.2.3 the SAP CallAPI does not work

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

This Article gives an important hint why SAP CallAPI  could not work after installation when following error is notified in the dev_jco_trc.txt file (trace of the RFC interface)

============================================================================

Error thrown [Fri Dec 06 11:20:09,442]: Error thrown by application running in JCoServer
java.lang.NoClassDefFoundError: com.uc4.communication.requests.XMLRequest
        at com.uc4.callapisap.RFCServer.handleRequest(Unknown Source)
        at com.uc4.callapisap.RFCServer.handleRequest(Unknown Source)
        at com.sap.conn.jco.rt.DefaultServerWorker$FunctionDispatcher.handleRequest(DefaultServerWorker.java:1047)
        at com.sap.conn.jco.rt.DefaultServerWorker$FunctionDispatcher.handleRequest(DefaultServerWorker.java:983)
.....
        at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:231)
        at java.lang.Thread.run(Thread.java:812)
Caused by: java.lang.ClassNotFoundException: com.uc4.communication.requests.XMLRequest
.....

============================================================================

 

Environment

Release : 12.2

Component : AUTOMATION ENGINE

Cause

The error 'java.lang.NoClassDefFoundError' message is a very reliable indicator that the library UC4.jar is missing from the customers installation.

 

Resolution

The installation package of the SAP CallAPI component contains a UC4.jar component with all the Java classes specific to this application.

Make sure that this file is present in the bin-folder of the SAP-Call API installation.