Installation changes in 10.15.5
As of June 2024, Apama is no longer available from within the Software AG Installer. This option has been replaced with .zip (Windows) and .tar.gz (Linux) files that are extracted to the desired installation location.
Migration from the Software AG Installer
The installed structure of the extracted contents of the installation packages matches that created by the Software AG Installer. Therefore, the installations are equivalent. The recommended method for upgrading an installation package for a release, service pack or fix is to remove the existing installation and extract the upgraded package in its place at the same location on the disk. The same procedure can be used with an installation originally created by the Software AG Installer.
Differences between the installations
While the structure of the installations on the disk is the same, there are some other differences.
License file The Software AG Installer provides the ability to select an arbitrary license file and put in place during the installation. For a new installation, the license file must be manually copied into place, typically into the
APAMA_WORK.license directory (see
About Apama license files). If the installation is upgraded, this should not be necessary, as the license file is already in place and the
APAMA_WORK directory is not touched, assuming it was placed outside of the installation directory.
Windows Start menu Installation by extraction does not automatically create any entries in the Windows Start menu. This can be done manually if required, and does not need to be changed if the installation is updated.
Software AG Designer / Eclipse Software AG Designer, which is an OEM version of Eclipse, has been replaced with a standard copy of Eclipse using the Apama plug-in. The packages that contain the Apama plug-in include a full copy of Eclipse. There is no need to install Eclipse separately or add the plug-in manually.
The Apama demos (BackTesting, StatisticalArbitrage and Weather) have been removed.
Choosing which package to use
Several installation packages are available from Software AG Empower, as shown in the table below. Used without a license, these packages provide the freemium Apama Community Edition, with the limitations that come with it (see
Running Apama without a license file).
Package Name | Use Case | Notes | Contents |
Core | Cumulocity IoT | Eclipse with Apama plug-in1 | IAF2/ADBC3 | IBM webMethods | Samples | Documentation | SL Dashboard |
apama_core | Runtime deployment | Current apama_core. | | | | | | | | |
apama-c8y-dev | Cumulocity IoT development | | | | | | | | | |
apama-dev | Standalone customers without IBM products (that is, not needing client libraries to connect to Universal Messaging and/or Terracotta) | | | | | | | | | |
apama-dbp-dev 4 | Standalone customers with IBM products (that is, needing client libraries to connect to Universal Messaging and/or Terracotta) | As apama-dev with IBM components. | | | | | | | | |
apama_core_{VERSION}_cumulocity | Retained for compatibility with existing zip files | Cumulocity IoT components only. Overlay on apama_core or apama-dev. | | | | | | | | |
apama_core_{VERSION}_samples | Samples for EPL et al. | Current samples zip. Can be extracted separately. | | | | | | | | |
apama_core_{VERSION}_doc | Apama documentation | Current documentation zip. Can be extracted separately. | | | | | | | | |
apama-sl-dashboard | Dashboard development or deployment | Only SL components. Installs its own JVM into a separate directory. | | | | | | | | |
1 Windows only.
2 IAF: Integration Adapter Framework.
3 ADBC: Apama Database Connector.
4 DBP refers to the Digital Business Platform that was a collection of multiple products aligned to work together, some of which transferred to IBM in 2024.
For more information, see
Installing Apama.