Crystal reporting task

Adding this task or feature to the library of supported Services Framework tasks requires copying JAR files to the /opt/ibm/ftm/services-engine/lib directory in the Services Framework container. You can use the FTP server with the <ftm-instance>-application persistent volume claim to add, remove, or update the JAR files for your tasks. Copy the JAR files to the /services-engine/lib directory in the root directory of the <ftm-instance>-application persistent volume claim.
Notes:
  • If any of the JAR files were copied to this directory when another feature or task was added, they do not need to be copied again.
  • Stop and restart the Services Framework pod to use the new files.
For more information about using the FTP server and the mount paths of the persistent volume claims, see SFTP server deployment.

JAR files to copy for this task or feature

Copy the following JAR files for this Services Framework task or feature. These JAR files are provided in the artifacts container for your offering.

  • No JAR files from your FTM offering need to be copied.
  • You need to provide some JAR files from your own installation of the SAP Crystal Server. Copy the JAR files that are shown in the following list:
    • aspectjrt.jar
    • bcm.jar
    • biarengine.jar
    • biplugins.jar
    • boconfig.jar
    • ceaspect.jar
    • cecore.jar
    • celib.jar
    • ceplugins_core.jar
    • cereports.jar
    • cesdk.jar
    • cesession.jar
    • corbaidl.jar
    • ebus405.jar
    • logging.jar
    • sapjce.jar
    • SL_plugins.jar
    • TraceLog.jar

Cryptographic library changes

The RSA cryptographic JAR files that were needed in the SAP Crystal Reports 2020 (RSA 4.3 SP02 and Earlier) are shown in the following list.
  • certjFIPS.jar
  • cryptojce.jar
  • cryptojFIPS.jar
  • jcmFIPS.jar
  • ssljFIPS.jar
Starting with SAP Crystal Reports 2025 (4.3 SP02), the cryptographic implementation has changed. SAPJCE is now used for all cryptographic operations, replacing RSA completely. The RSA JAR files listed above are no longer available and are replaced by the Common Crypto Library (CCL) package. The JAR files in the CCL package are shown in the following list.
  • sapjce.jar

The native libraries in the CCL package are shown in the following list.

  • Linux: libsapcrypto.so, libslcryptokernel.so, and libslcryptokernel.so.sha256
  • Windows Operating system: sapcrypto.dll, slcryptokernel.dll, and slcryptokernel.dll.sha256

Installing SAP Crystal Reports 2025

The steps to install SAP Crystal Reports 2025 are shown in the following list.
  1. Copy all JAR files to the Services Framework container at the following directory. 
    /opt/ibm/ftm/services-engine/lib
  2. Copy the native libraries (.so files for Linux or .dll files for Windows) to the same directory that is mentioned in Step 1.
    /opt/ibm/ftm/services-engine/lib
  3. Configure the library path by adding the following customization to your FTM Custom Resource (CR) for the services-engine container.
    - containers:
        services-engine:
          env:
            - name: LD_LIBRARY_PATH
              value: /opt/ibm/ftm/services-engine/lib
      maxReplicas: 1
      name: services-engine
      replica: 1
Note: By default, .so and .dll files are not loaded from the library directory that causes the crystal report task configuration to fail. The LD_LIBRARY_PATH environment variable is needed to make sure that the native libraries are properly loaded. This customization is used to run the crystal reports task configuration.