- Download ColdFusion MX from Adobe website.
- Get all confused about needing a serial number and try to think of ways to get around it.
- Finally realize you don't need a serial number to install the developer edition, and also think that even if you did "find" one, you'd be in hot water for using not-so-legal software on company property.
- Set up multiserver configuration using Apache2, not realizing it may cause issues since PHP4 is also on Apache.
- Wait 20 minutes.
- Freak out when you try to start the Apache server when an error comes up, only to find out it's already been started and it's a Windows bug.
- Run configuration wizard.
- Wait another 10 minutes.
- Spend the rest of the day doing actual work. In the meantime, [incorrectly] shut down the multiple instances of JRun that are using up approximately 300 KB of memory. Stop Apache server while you're at it, that thing eats memory too.
- Start Apache again, try to start JRun only to fail because "some JDBC thing wasn't defined in jrun.xml." (Not exact wording.)
- Rinse, repeat, get multiple Internal Server Errors while trying to load the ColdFusion admin. Try to figure out why JRun isn't working, realize that PHP4 is probably also messed up since CF is now on the same port, etc.
- Uninstall ColdFusion.
- Try to reinstall, only to find out stupid JRun wasn't uninstalled the first time around.
- 1 hour later: Finally get ColdFusion back up and running.
Go home, because it's already 5, I need to go biking, and there's no way I'm going to sit here another hour going through the tutorials.






August 15th, 2008 at 11:29 am
Wow dude, rough day. One thing I would like to note is that PHP and CFML can easily co-exist in apache easily. I have never experienced any issues where they collide. Apache will read the file extension .php or .cfm and determine which to use.. nothing to do with ports.
Let me know if you need anything help. I have done my fair share of installing PHP , CF, PERL etc…
-Randy