Hitachi

uCosminexus Application Server System Design Guide


3.5.1 Integration between servers invoking Session Bean and Entity Bean

This subsection describes the configuration for invoking Session Beans and Entity Beans from the J2EE server that runs on another Application Server machine.

Organization of this subsection

(1) Features of the system configuration

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

[Figure]

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

Features
  • You can use this configuration for integrating the applications. Use the configuration for invoking the server application from multiple client applications.

  • You can also use this configuration for integrating the systems. If an already built client system and server system are changed as per this configuration, you can invoke the applications between the systems.

Flow of requests

The client side J2EE server sends the requests to the Session Beans or Entity Beans forming the server side access points.

At this point, the Session Beans or Entity Beans are accessed in the client side by looking up the names from the CORBA Naming Service that is invoked as an in-process in the J2EE server on the server-side application server.

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

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.

(a) Client-side application server machine (execution environment of servlets or JSPs)

You need to install Application Server on client-side application server machine that operates the servlets and JSPs.

Invoke the following processes:

  • Web server

  • J2EE server

  • Administration Agent

  • PRF daemon

(b) Client-side application server machine (execution environment of Message-driven Beans)

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:

  • J2EE server

  • Administration Agent

  • PRF daemon

(c) Server-side application server machine

You need to install Application Server on the server-side application server machine.

Invoke the following processes:

  • J2EE server

  • Administration Agent

  • PRF daemon

(d) Management Server machine

You need to install Application Server on the Management Server machine.

Invoke the following process:

  • Management Server