Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The relevant jar files required for the preparations must be obtained from the SAP CC server provider.

Jar Files for Version 4.0/4.1/5.0/2020/2021

The following jar files are required by the SAP CC Batch agent when running version 4.0, 4.1, 5.0, 2020 or 2021:

  • common_message.jar
  • common_util.jar
  • core_chargingplan.jar
  • core_chargingprocess.jar
  • core_client.jar
  • logging.jar
  • sap.com~tc~logging~java.jar

Note!

The version of SAP CC client JAR files must match the SAP CC core system (i.e the back end servers) version.

The classpaths for the jar files are specified for each EC/ECSA. In the example below, the SAP jar files are located in MZ_HOME/3pp.

Note!

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

$ 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"]'

After the classpath has been set, the jar file should be manually distributed to be in place when the EC/ECSA is started.



  • No labels