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:
When you have an environment that contains different versions of
IBM Integration Bus, the following tasks have limitations:
- Editing source artifacts in the IBM Integration Toolkit
- Artifacts cannot be shared between different versions of the IBM Integration Toolkit. Changes made to an artifact
by using the IBM Integration Toolkit make the
artifact incompatible with earlier versions of the IBM Integration Toolkit. You should consider branching
your version control system when you migrate to a new version.
- Building BAR files from
artifacts
- Your build system must use the same or later version as the IBM Integration Toolkit system that was used to
create the artifact. A build system cannot build a BAR file from an artifact that
was created or edited in a later version of the IBM Integration Toolkit.
- Deploying BAR files to
an integration node
- You can deploy BAR files
that are built with one version of IBM Integration Bus (by
using the IBM Integration Toolkit, mqsicreatebar, or mqsipackagebar) to an integration
node at a later version. You do not have to rebuild your BAR files. However it is not supported
to deploy BAR files to an integration
node at an earlier version. The BAR files
are likely to contain new properties that will cause deployment errors.
- Connecting a Java™ administration
application to a remote integration node.
- Java administration applications
(including the IBM Integration Toolkit and commands)
that use the IBM Integration Bus Version 10.0 Integration
API code can be connected to only Version 10.0 integration nodes.
Administration applications that use API code from a version earlier
than Version 10.0, cannot administer
a Version 10.0 integration node.
Coexistence on Windows
The following
restrictions apply to coexistence on
Windows:
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 part of a shared installation
or part of 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.n/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
Coexistence on z/OS
The following
restrictions apply to coexistence on
z/OS®:
- 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 must have a unique name and a different
PDSE and HFS location.
- 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.
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.