FileMaker - Web Based Applications

ITAG Standard #2: Web Based applications may be used but must follow additional web specific guidelines.

Static web sites with FileMaker data

There are several ways to generate static web pages from data or content stored in FileMaker. This is an acceptable way to use FileMaker-housed data on the web, provided all rules of privacy and security are being observed. Examples of data that often appear in FileMaker databases but should never appear on the web include any kind of student data, or staff data other than directory information.

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

• If your site does not require interaction between the data and your site visitors, e.g., querying/reporting, personalization
• If your site content does not change often
• If your site is housed in an Athena locker

Methods of generating static pages from FileMaker

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.

Generating web pages from FileMaker:

• You may export records as html tables. This will create a data table containing whichever fields you specified. There is no style associated with the exported file, but the html code may be pasted into a web site template to make it more attractive. The tags are uppercase and therefore not xhtml compliant.
• You may export records in xml format. This also is bare bones unless transformed with an xsl stylesheet during export to create an attractive page. The style sheet may reside locally or may be called with an URL.
• You may save records as PDF files. This is appropriate only for certain publications and is not compliant with accessibility standards unless used in accordance with guidelines. For more information, see http://web.mit.edu/atic/www/accessibility/developweb.html#pdf

Dynamic FileMaker Web Sites

FileMaker has two native methods for dynamic site hosting. Neither method is currently supported for use on the MIT network.

Instant Web Publishing (IWP): If you are running FileMaker Server Advanced, and have a server running IIS (Windows) or Apache (OS X), you may turn on Instant Web Publishing to make your database available over the web. While this approach simulates a thin client experience of the database, you should be aware that not all functionalities available through the normal server/client configuration are available to users accessing the system through IWP. Scripting, layout design, and most importantly, security must be carefully attended to during testing to ensure that the system functions properly when web-enabled. Due to its limited capabilities, IWP is not recommended for use on the MIT network.

Custom Web Publishing (CWP): As of v9, FileMaker Server comes packaged with two web technologies built-in: 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 web sites. Alternatively, you can develop dynamic web sites using the widely accepted php scripting language in conjunction with the FileMaker-specific classes that are available through the FileMaker Server deployment assistant.

As always when developing web sites with database backends, great care must be paid to security, e.g., appropriate 3-tier configuration, authorization, and authentication issues. While custom web publishing is not supported at MIT, it may be appropriate for web applications that do not publish or house sensitive data.