To use a standalone java utility to test the connection:
<ODI_HOME>/odi/sdk/lib directory.sapjco3.jar and the sapjco3 library are in the <ODI_HOME>/odi/sdk/lib directory.On Windows:
java -cp sapjco3.jar;odi-sap.jar oracle.odi.sap.km.test.JCoTest
On Linux/UNIX:
java -cp sapjco3.jar:odi-sap.jar oracle.odi.sap.km.test.JCoTest
This should result in an output similar to this:
ODI_SAP_CON_POOL.jcoDestination file in the oracledi/drivers directory. The file should look like this:
#for tests only! jco.client.lang=EN jco.destination.peak_limit=10 jco.client.client=800 jco.client.passwd=<SAP Password> jco.client.user=<SAP User> jco.client.sysnr=00 jco.destination.pool_capacity=5 jco.client.ashost=<SAP Application Server>
#for tests only ! jco.client.lang=EN jco.destination.peak_limit=10 jco.client.client=800 jco.client.passwd=ODI123 jco.client.user=ODI jco.client.sysnr=00 jco.destination.pool_capacity=5 jco.client.ashost=123.123.123.123.
On Windows:
java -cp sapjco3.jar;odi-sap.jar oracle.odi.sap.km.test.JCoTest
On Linux/UNIX:
java -cp sapjco3.jar:odi-sap.jar oracle.odi.sap.km.test.JCoTest
This should result in an output similar to this:
In addition to just testing the SAP connection, the utility will also validate the existence of certain Function Modules required for the RKM. These are installed during first execution of the RKM (UPLOAD_ABAP_CODE and UPLOAD_ABAP_BASE set to true).
ODI_SAP_CON_POOL.jcoDestination file after execution, as it contains the SAP login credentials.