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

...

$ 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 Online agent.

The agent can be configured for secure communication via SSLTLS. This requires that a keystore is created for each EC/ECSA host.   For For more information about setting up a keystore, see the next section. secure communication, refer to 9.69.5 SAP CC Secured Connection.

Creating a New Keystore File

Follow the steps below to create a new Java Keystore File using the mzsh keytool command.

Run the mzsh keytool generate command to create a new certificate and keystore file. The certificate generated by the command will have the alias: Platform.

$ mzsh keytool generate -k <keystore file/>