3.4.2 Configuration where servlets and JSPs are used as access points (when using the in-process HTTP server)

This subsection describes the web-based system configuration where servlets and JSPs are used as access points. The explanation of the configuration using the in-process HTTP server is also mentioned in this subsection.

When connecting to the Internet with this configuration, set up the deployment of a Web server having a reverse proxy function on the DMZ from the security point of view. For details, see 3.3 Determining the deployment of reverse proxy on DMZ in the uCosminexus Application Server Security Management Guide.

Organization of this subsection
(1) Features of the system configuration
(2) Process and software required for each machine

(1) Features of the system configuration

A system configuration applied when processing requests sent from the Web browser on the Application Server, in Web front-end systems.

The most basic Web client configuration can be built with a client machine and one Application Server machine. If you are using the in-process HTTP server, there is no need to start a Web server at the front-end of the J2EE servers. Use functions of HTTP servers on J2EE servers.

The following figure shows the Web client configuration using the in-process HTTP server:

Figure 3-29 Example of Web client configuration built on one Application Server machine (for using in-process HTTP server)

[Figure]

Note: For other legend items, see 3.2 Description of the system configuration.

Features
A Web browser is the only software used by clients.
From the Web browser, direct access to the J2EE server is possible without using Web servers, and hence, the Web browser has a merit of higher performance. Moreover, operations are simple because you need not start a Web server.
If you are using an in-process HTTP server, you must consider the following points:
  • Only minimum functions are supported by the in-process HTTP server as the Web server operation. Therefore if various functions of a Web server are required, this configuration is not appropriate. Select the configuration linked to the Web server embedded with a redirector module. For details about the functions that can be used on the in-process HTTP server, see 5.2.2 Functions that can be used on the in-process HTTP server in the uCosminexus Application Server Web Container Functionality Guide.
  • HTTPS is not supported by the in-process HTTP server. Therefore, for using SSL, use the SSL function of the Web server embedded with the proxy module deploying proxy server at the front-end or deploying SSL accelerator at the front-end.
  • From the security point of view, deploy a reverse proxy at front-end, for systems connected to Internet. For details about the configuration deploying a reverse proxy, see 3.3 Determining the deployment of reverse proxy on DMZ in the uCosminexus Application Server Security Management Guide.
Request flow
Operate servlets and JSPs that are used as access points, on the J2EE server. These components are directly accessed from the Web browser.

(2) Process and software required for each machine

This subsection describes the software and processes required on the respective machines. For details about processes required to connect to resource, see 3.6 Determining the transaction type.

(a) Application server machine

You must install Application Server on the Application Server machine.

The required processes are as follows:

(b) Management Server machine

You must install Application Server on the Management Server machine.

The process to be started is as follows:

(c) Web client machine

A Web client machine must have a Web browser.