Notes on the SAP Java Connector (SAP JCo) 

There are no special configuration options provided for the SAP Java Connector in SAP Web AS. For this reason it is usually not necessary to make any administrative settings for the SAP Jco functions.

If problems do occur while you are using the SAP JCo (for example, installation errors), you should contact SAP Support. To shorten the processing time, you should carry out the following activities, before you open an OSS message.

Ascertain the SAP JCo Version Number for SAP Web AS 6.30

Before you open a message, test the consistency of the installation.

java -jar {path-to-sapjco.jar}/sapjco.jar –stdout

Versions of JCo API/JCo Middleware, Jco Library and RFC Library are displayed. If the installation is correct, all the versions are displayed. In this case, check that the SAP JCo versions are the same. Note that the RFC Library for SAP JCo 6.30.x must have the version number 620 with minor release number larger than 000.

Include your test results in your OSS message.

Activate SAP JCo Traces

To activate SAP JCo Traces on the SAP J2EE Engine, start

<SAP J2EE 630 Instal>\usr\sap\C11\JC00\j2ee\configtool\configtool.bat

on the database GUI login. Then choose Server in the navigation tree and add the following line to the Java parameters:

-Djco.trace_level=<trace_level> -Djco.trace_path=<path>

hinzu.

To activate Traces for the Java Resource Adapter, execute the above actions for the parameters:

-Djra.trace_level=<trace_level> -Djra.trace_path=<path>

aus.

Further Notes

Before you create a message you should also refer to the following OSS notes for SAP JCo support.

636912 Frequent Installation Problems with SAP Java Connector

598891 Tools for Analyzing SAP JCo and RFC Errors in SAP Web AS

628962 Activation of the SAP JCo Trace