The EDB PostgreSQL module provides two-phase commit support using PostgreSQL-provided SQL calls, and ensures that any database connections made using this switch module all participate in a single XA transaction.
ESPGSQLXA.so | 32-bit | dynamic |
ESPGSQLXA64.so | 64-bit | dynamic |
ESPGSQLXA_S.so | 32-bit | static |
ESPGSQLXA64_S.so | 64-bit | static |
You can register an RM switch module with Enterprise Server dynamically, or register it statically depending on which binary file you use. We recommend that you use the dynamic switch module option, as this ensures that only active databases used in the global transaction participate in the TM/RM XA flow.
Your enterprise server region requires an XA resource for each datastore that contains one or more transactional files. If the database containing the datastore is also used by other COBOL applications, additional XA resources are required. Refer to Working with Multiple XARs for details on how to handle such situations.
Option | Description |
---|---|
ID | Unique ID for the XAR. |
Name | Unique name for the XAR. |
Module | Specify the location of the RM switch module executable file (.dll on Windows or .so on UNIX platforms). This is database specific: esmssql.dll/.so for MSSQL and Azure SQL, ESPGSQLXA.dll/.so for PostgreSQL, and ESDB2XA.dll/.so for Db2. Refer to Building RM Switch Modules for more information. |
Open string | DSN=<datastore-dsn>
where <datastore-dsn> is the ODBC data source name of the datastore you are configuring. Note: These are only the mandatory options required, with the addition of
USRPASS=userid.password if you are using a PostgreSQL database. You can also specify further options as required, as detailed in
To Define an XA Resource (XAR) for an Enterprise Server Region.
|
The XA resource should be effective immediately.