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

...

1. Copy the jar files to the 3pp directory of the persistent storage.

   Code Block

   cp common_message.jar /nfs_share/persistent/3pp cp common_util.jar /nfs_share/persistent/3pp cp core_chargingplan.jar /nfs_share/persistent/3pp cp core_chargingprocess.jar /nfs_share/persistent/3pp cp core_client.jar /nfs_share/persistent/3pp cp jaxb-api-2.3.1.jar /nfs_share/persistent/3pp cp jaxb-core-2.3.0.1.jar /nfs_share/persistent/3pp cp jaxb-impl-2.3.8.jar /nfs_share/persistent/3pp cp logging.jar /nfs_share/persistent/3pp ,, cp sap.com~tc~loggging~java.jar /nfs_share/persistent/3pp

   
   

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

   
   

2. 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>

   
   

The agent can be configured for secure communication via TLS. This requires that a keystore is created for each EC host. For more information about setting up secure communication, refer to SAP CC Secured Connection.

...