SAP JCo Uploader Agent Preparations

The following is required in order to use the SAP JCo Uploader agent:

1. You must run the sapjco3.jar. Add <file location>/sapjco3.jar to the classpath for the jar files for the relevant Execution Context. In the example below, the SAP jar files are located in MZ_HOME/3pp, the configuration includes the jar files required to use any of the SAP CC agents, and the Platform database is Derby:

   Example.

   Note!

   Ensure that you include existing paths, so that they are not overwritten.

   $ mzsh topo get topo://container:<container>/pico:platform/obj:config.classpath
   $ mzsh topo get topo://container:<container>/pico:<ec>/obj:config.classpath

   $ mzsh topo set topo://container:<container>/pico:<ec name>/obj:config.classpath.jars '
   ["lib/picostart.jar",
   "3pp/common_message.jar",
   "3pp/common_util.jar",
   "3pp/core_chargingplan.jar",
   "3pp/core_chargingprocess.jar",
   "3pp/core_client.jar",
   "3pp/logging.jar",
   "3pp/sap.com~tc~logging~java.jar",
   <file location>/sapjco3.jar"]'
   
   
   $ mzsh topo set topo://container:&lt;container>/pico:platform/obj:config.classpath.jars '
   ["lib/derby.jar","lib/picostart.jar",
   "lib/javassist.jar",
   "lib/codeserver.jar",
   "lib/codeserver_common.jar",
   "<file location>/sapjco3.jar"]'

2. Place the libsapjco3.so file in the  MZ_HOME/common/lib/native directory of the Platform Container and each Execution Container. 
   
   
3. Create a database connection, e g Oracle, Derby, or MySQL.
   
   

4. Create a table to keep track of 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");