3.6.2 Configuration when using a global transaction

This subsection describes the configuration, when multiple resources participate in a transaction.

Organization of this subsection
(1) Features of the system configuration
(2) Required software and the processes to be invoked on the respective machines

(1) Features of the system configuration

In this configuration, multiple resource managers are accessed from a single J2EE application consisting of Session Beans, through the resource adapter. The J2EE server manages the transaction that is used for accessing the resource manager from the application. The transaction type is a global transaction that uses an XA interface.

The following figure shows an example configuration when you use a global transaction. The following figure shows an example of the configuration of a system using CTM:

Figure 3-35 Example configuration when using a global transaction

[Figure]

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

Features
  • In this configuration, multiple resource managers will be accessed from the application. A two-phase commit is required.
  • You need to implement this configuration even in a system where the applications that access the single resource manager and applications that access multiple resource managers are mixed.
Flow of accessing the resource manager from the application through the resource adapter
A Stateless Session Bean that is accessed from the EJB client application accesses the resource manager through the resource adapter.

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

This subsection describes the required software and the processes to be invoked on the respective machines when you use a global transaction:

(a) Application server machine

You need to install Application Server on the Application Server machine.

The following software is required for connecting to the resource manager:

Resource manager to be connected toRequired software
HiRDBHiRDB Run Time or HiRDB Type4 JDBC Driver
OracleOracle Client or Oracle JDBC Thin Driver
TP1/Message QueueTP1/Message Queue - Access
SPP of OpenTP1uCosminexus TP1 Connector
TP1/Client/J

Note: You cannot use SQL Server and XDM/RD E2 in a global transaction.


Invoke the following processes:

In a configuration where CTM is used, you must install Application Server and start the global CORBA Naming Service, CTM processes, CTM domain manager, and Smart Agent apart from the above processes. For details, see 3.5.2 Integration between the servers that invokes Stateless Session Bean through CTM.

(b) Machine on which the resource manager is running

You install any of the following software on the machine on which the resource manager is running. You cannot use SQL Server and XDM/RD E2 in a global transaction.

Invoke the processes required on the respective resource managers.

(c) Management Server machine

You need to install Application Server on the Management Server machine.

Invoke the following process:

(d) EJB client machine

You need to install Application Server or the uCosminexus Client (in the case of Windows) on the EJB client machine.

Invoke the processes of the EJB client application.