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
Chapter 2
About Custom Web Publishing with XML and XSLT
Creating dynamic websites with the Web Publishing Engine
The Web Publishing Engine provides Custom Web Publishing for FileMaker Server using XML data
publishing and server-processed XSLT stylesheets. Custom Web Publishing provides several benefits:
1 Customization: You can determine how web users interact with FileMaker data, and how the data
displays in web browsers.
1 Data interchange: By using FileMaker XML, you can exchange FileMaker data with other websites and
applications.
1 Data integration: By using FileMaker XSLT stylesheets, you can integrate FileMaker data into other
websites, with other middleware, and with custom applications. You can make the data look like it
belongs to another website instead of displaying an entire FileMaker layout in the web browser.
1 Security: The FileMaker Server administrator can individually enable or disable Instant Web Publishing,
XML web publishing, or XSLT web publishing for all databases hosted by the server. As the FileMaker
database owner, you can control web user access to Instant Web Publishing, XML web publishing, or
XSLT web publishing for each database.
1 Server-side stylesheets: Server-side XSLT stylesheet processing prevents unauthorized examination of
confidential database information that might otherwise be possible with client-side stylesheets.
1 Control and filtering of published data: By using XSLT stylesheets, you can control and filter the data
and the type of database information you want to publish, which prevents unauthorized use of the
database. You can also hide metadata, such as database and field names.
1 Based on open standards: You have more access to tools, resources and skilled personnel for Custom
Web Publishing solutions. If you know standard XML or XSLT, then you can immediately start
developing solutions after learning a few unique details about Custom Web Publishing with XML, such
as the URL syntax and query parameters to use.
About Custom Web Publishing with XML
Custom Web Publishing with XML allows you to retrieve data from FileMaker databases, and easily use
the data in other output formats. By using an HTTP request with the appropriate query commands and
parameters, you can retrieve FileMaker data as an XML document. You can then use the XML data in other
applications, or apply an XSLT stylesheet to the XML data. See
chapter 4, “Accessing XML data with the
Web Publishing Engine.”
About Custom Web Publishing with XSLT
Custom Web Publishing with XSLT provides the ability to transform, filter, or format XML data for use in
a web browser or in other applications. You can use an XSLT stylesheet to transform the data between a
FileMaker XML grammar and another XML grammar for use in another application or database. You can
filter the data by controlling which database fields are published by the stylesheet. You can format how the
data is presented in a web page, and control how the web user interacts with the data. See
chapter 5,
“Introduction to Custom Web Publishing with XSLT.”