Problem:

What do you do if you have a legacy code which uses the AT SQL statement to explicitly use an Oracle named database connection. How can you deploy this code as a service within Enterprise Server, using an XA connection?

How can you set a XA resource manager which sets an Oracle named connection? How can you install more XA resources managers within the same Enterprise Server region?

Resolution:

You just have to use the Optional field DB of the Oracle XA_open string. As described in Oracle® Database Application Developer's Guide – Fundamentals

Oracle XA_open string, optional field DB

DBSpecifies the database name

Db_nameIndicates the name used by Oracle Database precompilers to identify the database.

XA Open string set within Enterprise Server region

XA connection 1

ID: XA_CNN1

NAME: Oracle_XA_CNN1

Module: C:\\Program Files\\Micro Focus\\Net Express 5.1\\Base\\SOURCE\\ENTERPRISESERVER\\XA\\ESORA10XA.DLL

OpenString :

Oracle_XA_CNN1 SesTm=100 SqlNet=connect_string Acc=P/OracleUserID/OraclePasswd DB=Connection1

XA connection 2

ID: XA_CNN2

NAME: NAME: Oracle_XA_CNN2

Module: C:\\Program Files\\Micro Focus\\Net Express 5.1\\Base\\SOURCE\\ENTERPRISESERVER\\XA\\ESORA10XA.DLL

OpenString :

Oracle_XA_CNN2 SesTm=100 SqlNet=connect_string Acc=P/OracleUserID/OraclePasswd DB=Connection2

Incident Number: 2429116