Chapter 17. Web Subsystem

17.1. Configure the Web Subsystem

You can configure most aspects of the Web subsystem using the web-based Management Console or the command-line Management CLI. Each setting is explained in the order it appears in the Management Console, and Management CLI commands are also provided.
View the Web Subsystem Using the Management Console

To configure the Web Subsystem using the web-based Management Console, click the Configuration tab at the top of the screen. Expand the Subsystems menu and then expand the Web menu. Each configurable part of the Web subsystem is shown.


The mod_cluster component is only available if your profile is ha or full-ha, in a managed domain, or if you start your standalone server with the standalone-ha or standalone-full-ha profile. mod_cluster configuration is covered in Section 19.5.2, “Configure the mod_cluster Subsystem”.
Configure the JSP Container, HTTP Connectors, and Virtual HTTP Servers

To configure the JSP Container, HTTP connectors, and virtual HTTP servers, click the Servlet/HTTP menu entry. Click the Edit button to change any values. Click the Advanced button to view advanced options. The options are explained below. Options for HTTP connectors and virtual servers are shown in separate tables.

Table 17.1. Servlet/HTTP Configuration Options

Option Description CLI Command
Instance ID
The identifier used to enable session affinity in load balancing scenarios. The identifier must be unique across all JBoss EAP servers in the cluster and is appended to the generated session identifier. This allows the front-end proxy to forward the specific session to the same JBoss EAP instance. The instance ID is not set as a default.
If true, disables the Java ServerPages (JSP) container. Defaults to false. This is useful if you do not use any JSPs.
If true, enables Development Mode, which produces more verbose debugging information. Defaults to false.
Keep Generated?
Click Advanced to see this option, if it is hidden. If true, keeps generated Servlets. Defaults to true.
Check Interval?
Click Advanced to see this option, if it is hidden. A value in seconds, which determines how often to check for JSP updates using a background process. Defaults to 0.
Display Source?
Click Advanced to see this option, if it is hidden. If true, the JSP source fragment is displayed when a runtime error occurs. Defaults to true.
AJP and HTTP connectors use mod_cluster, mod_jk, mod_proxy, ISAPI, and NSAPI for load balancing and HA clustering. To configure a connector, select the Connectors tab and click Add. To remove a connector, select its entry and click Remove. To edit a connector, select its entry and click Edit.
When you create a new connector using the Management CLI, its options are all set at once, as in the following command:

Example 17.1. Create a New Connector


Table 17.2. Connector Options

Option Description CLI Command
A unique name for the connector, for display purposes.
Socket Binding
The named socket binding to which the connector is to be bound. A socket binding is a mapping between a socket name and a network port. Socket bindings are configured for each standalone server, or via socket binding groups in a managed domain. A socket binding group is applied to a server group.
The web connector scheme, such as HTTP or HTTPS.
The web connector protocol to use, such as AJP or HTTP.
Whether or not this web connector is enabled.
Redirect Port
Used to specify a port number to be used in cases of redirection; the common ones being redirection to secure (https) or AJP connector
Redirect Binding
Redirect binding is similar to redirect port in terms of behavior except that it requires specification of a socket-binding name in "value" instead of a port number. redirect-binding provides higher configuration flexibility because it allows the use of pre-defined socket binding (https, AJP etc.) to the specific port for redirection. It gives the same results as redirect-port option.
To configure virtual servers, click the Virtual Servers tab. Use the Add button to add a new virtual server. To edit or remove a virtual server, select its entry and click the Edit or Remove button.
When you add a new virtual server using the Management CLI, all required options are set at once, as in the following command.

Example 17.2. Add a New Virtual Server


Table 17.3. Virtual Servers Options

Option Description CLI Command
A unique name for the virtual server, for display purposes.
A list of hostnames which should match this virtual server. In the Management Console, use one hostname per line.
Default Module
The module whose web application should be deployed at the root node of this virtual server, and will be displayed when no directory is given in the HTTP request.