Chapter 12. JBoss Enterprise Application Platform Pre-upgrade Test Guidelines

JBoss Enterprise Application 5.2.0 is a minor release of JBoss Enterprise Application Platform 5.1.
An in-place upgrade from version 5.1.x to the latest version is available for customers who have installed the platform using RPM.

Important

This is a platform upgrade, not an assisted migration. The platform software will be updated to the latest version, however, you will have to update configuration files and verify the compatibility of your applications.
Follow Upgrade JBoss Enterprise Application Platform 5.1.x to the latest 5.1.x version using RPM to test and verify the entire process before applying it to a production system.

Upgrade JBoss Enterprise Application Platform 5.1.x to the latest 5.1.x version using RPM

Follow the overarching guidelines in this task to perform a non-production system pre-upgrade test. Complete this task before upgrading your production systems as a best practice platform upgrade task.
Once you are satisfied with the results collected as a result of the task guidelines, refer to Chapter 5, RPM Installation via Red Hat Network for upgrade commands and prerequisites for different operating systems.

Prerequisites

  • You have backed-up your JBoss Enterprise Application Platform data and configuration, and have verified you can restore the system to a known state.
  1. Stop all JBoss instances.
  2. Upgrade the 5.1 install to the latest update level.
  3. Locate and examine all .rpmnew files installed on your system by the upgrade process. 
    find $JBOSS_HOME -name *.rpmnew -ls
    Identify the impact of these changes on your infrastructure and your applications.
    Compare the old versions of the new files, and make any necessary changes to the files before performing this upgrade on your production systems.
    During an RPM upgrade, RPM will install new versions of configuration files. These new versions will be saved with the extension .rpmnew, in order to preserve your existing configuration data. After the upgrade look for these files and compare them with your existing configuration files, making any necessary changes.
  4. Start all JBoss instances.
  5. Systematically test all applications and verify all applications work according to original specifications.
  6. Once satisfied with the results of your testing, roll the upgrade out to your production systems.