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

Version 1 Current »

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 2023

The following jar files are required by SAP CC agents when using with SAP Convergent Charging server version 2023:

  • 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

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/CC2023_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 CORESDK02_0-80008788.ZIP -d core_sdk

Example - Listing SAP CC Core SDK jar files

$ ls -gG core_sdk/jars/
total 17152
-rw-r--r-- 1 174853 Feb 12 2024 common_message.jar
-rw-r--r-- 1 660812 Feb 12 2024 common_util.jar
-rw-r--r-- 1 691798 Feb 12 2024 core_chargingplan.jar
-rw-r--r-- 1 426602 Feb 12 2024 core_chargingprocess.jar
-rw-r--r-- 1 4917429 Feb 12 2024 core_client.jar
-rw-r--r-- 1 128076 Feb 12 2024 jaxb-api-2.3.1.jar
-rw-r--r-- 1 254858 Feb 12 2024 jaxb-core-2.3.0.1.jar
-rw-r--r-- 1 1117712 Feb 12 2024 jaxb-impl-2.3.8.jar
-rw-r--r-- 1 89161 Feb 12 2024 logging.jar
-rw-r--r-- 1 302450 Feb 12 2024 sap.com~tc~logging~java.jar

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 :

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

Secure Communications via TLS

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

Note!

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 SAP CC Online Agent Configuration page. 

  • No labels