I actually got around to doing the upgrade. Here are my comments …PAINLESS. I installed 3.3.2 on another Linux Box and followed the directions in the upgrade guide … moving the necessary files over from Wildfire. Forget about copying over the plugins … When you bring the new system up, go ahead and reload them after you configure the new server via the webtool. When you copy over the wildfire.xml->openfire.xml, make sure you set the attributes (chmod 0755 openfire.xml). If you don’t, the IM server will run when started using …/bin/openfire.sh but will have issues using “service openfire start” because it doesn’t have “write” privilege.
After testing on my test system, I started looking at the file structure and it dawned on me that you can install openfire over wildfire. This is possible because wildfire is stored in /opt/wildfire/… and openfire is stored in /opt/openfire/… The openfire startup files (init.d and /etc/sysconfig) are named openfire so there is no name conflict.
By testing on my test system, I could configure openfire using my postgreSQL and test by pointing a few IM Clients to my test system. When I had a “warm and cozy” feeling, I copied the openfire files (openfire->init.d and openfire->/etc/sysconfig) to my live system and I did the rcX.d files by hand. Did a tarball of /opt/openfire and dumped it onto the live server. Turned off wildfire and started up openfire. The IM client disconnected and reconnected with NO ISSUES.
Hope this helps … thanks for all the comments