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:
...
Code Block |
---|
$ 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 setting the classpath has been set, manually distribute the jar file should be manually distributed to be so it is in place when the EC/ECSA is startedrestarted.
You can then restart the EC/ECSA to register the changes in the configuration above for the SAP CC Batch agent.
The agent can be configured for secure communication via TLS. This requires that a keystore is created for each EC/ECSA host. For more information about setting up secure communication, refer to 9.69.5 SAP CC Secured Connection.
Scroll ignore | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
...