Page Comparison

...

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 in  Image Added. The following steps will show you how to extract and store the files:

1. 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 labeled libsapjco3.so:

   Code Block
   tar xvfz sapjco3-<platform_version>.tgz

   
   

2. Copy the sapjco3.jar file that you had just extracted to the 3pp directory of the persistent storage.

   Code Block
   cp sapjco3.jar /nfs_share/persistent/3pp

   
   

   Info
   title Info!
   For users of the previous  versionsprevious Image Added 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.

   
   

3. Copy the extracted libsapjco3.so file to the jni directory of the persistent storage.

   Code Block
   cp libsapjco3.so /nfs_share/persistent/jni

   
   

4. Commit the changes by restarting the platform pod. The pod should reinitialize not long after.

   Code Block
   kubectl delete pod platform-0 --namespace <namespace name>

   
   

5. Create a database connection on an Oracle, Derby, or MySQL database.
   
   

6. Create a table in the database to keep track of the file states. See the example below:

   Info
   title Example - JCO Uploader state table
   Code Block 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");

   
   

...