There have been a number of discussions on whether it is
possible to have WebSphere MQ (WMQ) and WebSphere Application Server (WAS)
v5.x with Embedded Messaging on the same machine. There have also been
requests for customers to have the ability to upgrade their Embedded
Messaging Server to either the full version of WMQ v5.3 or v6.0. This
document provides the supported steps for either installing both Embedded
Messaging and WMQ on the same machine, as well as the official migration
path.
WAS v5.x Embedded Messaging and WMQ v5.3
- There can only be a single physical installation of WebSphere MQ v5.3
on any given machine
- There can be two logical installations - a standalone WMQ and the
WebSphere JMS Provider:
- If the standalone WebSphere MQ v5.3 has been installed first, and you
wish to install WAS v5.x with the Embedded JMS Provider, the recommended
approach is as follows:
- Uninstall WMQ, selecting the option to leave the existing queue
manager data on the system.
- Install either WAS v5.0 or WAS v5.1, ensuring the option to install
the WebSphere Embedded Messaging Server and Client has been selected.
- Install either Fix Pack 2 for WAS v5.0 (to bring the application
server up to the v5.0.2 level) or Fix Pack 1 for WAS 5.1.0 (which will
bring WAS up to the v5.1.1 level).
- Uninstall WMQ (the embedded WebSphere JMS Provider), selecting the
option to leave the existing queue manager data on the system. Do not
uninstall the WEMPS component.
- Reinstall standalone WMQ.
When you choose to install the Embedded Messaging Server and Client in
WAS, the application server's installation process will check to see if
WMQ is currently installed, and that it is at the correct level for the
version of WAS that is being installed (e.g. if you are installing WAS
5.0, WMQ 5.3 must be at the CSD01 level - if you are installing WAS 5.1,
WMQ must be at the CSD04 level). If WMQ is not at the right CSD level for
the version of WAS being installed, the WAS installation will fail, and in
some cases, damage the existing WMQ installation.
It is also important that WAS Fix Packs are installed prior to the
WebSphere JMS Provider being removed and replaced with standalone WMQ. The
WAS Fix Pack process will check to see if the WebSphere JMS Provider has
been installed, and if it has, the Fix Pack will attempt to apply WMQ
maintenance. If you have already upgraded the WebSphere JMS Provider to
standalone WMQ, and then apply a WAS Fix Pack, you could potentially
damage your WMQ installation as the Fix Pack could be applying a back
level CSD to WMQ.
- If WAS with the embedded JMS Provider has been installed first, and
you wish to install standalone WMQ onto the same machine, the recommended
approach is shown below:
- Install either Fix Pack 2 for WAS v5.0 (to bring the application
server up to the v5.0.2 level) or Fix Pack 1 for WAS 5.1.0 (which will
bring WAS up to the v5.1.1 level).
- Uninstall WMQ (the Embedded JMS Provider), selecting the option to
leave the existing queue manager data on the system.
- Install standalone WMQ.
It is important that WAS Fix Packs are installed prior to the WebSphere
JMS Provider being removed and replaced with standalone WMQ. The WAS Fix
Pack process will check to see if the WebSphere JMS Provider has been
installed, and if it has, the Fix Pack will attempt to apply WMQ
maintenance. If you have already upgraded the WebSphere JMS Provider to
standalone WMQ, and then apply a WAS Fix Pack, you could potentially
damage your WMQ installation as the Fix Pack could be applying a back
level CSD to WMQ.
On all platforms apart from AIX®, uninstalling the embedded JMS
provider will only uninstall WMQ. The WebSphere Embedded Messaging Publish
Subscribe (WEMPS) Broker will be left on the system.
On AIX, uninstalling the embedded JMS provider will remove both WMQ and
the WEMPS broker. To continue to use publish/subscribe functionality, a
message broker (such as the WMQ broker provided with WMQ v5.3 Fix Pack 8
and v6.0) will need to be installed, and any Topic Connection Factories
and Topic Destinations that have been defined under the WebSphere JMS
Provider will need to be recreated under the WebSphere MQ JMS
Provider.
- With two logical installations, WMQ maintenance should be applied to
upgrade both standalone WMQ and the WebSphere JMS Provider. You should not
apply any WAS Fix Packs onto your system after you have migrated your
system to contain two logical installations.
- If there is only a single physical/logical install then:
- If it is a standalone WMQ, it is serviced via the WMQ service
site
- If it is the WebSphere JMS Provider, it is serviced via WAS v5.x Fix
Packs with only Interim Fixes being made available via the WMQ service
site
WAS v5 Embedded Messaging and WMQ v6
- There can only be a single WMQ installation on a machine. It is not
possible to have WMQ v5.3 and v6.0 installed on the same system.
- There can be two logical installations - a standalone WMQ and the
WebSphere JMS Provider:
- If the standalone WebSphere MQ v6.0 has been installed first, and you
wish to install WAS v5.x with the Embedded JMS Provider, the recommended
approach is as follows:
- Uninstall WMQ, selecting the option to leave the existing queue
manager data on the system.
- Install either WAS v5.0 or WAS v5.1, ensuring the option to install
the WebSphere Embedded Messaging Server and Client has been selected.
- Install either Fix Pack 2 for WAS v5.0 (to bring the application
server up to the v5.0.2 level) or Fix Pack 1 for WAS 5.1.0 (which will
bring WAS up to the v5.1.1 level).
- Uninstall WMQ (the embedded WebSphere JMS Provider), selecting the
option to leave the existing queue manager data on the system. Do not
uninstall the WEMPS component.
- Reinstall standalone WMQ.
When you choose to install the Embedded Messaging Server and Client in
WAS, the application server's installation process will check to see if
WMQ is currently installed, and that it is at the correct level for the
version of WAS that is being installed (e.g. if you are installing WAS
5.0, WMQ 5.3 must be at the CSD01 level - if you are installing WAS 5.1,
WMQ must be at the CSD04 level). If WMQ is not uninstalled first, the WAS
installation will fail as WMQ is not at the correct level, and in some
cases, the WAS install may damage the existing WMQ installation.
It is also important that WAS Fix Packs are installed prior to the
WebSphere JMS Provider being removed and replaced with standalone WMQ. The
WAS Fix Pack process will check to see if the WebSphere JMS Provider has
been installed, and if it has, the Fix Pack will attempt to apply WMQ
maintenance. If you have already upgraded the WebSphere JMS Provider to
standalone WMQ v6.0, and then apply a WAS Fix Pack, the Fix Pack
installation will fail.
- The WebSphere Embedded Messaging Component that is shipped with WAS
v5.x is equivalent to WMQ v5.3. If you have installed WAS v5.x with the
Embedded JMS Provider and wish to upgrade it to the full version of WMQ
v6, the guidelines below must be followed precisely, or problems may
result. The only supported migration path is as follows:
- Install either Fix Pack 2 for WAS v5.0 (to bring the application
server up to the v5.0.2 level) or Fix Pack 1 for WAS 5.1.0 (which will
bring WAS up to the v5.1.1 level).
- Uninstall WMQ v5.3 (the Embedded JMS Provider), selecting the option
to leave the existing queue manager data on the system.
- Install WMQ v6.0
It is important that WAS Fix Packs are installed prior to the WebSphere
JMS Provider being removed and replaced with WMQ v6.0. The WAS Fix Pack
process will check to see if the WebSphere JMS Provider (WMQ v5.3) has
been installed. If you have already upgraded the WebSphere JMS Provider to
WMQ v6.0, and then try to apply a WAS Fix Pack, the Fix Pack installation
will fail.
When upgrading the WebSphere JMS Provider on AIX systems, you will no
longer be able to use the Embedded Broker. Any Topic Connection Factories
and Topic Destinations that have been defined under the WebSphere JMS
Provider will need to be recreated under the WebSphere MQ JMS
Provider.
|