3.13.2 Configuration for invoking a Message-driven Bean from SUP of OpenTP1 using the TP1 inbound integrated function

(1) Features of the system configuration

The is one type of message driven system.

The following figure shows an example of a message driven system configuration using the TP1inbound integrated function.

Figure 3‒58: Example of message driven system configuration (when using the TP1 inbound integrated function)

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

Features

The TP1 inbound adapter running on a J2EE server receives the requests sent by SUP running on TP1/Server Base and executes the process. You can access the Message-driven Bean on the J2EE server from SUP by the same procedure^# as invoking the SPP.

#

Some of the procedures are different. For details, see 4. Calling Application Server from Open TP1 (TP1 Inbound Linkage Functionality) in the uCosminexus Application Server Common Container Functionality Guide.

Request flow

The Message-driven Bean, which is the access point, and the library of the TP1 inbound adapter, which is the resource adapter, run on the J2EE server of Application Server.

The TP1 inbound adapter of Application Server receives the requests from SUP running on TP1/Server Base of the OpenTP1 system and invokes the Message-driven Bean.

To Page Top

(2) Processes to be invoked and software required on the respective machines

This subsection describes the software required on the respective machines and processes to be started.

To Page Top