In order to add an IIS application pool to a packaging project, users go to the IIS view of the Visual Designer mode.
•With a click on the Create new... button, the options menu is displayed. Click on Application pool to invoke the New Application Pool Wizard.
•As an alternative access to the very same wizard, users may click on the Application pools node within the IIS object tree structure on the left hand side of the IIS view, and click on the Add new application pool button that is displayed within the details pane at the right-hand side.
Work your way through the steps of the wizard to define all required properties for the new item.
At any time, using the Next or Back buttons, which are displayed at the bottom of the wizard dialog, allows to navigate within the already processed steps.
To exit the wizard without creating a new object, use the Cancel button, also located at the bottom of the wizard dialog.
Step 1: General
.NET CLR version
This property specifies the .NET Framework version to be used by the application pool. Please select the required version from the predefined set of available options.
Managed Pipeline mode
Please select one of the predefined settings:
•Classic
Is the traditional mode as known from IIS6 and earlier. Run this way, IIS operates directly on ISAPI extensions and ISAPI filters.
•Integrated
was introduced as new mode in IIS7. The IIS pipeline is equal to the ASP.NET request pipeline.
Whilst the classic mode treats ASP.NET as external plugin, without knowledge about and access to internal processes, the integrated mode has ASP.NET fully integrated into IIS.
Name
The name of the app pool as it will be displayed within the IIS application pools overview. It is an alphanumerical string of max. 72 characters length. It is recommended to make sure each application pool has a unique and informative name, as this helps to support object management for the created IIS structure on the target machine.
Queue length
This value defines the maximum number of requests that Http.sys queues for the application pool. When the queue is full, new requests receive a 503 “Service Unavailable” response. The default of 1000 is already given as a recommendation when the wizard is invoked.
Component
Each application pool object has to be related to a component item of the packaging project.
To select an existing component as parent object of the app pool item, users click on the downwards-pointing arrow at the right-hand side of the component selector control. A list of existing components is displayed. The actual selection is done with a click on any of the given components.
To create a new component for the app pool object, users click on the browse button [...] at the right-hand side of the component control. The common dialog type Select Component is displayed, ready for creating and selecting components.
Overwrite existing application pool
This checkbox triggers a check on the target machine IIS, searching for application pools with the same name. If such an object exists, it is either fully overwritten with the properties defined for the application pool contained in the package (when the checkbox is active), or left totally unchanged (when the checkbox is inactive).
Step 2: CPU
Limit
Configures the maximum percentage of CPU time that the worker processes in an application pool are allowed to consume over a period of time as indicated by the Limit Interval setting.
Setting this value to 0 disables limiting the worker processes to a percentage of CPU time.
Limit action
Please select the action that has to be taken when the limit is reached:
•NoAction - an event log entry is generated.
•KillW3WP - the application pool is shut down for the duration of the reset interval and an event log entry is generated.
•Throttle - the CPU consumption is limited to the value set in Limit. The Limit interval is not used and an event log entry is generated.
•ThrottleUnderLoad - the CPU consumption is limited only when there is contention on the CPU. The Limit interval is not used and an event log entry is generated.
Limit interval
Specifies the reset period for CPU monitoring and throttling limits on the application pool. When the number of minutes elapsed since the last process accounting reset equals the number specified by this property, IIS resets the CPU timers for both the logging and limit intervals.
Setting this value to 0 disables CPU monitoring.
Step 3: Process Model
Identity
Configures the application pool to run as a built-in account, such as
•Network Service (recommended)
•Local Service
•Local System
•ApplicationPoolIdentity
•As a specific user identity (Other)
User
This set of control becomes active as soon the the Identity property is set to Other.
Accessing system parts in the name of an explicit user identity usually requires credentials. These have to be given in the form of a user object. To select or create a user object, click on the browse button [...] at the right-hand side of the user input field. The Select User dialog is displayed. Please refer to the Common dialogs section for further details on how to manage user data objects.
|
Be aware: User objects may very likely be used at several places within SQL database, script, and IIS management structures. When the same user item is referred to from different locations, changing the properties of that user item actually takes effect for all related objects. Please double-check the correctness of user profile changes, and make sure all related objects are still valid and operational with the modified set of properties. |
Idle timeout
Amount of time a worker process remains idle before it shuts down. A worker process is idle if it is not processing requests and no new requests are received. The default of 20 minutes is already given as a recommendation when the wizard step is displayed.
Maximum worker processes
The maximum number of worker processes permitted to service requests for the application pool. If this number is greater than the recommended default value of 1, the application pool is called a "web garden".
Step 4: Recycling
Private memory limit
The maximum amount of private memory a worker process can consume before causing the application pool to recycle. A value of 0 means there is no limit.
Regular time interval
The period of time after which an application pool recycles. A value of 0 means the application pool does not recycle at a regular interval.
Request limit
The maximum number of requests an application pool can process before it is recycled. A value of 0 means the application pool can process an unlimited number of requests.
Specific times
A set of specific local times, in 24 hour format, when the application pool is recycled.
Virtual memory limit
The maximum amount of virtual memory a worker process can consume before causing the application pool to recycle. A value of 0 means there is no limit.
Step 5: Summary
Use the summary page to check the correctness of the application pool properties that were defined during the previous wizard steps.
•If all properties are set as required, click Process to finally create the application pool item.
•If changes are due, click Back until the wizard step with the incorrect property definition(s) is displayed and make modifications as required.
Please note that changes in an early step may lead to different defaults or options in any later step. Therefore, please verify that all steps contain the desired settings whilst NEXTing to the summary page again.
Step 6: Finished
Once the new application pool object has been created, the wizard can be closed by using the Finish button at its lower right corner. The IIS view is updated, and the tree structure of existing items contains the newly created object.