Chapter 2. Installing JBoss Web Server on Red Hat Enterprise Linux from archive files You can install JBoss Web Server on Red Hat Enterprise Linux (RHEL) from archive files or RPM packages. If you want to install JBoss Web Server from archive files, you can download and extract the JBoss Web Server archive files from the Red Hat Customer Portal . When you install JBoss Web Server from an archive file, you can manage the product in different ways. For example, you can use a system daemon at system startup or manage JBoss Web Server from a command line. Note You can install JBoss Web Server on RHEL versions 8 and 9. Red Hat does not provide a distribution of JBoss Web Server 6.x for RHEL 7 systems. 2.1. Prerequisites You have installed a supported Java Development Kit (JDK) by using the DNF package manager or from a compressed archive. Your system is compliant with Red Hat Enterprise Linux package requirements. 2.1.1. Installing a JDK by using the DNF package manager You can use the DNF package manager to install a Java Development Kit (JDK). For a full list of supported JDKs, see JBoss Web Server operating systems and configurations . Note This procedure describes how to install OpenJDK. If you want to install the Oracle JDK, see the Oracle documentation for more information. Procedure Subscribe your Red Hat Enterprise Linux system to the appropriate channel: rhel-8-server-rpms rhel-9-server-rpms To install a supported JDK version, enter the following command as the root user: In the preceding command, replace java- <version> with java-11 or java-17 . Note JBoss Web Server 6.x does not support OpenJDK 8. To ensure the correct JDK is in use, enter the following command as the root user: The preceding command returns a list 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. Important All software that uses the java command uses the JDK set by alternatives . Changing Java alternatives might impact on the running of other software. 2.1.2. Installing a JDK from a compressed archive You can install a Java Development Kit (JDK) from a compressed archive such as a .zip or .tar file. For a full list of supported JDKs, see JBoss Web Server operating systems and configurations . Procedure If you downloaded the JDK from the vendor's website (Oracle or OpenJDK), use the installation instructions provided by the vendor and set the JAVA_HOME environment variable. If you installed the JDK from a compressed archive, set the JAVA_HOME environment variable for Tomcat: In the bin directory of Tomcat ( JWS_HOME /tomcat/bin ), create a file named setenv.sh . In the setenv.sh file, enter the JAVA_HOME path definition. For example: In the preceding example, replace jre- <version> with jre-11 or jre-17 . 2.1.3. Red Hat Enterprise Linux package requirements Before you install JBoss Web Server on Red Hat Enterprise Linux, you must ensure that your system is compliant with the following package requirements. On Red Hat Enterprise Linux version 8 or 9, if you want to use OpenSSL or Apache Portable Runtime (APR), you must install the openssl and apr packages that Red Hat Enterprise Linux provides. To install the openssl package, enter the following command as the root user: To install the apr package, enter the following command as the root user: You must remove the tomcatjss package before you install the tomcat-native package. The tomcatjss package uses an underlying Network Security Services (NSS) security model rather than the OpenSSL security model. To remove the tomcatjss package, enter the following command as the root user: 2.2. Downloading and extracting archive files for a base release of JBoss Web Server A base release is the initial release of a specific product version (for example, 6.0.0 is the base release of version 6.0). You can download the JBoss Web Server archive files from the Software Downloads page on the Red Hat Customer Portal. Prerequisites You have installed a supported Java Development Kit (JDK) by using the DNF package manager or from a compressed archive . Your system is compliant with Red Hat Enterprise Linux package requirements . Procedure Open a browser and log in to the Red Hat Customer Portal . Click the Downloads tab. From the Product Downloads list, select Red Hat JBoss Web Server . On the Software Downloads page, from the Version drop-down list, select the appropriate JBoss Web Server version. Click Download to the Red Hat JBoss Web Server 6.0.0 Application Server file. The downloaded file is named jws-6.0.0-application-server.zip on your local host. If you also want to download the native JBoss Web Server components for your operating system, click Download to the Red Hat JBoss Web Server 6.0.0 Optional Native Components for <platform> <architecture> file. In this situation, ensure that you select the correct file that matches the platform and architecture for your system. The downloaded file is named jws-6.0.0-optional-native-components- <platform> - <architecture> .zip (for example, jws-6.0.0-optional-native-components-RHEL8-x86_64.zip ). Extract the downloaded archive files to your installation directory. For example: The top-level directory for JBoss Web Server is created when you extract the archive. This document refers to the top-level directory for JBoss Web Server as JWS_HOME . 2.3. Downloading and extracting archive files for JBoss Web Server patch updates If product patch updates are available for the appropriate JBoss Web Server version, you can install the archive files for the latest cumulative patches. You can download the JBoss Web Server archive files from the Software Downloads page on the Red Hat Customer Portal. Important You cannot use cumulative patch updates to install the base ( X.X .0) release of a product version. For example, the installation of a 6.0.2 patch would install the 6.0.1 and 6.0.2 releases but cannot install the base 6.0.0 release. Service pack releases are cumulative. By downloading the latest service pack release, you also install any service pack releases automatically. Prerequisites You have downloaded and extracted the archive files for the base JBoss Web Server release . Procedure Open a browser and log in to the Red Hat Customer Portal . Click the Downloads tab. From the Product Downloads list, select Red Hat JBoss Web Server . On the Software Downloads page, from the Version drop-down list, select the appropriate JBoss Web Server version. Click the Patches tab. Click Download to the latest Red Hat JBoss Web Server 6.0 Update XX Application Server file. The downloaded file is named jws-6.0. x -application-server.zip on your local host. If you also want to download the native JBoss Web Server components for your operating system, click Download to the latest Red Hat JBoss Web Server 6.0 Update XX Optional Native Components for <platform> <architecture> file. In this situation, ensure that you select the correct file that matches the platform and architecture for your system. The downloaded file is named jws-6.0. x -optional-native-components- <platform> - <architecture> .zip (for example, jws-6.0. x -optional-native-components-RHEL8-x86_64.zip ). Extract the downloaded archive files to your installation directory. For example: 2.4. Managing JBoss Web Server by using systemd when installed from an archive file When you install JBoss Web Server from an archive file on Red Hat Enterprise Linux, you can use a system daemon to perform management tasks. Using the JBoss Web Server with a system daemon provides a method of starting the JBoss Web Server services at system startup. The system daemon also provides start, stop and status check functions. On Red Hat Enterprise Linux versions 8 and 9, the default system daemon is systemd . Prerequisites You have installed JBoss Web Server from an archive file . Procedure To determine which system daemon is running, enter the following command: If systemd is running, the following output is displayed: To set up the JBoss Web Server for systemd , run the .postinstall.systemd script as the root user: To control the JBoss Web Server with systemd , you can perform any of the following steps as the root user: To enable the JBoss Web Server services to start at system startup by using systemd : To start the JBoss Web Server by using systemd : Note The SECURITY_MANAGER variable is now deprecated for JBoss Web Server configurations that are based on archive file installations. Consider the following deprecation comment: To stop the JBoss Web Server by using systemd : To verify the status of the JBoss Web Server by using systemd : Note Any user can run the status operation. Additional resources RHEL 8: Configuring basic system settings: Managing system services with systemctl RHEL 9: Configuring basic system settings: Managing system services with systemctl 2.5. JBoss Web Server configuration for managing archive installations from the command line When you install JBoss Web Server from an archive file on Red Hat Enterprise Linux, you can start and stop JBoss Web Server directly from the command line. Before you can run JBoss Web Server from the command line, you must perform the following series of configuration tasks: Set the JAVA_HOME environment variable for Tomcat. Create a tomcat user and its parent group. Grant the tomcat user access to JBoss Web Server. Note When you manage JBoss Web Server by using a system daemon rather than from the command line, the .postinstall.systemd script performs these configuration steps automatically. 2.5.1. Setting the JAVA_HOME environment variable for Apache Tomcat Before you run JBoss Web Server from the command line for the first time, you must set the JAVA_HOME environment variable for Apache Tomcat. Prerequisites You have installed JBoss Web Server from an archive file . Procedure On a command line, go to the JWS_HOME /tomcat/bin directory. Create a file named setenv.sh . In the setenv.sh file, enter the JAVA_HOME path definition. For example: 2.5.2. Creating a Tomcat user and group Before you run JBoss Web Server from the command line for the first time, you must create a tomcat user account and user group to enable simple and secure user management. On Red Hat Enterprise Linux, the user identifer (UID) for the tomcat user and the group identifier (GID) for the tomcat group both have a reserved value of 53 . Note You must perform all steps in this procedure as the root user. Prerequisites You have set the JAVA_HOME environment variable for Tomcat . Procedure On a command line, go to the JWS_HOME directory. Create the tomcat user group: Create the tomcat user in the tomcat user group: The preceding commands set both the UID and the GID to 53 . If you subsequently want to change the UID and GID values, see Changing the UID and GID for the tomcat user and group . 2.5.3. Granting the Tomcat user access to JBoss Web Server Before you run JBoss Web Server from the command line for the first time, you must grant the tomcat user access to JBoss Web Server by assigning ownership of the Tomcat directories to the tomcat user. Note You must perform all steps in this procedure as the root user. Prerequisites You have created a tomcat user and its parent group . Procedure Go to the JWS_HOME directory. Assign ownership of the Tomcat directories to the tomcat user: Ensure that the tomcat user has execute permissions for all parent directories: Verification Verify that the tomcat user is the owner of the directory: 2.6. Starting JBoss Web Server from the command line when installed from an archive file When you install JBoss Web Server from an archive file on Red Hat Enterprise Linux, you can start JBoss Web Server directly from the command line. Prerequisites You have set the JAVA_HOME environment variable for Tomcat . You have created a tomcat user and its parent group . You have granted the tomcat user access to JBoss Web Server . Procedure Enter the following command as the tomcat user: 2.7. Stopping JBoss Web Server from the command line when installed from an archive file When you install JBoss Web Server from an archive file on Red Hat Enterprise Linux, you can stop JBoss Web Server directly from the command line. Prerequisites You have started JBoss Web Server from the command line . Procedure Enter the following command as the tomcat user: 2.8. SELinux policies for JBoss Web Server You can use Security-Enhanced Linux (SELinux) policies to define access controls for JBoss Web Server. These policies are a set of rules that determine access rights to the product. 2.8.1. SELinux policy information for jws6-tomcat The SELinux security model is enforced by the kernel and ensures that applications have limited access to resources such as file system locations and ports. SELinux policies ensure that any errant processes that are compromised or poorly configured are restricted or prevented from running. The jws6-tomcat-selinux packages in your JBoss Web Server installation provide a jws6_tomcat policy. The following table contains information about the supplied SELinux policy. Table 2.1. RPMs and default SELinux policies Name Port Information Policy Information jws6_tomcat Four ports in http_port_t (TCP ports 8080 , 8005 , 8009 , and 8443 ) to allow the tomcat process to use them The jws6_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 the following directories: /var/opt/rh/jws6/lib/tomcat /var/opt/rh/jws6/log/tomcat /var/opt/rh/jws6/cache/tomcat /var/opt/rh/jws6/run/tomcat.pid Additional resources RHEL 8: Using SELinux RHEL 9: Using SELinux 2.8.2. Installing SELinux policies for a JBoss Web Server archive installation In this release, the archive packages provide SELinux policies. The tomcat folder of the jws-6.0.0-application-server- <platform> - <architecture> .zip archive includes the .postinstall.selinux file. If required, you can run the .postinstall.selinux script. Procedure Install the selinux-policy-devel package: Run the .postinstall.selinux script: Add access permissions to the required ports for JBoss Web Server: Note The JBoss Web Server has access to ports 8080 , 8009 , 8443 and 8005 on Red Hat Enterprise Linux systems. When additional ports are required for JBoss Web Server, use the preceding semanage command to provide the necessary permissions, and replace <port> with the required port. Start Tomcat: Check the context of the running process expecting jws6_tomcat : Verify the contexts of the Tomcat directories. For example: Note By default, the SElinux policy that JBoss Web Server provides is not active and the Tomcat processes run in the unconfined_java_t domain. This domain does not confine the processes. If you choose not to enable the SELinux policy that is provided, you can take the following security measures: Restrict file access for the tomcat user, so that the tomcat user only has access to the files and directories that are necessary for the JBoss Web Server runtime. Do not run Tomcat as the root user. Note When JBoss Web Server is installed from an archive file, Red Hat does not officially support the use of network file sharing (NFS). If you want your JBoss Web Server installation to use an NFS-mounted file system, you are responsible for ensuring that SELinux policies are modified correctly to support this type of deployment. 2.9. Changing the UID and GID for the tomcat user and group On Red Hat Enterprise Linux, the user identifer (UID) for the tomcat user and the group identifier (GID) for the tomcat group both have a reserved value of 53 . Depending on your setup requirements, you can change the UID and GID for the tomcat user and group to some other value. Warning To avoid SELinux conflicts, use UID and GID values that are less than 500. If SELinux is set to enforcing mode, UID and GID values greater than 500 might cause unexpected issues. Prerequisites You have created a tomcat user account and group . Procedure If JBoss Web Server is already running, stop JBoss Web Server as the tomcat user. For more information, see Stopping JBoss Web Server from the command line when installed from an archive file . To view the current UID and GID for the tomcat user and group, enter the following command as the root user: The preceding command displays the user account and group details. For example: To assign a new GID to the tomcat group, enter the following command as the root user: For example: To assign a new UID to the tomcat user, enter the following command as the root user: For example: To reassign file and directory permissions to the new UID, enter the following command as the root user: In the preceding command, replace <original_uid> with the old UID and replace <new_uid> with the new UID. For example, to reassign file and directory permissions from UID 53 to UID 401 , enter the following command: To reassign file and directory permissions to the new GID, enter the following command as the root user: In the preceding command, replace <original_gid> with the old GID and replace <new_gid> with the new GID. For example, to reassign file and directory permissions from GID 53 to GID 410 , enter the following command: To restart JBoss Web Server as the tomcat user, see Starting JBoss Web Server from the command line when installed from an archive file . Additional resources What are the reserved UIDs/GIDs in Red Hat Enterprise Linux?

