8.2.8 Modifying the registration information in the transaction manager
To modify registration information in the transaction manager, use the following procedure to reregister HiRDB in the transaction manager. Because a WebLogic Server can use static registration only, the registration cannot be modified.
- Organization of this subsection
- (1) OpenTP1
- (2) TPBroker
- (3) TUXEDO
- (4) TP1/EE
(1) OpenTP1
To modify registration information in the transaction manager when using OpenTP1:
- Use OpenTP1's trnlnkrm command to reregister HiRDB in the transaction manager.
- Use OpenTP1's trnmkobj command to re-create the object file for transaction control.
- Relink all UAPs with HiRDB's XA library on the basis of the object file for transaction control re-created in step 2 and the information described in 8.2.6 Information to be registered in the transaction manager. Otherwise, UAP operation cannot be guaranteed.
(2) TPBroker
To modify registration information in the transaction manager when using TPBroker:
- Use TPBroker's tslnkrm command to reregister HiRDB in the transaction manager.
- Use TPBroker's tsmkobj command to re-create the object file for transaction control.
- Relink all UAPs with HiRDB's XA library on the basis of the object file for transaction control re-created in step 2 and the information described in 8.2.6 Information to be registered in the transaction manager. Otherwise, UAP operation cannot be guaranteed.
(3) TUXEDO
(4) TP1/EE
- To modify registration information in the transaction manager when using TP1/EE:
- Use TP1/EE's eetrnmkobj command to reregister HiRDB in the transaction manager.
- Use TP1/EE's eetrnmkobj command to re-create the resource manager linkage object file.
- Relink all UAPs with HiRDB's XA library on the basis of the resource manager linkage object file re-created in step 2 and the information described in 8.2.6 Information to be registered in the transaction manager. Otherwise, UAP operation cannot be guaranteed.