Semeru Runtimes installation

The Windows® installer packages are available as standard .msi files, which can be installed interactively or run silently from the command line.

Notes:

• Windows installer packages are supported only on Windows x64 systems.
• The installer is designed for use on a per-machine basis, not per-user basis, so you can have only one installation on a machine for all users.

GUI installation

Use the following steps to install the package interactively from the Windows desktop.

1. Download the .msi package file. Open it to launch the installation program.
2. Read and accept the license if you are happy with the terms.
3. On the Custom Setup screen, select the features and configuration options that you want and optionally change the default installation directory.
   • The following options are available:
     • Adding the install directory to the PATH environment variable
     • Associating .jar files with Java applications
     • Updating the JAVA_HOME environment variable
     • Installing IcedTea-Web (Version 8 only)
     • Associating .jnlp files with the IcedTea-Web application (Version 8 only)
   • The default installation directory depends on the edition of IBM Semeru Runtimes:
     • Open Edition: C:\Program Files\Semeru
     • Certified Edition: C:\Program Files\IBM\ibm-semeru-certified-<release>-<jdk|jre>

   Click Next.

4. Click Install to start the installation.
5. When the installation completes, click Finish to close the program.

Command-line installation

Use the command line to install and configure the Windows package without user interaction, which can be useful for wide scale deployment. Follow these steps:

1. Download the .msi file.
2. Choose the features and configuration options that you want, which are shown in the following table:

   Feature	Description
   FeatureMain	Core IBM® Semeru Runtimes installation (DEFAULT)
   FeatureEnvironment	Updates the PATH environment variable (DEFAULT)
   FeatureJarFileRunWith	Associates .jar files with Java applications (DEFAULT)
   FeatureJavaHome	Updates the JAVA_HOME environment variable
   FeatureIcedTeaWeb	Installs IcedTea-Web
   FeatureJNLPFileRunWith	Associates .jnlp files with IcedTea-web
   FeatureOracleJavaSoft	Updates registry keys HKLM\SOFTWARE\JavaSoft\

   Note: FeatureOracleJavaSoft can be used to prevent an Oracle Java runtime launching from PATH when IBM Semeru Runtimes is uninstalled. If you need to restore the Oracle registry keys, reinstall Oracle Java .

   The following optional parameters can be used to group some features together:

   Parameter	Features
   INSTALLLEVEL=1	FeatureMain,FeatureEnvironment,FeatureJarFileRunWith
   INSTALLLEVEL=2	FeatureMain,FeatureEnvironment,FeatureJarFileRunWith,FeatureJavaHome,FeatureIcedTeaWeb
   INSTALLLEVEL=3	FeatureMain,FeatureEnvironment,FeatureJarFileRunWith,FeatureJavaHome,FeatureIcedTeaWeb,FeatureJNLPFileRunWith

3. IBM Semeru Certified Edition supports different languages. Use the ProductLanguage parameter to open the user interface in a language from the following table:

   Parameter	Language
   ProductLanguage=1031	Germany
   ProductLanguage=3082	Spanish
   ProductLanguage=1036	French
   ProductLanguage=1040	Italian
   ProductLanguage=1041	Japanese
   ProductLanguage=2052	Chinese Simplified
   ProductLanguage=1028	Chinese Traditional (Taiwan)
   ProductLanguage=1042	Korean
   ProductLanguage=1051	Slovak
   ProductLanguage=1029	Czech
   ProductLanguage=1032	Greek
   ProductLanguage=1038	Hungarian
   ProductLanguage=1027	Catalan
   ProductLanguage=1060	Slovenian
   ProductLanguage=2070	Portuguese
   ProductLanguage=1045	Polish
   ProductLanguage=1049	Russian

4. Run the command on the target workstation.

   The following example silently installs the runtime, updates the PATH, associates .jar files with Java applications and defines JAVA_HOME:

   msiexec /i <package>.msi ADDLOCAL=FeatureMain,FeatureEnvironment,FeatureJarFileRunWith,FeatureJavaHome INSTALLDIR="c:\Program Files\Semeru\" /quiet

   Note: You must use INSTALLDIR with FeatureMain.

   The following example silently installs all the features for INSTALLLEVEL=1:

   msiexec /i <package>.msi INSTALLLEVEL=1 /quiet

   The following example, which is only available for IBM Semeru Runtime Certified Edition, will open the user interface in German:

   msiexec /i <package>.msi ProductLanguage=1031

Reinstalling or upgrading

To reinstall the IBM® Semeru Runtimes in silent mode with default features, run the following command:

msiexec /i <package>.msi REINSTALL=ALL /quiet

If you want to upgrade the IBM Semeru Runtimes in silent mode, run the following command:

msiexec /i <package>.msi REINSTALL=ALL REINSTALLMODE=amus /quiet

As described in the installer user guide, the following options can be used with REINSTALLMODE:

• a: Force all files to be installed regardless of checksum or version
• m: Rewrite all required registry entries from the Registry Table that go to the HKEY_LOCAL_MACHINE
• o: Reinstall if the file is missing or is an older version
• u: Rewrite all required registry entries from the Registry Table that go to the HKEY_CURRENT_USER or HKEY_USERS
• s: Reinstall all shortcuts and recache all icons overwriting any existing shortcuts or icons

