Introduction
Embedded messaging is a component of WebSphere® Application Server
(WAS) v5, where it provides WebSphere MQ (WMQ) messaging functionality for
the application server. It is optionally installed as part of the WAS
installation, and if selected installs a modified WebSphere MQ
installation. As embedded messaging is a component of WAS, then
maintenance to this component has been applied through the WAS fix packs
previously as follows:
WAS level in 5.0 product |
WMQ level of embedded messaging |
5.0.0 |
WMQ v5.3 fix pack 1 (CSD01) |
5.0.1 (fix pack) |
WMQ v5.3 fix pack 3 (CSD03) |
5.0.2 (fix pack) |
WMQ v5.3 fix pack 4 (CSD04) |
|
WAS level in 5.1 product |
WMQ level of embedded messaging |
5.1.0 |
WMQ v5.3 fix pack 4 (CSD04) |
5.1.1 (fix pack) |
WMQ v5.3 fix pack 7 (CSD07) |
|
There will be no new WAS v5 fix packs beyond 5.0.2 or 5.1.1, although
service packs will continue to be released (see here
for the latest). In order to allow continued maintenance of the embedded
messaging component, for WAS levels of 5.0.2 or later for the 5.0 product,
or 5.1.1 or later for the 5.1 product, the regular WMQ fix packs for the
full stand-alone WebSphere MQ v5.3 product can now be installed on top of
embedded messaging.
Applying WebSphere MQ 5.3 fix packs
The rules and instructions below must be followed exactly, in order
to remain supported. Please also read the whole page before
proceeding, as there is additional information on more complicated set ups
towards the bottom of the page.
Rules
These rules must be followed to remain supported. If you are in any doubt,
or have further questions, contact IBM® Support first.
- WMQ 5.3 fix packs can ONLY be installed on top of embedded messaging
at the WAS v5.0.2 or v5.1.1. level, or later. WMQ fix packs cannot be
installed on top of embedded messaging in 5.0.0, 5.0.1 or 5.1.0.
- For co-existence, the order of install is crucial. Once WMQ fix packs
have been applied, no older WAS levels can be installed on the same
machine afterwards. For example it would not be permitted to install WAS
v5.0.2 + embedded messaging (CSD01), a WMQ fix pack (eg, CSD12), then WAS
v5.1.0 + embedded messaging (CSD04); even if the intended target is
v5.1.1. It would be permitted to install WAS v5.0.2, v5.1.0 upgrading to
v5.1.1, then a WMQ fix pack; unless the 5.1.0 installation is without
embedded messaging.
- WMQ fix packs must be backed off before WAS fix packs are backed off,
or WAS is uninstalled. This will ensure WAS is in an 'original' state
before invoking its uninstallers.
- WMQ 5.3 fix pack 12 (CSD12) is the minimum supported level for this
process. Do not apply earlier WMQ 5.3 fix packs to Embedded
Messaging.
- WMQ 6.0 refresh or fix packs cannot be applied to Embedded
Messaging.
Installation Steps
- This procedure can only be followed, if you have a minimum level of
WAS of 5.0.2 or later, or 5.1.1 or later. This procedure cannot be
followed if 5.0.0, 5.0.1 or 5.1.0 are on the same system, as it could
otherwise lead to serious problems (see Example 2 below). Therefore
install WAS fix packs as necessary to bring WAS up to the pre-requisite
level before the next step. They can be downloaded from here.
- Back up your applications and configurations if you have not already
done so.
- Stop any running application servers (and JMS servers for Network
Deployment users). This will automatically stop the embedded queue
manager. There should be no MQ processes running.
- Download the latest WebSphere MQ v5.3 fix pack from the WebSphere MQ
support web
site (minimum of fix pack 12 (CSD12)). Do not use the WebSphere MQ v6
fix packs.
- Install the WebSphere MQ v5.3 fix pack you just downloaded,
remembering to save replaced files where appropriate. Note: for AIX®
users, do not commit the install straight away until the installation has
been thoroughly tested. Once a MQ fix pack has been committed it is not
possible to roll it back, so care needs to be taken.
- Remove any previous Embedded Messaging interim fixes from the
<WAS_HOME>\classes directory (including 'embedded messaging
cumulative JMS interim fixes' such as IC45152 and IC46552). This will
avoid potentially back-levelling parts of the WMQ v5.3 fix pack
installation.
(Note: IC47440 is unlike previous Embedded Messaging interim fixes, in
that it contains fixes for the Embedded Messaging broker (WEMPS) as well
as the usual MQ fixes. The MQ part of IC47440 should be backed-off (i.e.
com.ibm.mq.jar and com.ibm.mqjms.jar) before applying MQ fix pack 12. The
WEMPS bipbroker.jar from IC47440 is not updated in fix pack 12, so that
can be left in place as (a) it contains the latest WEMPS fixes at the
current time and (b) there is no risk of it being back-levelled by any MQ
fix packs.)
- Start your application servers (and JMS servers for Network Deployment
users).
- Test the new installation thoroughly, to ensure your applications
continue to function as expected. Always test in a separate test
environment first, before making changes to a production system.
Frequently Asked Questions
Q1: Is this maintenance procedure
relevant to me if I have upgrade embedded messaging to the full WebSphere
MQ product?
A1: Once you upgrade to the full WebSphere MQ
product, responsibility of the maintance is then owned by WebSphere MQ.
Therefore the WebSphere MQ fix packs can be used to apply maintenance.
Q2: What should I do to apply maintenance
to the embedded broker WebSphere Embedded Messaging Publish and Subscriber
(WEMPS)?
A2: Maintenace to this component will be
applied through the WAS service packs for 5.1 at a later stage, and is not
included in the WebSphere MQ fix packs.
Q3: What should I do if I have the
Network Deployment version?
A3: You should ensure both the base
installation(s) and network deployment installation(s) are upgrade to the
pre-requisite fix pack level (5.0.2 or 5.1.1) before following the
instructions above. The instructions can then be followed as documented
above.
Q4: Can I use the WebSphere MQ v6 fix
packs instead?
A4: No, they cannot be used because the
embedded messaging component is built on the WebSphere MQ v5.3 level, so
v6 fix packs should not be applied.
Q5: Once I have applied a WMQ v5.3 fix
pack, how do I apply further maintenance?
A5: WMQ v5.3 fix packs can be applied on top
of other fix packs, as long as the the installation is always on top of
older fix packs. For example it will be possible to apply WMQ v5.3 fix
pack 13 on top of fix pack 12.
Q6: Do I need to apply WMQ v5.3 fix packs
when I already have installed the latest embedded messaging cumulative JMS
interim fix?
A6: The embedded messaging cumulative JMS
interim fixes (for example, IC45152 or IC46552) are for the JMS client
only. The WMQ v5.3 fix pack also installs WMQ server fixes, and takes
precedence over all previous embedded messaging cumulative JMS interim
fixes, as long as fix pack being installed is at WMQ 5.3 fix pack 12 or
greater. In which case, all previous embedded messaging fixes that may be
in the <WAS_HOME>\classes directory should be removed to avoid
back-levelling parts of the new WMQ v5.3 fix pack installation.
Q7: How can I check what level of
WebSphere MQ is installed?
A7: The 'mqver' command will show the level
of WebSphere MQ installed on a system, although it should be noted that
this should only be used as an approximate guide. This command will not
necessarily display any code changes resulting from APARs or interim
fixes, or if other WebSphere MQ code is present (for example, older fixes
still accidentally being referenced in the classpath). As a result the
'mqver' command cannot be relied upon in place of good change management
practice.
Q8: How does applying WebSphere MQ 5.3
fix packs to WAS Embedded Messaging affect my licences?
A8: WAS Embedded Messaging is still a
WAS-component, even after WebSphere MQ 5.3 fix packs have been applied.
Therefore, customers are still covered by their WAS licence agreements.
This means for WMQ functionality not available in standard WAS Embedded
Messaging, such as 'runmqsc', it is still not permitted to take advantage
of this after applying WMQ fix packs (unless specifically directed by
Service for diagnostic purposes). Similarly, in WAS 5.0 the licence
agreement stipulates it is not possible to connect the embedded queue
manager created by WAS to other queue managers. The same applies after the
installation of WMQ fix packs.
Q9: What if a customer has already
applied a WMQ 5.3 fix pack to Embedded Messaging, without being directed
by L2/L3?
A9: If they have followed the same process as
documented here, and both the WAS and WMQ levels (eg, 5.1.1 and 5.3 fix
pack 12) are correct then the customer is supported. Otherwise, they are
not supported, so to get them to a supported state it may mean backing off
changes and trying again, but with the strict adherance to the guidelines.
Q10: What if I have applied multiple WMQ 5.3
fix packs to WAS Embedded Messaging (e.g. WAS 5.1.1 with Embedded
Messaging, then WMQ 5.3 fix pack 12 applied followed by then fix pack 13)
- can I back all WMQ fix packs off to get back to a standard WAS
state?
A10: Yes, it is possible to back off multiple WMQ
fix packs, but care needs to be taken on some platforms to ensure that the
files are backed up before applying WMQ fix packs, and that the levels are
not committed. For example on AIX, when applying the WMQ fix packs ensure
"COMMIT software updates = no" and "SAVE replaced files =
yes". If levels are committed then there is no way to back them off.
This is the same behaviour as with the full WeSphere MQ product.
Q11: What should I do if I encounter a
problem?
A11: Do not commit any fix pack installations, and
contact IBM support straight away.
Q12: How do I upgrade an embedded messaging
client-only install?
A12: The installation steps are the same as for a
server install, the FixPack will only update the client code.
Examples
Example 1: Applying embedded messaging
maintenance beyond 5.0.2 (although the same applies to the 5.1 product at
the 5.1.1 level).
- Install WAS v5.0.0 with embedded messaging (the embedded messaging
level is then WMQv5.3 fix pack 1).
- Apply the WAS 5.0.2 fix pack with embedded messaging (the embedded
messaging level is then WMQv5.3 fix pack 4).
- Apply WMQ v5.3 fix pack 12 as per the instruction above, taking the
embedded messaging level to WMQv5.3 fix pack 12. Please note, the user
then has the following further options at this point:
-
- If the user wants to uninstall WAS from the system, the WMQ v5.3 fix
pack must be uninstalled first before invoking the WAS uninstaller.
- If the user wants to migrate to a WAS v5.1 installation and continue
using the embedded messaging features (for example, the WebSphere JMS
provider Resource option or the WebSphere Embedded Messaging Publish
Subscribe broker), the WMQ v5.3 fix pack must be uninstalled first.
Otherwise the WAS v5.1 embedded messaging installation will fail.
- If the user wants to install a separate WAS v5.1 installation to
co-exist with the 5.0 installation, and continue using the embedded
messaging features (for example, the WebSphere JMS provider Resource
option or the WebSphere Embedded Messaging Publish Subscribe broker), the
WMQ v5.3 fix pack must be uninstalled first. Otherwise the WAS v5.1
embedded messaging installation will fail. See example 3 for more
information.
Example 2: Applying embedded messaging
maintenance to 5.0.1 (or 5.0.0 or 5.1.0) - DO NOT DO THIS
EXAMPLE. It is to help your understanding of potential issues only.
- Install WAS v5.0.0 with embedded messaging (the embedded messaging
level is then WMQv5.3 fix pack 1).
- Apply WMQ v5.3 fix pack 12, taking the embedded messaging level to
WMQv5.3 fix pack 12.
- Apply the WAS 5.0.2 fix pack with embedded messaging (which is at the
WMQv5.3 fix pack 4 level in this fix pack), which may result in a system
of mixed WMQ v5.3 fix pack 4 and 12 leading to problems. Therefore WMQ
v5.3 fix packs should not be installed on top of WAS v5.0.0, 5.0.1 or
5.1.0 installations.
Example 3: How to install a co-existing WAS v5.0
and v5.1 installations, and applying embedded messaging maintenance beyond
5.0.2 and 5.1.1.
- Install WAS v5.0.0 with embedded messaging (the embedded messaging
level is then WMQv5.3 fix pack 1).
- Apply the WAS 5.0.2 fix pack with embedded messaging (the embedded
messaging level is then WMQv5.3 fix pack 4).
- Install WAS v5.1.0 with embedded messaging (the embedded messaging
level remains at WMQv5.3 fix pack 4 - see the table above for more
information).
- Apply the WAS 5.1.1 fix pack with embedded messaging (the embedded
messaging level is then WMQv5.3 fix pack 7).
- Apply WMQ v5.3 fix pack 12 as per the instruction above, taking the
embedded messaging level to WMQv5.3 fix pack 12. Please note, the user
then has the following further option at this point:
-
- If the user wants to uninstall either of the WAS installations from
the system (5.0 or 5.1), the WMQ v5.3 fix pack must be uninstalled first
before invoking the WAS uninstaller. Once the uninstall is complete the
WMQ v5.3 fix pack can be reapplied.
|