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/2022

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

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

Setting up the jar files

You will need to copy the jar files into the specific persistent storage directory. Refer to Persistent Storage (3.0) for information on setting up persistent storage if you have not or if you would like to know more about the use of persistence in . The following steps will show you how to copy the jar files for version 3.0:

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

    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

    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.

    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.

  • No labels