Developer’s Guide
Table Of Contents
- Contents
- Chapter 1 Introducing FileMaker Developer 5
- Chapter 2 Customizing your database solution
- About the custom solution examples
- Using the FileMaker Developer Tool
- Binding your databases into a runtime database solution
- Displaying databases in Kiosk mode
- Renaming your databases
- Removing design access to your databases
- Customizing the About, Help, and Scriptsmenus
- Adding the FileMakerPro extension to database filenames
- Saving your settings in the Developer Tool
- Chapter 3 Preparing files for a custom solution
- About the Relational Example
- General steps for preparing your solutionfiles
- Issues to consider before creating a runtime database solution
- Opening files in Kiosk mode
- Design tips for navigating in Kiosk mode
- Creating startup scripts
- Using button image samples
- Documenting your database solution
- Design tips for cross-platform solutions
- Creating a consistent appearance
- Simulating outline and shadow text styles
- Using common character sets
- Designing text layouts for cross-platform solutions
- Using a common color palette
- Using graphics in cross-platform solutions
- Using QuickTime movies in cross-platform solutions
- Showing the status bar in Windows
- Using separate scripts for printing
- Using the Status (CurrentPlatform) function
- Creating platform-specific scripts
- Protecting your runtime database solutionfiles
- Testing before and after creating yoursolution
- Converting and upgrading solution files
- Chapter 4 Distributing FileMakerPro runtime database solutions
- Chapter 5 Creating custom layout themes
- Chapter 6 Publishing your database on the Web
- Moving forward using open web standards
- Using the FileMakerPro Web Companion
- Displaying a custom home page
- Using a custom home page with Instant Web Publishing
- Monitoring your site
- Exporting data to a static HTML page
- Testing your site without a networkconnection
- Opening password-protected databasesremotely
- Using the Web Security Database
- Chapter 7 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 8 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
- Chapter 9 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
- New and 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 10 Writing external function plug-ins
- About the plug-in examples and templates
- Installing, enabling, and configuring FileMakerPro plug-ins
- Using external functions in a calculation
- Requirements for writing an external function plug-in
- FileMakerPro messages sent to theplugin
- Debugging your plug-in
- Avoiding potential MacOS resourceconflicts
- Providing documentation for your plug-in
- Naming and registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMakerPro
- Appendix B 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 C FileMaker Pro values for error codes
- Index
Publishing your database on the Web
6-9
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.
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. 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
Using the error.log file
The error.log file, stored in the root level of the folder containing the
database, is generated by the Web Companion whenever any unusual
errors have occurred. Common errors reported to the web user, such
as “Database not open,” are not recorded in the error.log file.
[08/Jun/1999:16:16:01:53 –0800] Web Security database not open.
Security disabled.
[12/Jul/1999:06:07:02 –0800] ERROR: 6. Could not find email format file.
[23/Jul/1999:11:12:38 –0800] ERROR: 12: Badly formatted URL.
Using the info.log file
The info.log file, stored in the root level of the folder for the
database, contains entries generated by the [FMP-Log] CDML
replacement tag. Whenever web users access FileMaker Pro from
your custom CDML web page, information you’ve included within
a [FMP-Log] tag is recorded by the Web Companion in the info.log
file.
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
“request” The request line exactly as it came from the client
status The HTTP status code returned to the client (for information,
see the World Wide Web Consortium’s web site at
www.w3c.org)
bytes The content length of the document transferred to the client