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

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

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

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.

$ 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 the classpath has been set, the jar file should be manually distributed to be in place when the EC/ECSA is started.

The agent can be configured for secure communication via SSL. This requires that a keystore is created for each EC/ECSA host.  For information about setting up a keystore, see the next section. 

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


Creating a New Keystore File

Follow the steps below to create a new Java Keystore File using the mzsh keytool command.

Run the mzsh keytool generate command to create a new certificate and keystore file. The certificate generated by the command will have the alias: Platform.

$ mzsh keytool generate -k <keystore file/>

Example - Creating a keystore

$ mzsh keytool generate -k $MZ_HOME/keys/container.keys
  • No labels