Administrator’s Guide
Table Of Contents
- Preface Introducing FileMaker Pro 5.5 Unlimited
- Chapter 1 Installing the FileMaker Web Server Connector
- Chapter 2 Administering the Web Server Connector
- Chapter 3 Publishing your database on the Web
- Types of web publishing
- Using the FileMakerPro Web Companion
- Creating a custom home page
- Creating a custom home page for Instant Web Publishing
- Creating a custom web site using a database layout
- Web Companion support for Internet mediatypes
- Monitoring your site
- Exporting data to a static HTML page
- Testing your site without a networkconnection
- Opening password-protected databasesremotely
- Chapter 4 Custom web publishing using CDML
- About the CDML examples
- General steps for custom web publishing using CDML
- About CDML format files
- Generating FileMakerPro CGI requests using CDML
- Using the CDML Tool and templates
- Modified CDML tags
- About the CDML Reference database
- Creating error messages
- Using an encoding parameter with a CDML replacement tag
- Planning your web site
- Chapter 5 Using FileMakerPro XML to deliver your data
- About the XML examples
- General process for custom web publishing using XML
- Generating an XML document
- Using the FMPDSORESULT grammar
- Using the FileMakerPro Extended XMLgrammars
- About UTF-8 encoded data
- Generating FileMakerPro CGI requests for an XML document
- Using style sheets with your XMLdocument
- Comparing CSS, XSLT, and JavaScript
- Looking at the XML Inventory example
- Chapter 6 Using Java and JDBC to deliver your data
- About the JDBC examples
- About JDBC
- Using the FileMaker JDBC Driver
- SQL supported by the FileMaker JDBCDriver
- FileMakerPro support for Unicodecharacters
- About the FileMaker JDBC Driver interfaces and extensions
- Example 1: Looking at the FileMakerPro Explorer application
- Example 2: Creating the JBuilder Inventoryapplication
- Example 3: Creating the Visual Cafe Inventory application
- Using the FileMaker Java classes
- Appendix A Valid names used in CGI requests for FileMaker XML data
- Generating a –find, –findall, or –findany request
- Generating a –view request
- Generating a –new request
- Generating an –edit request
- Generating a –delete request
- Generating a –dbnames request
- Generating a –layoutnames request
- Generating a –scriptnames request
- Generating a –dbopen request
- Generating a –dbclose request
- Specifying parameters for the request
- –db (Database)
- –lay (Layout)
- –format (Format)
- –recid (Record ID)
- –modid (Modification ID)
- –lop (Logical operator)
- –op (Comparison operator)
- –max (Maximum records)
- –skip (Skip records)
- –sortfield (Sort field)
- –sortorder (Sort order)
- –script (Script)
- –script.prefind (Script before Find)
- –script.presort (Script before Sort)
- –styletype (Style type)
- –stylehref (Style href)
- –password (Database password)
- field name (Name of specific field)
- Appendix B FileMaker Pro values for error codes
- Appendix C Enabling the FileMaker Pro Web Companion in MacOS X
- Index
3-14 FileMaker Pro 5.5 Unlimited Administrator’s Guide
For example, you might want to serve WML (Wireless Markup
Language) documents from your web site. Browsers with the
appropriate plug-in would be able to display the file in the browser
window.
For information about the Internet media type registry, go to
ftp://ftp.iana.org/in-notes/iana/assignments/media-types/.
Monitoring your site
The FileMaker Pro Web Companion generates three types of log
files that you can use for gathering information about web users who
visit your site:
1 access.log
1 error.log
1 info.log
For information on enabling log files, see “Setting Web Companion
configuration options” on page 3-3.
In addition, the Web Companion provides several external functions
for monitoring activity with your databases, which can be used in
your calculation fields and scripts.
Note For information about the log files generated by the Web Server
Connector, see “Using the Web Server Connector log files” on
page 2-5.
Using the access.log file
The access.log file keeps a record of every time someone accesses
the Web Companion from a web browser and lists the hits in NCSA/
CERN-compatible Common Log Format.
When you enable the Access Log File option in the Web Companion
Configuration dialog box, the Web Companion generates an
access.log file and places it in the root level of the FileMaker Pro
folder.
Every time a web user accesses your database, the Web Companion
continuously adds entries to the access.log file.
Note Neither the entries nor the file are automatically deleted, and so
the file may become very large. To save hard disk space on your host
computer, consider archiving the access.log file on a regular
schedule.
The Common Log Format used for the access.log file is:
remotehost rfc931 authuser [date] “request” status bytes
Where Means this
remotehost The remote IP address or hostname
rfc931 Required for UNIX systems
authuser The user name authenticated by the web user
[date] The date and time of the request