Installing and using Red Hat build of OpenJDK 17 for Windows

Red Hat build of OpenJDK 17

Red Hat Customer Content Services

Abstract

Red Hat build of OpenJDK 17 for Windows is a Red Hat offering on the Microsoft Windows platform. The Installing and using Red Hat build of OpenJDK 17 for Windows guide provides an overview of this product and explains how to install the software and start using it.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Providing feedback on Red Hat documentation

We appreciate your feedback on our documentation. To provide feedback, you can highlight the text in a document and add comments.

This section explains how to submit feedback.

Prerequisites

  • You are logged in to the Red Hat Customer Portal.
  • In the Red Hat Customer Portal, view the document in Multi-page HTML format.

Procedure

To provide your feedback, perform the following steps:

  1. Click the Feedback button in the top-right corner of the document to see existing feedback.

    Note

    The feedback feature is enabled only in the Multi-page HTML format.

  2. Highlight the section of the document where you want to provide feedback.

  3. Click the Add Feedback pop-up that appears near the highlighted text.

    A text box appears in the feedback section on the right side of the page.

  4. Enter your feedback in the text box and click Submit.

    A documentation issue is created.

  5. To view the issue, click the issue tracker link in the feedback view.

Chapter 1. Red Hat build of OpenJDK 17 for Microsoft Windows installation options

Red Hat build of OpenJDK 17 for Microsoft Windows can be installed using an archive or through a graphical user interface using an MSI-based installer.

Depending on your circumstance, use one of the following installation methods:

Chapter 2. Installing Red Hat build of OpenJDK 17 for Microsoft Windows with the archive

This procedure describes how to manually install Red Hat build of OpenJDK 17 for Microsoft Windows using the archive.

Procedure

  1. Download the archive of Red Hat build of OpenJDK 17 for Microsoft Windows.

  2. Extract the contents of an archive to a directory of your choice.

    Note

    Extracting the contents of an archive to a directory path that does not contain spaces is recommended.

  3. Update the PATH as below:

    1. Add the bin directory contained in your Red Hat build of OpenJDK 17 for Microsoft Windows installation path to the %PATH% environment variable: 

      C:\> setx /m PATH "%PATH%;C:\Progra~1\RedHat\java-17-openjdk-17.0.0.0.35-1\bin"

      If the path contains spaces, use the shortened path name.

    2. Restart Command Prompt to reload the environment variables.

  4. Verify the Red Hat build of OpenJDK 17 for Microsoft Windows is successfully installed, run java -version command in a command prompt and you must get the following output: 

    openjdk version "17" 2021-09-14 LTS
OpenJDK Runtime Environment 21.9 (build 17+35-LTS)
OpenJDK 64-Bit Server VM 21.9 (build 17+35-LTS, mixed mode, sharing)

  5. The %JAVA_HOME% environment variable must also be set to use some developer tools. Set the %JAVA_HOME% environment variable as follows:

    1. Open Command Prompt as an administrator.

    2. Set the value of the environment variable to your Red Hat build of OpenJDK 17 for Microsoft Windows installation path: 

      C:\> setx /m JAVA_HOME "C:\Progra~1\RedHat\java-17-openjdk-17.0.0.0.35-1"

      If the path contains spaces, use the shortened path name.

    3. Restart Command Prompt to reload the environment variables.

Chapter 3. Updating Red Hat build of OpenJDK 17 for Microsoft Windows using the archive

Red Hat build of OpenJDK 17 for Microsoft Windows can be manually update using the archive.

Procedure

  1. Download the archive of Red Hat build of OpenJDK 17.

  2. Extract the contents of an archive to a directory of your choice.

    Note

    Extracting the contents of an archive to a directory path that does not contain spaces is recommended.

  3. On Command Prompt, update JAVA_HOME environment variable as follows:

    1. Open Command Prompt as an administrator.

    2. Set the value of the environment variable to your Red Hat build of OpenJDK 17 for Microsoft Windows installation path: 

      C:\> setx /m JAVA_HOME "C:\Progra~1\RedHat\java-17-openjdk-17.0.0.0.35-1"

      If the path contains spaces, use the shortened path name.

    3. Restart Command Prompt to reload the environment variables.

  4. Set the value of PATH variable if it is not set already: 

      C:\> setx -m PATH "%PATH%;%JAVA_HOME%\bin";
  5. Restart Command Prompt to reload the environment variables.

  6. Verify that java -version works without supplying the full path. 

    C:\> java -version
