Versions Compared

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.

Jar Files for

...

SAP CC SDK

The following jar files are required by the SAP CC Online collection agent 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

  • 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

...

You will need to copy the jar files into the specific persistent storage directory. Refer to Persistent Storage (4.2) 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 Usage Engine. The following steps will show you how to copy the jar files for version 3.0 :

  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

Note!

If you are using earlier versions of Usage Engine, there is not need to split it into separate directories for EC and Platform since the Platform and EC will retrieve the file from the same directory.

...

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

...