+

Search Tips   |   Advanced Search


Manage WAS in the cluster

In some situations you might need to install additional WAS features on the nodes in the cluster.

For example, this could be necessary if a portlet requires a WAS feature not currently installed on the nodes. When installing additional features in a clustered environment, install the features on every node in the cluster. Also, the WAS Network Deployment node cannot have fewer features than the nodes that it manages. Consequently, if install a new feature on the managed nodes, review the features on the WAS Network Deployment node to determine whether also install the feature on the WAS Network Deployment node.

For example, if you select the full installation option for WebSphere Portal, the WAS will not have the extended messaging feature installed by default. If any of your portlets use the extended messaging feature, you will have to install this new feature on all nodes before you are able to deploy these portlets.

To install additional WAS features:

  1. Run...

      following

    to verify whether the feature is installed:

    Option Description
    Windows versionInfo -components task from the AppServer_root\bin directory and the nd_root\bin directory

    For information about the versionInfo command, refer to the WAS documentation.

    UNIX ./versionInfo.sh -components task from the AppServer_root/bin directory and the nd_root/bin directory

    For information about the versionInfo command, refer to the WAS documentation.

    i5/OS versionInfo.sh -profileName profile_root -components task from the AppServer_root/bin directory and the nd_root/bin directory profile_root is the name of the WAS profile where WebSphere Portal is installed; for example, wp_profile.

    For information about the versionInfo command, refer to the WAS documentation.

  2. Perform the following steps on each node to install the extended messaging component:

    1. Run the WebSphere Process Server installation program, located on the WebSphere Process Server disc for your platform. During installation, select to add to the existing copy of WAS and follow the Custom install path.

    2. On the features list panel, ensure that only Extended Messaging is selected, and complete the installation.

    3. Before updating the extended messaging feature to the required level, make a list of any interim fixes that are currently installed on the node.

    4. Install the required fix packs and cumulative fixes for WebSphere Process Server to update the extended messaging feature. The fix pack files are located on the WPS - WAS Fix Pack disc for your platform.

    5. Reapply any required interim fixes.


Parent topic:

Manage the cluster


Related information


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp