Chapter 3. Installing JBoss Web Server on Red Hat Enterprise Linux
You can install JBoss Web Server on Red Hat Enterprise Linux using one of two methods:
Regardless of which method you choose, you must first install a supported Java Development Kit (JDK).
3.1. Prerequisites Copy linkLink copied to clipboard!
3.1.1. Installing a Java Development Kit (JDK) Copy linkLink copied to clipboard!
Before installing JBoss Web Server, you must first install a supported Java Development Kit (JDK).
Full list of supported JDKs for Red Hat JBoss Web Server 5.1:
| Operating System | Chipset Architecture | Java Virtual Machine |
|---|---|---|
| Red Hat Enterprise Linux 8 | x86_64 | OpenJDK 1.8, OpenJDK 11, OracleJDK 11 |
Installing a JDK using the YUM package manager
Subscribe your Red Hat Enterprise Linux system to the appropriate channel:
OpenJDK:
- rhel-8-server-rpms
As the root user, execute the command to install a 1.8 JDK:
# yum install java-1.8.0-openjdk-develRun the following commands as the root user to ensure the correct JDK is in use:
# alternatives --config java# alternatives --config javacThese commands return lists of available JDK versions with the selected version marked with a plus (
+) sign. If the selected JDK is not the desired one, change to the desired JDK as instructed in the shell prompt.ImportantAll software that use the
javaandjavaccommands uses the JDK set byalternatives. Changing Java alternatives may impact on the running of other software.
Installing a JDK from a compressed archive (such as .zip or .tar)
If the JDK was downloaded from the vendor’s website (Oracle or OpenJDK), use the installation instructions provided by the vendor and set the JAVA_HOME environment variable.
If the JDK has was installed from a compressed archive, set the JAVA_HOME environment variable for Tomcat before running JBoss Web Server.
In the bin directory of Tomcat (JWS_HOME/tomcat/bin), create a file named setenv.sh, and insert the JAVA_HOME path definition.
For example:
$ cat JWS_HOME/tomcat/bin/setenv.sh
export JAVA_HOME=/usr/lib/jvm/jre-1.8.0-openjdk.x86_64
3.1.2. Red Hat Enterprise Linux Package Prerequisites Copy linkLink copied to clipboard!
Before installing JBoss Web Server on Red Hat Enterprise Linux, ensure the following prerequisites are met.
- A supported JDK is installed.
- Additionally, RHEL-8 users needing to run JSSE+OpenSSL or APR, you will need to use Tomcat-Native for it to work properly. The file for Tomcat-Native can be found in the native zip directory. To install OpenSSL and APR, run the following commands:
# yum install openssl
# yum install apr
-
You must remove the
tomcatjsspackage before installing thetomcat-nativepackage. Thetomcatjsspackage uses an underlying NSS security model rather than the OpenSSL security model.
Removing the tomcatjss Package
As the root user, run the following command to remove
tomcatjss:# yum remove tomcatjss
3.2. ZIP Installation Copy linkLink copied to clipboard!
Ensure that all of the prerequisites are met before installing JBoss Web Server.
3.2.1. Downloading and Extracting JBoss Web Server Copy linkLink copied to clipboard!
To install JBoss Web Server, download and extract the installation ZIP files.
- Open a browser and log in to the Red Hat Customer Portal.
- Click Downloads.
- Click Red Hat JBoss Web Server in the Product Downloads list.
- Select the correct JBoss Web Server version from the Version drop-down menu.
Click Download for each of the following files, ensuring that you select the correct platform and architecture for your system:
-
The Red Hat JBoss Web Server 5.1 Application Server (
jws-application-servers-5.1.0.zip). -
The Red Hat JBoss Web Server 5.1 Native Components for RHEL (
jws-application-servers-5.1.0-<platform>-<architecture>.zip).
-
The Red Hat JBoss Web Server 5.1 Application Server (
Unzip the downloaded ZIP files to your installation directory.
For example:
# unzip jws-application-server-5.1.0.zip -d /opt/ # unzip -o jws-application-server-5.1.0-<platform>-<architecture>.zip -d /opt/
The directory created by extracting the ZIP archives is the top-level directory for JBoss Web Server. This is referred to as JWS_HOME.
3.2.2. Managing JBoss Web Server on Red Hat Enterprise Linux Copy linkLink copied to clipboard!
There are two supported methods for running and managing Red Hat JBoss Web Server on Red Hat Enterprise Linux:
The recommended method for managing the JBoss Web Server is using a system daemon.
3.2.2.1. Managing JBoss Web Server using a system daemon for .zip installations on Red Hat Enterprise Linux Copy linkLink copied to clipboard!
Using the JBoss Web Server with a system daemon provides a method of starting the JBoss Web Server services at system boot. The system daemon also provides start, stop and status check functions.
The default system daemon for Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 7 is systemd and for Red Hat Enterprise Linux 6 the default is SysV.
To determine which system daemon is running, issue ps -p 1 -o comm=.
For systemd:
$ ps -p 1 -o comm= systemdFor SysV:
$ ps -p 1 -o comm= init
3.2.2.1.1. Setting up and using the JBoss Web Server with SysV Copy linkLink copied to clipboard!
Prerequisites
-
The
redhat-lsb-corepackage. To install, run:yum install redhat-lsb-core
Setting up the JBoss Web Server for SysV
As the root user, execute the .postinstall.sysv script:
# cd JWS_HOME/tomcat
# sh .postinstall.sysv
Controlling the JBoss Web Server with SysV
SysV commands can only be issued by the root user.
To enable the JBoss Web Server services to start at boot using SysV:
# chkconfig jws5-tomcat onTo start the JBoss Web Server using SysV:
# service jws5-tomcat startTo stop the JBoss Web Server using SysV:
# service jws5-tomcat stopTo verify the status of the JBoss Web Server using SysV (the
statusoperation can be executed by any user):$ service jws5-tomcat status
For more information on using SysV, see: Red Hat Enterprise Linux 6 Deployment Guide: Running Services
3.2.2.1.2. Setting up and using the JBoss Web Server with systemd Copy linkLink copied to clipboard!
Setting up the JBoss Web Server for systemd
As the root user, execute the .postinstall.systemd script:
# cd JWS_HOME/tomcat
# sh .postinstall.systemd
Controlling the JBoss Web Server with systemd
Systemd commands can only be issued by the root user.
To enable the JBoss Web Server services to start at boot using systemd:
# systemctl enable jws5-tomcat.serviceTo start the JBoss Web Server using systemd:
# systemctl start jws5-tomcat.serviceTo stop the JBoss Web Server using systemd:
# systemctl stop jws5-tomcat.serviceTo verify the status of the JBoss Web Server using systemd (the
statusoperation can be executed by any user):# systemctl status jws5-tomcat.service
For more information on using systemd, see: RHEL 7 System Administrator’s Guide: Managing System Services
There is currently no RHEL 8 System Administrator’s Guide available. This document will be updated to include it when it is made available.
3.2.2.2. Managing JBoss Web Server on a command line Copy linkLink copied to clipboard!
3.2.2.2.1. Configuring the JBoss Web Server Installation Copy linkLink copied to clipboard!
The following configuration steps are performed by the .postinstall.sysv script and the .postinstall.systemd script described in Managing JBoss Web Server using a system daemon for .zip installations on Red Hat Enterprise Linux
Some configuration is required before running JBoss Web Server. This section includes the following configuration procedures:
- Setting the JAVA_HOME Environment Variable.
- Creating the tomcat user for simple and secure user management: Creating a Tomcat User.
- Grant the tomcat user access to the JBoss Web Server by moving the ownership of tomcat directory to the tomcat user.
Setting the JAVA_HOME Environment Variable
You must set the JAVA_HOME environment variable for Tomcat before running JBoss Web Server.
In the bin directory of Tomcat (JWS_HOME/tomcat/bin), create a file named setenv.sh, and insert the JAVA_HOME path definition.
For example: export JAVA_HOME=/usr/lib/jvm/jre-1.8.0-openjdk.x86_64
Creating a Tomcat User
Follow this procedure to create the tomcat user and its parent group:
-
In a shell prompt as the root user, change directory to
JWS_HOME. Run the following command to create the
tomcatuser group:# groupadd -g 53 -r tomcatRun the following command to create the
tomcatuser in thetomcatuser group:# useradd -c "tomcat" -u 53 -g tomcat -s /bin/sh -r tomcat
Move the ownership of tomcat directory to the tomcat user
From
JWS_HOME, run the following command to assign the ownership of the Tomcat directories to thetomcatuser to allow the user to run the Tomcat service:# chown -R tomcat:tomcat tomcat/You can use
ls -lto verify that thetomcatuser is the owner of the directory.Ensure that the
tomcatuser has execute permissions to all parent directories. For example:# chmod -R u+X tomcat/
3.2.2.2.2. Starting JBoss Web Server Copy linkLink copied to clipboard!
Run the following command as the tomcat user:
$ sh JWS_HOME/tomcat/bin/startup.sh
3.2.2.2.3. Stopping JBoss Web Server Copy linkLink copied to clipboard!
To stop Tomcat, run the following command as the tomcat user:
$ sh JWS_HOME/tomcat/bin/shutdown.sh
3.3. RPM Installation Copy linkLink copied to clipboard!
Installing JBoss Web Server from RPM packages installs Tomcat as service, and installs its resources into absolute paths. The RPM installation option is available for Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, and Red Hat Enterprise Linux 8.
RPM installation packages for JBoss Web Server are available from Red Hat Subscription Management.
3.3.1. Installing JBoss Web Server from RPM packages Copy linkLink copied to clipboard!
Before downloading and installing the RPM packages, you must register your system with Red Hat Subscription Management and subscribe to the respective Content Delivery Network (CDN) repositories.
For information on registering Red Hat Enterprise Linux, see:
Configuring the Subscription Service for Red Hat Enterprise Linux 6
OR
The Subscription Manager for Red Hat Enterprise Linux 7
OR
The Subscription Manager for Red Hat Enterprise Linux 8
Attaching subscriptions to Red Hat Enterprise Linux (if required)
If the system does not have a subscription attached that provides JBoss Web Server:
- Log in to the Red Hat Subscription Manager.
- Click on the Systems tab.
-
Click on the
Nameof the system to add the subscription to. -
Change from the Details tab to the Subscriptions tab, then click
Attach Subscriptions. -
Select the check box beside the subscription to attach, then click
Attach Subscriptions.
To verify that a subscription provides the required CDN repositories:
- Log in to: https://access.redhat.com/management/subscriptions.
-
Click the
Subscription Name. Under Products Provided, you require:
- JBoss Enterprise Web Server.
- Red Hat JBoss Core Services.
Installing JBoss Web Server from RPM packages using YUM
On a command line, subscribe to the JBoss Web Server CDN repositories for your operating system version using
subscription-manager:# subscription-manager repos --enable <repository>For Red Hat Enterprise Linux 6:
- jws-5-for-rhel-6-server-rpms
- jb-coreservices-1-for-rhel-6-server-rpms
For Red Hat Enterprise Linux 7:
- jws-5-for-rhel-7-server-rpms
- jb-coreservices-1-for-rhel-7-server-rpms
Issue the following command as the root user to install JBoss Web Server:
# yum groupinstall jws5Note- Although not recommended, instead of using the group install, you can install each of the packages and their dependencies individually.
- The Red Hat JBoss Core Services repositories above are required for the installation of JBoss Web Server.
3.3.2. Starting JBoss Web Server Copy linkLink copied to clipboard!
In a shell prompt as the root user, start the Tomcat service.
For Red Hat Enterprise Linux 6:
# service jws5-tomcat startFor Red Hat Enterprise Linux 7:
# systemctl start jws5-tomcat.service
This is the only supported method of starting JBoss Web Server for an RPM installation.
To verify that Tomcat is running, the output of the service
statuscommand should be reviewed. This can be executed as any user.For Red Hat Enterprise Linux 6:
# service jws5-tomcat statusFor Red Hat Enterprise Linux 7:
# systemctl status jws5-tomcat.service
For complete instructions on installing and configuring HTTPD on RHEL 8, please see this link
3.3.3. Stopping JBoss Web Server Copy linkLink copied to clipboard!
In a shell prompt as the root user, stop the Tomcat service.
For Red Hat Enterprise Linux 6:
# service jws5-tomcat stopFor Red Hat Enterprise Linux 7:
# systemctl stop jws5-tomcat.service
To verify that Tomcat is no longer running, the output of the service
statuscommand should be reviewed. This can be executed as any user.For Red Hat Enterprise Linux 6:
# service jws5-tomcat statusFor Red Hat Enterprise Linux 7:
# systemctl status jws5-tomcat.service
For complete instructions on installing and configuring HTTPD on RHEL 8, please see this link
3.3.4. Configuring JBoss Web Server Services to Start at Boot Copy linkLink copied to clipboard!
Use the following commands to enable the JBoss Web Server services to start at boot.
For Red Hat Enterprise Linux 6:
# chkconfig jws5-tomcat onFor Red Hat Enterprise Linux 7:
# systemctl enable jws5-tomcat.service
3.4. SELinux Policies Copy linkLink copied to clipboard!
3.4.1. SELinux Policy Information Copy linkLink copied to clipboard!
The following table contains information about the SELinux policies provided in the jws5-tomcat-selinux packages.
| Name | Port Information | Policy Information |
|---|---|---|
| jws5_tomcat |
Four ports in |
The jws5_tomcat policy is installed, which sets the appropriate SELinux domain for the process when Tomcat executes. It also sets the appropriate contexts to allow tomcat to write to |
For more information about using SELinux and other Red Hat Enterprise Linux security information, see the Red Hat Enterprise Linux Security Guide.
3.4.2. SELinux Policies for an RPM Installation Copy linkLink copied to clipboard!
SELinux policies for JBoss Web Server are provided by the jws5-tomcat-selinux package. These packages are available in the JWS channel.
To enable SELinux policies for JBoss Web Server 5.1, install the jws5-tomcat-selinux package.
3.4.3. SELinux Policies for a ZIP Installation Copy linkLink copied to clipboard!
In this release, SELinux policies are provided in the ZIP packages. The SELinux security model is enforced by the kernel and ensures applications have limited access to resources such as file system locations and ports. This helps ensure that the errant processes (either compromised or poorly configured) are restricted and in some cases prevented from running.
The .postinstall.selinux file is included in the tomcat folder of jws-application-server-5.1.0-<platform>-<architecture>.zip. If required, you can run the .postinstall.selinux script.
To install the SELinux policies using ZIP:
Install the
selinux-policy-develpackage:yum install -y selinux-policy-develExecute the
.postinstall.selinuxscript:cd <JWS_home>/tomcat/ sh .postinstall.selinuxMake and install the SELinux module:
cd selinux make -f /usr/share/selinux/devel/Makefile semodule -i jws5-tomcat.ppApply the SELinux contexts for JBoss Web Server:
restorecon -r <JWS_home>/tomcat/Add access permissions to the required ports for JBoss Web Server. The JBoss Web Server has access to ports
8080,8009,8443and8005on Red Hat Enterprise Linux 7 systems.When additional ports are required for JBoss Web Server, use the
semanagecommand to provide the necessary permissions, replacing the port number with the port required:semanage port -a -t http_port_t -p tcp <port>NoteThe JBoss Web Server on Red Hat Enterprise Linux 6 systems has access to the same ports as Red Hat Enterprise Linux 7 systems, with the exception of port
8005. To grant the JBoss Web Server access to this port on a Red Hat Enterprise Linux 6 system, as the root user, issue:semanage port -a -t http_port_t -p tcp 8005Start the Tomcat service:
<JWS_home>/tomcat/bin/startup.shCheck the context of the running process expecting
jws5_tomcat:ps -eo pid,user,label,args | grep jws5_tomcat | head -n1To verify the contexts of the Tomcat directories, for example:
ls -lZ <JWS_home>/tomcat/logs/
By default, the SElinux policy provided is not active and the Tomcat processes run in the unconfined_java_t domain. This domain does not confine the processes, and it is recommended that you undertake the following security precautions if you chose not to enable the SElinux policy provided:
-
Restrict file access for the
tomcatuser to only the files and directories that are necessary to the JBoss Web Server runtime. -
Do not run Tomcat as the
rootuser.