Procedure

1. Open a browser and log in to the Red Hat Customer Portal.
2. Click Downloads.
3. Click Red Hat JBoss Web Server in the Product Downloads list.
4. Select the correct JBoss Web Server version from the Version drop-down menu.

5. 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.7 Application Server (jws-5.7.0-application-server.zip).
   • The Red Hat JBoss Web Server 5.7 Native Components for RHEL (jws-5.7.0-application-server-<platform>-<architecture>.zip).

6. Unzip the downloaded archive files to your installation directory.

   For example:

   # unzip jws-5.7.0-application-server.zip -d /opt/
   # unzip -o jws-5.7.0-application-server-<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 jws5-tomcat.service

   • To start the JBoss Web Server by using systemd:

     # systemctl start jws5-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 jws5-tomcat.service

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

     # systemctl status jws5-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.

Procedure

1. Log in to the Red Hat Subscription Management web page.
2. Click the Systems tab.
3. Click the Name of the system that you want to add the subscription to.
4. Change from the Details tab to the Subscriptions tab, then click Attach Subscriptions.
5. Select the check box next to the subscription you want to attach, and then click Attach Subscriptions.

Verification

1. Log in to the Red Hat Subscriptions web page.
2. In the Subscription Name column, click the subscription that you want to select.

3. Under Products Provided, you require both of the following:

   • JBoss Enterprise Web Server
   • Red Hat JBoss Core Services

Procedure

1. To subscribe to the JBoss Web Server CDN repositories for your operating system version, enter the following command:

   # subscription-manager repos --enable <repository>

   Note

   In the preceding command, replace <repository> with the following values:
   

   • On Red Hat Enterprise Linux 7, replace <repository> with both jws-5-for-rhel-7-server-rpms and jb-coreservices-1-for-rhel-7-server-rpms.
   • On Red Hat Enterprise Linux 8, replace <repository> with jws-5-for-rhel-8-x86_64-rpms.
   • On Red Hat Enterprise Linux 9, replace <repository> with jws-5-for-rhel-9-x86_64-rpms.

2. To install JBoss Web Server, enter the following command as the root user:

   # yum groupinstall jws5

   Important

   When you install JBoss Web Server from RPM packages, the JWS_HOME folder is /opt/rh/jws5/root/usr/share.

Procedure

1. To access the Oracle website, open a browser window and enter the following URL:

   http://www.oracle.com/technetwork/java/javase/downloads/index.html

2. Download the Oracle JDK for your operating system and architecture.
3. Double-click the downloaded file to start the installation.
4. Proceed as instructed in the installation window.

Procedure

1. Open a browser and log in to the Red Hat Product Downloads page.
2. In the Product Downloads list, click Red Hat JBoss Web Server.
3. In the Software Downloads page, select the correct JBoss Web Server version from the Version drop-down menu.

4. In the Download File table, click Download next to each of the following files:

   • The Red Hat JBoss Web Server 5.7 Application Server (jws-5.7.0-application-server.zip).

   • The Red Hat JBoss Web Server 5.7 Native Components for Windows Server (jws-5.7.0-application-server-<platform>-<architecture>.zip).

     Note

     Ensure that you select the correct file that matches the platform and architecture in your system.

5. Unzip the downloaded archive files to your installation directory.

Procedure

1. Depending on the Maven repository you want to use, get the Hibernate JAR files from either jboss-web-server-X.X.x-maven-repository.zip or https://maven.repository.redhat.com/ga/.
2. Add the Hibernate JAR files to your deployment WAR file.

Procedure

1. Open the /META-INF/context.xml file.

2. Modify the JDBC connection pools that are available to applications.

   For example:

   <Context>
     <Resource
       name="jdbc/DsWebAppDB"
       auth="Container"
       type="javax.sql.DataSource"
       username="sa"
       password=""
       driverClassName="org.h2.Driver"
       url="jdbc:h2:mem:target/test/db/h2/hibernate"
       maxActive="8"
       maxIdle="4"/>
   </Context>

Procedure

1. Open the /WEB-INF/classes/META-INF/persistence.xml file.

2. Configure Hibernate to consume connections from Tomcat.

   For example:

   <persistence version="1.0"
     xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
   
     <persistence-unit name="dswebapp">
       <provider>org.hibernate.ejb.HibernatePersistence</provider>
       <properties>
         <property name="hibernate.dialect" value="org.hibernate.dialect.H2Dialect" />
         <property name="hibernate.connection.datasource" value="java:comp/env/jdbc/DsWebAppDB"/>
       </properties>
     </persistence-unit>
   </persistence>

Procedure

1. Open the /WEB-INF/web.xml file.

