This subsection describes the configuration when only one resource participates in the transaction.
In this configuration, one resource manager is accessed from a single J2EE application consisting of servlets, JSPs, and Session Beans, through a resource adapter. The resource manager manages the transaction used for accessing the resource manager from the application. The transaction type is a local transaction that does not use an XA interface.
The following figure shows an example configuration when using a local transaction:
Figure 3-34 Example configuration when using a local 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 local 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 |
SQL Server | JDBC driver for SQL Server |
XDM/RD E2 | HiRDB Run Time or HiRDB Type4 JDBC Driver |
TP1/Message Queue | TP1/Message Queue - Access |
SPP of OpenTP1 | uCosminexus TP1 Connector TP1/Client/J |
Invoke the following processes:
Install any of the following software on the machine on which the resource manager is running:
Invoke the required processes in the respective resource managers.
You need to install Application Server on the Management Server machine.
Invoke the following process:
A Web browser is required on the Web client machine.