Configuring application manifest caching and timeout

In the Application Host settings.xml file, you can control how regularly the Application Host reloads manifest files using the <manifestCacheMaxAge> element, and control when the Application Host times out using the <manifestLoadTimeout> element.

Procedure

  1. Go to the Web site where an SDL Application is running.
  2. Open the Application Host settings.xml file in a text editor.
  3. Specify, in seconds, the <manifestCacheMaxAge> and <manifestLoadTimeout>:
    <applicationHost>
            <manifestCacheMaxAge>3600</manifestCacheMaxAge>
            <manifestLoadTimeout>5</manifestLoadTimeout>
            <applicationReferences>
                   <applicationReference id="sc" url="https://DomainName/InfoShareAuthorQ/manifest/manifest.html"/>
                   <applicationReference id="wcm" url="http://DomainName/SDL/manifest/manifest.html"/>
                   <applicationReference id="cma" url="http://DomainName/Frame/manifest/manifest.html"/>
                   <applicationReference id="mm" url="https://DomainName/vms/frame/manifest/manifest.html"/>
             </applicationReferences>
    </applicationHost>
    <manifestCacheMaxAge>
    When the Application Host is loaded it reads its configuration settings, builds the list of <applicationReferences> and loads their manifest files. As manifest files are fairly static, they are cached by the browser and/or proxy servers. You can control how regularly the Application Host reloads manifest files using the <manifestCacheMaxAge> element.
    The <manifestCacheMaxAge> element defines the maximum period (in seconds) that the manifest file can be used from the cache. By default, the value is set to 1 hour so when changes are made to a manifest file users will see the changes take effect in an hour.
    <manifestLoadTimeout>
    The Application Host may fail to load application manifest files, especially when these are loaded from different locations. When this happens, for example because the remote web server is inaccessible, the Application Host logs a warning message in the browser console and initializes the UI without the failed application suite data.
    You can control when the Application Host times out if it does not get a response from the manifest file using the <manifestLoadTimeout> element. By default,<manifestLoadTimeout> is set to 5 seconds.
  4. Save and close settings.xml.