Application Pool in IIS6

 Application pool in IIS6 :

 ________________________________________

Follow us on Facebook

Follow us on Google+

________________________________________

Application pools define the configuration parameters and boundaries of applications. An application pool is composed of one or more applications and require him or their execution in a shared context (eg same version of asp. Net for the entire pool) and the application pool settings (detection failure, recycling, monitoring CPU ...)

 

Creating an application pool :

 

 

To create an application pool, you must right-click Application Pools in IIS Manager console (IIS), and then choose New Application Pool.









 You can create an application pool with the default settings or choose another pool that you previously created to have the same configuration settings.

   

Settings application pool recycling :

. NET Framework 1.1 :
 
Settings application pool recycling allow you to control how system resources are recovered. The following sections describe how to specify the settings for application pool recycling.

Specifying settings application pool recycling :

 

Settings application pool recycling are specified in the Recycling tab of the Properties dialog box for an application pool.

To define the settings application pool recycling:

•  Open the IIS management console and expand the local computer by clicking the plus sign.
•  Expand the Application Pools folder by clicking the plus sign.
•  Click the right mouse button on the appropriate application pool, and then click Properties. The properties dialog box of the application pool is displayed.
•  Click on the Recycling tab, then set the appropriate settings for the application pool.

 
Recycling tab of the Properties dialog box of the application pool 

 

 Memory recycling :

 

Setting application pool recycling memory is equivalent to setting the ASP.NET process model memoryLimit. It indicates the maximum amount of memory that a worker process can use. If the work process exceeds this amount, a new process is created to replace it and all pending requests are reassigned to the new process. There are two important differences between the parameter of the ASP.NET process model and parameter memoryLimit application pool recycling memory: 

• The parameter memoryLimit ASP.NET process model uses only physical memory. Setting application pool recycling memory allows you to specify separate limits for physical memory and virtual memory. Physical memory (or a combination of physical memory and virtual memory) is commonly used for ASP.NET applications because of how the garbage collector works the Common Language Runtime. Virtual memory is commonly used for classic native applications that fragment the heap.

• The setting of application pool recycling memory is specified in megabytes, not as a percentage of the total memory.

 

Recycle work process :

Setting application pool recycle the worker process is equivalent to setting the ASP.NET process model requestLimit. It shows the number of requests that cause the recycling process work or an application pool. Recycle the worker process is disabled by default. Recycle to activate the workflow, select the check box and specify the number of requests in the spin box.

Recycle work process :

 

Setting application pool recycle worker processes is equal to the parameter timeout ASP.NET process model. It indicates the interval between recycling process work or an application pool. Recycle work process is enabled and set to 120 minutes by default. You can specify a different interval by changing the value in the spin box. To disable the Recycle work process, clear the checkbox. 

Settings application pool performance :

. NET Framework 1.1 :
 
Settings application pool performance allow you to control the operation of the labor process. The following sections explain how to specify the settings for the application pool performance.

Specifying settings application pool performance :
 
Settings application pool performance are specified in the Performance tab of the Properties dialog box for an application pool.

To define the settings application pool performance :

•  Open the IIS management console and expand the local computer by clicking the plus sign.
•  Expand the Application Pools folder by clicking the plus sign.
•  Click the right mouse button on the appropriate application pool, and then click Properties. The properties dialog box of the application pool is displayed.
•  Click the Performance tab, and then set the appropriate settings for the application pool.

Performance tab of the Properties dialog box of the application pool :

Garden Web :

 
Parameter Garden Web application pool parameters equivalent to ASP.NET process model and webGarden cpuMask. To enable Web Garden, specify a value greater than 1 for Maximum work process. This value also determines the maximum number of processes in the application pool.
Web gardens for using multiple processes, each process has its own copy of application state, session state in-process caches and static data. Web gardens are not to be used for all applications, especially if they maintain their status. Evaluate the performance of the application before deciding whether Web garden mode is appropriate.
When using a Web garden, it is important to understand how session state and round robin. It is also important to consider how other application pool settings affect the application.

