7.2.7 Example of registering in the transaction manager

Organization of this subsection
(1) OpenTP1
(2) TPBroker for C++
(3) TUXEDO
(4) WebLogic Server

(1) OpenTP1

To register HiRDB in OpenTP1, use OpenTP1's trnlnkrm command. The following shows examples of trnlnkrm command specification:

(a) Dynamic registration

trnlnkrm -a HiRDB_DB_SERVER -s pdtxa_switch
-o C:\win32app\hitachi\hirdb_s\client\lib\pdcltx32.lib

Explanation:
-a: Specifies the RM name.
-s: Specifies the RM switch name (name of the XA switch structure). The RM switch name depends on the registration method (dynamic or static).
-o: Specifies the RM-related object name (shared library's file name).
(b) Static registration

trnlnkrm -a HiRDB_DB_SERVER -s pdtxa_switch_y
-o C:\win32app\hitachi\hirdb_s\client\lib\pdcltx32.lib

Explanation:
-a: Specifies the RM name.
-s: Specifies the RM switch name (name of the XA switch structure). The RM switch name depends on the registration method (dynamic or static).
-o: Specifies the RM-related object name (shared library's file name).

(2) TPBroker for C++

To register HiRDB in TPBroker for C++, use TPBroker for C++'s tslnkrm command. The following shows examples of tslnkrm command specification:

(a) Dynamic registration

tslnkrm -a HiRDB_DB_SERVER_1 -s pdtxa_switch
-o 'C:\win32app\hitachi\hirdb_s\client\lib\pdcltxm.lib' -r -m
tslnkrm -a HiRDB_DB_SERVER_2 -s pdtxa_switch
-o 'C:\win32app\hitachi\hirdb_s\client\lib\pdcltxm.lib' -r -m

Explanation:
-a: Specifies the RM name.
-s: Specifies the RM switch name (name of the XA switch structure). The RM switch name depends on the registration method (dynamic or static).
-o: Specifies the RM-related object name (shared library's file name).
-r: Indicates dynamic registration.
-m: Enables OTS daemon operation with multi-thread.
(b) Static registration

tslnkrm -a HiRDB_DB_SERVER_1 -s pdtxa_switch_y
-o 'C:\win32app\hitachi\hirdb_s\client\lib\pdcltxm.lib' -r -m
tslnkrm -a HiRDB_DB_SERVER_2 -s pdtxa_switch_y
-o 'C:\win32app\hitachi\hirdb_s\client\lib\pdcltxm.lib' -r -m

Explanation:
-a: Specifies the RM name.
-s: Specifies the RM switch name (name of the XA switch structure). The RM switch name depends on the registration method (dynamic or static).
-o: Specifies the RM-related object name (shared library's file name).
-r: Indicates static registration.
-m: Enables OTS daemon operation with multi-thread.

(3) TUXEDO

Use the %TUXDIR%\udataobj\RM file to register HiRDB in TUXEDO. %TUXDIR% indicates the absolute path name of the directory that contains the TUXEDO system software. The following shows examples of RM file specification:

(a) Dynamic registration

HiRDB_DB_SERVER;pdtxa_switch;C:\HiRDB\client\lib\pdcltxs.lib

(b) Static registration

HiRDB_DB_SERVER;pdtxa_switch_y;C:\HiRDB\client\lib\pdcltxs.lib

(4) WebLogic Server

Register HiRDB using the driver class name and the provider for the WebLogic Server's JDBC connection pool. An example specification follows:

(a) Static registration

Driver-class-name:JP.co.Hitachi.soft.HiRDB.JDBC.JdbhXADataSource
Property(key=value):user=authorization-identifier
                  password=password
                  XAOpenString=name-defined-by-transaction-data-source
                  dataSourceName=name-specified-by-JDBC-connection-pool
                  Description=name-defined-by-transaction-data-source

Explanation
When HiRDB is registered, the following JDBC driver package name and driver class must be specified:
  • Package-name: JP.co.Hitachi.soft.HiRDB.JDBC
  • Driver-class-name: JdbhXADataSource