ImageMaster 9 is a JEE application, which requires a Java Development Kit (JDK). It is recommended using the latest JDK update. The approved version numbers for supported application servers and the required JDK versions are listed in the compatibility guide [T Compatibility Guide].
For better performance use Java ≥ 11 with a supported JDK version according to the compatibility guide.
You can download Java, for example for OpenJDK, from open-source package repositories or further commercial distributors. A project team shall think carefully about the Java strategy and consider to use a commercial OpenJDK distribution if they need support for Java. This can be required by security regulations like the PSA/SDSK process within the German Telekom.
Check or update Java JDK
You can check the installed version and the current patch level to avoid later errors and problems by the following java command:
$> java –version
Check if the currently used Java version in your environment is supported by ImageMaster and replace this by a newer version if required:
-
To make the application server use the correct Java version, set the environment variable:
JAVA_HOME
-
A typical practice also is to use a soft link instead of a real directory as Java home.
Illustration of commands to install newer JDK on Linux
There are different ways you can install a Java JDK, where details depend on the used operating system and on the fact if you can directly download into your environment. Below is just an example, assuming that “yum” can be used for an installation and a soft link can be adjusted to set your Java home directory.
All given Java versions and related directory or filenames are just examples. You must make sure to use a supported version for your environment:
-
Identify current Java version:
# java -version
-
Update / install newer Java JDK (this is possible with yum, for example, on certain systems):
# yum install java-...-openjdk
-
Identify Java home location:
# echo $JAVA_HOME
/opt/javahome
-
Investigate the Java home directory item:
# ll /opt/javahome
lrwxrwxrwx. 1 root root 22 May 10 06:20 javahome -> /opt/java/jdk...
This is a symbolic link. In this example it is assumed that it can be replaced and there are no other applications depending on exactly this JDK version.
-
Remove this soft link that points to the current Java home directory:
# rm /opt/javahome
-
Replace it by a new one, which points to the new Java home (resulting from the yum installation above), for example:
# ln -s /usr/lib/jvm/java-... javahome
(In the example above the patch level in the version number was replaced by “xxx”. This should represent a supported patch level in a real scenario and the complete name is only supposed to be an example.)
The last command has created a soft link with a new target location:
# ll /opt/javahome
lrwxrwxrwx. 1 root root 60 May 10 12:18 /opt/javahome -> /usr/lib/jvm/java...
Instead of the soft link approach you could also set the JAVA_HOME environment variable to point to the correct path, which is typically done via the script “.bashrc” in corresponding Linux environments.
When the installation of the new JDK is finished, verify that the new version is active:
# java -version
openjdk version "..."
Related information