Skip to Content

Auto start IIS 7.5 in Jitterbit App Builder

Confirm that the application initialization module is already installed in IIS

  1. Open up IIS Manager
  2. Click on the Server
  3. In the main panel, click on Configuration Editor
  4. Expand the system.webServer node.

  5. If there is no ApplicationInitialization element in this node, then it needs to be installed.

    Applicationinitializationnotinstalled

    • (in above screenshot, Application Initialization is not installed)

    • (in the screenshot below, Application Initialization is installed)

    Applicationinitializationisinstalled

  6. If not installed, install application initialization.

    Caution

    Server restart will be required after installation.

  7. Close IIS Manager

  8. Download the installation package from Microsoft using one of the following links:

  9. Run this file. There are no options, click install, then Finish.

    Installcomplete

  10. Restart the Server for changes to take place. This feature will not work without restarting the server.

  11. Check installation. (see step 1 above)

Important

This element will appear after the installation even if you do not restart the server. This does not mean that application initialization was fully installed. You must restart your server for the changes to take affect.

Configure application initialization

  1. Open IIS Manager

  2. Change every application pool to have AutoStart = False except for the App Builder application pool.

    1. Click on each application pool
    2. Choose Advanced Properties
    3. Set AutoStart = False
    4. For the App Builder application pool set AutoStart = True

The next settings are not available in the IIS 7.5 Manager UI. They will be performed in the applicationHost.config file.

  1. In a standard installation the applicationHost.config should be located in: C:\Windows\System32\inetsrv\config
  2. SAVE A COPY OF THE THE FILE
  3. Open up ApplicationHost.config in a text editor

  4. Locate the App Builder Application

    <applicationPools>
    <add name="DefaultAppPool" autoStart="false" enable32BitAppOnWin64="false" managedRuntimeVersion="v4.0" />
    ...
    <add name="App Builder" autoStart="true" managedRuntimeVersion="v4.0" />
    ...
</applicationPools>

  5. Change the App Builder node by adding startMode="AlwaysRunning":

    <applicationPools>
    <add name="DefaultAppPool" autoStart="false" enable32BitAppOnWin64="false" managedRuntimeVersion="v4.0" />
    ...
    <add name="App Builder" autoStart="true" managedRuntimeVersion="v4.0" startMode="AlwaysRunning" />
    ...
</applicationPools>

  6. Locate the App Builder Application:

    <site name="Default Web Site" id="1">
    ...
    <application path="/" applicationPool="DefaultAppPool">
        <virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\wwwroot" />
    </application>
    <application path="/App Builder" applicationPool="App Builder">
        <virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\wwwroot\App Builder" />
    </application>
    ...
</sites>

  7. Change the App Builder node by adding preloadEnabled="true":

    <site name="Default Web Site" id="1">
    ...
    <application path="/" applicationPool="DefaultAppPool">
        <virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\wwwroot" />
    </application>
    <application path="/App Builder" applicationPool="App Builder" preloadEnabled="true">
        <virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\wwwroot\App Builder" />
    </application>
    ...
</sites>

Application Initialization is now configured correctly. Following are links indicating how to test the behavior or trouble shoot some common issues that have been encountered.

Set idle-timeout to 0

Image 002 1

Testing and troubleshooting