1. JBoss version changed from 3.2.6 to 3.2.7
Please follow the general guidelines whenever you upgrade versions - see User Guide - Upgrading Applications
http://support.eapps.com/hsp/upgrades
Things to consider in this update:
1. The original /etc/jboss3/jboss.conf will be saved as /etc/jboss3/jboss.conf.rpmsave and a new one will be put in its place. If the customer had any configuration changes, they will need to apply them again from the .rpmsave file (but do not just copy that file over, otherwise the bug fix will be removed).
2. Permissions will be updated to user:group jboss:jboss once this is installed.
3. Due to the extensive amount of changes between versions, instead of upgrading files in the /opt/jboss3/server directory, that directory is renamed to /opt/jboss3/server.backup.[datetime]. A new fresh 3.2.7 instance of the /opt/jboss3/server directory is then put in place. All applications, configurations, etc. will need to be moved back in.
4. Authentication is performed using a flatfile system. The files are located in /opt/jboss3/server/[config set]/conf/. The users are setup in users.properties and roles are setup in roles.properties. By default, a user is created called admin with a password set to the default domain. The admin user is added to the JBossAdmin role which has access to both the jmx-console and web-console.
