3.4.4 Configuration where Stateless Session Bean is used as access point when using CTM
This subsection describes about the system configuration where a Stateless Session Bean is used as the access point when you use CTM.
- Reference note
-
An example of EJB client configuration is explained here where an EJB client application is used as the client. When you use the CTM gateway function, you can implement a configuration where an EJB application on the J2EE server is directly invoked from a client application other than an EJB client. For details about the configurations, see 3.13.3 Configuration in which a Stateless Session Bean is invoked from other than an EJB client using the CTM gateway function.
- Organization of this subsection
(1) Features of the system configuration
This system configuration is one of the EJB client configurations. The scheduled requests are transmitted by CTM to a Stateless Session Bean, which is the access point.
The following figure shows an example of EJB client configuration when using CTM:
|
|
![[Figure]](GRAPHICS/ZU032500.GIF)
Note: For other legend items, see 3.2 Description of the system configuration.
- Features
-
-
Request scheduling is executed by the CTM and the system operations such as executing service lock and controlling the concurrent execution count can be executed.
-
Start two or more J2EE servers. If an error occurs on a J2EE server, the system operation can be continued by executing degeneration operation.
-
In Windows, the environment of the client machine can be built using uCosminexus Client.
-
- Requests flow
-
A Stateless Session Bean, which is the access point, operates on the J2EE server.
The requests from the EJB client application are transmitted through the CTM and invoke the Stateless Session Bean. In such cases, the EJB client application looks up the name from the global CORBA Naming Service and accesses Stateless Session Bean.
(2) Required software and processes to be started on each machine
This subsection describes the required software and processes to be started on the respective machines. For details about the processes to connect to a resource, see 3.6 Determining the transaction type.
(a) Application server machine
You must install Application Server on the Application Server machine.
The processes to be started are as follows:
-
J2EE server
-
Administration Agent
-
PRF daemon
-
Global CORBA Naming Service
-
CTM processes (CTM daemon and CTM regulator)
-
CTM domain manager
-
Smart Agent
(b) Management Server machine
You must install Application Server on Management Server machines.
The process to be started is as follows:
-
Management Server
(c) EJB client machine
You must install Application Server or uCosminexus Client (in Windows) on EJB clients.
The process to be started is the processing for EJB client application.