FileMaker and the Web

On this page:

Note: The information on this page is accurate for FileMaker 17. Certain features and settings may either not apply to, or differ from, prior versions.

Dynamic FileMaker websites

FileMaker has three native methods described below for dynamic site hosting: WebDirect, Custom Web Publishing, and the FileMaker Data API. Note that at MIT, our volume license for FileMaker Server allows for the use of WebDirect in restricted situations only and never where unknown users (annonymous users) would be able to connect. Anyone interested in using WebDirect should contact filemaker-support@mit.edu to inquire about options for hosting solutions for wider access before development starts. While neither WebDirect nor Custom Web Publishing are fully supported at MIT, they may be appropriate for web applications that do not publish sensitive data. Please take special note of the Security section below.

WebDirect (WD)

FileMaker introduced WebDirect with version 13. This technology makes it possible to turn a native FileMaker solution into web application with no additional web development necessary. Technically, all that is required to make a database readable and writeable over the web are a few configuration changes to the hosting FileMaker Server and the creation of web-specific user privilege sets in the hosted solution. In practice, there are many things to consider before you would want to allow others to access your database via WD. First and foremost is security, since users can be granted privileges that will let them read, edit, create and delete records. Controlling what data, layouts and menu commands a user can access via WD is entirely managed at the privilege set level. Without careful consideration, poorly restricted privilege sets and poorly designed user interfaces can leave a web-enabled database fairly exposed. Further, although WD can render layouts in a browser with a great degree of visual fidelity, it is important to design the web-facing user interface around dedicated layouts that function predictably in the web environment. Note that not all FileMaker features are supported in WebDirect.

Note: See Licensing Considerations below for important information on the use of WebDirect at MIT.

FileMaker Data API

With release of FileMaker 17 the FM Data API v1 the trial version introduced with FM 16 has been deprecated.   The FM Data API is a robust REST API for delivering FileMaker data as a web service as well as for other purposes.  There are security considerations to consider when setting up a hosted file, making FM data available via the FM Data API, but for those with their own web sites, connectivity to FM via the Data API is a viable, cost-effective integration option.  

Note: See Licensing Considerations below for important information on the use of the Data API in version 17.

Custom Web Publishing (CWP)

FileMaker Server comes packaged with two built-in technologies for hosting websites: an XSLT publishing engine and an API for PHP. With XSLT, you can develop XML-based sites, using XSL style sheets to create fairly complex dynamic websites. Alternatively, you can develop dynamic websites using the widely accepted PHP scripting language in conjunction with the FileMaker-specific classes that are available through the FileMaker Server deployment assistant.

Security

Although IS&T does not provide full support to users wishing to employ any of these tools, there are some recommended guidelines for doing so in the MIT environment. When developing websites with database backends, great care must be paid to security, e.g., appropriate server configuration, authorization, and authentication issues.

• Only dedicated privilege sets with the narrowest permissions required should be created for use with WebDirect.
• If using web publishing with solutions that contain sensitive data, extreme care should be taken with the implementation of user accounts and privilege sets such that the sensitive data is never exposed to the web.

Licensing Considerations

Anyone using or considering one of these technologies is advised to plan for costs associated with any connectivity licensing requirements and/or costs for ancillary web hosting or development services. This is especially important to know and plan for prior to starting any new development project.

In particular:

• MIT's volume license for FileMaker Server allows for WebDirect or FileMaker Go connectivity only in cases where those accessing the files qualify for to download the MIT licensed FM client software (limited to students and staff). For more information, please consult WebDirect and FileMaker Go Licensing at MIT.
• The Data API as of release of FileMaker Server 17 (v1) is available for use with MIT licensed copies of FileMaker Advanced and FileMaker Server 17.  There are no restrictions on how the data is disseminated.  There are limits on total volume of data that the MIT licenses in aggregate can transmit before fees are incurred.  At this time we do not anticipate that the volume of data will exceed our annual data limits.

Static FileMaker websites

Overview

FileMaker can be used to generate static html pages that are then moved to a (non-FileMaker) web server or Athena locker for hosting.

A static site approach is appropriate under any of these conditions:

• Your site does not require interaction between the data and your site visitors, e.g., querying or updating
• Your site content does not change often
• Your site is housed on an IS&T managed server or in an Athena Locker

Note: Examples of data that often appear in FileMaker databases but should almost never appear on the web include student or staff data that goes beyond basic directory information.

Generating static pages

There are several approaches for generating web pages from FileMaker. These pages can then be uploaded to any Athena locker or MIT web server. Any time you want to change the web page content, you must make the change in the database, then generate and upload the new page. Do not bypass FileMaker and edit the page directly, or your changes will be lost at the next generation of that page.

• Exporting records in JSON format would create data that could easily be integrated into a web page displaying static data.  FileMaker now includes JSON formatting functions that will parse FM data appropriately.
• Exporting records as html tables creates a data table containing specified fields; no style is associated with the exported file, but html code pasted into a website template can be custom formatted (tags are uppercase and therefore not xhtml compliant)
• Exporting records in xml format is bare-bones unless transformed with an xsl stylesheet during export to create an attractive page; style sheet may reside locally or may be called with an URL
• Saving records as PDF files is appropriate only for certain publications; this method is not compliant with accessibility standards unless used in accordance with accessibility guidelines