Coexistence of IBM Integration Bus Version 10.0 with previous
versions
IBM® Integration Bus Version 10.0 can coexist with previous versions so
that you can test and compare functions that changed between a previous version and IBM Integration Bus Version 10.0. You can then control your migration to IBM Integration Bus Version 10.0 by migrating individual integration nodes
one at a time, rather than by migrating all the integration nodes to IBM Integration Bus Version 10.0 at the same time.
Different versions of IBM Integration Bus or WebSphere® Message Broker can coexist and can run independently, and
you can migrate integration nodes from one version to another.
Because different versions and releases can coexist, you can migrate to Version 10.0 from an earlier version in a controlled
manner, and you do not have to migrate all integration nodes at the same time. For more
information, see Migrating.
IBM Integration Bus Version 10.0 can coexist with previous versions as follows:
- IBM Integration Bus
Version 9.0
- WebSphere Message Broker
Version
8.0
- WebSphere Message Broker
Version 7.0.
The following sections describe how to achieve coexistence, and the restrictions that apply for
each platform.
Coexistence on Windows
The following restrictions apply to coexistence on
Windows:
- You can install multiple instances of IBM Integration Bus
on the same computer, but you cannot install multiple instances of a product
version at the same fix pack level; for example, you can install Version 10.0.0.1 on the same computer as
Version 10.0.0.0, but you cannot
install two instances of Version 10.0.0.1
on the same computer.
- All integration nodes from all versions are accessible by all users of the
Windows system, and must have unique
names.
- Each integration node is associated with the product code from a specific
installation location and uses that product code when the integration node
is started.
- If you have more than one installation on a single computer, you must ensure
that the commands that you issue to integration nodes on that computer are
using the correct version of installed code. On Windows, there is an IBM Integration Console available for each installation.
You must run commands in the correct instance of the IBM Integration Console for a particular installation.
If you prefer, you can run the mqsiprofile
command. By default, this command is stored in C:\Program Files\IBM\IIB\10.0.0.0\server\bin.
- For a specific version and release of the product, the product code that is
used by an integration node can be changed from one fix pack level to
another by any of the following methods:
- Start the IBM Integration Console for a different
fix pack level, and start the integration node by using the mqsistart command.
- Start the integration node by using a script that first runs the
mqsiprofile for a
different fix pack level.
- Start the IBM Integration Toolkit for a different
fix pack level. Any local integration nodes that are stopped and
configured to start automatically with the IBM Integration Toolkit use the product code that
is associated with the version of the IBM Integration Toolkit.
Note: These methods are valid only for switching the integration node
between different fix pack levels that are associated with the same
product code version. You must use the mqsimigratecomponents command to
migrate an integration node to a different version and
release.
Coexistence on Linux and UNIX systems
The following restrictions apply to coexistence on
Linux and
UNIX systems:
- You can install multiple instances of IBM Integration Bus
on the same computer, including multiple instances of a product version at
the same fix pack level.
- Each integration node can be either be part of a shared installation or a
single-user installation. Integration nodes that are part of a shared
installation are accessible by all users of the IBM Integration Bus installation. Integration nodes that
are part of a single-user installation are only accessible by a specific
user.
- Integration nodes are not automatically associated with product code from
specific installation locations. Before you start the integration node, you
must run the mqsiprofile command that
is associated with the product code that the integration node should use.
The command is stored in install_dir/iib-10.0.0.0/server/bin, where install_dir is the
directory where you unpacked the IBM Integration Bus
software. If you add the mqsiprofile command to your
system login profile, it is run automatically whenever you log on.
- If you have more than one installation on a single computer, you must ensure
that the commands that you issue to integration nodes on that computer are
using the correct version of installed code. You must run the mqsiprofile command to set up the correct
environment before you run other IBM Integration Bus
commands, such as mqsicreatebroker.
If you have installed an earlier version of this product on the same
computer, check that the earlier mqsiprofile command is not included in
the system profile for the current user ID. The environment that is set
up by the mqsiprofile command of
a previous version of IBM Integration Bus or WebSphere Message Broker is not compatible with a
later version of IBM Integration Bus. To avoid
potential problems, consider using a different user ID for each version
and add the correct command for each version to the system profile of
each user ID. For more information about the mqsiprofile command, see Setting up a command environment
- For a specific version and release of the product, the product code that is
used by an integration node can be changed from one fix pack level to
another by running the mqsiprofile
from a different fix pack level.
Note: This method is valid only for
switching the integration node between different fix pack levels that
are associated with the same product code version. You must use the
mqsimigratecomponents command
to migrate an integration node to a different version and
release.
Coexistence on z/OS
The following restrictions apply to coexistence on
z/OS®:
For more information about locations, libraries, and file system paths for IBM Integration Bus on z/OS,
search for Integration Bus for z/OS on
the
IBM Publications Center website, and download the Program
Directory for your version of IBM Integration Bus.