3.8.2 Configuration in which a Message-driven Bean is used as the access point (when using TP1/Message Queue)

(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 TP1/Message Queue:

Figure 3‒43: Example of the message driven system configuration (for using TP1/Message Queue)

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

Features

A Message Queue client application and TP1/Message Queue that send TP1/Message Queue messages are used at the client. Note that the Message Queue client application is a J2EE application that uses a JMS interface.

Request flow

The Message-driven Bean, which is the access point, operates on the J2EE server of the Application Server at the server side. TP1/Message Queue - Access library, which exists in the resource adapter, operates on the J2EE server of the Application Server at the server side, and on the J2EE server of the Application Server at the client side.

The request message (message) is sent from the J2EE application of the Application Server at the client side through TP1/Message Queue, and invokes the Message-driven Bean on the Application Server at the server side.

To Page Top

(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. For details about the processes to connect to resource, see 3.6 Determining the transaction type.

To Page Top