This subsection describes the configuration, when multiple resources participate in a transaction.
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
Note: For other legend items, see 3.2 Description of the system configuration.
This subsection describes the required software and the processes to be invoked on the respective machines when you use a global transaction:
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 to | Required software |
---|---|
HiRDB | HiRDB Run Time or HiRDB Type4 JDBC Driver |
Oracle | Oracle Client or Oracle JDBC Thin Driver |
TP1/Message Queue | TP1/Message Queue - Access |
SPP of OpenTP1 | uCosminexus 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.
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.
You need to install Application Server on the Management Server machine.
Invoke the following process:
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.