IBM i Installation Requirements

If Java-based adapters, server-side graphics, XBRL, or user-written CALLJAVA applications are to be used, a Java Runtime Environment (JRE) JVM must be installed on the machine, and the server must be configured to use it.

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 properly (and will show errors in edaprint) if 1.8 (or higher) is not in use.

The following URL has Java EOL and EOSL information:

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

ON IBM i5, Java is a system installed option and there is no differentiation between JRE and SDK, but the build version in uses must also match the 32-bit or 64-bit bit type of the server.

By default, the server uses the system default Java level and directories. If JVM is found with the correct bit size and level (1.8+), the Java Listener will start and send the start message to edaprint, in which case no further configuration is needed. If 1.8 is not the default and the site does not want it as the default, then an explicit set up variable must be configured.

If JVM loading fails, the server will start, but not the Java Listener. This should be corrected. The default IBM i Java level may be set at a system level, however, changing this may affect other processes, so control is best done at the server level. For V7R2 (or higher), this is done by setting the following in the server environment file, edaenv.cfg,

 JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk80/32bit

The location of the default JVM on IBM i is controlled by the object QSYS/QJVAJNI. This is normally on the system path, so you do not need to do anything to fulfill basic JVM find requirements. However, if the default JVM level of the machine is not 1.8 or higher, corrective action may be required to access the correct JVM level.

If the default JVM is not found or is set to an appropriate release at server start time, a Failed to find JVM message will be displayed. Further Java Services debugging information about loading the JVM will be written to the server start log, indicating JSCOM3 start failed, as well as additional information that may be useful in resolving the problem. JSCOM3 is the actual process name for the Java Services Listener, and the terms are often used interchangeably.

The easiest way to determine the current default for the server iadmin ID is to issue the command QSH CMD('java -version'), which will display the default release level for the ID.

There are several choices on how to address using the correct JVM level, but as of V7R2, the steps no longer vary by operating system.

• Change the Java (5761-JV1) install options to point at the desired JVM level as a machine default. This may or may not be desirable based on other applications that may be using Java.
• Set JAVA_HOME to point at a desired JVM release level.

The various Java releases and PTF releases that may be available will be found in the following folder:

/QOpenSys/QIBM/ProdData/JavaVM 

For example:

/QOpenSys/QIBM/ProdData/JavaVM/jdk70/32bit 
/QOpenSys/QIBM/ProdData/JavaVM/jdk70/64bit 
/QOpenSys/QIBM/ProdData/JavaVM/jdk80/32bit 
/QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit

To use the JVM from one of these releases, specifically for the server iadmin ID (if it is not already the system default), set the JAVA_HOME variable to point at a 32bit JDK. For example:

JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk80/32bit 

The variable may be set in any of the following ways:

• As a system variable set from the profile of the server iadmin ID, using INLPGM exit, a JOBD RQSDTA() CL option, or any number of other methods for setting system variables within the environment of a job.
• As an exported QSH variable in any script that is used to call the edastart script.
• As a system variable in any customized CL that is used to call the QSH IFS edastart script, or as an export variable within the QSH portion of the CL.
• Add to the edaenv.cfg environment configuration file of the server.

Formerly, a -Djava class property could be used to control the Java JVM release level, however, this method is no longer supported as of V7R2. If this method was used previously under V7R1, and the machine is upgraded to V7R2, the parameter should be removed and the server must be configured using V7R2 methods (described above).

To change or add operating system environment variables, set and export the variable in a .profile, script, or CL that always gets called during a server start. It is very common to place variables in the server edastart script, but it is recommended that they be placed in a script that in turn calls edastart (so that the edastart script remains vanilla).

To change or add a variable in a 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 log on 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 (changes are not effective until restart).

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 require quoting. Variables are always uppercase.

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 by using the Web Console to access the Java Listener:

1. Select Workspace from menu bar.
2. Open the Java Services folder.
3. Right-click DEFAULT and select Properties.

   The Java Services Configuration pane opens.

4. Expand the Class Path section.
5. Add the desired full path jar names (one per line).
6. Click Save and Restart Java Services.

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.