See information about the latest product version
Updating ODBC definitions when migrating
Before you migrate a broker, create ODBC definitions for user databases that specify appropriate database drivers for WebSphere® Message Broker Version 8.0.
The database drivers that are supported by WebSphere Message Broker Version 8.0 might be at a later version than the drivers used by WebSphere Message Broker Version 7.0 or WebSphere Message Broker Version 6.1.
Complete this update before you run the mqsimigratecomponents command for the broker that uses these ODBC connections.
Follow the instructions that are provided for your operating system:
- Windows systems
- To change the ODBC connection definitions:
- Open the ODBC Data Source Administrator window.
- Open the System DSN page.
- For each Oracle and Sybase database that is accessed by the broker,
compare the ODBC driver against the entries that are listed in the
following table. If the ODBC driver does not match, you must associate
the data source name with the new ODBC driver by using the following
instructions:
- Delete the data source by clicking Remove.
- 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 WebSphere Message Broker Version 8.0 ODBC driver name Oracle WebSphere Message Broker DataDirect Technologies 6.0 32-BIT Oracle Wire Protocol Sybase WebSphere Message Broker DataDirect Technologies 6.0 32-BIT Sybase Wire Protocol
- To change the XA resource manager definitions:
- Open the Properties window of the broker queue manager by using the WebSphere MQ Services snap-in.
- Open the Resources page.
- For each Oracle and Sybase database that participates in a global
unit of work that is coordinated by the broker queue manager, change
the contents of the SwitchFile field. For changes
to the switch file configuration to take effect, you must restart
the broker queue manager.The following table specifies what you must change for each database management system (DBMS). WBIMB represents the fully qualified path name of the directory in which you installed WebSphere Message Broker.
DBMS Change ... To ... Oracle WBIMB\bin\ukor8dtc22.dll or
WBIMB\bin\ukor8dtc23.dllWBIMB\bin\ukora24.dll Sybase WBIMB\bin\ukase22.dll or
WBIMB\bin\ukase23.dllWBIMB\bin\ukase24.dll
- Linux and UNIX systems
- To change the ODBC connection definitions:
- Create an ODBC definitions file by following the instructions in Connecting to a database from Linux and UNIX systems by using the WebSphere Message Broker ODBC Database Extender. Before you run the commands at the new service level, check that your ODBCINI environment variable points to the new file and not to the existing file. Check that ODBCSYSINI environment variable is set to point to the directory that contains your odbcinst.ini file.
- To change the XA resource manager definitions:
- To change the XA resource manager definitions, edit the queue
manager configuration file (qm.ini) of the queue
manager that is associated with the broker. The qm.ini file
is located at /var/mqm/qmgrs/queue_manager_name/qm.ini,
where queue_manager_name is the name of the queue
manager that is associated with the broker.
In the XAResourceManager stanza for each Oracle and Sybase database that participates in a global unit of work that is coordinated by the broker queue manager, change the entry for the switch file. For changes to the switch file configuration to take effect, you must restart the broker queue manager.
The following table specifies what you must change for each broker operating system and database management system (DBMS).
DBMS Change ... To ... Oracle SwitchFile=UKor8dtc22.so or
SwitchFile=UKoradtc22.soor
SwitchFile=UKor8dtc23.soor
SwitchFile=UKoradtc23.soSwitchFile=UKoradtc24.so Sybase (not supported on Linux on IBM® z Systems) SwitchFile=UKasedtc22.so or
SwitchFile=UKasedtc23.soSwitchFile=UKasedtc24.so To check that your ODBC environment is set up correctly on Linux and UNIX systems, run the mqsicvp command. This command also validates the connection to all data sources that are listed in the odbc.ini file that are associated with a broker by using the mqsisetdbparms command. For more information, see mqsicvp command.
If you revert to a previous version of WebSphere Message Broker, you must reverse the changes that you make to the ODBC definitions. Update your ODBC files after you run the mqsimigratecomponents command, but before you restart the broker at the earlier version.