UNIX Installation Requirements

Many modern data adapters, server side graphics, and other services use a Java JVM to implement execution. These require a Java JVM to be installed (separate from the server) and that the server be configured to use it. You may install a commercial Oracle Java JRE, Oracle Java SDK (also known as JDK) or an open source OpenJDK JDK (from such sites as adoptopenjdk.net or azul.com).

The minimum Java JVM release level is 1.8 or higher, due to required internal components of the server. The Java Listener will not start unless the applicable minimal level for the platform is used by setting JAVA_HOME/JDK_HOME values.

The following URL has Java EOL and EOSL information:

http://www.oracle.com/technetwork/java/eol-135779.html

You may install a commercial Oracle Java JRE (if available), Oracle Java SDK (also known as JDK, if available), an open source OpenJDK JDK (from such sites as adoptopenjdk.net or azul.com), or the Java that may have come with the operating system (or available separately from the operating system vendor). The JRE or SDK build version must also match the 32-bit or 64-bit bit type of the server. When you install a Java SDK, the JRE component (where the JVM lives) is also included, so either is allowed. However, if using the servlet feature, the Java SDK is required for access to the jar command, so an SDK installation is generally preferred over a JRE installation.

While OpenJDK uses a different directory organization from the Oracle JDK and JRE, the Azul OpenJDK directory structure is more like the Oracle JDK and JRE, plus the directory structure may also vary from implementations delivered by the operating system vendor. The server is aware of all of these implementations when it attempts to locate and set up use of the actual Java JVM DLL (so you can use JAVA_HOME= or JDK_HOME= to point at the desired implementation).

Some third party Java JDK/JRE providers, such as Adpotopenjdk.com, provide not only classic JDK and JRE implementations (also known as Hotspot), but also Eclipse Open9J Java implementations. While the server Java Listener will start with either implementation, it has been found that some third party JDBC DBMS drivers do not work with some Adpotopenjdk.com Open9J implementations (Vertica and Snowflake JDBC Drivers, in particular, on Windows). If your site chooses to use an Open9J JVM implementation or other third party JVM provider and experiences JDBC DBMS problems, a classic Java (Hotspot) implementation from Oracle or Adpotopenjdk.com should be installed and tested to confirm that the server software and DBMS setup are not at issue (and to correct, if needed). If the Open9J Java implementation is still desired, the site should follow up with the Open9J JVM or DBMS provider as to why this combination fails.

Installation of any third-party Java JVM that follows the same directory structure as any of the known implementations should work, but use of such alternate packages should be self-certified.

Use explicit variables to specify the Java JVM location:

• For Java JDK, set JDK_HOME (to the install home location) in the environment or server environment start-up file (edaenv.cfg).
• For Java JRE, set JAVA_HOME (to the install home location) in the environment or server environment configuration file (edaenv.cfg).

If JDK_HOME and JAVA_HOME variables are both declared, the JDK_HOME value will be used.

To change or add a variable in the server environment start up file (EDACONF bin/edaenv.cfg), either edit the file in a text editor before starting the server or:

1. Start the server (services like Java Listener may fail until configured and the server is restarted).
2. Open the Web Console and sign in using an administrator ID.
3. Select Workspace from the main menu.
4. In the navigation pane, open the Configuration Files and Miscellaneous folders.
5. Right-click Environment - edaenv.cfg, and click Edit.
6. Make the desired edit.
7. Save the file.
8. Restart the server (changes are not effective until server is restarted).

The format of edaenv.cfg variables is one per line in name=value pairs. Spaces before and after the equal sign are optional. Values with embedded spaces do not have to be enclosed in quotation marks.

To add classes to the JVM class path for customer-written CALLJAVA applications, set and export the CLASSPATH variable to the operating system level before server start-up or use the Web Console to set the Java Listener IBI_CLASSPATH property.

If JVM-based adapters or features are not required, and the JVM environment is not configured, the message Failed to find JVM is normal and can be ignored.