• All Products
• Apama
• Support

Apama Version 4.2.2.x

Support key

• Supported – Progress has tested this configuration and fully supports it.
• Maintained – Progress has not necessarily tested this configuration but believes that it would work. Progress would be willing to provide technical support and consider patching the software (if appropriate) in the event that the customer encounters a problem related to this configuration.
• Unqualified – This configuration is unsupported. Progress cannot advise as to whether it might work or not.
• Unserviceable – This configuration is unsupported. Progress confirms that this configuration is known not to work.
  
  

If a configuration is not called out below it should be assumed to be Unqualified.

Linux x86 32-bit | Linux x86 64-bit | Solaris SPARC 64-bit| Solaris X64 64-bit | Windows x86 32-bit | Windows x86 64-bit | General Notes

Apama Platforms

Apama for Linux x86 32-bit

Only the operating systems and update levels / service packs listed here have been tested with Apama 4.2.0.

Platform Notes

1. No graphical development or deployment tools are supported on these platforms.
2. Apama does not support Security Enhanced Linux (SELinux). This option should be turned off on Linux for Apama to run. Note that RHEL5 install has default SELinux setting as "enforcing". To disable SELinux set it to "Disabled" when installing the operating system or using the GNOME menu under "System"->"Administration"->"SELinux Management".
3. The Apama platform is compatible with an older version of the libdb libraries (db 4.2) than those installed by default on RHEL5. The package that needs to be installed on RHEL5 to use the Apama platform is compat-db. See the Apama 4.2 Release Notes for more complete information.
4. The Apama platform is compatible with an older version of the libdb libraries (db 4.2) than those installed by default on SLES10. The package that needs to be installed on SLES10 to use the Apama platform is db42. See the Apama 4.2 Release Notes for more complete information.
5. To build the samples and develop applications using the C/C++ API, development tools which are not present in the default installation of the supported platforms must be installed. On all the supported Linux platforms, except SLES9, the gcc-c++ package and all its dependencies must be installed. See the Apama 4.2 Release Notes for more complete information. For SLES9 specific information, see below.
6. In order to run the deprecated EventStore software a change must be made to the memory management settings prior to product installation. See the Apama 4.2 Release Notes for more complete information. Specific additional instructions are provided for SLES9.
7. The Apama platform is not compatible with the default C++ runtime available on SLES9. The package that needs to be installed on SLES9 to use Apama is gcc runtime 3.4.6 or 4.1, or the equivalent compiler for development. Since 4.1 ‘rpm’s are officially available for download from Novell, this is the version recommended by Progress. See the Apama 4.2 Release Notes for more complete information.
8. Apama includes JRE 6.0 update 14, and Progress recommends that you use JRE or JDK 6.0 update 14 or later to develop, build, test, and deploy your applications. If you want, you can build your application with JDK 5.0 update 10 or later instead of JDK 6.0. However, it is still recommended that you use JRE 6.0 at runtime.
9. Adobe Acrobat Reader 8 or later is required to view the product documentation.

Apama for Linux x86 64-bit

Only the operating systems and update levels / service packs listed here have been tested with Apama 4.2.0.

Platform Notes:

1. No graphical development or deployment tools are supported on these platforms.
2. The deprecated EventStore tool is currently unsupported on SLES10 64-bit and SLES11 64-bit.
3. Apama does not support Security Enhanced Linux (SELinux). This option should be turned off on Linux for Apama to run. Note that the RedHat 5 install has default SELinux setting as "enforcing". To disable SELinux set it to "Disabled" when installing the operating system or using the GNOME menu under "System"->"Administration"->"SELinux Management".
4. The Apama platform is compatible with an older version of the libdb libraries (db 4.2) than those installed by default on RHEL5. The package that needs to be installed on RHEL5 to use the Apama platform is compat-db. See the Apama 4.2 Release Notes for more complete information.
5. The Apama platform is compatible with an older version of the libdb libraries (db 4.2) than those installed by default on SLES10. The package that needs to be installed on SLES10 to use the Apama platform is db42. See the Apama 4.2 Release Notes for more complete information.
6. To build the samples and develop applications using the C/C++ API, development tools which are not present in the default installation of the supported platforms must be installed. On all the supported Linux platforms, except SLES9, the gcc-c++ package and all its dependencies must be installed. See the Apama 4.2 Release Notes for more complete information. For SLES9 specific information, see below.
7. In order to run the deprecated EventStore software (not applicable on SLES10 64-bit) a change must be made to the memory management settings prior to product installation. See the Apama 4.2 Release Notes for more complete information.
8. The Apama platform is not compatible with the default C++ runtime available on SLES9. The package that needs to be installed on SLES9 to use Apama is gcc runtime 3.4.6 or 4.1, or the equivalent compiler for development. Since 4.1 ‘rpm’s are officially available for download from Novell, this is the version recommended by Progress. See the Apama 4.2 Release Notes for more complete information.
9. Apama includes JRE 6.0 update 14, and Progress recommends that you use JRE or JDK 6.0 update 14 or later to develop, build, test, and deploy your applications. If you want, you can build your application with JDK 5.0 update 10 or later instead of JDK 6.0. However, it is still recommended that you use JRE 6.0 at runtime.
10. Adobe Acrobat Reader 8 or later is required to view the product documentation.
11. Some changes to C/C++ clients may be required; this normally requires including #include <stdlib.h> and #include <cstring> in your source due to the compiler changes on the SLES11 64-bit OS
12. To allow the StateStore Plugin to function on SLES11 64-bit OS, the following libraries need to be sym-linked:
     - sudo ln -s /usr/lib64/libgdbm.so /usr/lib64/libgdbm.so.2
     - sudo ln -s /usr/lib64/libdb-4.5.so /usr/lib64/libdb-4.2.so

