Versions Compared

Old Version 9

changes.mady.by.user Yuri Au Yong

Saved on

compared with

New Version Current

changes.mady.by.user Kevin Wu

Saved on

Key

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

...

Info
titleExample - Setting classpath


Code Block
$ 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 has been set, manually distribute the jar file should be manually distributed to be so it is in place when the EC/ECSA is startedrestarted.


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


The agent 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.5 SAP CC Secured Connection.

Note

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 execution content server. The IP address needs to be explicitly mentioned. Refer to the 9.69.1.2 SAP CC Online Agent Configuration page. 

...