This subsection describes the configuration where the respective J2EE servers connect to the different resources in the case of an integrated server configuration. Use transaction context propagation in this configuration. Note that CTM cannot be used for this 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.
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.