Upgrade Websphere Application Server 5.0 to 5.1

 

Tips

 

Overview

These are instructions for upgrade WebSphere Application Server Version 5.0 to Version 5.1. The procedure outline below was performed on an Solaris 8.x operation system, but is generally applicable to other UNIX flavors.

  1. Run versionInfo.sh

  2. Run versionInfo.sh

  3. Run product history reports

  4. Document port usage

  5. If the current 5.0 environment that you'll be upgrading has already been configured with installed applications, you can save about 3-4 hours by making a backup copy of the current 5.0 configs:

    • Shut down the nodes in the cluster but leave DeploymentManager running.

    • cd /opt/WebSphere/DeploymentManager/bin

    • backupConfig.sh -user username -password password 

      hostname [8:52am] # backupConfig.sh -user username -password password
ADMU0116I: Tool information is being logged in file
           /opt/WebSphere/DeploymentManager/logs/backupConfig.log
ADMU5001I: Backing up config directory /opt/WebSphere/DeploymentManager/config
           to file
           /opt/WebSphere/DeploymentManager/bin/WebSphereConfig_2004-04-09.zip
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: dmgr
ADMU2010I: Stopping all server processes for node hostManager
ADMU0510I: Server dmgr is now STOPPED
ADMU5002I: 212 files successfully backed up
host [8:54am] #

    • A file called...

      WebSphereConfig_YYYY-MM-DD.zip

      ...will be created in...

      /opt/WebSphere/DeploymentManager/bin

      Important: This file should then be copied OUT of this directory and kept in a safe place, as the /opt/WebSphere directory and everything underneath it will eventually need to be deleted to perform the upgrade.

  6. Uninstall the WebSphere AppServer

    • cd /opt/WebSphere/AppServer/_uninst

    • Set the DISPLAY variable to export your X session back to your local machine (ie. set DISPLAY yourbox:0.0)

    • uninstall

    • Follow the prompts to remove the product

  7. Uninstall the WebSphere Deployment Manager

    • cd /opt/WebSphere/DeploymentManager/_uninst

    • uninstall

    • Follow the prompts to remove the product

  8. Verify whether or not MQ is installed on the machine and if so, remove it:

    • pkginfo | grep -i mqm

      If it's installed, the output will look something like this: 

      host [9:06am] # pkginfo | grep -i mqm
application mqm   WebSphere MQ for Sun Solaris
host [9:06am] #

    • Since uninstalling the AppServer and DeploymentManager doesn't fully remove the /opt/WebSphere/AppServer and /opt/WebSphere/DeploymentManager directories, these directories should either be moved out of the way or removed altogether to make way for the new installation. If the directories are still there when you go to perform the 5.1 install, the installation will fail.

      • Either:

        mv /opt/WebSphere /opt/WebSphere.old

        or:

        rm -rf /opt/Websphere

    • Install WebSphere Deployment Manager 5.1, AppServer 5.1 and Cumulative Fixpack 3:

    • Install WAS51 BASE first:

      cd WAS_51_BASE_SOLARIS/sun
      launchpad.sh

      Follow the prompts to complete the install (note: make sure to select .Embedded Messaging Client. only, not the Embedded Messaging Server in it's entirety!)

    • Install WAS51 ND second:

      cd ../../WAS_51_ND_SOLARIS/sun
      launchpad.sh

      Follow the prompts to complete the install

    • Install the Cumulative Fixpack 3 for both BASE and ND (this needs to be run twice, once for each of the products)

      cd ../../WAS_51_CF3_BASE_AND_ND_SOLARIS
      updateWizard.sh

  9. Federate the nodes into your cluster:

    • On *EACH* of the nodes (do not try to federate more than one node at a time, you'll get errors) you'll be adding to the cluster, perform the following:

      cd /opt/WebSphere/AppServer/bin
      addNode.sh dmgr_host

  10. Restoring the initial configuration: At this point, I'm unaware of a way to restore the initial backup image that we created back in step 1c due to the encrypted LTPA information contained within the initial security.xml file. The following steps (though not ideal, will get you around this):

    • Make a backup copy of the current security.xml file:

      cd /opt/WebSphere/DeploymentManager/config/cells/hostNetwork
      cp security.xml security.xml.backup

    • Restore the original backup file:

      cd /opt/WebSphere/DeploymentManager/bin
      restoreConfig /path/to/your/backup_file.zip

    • Copy the security.xml.backup file you created in step 8a above over the top of the one that's now in:

      /opt/WebSphere/DeploymentManager/config/cells/hostNetwork

    • Start the DeploymentManager process:

      /opt/WebSphere/DeploymentManager/bin/startManager.sh

    • Security will need to be reconfigured via the console (during which point the new LTPA encryption information will be created for the new environment/server). Also, all of the aliases will all need to be re-created).

  11. Once security has been configured, shut down the DeploymentManager and re-sync the nodes to that they all contain the proper configurations:

    • /opt/WebSphere/DeploymentManager/bin/stopManager.sh -username username -password password

    • On *ALL* of the app servers in the cluster, perform the following:

      cd /opt/WebSphere/AppServer/bin
      syncNode.sh dmgr_name

  12. Start the DeploymentManager:

    cd /opt/WebSphere/DeploymentManager/bin
    startManager.sh

  13. Start the AppServer on each of the nodes in the cluster:

    cd /opt/WebSphere/AppServer/bin
    startNode.sh

  14. Run Install Verification Test (IVT)

  15. If necessary, run WASPostUpgrade.sh. This is only necessary if above procedure generated errors.

  16. Log into the console and perform a final check on your configuration (test DB connections, verify security is configured for use and working with LDAP, etc).

  17. Run versionInfo.sh

  18. Run versionInfo.sh

  19. Run product history reports