This subsection describes how to set up the in-process HTTP server.

To receive HTTP requests by using the Web server functionality provided in the J2EE server processes, the system must be built with a configuration using the in-process HTTP server functionality. For details on the system configuration and building with the in-process HTTP server functionality, see the uCosminexus Application Server System Setup and Operation Guide.

Procedure:

1. Enabling the in-process HTTP server functionality.
   Define the specifications for the in-process HTTP server by specifying true in the webserver.connector.inprocess_http.enabled parameter in the <configuration> tag of the logical J2EE server (j2ee-server) in the Easy Setup definition file. By default, false is specified. For details on the Easy Setup definition file and the parameters to be specified, see the uCosminexus Application Server Definition Reference Guide.
   
2. Specify settings for controlling the number of connections from the Web client and controlling the number of request processing threads.
   By adjusting the number of request processing threads according to the performance of the host that operates the server and the status of access from the client, you can improve the performance of the in-process HTTP server. For details on settings, see 5.3 Controlling the number of connections from the Web client and 5.4 Controlling the number of request processing threads.
   Note the following when you set up the in-process HTTP server:
   
   • If a large number of requests need to be processed immediately after the server starts, specify a big value as the number of request processing threads to be created when the server starts.
   • Note that if you increase the maximum number of spare threads, you can promptly support sudden increase in access, but a lot of resources will be consumed.
3. Specify settings for controlling access from the Web client.
   By enhancing the security for connections and requests sent from the client, you can prevent unauthorized access and attacks on the server from outside. For details on settings, see 5.11 Controlling access by limiting the hosts that are allowed access, 5.12 Controlling access by limiting the request data size, and 5.13 Controlling access by limiting the HTTP-enabled methods.
   
4. As and when required, specify settings for the functionality that can be used in the in-process HTTP server.
   For details on the functionality available in the in-process HTTP server, see 5.2.2 Functionality available in the in-process HTTP server.