Home

	Expand Search

XA Interface Integration Guide for CICS, Encina, and TUXEDO Adaptive Server Version 12.5

Chapter 3 Configuring the XA Environment

XA configuration file for DTM XA Interface

XA configuration file for DTM XA Interface

The DTM XA Interface to Adaptive Server provides mechanisms for configuring the Open Client connections using the XA configuration file. Set all connection capabilities, properties, and options using the XA configuration file.

Environment variable for specifying configuration file

The DTM XA Interface uses the environment variable XACONFIGFILE to find the full path and file name of the XA configuration file. You can set this environment variable to specify different locations and names to use for configuration information as necessary.

For example, on UNIX platforms:

setenv XACONFIGFILE /usr/u/sybase/xaconfig1.txt

If XACONFIGFILE is not defined, or if it does not specify a valid configuration file, the DTM XA Interface looks for a file named xa_config in the following directories:

• $SYBASE/$SYBASE_OCS/config

• $SYBASE/$SYBASE_OCS

• $SYBASE/config

• $SYBASE

The DTM XA Interface uses the first xa_config file it finds.

[all] section for defining common LRM parameters

The DTM XA Interface uses the [all] section to define parameters that apply to all LRMs.

Certain parameters defined in the [all] section--log file and trace flag definitions--may also be defined in the open string for X/Open XA transaction managers.

Entries for the [all] section in the XA configuration file are as follows:

[all]
logfile=logfile_name
traceflags=[xa | xl | xc | cm| event | misc | os | ct | all]
[properties=name=value] [...]

Table 3-3 describes each component.

Editing the XA configuration file

You must customize the XA configuration file for the application environment. Use the text editor of your choice to open the XA configuration for editing. The sample contents of an XA configuration file are as follows:

; Comment line as first line of file REQUIRED!
;
; xa_config - sample xa_config file.
;
; Note that the Adaptive Server names may need 
; to be customized for your environment.

; simprpc.ct sample application entry.

[all]
         logfile=logfile_name
        traceflags=traceflags
        properties=name=value [, name=value] [...]
 [xa]
         lrm=connection1
         server=sqlserver
 
 ; Rentapp sample xa_config entries.
 
 [xa]
         lrm=FLEET_CON
         server=fleetsrv
 
 [xa]
         lrm=RESERVE_CON
         server=rsrvsrv

The first line of the xa_config file MUST be a comment which is denoted by a semicolon (;) in the first character position.

For each additional LRM, create an entry with the following format. Keep the connection1 entry for installation verification.

[xa]
 <tab> lrm=connection_name
 <tab> server=adaptive_server_name
 <tab> capabilities=name=value [, name=value] [...]
 <tab> properties=name=value [, name=value] [...]
 <tab> options=name=value [, name=value] [...]

The connection_name is the symbolic name for the connection between the application and SQL. The adaptive_server_name is the name of the Adaptive Server associated with the connection. adaptive_server_name must correspond to a server name defined in the interfaces file.

See "Additional capabilities, properties, and options" for information a list of capabilities, properties, and options that can be used with the DTM XA Interface.

Additional capabilities, properties, and options

XA configuration file entries for capabilities, properties, and options have the following general format:

<tab> capabilities=name=value [, name=value] [...]
 <tab> properties=name=value [, name=value] [...]
 <tab> options=name=value [, name=value] [...]

Table 3-4, Table 3-5, and Table 3-6 list the names for capabilities, properties, and options that can be defined in the XA configuration file for the DTM XA Interface. Unless otherwise specified in these tables, the valid values for each capability, property, or option are CS_TRUE or CS_FALSE.

All names and values for these capabilities, properties, and options correspond to CS-Library keywords. See the Open Client Client-Library/C Reference Manual for specific descriptions.