Custom Web Publishing with XML and XSLT

84 FileMaker Server Custom Web Publishing with XML and XSLT
Using the web server access and error logs
Apache (Mac OS): The Apache web server generates an access log file and an error log file. The Apache access log
file, which is in the W3C Common Logfile Format by default, is a record of all incoming HTTP requests to the web
server. The Apache error log is a record of problems involving processing HTTP requests. For more information on
these log files, see the documentation for the Apache web server.
IIS (Windows): The Microsoft IIS web server generates an access log file and displays errors in the Windows Event
Viewer instead of writing them to a log file. The access log file, which is in the W3C Extended Log File Format by
default, is a record of all incoming HTTP requests to the web server. You can also use the W3C Common Logfile
Format for the access log. For more information, see the documentation for the Microsoft IIS web server.
For information on the W3C Common Logfile Format and the W3C Extended Log File Format, see the World Wide
Web Consortium website at www.w3.org.
Using the Web Publishing Engine application log
By default, the Web Publishing Engine generates an application log file that is a record of Web Publishing Engine
error, script, and user log information.
1 The error log information describes any unusual Web Publishing Engine errors that have occurred. Common
errors reported to the web user, such as “Database not open,” are not recorded.
1 The script log information describes any errors generated when web users execute scripts. For example, it lists
script steps that are skipped if they’re not web-compatible.
1 The user log messages contains messages generated by the XSLT <xsl:message> element in XSLT stylesheets.
Whenever web users access your XSLT stylesheet, information you’ve included within a <xsl:message> element
is recorded in the application log file. See
chapter 6, “Developing FileMaker XSLT stylesheets.”
The application log is named pe_application_log.txt and is located in the Logs folder in the FileMaker Server folder on
the Web Publishing Engine host.
The pe_application_log.txt file is generated if any of the following Logging options are enabled in the Web Publishing
Engine.
All three of these Logging options are enabled by default. For information on setting these options via the Admin
Console, see FileMaker
Server Help.
Note The entries in the application log are not automatically deleted, and over time the file may become very large.
To save hard disk space on your host computer, archive the application log file on a regular basis.
Using the Web Server Module error log
If the web server is unable to connect to the Web Publishing Engine, the Web Server Module generates a log file
that records any errors with its operation. This file is called web_server_module_log.txt and is located in the Logs
folder in the FileMaker Server folder on the web server host.
Logging option enabled Information recorded in pe_application_log.txt
Error Logging Any unusual Web Publishing Engine errors that have occurred. Common errors
reported to the web user, such as “Database not open,” are not recorded.
Script Logging Any errors generated when web users execute scripts. For example, it lists script
steps that are skipped if they’re not web-compatible.
User Logging Messages generated whenever web users access your Custom Web Publishing solution.