3.6.1 Configuration when using a local transaction
This subsection describes the configuration when only one resource participates in the transaction.
- Organization of this subsection
(1) Features of the system configuration
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]](GRAPHICS/ZU032800.GIF)
Note: For other legend items, see 3.2 Description of the system configuration.
- Features
-
In this configuration, one resource manager will be accessed from the application. A two-phase commit is not required.
- Flow of accessing the resource manager from the application through the resource adapter
-
Servlets and JSPs that are accessed from the Web browser through the Web server locally invoke a Session Bean existing in the same application. A Session Bean accesses the resource manager (HiRDB in the case of the figure) 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 local 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 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:
-
Web server
-
J2EE server
-
Administration Agent
-
PRF daemon
(b) Machine on which the resource manager is running
Install any of the following software on the machine on which the resource manager is running:
-
HiRDB (when connecting to HiRDB)
-
Oracle (when connecting to Oracle)
-
SQL Server (when connecting to SQL Server)
-
XDM/RD E2 (when connecting to XDM/RD E2)
-
TP1/Message Queue (when connecting to TP1/Message Queue)
-
TP1/Server Base (when connecting to SPP of OpenTP1)
Invoke the required processes in the respective resource managers.
(c) Management Server machine
You need to install Application Server on the Management Server machine.
Invoke the following process:
-
Management Server
(d) Web client machine
A Web browser is required on the Web client machine.