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
12 Custom Web Publishing Guide
Web publishing requirements
What is required to publish a database using Custom Web Publishing
To publish databases using Custom Web Publishing with XML or XSLT, the following are required:
1 a Windows- or Mac OS X-based computer running FileMaker Server, enabled for Custom Web Publishing
1 one or more FileMaker Pro databases hosted by FileMaker Server
1 the FileMaker Server Web Publishing Engine, installed and configured
1 a web server, either Microsoft IIS on Windows or Apache on Mac OS X
1 the IP address or domain name of the host running the web server
1 any web browser and access to the web server to develop and test your Custom Web Publishing solution
What web users need to access a Custom Web Publishing solution
To access a Custom Web Publishing solution that uses XML or XSLT, web users need:
1 any web browser software
1 access to the Internet or an intranet and the web server
1 the IP address or domain name of the host running the web server
1 if the database is password-protected, web users must also enter a user name and password for a database
account
Connecting to the Internet or an intranet
When you publish databases on the Internet or an intranet, the host computer must be running
FileMaker Server, and the databases you want to share must be hosted and available. In addition:
1 It is strongly recommended that you publish your database on a computer with a full-time Internet or
intranet connection. You can publish databases without a full-time connection, but they are only available
to users when your computer is connected to the Internet or an intranet.
1 The host computer for the Web Publishing Engine must have a dedicated static (permanent) IP address or
a domain name. If you connect to the Internet with an Internet service provider (ISP), your IP address might
be
dynamically allocated (it is different each time you connect). A dynamic IP address makes it more
difficult for users to locate your databases. If you are not sure of the type of access available to you, consult
your ISP or network administrator.
New features in Custom Web Publishing with XML and XSLT
Custom Web Publishing with XML and XSLT provides several important new features:
1 Databases are hosted on FileMaker Server, and FileMaker Pro is not required to be running.
1 You can now use server-side XSLT stylesheet processing, which is more secure than client-side stylesheet
processing.
1 You can prevent the unauthorized use of query commands and query parameters with your FileMaker
XSLT stylesheet by statically defining the query commands, parameters, and values that you want to use
when XML data is requested. See
“Using statically defined query commands and query parameters” on
page 51.