Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 6. Installing JBoss EAP by using the RPM installation method

You can install JBoss EAP by using RPM packages on supported installations of Red Hat Enterprise Linux 8, and Red Hat Enterprise Linux 9.

6.1. Subscribing to the JBoss EAP software repository

If you want to install JBoss EAP by using the RPM installation method, you must subscribe to the Red Hat Enterprise Linux Server base software repository, and a minor JBoss EAP repository.

Prerequisites

  • You have set up an account on the Red Hat Customer Portal.
  • Your JBoss EAP host is running on a supported operating system.
  • You have subscribed to the Red Hat Enterprise Linux Server base software repository.
  • You have administrator privileges on the server.

Procedure

  1. Enter the Red Hat Subscription Manager.

    Important

    To subscribe to the Red Hat Enterprise Linux server base repository and a minor JBoss EAP repository, enter one of the following commands:

  2. Replace EAP_MINOR_VERSION with your intended JBoss EAP minor version. For example, 8.0.

    Copy to Clipboard Toggle word wrap 
    subscription-manager repos --enable=jb-eap-EAP_MINOR_VERSION-for-rhel-RHEL_VERSION-ARCH-rpms

Additional resources

6.2. Installing JBoss EAP by using the RPM installation method

Prerequisites

  • You have set up an account on the Red Hat Customer Portal.
  • Your JBoss EAP host is running on a supported operating system.
  • You have administrator privileges on the server.
  • You have subscribed to the Red Hat Enterprise Linux Server base software repository.
  • You have subscribed to the JBoss EAP8 software repository.

Procedure

  1. Install JBoss EAP and JDK 17.

    Copy to Clipboard Toggle word wrap 
    dnf groupinstall jboss-eap8

  2. Install JBoss EAP and JDK 11. JDK 11 is available for Red Hat Enterprise Linux 8 and later:

    • Red Hat Enterprise Linux 8:

      Copy to Clipboard Toggle word wrap 
      dnf groupinstall jboss-eap8-jdk11
Note

If the specified version of the JDK is not already installed on the system, the groupinstall command automatically installs this version of the JDK. If a different version of the JDK is already installed, the system contains multiple installed JDK versions after you run the preceding command.

If multiple JDK versions are installed on your system after you run the groupinstall command, check which JDK version JBoss EAP is using. By default, JBoss EAP uses the system default JDK.

  1. Modify the default JDK in either of the following ways:

    • Change system wide configuration by using the alternatives command:

      Copy to Clipboard Toggle word wrap 
      alternatives --config java
    • Change the JDK that uses JBoss EAP by using the JAVA_HOME property. Your installation is complete. The default EAP_HOME path for the RPM installation is /opt/rh/eap8/root/usr/share/wildfly.
Important

When you install JBoss EAP by using RPM packages, you cannot configure multiple domain or host controllers on the same machine.

Additional resources

  • Setting up the EAP_HOME variable, in the JBoss EAP Installation Guide.
  • Subscribing to a Minor JBoss EAP repository, in the JBoss EAP Installation Guide.
  • For more information about changing the JAVA_HOME property, see the RPM Service Configuration Properties section of the Configuration Guide.

6.3. Configuring JBoss EAP RPM installation as a service on RHEL

You can configure the Red Hat Packet Manager (RPM) installation to run as a service in Red Hat Enterprise Linux (RHEL). An RPM installation of JBoss EAP installs everything that is required to run JBoss EAP as a service

Run the appropriate command for your RHEL, as demonstrated in this procedure. Replace EAP_SERVICE_NAME with either eap8-standalone for a standalone JBoss EAP server, or eap8-domain for a managed domain.

Prerequisites

  • You have installed JBoss EAP as an RPM installation.
  • You have administrator privileges on the server.

Procedure

  • For Red Hat Enterprise Linux 8 and later:

    Copy to Clipboard Toggle word wrap 
    systemctl enable EAP_SERVICE_NAME.service

Additional resources

6.4. Changing the software subscription from one JBoss EAP repository to another

You can change the software subscription from one JBoss EAP repository to another based on the following conditions:

  • If you are changing to the next minor JBoss EAP version, you can change from a minor repository to another minor repository. For example, you can change from JBoss EAP 8.0 to JBoss EAP 8.1, but you cannot change from JBoss EAP 8.0 to JBoss EAP 8.2.

Prerequisites

  • You have installed JBoss EAP by using the RPM installation method.
  • You have chosen a repository.
  • You have applied all the applicable updates to your JBoss EAP application.
  • You have administrator privileges on the server.

Procedure

  1. Unsubscribe from the existing repository and subscribe to the new repository by using the Red Hat Subscription Manager.

    Copy to Clipboard Toggle word wrap 
    subscription-manager repos --disable=EXISTING_REPOSITORY --enable=NEW_REPOSITORY

6.5. Uninstalling JBoss EAP using the RPM installation method

Note

To avoid potential issues, do not uninstall a JBoss EAP installation that you have installed from RPM packages.

Because of the nature of RPM package management, uninstalling JBoss EAP might not completely remove all installed packages and dependencies. Uninstalling JBoss EAP might also leave the system in an inconsistent state because of missing package dependencies.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat, Inc.