IIS App Pools: Suggestions, best practices?

[bermanbp]

Hello,

I inherited several web applications hosted on the Win2k3, IIS 6.0 server. I noticed early on that each application was not broken out into separate app pools as is good practice and beneficial in troubleshooting any possible serious application bugs. Most of the applications are asp.net 2.0 apps but there are a couple legacy ColdFusion sites.

I was asked to move these in their own pools. I have never actually set this up myself. Can somebody tell me how to best do this on production sites and what, if any downtime, I should expect?

Any tips, pointers, or anecdotes would be greatly appreciated.

Thanks,
Brett

[Brandoe85]

I've never had any problem doing so - it's quite simple as well. In IIS you create the new application pool; you then set the application pool that you want the application to use on the virtual directory properties of that application.

I've done this over and over with no issues - just remember if you have 1.1 and 2.0 apps they need to be in their own application pools you can't mix 1.1 with 2.0. I've never done coldfusion so I can't comment on that.

Good luck

[bermanbp]

Thanks. I didn't think there was too much more to it, but it is reassuring to hear it elsewhere. I'll probably separate the CF from the .NET as well.

Cheers,
Brett

[demtron]

I tend to put low volume sites together in a common pool and high volume sites each in their own individual pool. I run a server with over 30 sites, some with .Net 1.1 and some with .Net 2.0 The flexibility with troubleshooting is really important to me. You'll be glad you set up your sites this way.