Generating a UTM database connection

You must generate the UTM database connection in the KDCDEF statement RMXA. Here you specify:

• the name of the xa_switch_t structure as preset by the database used

• for Windows systems: whether the xa_switch_t structure is addressed with dllimport; when linking with Oracle, dllimport must always be used for addressing

• Database access data (user name, password).

  These specifications are optional. If you want to store the access data in the UTM generation then you must use placeholders in the open string for the user name and the password.

As a rule, there is a static and dynamic XA switch. A database can provide one or both variants. If the database provides a dynamic XA switch, you should use this, as this minimizes resource occupancy in the database system.

For further details on the RMXA statement, refer to the openUTM manual “Generating Applications” and the description of the RMXA statement.

Configuration of the dynamic XA switch of Oracle on Windows systems

When the dynamic XA switch xaoswd is used for the XA connection with Oracle on Windows systems, you must first extend the Windows Registry by adding the entry ORA_XA_REG_DLL.

To do this, perform the following steps after installing Oracle Client and openUTM:

1. Start the Windows Registry Editor in the Windows prompt with the regedit command.

2. Permit system access in the User Accounts tab of the control panel.

3. Under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE select the keyKEY_OraClientnnHome1, e.g. KEY_OraClient12Home1.

4. In the Edit menu select the command New -> Expandable String Value and enter the following:

   • For Name (default setting New Value #1) the value ORA_XA_REG_DLL

   • For Type the value REG_EXPAND_SZ.

   • For Data the fully qualified name of the installed dynamic openUTM library (libwork.dll), e.g. C:\openUTM-Server\ex\libwork.dll.

5. Confirm with OK and terminate the Registry Editor.

The Windows system is thus configured with openUTM and Oracle for use with the dynamic Oracle XA connection.

Important!
To ensure that the XA connection between openUTM and Oracle was configured correctly, the following must be checked once: xa_reg calls are logged in the following manner by openUTM when logging of the CA interface is performed and when updates are integrated into the Oracle database

kdcrtxa-<pid>: AX_CALL-1: ax_reg, XID.GTRID=<utm-gtrid-value>

If the openUTM XA debug information contains no entries of the aforementioned type, or if the Oracle XA debug information contains xa_reg calls which display the NULL XIDs, a serious configuration problem exists!

You enable the logging of the XA interface by means of the "XA debug" function (e.g. with KDCDIAG), see openUTM manual “Administering Applications” and section "Debug parameters".