JRE support

As of version 9.50, Service Manager (SM) adds the support of Open Java Development Kit (OpenJDK) for all SM components that require a JRE or JDK to work.

Important Out-of-box, an OpenJDK JRE is bundled with the Windows Server, Windows Client, and Service Portal so that you do not have to manually install a JRE for them. For the other components, including the Linux Server installation package, you need to manually install either an OpenJDK JRE or Oracle JRE.

You have the option to use either Oracle JDK or OpenJDK with Service Manager. For the supported versions of Oracle JRE and OpenJDK JRE, see the Service Manager Support Matrix.

JRE bitness

For the Server (both Windows and Linux) and Windows Client: use 32-bit JRE.

For the rest of the components: use a JRE with the same bitness as the operating system.

How to use OpenJDK with Service Manager

Use OpenJDK with SM components as described in the following table.

Caution Service Manager does not support enabling FIPS mode with OpenJDK. If you want to enable FIPS mode for Service Manager, use Oracle or IBM JDK as needed. For more information, see Configure Java for FIPS mode.

Component(s) How to use OpenJDK
  • Windows Server
  • Windows Client
An OpenJDK jre folder is already bundled with the components. No installation is required.
Linux Server

Follow the steps for specific for your Linux operating system.

Important For Red Hat Linux 7.1, the 32-bit OpenJDK cannot be installed by the yum command. You need to upgrade to version 7.2 or higher or use Oracle JDK instead.

  1. Make sure your Linux host has Internet access.
  2. Go to the SM Server installation directory, run one of the following scripts as a superuser (such as root) according to your Linux platform:

    For Red Hat Enterprise Linux or Oracle Enterprise Linux: installOpenJDK.sh -i4sm

    For Novell SUSE Linux Enterprise: installOpenJDKSUSE.sh -i4sm

    Running each of the scripts will install OpenJDK and the related 32-bit dependent libraries. Each script will also install a “fontconfig” rpm that is required for exporting reports generated by the Service Manager Reports functionality.

    Note If your Linux host has no Internet access, you can use 32-bit Oracle JDK. Alternatively, do the following to use OpenJDK:

    1. Install 32-bit OpenJDK by yourself.
    2. Update the JAVA_HOME environment variable to make it point to the OpenJDK jre directory.
    3. From the SM Server's RUN directory, run "setupLink.sh jre" as the owner of the Service Manager installation directory. This will create a symbolic link for the OpenJDK JRE.
  • Web tier
  • SRC
  • Mobility Client

Note If the web tier or Mobility Client is deployed on WebSphere, IBM JDK must be used instead.

  1. Install an appropriate version of OpenJDK on the Tomcat host. You can download it from https://zulu.org/.
  2. On the Tomcat host, update the JAVA_HOME variable to make it point to the OpenJDK.

Solr Search Engine
  1. Install an appropriate version of OpenJDK according to the operating system bitness of the Tomcat host. You can download it from https://zulu.org/.
  2. Update the JAVA_HOME variable on the Tomcat host to make it point to the OpenJDK.

How to use Oracle JDK with Service Manager

Note Before you proceed, make sure that Oracle JDK or JRE is already installed on the corresponding system (SM Server, Windows Client, and so on).

Use Oracle JDK as described in the following table.

Component How to use Oracle JDK
Windows Server
  1. Rename the <SM Server installation path>\RUN\jre folder to create a backup copy.
  2. Download an appropriate version of 32-bit Oracle JRE from the Oracle website.
  3. Copy the Oracle jre folder to the SM Server's RUN folder.
Windows Client
  1. Rename the Client's jre folder to create a backup copy. For example:

    C:\Program Files (x86)\HPE\Service Manager 9.52\Client\jre.bak

  2. Download an appropriate version of Oracle JRE from the Oracle website.
  3. Copy the Oracle jre folder to the <Service Manager installation path>\Client folder.
Linux Server
  1. If there is an existing jre link or jre folder in the Server's RUN directory, remove it.
  2. Update the JAVA_HOME environment variable to make it point to the Oracle JRE.
  3. From the Server's RUN directory, run the "setupLinks.sh jre" command as the owner of the Service Manager installation directory. This will create a symbolic link for the Oracle JRE.

Web tier

SRC

Mobility Client

Note If these components are deployed on WebSphere, you must use IBM JDK instead.

  1. Install an appropriate version of Oracle JRE according to the operating system bitness of the Tomcat host.
  2. Update the JAVA_HOME variable on the Tomcat host to make it point to the Oracle JRE.
Solr Search Engine
  1. Install an appropriate version of Oracle JRE according to the operating system bitness of the Tomcat host.
  2. Update the JAVA_HOME variable on the Solr Search Engine host to make it point to the Oracle JDK.