Apama 2.4

Linux | Solaris (32-bit) | Windows

Operating Systems

Linux

The information regarding Linux platform support below applies to the following Apama products

• Event Manager
• EventStore
• Platform and Development Environment

• Scalability and Management Environment

Platform Notes:

• Event Store is not supported on Red Hat 7.3.
• The client tools of Event Store (Research Studio) and the Platform and Development Environment (EMM) are not supported on Linux although the server components are.
• C++ Clients compiled against the C API using GCC 2.96RH will crash when an exception is thrown by the Engine client library. This arises from a fundamental incompatibility between the C++ runtimes of the client and the Engine client library. The Workaround is to use pure C or to not use exceptions in the C++ code.
• RedHat Enterprise Linux 3 installations prior to Update 1 contain serious bugs that will prevent this product from operating correctly. PDE is certified on RedHat Enterprise Linux 3, Update 5. Attempting to run on a version of Enterprise Linux at an earlier update level is not a supported configuration.
• The Java API has been successfully tested with most Sun JREs post version 1.1, and with the Microsoft 5.00.3805 JVM. However minor differences in output format and behaviour are evident with pre-1.3.1 JREs - it is recommended that version 1.3.1 or later is used.
• It is recommended that all transport and codec plugins for the IAF be written in pure C. While C++ plugins can be written and will work in most cases, you may experience problems loading such plugins into an adapter. See the Release Notes for further information
• Console-mode installation is not supported and installation requires an X server to be running. If you are accessing the machine over ssh, on Solaris the 'xauth' program must be installed in order for the X server connection forwarding to be set up correctly by sshd. On Linux, either select to install the XFree86 server at initial install time, or install the appropriate XFree86-4.1.0 (or later) package.
• RedHat Enterprise Linux 3 installations prior to Update 1 contain serious bugs that will prevent this product from operating correctly. The EventStore is certified on RedHat Enterprise Linux 3, Update 5. Attempting to run
• on a version of Enterprise Linux at an earlier update level is not a supported configuration
• Installation of EventStore requires administrative rights on both windows and unix systems
• The EventStore cannot be installed on an NFS mounted disk, and must be installed locally
• Runtime Exceptions (e.g. divide-by-zero, sequence index out of bounds) cannot be caught in this release. In case of a Runtime Exception, the Monitor or subMonitor will be killed by the Correlator
• There are currently known issues with the memory allocator (malloc) on Linux, which will cause the Correlator to fail when its memory usage exceeds approximately 1.1GB. On systems with stock kernels (such as RedHat 7.1) processes are unable to allocate much more than 1GB of small objects (i.e. objects < 4KB in size). It has been determined that upgrading to a more recent kernel, version 2.4.18, will allow almost 3GB of memory to be allocated.
• RedHat Enterprise Linux 3 installations prior to Update 1 contain serious bugs that will prevent this product from operating correctly. The Event Manager is certified on RedHat Enterprise Linux 3, Update 5. Attempting to run on a version of Enterprise Linux at an earlier update level is not a supported configuration.
• To run this version of the Apama Correlator requires the following two packages, which are not installed by default in RedHat 7.3:
  • libgcc-3.0.4-1.i386.rpm
  • libstdc++3-3.0.4-1.i386.rpm
• To compile plug-ins or C++ client programs on RedHat 7.3 requires the following packages in addition to those listed above:
  • gcc3-3.0.4-1.i386.rpm
  • gcc3-c++-3.0.4-1.i386.rpm
  • libstdc++3-devel-3.0.4-1.i386.rpm
  These can be downloaded from ftp://fr2.rpmfind.net/linux/redhat-archive/updates/7.2/en/os/i386/ or some mirror thereof (a full list of RedHat mirror sites can be found at http://www.redhat.com/download/mirror.html).

* Client code compiled with the 3.4.6 compiler will not dynamically link with Apama's pre-built libraries (built on gcc 3.2.3 on Redhat 3). When using Redhat 4 customers are required to download and install g++ 3.2.3. This can be installed alongside the default compiler but any Apama code must be compiled with the older version. This applies to all C++ clients built against the C/C++ Client APIs, any C/C++ IAF plugins, and any Correlator plugins.

Solaris (32-bit)

The information regarding Linux platform support below applies to the following Apama products

• Event Manager
• EventStore
• Platform and Development Environment
• Scalability and Management Environment

Platform Notes:

• The client tools of Event Store (Research Studio) and the Platform and Development Environment (EMM) are not supported on Solaris although the server components are.
• Installation of EventStore requires administrative rights on both windows and unix systems
• The EventStore cannot be installed on an NFS mounted disk, and must be installed locally
• Console-mode installation is not supported and installation requires an X server to be running. If you are accessing the machine over ssh, on Solaris the 'xauth' program must be installed in order for the X server connection forwarding to be set up correctly by sshd. On Linux, either select to install the XFree86 server at initial install time, or install the appropriate XFree86-4.1.0 (or later) package.
• There are known problems with compiling C++ plugins with the C Plugin Development Kit using gcc-3.0.x on Solaris. If developers wish to use gcc on Solaris, it is recommended that they use gcc-3.1.1 (or more recent) or gcc-2.95.
• The Java API has been successfully tested with most Sun JREs post version 1.1, and with the Microsoft 5.00.3805 JVM. However minor differences in output format and behaviour are evident with pre-1.3.1 JREs - it is recommended that version 1.3.1 or later is used
• Runtime Exceptions (e.g. divide-by-zero, sequence index out of bounds) cannot be caught in this release. In case of a Runtime Exception, the Monitor or subMonitor will be killed by the Correlator
• A number of problems with communicating to an Event Correlator have been traced to a common mis-configuration of Solaris machines, where the machine does not report a fully-qualified hostname when asked (i.e. calls to gethostbyname() return 'host' rather than 'host.domain.com'). To verify if this might be a problem on your installation, on start-up of the Event Correlator check the output line "Running on host ' <hostname>'" and ensure this is a fully-qualified name.
  If the name is not fully-qualified, either fully-qualify the host's entry in its local /etc/inet/hosts file, or change the 'hosts' resolution order in /etc/nsswitch.conf to use NIS or DNS before local hosts files.

Windows

The information regarding Linux platform support below applies to the following Apama products

• Event Manager
• EventStore
• Platform and Development Environment
• Scalability and Management Environment
• Dashboard Studio
• Event Modeler

Platform Notes:

• Event Store is unqualified on NT4.
• Dashboard Studio and Event Modeler require Microsoft Internet Explorer 5.5 or later
• Dashboard Studio and Event Modeler require the Sun Java plug-in for IE.
• The Microsoft Java plugin is considered Unserviceable as it breaks some functionality of the Event Modeler.
• Runtime Exceptions (e.g. divide-by-zero, sequence index out of bounds) cannot be caught in this release. In case of a Runtime Exception, the Monitor or subMonitor will be killed by the Correlator
• Running the Event Correlator on a version of Windows 2000 earlier than Service Pack 2 may result in poor performance in some circumstances. For optimum performance, Apama recommends patching Windows 2000 with Service Pack 2 or later.
• Installation and operation on Windows NT 4 (Service Pack 6) requires that the latest version of Microsoft's Runtime Libraries are installed. The newer version is automatically installed by Microsoft Visual Studio/C++ 6.0 (SP5). Alternatively the libraries may be downloaded from Microsoft as detailed in this knowledge-base article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q259403
• The Java API has been successfully tested with most Sun JREs post version 1.1, and with the Microsoft 5.00.3805 JVM. However minor differences in output format and behaviour are evident with pre-1.3.1 JREs - it is recommended that version 1.3.1 or later is used