This subsection describes the configuration for invoking Session Beans and Entity Beans from the J2EE server that runs on another Application Server machine.
In this configuration, the Application Server instance on the client side invokes the Application Server instance on the server side. An application consisting of servlets, JSPs, Entity Beans, Session Beans, or Message-driven Beans runs on the client-side application server. The access point component of the server side is either a Session Bean or an Entity Bean. The invocation from the client-side application is executed by RMI-IIOP.
The following figure shows an example configuration of integration between servers that invoke Session Beans and Entity Beans:
Figure 3-32 Example of the configuration for integration between servers that invoke Session Bean and Entity Bean
Note: For other legend items, see 3.2 Description of the system configuration.
This subsection provides information about the required software and the processes to be invoked in the respective machines when integrating the servers that invoke Session Beans or Entity Beans. For details about the processes required for connecting to the resources, see 3.6 Determining the transaction type.
You need to install Application Server on client-side application server machine that operates the servlets and JSPs.
Invoke the following processes:
You need to install Application Server on the client-side application server machine that operates the Message-driven Bean. To use TP1/Message Queue - Access as a resource adapter, you must install TP1/Message Queue - Access. If you use Cosminexus RM, you need not install TP1/Message Queue - Access separately because TP1/Message Queue - Access is included in Application Server.
Invoke the following processes:
You need to install Application Server on the server-side application server machine.
Invoke the following processes:
You need to install Application Server on the Management Server machine.
Invoke the following process: