|
Problem(Abstract) |
The following information describes how to add the
embedded messaging feature to an existing federated installation of IBM®
WebSphere® Application Server V5. This procedure requires the node to be
rebuilt. |
|
|
|
Cause |
The process outlined in the Solution section sets the
requirements for how to add the embedded messaging feature to a node
within the cell. This document does not pertain to situations where
WebSphere Application Server has not yet been installed or federated. If
WebSphere Application Server has not yet been installed, refer to the
Information Center article titled "Installing WebSphere embedded messaging
as the JMS provider."
Utilizing embedded messaging is a major architectural decision concerning
WebSphere Application Server. Under optimal circumstances, the embedded
messaging feature is installed with WebSphere Application Server during
the initial installation process. As discussed in the Solution section, adding the
embedded messaging feature to a cell containing federated nodes is an
extremely disruptive operation. It is strongly encouraged that this
solution be thoroughly tested before making any attempt to apply it to a
production environment.
When attempting to add the embedded messaging feature to a federated
node, the installer does not allow the installation to take place and
results in the following error message:
INST0055E: You may not add components
to a node that has already been federated into a cell. Unfederate the node
and try again or choose a different location. |
Special note concerning the full, stand-alone WebSphere MQ (formerly
MQSeries®) product:
If a full, stand-alone WebSphere MQ (formerly MQSeries) product is already
installed on the same physical system, proceed with care.
Consider the following points if WebSphere MQ is installed on the same
physical system:
- If you intend to install the WebSphere Application Server embedded
messaging client for use with the full WebSphere MQ server
product, stop now. Using the embedded messaging client in
this way is in violation of the WebSphere Application Server product
license. Instead, use the WebSphere MQ client, which is available free on
the WebSphere MQ support site.
- If you intend to use the WebSphere embedded messaging publish and
subscribe service or the embedded messaging broker, then
proceed. Note that installing the embedded messaging
feature to take advantage of WebSphere embedded messaging publish and
subscribe or the embedded messaging broker adds those features to the
existing full WebSphere MQ installation.
- If you intend to use the WebSphere embedded messaging server and do
not need WebSphere embedded messaging publish and subscribe or embedded
messaging broker, then stop now. If the full
WebSphere MQ server product is already is installed on the same physical
system, in this case it is not necessary to install the WebSphere
Application Server embedded messaging feature.
- Fix Packs, CSD, and maintenance: WebSphere Application Server
Fix Packs provide updates to the WebSphere embedded messaging component.
If the full WebSphere MQ product (server or client) is not installed on
the same physical system as WebSphere Application Server, it is
appropriate to have the Fix Pack update the embedded messaging (MQ).
For further details, see the technote titled "Applying maintenance to WebSphere Application Server V5
embedded messaging."
|
|
|
Resolving the
problem |
Important: Adding the embedded messaging feature to
a cell containing federated nodes requires a significant rebuild of the
existing configuration. In fact, the amount of work required to complete
this process is equivalent to the amount of work involved in installing
the entire cell. It might turn out to require even more effort than
reinstalling the entire cell. In an especially complex cell environment,
it is advisable to completely reinstall and reconfigure the cell.
There is no way to add the embedded messaging feature on top of an
existing federated node. Each node that requires use of the embedded
messaging feature must be removed from the cell before adding the feature.
The act of removing the node from the cell causes the node to lose its
configuration information. When the node is re-federated into the cell, it
must be manually reconfigured. For example, all servers created on that
node must be reconfigured. Applications previously deployed on that node
must be reinstalled. Also, other configuration information such as data
source definitions or security settings must be reconfigured.
After the embedded messaging feature is installed onto a node, do
not use the restoreConfig command to restore from a
backupConfig made before the embedded messaging feature is installed. This
is not an acceptable way to restore the previous configuration, and it
will corrupt the cell configuration. The act of installing the Embedded
Message feature into an existing node alters the configuration for that
node. Restoring previous configuration data erases the configuration
information pertinent to the embedded messaging feature. The embedded
messaging feature for that node ceases to function, and the feature cannot
be reinstalled to repair the configuration.
Adding the embedded messaging feature to a cell
This procedure outlines the process of adding the embedded messaging
feature to a cell that contains nodes that have been federated. These
instructions assume that you are using the installation wizard instead of
a silent installation.
- Make sure that you have over 200 megabytes free in both your
Application Server file system and temporary file system to install the
embedded messaging feature.
- Use the Deployment Manager to shut down all the base nodes in the
environment. Then stop the node agent processes on the individual nodes.
Make sure to leave the Deployment Manager running.
- Remove each node that is targeted for using embedded messaging from
the cell. If every node in the cell will use embedded messaging, every
node must be removed.
Refer to the V5.0 Information Center section regarding the removeNode
command for more details.
- Remove Interim Fixes, Cumulative Fixes, and Fix Packs. This is
necessary to prepare the environment for installing additional features.
It also makes it possible to update the newly-installed features with
fixes.
- As with any update, it is important to download and use the latest
version of the update installer software for V5.0.
- Uninstall the Cumulative Fix applied to your WebSphere
Application Server product. For example, if the product is at version
5.0.2.1 (Fix Pack 2 plus Cumulative 1), uninstall Cumulative Fix 1.
Note: The update installer also uninstalls any Interim Fixes
applied to WebSphere Application Server. Make a note of these fixes so you
can reapply them later.
- Uninstall the Fix Pack applied to your WebSphere Application
Server product.
As with any update, it is important to download and use the latest
version of the update installer software for V5.0.
- Install the embedded messaging feature to the base node:
- Run the WebSphere Application Server Base edition installation
program. Accept the license agreement if you agree to the terms specified.
- When prompted, choose Add features to an existing installation,
and specify the installation directory of the WebSphere Application Server
base node.
- Specify a custom installation, and select the appropriate
embedded messaging installation options. For example, choose the
embedded messaging option and Server and Client sub-option.
Note: By default, the installer selects all available
features to install. Clear any undesired installation options that are
selected on this panel. (You cannot clear options that are already
installed).
- Proceed to the next installation panel. The Installation Wizard
prompts for the product installation directories. Be sure to specify the
desired installation location for the embedded messaging (WebSphere MQ)
feature.
Note: If the full, stand-alone product is already installed on the
same physical system, the installer does not prompt for the WebSphere MQ
installation directory. Instead, it installs additional features to the
existing WebSphere MQ installation (make sure to read the special notes
concerning the full, stand-alone WebSphere MQ product in the Cause
section of this document).
- The Space Required for Installation metric will be listed
incorrectly. It might list a negative number. This is a known behavior.
- If the installer asks to register WebSphere Application Server as a
service, clear that option.
Note: If this option is selected during the initial installation,
WebSphere Application Server has already been installed as a service, and
allowing this installation session to register the service again is
redundant.
If WebSphere Application Server has not been installed as a service, and
this option is desired, do not select this option in the installer.
Instead, use the WASService utility to add the WebSphere
Application Server service.
Refer to the V5.0 Information Center section for the WASService command
for more details.
- Allow the installation to complete. The embedded messaging feature is
now installed on this base node.
- Repeat the previous step, but run the Deployment Manager installer and
add the embedded messaging feature to the existing Deployment Manager. The
process for doing this is very similar to the process described in the
previous step.
Note: The embedded messaging feature for the Deployment Manager
offers the client option only, not the server or server
and client. The client-only option must be installed
after any base node on the same physical system is updated with the
embedded messaging server.
- Update the product with Fix Packs and Cumulative Fixes:
- As with any update, it is important to download and use the latest
version of the update installer software for V5.0.
- Install the desired Fix Pack, which is most likely the same Fix Pack
that was uninstalled previously.
Note: If the full WebSphere MQ product is NOT installed on the
same system, be sure to specify that the embedded messaging should be
updated by the Fix Pack installer. If the full WebSphere MQ product IS
installed on the same system, refer to Applying maintenance to WebSphere Application Server V5
embedded messaging. In that case, do not allow the Fix Pack to update
embedded messaging.
- Install the desired Cumulative Fix, which is most likely the same
Cumulative Fix that was uninstalled previously.
- Install the Interim Fixes that were removed as part of the uninstall
process, if any.
- Add the node to the cell. To do this, use the addNode command
on the node while Deployment Manager is running.
Refer to the V5.0 Information Center section for the addNode command for
more details.
- Reconfigure all of the settings that were once associated with this
node, and also redeploy all the applications that were once associated
with the servers on the node.
Note: As per the warning preceding these instructions, it is not
possible to restore the old configuration from an old backup. The addition
of the embedded messaging feature has altered the configuration and those
alterations are erased if an old configuration is restored from backup.
- The process is complete. The cell is now enabled for embedded
messaging.
|
|
|
|