WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Coexistence and migration

WebSphere® Message Broker Version 8.0 can coexist with previous versions.

You can install WebSphere Message Broker Version 8.0 on a computer on which you have installed previous versions, but each version must be installed into its own directory, referred to as install_dir. Different versions can coexist and can run independently, and you can migrate brokers from one version to another, if and when appropriate. For the Broker component and WebSphere Message Broker Toolkit, you can install multiple instances of the same version on the same computer, each in its own separate directory. For example, the Broker component can coexist with different fix pack levels, such as Version 7.0.0.0 with Version 7.0.0.1. You can install multiple instances of the same version of the Broker component and WebSphere Message Broker Toolkit on the same computer, however only one version of WebSphere Message Broker Explorer is allowed.

The following sections provide further details:

Coexistence

WebSphere Message Broker Version 8.0 can coexist with previous versions as follows:
  • The Broker component can coexist with runtime components at Version 7.0.
  • The WebSphere Message Broker Toolkit can coexist with the toolkit at Version 7.0.

The following sections describe how to achieve coexistence, and the restrictions that apply.

Broker component on distributed systems

When you install the Broker component on distributed systems, the default action taken by the installation wizard is to complete a typical installation, which installs the Broker component into a default directory. A default directory for a typical installation is provided, however you can change it if you prefer.

If you accepted the default location during installation, this directory is as follows. The default directory includes the version, release, modification, and fix of the product that you are installing in the format v.r.m.f (version.release.modification.fix):
Linux
/opt/ibm/mqsi/v.r.m.f
UNIX
/opt/IBM/mqsi/v.r.m.f
Windows 32-bit
C:\Program Files\IBM\MQSI\v.r.m.f
Windows 64-bit
C:\Program Files\IBM\MQSI\v.r.m.f for the 64-bit version of WebSphere Message Broker
C:\Program Files (x86)\IBM\MQSI\v.r.m.f for the 32-bit version of WebSphere Message Broker
These locations define the default value of install_dir on each platform.

Each unique version, release, modification, and fix of the product is therefore installed into a different default location.

The installation wizard differentiates at version, release, modification, and fix level; therefore it differentiates between different modification levels and fix pack levels. The current modification level is 0 (Version 8.0.0). If a later modification level is made available, it installs into a different default location, and therefore does not upgrade the Version 8.0.0 to the higher modification level (for example, Version 8.0.1).

The wizard does not install one fix pack over a previous fix pack, and prohibits you from installing a previous modification or fix pack over a more recent one.

You can install the product at the same version and release more than once; these installations can be at the same modification or fix pack level, or at different levels. To achieve concurrent installations, you must select the custom installation option and specify a unique directory for each installation (one of which can be the default directory).

You can also use the custom installation to install into a non-default directory.

If you have never completed a typical installation of the product on the computer on which you have selected a custom installation, the directory is initially set to the default directory, but you can change this default value to your chosen value.

If you attempt to install the Broker component into a directory that already contains an installation of the Broker component at a previous version, you are prompted to confirm that you want to continue with the installation, because it overwrites the existing installation. Cancel the installation and select a different directory to preserve your existing configuration.

If you install the same version and release more than once, the native installer support cannot manage these installations in the normal way. For more information, see How to uninstall multiple installations of the Broker component.

You can use multiple installations at different modification or fix pack levels to test out fixes or new functions, or to stage your adoption of a new fix pack level. For more information, see Applying service.

During and after installation, files are also stored in the working directory, which is associated with the user ID with which you are currently logged on. The location depends on the operating system:

Linux and UNIX
/var/mqsi
Windows
%ALLUSERSPROFILE%\IBM\MQSI
The environment variable %ALLUSERSPROFILE% defines the system working directory. The default directory depends on the operating system:
  • On Windows XP and Windows Server 2003: C:\Documents and Settings\All Users\IBM\MQSI
  • On Windows 7 and later operating systems: C:\ProgramData\IBM\MQSI
The actual location might be different on your computer.

If you have multiple installations on a single computer, you can review the contents of the file install.properties, which is stored in the root of the working directory. For each installation at Version 6.1 and above, the file is updated with the location and the level.

This example shows the contents of install.properties on a Windows 32-bit operating system on which a single installation has completed:

C\:\\Program\ Files\\IBM\\MQSI\\8.0=8.0.0.0

(The backslash character \ is interpreted as an escape character. It is inserted before each non-alphabetic and non-numeric character in the string to preserve the character. A colon, a space, and several backslash characters are escaped in this example.)

If you want to revert from your latest installation to a previous level for any reason, you must uninstall the current version and install the previous level of the product. Before you uninstall, back up any resources that you want to return to a previous state.

Because the version and release are included in the directory structure when you complete a typical installation, you can also install Version 8.0 and later releases on the computer on which you have already installed previous releases of WebSphere Message Broker. The Version 8.0 installation can coexist with the existing installation; you can operate the two configurations independently.

If you use custom installations for Version 8.0 and later releases, you can specify a unique installation directory for each release, and therefore achieve coexisting releases on a single computer.

The number of installations of Version 8.0, or later, is limited only by the availability of system resources.

Because different versions and releases can coexist, you can migrate to Version 8.0 from an earlier version in a controlled manner, and you do not have to migrate all brokers at the same time. For more information, see Migration.

Broker component on z/OS

