QE (N)ACK - EAP 4.3 to 5.1 upgrade instructions

Rajesh, below is the upgrade procedure for EAP 4.3 to EAP 5.1.

Please give this procedure an ACK or NACK from QE for inclusion in the EAP 5.1 Installation Guide.

5. Upgrading from 4.3 via RPM

An in-place upgrade from version 4.3 to 5.1 is available for customers who have installed the platform using RPM. Please note that using this is a platform upgrade and is 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.

The procedure for performing an RPM upgrade is as follows:

Procedure 5.1 Upgrading from EAP 4.3 to EAP 5.1 using RPM

1. Unsubscribe the system from the EAP 4.3 channel in RHN
2. Subscribe the system to the EAP 5.1 channel in RHN
3. Choose which optional components to install
4. Issue the upgrade command
5. Remove remaining 4.3 packages
6. Select Java 6 via alternatives
7. Update configuration files

The first three steps are described in further detail in the following procedures.

NOTE: The final step, updating configuration files, is out of scope for this guide. Some guidance is given in "5.1 Identifying changed configuration files after an RPM upgrade"

Procedure 5.2 Unsubscribe the system from the EAP 4.3 channel in RHN

Refer to the RHN documentation for instructions to unsubscribe a system from a channel: <link to RHN documentation will go here>

Procedure 5.3 Subscribe the system to the EAP 5.1 channel in RHN

The channel names are as follows:

Refer to the RHN documentation for instructions to subscribe a system to a channel: <link to RHN documentation will go here>.

Choose which optional components to install

EAP 4.3 included JBoss Messaging as the messaging provider. EAP 5.1 provides either JBoss Messaging or HornetQ as the messaging provider. EAP 4.3 included ws-native as the web server. EAP 5.1 provides either JBoss Native or JBoss CXF as the web server. When installing or upgrading EAP 5.1 you must choose which one of the two messaging providers you will install; and which one of the two web servers you will install. To switch to the other option after installation or upgrade requiring reinstalling the product.

In the following procedures $JMS_choice denotes the messaging provider you wish to install. Replace $JMS_choice with one of either jbossas-hornetq for HornetQ, or jbossas-messaging for JBoss Messaging.

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

Procedure 5.4 Issue the upgrade command on RHEL 4

Issue the following commands as root, substituting your choice for the optional $JMS_choice and $WS_choice:

up2date $JMS_choice $WS_choice resteasy jboss-eap5-native
up2date -u

Procedure 5.5 Issue the upgrade command on RHEL 5

Issue the following commands as root, substituting your choice for the optional $JMS_choice and $WS_choice:

yum install JMS_choice WS_choice resteasy jboss-eap5-native
yum upgrade --disablerepo=rhel-i386-server-5

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 EAP 4.3 channel, these packages will not receive security updates if they are left on the system.

Procedure 5.6 Remove remaining 4.3 packages on RHEL 4

Issue the following command as root:

rpm -e tomcat5-servlet-2.4-api-5.5.17-6jpp.ep1.2 geronimo-j2ee-1.4-apis-1.0-3jpp.ep1.2 qdox-1.6.1-1jpp.ep1.4 jacorb-2.3.0-1jpp.ep1.10.el4 asm-1.5.3-1jpp.ep1.2.el4 hsqldb-1.8.0.8-3.patch03.1jpp.ep1.3.el4 odmg-3.0-3jpp.ep1.2 jboss-seam-docs-1.2.1-3.JBPAPP_4_3_0_GA.ep1.20.el4 xml-commons resolver-1.1-1jpp.ep1.1 servletapi6-6.0.10-3jpp.ep1.1 ws-commons-policy-1.0-2jpp.ep1.7.el4 tanukiwrapper-3.2.1-2jpp.ep1.2.el4 berkeleydb-2.0.90-1jpp.ep1.1

Procedure 5.7 Remove remaining 4.3 packages on RHEL 5

Issue the following command as root:

yum remove bea-stax-api-1.2.0-0.rc1.2jpp.ep1.1.el5 berkeleydb-2.0.90-1jpp.ep1.1.el5 jboss-seam-docs-1.2.1-3.JBPAPP_4_3_0_GA.ep1.20.el5.1 tanukiwrapper-3.2.1-2jpp.ep1.2.el5 asm-1.5.3-1jpp.ep1.2.el5 geronimo-j2ee-1.4-apis-1.0-3jpp.ep1.3.el5.1 odmg-3.0-3jpp.ep1.2.el5.1 jacorb-2.3.0-1jpp.ep1.10.1.el5 bea-stax-1.2.0-0.rc1.2jpp.ep1.1.el5 servletapi6-6.0.10-3jpp.ep1.1.el5 ws-commons-policy-1.0-2jpp.ep1.7.el5 qdox-1.6.1-1jpp.ep1.5.el5

5.1 Identifying changed configuration files after an 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 you should 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. You should be careful to identify the impact of these changes on your infrastructure and your applications before performing this upgrade on your production systems.