Show Table of Contents
19.6.2. Configure JBoss EAP 6 to Communicate with Apache Mod_jk
Overview
The mod_jk HTTP connector has a single component, the mod_jk.so module loaded by the web server. This module receives client requests and forwards them to the container, in this case JBoss EAP 6. JBoss EAP 6 must also be configured to accept these requests and send replies back to the web server.
Configuring the Apache HTTP Server is covered in Section 19.6.3, “Install the mod_jk Module Into the Apache HTTP Server (ZIP)”.
In order for JBoss EAP 6 to be able to communicate with the Apache HTTP server, it must have the AJP/1.3 connector enabled. This connector is present by default in the following configurations:
- In a managed domain, in server groups using the
haandfull-haprofiles, and thehaorfull-hasocket binding group. Theother-server-groupserver group is configured correctly in a default installation. - In a standalone server, the
standalone-haandstandalone-full-haprofiles are configured for clustered configurations. To start the standalone server with one of these profiles, issue the following command, from theEAP_HOME/directory. Substitute the appropriate profile name.[user@host bin]$
./bin/standalone.sh --server-config=standalone-ha.xml
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.