openjdk version "17" 2021-09-14 LTS
OpenJDK Runtime Environment 21.9 (build 17+35-LTS)
OpenJDK 64-Bit Server VM 21.9 (build 17+35-LTS, mixed mode, sharing)

Chapter 4. Installing Red Hat build of OpenJDK with the MSI installer

This procedure describes how to install Red Hat build of OpenJDK 17 for Microsoft Windows using the MSI-based installer.

Procedure

  1. Download the MSI-based installer of Red Hat build of OpenJDK 17 for Microsoft Windows.
  2. Run the installer for Red Hat build of OpenJDK 17 for Microsoft Windows.
  3. Click Next on the welcome screen.
  4. Check I accept the terms in license agreement, then click Next.
  5. Click Next.
  6. Accept the defaults or review the optional properties.
  7. Click Install.
  8. Click Yes on the Do you want to allow this app to make changes on your device?.

  9. Verify the Red Hat build of OpenJDK 17 for Microsoft Windows is successfully installed, run java -version command in the command prompt and you must get the following output: 

    openjdk version "17" 2021-09-14 LTS
OpenJDK Runtime Environment 21.9 (build 17+35-LTS)
OpenJDK 64-Bit Server VM 21.9 (build 17+35-LTS, mixed mode, sharing)

Chapter 5. Red Hat build of OpenJDK MSI installer components

You can set the following Red Hat build of OpenJDK 17 for Microsoft Windows MSI-based installer components. Setting these components is optional. If these components are not set, the default settings will be used.

jdk
Java Development Kit (JDK) files. Defaults to true, meaning that the jdk component is enabled.
jdk_registry_runtime

A set of Windows registry keys that other software can use to locate JDK installation files. Defaults to true, meaning that the jdk_registry_runtime component is enabled. This component includes the following registry keys: 

HKLM\Software\JavaSoft\JDK\<version>, entries:
    JavaHome: <INSTALLDIR>
    RuntimeLib: <INSTALLDIR>\bin\server\jvm.dll

HKLM\Software\JavaSoft\JDK, entries:
    CurrentVersion: <version>
jdk_env_path
Appends <INSTALLDIR>\bin to the system %PATH% environment variable.
jdk_env_java_home
Sets <INSTALLDIR> to the system %JAVA_HOME% environment variable.
jdk_env_vendor_java_home
Sets <INSTALLDIR> to the system %REDHAT_JAVA_HOME% environment variable.
jdk_registry_jar
Association for JAR files. Launch JAR files with the Red Hat build of OpenJDK context menu.
jmc
JDK Mission Control files, installed into <INSTALLDIR>\missioncontrol.
jmc_env
Appends <INSTALLDIR>\missioncontrol to the system %PATH% environment variable.

Appendix A. MSI-based installer properties

The Red Hat build of OpenJDK for Windows MSI-based installer includes the JDK Files component and the following optional properties:

Table A.1. Red Hat build of OpenJDK for Windows MSI-based installer properties

PropertyDescriptionDefault value

OpenJDK Runtime - Windows Registry

Sets registry keys that other software can use to locate JDK installation files.

Yes

OpenJDK Runtime - Path Variable

Adds the Runtime to the Path variable so it is available from the command line.

Yes

OpenJDK Runtime - JAVA_HOME System Variable

JAVA_HOME is used by some programs to find the Java runtime.

No

OpenJDK Runtime - REDHAT_JAVA_HOME System Variable

REDHAT_JAVA_HOME can be used by some programs to find the Red Hat build of OpenJDK runtime.

No

OpenJDK Runtime - Jar Files Association

This enables Jar files to be run from within Windows Explorer.

No

Mission Control - Files

Contains files that are installed in the <installdir>\missioncontrol directory.

No

Mission Control - Path Variable

Appends <installdir>\missioncontrol to the system PATH environment variable.

No

Revised on 2023-08-15 12:07:46 UTC

Legal Notice

Copyright © 2023 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.