Apama for Solaris SPARC 64-bit

Only the operating systems and update levels / service packs listed here have been tested with Apama 4.2.0.

Platform Notes:

1. No graphical development or deployment tools are supported on this platform.
2. Apama includes JRE 6.0 update 14, and Progress recommends that you use JRE or JDK 6.0 update 14 or later to develop, build, test, and deploy your applications. If you want, you can build your application with JDK 5.0 update 10 or later instead of JDK 6.0. However, it is still recommended that you use JRE 6.0 at runtime.
3. The binaries provided for this release are 64-bit binaries.
4. Adobe Acrobat Reader 8 or later is required to view the product documentation.

Apama for Solaris X64 64-bit

Only the operating systems and update levels / service packs listed here have been tested with Apama 4.2.0.

Platform Notes:

1. No graphical development or deployment tools are supported on this platform.
2. The deprecated EventStore tool is unsupported and not available on this platform.
3. Apama includes JRE 6.0 update 14, and Progress recommends that you use JRE or JDK 6.0 update 14 or later to develop, build, test, and deploy your applications. If you want, you can build your application with JDK 5.0 update 10 or later instead of JDK 6.0. However, it is still recommended that you use JRE 6.0 at runtime.
4. Sun Studio 12 should be patched up to patch level 127157 or later.
5. Adobe Acrobat Reader 8 or later is required to view the product documentation.

Apama for Windows x86 32-bit

For all components and tools:

For client-side dashboards:

Only the operating systems and update levels / service packs listed here have been tested with Apama 4.2.0.

Platform Notes:

1. Apama includes JRE 6.0 update 14, and Progress recommends that you use JRE or JDK 6.0 update 14 or later to develop, build, test, and deploy your applications. If you want, you can build your application with JDK 5.0 update 10 or later instead of JDK 6.0. However, it is still recommended that you use JRE 6.0 at runtime.
2. For client-side dashboard deployments using Java WebStart Apama requires that end users have JRE or JDK 5.0 Update 13 or later installed.
3. For dashboard use Apama supports Internet Explorer 7 with a Sun JRE 5.0 or later configured as the Java plugin in the browser.
4. Administrator privileges are required to install Apama.
5. Adobe Acrobat Reader 8 or later is required to view the product documentation.
6. Apama for Windows 32-bit may be installed and run on Windows 64. However, since the Correlator in this version is 32-bit, only up to 2Gb of memory will be available to it. If, however, the Correlator binary is modified to enable the Large Address Aware property, up to 4Gb of memory will be available to it. Note that this modification would not apply to the embedded JVM; and only up to 2Gb may be addressed by a Correlator Java application.

Apama for Windows x86 64-bit

For all components and tools:

For client-side dashboards:

Only the operating systems and update levels / service packs listed here have been tested with Apama 4.2.0.

Platform Notes:

1. Apama includes JRE 6.0 update 14 64-bit, and Progress recommends that you use JRE or JDK 6.0 update 14 or later 64-bit to develop, build, test, and deploy your applications. Use of any JRE other than the one that Apama ships with is discouraged. If you want, you can build your application with JDK 5.0 update 10 64-bit or later instead of JDK 6.0. However, it is still recommended that you use JRE 6.0 at runtime.
2. For client-side dashboard deployments using Java WebStart Apama requires that end users have JRE or JDK 5.0 Update 13 or later installed. However, as of shipping date, WebStart is only available with Sun 64-bit JRE/JDK 6.0 Update 12 or later, on Windows only. Otherwise a 32-bit JRE or JDK is required to use WebStart.
3. If you deploy client-side dashboards on a 32-bit JRE or JDK these will only be able to address up to 2Gb of memory.
4. For dashboard use Apama supports Internet Explorer 7 with a Sun JRE 5.0 or later configured as the Java plugin in the browser.
5. Administrator privileges are required to install Apama.
6. Adobe Acrobat Reader 8 or later is required to view the product documentation.

General Notes

Virtualization Software

Application Virtualization Software (similar to such products as VMWare and Citrix) provide an abstraction layer that decouples the physical hardware from the 'guest' operating system to deliver greater IT resource utilization and flexibility. Progress Technical Support will provide 'best effort' assistance with Application Software environments but can only log product deficiency bugs if the problem can be demonstrated in a non Application Virtualization Software environment. If the problem/behavior is seen only in the Virtualized environment, then it should ultimately be pursued with the VM provider and Progress Technical Support will assist to the degree possible in investigating the issue.

• Capital Markets Platform
  • Algorithmic Trading
  • Capital Markets Foundation
  • Capital Markets Connectivity
  • Apama Architecture
  • Capital Markets Resources
• Event Processing Platform
  • Complex Event Processing
  • Apama Architecture
  • Event Processing Resources
• Apama Solutions
• Apama Customers
• Apama Resources
  • Capital Markets
  • Event Processing
• Apama Support