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
- Using server-side processing of scripting languages
- 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.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
- 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
Chapter 1
Introducing Custom Web Publishing
With FileMaker
®
Server Advanced, you can publish FileMaker databases on the Internet or an intranet in
these ways:
1 Custom Web Publishing using Extensible Markup Language (XML)
1 Custom Web Publishing using Extensible Stylesheet Language Transformations (XSLT) stylesheets
1 Instant Web Publishing. See the FileMaker Instant Web Publishing Guide.
Custom Web Publishing with XML and XSLT gives you choices and control over the design and
functionality of your web pages. FileMaker Server, which hosts the published databases, does not require
FileMaker
Pro to be installed or running for Custom Web Publishing to be available.
To support Instant Web Publishing and Custom Web Publishing with XML and XSLT, FileMaker Server
uses a set of software components called the FileMaker Server Web Publishing Engine. The Web Publishing
Engine handles interactions between a web user’s browser, your web server, and FileMaker
Server. The Web
Publishing Engine functions as an XSLT processor and provides output as HTML, XML, or text (such as
vCards) to the web server, which then provides the output to the web browser.
Web users access your Custom Web Publishing solution either by clicking an HREF link or entering a
Uniform Resource Locator (URL) that specifies the web server address and a FileMaker query string
request. The URL can either access XML data or reference an XSLT stylesheet. The Web Publishing Engine
returns the XML data specified in the query string request, or the results of the referenced XSLT stylesheet.
Important Security is increasingly important when you publish data on the web. Review the security
guidelines in the FileMaker Security Guide, available at www.filemaker.com/downloads.
Web
Browser
Customers.fp7
FileMaker Server
Products.fp7
FileMaker Server
Web Publishing
Engine
1. XML or XSLT
request is sent from
web browser or
program to web
server.
2. Web server routes
request to Web
Publishing Engine.
3. Web Publishing Engine
requests data from
database hosted by
FileMaker Server.
6. Web server sends
output to web browser
or program.
5. Web Publishing Engine converts
FileMaker data to XML data.
For XML requests, the Web Publishing
Engine sends the XML data directly to the
web server.
For XSLT requests, the Web Publishing
Engine uses an XSLT stylesheet to format
or transform the XML data, and generates
output as HTML pages, an XML document,
or text to web server.
4. FileMaker Server
sends requested
FileMaker data to
the Web Publishing
Engine.
Using the FileMaker Server Web Publishing Engine for Custom Web Publishing with XML or XSLT
Web Server
Web Server Module
Administration Console