3.5.2 Integration between the servers that invokes Stateless Session Bean through CTM

This subsection describes a configuration using CTM, when you invoke Stateless Session Beans from a J2EE server exists on another Application Server through CTM.

Organization of this subsection
(1) Features of the system configuration
(2) Required software and process to be started on each machine

(1) Features of the system configuration

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

[Figure]

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

Features
  • This is a configuration used in the integration between applications. This configuration is suitable when invoking a server application from multiple client applications.
  • This can also be used for integration between the systems. Since this system configuration includes the already built client side system and the server side system, the application can be invoked between the systems.
Request flow
The requests of a Stateless Session Bean, which is the access point at server side, are sent from the J2EE server at client side through CTM.
The name from the global CORBA Naming Service of the server-side application is looked up at the client side and the Stateless Session Bean is accessed through CTM.
The request through CTM can be appropriately distributed to a Stateless Session Bean running on the J2EE server by CTM.

(2) Required software and process to be started on each machine

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.

(a) Application server machine at client side (Execution environment of Servlet/JSP)

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:

(b) Application server machine at client side (Execution environment of Session Bean)

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:

(c) Application server machine at server side

You must install Application Server on the Application Server machine at server side.

The processes to be started are as follows:

(d) Management Server machine

You must install Application Server on the Management Server machine.

The process to be started is as follows: