Make sure that you are running one of the supported operating system versions. For detailed information, see the Supported Platforms document for the current Apama version, which is available from the following web page: http://documentation.softwareag.com/apama/index.htm.

On Windows, an Oracle JRE is provided with the Software AG Installer for use when running the .exe file. No further steps are required.

On Linux, an Oracle JRE must be already installed in order to run the Software AG Installer .jar file. You can download this from http://www.oracle.com/technetwork/java/javase/downloads/index.html.

For information on the required version, see the Supported Platforms document for the current Apama version, which is available from the following web page: http://documentation.softwareag.com/apama/index.htm.

The disk space requirements vary, depending on which options you want to install. For a full installation of Apama including Software AG Designer (Windows only), approximately 1.5 GB of hard-disk space is required.

If you are going to run the Software AG Installer on Windows, you must have Windows system administrator privileges.

You can only install Software AG products on a local hard drive on a Windows system. You cannot install the products on a network-mounted drive.

For more requirements, see the Using the Software AG Installer guide.

Apama does not support Security Enhanced Linux (SELinux). This option should be turned off on Linux for Apama to run.

To build the samples and develop applications using the C/C++ API, development tools that are not present in the default installation of the supported platforms must be installed. On all supported Linux platforms, the GCC-C++ package and all its dependencies must be installed. These are typically provided on the installation media as part of your distribution.

If you intend to use the compiled runtime, please ensure that the binutils package is installed.

Note that the performance of latency-critical applications can be significantly impacted by the choice of the file system where the correlator writes its log files and/or persistence database. File systems such as ext3, ext4, NFS, ZFS and GFS2 can have surprisingly poor worst-case latency especially when the system is loaded, so for latency-critical applications we would recommend use of XFS where possible.