In order for the IAF to successfully locate and load C/C++ transport layer and codec plug-ins, the location(s) of these must be added to the environment variable LD_LIBRARY_PATH on UNIX, or PATH on Windows.

A transport or codec plug-in library may depend on other dynamic libraries, whose locations should also be added to the LD_LIBRARY_PATH or PATH environment variable as appropriate for the platform. The documentation for a packaged adapter will state which paths should be used for the adapter’s plug-ins. Note that on the Windows platform, the IAF may generate an error message indicating that it was unable to load a transport or codec plug-in library, when in fact it was a dependent library of the plug-in that failed to load. On UNIX platforms the IAF will correctly report exactly which library could not be loaded.

When using the IAF with a Java adapter the location of the Java Virtual Machine (JVM) library is determined in the same way. On UNIX systems the LD_LIBRARY_PATH environment variable will be searched for a library called libjvm.so, and on Windows the IAF will search for jvm.dll, first in the third_party\jre\bin\server and third_party\jre\bin directories of the Apama installation referenced by the APAMA_HOME environment variable, then in any other directories on the PATH environment variable. Using a JVM other than the one shipped with Apama is not supported and Technical Support will generally request that any Java-related problems with the IAF are reproduced with the supported JVM.

To develop, build, and test an Apama application, the recommendation is that you use Oracle JDK 8. The minimum you can use is JDK 7.

To deploy an Apama application, the recommendation is that you use Oracle JRE 8, which is the version that Apama provides. Use of any JRE other than the one that Apama ships with is discouraged.

See Java configuration (optional) for information about how the location of Java plug-in classes are determined.