SAP RFC Agent Preparations(3.0)
To be able to use the SAP RFC profile and processing agent, you will need to extract the JNI and jar file and place them in the specific persistent storage directory. Refer to Persistent Storage (3.0) for information on setting up persistent storage if you have not or if you would like to know more about the use of persistence in .
The following jar files are required by the SAP RFC agent:
sapjco3.jar
libsapjco3.so
Setting up the jar files
The following steps will show you how to extract and store the files:
Extract the SAP JCo library binaries. There should be 2 files present, the Java class file labeled
sapjco3.jar
and the java native library file labeledlibsapjco3.so
:tar xvfz sapjco3-<platform_version>.tgz
Copy the extracted
sapjco3.jar
file to the 3pp directory of the persistent storage.cp sapjco3.jar /nfs_share/persistent/3pp
Info!
For users of the previous  versions, there will be no need to split it into separate directories for EC and Platform as the Platform and EC will retrieve the file from the same directory.
Copy the extractedÂ
libsapjco3.so
file to the jni directory of the persistent storage.cp libsapjco3.so /nfs_share/persistent/jni
Commit the changes by restarting the platform pod. The pod should reinitialize not long after.
kubectl delete pod platform-0 --namespace <namespace name>