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
46 FileMaker Server Custom Web Publishing with XML and XSLT
Using FileMaker XSLT Site Assistant to generate FileMaker XSLT stylesheets
FileMaker XSLT Site Assistant is an application you can use to create basic XSLT stylesheets as a starting
point for use with Custom Web Publishing with XSLT. XSLT Site Assistant is a good way to learn how
FileMaker XSLT stylesheets are constructed. You can then use your own XSLT stylesheet authoring or text
editing tools to modify the stylesheets as necessary. You cannot use XSLT Site Assistant to edit or update
existing stylesheets, but you can use XSLT Site Assistant to generate the initial stylesheets for an entire site,
or a single stylesheet to add basic functionality (such as deleting records) to an existing site.
You can use XSLT Site Assistant to generate XSLT stylesheets for all of the types of pages that are useful
for working with FileMaker databases via Custom Web Publishing. Depending on the options you choose
in XSLT Site Assistant, you can create a site that allows users to:
1 browse a single record at a time
1 view a list of all the records in the database
1 search the database and view the results in a list
1 sort records
1 add records
1 edit and duplicate records
1 delete records
1 view a summary report
You can also generate an optional home page that is linked to the other generated XSLT stylesheet pages.
The Web Publishing Engine uses each of your stylesheets to dynamically obtain data from a FileMaker
database whenever a web user sends an HTTP request and a URL that references one of your XSLT
stylesheets. The Web Publishing Engine uses a stylesheet to transform and format the XML data, and
generates the resulting HTML page that the web user can work with.
Note The XSLT Site Assistant stylesheets transform FileMaker XML data into HTML pages based on the
fmresultset XML grammar, which makes the stylesheets incompatible with other uses of XML
data such as
FileMaker Pro XML
export.
Before using XSLT Site Assistant
Before you can use XSLT Site Assistant to generate XSLT stylesheets for a database:
1 Set the extended privilege fmxslt in the database. Use privilege sets when running XSLT Site Assistant
that are equivalent to those you give to web users. See
“Enabling Custom Web Publishing in a database”
on page 19.
1 Open and host the database on the Database Server component of FileMaker Server. See
FileMaker
Server Help.
1 Be sure the web server component of the FileMaker Server deployment is running.
1 Be sure the Web Publishing Engine component of the FileMaker server deployment is running.
1 Enable XSLT Publishing in the Web Publishing Engine for using and testing the XSLT stylesheets. See
FileMaker
Server Help.