Session State in a Web garden mode using process isolation work

When using a session state, you must not forget that isolation mode worker process does not support the routing of requests to return a process that issued the request. When an application runs in a Web garden with session state or ASP application, the application requests must be sent to the originating process. When using the IIS 6.0 application pool, make sure that the application maintains an open connection so its applications are returned to the appropriate process. If the connection is not kept open, the request will be sent to the next available work processes serving Web garden.

Robin in a Web garden by using the isolation mode workflow :

Robin is a method of load balancing application. When a request arrives, it is automatically sent to the next sequential process. For example, if a Web garden has four processes, requests are sent to process 0, 1, 2 and 3, in that order. The cycle is then repeated for the other queries.

Parameters of an application pool in a Web garden mode using process isolation work :

Some settings application pool have a specific behavior to a Web garden. The following table summarizes these behaviors. 

Settings application pool health :

. NET Framework 1.1 :
 
Settings application pool health allow you to control how the work process is monitored to function properly. The following sections describe how to specify settings for application pool health.
Specifying settings application pool health
Settings application pool health are specified in the Health tab of the Properties dialog box for an application pool.

To define the settings application pool health

•  Open the IIS management console and expand the local computer by clicking the plus sign.
•  Expand the Application Pools folder by clicking the plus sign.
•  Click the right mouse button on the appropriate application pool, and then click Properties. The properties dialog box of the application pool is displayed.
•  Click the Health tab, and set the appropriate settings for the application pool.

Health tab of the Properties dialog box of the application pool :

 

Activate the pinging :

The application pool setting Enable pinging is equivalent to setting the ASP.NET process model pingFrequency. It indicates the frequency with which ASP.NET ISAPI verifies the existence of the work process. If the workflow is absent, it is restarted. Activate the pinging is enabled and set to 30 seconds by default. You can specify a different frequency by changing the value in the spin box. To disable the Enable pinging, clear the checkbox.

Deadline to stop

The application pool setting time limit for the stop is equivalent to setting the ASP.NET process model shutdownTimeout. It indicates the time left in a working process to close properly. If the workflow is not closed within the specified time, the ASP.NET ISAPI interrupts workflow. Time for the stop is set to 90 seconds by default. You can specify a different maximum by changing the value in the spin box.

 

Settings application pool identity :

 

. NET Framework 1.1 :
 
Settings application pool identity, you can specify the account used by the workflow. By default, the workflow uses the Network Service account. However, you can specify a different Windows identity. The following sections describe how to specify the settings for the application pool identity.

Specifying settings application pool identity :

Settings application pool identity specified in the Identity tab of the Properties dialog box for an application pool.

To define the settings application pool identity :

•  Open the IIS management console and expand the local computer by clicking the plus sign.
•  Expand the Application Pools folder by clicking the plus sign.
•  Click the right mouse button on the appropriate application pool, and then click Properties. The properties dialog box of the application pool is displayed.
•  Click the Identity tab, and then set the appropriate settings for the application pool.
•  

Identity tab of the Properties dialog box of the application pool :

 

 Username and Password :

Settings application pool user name and password parameters are equivalent to the ASP.NET process model username and password. These parameters are used together to run the workflow using the specified Windows identity. By default, the workflow uses the Network Service account. However, if the check box is selected and Configurable text boxes Username and Password contain valid values​​, the workflow uses the Windows identity specified. In addition, you must add the Windows identity user group IIS_WPG.
 
To add the Windows identity of the user group IIS_WPG.
 
1. From the Start menu, right-click My Computer, and then click Manage.
2. Expand the Local Users and Groups by clicking the plus sign.
3. Click the Groups folder. A list of all groups defined on the computer is displayed in the right pane.
4. Right click IIS_WPG, and then click Add to Group.
5. Click the Add button and enter the account you want to use for the workflow.