2. Configure JDBC datasources with the resource-env-ref element.

   For example:

   <?xml version="1.0" encoding="UTF-8"?>
   <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
     http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
   
    <resource-env-ref>
     <resource-env-ref-name>jdbc/DsWebAppDB</resource-env-ref-name>
     <resource-env-ref-type>javax.sql.DataSource</resource-env-ref-type>
    </resource-env-ref>
   </web-app>

   Note

   The preceding example uses a a jdbc/DsWebAppDB data source.

Procedure

1. Open the JWS_HOME/tomcat/conf/server.xml configuration file.

2. In the server.xml file, add the HTTP/2 upgrade protocol to the connector.

   For example:

   <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
              maxThreads="150" SSLEnabled="true">
       <UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
       <SSLHostConfig>
           <Certificate certificateKeystoreFile="/KeyStore.jks"
                        certificateKeystorePassword="changeit"
                        type="RSA" />
       </SSLHostConfig>
   </Connector>

   The server.xml file contains an example connector definition for the APR protocol with the upgrade protocol set to HTTP/2.

   For example:

   <Connector port="8443"
              protocol="org.apache.coyote.http11.Http11AprProtocol"
              maxThreads="150" SSLEnabled="true" >
       <UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
       <SSLHostConfig>
           <Certificate certificateKeyFile="conf/localhost-rsa-key.pem"
                        certificateFile="conf/localhost-rsa-cert.pem"
                        certificateChainFile="conf/localhost-rsa-chain.pem"
                        type="RSA" />
       </SSLHostConfig>
   </Connector>

3. To apply the configuration updates, restart the Red Hat JBoss Web Server as the root user.

   • To restart JBoss Web Server on Red Hat Enterprise Linux by using systemd, enter the following command:

     # systemctl restart jws5-tomcat.service

   • To restart JBoss Web Server on Red Hat Enterprise Linux by using startup.sh, enter the following commands:

     # JWS_HOME/sbin/shudown.sh
     # JWS_HOME/sbin/startup.sh

   • To restart JBoss Web Server on Microsoft Windows, enter the following command:

     # net restart tomcat9

Procedure

1. To check that the HTTP/2 protocol is active, enter the following command:

   $ curl -I http://<JBoss_Web_Server>:8080/

   Note

   In the preceding example, replace <JBoss_Web_Server> with the URI of the modified connector, such as example.com. The port number is dependent on your configuration.

Procedure

1. Stop Tomcat if it is already running.
2. Open the JWS_HOME/tomcat/conf/catalina.properties file.

3. In the catalina.properties file, enter the following line:

   org.apache.tomcat.util.digester.PROPERTY_SOURCE=org.apache.tomcat.vault.util.PropertySourceVault

   Note

   In the preceding example, replace JWS_HOME with the path to your JBoss Web Server installation. The paths shown in this example use a forward slash (/) for directory separators.

Procedure

1. Go to the JWS_HOME/tomcat/conf/ directory.
2. Create a file named vault.properties.

3. In the vault.properties file, enter the vault configuration properties that you specified when you initialized the password vault for Tomcat.

   For example:

   KEYSTORE_URL=JWS_HOME/tomcat/vault.keystore
   KEYSTORE_PASSWORD=MASK-3CuP21KMHn7G6iH/A3YpM/
   KEYSTORE_ALIAS=my_vault
   SALT=1234abcd
   ITERATION_COUNT=120
   ENC_FILE_DIR=JWS_HOME/tomcat/

Procedure

1. Go to the directory that contains the tomcat-vault.sh script:

   • If you installed the password vault from an archive file, go to the JWS_HOME/tomcat/bin directory.
   • If you installed the password vault from an RPM package, go to the /opt/rh/jws5/root/usr/bin directory.

2. To use the tomcat-vault.sh script in noninteractive mode, enter the following command:

   $ ./tomcat-vault.sh \
    --keystore JWS_HOME/tomcat/vault.keystore \
    --keystore-password <vault_password> \
    --alias my_vault \
    --enc-dir JWS_HOME/tomcat \
    --iteration 120 \
    --salt 1234abcd \
    --vault-block my_block \
    --attribute manager_password \
    --sec-attr P@SSW0#D

Procedure

1. Open the Tomcat configuration file that contains the sensitive string.

2. Replace the sensitive string with the attribute name for the string, and ensure that you enter the attribute name in the following format: ${VAULT::block_name::attribute_name::}

   For example:

   Consider the following example file entry for the secured string, P@SSW0#D:

   <user username="manager" password=*"P@SSW0#D"* roles="manager-gui"/>

   If the secured string, P@SSW0#D, has the attribute name, manager_password, replace the secured string with the following value:

   <user username="manager" password=*"${VAULT::my_block::manager_password::}"* roles="manager-gui"/>