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
10 Custom Web Publishing Guide
About this guide
This guide assumes you are experienced with XML and XSLT, developing web sites, and using FileMaker Pro
to create databases. This guide provides the following information about Custom Web Publishing with XML
and XSLT on FileMaker Server:
1 what is required to develop a Custom Web Publishing solution using XML or XSLT
1 how to publish your databases using XML or XSLT
1 what web users need to access a Custom Web Publishing solution
1 how to obtain XML data from databases hosted by FileMaker Server
1 how to develop FileMaker XSLT stylesheets
1 how to convert CDML solutions to FileMaker XSLT
Important You can download PDFs of FileMaker 7 documentation from www.filemaker.com. Any updates to
this document are also available from the web site.
The documentation for FileMaker Server also includes the following additional information:
Creating dynamic web sites 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 web sites and
applications.
1 Data integration: By using FileMaker XSLT stylesheets, you can integrate any subset of the FileMaker
data into other web sites and with other middleware and custom applications. You can make the data look
like it belongs to another web site instead of displaying an entire FileMaker layout in the web browser.
1 Security: As the administrator for the Web Publishing Engine, you 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 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.
For information about See
Installing and configuring Instant Web Publishing and
Custom Web Publishing with XML and XSLT for FileMaker
Server
FileMaker Server Advanced Web Publishing
Installation Guide
Installing and configuring FileMaker Server FileMaker Server Administrator’s Guide
FileMaker Server Administration Help
Instant Web Publishing FileMaker Instant Web Publishing Guide
Security guidelines for web publishing FileMaker Security Guide
Publishing files from previous versions of FileMaker Pro Converting FileMaker Databases from Previous
Versions