Release Notes - JBoss 7 (CentOS 6/ISPmanager)
- 09/01/2012 12:35 PM
Release Notes - JBoss 7 (ISPmanager Control Panel)
Highlighted Features and Fixes in JBoss AS 7.1.1
Features
- High-level CLI commands for many tasks
- New system health displays
- Numerous usability improvements
Fixes
- All passwords are now pre-hashed for each realm
- CLI tool now available to add users to the properties file
The official Release Notes for JBoss 7.1.1 are available here - https://community.jboss.org/wiki/AS710FinalReleaseNotes
For more information about all the new features in JBoss 7, including links to several webinars, go here - http://www.jboss.org/as7
Highlighted Features and Fixes in JBoss AS 7.0.2
Features
- Faster startup
- Better memory management
- New Web-based deployment and management interface
The official Release Notes for JBoss 7.0.2 are available here - https://docs.jboss.org/author/display/AS7/Getting+Started+Guide
For more information about all the new features in JBoss 7, including links to several webinars, go here - http://www.jboss.org/as7
How to upgrade
The methods to upgrade from JBoss 6 to JBoss 7 or from JBoss 7 to a newer version of JBoss 7 differ. Please read these Release Notes carefully.
 |
The upgrade for JBoss has to be done manually, there is no way to automate the process. Please read the upgrade instructions for your scenario and proceed accordingly. Failure to follow the correct upgrade instructions can result in data loss and extended downtime for your applications and users. |
For best results, you should provision a small Virtual Machine with JBoss 7 and the required database server for your application, and then deploy your application there for testing. That way you can ensure that everything will work correctly before doing the upgrade on your production server. Once the testing is over, you can simply cancel the testing server from the Portal. Before upgrading to JBoss 7, make sure that your application is compatible with any new features and configurations available in JBoss 7.
The method to deploy and manage applications is very different in JBoss 7 than in previous versions of JBoss, so please make sure you read the available eApps User Guides and also the official JBoss 7 documentation.
The eApps User Guides are found here:
- JBoss 7 Installation and Tuning - http://support.eapps.com/ispmgr/jboss7-install
- JBoss 7 with mod_jk and mod_proxy_ajp - http://support.eapps.com/ispmgr/jboss7-mod_jk
- JBoss 7 Standalone (without Apache) - http://support.eapps.com/ispmgr/jboss7-standalone
The official JBoss 7 documentation is found here:
- Documentation: JBoss 7 AS - https://docs.jboss.org/author/display/AS71/Documentation
How to upgrade - JBoss 6 to JBoss 7
To upgrade, you will need to backup your existing application files, databases, and any configuration files related to your application. Then you will need to uninstall the previous version of JBoss, and then install JBoss 7, and then redeploy your application. See the User Guides listed above for more information on how to deploy your applications using JBoss 7.
The best case scenario is that you provision a test VM running JBoss 7 and your database server, and deploy your application on the test VM to make sure that your existing JBoss 6 codebase works correctly with the new features in JBoss 7. You need to test very thoroughly. Once you are sure that all works as expected, you could then perform the upgrade on the production server. You could then cancel the test VM in the Customer Portal.
Information on how to remove and install applications in ISPmanager is available in the ISPmanager Overview: http://support.eapps.com/ispmgr/overview#applications
How to upgrade - JBoss 7 to JBoss 7
If you are currently running JBoss 7 and wish to update to a newer version of JBoss 7, you will need to make a backup of your existing application files, databases, and any configuration files related to your application. Then you will need to update JBoss 7 from the command line of the Virtual Machine using yum, and then redeploy your applications.
The best case scenario is that you provision a test VM running the newer version of JBoss 7 and your database server, and deploy your application on the test VM to make sure that your existing JBoss 7 codebase works correctly with the new features in the newer version of JBoss 7. You need to test very thoroughly. Once you are sure that all works as expected, you could then perform the upgrade on the production server. You could then cancel the test VM in the Portal.
Upgrading JBoss 7 using yum
To upgrade JBoss 7 using yum, you will need to log in to the Virtual Machine using SSH, and be able to work as the root user.
Once you are logged in, change directories to /opt, which is where the existing jboss7 directory is located. Upgrade JBoss with the yum update jboss7 command.
| [root@eapps-example ~]# cd /opt/ [root@eapps-example opt]# ll total 4 drwxr-xr-x 10 jboss jboss 4096 May 1 11:58 jboss7 [root@eapps-example opt]# yum update jboss7 |
Once the installation is complete, there will be two JBoss 7 directories - the jboss7 directory which is the new version, and the jboss7-pre-7.X.X.Final-upgrade directory, which contains all the files from the original jboss7 directory.
| [root@eapps-example opt]# ll total 8 drwxr-xr-x 11 jboss jboss 4096 May 1 12:38 jboss7 drwxr-xr-x 10 jboss jboss 4096 May 1 11:58 jboss7-pre-7.1.1.Final-upgrade [root@eapps-example opt]# |
At this point, you need to redeploy your application, making sure that you have put all configuration files, tunings, JDBC connectors, and application files back in place. Be sure to restart JBoss after making any changes. See the User Guides listed above for information on how to deploy your files if needed.