Setting REINSTALL=ALL is equivalent to REINSTALLMODE=omus

Note: Upgrading .msi files works only for the first 3 digits of the build number because of an MSI limitation. For example:

• Upgrading 8.0.2.1 to 8.0.3.1 works.
• Upgrading 8.0.2.1 to 8.0.2.2 does not work. Uninstall the previous .msi package and install the new one.
• Upgrading 8.0.2.1 to 8.1.2.1 works.
• Upgrading 8.0.2.1 to 11.0.2.1 does not work. IBM does not provide upgrades for major versions. Either keep both installations or uninstall the older one.

Verification

You may optionally check that a Windows installer package has not been corrupted or altered. Follow the guidance on verifying Windows Installer packages.

You may also verify any executable (.exe) and dynamic link library (.dll) files installed by the .msi.

The macOS® installer packages are available as standard .pkg files, which can be installed interactively or run silently from the command line.

Note: The macOS® installer packages are only available for the IBM® Semeru Runtime™ Open Edition.

GUI installation

Use the following steps to install the package interactively from the macOS desktop:

1. Download the .pkg file.
2. Use Finder to navigate to the folder that contains the file. Open the file to launch the installation program or drag the icon to your Application folder.
3. The Introduction screen identifies the target location for the installation, which you can change later in the install process. Click Continue.
4. Read and accept the license, if you are happy with the terms.
5. Optionally change the target location for the installation. Click Install to complete the installation.

Command-line installation

A silent installation allows you to install the macOS package without user interaction, which can be useful for wide scale deployment. You must have administrator privileges. Complete the following steps:

1. Download the .pkg file.
2. Launch the Terminal app (terminal.app).
3. Run the following command:

   installer -pkg <path_to_pkg>/<pkg_name>.pkg -target /</pkg_name></path_to_pkg>

4. Enter the Administrator password.
5. The package installs in the

   /Library/Java/JavaVirtualMachines/ibm-semeru-open-<version>.<jdk|jre>/

Homebrew installation

The IBM® Semeru Runtime™ Open Edition can also be installed using the Homebrew package manager. Run the command:

brew install --cask semeru-jdk-open

Notarization

Use the spctl command to verify that the macOS Installer packages have been notarized. Follow these steps:

1. Launch the Terminal app (terminal.app).
2. Run the following command:

   spctl -a -v --type install <filename>

3. For example:

   spctl -a -v --type install ibm-semeru-open-jdk_x64_mac_11.0.12_7_openj9-0.27.0.pkg

4. If the verification is successful then the command returns:

   <filename>: accepted
   source=Notarized Developer ID
   

Verification

You may optionally manually check the authenticity and integrity of an .pkg package. Refer to the Apple® support article How to verify the authenticity of manually downloaded Apple software updates.

Note: Stand alone .zip packages are only available for the IBM Semeru Runtime Open Edition.

The archive files can be extracted directly in to a directory of your choice in a few easy steps.

The naming format of the archive file includes the following elements:

ibm-semeru-<certified|open>-<jdk|jre>_<architecture>_<operating_system>_<openjdk_level>_openj9-<openj9_level>.<extension>

When extracted, the binary is installed to the following directory:

<openjdk_level>""|-<jre>

Examples:

.tar.gz files

Follow these steps:

1. Download the latest tar.gz file to a directory of your choice.

2. Change to the directory and verify that the download is successful by comparing the checksum information. Run the following command and compare the output with the value on the download page:

   sha256sum <file_name>.tar.gz

   If the checksum values match, the download is successful. If they don't match, repeat this step.

3. Extract the archive file by running the appropriate command.

   On Linux and macOS:

   tar xzf <file_name>.tar.gz

   On AIX:

   gunzip -c <file_name>.tar.gz | tar xf -

4. If you want to add this version of Java to your PATH, run the following command:

   export PATH=$PWD/<install_dir>:$PATH

5. Run the following command to check that Java installed correctly:

   java -version

You may optionally check that an .tar.gz package has not been corrupted or altered. Follow the guidance in the documentation on verifying InstallAnywhere and .tar.gz archive packages.

.zip files

Follow these steps:

1. Download the latest zip file to a directory of your choice.

2. Change to the directory and verify that the download is successful by comparing the checksum information. Run the following command and compare the output with the value on the download page:

   certutil -hashfile .zip SHA256

   If the checksum values match, the download is successful. If they don't match, repeat this step.

3. Extract the archive file by running the following command:

   powershell -Command Expand-Archive -Path .\<file_name>.zip -DestinationPath .</file_name>

4. If you want to add this version of Java to your PATH, run the following command:

   set PATH=%cd%\<install_dir>\bin;%PATH%

5. Run the following command to check that Java installed correctly:

   java -version

Note that .zip packages are not signed. You may validate the executable (.exe) and dynamic link library (.dll) files contained within a .zip by using the same procedure as verifying Windows Installer packages.

