Web Publishing Installation Guide
Table Of Contents
- Chapter 1 Introduction
- About this guide
- Hardware and software requirements
- Windows requirements for the Web Publishing Engine
- Windows requirements for FileMaker Site Assistant and FileMaker CDML Converter tools
- Mac OS requirements for the Web Publishing Engine
- Mac OS requirements for FileMaker Site Assistant and FileMaker CDML Converter tools
- Important note about supported operating systems
- About the license key
- Customer support
- Overview of installing, configuring, and using the Web Publishing Engine
- Chapter 2 Installation quick start
- Chapter 3 Migrating web publishing settings from the previous version
- Chapter 4 Installing the Web Publishing Engine in various host configurations
- Chapter 5 Installing the Web Publishing Engine in Windows
- Chapter 6 Installing the Web Publishing Engine in Mac OS
- Chapter 7 Configuring the Web Publishing Engine
- About the Web Publishing Engine Administration Console
- General steps for configuring the Web Publishing Engine
- Configuring the Web Publishing Engine for the first time
- Viewing an overview of the Web Publishing Engine configuration
- Configuring Instant Web Publishing
- Disabling Custom Web Publishing with XML
- Configuring Custom Web Publishing with XSLT
- Setting the Web Publishing Engine mode
- Setting server-side XSLT stylesheet caching
- Configuring the interaction between web sessions and database sessions
- Configuring access to a mail server for the Web Publishing Engine
- Setting the default text encoding for XSLT requests
- Disabling Custom Web Publishing with XSLT
- Specifying general settings for the Web Publishing Engine
- Restricting access to the Administration Console
- Viewing a list of the published databases for FileMaker Server
- Logging out of the Administration Console
- Using the Web Publishing Engine and Administration Console services
- Changing the user name and password for the Administration Console
- Where to go from here
- Index
62 FileMaker Server Advanced Web Publishing Installation Guide
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 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 persist between requests.
1 The total number of web sessions is limited to the maximum number of concurrent web database sessions on
FileMaker Server. This limit applies both to IWP (instant web publishing) sessions and XSLT sessions.