Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 3. Upgrading from JBoss Enterprise Application Platform 4.3 to version 5.1 via RPM

JBoss Enterprise Application 5 was a major release and includes major changes from JBoss Enterprise Application Platform 4.x, including a completely new Microcontainer and full compliance with the Java EE 5 standard. While Red Hat tries to maintain compatibility across releases, major releases provide us with the opportunity to advance our products in significant ways. Be aware that upgrading to a new version family (ie. 4.x to 5.x) will likely require changes to application configuration and application code.
An in-place upgrade from version 4.3 to 5.1 is available for customers who have installed the platform using RPM. This is a platform upgrade, not an assisted migration. The platform software will be updated to version 5.1, however, you will have to update configuration files and verify the compatibility of your applications. You should test and verify the entire process before applying it to a production system.

Warning

Users on any release of JBoss Enterprise Application Platform 4.2, and users on any JBoss Enterprise Application Platform Feature Pack or Technology Preview, should not attempt to upgrade with this procedure.
The procedure for performing an RPM upgrade is as follows:

Procedure 3.1. Upgrading JBoss Enterprise Application Platform 4.3 to version 5.1 using RPM

  1. Back up your environment
  2. Upgrade the 4.3 install to the latest update level

    Note

    Upgrading from a 4.2 or 4.3 Tech Preview (TP) or Feature Pack (FP) is not supported.
  3. Unsubscribe the system from the JBoss Enterprise Application Platform 4.3 channel in Red Hat Network
  4. Subscribe the system to the JBoss Enterprise Application Platform 5.1 channel in Red Hat Network
  5. Decide which of the optional components to install
  6. Issue the upgrade command
  7. Remove remaining 4.3 packages
  8. Select Java 6 via alternatives
  9. Update configuration files

Note

The final step, updating configuration files, is out of scope for this guide. Some guidance is given in Procedure 3.10, “Identify changed configuration files after the RPM upgrade”.

Procedure 3.2. Back up your environment

  • Regular backups and the ability to restore a system to a state of known configuration are best practice at all times. You should back up your data and configuration and ensure that you are able to restore the system to a known state, before performing this procedure.

Procedure 3.3. Unsubscribe the system from the JBoss Enterprise Application Platform 4.3 channel in RHN

Procedure 3.4. Subscribe the system to the JBoss Enterprise Application Platform 5.1 channel in Red Hat Network (RHN)

  • Refer to the following Red Hat Knowledgebase article for instructions to subscribe a system to a channel: "How do I subscribe a system to a sub-channel or a child channel using Red Hat Network (RHN)?".
    The channel names are as follows:

    Red Hat Network channel names for JBoss Enterprise Application Platform 5

    Red Hat Enterprise Linux 5 32-bit
    jbappplatform-5-i386-server-5-rpm
    Red Hat Enterprise Linux 5 64-bit
    jbappplatform-5-x86_64-server-5-rpm
    Red Hat Enterprise Linux 4 32-bit ES
    jbappplatform-5-i386-es-4-rpm
    Red Hat Enterprise Linux 4 32-bit AS
    jbappplatform-5-i386-as-4-rpm
    Red Hat Enterprise Linux 4 64-bit ES
    jbappplatform-5-x86_64-es-4-rpm
    Red Hat Enterprise Linux 4 64-bit AS
    jbappplatform-5-x86_64-as-4-rpm
Choose which optional components to install

JBoss Enterprise Application Platform 4.3 included JBoss WS Native as a web services provider. JBoss Enterprise Application Platform 5.1 includes both JBoss WS Native and JBoss WS CXF as web services providers. When installing or upgrading to JBoss Enterprise Application Platform 5.1, you must select one of the two web services stacks provided. To switch web services stacks, you must reinstall the product.

In the following procedures WS_CHOICE denotes the web services provider you wish to install. Replace WS_CHOICE with either jbossas-ws-native for JBoss Native web services, or jbossas-ws-cxf for JBoss CXF web services.

Procedure 3.5. Issue the upgrade command on Red Hat Enterprise Linux 4

  • Issue the following commands as root, substituting your choice for the optional WS_CHOICE: 
    up2date WS_CHOICE jbossas-messaging resteasy jboss-eap5-native jboss-seam2
up2date -u
    Copy to Clipboard Toggle word wrap

Procedure 3.6. Issue the upgrade command on Red Hat Enterprise Linux 5

  • Issue the following commands as root, substituting your choice for the optional WS_CHOICE: 
    yum remove classpathx-jaf
yum install WS_CHOICE jbossas-messaging resteasy jboss-eap5-native jboss-seam2
yum upgrade --disablerepo=rhel-i386-server-5
    Copy to Clipboard Toggle word wrap

Warning

It is important that you now perform the following procedure to remove remaining 4.3 packages. Since the system is no longer subscribed to the JBoss Enterprise Application Platform 4.3 channel, these packages will not receive security updates if they are left on the system.

Procedure 3.7. Remove remaining 4.3 packages on Red Hat Enterprise Linux 4

  • Issue the following command as root:
    (Note that the command is split across two lines in this document for presentation purposes, but should be entered on a single line) 
    rpm -e berkeleydb jboss-profiler servletapi6 tomcat5-servlet-2.4-api asm odmg jboss-seam-docs geronimo-j2ee-1.4-apis qdox jacorb ws-commons-policy tanukiwrapper jboss-seam xml-commons-resolver
    Copy to Clipboard Toggle word wrap

Procedure 3.8. Remove remaining 4.3 packages on Red Hat Enterprise Linux 5

  • Issue the following command as root:
    (Note that the command is split across two lines in this document for presentation purposes, but should be entered on a single line) 
    yum remove bea-stax-api berkeleydb jboss-seam-docs tanukiwrapper asm odmg jacorb bea-stax servletapi6 ws-commons-policy qdox jboss-profiler jboss-seam geronimo-j2ee-1.4-apis
    Copy to Clipboard Toggle word wrap

Procedure 3.9. Select Java 6 via alternatives

JBoss Enterprise Application Platform 5 requires a Java 6 run-time environment. Install and correctly configure a 1.6 JDK (Java Development Kit) or JRE (Java Runtime Environment) to use the Platform.

Procedure 3.10. Identify changed configuration files after the RPM upgrade

During an RPM upgrade from version 4.3, 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.
Between versions 4.3 and 5.1 of the Enterprise Application Platform a significant number of changes have taken place. Identify the impact of these changes on your infrastructure and your applications before performing this upgrade on your production systems.
  • Locate and examine all .rpmnew files installed on your system by the upgrade process. 
    find $JBOSS_HOME -name *.rpmnew -ls
    Copy to Clipboard Toggle word wrap
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat