Help
Table Of Contents
- FileMaker Server 9 Help
- About FileMaker Server
- New features in FileMaker Server 9
- Deploying FileMaker Server
- Starting Admin Console
- Hosting databases
- Hosting websites
- Starting and stopping FileMaker Server
- Configuring general settings
- Configuring Database Server settings
- Configuring web publishing settings
- Administering clients
- Administering databases
- Using ODBC and JDBC with FileMaker Server
- Monitoring FileMaker Server
- Managing plug-ins
- Securing your data
- Scheduling administrative tasks
- Troubleshooting
- Checking for updates
- About the license key
- Command line reference
- Glossary
- Registration
- Customer support and Knowledge Base
- Copyright information
Configuring web publishing settings XSLT web publishing settings
F
ILEMAKER SERVER 9 HELP 85
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:
• 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.
• 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 F
ILEMAKER SERVER CUSTOM
W
EB PUBLISHING WITH XML AND XSLT on the Start Page. The maximum number of web
sessions is limited only by the amount of memory on the Web Publishing Engine machine.
In Admin Console, you can use the Enable 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 uses a database
session for each request. This option is disabled by default.
If you enable the database sessions:
• Global values are stored between requests.
• If a ScriptMaker
script modifies a state, that state is maintained between requests. For
example, privileges that are modified by the Re-Login script step to switch accounts persist
between requests.
• The total number of web sessions is limited to the maximum number of concurrent web
database sessions on FileMaker Server. This limit applies to Instant Web Publishing
sessions and XSLT sessions.
If you disable the database sessions:
• Global values are not stored between requests.
• If a script modifies a state, that state is not maintained between requests.
• The number of XSLT web sessions is not limited to the maximum number of web database
sessions on FileMaker Server, which allows greater scalability to Custom Web Publishing.
However, Instant Web Publishing sessions are still subject to the limit.
If your stylesheets do not use global values or scripts that require a state to be maintained between
requests, you should disable database sessions. The setting for the Enable database sessions
option applies to all stylesheets deployed on the Web Publishing Engine.
Related topic
XSLT web publishing settings (page 82)