Commands:
dnf install java- <version> -openjdk-headless
alternatives --config java
cat JWS_HOME /tomcat/bin/setenv.sh export JAVA_HOME=/usr/lib/jvm/jre- <version> -openjdk.x86_64
dnf install openssl
dnf install apr
dnf remove tomcatjss
unzip jws-6.0.0-application-server.zip -d /opt/ unzip -o jws-6.0.0-optional-native-compoonents- <platform> - <architecture> .zip -d /opt/
unzip jws-6.0. x -application-server.zip -d /opt/ unzip -o jws-6.0. x -optional-native-compoonents- <platform> - <architecture> .zip -d /opt/
ps -p 1 -o comm=
systemd
cd JWS_HOME /tomcat sh .postinstall.systemd
systemctl enable jws6-tomcat.service
systemctl start jws6-tomcat.service
SECURITY_MANAGER has been deprecated. To run tomcat under the Java Security Manager use: JAVA_OPTS="-Djava.security.manager -Djava.security.policy==\"USDCATALINA_BASE/conf/"catalina.policy\"""
systemctl stop jws6-tomcat.service
systemctl status jws6-tomcat.service
export JAVA_HOME=/usr/lib/jvm/jre-11-openjdk.x86_64
groupadd -g 53 -r tomcat
useradd -c "tomcat" -u 53 -g tomcat -s /sbin/nologin -r tomcat
chown -R tomcat:tomcat tomcat/
chmod -R u+X tomcat/
ls -l
sh JWS_HOME /tomcat/bin/startup.sh
sh JWS_HOME /tomcat/bin/shutdown.sh
dnf install -y selinux-policy-devel
cd <JWS_home> /tomcat/ sh .postinstall.selinux
semanage port -a -t http_port_t -p tcp <port>
<JWS_home> /tomcat/bin/startup.sh
ps -eo pid,user,label,args | grep jws6_tomcat | head -n1
ls -lZ <JWS_home> /tomcat/logs/
id tomcat
uid=53(tomcat) gid=53(tomcat) groups=53(tomcat)
groupmod -g <new_gid> tomcat
groupmod -g 410 tomcat
usermod -u <new_uid> -g <new_gid> tomcat
usermod -u 401 -g 410 tomcat
find / -not -path '/proc*' -uid <original_uid> | perl -e 'USDug = @ARGV[0]; foreach USDfn (<STDIN>) { chomp(USDfn);USDm = (stat(USDfn))[2];chown(USDug,-1,USDfn);chmod(USDm,USDfn)}' <new_uid>
find / -not -path '/proc*' -uid 53 | perl -e 'USDug = @ARGV[0]; foreach USDfn (<STDIN>) { chomp(USDfn);USDm = (stat(USDfn))[2];chown(USDug,-1,USDfn);chmod(USDm,USDfn)}' 401
find / -not -path '/proc*' -gid <original_gid> | perl -e 'USDug = @ARGV[0]; foreach USDfn (<STDIN>) { chomp(USDfn);USDm = (stat(USDfn))[2];chown(-1,USDug,USDfn);chmod(USDm,USDfn)}' <new_gid>
find / -not -path '/proc*' -gid 53 | perl -e 'USDug = @ARGV[0]; foreach USDfn (<STDIN>) { chomp(USDfn);USDm = (stat(USDfn))[2];chown(-1,USDug,USDfn);chmod(USDm,USDfn)}' 410