Servlet init params

Servlet specific options may be specified using servlet init-params in the plugin.xml used to define the servlet as in the following example:

    <extension point="org.eclipse.equinox.http.registry.servlets">
        <servlet alias="/testaggr" class="com.ibm.jaggr.service.impl.AggregatorImpl">
            <init-param name="config" value="testaggr-config.js"/>
        </servlet>
    </extension>

The Aggregator supports the following servlet init-params:

Name	Description
config	This init-param is required and has no default value.  It specifies the name of the server-side AMD config file.
modulebuilders	Specifies the id of an extension implementing the com.ibm.jaggr.service.modulebuilders extension point that is used by the application.  More than one modulebuilders init-param may be specified.  If none are specified, then the default.modulebuilders extension defined in the Aggregator's plugin.xml is used.  See Extensibility for a description of module builder extensions.
resourcefactories	Specifies the id of an extension implementing the com.ibm.jaggr.service.resourcefactries extension point that is used by the application.  More than one resourcefactories extension may be specified.  If none are specified, then the default.modulebilders extension defined in the Aggregator's plugin.xml is used.  See Extensibility for a description of resource factory extensions.
httptransport	Specifies the id of an extension implementing the com.ibm.jaggr.service.httptransport extension point that is used by the application.  If not specified, the dojo.httptransport extension defined in the Aggregator's plugin.xml is used.  See Extensibility for a description of http transport extensions.
maxlayercacheentries	Specifies the maximum allowed number of layer cache entries. The default value is -1, which specifies no limit. This parameter is intended to guard against possible DOS attacks which might attempt to consume all available disk space on the server by methodically sending requests for layers with random combinations of modules. By specifying an upper limit on the number of layer cache entries, this situation can be avoided. The current implementation simply starts rejecting requests which attempt to add to the layer cache once the limit is reached. We intend to enhance the cache manager in a future release to allow specification of a maximum cache size in bytes, with the cache manager employing an LRU algorithm to age out stale cache entries when the maximum cache size is reached.
options	Specifies the filename of the properties file containing Aggregator options. If not specified, the default options file is aggregator.properties in the home directory of the user that launched the server.