Custom Web Publishing Guide
Table Of Contents
- Chapter 1 Introducing Custom Web Publishing
- Chapter 2 Preparing databases for Custom Web Publishing
- Chapter 3 Accessing XML data with the Web Publishing Engine
- Using Custom Web Publishing with XML
- General process for accessing XML data from the Web Publishing Engine
- About the URL syntax for XML data and container objects
- Accessing XML data via the Web Publishing Engine
- Using the fmresultset grammar
- Using other FileMaker XML grammars
- About UTF-8 encoded data
- Using FileMaker query strings to request XML data
- Switching layouts for an XML response
- Understanding how an XML request is processed
- Using server-side and client-side processing of stylesheets
- Troubleshooting XML document access
- Chapter 4 Introduction to Custom Web Publishing with XSLT
- Chapter 5 Developing FileMaker XSLT stylesheets
- Using XSLT stylesheets with the Web Publishing Engine
- About the FileMaker XSLT Extension Function Reference
- About the URL syntax for FileMaker XSLT stylesheets
- About the URL syntax for FileMaker container objects in XSLT solutions
- Using query strings in FileMaker XSLT stylesheets
- Specifying an XML grammar for a FileMaker XSLT stylesheet
- About namespaces and prefixes for FileMaker XSLT stylesheets
- Using statically defined query commands and query parameters
- Setting text encoding for requests
- Specifying an output method and encoding
- About the encoding of XSLT stylesheets
- Processing XSLT requests that do not query FileMaker Server
- Using tokens to pass information between stylesheets
- Using the FileMaker XSLT extension functions and parameters
- About the FileMaker-specific XSLT parameters set by the Web Publishing Engine
- Accessing the query information in a request
- Obtaining client information
- Using the Web Publishing Engine base URI parameter
- Using the authenticated base URI parameter
- Loading additional documents
- Using a database’s layout information in a stylesheet
- Using content buffering
- Using Web Publishing Engine sessions to store information between requests
- Using the session extension functions
- Sending email messages from the Web Publishing Engine
- Using the header functions
- Using the cookie extension functions
- Using the string manipulation extension functions
- Comparing strings using Perl 5 regular expressions
- Checking for values in a field formatted as a checkbox
- Using the date, time, and day extension functions
- Checking the error status of extension functions
- Using logging
- Chapter 6 Testing and monitoring a site
- Appendix A Valid names used in query strings
- About the query commands and parameters
- Using the query commands
- -dbnames (Database names) query command
- -delete (Delete record) query command
- -dup (Duplicate record) query command
- -edit (Edit record) query command
- -find, -findall, or -findany (Find records) query commands
- -layoutnames (Layout names) query command
- -new (New record) query command
- -process (Process XSLT stylesheets)
- -scriptnames (Script names) query command
- -view (View layout information) query command
- Using the query parameters
- -db (Database name) query parameter
- -encoding (Encoding XSLT request) query parameter
- -field (Container field name) query parameter
- fieldname (Non-container field name) query parameter
- fieldname.op (Comparison operator) query parameter
- -grammar (Grammar for XSLT stylesheets) query parameter
- -lay (Layout) query parameter
- -lay.response (Switch layout for response) query parameter
- -lop (Logical operator) query parameter
- -max (Maximum records) query parameter
- -modid (Modification ID) query parameter
- -recid (Record ID) query parameter
- -script (Script) query parameter
- -script.prefind (Script before Find) query parameter
- -script.presort (Script before Sort) query parameter
- -skip (Skip records) query parameter
- -sortfield (Sort field) query parameter
- -sortorder (Sort order) query parameter
- -styletype (Style type) query parameter
- -stylehref (Style href) query parameter
- -token.[string] (Pass values between XSLT stylesheets) query parameter
- Appendix B Error codes for Custom Web Publishing
- Appendix C Converting CDML solutions to FileMaker XSLT
- About the process of converting CDML solutions to FileMaker XSLT solutions
- Conversion of CDML action tags, variable tags, and URLs
- Conversion of the -error and -errornum CDML variable tags
- Conversion of obsolete CDML action tags
- Conversion of supported CDML action tags
- Conversion of obsolete CDML variable tags
- Conversion of supported CDML variable tags
- Conversion of CDML boolean parameters to XPath boolean parameters
- Conversion of CDML boolean operators to XPath
- Conversion of CDML intratag parameters to XSLT-CWP
- Manually fixing CDML conversion errors
- Conversion of CDML replacement tags to XSLT-CWP
- Index
Testing and monitoring a site 73
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 5, “Developing FileMaker XSLT
stylesheets.”
The application log is named pe_application_log.txt and is located in the Logs folder in the Web Publishing
folder in the FileMaker Server 7 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:
1 Error Logging
1 Script Logging
1 User Logging
All three of these Logging options are enabled by default. For information on setting these options via the
Administration Console, see the FileMaker Server Advanced Web Publishing Installation Guide.
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, consider archiving 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 is a record of any errors with its operation. This file is called web_server_module_log.txt and is
located in the Logs folder in the Web Publishing folder in the FileMaker Server 7 folder on the web server host.
Using Web Publishing Core internal access logs
The Web Publishing Core software component of the Web Publishing Engine generates two internal access
log files that are a record of each time the Web Publishing Core is accessed:
1 The wpc_access_log.txt access log is a record of all end-user requests to generate XML and to use
FileMaker Server Instant Web Publishing. These requests are routed from the web server directly to the
Web Publishing Core.
1 The pe_internal_access_log.txt access log is a record of all internal XML requests that the XSLT-CWP
software component of the Web Publishing Engine makes while processing XSLT requests. These requests
are routed internally within the Web Publishing Engine from the XSLT-CWP software component to the
Web Publishing Core software component.
These log files are located in the Logs folder in the Web Publishing folder in the FileMaker Server 7 folder on
the Web Publishing Engine host.