Context
Change Type: Announcement
Product area: Analytics
Component: Streaming Analytics
Technical details
Build artifact: apama-in-c8y
Internal ID: PAM-35403
Description
In an upcoming release, the Cumulocity Streaming Analytics (Apama) runtime images are upgraded to Debian 13 (Trixie) as their base operating system, replacing Debian 12 (Bookworm). The upgrade also introduces a new Java version and changes the location of the Python 3 interpreter.
Important
If you use custom Java or Python code in an Analytics Builder block uploaded to the apama-ctrl microservice, make the required changes promptly so that you are ready before the update is rolled out to your environment.
Most applications are unaffected. The changes matter if you build custom microservices on the Apama base image, use custom Java EPL or connectivity plugins, or run Python code from a block or extension uploaded to the apama-ctrl microservice.
Debian 13 base image
The published Apama runtime images are based on Debian 13 (Trixie) instead of Debian 12 (Bookworm). If you build a custom Cumulocity microservice on the Apama base image and install extra operating system packages, check that those packages are still available and that their names have not changed in Debian 13.
Java 25
Apama ships with OpenJDK 25 instead of OpenJDK 17. All Java code executed within the correlator runs on Java 25, so if you have custom EPL plugins or connectivity plugins you should recompile them with Java 25 and test that they still behave as expected. If you use Java in a block uploaded to an apama-ctrl microservice, make any required changes promptly so you are ready when the update is rolled out to SaaS environments.
See the JDK release notes for details of the breaking changes and new features between Java 17 and Java 25. Some applications may require updates to third-party library dependencies, but in most cases Apama plugins continue to work without changes.
Python interpreter path change
The Python 3 interpreter is the operating-system-provided /usr/bin/python3 (Python 3.13 from Debian 13) rather than a Python 3 installation shipped inside the Apama directory. If you have hardcoded the old Apama-provided Python 3 path anywhere — for example in a script, Dockerfile, or test configuration — update it to /usr/bin/python3.
Apama still ships PySys and the Apama PySys extensions; only the interpreter itself comes from the operating system. Review What’s New in Python for any language changes that may affect your code.
References & feedback
For more information on these and other changes, review the Apama change logs. If you have any questions, feel free to post to the streaming-analytics-apama tag on the Cumulocity Tech Community.