For details about how to register HiRDB as the resource manager in the transaction manager, see the applicable transaction manager documentation. Specification of information in the transaction manager is explained as follows.
For a WebLogic Server, perform the operations listed beginning in (6) below.
HiRDB's RM switch name determines whether dynamic or static registration is used. The following shows the HiRDB's RM switch name (xa_switch_t structure-name):
The RM name(resource manager name) defined in the RM switch (xa_switch_t structure) is HiRDB_DB_SERVER.
If you are using the multi-connection facility, specify the open character string to be used when the transaction manager opens the resource manager with xa_open. If you are not using the multi-connection facility, there is no need to specify an open character string. If the transaction manager is TP1/EE, specify the open character string for a single HiRDB that has been registered. For the TUXEDO or WebLogic Server transaction manager, you cannot use the multi-connection facility.
To use the multi-connection facility, register multiple HiRDBs in the transaction manager and specify the open character string for each HiRDB. For the open character string, specify the following information:
Use one of the following formats:
An open character string in any other format is ignored. The environment variable group ID always consists of four bytes, and the open character string cannot be longer than 256 bytes.
The following shows an example of registering the open character string for the OpenTP1, TPBroker, or TP1/EE transaction manager.
Register the open character string using the trnstring operand in OpenTP1's transaction service definition. This example registers two HiRDBs in OpenTP1. The registration conditions are as follows:
Resource manager | Environment variable group ID | Environment variable setup file name |
---|---|---|
HiRDB1 | HDB1 | /usr/conf/HiRDB/HiRDB11.ini /usr/conf/HiRDB/HiRDB12.ini |
HiRDB2 | HDB2 | /usr/conf/HiRDB/HiRDB21.ini /usr/conf/HiRDB/HiRDB22.ini |
The following shows an example of registering the open character string:
trnstring -n HiRDB_DB_SERVER -i H1 -o "HDB1*/usr/conf/HiRDB/HiRDB11.ini" |
trnrmid -n HiRDB_DB_SERVER -i H1,H2 |
Register the open character string using the xa_open_string_info operand in TPBroker's resource manager definition. This example registers two HiRDBs in TPBroker. The registration conditions are as follows:
Resource manager | Environment variable group ID | Environment variable setup file name |
---|---|---|
HiRDB1 | HDB1 | /usr/conf/HiRDB/HiRDB11.ini /usr/conf/HiRDB/HiRDB12.ini |
HiRDB2 | HDB2 | /usr/conf/HiRDB/HiRDB21.ini /usr/conf/HiRDB/HiRDB22.ini |
The following shows an example of registering the open character string:
tsdefvalue /OTS/RM/HiRDB_DB_SERVER_1/DMN/xa_open_string_info 1 |
tsdefvalue /OTS completion_process_env -a 'TPRMINFO='
Register the open character string using the trnstring operand in the TP1/EE transaction-related definition. This example registers two HiRDBs in TP1/EE. The registration conditions are as follows:
Resource manager | Environment variable group ID | Environment variable setup file name |
---|---|---|
HiRDB1 | HDB1 | /usr/conf/HiRDB/HiRDB11.ini /usr/conf/HiRDB/HiRDB12.ini |
HiRDB2 | HDB2 | /usr/conf/HiRDB/HiRDB21.ini /usr/conf/HiRDB/HiRDB22.ini |
The following shows an example of registering the open character string:
trnstring -n HiRDB_DB_SERVER -i H1 -o "HDB1*/usr/conf/HiRDB/HiRDB11.ini" \ |
There is no need to specify a character string to enable the transaction manager to close the resource manager using xa_close.
For the RM-related object name, specify the library name listed in Table 8-5. The suffix for the shared library depends on the platform. The suffix is .so in Solaris and Linux, and .a in AIX 5L. The archive library name is common to all platforms.
Table 8-5 Library names for RM-related object names
Library type | Library name | |
---|---|---|
Shared library | Single thread | libzclty.sl (libzcltx.sl) |
Single thread (Multi-connection facility supported) | libzcltys.sl11 (libzcltxs.sl) | |
Multi-thread (Multi-connection facility supported)2 | libzcltyk.sl (libzcltxk.sl) | |
Archive library | Single thread | libcltya.a (libcltxa.a) |
To enable the transaction manager to control HiRDB transaction processing, the HiRDB client environment definition must be specified in the transaction manager definitions. For details about how to specify the client environment definition in an OLTP environment, see the manual HiRDB Version 8 UAP Development Guide.
If the transaction manager is OpenTP1, the client environment definition must be specified in the putenv format in the following OpenTP1 system definitions:
For details about these definitions, see the manual OpenTP1 System Definition.
To connect to multiple OpenTP1s, be sure to specify the following client environment definition:
Specify the client environment definition in TPBroker's system definition.
Specify the client environment definition in the file that was specified with the ENVFILE parameter in the TUXEDO configuration file (UBBCONFIG file). For details about the TUXEDO configuration file, see the TUXEDO documentation.
The WebLogic Server process environment variables must contain the specifications for the client environment definition.
If the transaction manager is TP1/EE, you must specify the client environment definition in the following system definitions for the OpenTP1 that is in the TP1/EE execution environment:
For details about these definitions, see the manual OpenTP1 System Definition.
If you connect to multiple TP1/EEs, make sure that the following client environment definition is specified:
When HiRDB is registered, the following JDBC driver package name and driver class name must be specified: