3.2.2 Deployment of a firewall for Session and Entity Bean

(1) System configuration features

In this configuration, the firewall is installed before the Session and Entity Bean as seen from the EJB clients.

The figure below shows this configuration.

Figure 3‒2: Example configuration providing access to Session and Entity Bean via a firewall

For other examples, see 3.2 Description of the system configuration in the uCosminexus Application Server System Design Guide.

Features

Because access to the Session and Entity Bean 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 Session and Entity Bean from all EJB clients goes through the firewall.

To Page Top

(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 Session and Entity Bean as access points. See 3.4.3 Configuration with Session Beans and Entity Beans as access points in the uCosminexus Application Server System Design Guide.

To Page Top