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

WebSphere Message Broker Version 6.0 includes new versions of the ODBC drivers that are supplied by DataDirect Technology (formerly Merant). These ODBC drivers are for Oracle and Sybase databases. A new version of the DataDirect Driver Manager for Linux and UNIX systems is also included. There are a number of changes that you need to make as a result of these new versions of the ODBC drivers for Oracle and Sybase databases.
  • When you migrate a broker from Version 2.1 or Version 5.0 to Version 6.0 on a Linux, UNIX or Windows system, change the ODBC connection definition for each Oracle and Sybase database that is accessed by the broker.
  • In addition, if the broker is on AIX, change the ODBC connection definition for each DB2 database that is accessed by the broker. This is because the new version of Driver Manager on AIX requires a different ODBC driver for DB2. Databases that are accessed by a broker are the broker database and any databases that are accessed by the message flows that run in the broker.
  • You must also change the XA resource manager definition for the database if you have a message flow that is running in the broker and updates an Oracle or Sybase database within a global unit of work that is coordinated by the broker queue manager.

Make the required changes before you start the Version 6.0 broker. The following sections describe the changes in detail.

Changing the 32-bit ODBC connection definitions

Linux and UNIX systems

To change the ODBC connection definitions on a Linux or 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 that is accessed by the broker, and for each DB2 database that is 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 operating system 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 or Driver=  /usr/opt/mqsi/merant/lib/UKor818.so Driver=  <install_dir>/merant/lib/UKor820.so
Sybase Driver=  /usr/opt/mqsi/merant/lib/UKase16.so or Driver=  /usr/opt/mqsi/merant/lib/UKase18.so Driver=  <install_dir>/merant/lib/UKase20.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 or Driver= /opt/mqsi/merant/lib/UKor818.sl Driver= <install_dir>/merant/lib/UKor820.sl
Sybase Driver= /opt/mqsi/merant/lib/UKase16.sl or Driver= /opt/mqsi/merant/lib/UKase18.sl Driver= <install_dir>/merant/lib/UKase20.sl
On Solaris:
DBMS Change ... To ...
Oracle Driver= /opt/mqsi/merant/lib/UKor816.so or Driver= /opt/mqsi/merant/lib/UKor818.so Driver= <install_dir>/merant/lib/UKor820.so
Sybase Driver= /opt/mqsi/merant/lib/UKase16.so or Driver= /opt/mqsi/merant/lib/UKase18.so Driver= <install_dir>/merant/lib/UKase20.so

Windows systems

To change the ODBC connection definitions on a Windows system:
  1. Open the ODBC Data Source Administrator window.
  2. Open the System DSN page.
  3. For each Oracle and Sybase database that is accessed by the broker, associate the data source name with the new ODBC driver:
    1. Delete the data source by clicking Remove.
    2. Re-create 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 5.0 32-BIT Oracle
Sybase MQSeries DataDirect Technologies 5.0 32-BIT Sybase Wire Protocol

Changing the XA resource manager definitions

Linux and UNIX systems using 32-bit ODBC drivers and WebSphere MQ Version 5.0

To change the XA resource manager definitions on a Linux or 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 operating system and database management system (DBMS).

On AIX:
DBMS Change ... To ...
Oracle
SwitchFile= 
  /usr/opt/mqsi/merant/lib/UKor8dtc16.so
or
SwitchFile= 
  /usr/opt/mqsi/merant/lib/UKor8dtc18.so
SwitchFile= 
  <install_dir>/merant/lib/UKor8dtc20.so
Sybase
SwitchFile= 
  /usr/opt/mqsi/merant/lib/UKase16.so
or
SwitchFile= 
  /usr/opt/mqsi/merant/lib/UKase18.so
SwitchFile= 
  <install_dir>/merant/lib/UKase20.so
On Solaris:
DBMS Change ... To ...
Oracle
SwitchFile= 
  /opt/mqsi/merant/lib/UKor8dtc16.so
or
SwitchFile= 
  /opt/mqsi/merant/lib/UKor8dtc18.so
SwitchFile= 
  <install_dir>/merant/lib/UKor8dtc20.so
Sybase
SwitchFile= 
  /opt/mqsi/merant/lib/UKase16.so
or
SwitchFile= 
  /opt/mqsi/merant/lib/UKase18.so
SwitchFile= 
  <install_dir>/merant/lib/UKase20.so
On HP-UX:
DBMS Change ... To ...
Oracle
SwitchFile= 
  /opt/mqsi/merant/lib/libSwitchOracle.sl
SwitchFile= 
	<install_dir>/merant/lib/UKor8dtc20.sl
Sybase
SwitchFile= 
  /opt/mqsi/merant/lib/libSwitchSybase.sl
SwitchFile= 
	<install_dir>/merant/lib/UKasedtc20.sl

Windows systems

To change the XA resource manager definitions on a Windows system:
  1. Open the Properties window of the broker queue manager using the WebSphere MQ Services snap-in.
  2. Open the Resources page.
  3. 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 or WMQIB\bin\UKor8dtc18.dll 1 WBIMB\bin\UKor8dtc20.dll 2
Sybase WMQIB\bin\UKase16.dll 1 or WMQIB\bin\UKase18.dll 1 2WBIMB\bin\UKase20.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 Message Broker Version 6.0.