Windows 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.

The minimum Java JVM release level is 1.8.0_20 or higher, due to required internal components of the server. The Java Listener will not start properly (and will show errors in edaprint) if 1.8.0_20 (or higher) is not in use.

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, Oracle Java SDK (also known as JDK), or an open source OpenJDK JDK (from such sites as adoptopenjdk.net or azul.com). 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 you are using the servlet feature, a Java SDK (JDK) is required for access to the jar command, so a SDK (JDK) installation is generally preferred over a JRE installation.

New to 7707 and higher server release levels is an automatic Windows Registry look-up feature for the latest highest commercial Oracle Java available on the system. This feature only requires that an appropriate 1.8.0_20 or higher commercial Oracle Java JRE or SDK of the correct bit size has been installed on the system, using the standard commercial Oracle Java Installer, which registers the installation to the Windows Registry. In addition, it requires that no explicit variables be set on the system that would cause an override. If a commercial Oracle JRE and SDK are both installed (and no override variables are set), the SDK will be used.

The automatic look-up feature does not apply to a commercial Oracle Java JRE or SDK that has simply been copied to disk using an archive tool such as winzip or 7zip, as this method does not register the installation. If this has been done, use explicit variables to configure the server.

The automatic look-up feature also does not apply to OpenJDK JDK, as its standard installation method is to unzip (copy) to disk, and the installation is not registered. In addition, the automatic look-up feature does not apply to the Azul OpenJDK Client (also known as JRE) installer (or any other site providing a Java installer that registers its location), as its registry information differs from the Oracle entries.

Explicit JAVA_HOME or JDK_HOME variables, described below, may be used to manually configure Java access (to override locations found by the automatic Java look-up feature or because an unregistered Java is in use). 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. The server is aware of both implementations when it attempts to locate and setup use of the actual Java JVM DLL (so you should 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.

At server start-up time, if none of the above is true, the server Java Listener may still start if applicable JVM directories happen to be on the system PATH, but this not a recommended method, as it is not explicit.

If an appropriate JVM is not found at server start-up time, various failed to find JVM messages displays in EDAPRINT. Reviewing and following the instructions in this section will usually correct the problem.

JSCOM3 is the actual process name for the Java Services Listener and those terms, as well as the term Java Listener, are often used interchangeably.

To use explicit variables to specify the Java JVM location, do the following:

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

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 (a start menu icon is also available under the configure folder) 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 select 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 the CLASSPATH variable at the operating system level before server start-up or use the Web Console to set the Java Listener IBI_CLASSPATH property.

If Java JVM-based adapters or features are not required, and no Java is installed (or is below the minimum level), various EDAPRINT Java Listener fail messages are normal, acceptable, and can be ignored. However, this is not a recommended situation. If you make a support call, please make the representative aware of this, as it may take them unnecessary time to analyze the situation and realize that these messages are normal for your configuration and not part of the problem being called in.