Parameter:
HTTPEnableXPagesPreLoadShort description: Enables preloading of XPages applications when the HTTP task starts (faster first page request).
Profile
Parameter | HTTPEnableXPagesPreLoad |
Category | HTTP / Web |
Component | Server |
Available since | 9.0 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | 0 = disabled, 1 = enabled |
Description
XPages applications require considerable time on the first request to initialize OSGi bundles, JSF application trees, and the associated Java classes.
HTTPEnableXPagesPreLoad=1 instructs the HTTP task to perform this initialization already at startup – the first user request is then answered seconds to minutes faster.Which applications are preloaded specifically is controlled by
XPagesPreloadIncludeDB.Example configuration
HTTPEnableXPagesPreLoad=1 XPagesPreloadIncludeDB=apps\app1.nsf,apps\app2.nsf
Notes & pitfalls
- The HTTP startup takes noticeably longer – useful for productively used XPages applications.
- Without
XPagesPreloadIncludeDB, some versions preload all XPages NSFs – set the list explicitly.
- Increases the initial JVM heap requirement – adjust
HTTPJVMMaxHeapSizeif needed.
- With very many XPages apps, restrict the preload list to the most important ones.
- The change only takes effect after a restart of the HTTP task.