3.6.3 Configuration when using transaction context propagation

(1) Features of the system configuration

In this configuration, integration between servers is performed with multiple J2EE applications. This subsection describes an example of integrating servers using a J2EE application that consists of servlets, JSPs, and Session Beans and a J2EE application that consists of only Session Beans. The application that consists of servlets, JSPs, and Session Beans runs on the client-side application server and the J2EE application that consists of Session Beans runs on the server-side application server.

The respective J2EE applications access different resource managers through the resource adapter. In such a case, the J2EE server manages the transactions used when accessing the resource managers. The transaction type is global transaction that uses an XA interface.

In configurations where Stateless Session Bean is invoked by CTM, transaction context propagation cannot be used.

The following figure shows an example of the configuration when you use transaction context propagation. In this example, the J2EE applications access the database and SPP of OpenTP1.

Figure 3‒36: Example configuration when using transaction context propagation

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

Features

• This configuration is applicable when accessing multiple resource managers from applications where server integration is performed.

• You need to implement this configuration when linking servers in a system where applications that access a single resource manager and applications that access multiple resource managers are coexist.

Flow of accessing the resource manager from the application through a resource adapter

The servlets and JSPs that are accessed from the Web browser through the Web server, locally invoke a Session Bean existing in the same application. This Session Bean starts the transaction, accesses the database, and then invokes a Session Bean running on the J2EE server that runs on the server-side application server. The invoked Session Bean that runs on the server-side application server accesses SPP of OpenTP1. A Session Bean running on the client-side application server commits the transaction when the control returns from the server-side Session Bean.

To Page Top

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

The required software and the processes invoked when you use transaction context propagation are same as 3.6.2 Configuration when using a global transaction. However, if you are using transaction propagation of context, CTM cannot be used.

To Page Top