I did reinstalled CF9 many times and whenever I tried to create an ODBC DSN with ODBC Socket , I will get an error of 'ODBC is not installed.

When Installing/updating CF9, I have selected all subcomponnents to make sure it installed ODBC Socket.

Please help to see iif it works on your.

Thanks, BN.

Yeah, I did some tweaking, but couldn't get down even close to what Tomcat runs totally stock. As for clustering, I'm not sure what you mean? We run a whole pile of clustered apps on Tomcat at work without any issues… Perhaps JRun enabled some CF-specific clustering stuff, and that's what you're referring to?

If they're just plain ol' Java, you shouldn't have to change anything. If they rely on executing in a JEE App Server you'll be stuck, because Tomcat is only a JEE Web Container, but that (and reliance on internal JRun APIs) should be the only stumbling blocks to moving from one container to the other.

We've run JRun4 on IIS6 on top of Windows2003 with CF8 now for more than a year with absolutely no hiccups. JRun even is multiinstance, and we have a MSSQL 2005 db-engine. All the sites and the webapps are high-volume, so I don't know what's been bothering you!

Maybe went your problems here?

Sebastiaan

IIS 6/7 works with Tomcat just fine; that's how we used to host our CF before we switched to Apache (on Windows) and now to Linux. I'm not an IIS guy so this is really generic, but you set up a filter to Tomcat in much the same way you currently have a filter set up to JRun. Tomcat comes with stuff to make Windows services out of your daemons as well.

JRun provides some hard-core virtualization of the webroot that Tomcat does (and is much better done with the web server anyway), so if you're using that you'll probably need to reorganize your webroot a bit. But that shouldn't be too much work, and won't affect your code itself (unless you have hard coded paths in there or something).

In our company we have been running an application on IIS5.0 and JRUN 4.0 for about 6 years already. The app database is SQL 2005. Now we are in the need of upgrading to IIS 6.0 or IIS 7.0. We have been chasing a solution to implement JRUN 4.0 with those versions of IIS and it has been a complete nightmare for months.

We would like to find an easy way to get rid of JRUN 4.0 and upgrade our IIS server. Do you happen to know if IIS 6.0 or IIS 7.0 works fine with TomCat? Is there an easy way to do the migration smoothly without having to change code? We understand our code is not dependant on JRUN.

Thank you.

I'll have to agree on Railo there – develoing all new apps in Railo, but always building them so they are immune to app-engine specific oddities. It means writing as standard CFML as possible, and if needed build in switches for the different app-engines (f.ex. CF8+: CFIMAGE vs. Railo 3+: imageCFC).

Most of my development work I do on the standalone install with Railo + Jetty on WinXP/Apache/MySQL. Serverwise we're divided between CF8+/MySQL/Windows2003/IIS6 and Railo3+/Tomcat/Apache/Linux – but the Railo engine is so much faster and easier to set up. The two different administrators are a thing of beauty. It takes some time to get used to some Railo quirks in the administrator, and not all you can do in CF-Admin you can as easily or at all do in Railo-Admin. But I believe it's getting there towards v9 compatibility (the next Railo dognamed-version).