The RPM Package Manager installer packages are available as standard .rpm files, which can be installed interactively from the command line.

The naming format of the RPM file includes the following elements:

• Certified edition:

  ibm-semeru-certified-<major version>-<jdk|jre>-<ibm semeru runtimes version>-<release number>.<architecture>.rpm

• Open edition:

  ibm-semeru-open-<major version>-<jdk|jre>-<openjdk version>_<openj9 version>-<release number>.<architecture>.rpm

The binary is installed to the following directory:

• Certified edition: /opt/ibm
• Open edition: /usr/lib/jvm/

Examples:

The following steps describe how to install an RPM package for RHEL:

1. Download the latest rpm file to a directory of your choice.

2. Change to the directory and verify that the download is successful by comparing the checksum information. Run the following command and compare the output with the value on the download page:

   sha256sum <file_name>.rpm

   If the checksum values match, the download is successful. If they don't match, repeat this step.

3. Install the RPM package with the following command:

   yum install <file_name>.rpm

   The -v option will show verbose output. The -h option will display hash marks to show the progress of the install.

   If the installation fails due to RHEL or SLES dependencies, check for the distro specific packages before reinstalling. For distro specific libraries for installation, refer to the following links:

   • SLES : https://software.opensuse.org/search?baseproject=ALL
   • RHEL : https://access.redhat.com/downloads/content/package-browser

4. Verify that the package is available run the following command:

   rpm -q ibm-semeru-<package name>

Verification

You may optionally check that an .rpm package has not been corrupted or altered. Follow the guidance in the verification documentation on verifying RPM Package Manager packages.

IBM Semeru Runtime Images are available from the IBM Cloud® Container Registry, which is the public Docker registry for IBM Cloud.

These Images use Red Hat's Universal Base Image (UBI) as the operating system.

The container images use the following namespace:

icr.io/appcafe/ibm-semeru-runtimes

The container image tags contain edition and release information and are available in two formats:

• Multi-architecture:

  <edition>-<release>-<image_type>-<base_image_type>

• Platform specific:

  <edition>-<release>-<image_type>-<base_image_type>-<architecture>

Where:

• <edition> is one of the following values:

  • certified: IBM Semeru Runtime™ Certified Edition
  • open: IBM Semeru Runtime Open Edition

• <release> is one of the following values:

  • 21: IBM Semeru Runtimes, Version 21
  • 17: IBM Semeru Runtimes, Version 17
  • 11: IBM Semeru Runtimes, Version 11
  • 8: IBM Semeru Runtimes, Version 8

• <image_type> is one of the following values:

  • jdk: IBM Semeru Runtimes jdk package
  • jre: IBM Semeru Runtimes jre package

• <base_image_type> is one of the following values:

  • ubi: Redhat Universal Base Image (UBI), version 8.x, where x is the latest available version.
  • ubi-minimal: Redhat Universal Base Image Minimal (UBI Minimal), version 8.x, where x is the latest available version.
  • focal: Ubuntu 20.04
  • jammy: Ubuntu 22.04 (Limited support. See Notes below)

• <architecture> is one of the following values:

  • aarch64: Linux on ARM64
  • amd64: Linux on x86
  • ppc64le: Linux on POWER LE
  • s390x: Linux on IBM Z

For example:

• The multi-architecture tag “open-11-jdk-ubi” is used to pull the IBM Semeru Runtime Open Edition, Version 11, JDK UBI image.
• The tag “open-11-jdk-ubi-s390x” is used to pull the IBM Semeru Runtime Open Edition Version 11, JDK UBI image for Linux on IBM Z.

Notes:

• IBM Semeru Runtimes, Version 8 is only available for the Open Edition.
• The jammy base image type is supported only on the arm64, s390x and amd64 architectures. The jammy base image type is not supported on the ppc64le architecture.
• The IBM Semeru Runtime Images on the IBM Cloud Container Registry share the same tags as the IBM Semeru Runtimes Official Images on Docker Hub.

• To list the available IBM Semeru Runtime Images use the IBM Cloud CLI command:

  ibmcloud cr images --restrict appcafe/ibm-semeru-runtimes

• You can pull an image from the IBM Cloud Container Registry, without an IBM Cloud account. For example:

  • docker pull icr.io/appcafe/ibm-semeru-runtimes:open-11-jdk-ubi

  • docker pull icr.io/appcafe/ibm-semeru-runtimes:open-11-jdk-ubi-minimal

License

The UBI images and associated scripts are licensed under the Apache License 2.0.

Licenses for the products installed within the images:

• IBM® Semeru Runtime™ Open Edition, All versions: GNU General Public License, version 2, with the Classpath Exception.
• IBM® Semeru Runtime™ Certified Edition, Version 11: International License Agreement for Non-Warranted Programs.
• IBM® Semeru Runtime™ Certified Edition, Version 17: International License Agreement for Non-Warranted Programs.
• IBM® Semeru Runtime™ Certified Edition, Version 21: International License Agreement for Non-Warranted Programs.

As with all images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the Docker repo-info repository in the ibm-semeru-runtimes directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.