Read more articles...
It has been ages since I've setup ColdFusion with IIS and at my new job we're also using Railo. Last week we worked through the installation process for getting both Adobe ColdFusion and Rail connected to IIS.
I thought I'd blog about it here as it may be helpful to others.
- Windows 7
- IIS 7
- ColdFusion 9
- Railo 4
Edit your hosts file (C:\Windows\System32\drivers\etc\hosts) and add the following:
- 127.0.0.1 a.local
- 127.0.0.1 r.local
- Click Control Panel > Programs > Turn Windows Features on or off.
- Install IIS with these options
- Verify configuration
- For: IIS Metabase and IIS 6 configuration compatibility
- 32bit Windows - off
- 64bit Windows - on
- Open IIS Management Console
- Delete default website and setup two new sites.
- Adobe (C:\inetpub\wwwroot\adobe) a.local
- Railo (C:\inetpub\wwwroot\railo) r.local
- Create an index.html file and place a copy in each root /coldfusion/index.html & /railo/index.html
- Verify IIS responds to both http://a.local and http://r.local
While you can organize your directories how you like - this guide assumes you have created the two directories under the webroot.
- Select "Use internal web server"
- Verify you can access the local ColdFusion administrator on port 8500: http://127.0.0.1:8500/CFIDE/administrator/index.cfm
- Run the Unofficial Updater to patch ColdFusion
Install Railo (NOT Express)
- During Railo installation it will connect to IIS
- Verify Railo installed correctly by creating C:\inetpub\wwwroot\railo\index.cfm
<cfdump var="#server#" />
- Verify the dump for Railo information at http://r.local
- Run the ColdFusion web connector: C:\ColdFusion9\runtime\bin\wsconfig.exe
- Select the "Adobe" IIS Website (which you created above)
- Click "Configure web server for ColdFusion 9 applications"
- Click OK
- Create an index.cfm in C:\inetpub\wwwroot\adobe directory with a cfdump tag
- Verify http://a.local/index.cfm returns a proper ColdFusion dump (NOT a Railo dump!)
- If you continue to get the "Bon Code" error try re-registering ASP.net. Re-register asp.net under the correct .net version, run command: