Changing the ODBC connection and XA resource manager definitions for a migrated broker

WebSphere Business Integration Message Broker includes new versions of the ODBC drivers supplied by DataDirect Technology (formerly Merant). These ODBC drivers are for Oracle and Sybase databases. A new version of the DataDirect Driver Manager for UNIX systems is also included.

When you migrate a broker from the Version 2.1 level of code to the Version 5.0 level on a UNIX or Windows system, you must change the ODBC connection definition for each Oracle and Sybase database accessed by the broker because of the new versions of the ODBC drivers. If the broker is on AIX, you must also change the ODBC connection definition for each DB2 database accessed by the broker. This is because the new version of Driver Manager on AIX requires a different ODBC driver for DB2. Databases accessed by a broker are the broker database and any databases accessed by the message flows that run in the broker.

If a message flow running in the broker updates an Oracle or Sybase database within a global unit of work coordinated by the broker queue manager, you must also change the XA resource manager definition for the database. This is another consequence of the new versions of the ODBC drivers for Oracle and Sybase databases.

You must make the required changes before you start the broker at the Version 5.0 level of code. The following sections describe the changes in detail.

You might already have made the required changes on the broker system for another reason. In this case, you can use the information in this topic to check your configuration.

Changing the ODBC connection definitions

UNIX systems

To change the ODBC connection definitions on a UNIX system, edit the .odbc.ini file. The ODBCINI environment variable specifies the fully qualified path name of the .odbc.ini file.

In the data source name stanza for each Oracle and Sybase database accessed by the broker, and for each DB2 database accessed by the broker if it is running on AIX, change the entry for the ODBC driver. The following tables specify what you need to change for each broker platform and database management system (DBMS).

On AIX:
DBMS Change ... To ...
DB2 Driver=INSTHOME/sqllib/lib/db2.o 1 Driver=INSTHOME/sqllib/lib/libdb2.a 1
Oracle Driver=  /usr/opt/mqsi/merant/lib/UKor816.so Driver=  /usr/opt/mqsi/merant/lib/UKor818.so
Sybase Driver=  /usr/opt/mqsi/merant/lib/UKase16.so Driver=  /usr/opt/mqsi/merant/lib/UKase18.so
Note:
  1. INSTHOME is the fully qualified path name of the directory where you have installed the DB2 instance.
On HP-UX:
DBMS Change ... To ...
Oracle Driver= /opt/mqsi/merant/lib/UKor816.sl Driver= /opt/mqsi/merant/lib/UKor818.sl
Sybase Driver= /opt/mqsi/merant/lib/UKase16.sl Driver= /opt/mqsi/merant/lib/UKase18.sl
On Solaris:
DBMS Change ... To ...
Oracle Driver= /opt/mqsi/merant/lib/UKor816.so Driver= /opt/mqsi/merant/lib/UKor818.so
Sybase Driver= /opt/mqsi/merant/lib/UKase16.so Driver= /opt/mqsi/merant/lib/UKase18.so

Windows systems

To change the ODBC connection definitions on a Windows system, open the ODBC Data Source Administrator window. Open the System DSN page and, for each Oracle and Sybase database accessed by the broker, associate the data source name with the new ODBC driver. To do this, first delete the data source by clicking Remove, then recreate the data source with the new ODBC driver by clicking Add. The following table displays the name of the new ODBC driver for each database management system (DBMS):
DBMS New ODBC driver
Oracle MQSeries DataDirect Technologies 4.10 32-BIT Oracle
Sybase MQSeries DataDirect Technologies 4.10 32-BIT Sybase

Changing the XA resource manager definitions

UNIX systems

To change the XA resource manager definitions on a UNIX system, edit the queue manager configuration file (qm.ini) of the broker queue manager. This file is in the queue manager's directory.

In the XAResourceManager stanza for each Oracle and Sybase database that participates in a global unit of work coordinated by the broker queue manager, change the entry for the switch file. The following tables specify what you need to change for each broker platform and database management system (DBMS).

On AIX:
DBMS Change ... To ...
Oracle
SwitchFile= 
  /usr/opt/mqsi/merant/lib/UKor8dtc16.so
SwitchFile= 
  /usr/opt/mqsi/merant/lib/UKor8dtc18.so
Sybase
SwitchFile= 
  /usr/opt/mqsi/merant/lib/UKase16.so
SwitchFile= 
  /usr/opt/mqsi/merant/lib/UKase18.so
On Solaris:
DBMS Change ... To ...
Oracle
SwitchFile= 
  /opt/mqsi/merant/lib/UKor8dtc16.so
SwitchFile= 
  /opt/mqsi/merant/lib/UKor8dtc18.so
Sybase
SwitchFile= 
  /opt/mqsi/merant/lib/UKase16.so
SwitchFile= 
  /opt/mqsi/merant/lib/UKase18.so

You do not need to change the queue manager configuration file on HP-UX.

Windows systems

To change the XA resource manager definitions on a Windows system, open the Properties window of the broker queue manager using the WebSphere MQ Services snap-in. Open the Resources page and, for each Oracle and Sybase database that participates in a global unit of work coordinated by the broker queue manager, change the contents of the SwitchFile field. The following table specifies what you need to change for each database management system (DBMS):
DBMS Change ... To ...
Oracle WMQIB\bin\UKor8dtc16.dll 1 WBIMB\bin\UKor8dtc18.dll 2
Sybase WMQIB\bin\UKase16.dll 1 WBIMB\bin\UKase18.dll 2
Notes:
  1. WMQIB is the fully qualified path name of the directory where you originally installed WebSphere MQ Integrator Broker or WebSphere MQ Integrator.
  2. WBIMB is the fully qualified path name of the directory where you have installed WebSphere Business Integration Message Broker.

Related tasks
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0
Migrating a Version 2.1 broker to Version 5.0
Configuring databases for coordinated message flows