Tuxedo uses Transaction Manager Servers (TMS) for distributed transaction processing. You must create a TMS for each Resource Manager (RM). The RM must conform to the X/OPEN XA interface.
Note: This is only needed for Tuxedo Application Servers utilizing XA.
Not all RMs are XA compliant. RMs that are XA compliant include Oracle.
Typically, the Tuxedo administrator builds the TMS for each database before any CA Gen applications are built (that is, compiled and linked) on the server machine.
Building a TMS involves editing the file $TUXDIR/udataobj/RM. This file contains the list of libraries required for linking with the appropriate RM. This file is also used during the Gen server build process, so if the TMS is not built successfully, then the server build fails as well. The environment variables PATH, TUXDIR and SHLIB_PATH should be set before building the TMS.
Note: SHLIB_PATH is the system dependent environment variable used to indicate the location of the shared libraries. Use LD_LIBRARY_PATH on Solaris, LIBPATH on AIX.
Sample RM File
# Copyright (C) 2009 CA, All rights reserved.
# RM file for HPUX:
# Oracle 11g and DB2 9.5
# Copy this file into udataobj directory of your Tuxedo installation
# and rename it to RM, prior to running buildtms command
# ORACLE 11g
Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lclntsh -lsql11 -lpthread
# DB2 9.5
Db2_XA:db2xa_switch:-L{DB2DIR}/lib -ldb2 -lhppa -lm -ldld
Oracle_XA: The RM for Oracle.
A TMS for Oracle_XA can be built as follows:
$TUXDIR/bin/buildtms -o TMS_Oracle101 -r Oracle_XA
TMS_Oracle101: The TMS load module that is created as a result of the above stwp. You need to move this to the $TUXDIR/bin directory.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|