Web Publishing Installation Guide

Configuring the Web Publishing Engine 43
Setting server-side XSLT stylesheet caching
Server-side caching stores frequently used XSLT stylesheets in memory, which increases Web Publishing
Engine performance. The Web Publishing Engine uses caching only when it is in Production mode.
To set server-side XSLT stylesheet caching:
1. In the Publishing Engine Configuration: Custom Web Publishing with XSLT page, select Production mode.
2. For stylesheet caching, select Enabled.
3. Choose a size from the cache size menu:
1 Small: for solutions using less than 25 XSLT stylesheets
1 Medium: for solutions using between 25 and 100 XSLT stylesheets
1 Large: for solutions using more than 100 XSLT stylesheets
4. If you are finished making configuration changes in the Administration Console, click Commit to save the
settings.
5. If you want the new committed settings to take effect immediately, click Restart Publishing Engine.
Configuring the interaction between web sessions and database sessions
Sessions allow you to store data or maintain states between requests. Custom Web Publishing with XSLT
supports two types of sessions:
1 database sessions: FileMaker Server creates a database session whenever it retrieves data for a request. The
maximum number of concurrent database sessions is determined by your FileMaker Server license.
1 web sessions: The Web Publishing Engine creates a web session whenever you use the
fmxslt:create_session() extension function in an XSLT stylesheet. For information on the
fmxslt:create_session() extension function, see the FileMaker Server Advanced Custom Web Publishing
Guide. The maximum number of web sessions is limited only by the amount of memory on the Web
Publishing Engine host computer.
In the Administration Console, you can use the Database Sessions option to configure the interaction between
these two types of sessions. If you enable this option, the Web Publishing Engine uses a database session for
each web session. Otherwise, the Web Publishing Engine does not use database sessions. This option is
disabled by default.
There are trade-offs to enabling and disabling the Database Sessions option.
If you enable the Database Sessions option:
1 Global variable values are stored between requests.
1 If a script modifies a state, that state is maintained between requests. For example, privileges that are
modified by the Relogin script step to switch accounts will persist between requests.
1 The number of web sessions is limited to the maximum number of concurrent database sessions on
FileMaker Server.