Versions Compared

Old Version 1

changes.mady.by.user Yuri Au Yong

Saved on

compared with

New Version Current

changes.mady.by.user Yuri Au Yong

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

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

Info
titleExample - Unzip core_sdk.zip


Code Block
$ unzip DATA_UNITS/CC2023_TOOLS_CONTENT_UC_OSIND/core_sdk.zip -d core_sdk


...

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

    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>


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

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. 

...