Red Hat Training

A Red Hat training course is available for Red Hat JBoss Enterprise Application Platform

3.3. Upgrading JBoss EAP 6

3.3.1. Prepare for the Upgrade

Before you upgrade JBoss EAP using the ZIP or RPM installation, you need to be aware of the following potential issues.
  • This update may remove temporary folders. Any standalone or domain managed deployments stored in the data/content/ directory must be backed up prior to the update and restored after it completes, otherwise the server will fail to start due to the missing content.
  • Prior to applying the update, handle any open transactions. Then delete the data/tx-object-store/ transaction directory.
  • If you backup and restore your configuration files when updating to newer point releases, you could overwrite new configurations and prevent new features from being enabled automatically. The suggested approach is to compare the old configuration to the new configuration and only reapply specific configurations you need to keep. This can be done manually or by creating a CLI script that can apply the changes consistently to multiple server configuration files.
  • You can copy an existing configuration for an update, but the server restart updates the file and it may no longer be compatible with the previous version of the server.
  • The persistent timer data/timer-service-data data must be checked to determine whether it is compatible. Before the update, review the deployment-BEAN_NAME files in that folder to determine which timers are still in use.

3.3.2. Upgrade the JBoss EAP 6 ZIP Installation

Prerequisites

Summary

This procedure covers upgrading a JBoss EAP 6 ZIP installation between minor versions (for example, from JBoss EAP 6.1 to 6.2). For installing patches for a specific minor version, refer to the Patch Installation section. Upgrading to the latest release of JBoss EAP 6 requires some initial work to back up the existing installation.

Warning

For managed domains, the master Host Controller (or Domain Controller) instance should be upgraded first, before each Host Controller is upgraded.

Procedure 3.7. Upgrade to the latest JBoss EAP 6 version

  1. Move the downloaded ZIP archive to the desired location. It is recommended that this is a different location to the existing JBoss EAP 6 installation.

    Important

    If you wish to install the latest version of JBoss EAP 6 to the same directory location as the existing installation, you will need to move the existing installation to a different location before proceeding. This is to prevent modified configuration files, deployments, and upgrades from being lost.
  2. Unzip the archive. This step installs a clean instance of the latest JBoss EAP 6 release.
  3. Copy the EAP_HOME/domain/ and EAP_HOME/standalone/ directories from the previous installation over the new installation directories.

    Note

    New features in the new release, such as new subsystems, may not be activated if configuration files are copied from an older JBoss EAP 6 installation. To use these new features, it is necessary to compare and update the old configuration files with the ones from the new version.
  4. Review the changes made to the bin directory of the previous installation, and make the equivalent modifications to the new directory.

    Warning

    Files in the bin directory should not be overwritten by the files from previous versions. Changes should be made manually.
  5. Review the remaining modified files from the previous installation, and move these changes into the new installation. These files may include:
    • The welcome-content directory.
    • Custom modules in the modules directory.
    • Custom bundles in the bundles directory.
  6. Optional: If JBoss EAP 6 was previously configured to run as a service, remove the existing service and configure a new service for the upgraded installation.
Result

The JBoss EAP 6 ZIP installation has been successfully upgraded to the latest release.

3.3.3. Upgrade the JBoss EAP 6 RPM Installation

Prerequisites

  • Ensure that the base operating system is up to date and that the system is subscribed and enabled to get updates for the Base OS channel.
  • Ensure that the correct JBoss EAP 6 RHN channel is enabled. For example, on a x86, 64 bit architecture, this will be the JBoss Application Platform (v 6) for 6Server x86_64 channel (jbappplatform-6-x86_64-server-6-rpm).
  • Back up any modified configuration files, deployments, and all user data.
Summary

Upgrading to the latest release of JBoss EAP 6 requires some initial work to back up the existing installation. This topic covers upgrading the RPM installation via the Red Hat Network (RHN).

Warning

For managed domains, the master Host Controller (or Domain Controller) instance should be upgraded first, before each Host Controller is upgraded.

Procedure 3.8. Upgrade to the latest JBoss EAP 6 release

  1. Run the following command in a terminal to upgrade the installation:
    yum update
  2. Manually merge each created *.rpmnew file that contains changes into the production configuration files.
Result

JBoss EAP 6 has been successfully upgraded.

3.3.4. Upgrade JBoss EAP Cluster

Prerequisites

  • None
Summary

JBoss EAP 6 does not support the creation of clusters where the different nodes are made up of different versions of JBoss EAP servers. Thus, a mixed cluster based on different versions is not supported and all nodes within a cluster must be the same version.

Warning

The upgrade process for migrating traffic from a 6.3 cluster to a 6.4 cluster is therefore based on transferring all traffic to the 6.4 cluster and then shutting down the servers or nodes in the 6.3 cluster.

Procedure 3.9. Setup a JBoss EAP Cluster

  1. Refer to the HTTP Clustering and Load Balancing chapter of the JBoss EAP 6.4 Administration and Configuration Guide for instructions on how to setup a JBoss EAP cluster in 6.4.
  2. Migrate all traffic to this new cluster using the steps outlined in the Migrate Traffic between Clusters chapter of the JBoss EAP 6.4 Administration and Configuration Guide
Result

Your JBoss EAP 6.3 cluster has been migrated to a cluster based on JBoss EAP 6.4.