On z/OS®, you can install multiple copies of the Broker component on the same computer if you specify a different installation location for each copy. The installations can run independently of each other. The code can be at the same or different version and release levels; Version 6.0, Version 6.1, Version 7.0, and Version 8.0. The number of installations is restricted only by the availability of system resources.

For more details about locations, libraries, and file system paths, see the Program Directory for WebSphere Message Broker for z/OS on the WebSphere Message Broker Library web page.

Coexistence with components of the same version

Although you can install multiple versions of the Broker component on the same system, you should not install both an x86 and an x86-64 version, of the same version number, on the same system. Some data files used by the Broker component are specific to each version, and using files of the wrong version with a broker could cause unpredictable results. This warning applies for all versions of the product and for all platforms.

WebSphere Message Broker Toolkit on Linux on x86, Linux on x86-64, and Windows

Linux
When you install the WebSphere Message Broker Toolkit, the default action taken by the installation wizard is to install Installation Manager files, shared files, and product-specific files into the following directories:
  • Installation Manager installation directory:
    /opt/IBM/InstallationManager
  • Shared resources directory:
    /opt/IBM/SDPShared/
  • Package group directory:
    /opt/IBM/WMBT800

    This location defines the default value of install_dir on this platform.

For a description of these directories, see Installing the WebSphere Message Broker Toolkit.

You can install multiple instances of the WebSphere Message Broker Toolkit Version 8.0 at the same modification or fix pack level, or at different levels, on a single computer. Each installation must be in a separate package group; package groups are described in more detail in IBM Installation Manager.

Windows
When you install the WebSphere Message Broker Toolkit, the default action taken by the installation wizard is to install Installation Manager files, shared files, and product-specific files into the following directories:
  • Installation Manager installation directory:
    • C:\Program Files\IBM\InstallationManager for the 32-bit version of WebSphere Message Broker
    • C:\Program Files (x86)\IBM\InstallationManager for the 64-bit version of WebSphere Message Broker
  • Shared resources directory:
    • C:\Program Files\IBM\SDPShared\ for the 32-bit version of WebSphere Message Broker
    • C:\Program Files (x86)\IBM\SDPShared\v.r for the 64-bit version of WebSphere Message Broker
  • Package group directory:
    • C:\Program Files\IBM\WMBT800 for the 32-bit version of WebSphere Message Broker
    • C:\Program Files (x86)\IBM\WMBT800 for the 64-bit version of WebSphere Message Broker

    This location defines the default value of install_dir on this platform.

For a description of these directories, see Installing the WebSphere Message Broker Toolkit.

You can install multiple instances of the WebSphere Message Broker Toolkit at the same modification or fix pack level, or at different levels, on a single computer. Each installation must be in a separate package group; package groups are described in more detail in IBM Installation Manager.

If you install the WebSphere Message Broker Toolkit on Windows and you specify your own directory location, be aware of the file system limit of 256 characters imposed by Windows file systems. This limit can cause restrictions in path specification to resources (for example, message flows), and might cause access problems if the combination of path and resource name exceeds this limit. Keep installation locations and resource names short to avoid problems associated with this restriction.

Setting the environment for an installation

Because you can have more than one installation on a single computer, you must ensure that the commands that you issue on that computer are directed to the correct version of installed code.

  • On Linux and UNIX systems, you must run the profile file mqsiprofile to set up the correct environment before you run other WebSphere Message Broker commands, such as mqsicreatebroker. The profile file is stored in install_dir/bin.

    If you add the profile file to your system logon profile, it is run automatically whenever you log on.

  • On Windows systems, a command console is available for each installation. So you must run commands in the correct window for a particular installation.

    If you prefer, you can run the mqsiprofile.cmd file, which is stored in install_dir\bin.

If you have installed an earlier version of this product on the same computer, check that the earlier profile is not set for the current user ID. The two profiles are incompatible and might cause unpredictable results. Consider using a different user ID for each version and associate the correct profile with each user ID to avoid potential problems.

This requirement is not applicable on z/OS systems.

For more details about mqsiprofile, see Setting up a command environment.

WebSphere Message Broker Explorer

Only one copy of WebSphere Message Broker Explorer can be installed at any time on a single system, so you must ensure the latest level of WebSphere Message Broker Explorer is installed. For example, if you have WebSphere Message Broker Version 8.0.0.0 and WebSphere Message Broker Version 8.0.0.2 installed on the same system, you must ensure that WebSphere Message Broker Explorer 8.0.0.6 is installed. This only applies to Windows, Linux on x86, and Linux on x86-64 systems. However, you can use the latest version of WebSphere Message Broker Explorer to connect to brokers from previous versions.

Migration

Because you can install WebSphere Message Broker Version 8.0 on the same computer as previous versions and other installations of Version 8.0, you are not required to complete any migration tasks before you install Version 8.0.

If WebSphere Message Broker Version 8.0 requires a later version of WebSphere MQ than you are currently using, you must update any existing installations to use a version of WebSphere MQ that is supported by Version 8.0 before installing WebSphere Message Broker Version 8.0.

For the latest details of all supported levels of hardware and software, visit the WebSphere Message Broker Requirements website.

For details about migrating to WebSphere Message Broker Version 8.0, see Migrating.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:09


Concept topicConcept topic | Version 8.0.0.7 | bh25905_