JBoss EAP Installation Methods

Red Hat JBoss Enterprise Application Platform 8-beta

Downloading and installing JBoss EAP using the archive installation method on RHEL and Microsoft Windows server

Red Hat Customer Content Services

Abstract

Downloading and installing JBoss EAP using the archive installation method on RHEL and Microsoft Windows server.

Chapter 1. Installing and uninstalling JBoss EAP using archive installation method

1.1. JBoss EAP installation methods

You can choose to install JBoss EAP using any of the three types of installation methods:

  • Installer method
  • Archive installation method
  • RPM installation method
Note

This documentation only covers the archive installation process.

Depending on your requirements, each installation method is useful in certain situations.

The following table provides a brief overview of each type of installation methods.

Table 1.1. Installation Methods

MethodDescription

Installer installation

  • You can run the installer on a console or as a graphical wizard. Both options provide step-by-step instructions for installing and configuring the server instance. The Installer Installation is the preferred method to install JBoss EAP on all supported platforms.
  • The graphical installer also provides an additional setup option, including Quickstarts and configuration of the Maven repository.

Archive Installation

  • The archive installation is suitable for installation on all supported operating systems
  • Use this method if you want to extract the instance manually.
  • The archive installation provides a default installation of JBoss EAP, and you must implement any configuration changes after the installation.

RPM Installation

You can install JBoss EAP using RPM packages on supported installations of Red Hat Enterprise Linux 7 or later.

1.2. Downloading and installing JBoss EAP using archive installation method

You can download and install JBoss EAP using the archive installation method on Red Hat Enterprise Linux RHEL and on Microsoft Windows server.

Prerequisites

  • You are on a supported operating system.
  • You have set up an account on the Red Hat Customer Portal.
  • You have Installed a supported Java Development Kit (JDK).
  • You have reviewed the JBoss EAP 8 supported configurations and have ensured that your system is supported.
  • Microsoft Windows only: You have set the JAVA_HOME and PATH environment variables.
Note

If you do not set up the environment variables the shortcuts will not work.

Procedure

  1. Log in to the Red Hat Customer Portal.
  2. Click Downloads
  3. Select Red Hat JBoss Enterprise Application Platform from the Product Downloads list.
  4. In the Version drop-down list, select 8.0.
  5. Find Red Hat JBoss Enterprise Application Platform 8.0.0 in the list and click the Download link.
  6. Optional: Move the archive file to the server and location where you want to install JBoss EAP.
  7. Depending on your operating system, choose one of the following options:

    • For Red Hat Enterprise Linux, extract the archive file by entering the following command in the management CLI:

      $ unzip jboss-eap-8.0.0.zip
    • For Windows Server, right-click the archive file and select Extract All.

      Note

      EAP_HOME is the top-level directory for the JBoss EAP installation. Create the directory by extracting the archive file.

Additional resources

1.3. Uninstalling JBoss EAP archive installation

Depending on your work environment, the archive installation method might not meet the needs of your environment. You can remove the instance of JBoss EAP and any services associated with it. Thereafter, you can install JBoss EAP using a suitable installation method.

Prerequisites

  • You have archived any modified configuration files and deployments that you can reuse at a later stage.

Procedure

  1. Delete the installation directory to uninstall JBoss EAP.
  2. Delete any scripts that depend on JBoss EAP being installed on your machine.

Chapter 2. Running and removing JBoss EAP as a service on RHEL

2.1. Running JBoss EAP as a service on RHEL

You can configure JBoss EAP to run as a service in Red Hat Enterprise Linux RHEL. This enables your the JBoss EAP service to start automatically when the RHEL server starts.

Prerequisites

  • You have downloaded and Installed JBoss EAP.
  • You have set the JAVA_HOME system environment variable.
  • You have administrator privileges on the server.

