Chapter 2. Installing JBoss Web Server on Red Hat Enterprise Linux from archive files

Procedure

1. Open a browser and log in to the Red Hat Customer Portal.
2. Click the Downloads tab.
3. From the Product Downloads list, select Red Hat JBoss Web Server.
4. On the Software Downloads page, from the Version drop-down list, select the appropriate JBoss Web Server version.

5. Click Download next 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.

6. If you also want to download the native JBoss Web Server components for your operating system, click Download next 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).

7. Extract the downloaded archive files to your installation directory.

   For example:

   # unzip jws-6.0.0-application-server.zip -d /opt/
   # unzip -o jws-6.0.0-optional-native-compoonents-<platform>-<architecture>.zip -d /opt/

Procedure

1. Open a browser and log in to the Red Hat Customer Portal.
2. Click the Downloads tab.
3. From the Product Downloads list, select Red Hat JBoss Web Server.
4. On the Software Downloads page, from the Version drop-down list, select the appropriate JBoss Web Server version.
5. Click the Patches tab.

6. Click Download next 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.

7. If you also want to download the native JBoss Web Server components for your operating system, click Download next 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).

8. Extract the downloaded archive files to your installation directory.

   For example:

   # unzip jws-6.0.x-application-server.zip -d /opt/
   # unzip -o jws-6.0.x-optional-native-compoonents-<platform>-<architecture>.zip -d /opt/

Procedure

1. To determine which system daemon is running, enter the following command:

   $ ps -p 1 -o comm=

   If systemd is running, the following output is displayed:

   systemd

2. To set up the JBoss Web Server for systemd, run the .postinstall.systemd script as the root user:

   # cd JWS_HOME/tomcat
   # sh .postinstall.systemd

3. 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:

     # systemctl enable jws6-tomcat.service

   • To start the JBoss Web Server by using systemd:

     # systemctl start jws6-tomcat.service

     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:

     # SECURITY_MANAGER has been deprecated. To run tomcat under the Java Security Manager use:
       JAVA_OPTS="-Djava.security.manager -Djava.security.policy==\"$CATALINA_BASE/conf/"catalina.policy\"""

   • To stop the JBoss Web Server by using systemd:

     # systemctl stop jws6-tomcat.service

   • To verify the status of the JBoss Web Server by using systemd:

     # systemctl status jws6-tomcat.service

     Note

     Any user can run the status operation.

Procedure

1. 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.

2. To view the current UID and GID for the tomcat user and group, enter the following command as the root user:

   id tomcat

   The preceding command displays the user account and group details. For example:

   uid=53(tomcat) gid=53(tomcat) groups=53(tomcat)

3. To assign a new GID to the tomcat group, enter the following command as the root user:

   groupmod -g <new_gid> tomcat

   For example:

   groupmod -g 410 tomcat

4. To assign a new UID to the tomcat user, enter the following command as the root user:

   usermod -u <new_uid> -g <new_gid> tomcat

   For example:

   usermod -u 401 -g 410 tomcat

5. To reassign file and directory permissions to the new UID, enter the following command as the root user:

   # find / -not -path '/proc*' -uid <original_uid> | perl -e '$ug = @ARGV[0]; foreach $fn (<STDIN>) { chomp($fn);$m = (stat($fn))[2];chown($ug,-1,$fn);chmod($m,$fn)}' <new_uid>

   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:

   # find / -not -path '/proc*' -uid 53 | perl -e '$ug = @ARGV[0]; foreach $fn (<STDIN>) { chomp($fn);$m = (stat($fn))[2];chown($ug,-1,$fn);chmod($m,$fn)}' 401

6. To reassign file and directory permissions to the new GID, enter the following command as the root user:

   # find / -not -path '/proc*' -gid <original_gid> | perl -e '$ug = @ARGV[0]; foreach $fn (<STDIN>) { chomp($fn);$m = (stat($fn))[2];chown(-1,$ug,$fn);chmod($m,$fn)}' <new_gid>

   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:

   # find / -not -path '/proc*' -gid 53 | perl -e '$ug = @ARGV[0]; foreach $fn (<STDIN>) { chomp($fn);$m = (stat($fn))[2];chown(-1,$ug,$fn);chmod($m,$fn)}' 410

7. To restart JBoss Web Server as the tomcat user, see Starting JBoss Web Server from the command line when installed from an archive file.