FileMaker Server 13 Set-Up Instructions

IS&T recommends that IS&T-managed servers be used whenever possible for hosting FileMaker files at MIT. If you know you have a secure hosting environment and are experienced in hosting FileMaker database servers, here is a reminder of the important recommended settings at MIT:

• Do not enable ODBC/JDBC (This enables FileMaker to become a source for other databases)
• Do not enable web publishing unless you are setting up a dedicated server for web publishing
• Enable SSL

NOTE: The above list does not include all necessary settings but represents those for which MIT has specific recommendations.

Please follow all recommended MIT FileMaker Security Guidelines when setting up your server!

If you are uncertain of the process for setting up your server with the MIT recommendations, below is a step-by-step guide for configuring your server with our current recommended settings.

Basic Configuration

After installing FileMaker Server, you will be prompted to launch the Deployment Assistant.

1. In the Set Up Admin Console Account window, enter a User Name and Password for accessing the Admin Console, then click Next. The user name and password can be changed later through the Admin Console.
   Warning: For security reasons, do not use your Kerberos password or your Mac OS X administrator account password.
   
   
   
2. In the Identification section, enter a Server Name, Server Description, and Administrator Contact Information for your server, then click Next. This information will be visible to the users of the database at the Open Remote File dialog and at the Admin Console Start page.
   
   
   
3. In the Technologies section, under the ODBC/JDBC heading, select No, do not enable ODBC/JDBC.
   Note: Using a FileMaker database as a Data Source is not supported by IS&T at this time, but you may opt to enable this feature. Unless you plan to access your FileMaker database as a source via ODBC/JDBC, do not enable it.
   
   
   
4. Still in the Technologies section, under the Web Publishing heading, select No, do not enable Web Publishing, then click Next.
   Note: Unlike earlier versions, by default FileMaker Server 13 requires Web Services be enabled. In order for authorized server administrators to gain access to the HTML-based Admin Console service, Web Services must be enabled and Port 16000 must be open.  Enabling Web Services is not the same as enabling Web Publishing. The user will not see the Web Publishing and Web Services service settings in the Admin Console unless the Web Publishing feature has been enabled through the Deployment Assistant.  While 

IS&T does not provide help-desk support for use of the Web Publishing features, but if you choose to use Web Publishing, use should always be limited to publication of non-sensitive data and web enabled files should be located on a server where no FileMaker files with sensitive data reside. Please consult the MIT FileMaker Security Guidelines and the ITAG Infrastructure Requirements for Applications and Systems. To access the Web Publishing feature after you have installed FileMaker Server select Edit Deployment in the Server menu in the Admin Console.  

1. 
   Result: The Deployment Summary is displayed. Click Next.
   
   
   
2. Click Finish.
   Result: The FileMaker Server Admin Console opens, and displays the Status section.
   
   
   

   Additional Security Settings: Enable SSL Encryption and Use File Display Filter

To limit who can see your hosted files through the Open Remote command and enable SSL Encryption: 

1. In the left-hand column, select Database Server.
2. In the Database Server window, click the Security tab.
3. Check the option to "List only the databases each user is authorized to access.
4. To enable SSL encryption for communication between FM Server and FM Pro, Under Secure Connections, click to check the box for Require secure connections, then click Save.
5. For SSL encryption to take effect, you must stop and restart your server software (Be mindful of users who might be impacted by doing so!):
6. In the left navigation bar, select Status.
7. Click the icon in the upper-right to stop and restart the database server.

Signed Certificates

By default FileMaker uses unsigned 1024-bit certificates when communicating with FileMaker clients and Admin Console users. At MIT we recommend use of stronger 2048-bit signed certificates for FileMaker Server rather than the default unsigned 1024-bit certificates. See Installing Signed-Certificates for requesting and installing 2048-signed certificates for use with FileMaker Server.

Configuring Ports

To work with FileMaker Server  certain ports must be open and or available on your server machine in order for Server to communicate with various types of clients.  To see the recommended port settings at MIT and for FileMaker Server, see: FileMaker Server Port Settings.

Other Tasks

For more instructions on how to upload your databases, and create scheduled tasks to back them up, see Chapter 5 of the FileMaker Server 13 Getting Started Guide (PDF).

Important: FileMaker Server's backup feature creates a local copy of your databases, stored on the host machine. You should still use another mechanism, such as TSM, to back up those saved files to another secure location, in case of system failure.