- Print
- DarkLight
- PDF
How should the application pool be configured so that it is 'Awake' immediately in the morning?
In order to ensure that the WakeUp in the global.asax is triggered, a number of steps are important:
- Within IIS, the 'Application Initialization Module for IIS 7.5' must be installed. After installation, a server reboot is required. The module can be found here:
http://www.iis.net/downloads/microsoft/application-initialization
- Open inetmgr, and click on the server / root node in the top left corner, and go to configuration editor there
- At the top, go to Section and then ApplicationHost / ApplicationPools. In Collection, click on the dots at the end:
- Make sure that the application pools in question (at least BO and RV, but probably also RE-Kernel) have the following 2 settings correctly:
- autoStart: True
- StartMode: AlwaysRunning
- In order to ensure that the autostart also calls the Application_Start of the global.asax, the preLoadEnabled must now be set correctly (the Application Initializer module is required for this).
Open the file 'Applicationhost.config' for this, which can be found here: C:\Windows\System32\inetsrv\config. Make sure to backup this file before making any changes!! - Go to the <sites> node, and search within it for the correct site (e.g. bo.retail3000).
Within that node, in the 'application' node, add this: preloadEnabled="true" .For example:
<site name="acceptatie.retailvista.net" id="13" serverAutoStart="true">
<application path="/" applicationPool="acceptatie.retailvista.net" preloadEnabled="true">
<virtualDirectory path="/" physicalPath="c:\inetpub\wwwroot\acceptatie.retailvista.net" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:80:acceptatie.retailvista.net" />
</bindings>
</site>
- Open IIS now and check if the application pools start. If the IIS application initializer is not (correctly) installed, the site will not start anymore.
For IIS 8
1. The Application Initializer is already included by default.
Follow steps 2, 3, and 4 above.
2. In IIS, in the properties of the website (not the app pool!), enable preload: