Custom Web Publishing with XML and XSLT
Table Of Contents
- Preface
- Chapter 1 Introducing Custom Web Publishing
- Chapter 2 About Custom Web Publishing with XML and XSLT
- Chapter 3 Preparing databases for Custom Web Publishing
- Chapter 4 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 fmsresultset 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 5 Introduction to Custom Web Publishing with XSLT
- Chapter 6 Developing FileMaker XSLT stylesheets
- Using XSLT stylesheets with the Web Publishing Engine
- About the FileMaker XSLT Extension Function Reference
- About the FileMaker XSLT Starter Solution
- 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 the layout information for a database 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
- Using server-side processing of scripting languages
- Chapter 7 Staging, testing, and monitoring a site
- Appendix A Valid names used in query strings
- About the query commands and parameters
- Query command reference
- -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
- -findquery (Compound find) query command
- -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
- Query parameter reference
- -db (Database name) query parameter
- -delete.related (Portal records delete) 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
- -query (Compound find request) query parameter
- -recid (Record ID) query parameter
- -relatedsets.filter (Filter portal records) query parameter
- -relatedsets.max (Limit portal records) query parameter
- -script (Script) query parameter
- -script.param (Pass parameter to Script) query parameter
- -script.prefind (Script before Find) query parameter
- -script.prefind.param (Pass parameter to Script before Find) query parameter
- -script.presort (Script before Sort) query parameter
- -script.presort.param (Pass parameter to Script before Sort) query parameter
- -skip (Skip records) query parameter
- -sortfield (Sort field) query parameter
- -sortorder (Sort order) query parameter
- -stylehref (Style href) query parameter
- -styletype (Style type) query parameter
- -token.[string] (Pass values between XSLT stylesheets) query parameter
- Appendix B Error codes for Custom Web Publishing
- Index
44 FileMaker Server Custom Web Publishing with XML and XSLT
Getting started using Custom Web Publishing with XSLT
If you know standard XML and XSLT, then you can immediately start using the Web Publishing Engine
after learning a few unique details about FileMaker XML and XSLT publishing, such as how to use the
FileMaker XSLT extension functions and query commands and parameters. XSLT Site Assistant is a tool to
help you create stylesheets and learn how they are constructed. Then, you can use your favorite XML and
XSLT authoring tools to further enhance the stylesheets.
How the Web Publishing Engine generates pages based on XML data and XSLT stylesheets
After an XSLT Custom Web Publishing (XSLT-CWP) request is sent to the web server, the Web Publishing
Engine queries the FileMaker database based on the query commands and parameters that are defined in the
stylesheet and in the URL, and then outputs the data according to the instructions in the XSLT stylesheet.
Web
Browser
Web Server
Web Server Module
FileMaker Server Web
Publishing Engine
Custom Web Publishing
Engine (CWPE)
FileMaker
Database
Server
FileMaker Server Web
Publishing Engine
Web Publishing Core
Web Server
Web Server Module
Web
Browser
XSLT-CWP request is routed from web browser or program to FileMaker Database Server
1. XSLT-CWP
request is sent
from web
browser or
program to web
server.
2. Web server routes
XSLT-CWP request
to CWPE.
3. CWPE requests
XML data from
Web Publishing
Core based on
query command
and parameters.
4. Web Publishing
Core requests data
from database
hosted by FileMaker
Database Server.
Data is routed back from Database Server, and Web Publishing Engine uses XSLT stylesheet to transform and format data
8. Web server
sends output
to web
browser or
program.
7. CWPE uses XSLT
stylesheet to format or
transform XML data, and
sends output as HTML
pages, XML document,
or text to web server.
6. Web
Publishing Core
converts data to
XML and sends
it to CWPE.
5. FileMaker Database
Server sends requested
data to Web Publishing
Core.
Customers.fp7Products.fp7
Catalog.fp7Orders.fp7
Custom Web Publishing
Engine (CWPE)
Web Publishing Core