Configuring XA Transaction Managers to Use DB2 UDB1

 
 

Administration Guide


Configuring XA Transaction Managers to Use DB2 UDB

The sections that follow describe how to configure specific products to use DB2 as a resource manager. You can use any of the following:

    “Configuring IBM TXSeries CICS”

    “Configuring IBM TXSeries Encina”

    “Configuring BEA Tuxedo”

    “Configuring Microsoft Transaction Server”.

Configuring IBM TXSeries CICS

For information about how to configure IBM TXSeries CICS to use DB2 as a resource manager, refer to your IBM TXSeries CICS Administration Guide. TXSeries documentation can be viewed online at starting at http://www.transarc.com/dfs/public/www/htdocs/.hosts/external/Library/index.html

Host and AS/400 database servers can participate in CICS-coordinated transactions.

Configuring IBM TXSeries Encina

The following are the various API and configuration parameters required for the integration of Encina Monitor and DB2 Universal Database servers or DB2 for MVS, DB2 for OS/390, DB2 for AS/400, or DB2 for VSE&VM when accessed via DB2 Connect. TXSeries documentation can be viewed online starting at http://www.transarc.com/dfs/public/www/htdocs/.hosts/external/Library/index.html

Host and AS/400 database servers can participate in Encina-coordinated transactions.

Configuring DB2

To configure DB2:

1.    Each database name must be defined in the DB2 database directory. If the database is a remote database, then a Node Directory entry must also be defined. You can perform the configuration using the GUI Client Configuration Assistant (CCA), or the DB2 Command Line Processor (CLP). For example:

2.     DB2 CATALOG DATABASE inventdb AS inventdb AT NODE host1 AUTH SERVER

3.    

4.    DB2 CATALOG TCPIP NODE host1 REMOTE hostname1 SERVER svcname1

5.    The DB2 client can optimize its internal processing for Encina if it knows that it is dealing with Encina. You can specify this by setting the tp_mon_name database manager configuration parameter to ENCINA. The default is for no special optimization. If tp_mon_name is set, then the application must ensure the thread that performs the unit of work also immediately commits the work after ending it. No other unit of work may be started. If this is not your environment, then ensure that the value for tp_mon_name value is NONE (or via the CLP, the value is set to NULL). The tp_mon_name can be updated by invoking the CCA or by the CLP:

o    On AIX use: UPDATE DATABASE MANAGER CONFIGURATION USING TP_MON_NAME ENCINA

o    On Windows NT use: UPDATE DATABASE MANAGER CONFIGURATION USING TP_MON_NAME libEncServer:E

In Intel environments, this parameter contains the path and name of the DLL in an external transaction manager product containing the functions ax_reg and ax_unreg, and also informs DB2 which TP Monitor is being used.

Configuring Encina for Each Resource Manager

To configure Encina for each resource manager, an administrator must define the Open String, Close String, and Thread of Control Agreement for each DB2 database as a resource manager before the resource manager can be registered for transactions in an application. The configuration can be performed using the Enconcole full screen interface, or the Encina command line interface. For example:

monadmin create rm inventdb -open “inventdb,user1,password1”

There is one resource manager configuration for each DB2 database, and each resource manager (RM) configuration must have an rm name (“logical RM name”). To simplify the situation, you should make it identical to the database name.

The XA Open String contains information that is required to establish a connection to the database. The content of the string is RM specific. The XA Open String of DB2 UDB contains the alias name of the database to be opened, and optionally a userid and password to be associated with the connection. Note that the database name defined here must also be cataloged into the regular database directory required for all database access. The name can be up to 8 bytes long.

The XA Close String is not used by DB2.

The Thread of Control Agreement determines if an application agent thread can handle more than one transaction at a time. DB2 V5.0 supports the default of TMXA_SERIALIZE_ALL_OPERATIONS, where a thread can be reused only after a transaction has completed.

If you are accessing DB2 for OS/390, DB2 for MVS, DB2 for AS/400, or DB2 for VSE&VM, then you must use the DB2 Syncpoint Manager. Please refer to the DB2 Connect Enterprise Edition Quick Beginnings manual for configuration instructions.

Referencing a DB2 Database from an Encina Application

To reference a DB2 database from an Encina application:

     

如果这文章对你有帮助,请扫左上角微信支付-支付宝,给于打赏,以助博客运营

发表评论

您的电子邮箱地址不会被公开。 必填项已用*标注