3.4.3 Configuration with Session Beans and Entity Beans as access points

(1) Features of the system configuration

You can build the most basic EJB client configuration by using client machines and one Application Server machine.

The following figure shows an example of an EJB client configuration built with one Application Server machine:

Figure 3‒30: Example of EJB client configuration built with one Application Server machine

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

Feature

In Windows, you can use uCosminexus Client to build the environment on the client machine.

Flow of requests

The Session Beans and Entity Beans forming the access points run on the J2EE server. The requests from the EJB client application are sent to the access points by RMI-IIOP to invoke a Session Bean and Entity Bean. At this point, the EJB client application searches (lookup) for names from the Naming Service running on the J2EE server and accesses a Session Bean and Entity Bean.

To Page Top

(2) Required software and processes to be invoked on the respective machines

This subsection describes the required software and the processes to be invoked on the respective machines. For details about the processes used for connecting to the resources, see 3.6 Determining the transaction type.

To Page Top