This appendix describes how to perform an SAP stand-alone connection test.
In addition to the Connection Testing described above, a test can be performed outside of ODI using a standalone java utility:
To use a standalone java utility to test the connection:
Open a command window.
Change to oracledi/drivers directory.
Make sure that JAVA_HOME points to a JVM (at least 1.5).
Make sure that you have installed SAP Java Connector and that the sapjco3.jar and the sapjco3 library are in the oracledi/drivers directory.
Launch the utility using the following command:
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:
Use a text editor to open the 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>
Enter your SAP connection information, which you have received from your SAP administrator. The file will then look similar to this (use your connection information!):
#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.
Launch the utility again using the following command:
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 = Yes
).
Delete the ODI_SAP_CON_POOL.jcoDestination
file after execution, as it contains the SAP login credentials.