IIS Application Pools allow for grouping of similar or related applications to facilitate easy management and configuration. Each application assigned to an application pools (or app pool) is isolated from other apps so that issues in one pool do not impact apps in other pools. Applications which have similar performance profiles or which belong to the same department in the business can be grouped together.
IIS 7 automatically creates serveral application pools, including the default app pool which is used when you create a new application. When you create a new application, it is automatically assigned to the default application pool (DefaultAppPool), and a previously deployed app can have its application pool changed (for a varierty of reasons such as to enable it to use a newer version of the .NET framework). Application pools can be created and managed using IIS . In the IIS Management Console expand the server and select Application Pools. This lists the app pools currently set up on the server as shown below:
Application pools set up in IIS
The application pool listing displays most of the key characteristics of each app pool:
- Name : The name of the application pool which cannot be changed after it has been created.
- Status : Whether the application pool is running or stopped.
- .NET Framework Version : The .NET Framework version which will execute the code.
- Managed Pipeline Mode : IIS supports Integrated and Classic pipeline modes for handling requests.
- Identity : The Windows account which runs the apps in the pool.
- Applications : The number of applications running in the pool.
Creating a New Application Pool
Create a custom application pool by clicking the Add Application Pool link from the right hand panel of the Application Pools screen.