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 5
|
Introduction to Custom Web Publishing with XSLT 47
Starting XSLT Site Assistant
Note To use XSLT Site Assistant, you must have Java Runtime Environment 5 or Java Runtime
Environment 6 installed.
To start XSLT Site Assistant:
1. Open a browser to the FileMaker Server Web Publishing Tools page.
Go to the following URL:
http://<server>:16000/tools
Where <server> is the machine on which the FileMaker Server resides.
2. Click PHP Site Assistant and XSLT Site Assistant Tools to go to the FileMaker Server Web Publishing Tools page.
3. Click Start XSLT Site Assistant.
FileMaker Server installs the required JAR files on your local machine, displaying a progress dialog until
the procedure is complete.
4. (Optional) After the files are installed, you may select whether to install an icon for XSLT Site Assistant
on your desktop. Click OK to install the icon.
You can now begin using XSLT Site Assistant.
Using XSLT Site Assistant
For detailed information and step-by-step procedures for using XSLT Site Assistant, see XSLT Site
Assistant Help. For information about using the XSLT Site Assistant’s generated stylesheets, see
“Using
FileMaker XSLT stylesheets in a website or program” on page 48.
Important When using XSLT Site Assistant, if you select a database that contains multiple tables, be sure
to select layouts that are associated with the same table or else the generated site will return unexpected
results. For example, a database might contain a Products table and a Customers table. When you select the
layouts for a search page, an edit records page, and an add records page, be sure the layouts are all associated
with the same table.
About XSLT Site Assistant’s generated stylesheets
The XSLT stylesheets generated by XSLT Site Assistant include several FileMaker-specific processing
instructions, elements, and parameters. Here are a few examples of what is included:
1 The <?xslt-cwp-query params="query string-fragment"?> processing instruction specifies the XML grammar
to use and statically defines the name of the database you chose in XSLT Site Assistant. See
“Using
statically defined query commands and query parameters” on page 55.
1 The <xsl:param name="request-query"/> element is used to access query information in a request or HTML
form data. For example, this element can be used in the XSLT Site Assistant stylesheets to access the
current request query information to determine the current location in a found set of records and to create
links to the previous and next record. See
“Accessing the query information in a request” on page 59.
1 The <xsl:param name="authenticated-xml-base-uri"/> element, which isn’t always included, is used to
access the authenticated base URI in a request when more XML data is needed within the request. See
“Using the authenticated base URI parameter” on page 61.