Hitachi

uCosminexus Application Server Compatibility Guide


6.1 Organization of this chapter

Application Server provides an in-process HTTP server as Web server functionality. The in-process HTTP server is Web server functionality provided in the J2EE server processes. Since the J2EE server processing receives the HTTP request directly without passing through the Web server, you can use the Web server functionality with better processing performance than during the Web server integration.

The following table lists the functionality and the reference sections corresponding to the functionality of the in-process HTTP server:

Table 6‒1: Functionality and reference sections corresponding to each functionality of in-process HTTP server

Functionality

Reference

Overview of in-process HTTP server

6.2

Controlling the number of connections from the Web client

6.3

Controlling the number of request processing threads

6.4

Controlling the flow of requests by controlling the number of concurrent connections from the Web client

6.5

Controlling the flow of requests by controlling the number of concurrently executing threads

6.6

Request distribution with the redirector

6.7

Controlling the communication with the Web client by Persistent Connection

6.8

Communication timeout (In-process HTTP server)

6.9

Specifying the IP address (In-process HTTP server)

6.10

Controlling access by limiting the hosts that are allowed access

6.11

Controlling access by limiting the request data size

6.12

Controlling access by limiting the HTTP-enabled methods

6.13

Customizing responses to the Web client using HTTP responses

6.14

Error page customization (in-process HTTP server)

6.15

Notifying the gateway information to the Web container

6.16

Output of log and trace

6.17

URI decode functionality

6.18

Settings for acquiring the in-process HTTP server log

6.19

cjtracesync (synchronize trace file information for in-process HTTP server)

6.20

Precautions when operating SOAP applications

6.21