SAP JCo Uploader Agent Preparations(4.3)
Before using the SAP JCo Uploader agent, you must prepare the relevant jar files for the agent to properly function. The jar files can be acquired from the sapjco3 zip file that you can acquire from and SAP JCo jar files.
The following jar files are required by the SAP JCo Uploader agent:
sapjco3.jar
libsapjco3.so
Setting up the jar files
You will need to copy the jar files and the libsapjco3.so file into 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 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 sapjco3.jar file that you had just extracted 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>
- Create a database connection on an Oracle, Derby, or MySQL database.
Create a table in the database to keep track of the file states. See the example below:
Example - JCO Uploader state table
CREATE TABLE "MZ_SAP_JCO_UPLOADER_STATE" ("WF_NAME" VARCHAR2(100 BYTE), "FILENAME" VARCHAR2(100 BYTE), "START_POSITION" NUMBER, "END_POSITION" NUMBER); CREATE INDEX "UPLOADER_STATE_INDEX1" ON "MZ_SAP_JCO_UPLOADER_STATE" ("FILENAME", "WF_NAME");