Internet Information Services (IIS)
The Web Server will host the website for the Application. It does this with Microsoft Internet Information Services (IIS) which will be set up on the Web Server. IIS is responsible for receiving the requests when users browse the site and sending back the response.
If your site will have an SSL certificate applied, it will be done so through IIS. The Certificate Signing Request will then be created an completed using IIS. The result will be the SSL security of encrypting data sent to and from the site.
Users who browse the site are assigned a session Id by IIS. Any session variables created by application such as user session variables which identify a user as logged in, will be stored in the IIS worker process. This means that when the Application Pool Timeout is reached, IIS will kill the worker process and the associated session variables will be lost. The user will be logged out of the site because the user session variables that are set on login will no longer exist.
IIS kills off the worker processes every so often in a process called IIS Worker Process Recycling. Over time, problems could arise in the processing (memory leaks in the application code, undisposed resources, etc.) that IIS wants to clean up without having to shutdown the server. So it will periodically tell the worker process to die off, and spawn a new one.
This can be done manually be Recycling the Application Pool. Recycling means the worker process that handles requests for that application pool is terminated and a new one started. This is generally done to avoid unstable states that can lead to application crashes, hangs, or memory leaks. This also means all users on the site will be logged out because all session variables will be lost.
Application pools are used to separate sets of IIS worker processes that share the same configuration and application boundaries. If IIS is managing multiple sites, different application pools could be set up for each site so that recycling the default application pool does not kill the worker process in every site in IIS.
IIS can be configured to have more than one worker process for an application pool. This is called the Web Garden option and is not the default setting. As a result, ASP session data that is stored in one process is not available to other processes in that application pool. This means different work processes will be handling requests from the same user, so session variables cannot be stored in the worker process, which is the default option. Continuing to do so would result in the user logging on and the next time a request is made, if the same worker process is not used, the session variable for being logged in would not be present and the user would be logged out. If session variables are not stored here or are not used, this option can be used to increase performance.
IIS logs can be turned on and obtained if debugging an issue requires further information than EASYProcess can provide. Changing log settings and where the IIS log files are stored differs for the IIS version used.
If IIS is having any issues, it can be restarted. To restart, click Start, click Run, type IISReset, and then click OK. A Command Prompt window opens displaying the status of the IISReset command. You should read the status at the command prompt to make sure that IIS stops and restarts.