Hitachi

uCosminexus Application Server System Design Guide


3.8.1 Configuration in which a Message-driven Bean is used as the access point (when using Cosminexus JMS provider)

This subsection describes the configuration where a Message-driven Bean of the J2EE server is invoked using Cosminexus JMS provider.

In this configuration, Application Server on receiving machine is invoked via CJMSP Broker from Application Server on the sending machine that sends the message. An application configured with servlets, JSPs, Entity Beans, Session Beans, or Message-driven Beans operates in Application Server on the sending machine. The component that is the access point on the receiving machine is a Message-driven Bean.

Organization of this subsection

(1) Features of the system configuration

This configuration is one of the most basic message-driven systems.

The following figure shows an example of the message-driven system configuration for using Cosminexus JMS provider:

Figure 3‒42: Example of the message driven system configuration (for using Cosminexus JMS provider)

[Figure]

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

Features

In Application Server on the sending machine, J2EE client applications that use a JMS interface and CJMSP resource adapter are used for sending messages.

Request flow

The Message-driven Bean, which is the access point, operates on the J2EE server of Application Server on the receiving machine. The CJMSP resource adapter library in the resource adapter operates on the J2EE server of Application Server on the sending machine and the receiving machine.

The request message from the J2EE application of Application Server on the sending machine is sent through CJMSP Broker, and the Message-driven Bean on Application Server on the receiving machine is invoked.

Note that you can allocate Application Server for the sending machine, Application Server for the receiving machine, and CJMSP Broker on the same machine.

(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.

(a) Application Server machine (Application Server machine on the sending machine)

You must install Application Server on the Application Server machine (Application Server machine on the server machine).

The following are the processes to be started:

  • J2EE server

  • Administration Agent

  • PRF daemon

(b) Application Server machine (Machine for allocating CJMSP Broker)

You must install Application Server on the machine where CJMSP Broker is allocated.

CJMSP Broker is the process to be started. Furthermore, Management Server does not manage the CJMSP Broker.

(c) Application Server machine (Application Server machine on the receiving machine)

You must install Application Server on the client machine (Application Server machine on the client machine).

The processes to be started are as follows:

  • J2EE server

  • Administration Agent

  • PRF daemon

(d) Management Server machine

You must install Application Server on the Management Server machine.

The process to be started is as follows:

  • Management Server