9.69.5 SAP CC Agent Preparations

Owned by Yuri Au Yong
Last updated: Nov 15, 2024

The relevant jar files required for the preparations must be obtained from the SAP CC server provider. The Core SDK jar files can be found in SAP Convergent Charging Installation Materials.

SAP CC Core SDK Jar Files for Version 4.0/4.1/5.0/2020/2021/2022

The following jar files are required by SAP CC agents 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 Core SDK client JAR files must match the version of your SAP CC core system (i.e the back end servers).

From the unpacked SAP Convergent Charging installer, the jar files can typically be found by navigating to the directory and unzipping the core_sdk.zip file located in DATA_UNITS/<CC_VERSION>_TOOLS_CONTENT_UC_OSIND.

Example - Unzip core_sdk.zip

$ unzip DATA_UNITS/CC2021_TOOLS_CONTENT_UC_OSIND/core_sdk.zip -d core_sdk

For the SAP Convergent Charging server patches, the JAR files can typically be found by unpacking the patch file for the SAP CC Core SDK software unit.

Example - Unzip SAP CC Core SDK patch file

$ unzip CORESDK02P_5-70006882.ZIP -d core_sdk

Example - Listing SAP CC Core SDK jar files

$ ls -gG core_sdk/jars/
total 6976
-rw-r--r-- 1 181100 May 18 2021 common_message.jar
-rw-r--r-- 1 642584 May 18 2021 common_util.jar
-rw-r--r-- 1 677453 May 18 2021 core_chargingplan.jar
-rw-r--r-- 1 418615 May 18 2021 core_chargingprocess.jar
-rw-r--r-- 1 4822903 May 18 2021 core_client.jar
-rw-r--r-- 1 85372 May 18 2021 logging.jar
-rw-r--r-- 1 302450 May 18 2021 sap.com~tc~logging~java.jar

The classpaths for the jar files are specified for each EC/ECSA. In the example below, the SAP jar files are located in MZ_HOME/3pp.

Note!

Ensure that you include existing paths, so that they are not overwritten. Example command to get existing classpaths:

$ mzsh topo get topo://container:<container>/pico:<ec>/obj:config.classpath

Example - Setting classpath

$ 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, manually distribute the jar file so it is in place when the EC/ECSA is restarted.

You can then restart the EC/ECSA to register the changes in the configuration above for the SAP CC agents.

Secure Communications via TLS

The agents 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.6 SAP CC Secured Connection.

For SAP CC Online Agent, it is required to add the hostname information of the SAP Convergent Charging Core server Dispatcher Instance(s). This information is needed by the execution content server. The IP address needs to be explicitly mentioned. Refer to the 9.69.1.1 SAP CC Online Agent Configuration page.