3.2.1 Deployment of a firewall for servlets and JSPs
The following is an example of a system configuration that provides access to a servlet and JSP via a firewall.
- Organization of this subsection
(1) System configuration features
In this configuration, the firewall is installed before the servlet and JSP as seen from the Web clients.
The figure below shows this configuration. Note that this configuration is for Web server integration.
|
|
![[Figure]](GRAPHICS/ZU035100.GIF)
For other examples, see 3.2 Description of the system configuration in the uCosminexus Application Server System Design Guide.
- Features
-
Because access to the servlet and JSP goes through the firewall, this system prevents unauthorized third party access to the system, leakage of information handled by applications, and illegal operation by third parties.
- Access from the clients
-
Access to the servlet and JSP from all the clients goes through the firewall.
(2) Machine software required and processes to be activated
When using the firewall, the necessary software and processes to be activated on the application server machine and client machine are the same as those for system configurations that use servlets and JSPs as access points.
For details about a configuration that uses servlets and JSPs as access points, see the following sections:
-
3.4.1 Configuration with servlets and JSPs as access points (for Web server integration), in the uCosminexus Application Server System Design Guide
-
3.4.2 Configuration where servlets and JSPs are used as access points (when accessing the NIO HTTP server directly) in the uCosminexus Application Server System Design Guide