Procedure

  1. Configure the start-up options in the jboss-eap.conf file by opening the jboss-eap.conf in a text editor and set the options for your JBoss EAP installation.
  2. Copy the service initialization and configuration files into the system directories:

    1. Copy the modified service configuration file to the /etc/default directory.

      Note

      The commands in this procedure require root privileges to run. Either run su - to switch to the root user or preface the commands with sudo.

      $ sudo cp EAP_HOME/bin/init.d/jboss-eap.conf /etc/default
    2. Copy the service startup script to the /etc/init.d directory and give it execute permissions:

      $ sudo cp EAP_HOME/bin/init.d/jboss-eap-rhel.sh /etc/init.d
      $ sudo chmod +x /etc/init.d/jboss-eap-rhel.sh
      $ sudo restorecon /etc/init.d/jboss-eap-rhel.sh
  3. Add the new jboss-eap-rhel.sh service to the list of automatically started services using the chkconfig service management command:

    $ sudo chkconfig --add jboss-eap-rhel.sh
  4. Verify that the service has been installed correctly by using one of the following commands.

    1. For Red Hat Enterprise Linux 6:

      $ sudo service jboss-eap-rhel.sh start
    2. For Red Hat Enterprise Linux 7 and later:

      $ sudo service jboss-eap-rhel start
  5. Optional: To make the service start automatically when the RHEL server starts, run the following command:

    $ sudo chkconfig jboss-eap-rhel.sh on

Verification

  • To check the permissions of a file, enter the ls -l command in the directory containing the file.
  • To check that the automatic service start is enabled, enter the following command:

    $ sudo chkconfig --list jboss-eap-rhel.sh

Additional resources

  • For more information about controlling the state of services, see Management system services in the JBoss EAP Configuring basic system settings guide.
  • For more information about viewing error logs, see Bootup logging in the JBoss EAP Configuration Guide.

2.2. Removing JBoss EAP service on RHEL

You can remove an instance of JBoss EAP and any of its services associated. After you remove these components, you can install JBoss EAP by using a suitable installation method.

Prerequisites

  • You have JBoss EAP installed.

Procedure

  1. When the service is running, open a terminal and stop the service with one of the following command:

    $ sudo service jboss-eap-rhel.sh stop
    Note

    The commands in this procedure require root privileges to run. Either run su - to switch to the root user or preface the commands with sudo.

  2. Remove JBoss EAP from the list of services:

    $ sudo chkconfig --del jboss-eap-rhel.sh
  3. Delete the configuration file and startup script:

    $ sudo rm /etc/init.d/jboss-eap-rhel.sh
    $ sudo rm /etc/default/jboss-eap.conf

Chapter 3. Running and removing JBoss EAP as a service on Microsoft Windows Server

3.1. Running JBoss EAP as a service on Microsoft Windows server

You can configure JBoss EAP to run as a service on Microsoft Windows server. This method provides a basic default installation of a server, with configuration files and libraries placed in standard folders.

Note

If you use the set command to set system environment variables in a Windows Server command prompt, it does not permanently set the environment variables. You must use either the setx command, or the System interface in the Control Panel.

Prerequisites

  • You have installed JBoss EAP.
  • You have administrator privileges on the server.
  • You have set the JAVA_HOME system environment variable.
  • You have verified that the JBoss EAP server instance is not running.

Procedure

  1. Use the setx command to create two system environment variables: JBOSS_HOME and NOPAUSE.
  2. Use the setx command to configure the two environment variables:

    1. Set the path for the JBOSS_HOME variable to the JBoss EAP installation directory.
    2. The jboss-cli.bat script contains the "x%NOPAUSE%" == "x" pause line of code. This code creates a status message when you issue the pause command. To disable these messages, you must specify a value for the NOPAUSE variable. For example, setting the NOPAUSE variable to NOPAUSE=true disables status messages from appearing when a script completes.

Additional resources

  • To learn more about how to set environment variables on a Microsoft Windows Server, refer to the Microsoft Windows documentation.

3.2. Removing JBoss EAP service on Microsoft Windows Server

You can remove an instance of JBoss EAP and any services associated with it. Thereafter, you can install JBoss EAP by using a suitable installation method.

Prerequisites

  • You have JBoss EAP installed.

Procedure

  1. When the service is running, open the command prompt and stop the service by entering the net stop command with the name of the service:

    net stop JBossEAP7
  2. At a command prompt, change directories to EAP_HOME\bin and execute the following command:

    service.bat uninstall

Legal Notice

Copyright © 2022 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.