17.4. Web Server Configuration

Procedure 17.3. Install the Apache HTTP Server

1. Navigate to the JBoss EAP downloads list for your platform, on the Red Hat Customer Portal.

   Log in to the Customer Portal and navigate to the Software Downloads page. Select the appropriate Product and Version.

2. Choose the Apache HTTP Server binary from the list.

   Find the Apache HTTP Server option for your operating system and architecture. Click the Download link. A Zip file containing the Apache HTTP Server distribution downloads to your computer.

3. Extract the Zip to the system where the Apache HTTP Server binary will run.

   Extract the Zip file on your preferred server, to a temporary location. The Zip file will contain the httpd directory under a jboss-ews-version-number folder. Copy the httpd folder and place it inside the EAP_HOME directory.
   Your Apache HTTP Server is now located in the EAP_HOME/httpd/ directory. This directory is referred to as HTTPD_HOME.

4. Run the Post-installation script and create the apache user and group accounts

   In a terminal emulator, navigate to the EAP_HOME/httpd directory and execute the following command with root user privileges.

   ./.postinstall

   Next, verify that the apache user exists on the system by running the following command:

   id apache

   If the user does not exist then it will need to be added, along with the appropriate usergroup. In order to achieve this, execute the following with root user privileges:

   getent group apache >/dev/null || groupadd -g 48 -r apache
   getent passwd apache >/dev/null || useradd -r -u 48 \
   -g apache -s /sbin/nologin  -d HTTPD_HOME/httpd/www -c "Apache" apache
   

   Once this is completed, if the apache user will be running the Apache HTTP Server service, then the ownership of the HTTP directories will need to be changed to reflect this:

   chown -R apache:apache httpd

   To test that the above commands have been successful, check that the apache user has execution permission to the Apache HTTP Server install path.

   ls -l

   The output should be similar to:

   drwxrwxr-- 11 apache apache 4096 Feb 14 06:52 httpd

5. Configure the Apache HTTP Server.

   Prior to starting the Apache HTTP Server, configure it to meet the needs of your organization. You can use the documentation available from the Apache Foundation at http://httpd.apache.org/ for general guidance.

6. Start the Apache HTTP Server.

   Start the Apache HTTP Server using the following command:

   HTTPD_HOME/httpd/sbin/apachectl start

7. Stop the Apache HTTP Server.

   To stop the Apache HTTP Server, issue the following command:

   HTTPD_HOME/httpd/sbin/apachectl stop

Procedure 17.4. Install and Configure Apache HTTP Server in Red Hat Enterprise Linux 5 and 6 (RPM)

1. Install httpd

   To install the JBoss EAP specific version of httpd package run the following command:

   yum install httpd

   To install httpd explicitly from Red Hat Enterprise Linux (RHEL) channels run the following command:

    yum install httpd --disablerepo=jbappplatform-6-*

   Note

   You must run only one of the above commands to install the httpd package on your system.

2. Set the Service Boot Behavior

   You can define the service behavior for the httpd service at boot from the command line or with the service configuration graphical tool. Run the following command to define the behavior:

    chkconfig httpd on

   To use the service configuration tool run the following command and change the service setting in the displayed window:

    system-config-services

3. Start httpd

   Start httpd using the following command:

   service httpd start

4. Stop httpd

   Stop httpd using the following command:

   service httpd stop

Procedure 17.5. Install and Configure Apache HTTP Server in Red Hat Enterprise Linux 7 (RPM)

1. Install httpd22

   To install the JBoss EAP specific version of httpd22 package run the following command:

   yum install httpd22

2. Set the Service Boot Behavior

   Run the following command to start the httpd22 service at boot:

   systemctl enable httpd22.service

3. Start httpd22

   Start httpd22 using the following command:

   systemctl start httpd22.service

4. Stop httpd22

   Stop httpd22 using the following command:

   systemctl stop httpd22.service

Procedure 17.6. Install the Apache HTTP Server service for Microsoft Windows Server environment

• Install the Apache HTTP Server service using this command.

  cd /D "%EWS_HOME%\bin"
  httpd -k install

  This command installs an Apache HTTP Server service named Apache2.2.
  To specify a different name for the service, for example, ApacheBalancer, use the following command.

  cd /D "%EWS_HOME%\bin"
  httpd -k install -n ApacheBalancer

Procedure 17.7. Start the Apache HTTP Server service for Microsoft Windows Server environment

• To start a service, you can either use httpd.exe or service manager.

  Using httpd.exe:

  cd /D "%EWS_HOME%\bin"
  httpd -k start -n Apache2.2

  Using service manager:

  net start Apache2.2

Procedure 17.8. Stop the Apache HTTP Server service for Microsoft Windows Server environment

• To stop a service, you can either use httpd.exe or service manager.

  Using httpd.exe:

  cd /D "%EWS_HOME%\bin"
  httpd -k stop -n Apache2.2

  Using service manager:

  net stop Apache2.2

Procedure 17.9. Uninstall the Apache HTTP Server service for Microsoft Windows Server environment

• To uninstall a service, it must be referenced by name. For example, to uninstall the service names ApacheBalancer, use the following command.

  cd /D "%EWS_HOME%\bin"
  httpd -k uninstall -n ApacheBalancer

Procedure 17.10. Edit Configuration and add Socket Bindings

1. Configure the jvmRoute system property.

   For a standalone mode instance, remove the prefix /host=NODE_NAME. Replace NODE_NAME with the name of the host.

   /host=NODE_NAME/system-property=jvmRoute/:add(value=NODE_NAME)

2. List the connectors available in the web subsystem.

   Note

   This step is only necessary if you are not using the ha or full-ha profiles for either a standalone server, or a server group in a Managed Domain. Those configurations already include all of the necessary connectors.
   In order for an external web server to be able to connect to JBoss EAP 6's web server, the web subsystem needs a connector. Each protocol needs its own connector, which is tied to a socket group.
   To list the connectors currently available, issue the following command:

   /subsystem=web:read-children-names(child-type=connector)

   If there is no line indicating the connector your need (HTTP, HTTPS, AJP), you need to add the connector.

3. Read the configuration of a connector.

   To see the details of how a connector is configured, you can read its configuration. The following command reads the configuration of the AJP connector. The other connectors have similar configuration output.

   /subsystem=web/connector=ajp:read-resource(recursive=true)
   {
       "outcome" => "success",
       "result" => {
           "enable-lookups" => false,
           "enabled" => true,
           "max-post-size" => 2097152,
           "max-save-post-size" => 4096,
           "protocol" => "AJP/1.3",
           "redirect-port" => 8443,
           "scheme" => "http",
           "secure" => false,
           "socket-binding" => "ajp",
           "ssl" => undefined,
           "virtual-server" => undefined
       }
   }
   

4. Add the necessary connectors to the web subsystem.

   To add a connector to the web subsystem, it must have a socket binding. The socket binding is added to the socket binding group used by your server or server group. The following steps assume that your server group is server-group-one and that your socket binding group is standard-sockets.

   1. Add a socket to the socket binding group.

      To add a socket to the socket binding group, issue the following command, replacing the protocol and port with the ones you need.

      /socket-binding-group=standard-sockets/socket-binding=ajp:add(port=8009)

   2. Add the socket binding to the web subsystem.

      Issue the following command to add a connector to the web subsystem, substituting the socket binding name and protocol with the ones you need.

      /subsystem=web/connector=ajp:add(socket-binding=ajp, protocol="AJP/1.3", enabled=true, scheme="http")