So today was the day--I kicked everyone off one of our development servers and upgraded from CFMX 6.1 Standard to CFMX 7 Enterprise. I've done the installation on several machines by this point but this was the first installation on a server at my company that "matters" (i.e. other people use it and would gripe if it was down for too long).
As expected everything went 100% smoothly! I just thought I'd share some thoughts about the installation and the improvements I'm already seeing in moving from CFMX 6.1 Standard to CFMX 7 Enterprise.
This installation was on Windows Server 2003 (Enterprise Edition), and I did the multi-instance/integrated JRun installation (option 2). The server supports three separate web sites, and we use IIS 6. We have maybe 20 datasources involved and a bunch of Verity collections as well, but nothing too out of the ordinary. I must admit when I upgrade things I actually tend to do a completely fresh installation, so I decided to do that here as well. Yes, probably unnecessary, but it gives me a bit more peace of mind. (Hey, that's just me--I've done the "co-exist" install on some other machines and it worked great as well.)
So step one was to move all our web app files to a backup directory and then uninstall CFMX 6.1. No problems, no lingering "stuff" after the uninstall, so that was all good.
Step two was to install CFMX 7, and as most of you probably know by know, the installer is really sweet. I know there are people on the Macromedia forums that are having problems with the download, etc. but I did a fresh download today just as a test, and I had no problems whatsoever with the installer I just downloaded.
As I said above, I chose option 2 which does an integrated JRun installation. The reason for this is that it includes the Enterprise Manager that allows you to manage multiple instances of ColdFusion from the CF administrator. I blogged about this feature briefly before, but to reiterate, this is seriously cool stuff. Now you can much more easily deploy and control multiple instances of CF, even on remote servers.
So after the installation succeeded I moved my web app files into their new home and everything just worked. This was for the first of the three sites this servers supports. Now here's where things get cool!
Next, I went to the Enterprise Manager and clicked on "Instance Manager." Then I clicked on "Add New Instance," gave my new instance a name, and away it went. A couple of minutes later I had a second instance of ColdFusion. This of course is to run the second site on this server, and this isolation is going to be fantastic for several reasons. First, if one site needs to be restarted it doesn't affect the other. Second, I have better control over access, security, etc. because the sites are now running completely independently of one another.
Since this is our dev server we just use a single IP address for the whole server and user host headers in IIS for the different sites, so I used the JRun web server connector tool and hooked CF server 1 into IIS web site 1, and server 2 into a different IIS web site that had a host header. Again, no problems, everything just worked! I'll sleep better at night now that all my sites are independent from one another.
That's pretty much all there is to report right now--once this setup has been running well on our dev server for a week or two we're going to schedule this same process on our two clustered production servers. I'm really encouraged by how smoothly this went.
How about the rest of you? Any installation experiences to share?