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

Jar Files for SAP CC SDK

The following jar files are required by the SAP CC Online collection agent :

• common_message.jar
• common_util.jar
• core_chargingplan.jar
• core_chargingprocess.jar
• core_client.jar
• jaxb-api-2.3.1.jar
• jaxb-core-2.3.0.1.jar
• jaxb-impl-2.3.8.jar
• logging.jar
• sap.com~tc~logging~java.jar

Setting up the jar files

You will need to copy the jar files into the specific persistent storage directory. Refer to Persistent Storage (2.2) 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 Usage Engine. The following steps will show you how to copy the jar files :

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
   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!

   For users of the previous Usage Engine 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 SSL. This requires that a keystore is created for each EC host.