Migration might be affected by 32-bit and
64-bit support on your chosen platforms.
WebSphere
® Message Broker provides support for both 32-bit
and 64-bit platforms. The level of support is different to that provided for
previous versions, therefore you might have to take special action during
migration.
WebSphere Message Broker supports three types
of platforms:
- Platforms that have only 32-bit support. These platforms have 32-bit commands
and a 32-bit broker core, and support 32-bit execution groups.
- Platforms that have 32-bit and 64-bit support. These platforms have 64-bit
commands and a 64-bit broker core, and support both 32-bit and 64-bit execution
groups.
- Platforms that have only 64-bit support. These platforms have 64-bit commands
and a 64-bit broker core, and support only 64-bit execution groups.
Migrating from 32-bit platforms
If you are migrating
a broker from a 32-bit platform to a 64-bit platform:
- You do not have to export 32-bit libraries in the LIBPATH. You must remove
any environment variable settings that are similar to the following example:
export LD_LIBRARY_PATH=[DB2InstanceDir]/sqllib/lib32:$LD_LIBRARY_PATH
export SHLIB_PATH=$ORACLE_HOME/lib32:$SHLIB_PATH
- If you had previously set the following environment variable to use 64-bit
execution groups with DB2®, you can now remove this variable:
export MQSI_LIBPATH64=[DB2InstanceDir]/sqllib/lib64:$MQSI_LIBPATH64
- If you want to continue to use 32-bit execution groups with DB2, you must
set the following variable:
export MQSI_LIBPATH32=[DB2InstanceDir]/sqllib/lib32:$MQSI_LIBPATH32
If
you are migrating, or moving to, only 64-bit executions groups, you do not
need to set this variable.
- The sample ODBC files provided by WebSphere Message Broker have
not changed; .odbc.ini is provided for 32-bit support
and odbc64.ini is provided for 64-bit support. However,
the default environment variables have changed in mqsiprofile:
ODBCINI=/var/mqsi/.odbc.ini
ODBCINI64=/var/mqsi/odbc64.ini
have changed to:ODBCINI=/var/mqsi/odbc64.ini
ODBCINI32=/var/mqsi/.odbc.ini
If you do not want to use the default
values, you must change your environment variables to point to the correct
files.
Migrating 64-bit platforms
WebSphere Message Broker Version
6.1 supports
only 64-bit on some platforms. This section describes additional steps that
you must take when you migrate brokers on or to these platforms.
- Linux® (POWER™ platform)
and Solaris (x86-64 platform)
- DB2 must
run in 64-bit mode on these platforms. If you used WebSphere Message Broker Version 6.0 with DB2 Version
8 in 32-bit mode, you must migrate your DB2 instance and databases to 64-bit before
you migrate the broker.
If you are using DB2 Version 8 or Version 9 in 64-bit mode,
you do not have to complete any additional tasks.
- If you are using any C user-defined extensions, you must be recompile
these programs to be 64-bit compliant.
When you have completed these tasks, continue to migrate your brokers
using the instructions provided.
- Linux (zSeries® platform)
- You cannot migrate brokers that you have created on a computer running
a 31-bit Linux (zSeries platform) operating system to Version 6.1. If you have a Version 6.0 broker
in that environment, you must create a broker in a 64-bit installation and
deploy your resources to the new broker.
- If you have created a Version 6.0 broker
on a computer running a 64-bit Linux (zSeries platform) operating
system, follow the instructions provided above for Linux (POWER platform) and Solaris (x86-64 platform).
- AIX®,
HP-UX, Linux (x86 platform) (64-bit installations
only), and Solaris (SPARC platform)
- If you are using DB2 Version 8.2, and you have a 32-bit execution group
on a Version 6.0 broker on AIX, HP-UX, Linux (x86 platform) (64-bit
installations only), or Solaris (SPARC platform), you
must migrate your DB2 instance to a 64-bit instance before you migrate
the broker.
If you are using DB2 Version 9 on your Version 6.0 systems,
the database supports only 64-bit instances, and you do not have
to take any further action.