This subsection describes a configuration using CTM, when you invoke Stateless Session Beans from a J2EE server exists on another Application Server through CTM.
This is the configuration in which the Application Server on the server side is invoked from the Application Server on the client side through CTM. The application configured with servlet, JSP, Entity Bean. Session Bean, or Message-driven Bean operates on the Application Server at the client side. Stateless Session Bean is the access point component at server side. Invoking from the application at client side is executed by RMI-IIOP.
The following figure shows an example of the configuration of integration between the servers that invoke Stateless Session Bean through CTM:
Figure 3-33 Example of configuration of integration between servers that invoke Stateless Session Bean
Note: For other legend items, see 3.2 Description of the system configuration.
This subsection describes the required software and the processes to be started on the respective machine when integrating between the servers that invoke Stateless Session Beans through CTM. For details about the processes required for connecting to the resources, see 3.6 Determining the transaction type.
You must install Application Server on the Application Server machine at client side where the servlet and JSP operate.
The processes to be started are as follows:
You must install Application Server on the Application Server machine at client side that operates Session Bean.
The processes to be started are as follows:
You must install Application Server on the Application Server machine at server side.
The processes to be started are as follows:
You must install Application Server on the Management Server machine.
The process to be started is as follows: