Tim Dietrich

Custom Software Developer

Home Services Portfolio Blog About Contact Newsletter

FileMaker Server 13 On Mac OS X Mavericks (10.9)

This morning I installed FileMaker Server 13 on a Mac running OS X Mavericks (10.9). My goal was to test the next version of FMWebFrame by running a Web site directly on the same machine that FMS is running on. I would never do this myself - I've always preferred to run FMS on a dedicated machine, and Web sites elsewhere. However, someone that is interested in FMWebFrame recently contacted me, and he's having problems getting it installed on his FMS machine. So I thought I would give it a try.

Here are some notes that I took while working on this.

FileMaker Server really does install its own instance of Apache. I've seen a number of posts about this, and there seems to be confusion about whether it does or doesn't install a second Apache instance. It clearly does.

It is also worth noting that, during installation, FileMaker will disable any sites that had previously been configured on OS X's Apache instance if they are running on ports 80 and 443. FileMaker needs those ports, so this makes sense.

You cannot control FileMaker's Apache instance from the OS X "Server" application. However, you can stop and start FileMaker's Apache instance from the command line, like this:

  • sudo launchctl stop com.filemaker.fms
  • sudo launchctl start com.filemaker.fms

It is possible to run OS X's Apache instance and FileMaker's Apache instance side-by-side, as long as the ports that the Web sites are running on don't conflict.

The web root for FileMaker's Apache instance is:

/Library/FileMaker Server/HTTPServer/htdocs

In that folder, there are a few interesting files and sub-folders:

  • fmwebd_home.html: WebDirect's home page.
  • index.html: The "FileMaker Database Server Website" index page.
  • httpsRoot: A subfolder that "https" requests resolve to.

Again, my preference - and my strong recommendation - is that you truly dedicate a machine for FileMaker Server. I know that there are some developers who host FMS and other services (mail, Web, etc) on the same machine. However, my experience has been that FMS will give better performance, and will be easier to maintain, if you give it its own machine.

As a side note, I never was able to get an FMWebFrame-based site running on the FMS machine. I suspect that it is possible, but I grew frustrated when trying to setup a Web site running on a non-standard port using OS X's Apache instance.