FileMaker Server 18 Installation and Configuration Guide

FileMaker Server^® is a dedicated database server that hosts databases created using FileMaker Pro Advanced so that data can be shared and modified by FileMaker Pro Advanced, FileMaker Go^®, and FileMaker WebDirect^™ clients, and by other client applications supported by the FileMaker Server Web Publishing Engine and the FileMaker Data API Engine.

Before you install, confirm that your machines meet the minimum requirements. See the FileMaker Server system requirements.

FileMaker Server Admin Console is a web-based application that lets you configure and administer FileMaker Server. You can use Admin Console on machines that have network access to FileMaker Server and a supported web browser.

FileMaker Server supports the following client applications:

• FileMaker Pro Advanced versions 16, 17, and 18; and FileMaker Pro 16
• FileMaker Go 16, 17, and 18
• ODBC (Open Database Connectivity) and JDBC (Java Database Connectivity) client applications using the FileMaker client drivers. The FileMaker ODBC and JDBC drivers are available in the xDBC folder in the installation disk image and on the FileMaker downloads page. See FileMaker ODBC and JDBC Guide and FileMaker Pro Advanced Help.
• Web users accessing data via the FileMaker Server Web Publishing Engine using FileMaker WebDirect, Custom Web Publishing with PHP, and Custom Web Publishing with XML
• Web services or applications accessing data through the FileMaker Data API

Make sure users have applied the most recent update of their client software.

For additional information about supported clients and licensing requirements, see the FileMaker Server system requirements.

FileMaker Server uses a license certificate to set the license key. Do not lose this license certificate. Keep a copy of the license certificate in a safe place in case the software needs to be reinstalled.

You received an email message with a link to your software download page. Information about your license certificate is on that page.

The license certificate ensures adherence to the end user license agreement. If the license key is invalid or if too many installations of the software with that same license key are running on the network, the FileMaker Server software displays an error message.

• To install on a single machine, see Installation quick start (single-machine deployment).
• To install using a multiple-machine deployment, see Deploying FileMaker Server across multiple machines.
• To move from an existing installation of FileMaker Server, see Upgrading or moving an existing installation.

This section explains how to install FileMaker Server on a single machine. To install on more than one machine, see Deploying FileMaker Server across multiple machines.

• FileMaker Server requires a web server in all deployments. The web server serves web publishing clients, hosts the web-based Admin Console application, and handles some data transfer tasks. FileMaker Server requires that port 80 is available for web connections and port 443 is available for secure web connections. These ports are used by FileMaker Server even if web publishing is disabled. If the FileMaker Server installer detects existing websites using these ports, you must disable those websites and make the ports available.

  • Windows: The FileMaker Server installer enables the IIS web server if it isn’t already enabled, then runs the Microsoft Application Request Routing (ARR) installer, creates its own website in IIS, and configures the website to use the ports specified for web connections.
  • macOS: The web server included in macOS does not need to be enabled. If it is enabled, ensure that no existing website uses port 80 or 443. The installer creates a separate web server instance and enables it for FileMaker Server to use on these ports.

  See Setting up the web server.

• In the server computer's firewall, open the necessary ports so that FileMaker Server can communicate with administrators and clients:

  • The web connections port, port 80. This port is used by Admin Console and for web publishing (HTTP).
  • The secure web connections port, port 443. This port is used by Admin Console and for web publishing (HTTPS) if SSL connections are used.
  • Port 5003 for FileMaker clients.
  • Port 16000 for server administrators using Admin Console.
  • Port 16002 must be open on the master machine, open in the firewall, and available on the worker machines.
  • Port 2399 for ODBC and JDBC clients.
  • Ports 1895, 3000, 5013, 5015, 8989, 8998, 9889, 9898, 16001, 16003, 16004, 16020, 16021, 50003, and 50004 must be available on the machine, but not open in the firewall.

  See Ports used by FileMaker Server.

• To upgrade from an earlier version of FileMaker Server, see Upgrading or moving an existing installation.
• Locate your license certificate. See About the license certificate.
• If you are currently running FileMaker Pro or FileMaker Pro Advanced on the same machine, quit before installing FileMaker Server. On a FileMaker Server machine, use of FileMaker Pro or FileMaker Pro Advanced is for testing purposes only.
• Server security is important. Review the topic "Securing your data" in FileMaker Server Help and the information in the FileMaker Security Guide.

• If the machine has antivirus software installed, you may need to disable or uninstall it before running the FileMaker Server installer. Don’t enable antivirus software again until after the installer has finished.

  Do not allow antivirus software to scan the folders that contain hosted databases or the folders that contain files for container fields that store data externally.

• You cannot run two different versions of FileMaker Server on the same machine at the same time.
• Because some DHCP servers cycle IP addresses, use a static IP address.
• macOS: Avoid using the macOS Server application to enable any HTTP services while running FileMaker Server. HTTP services provided by macOS Server can interfere with FileMaker Server. See Using the Apache web server in macOS.

For best performance, run FileMaker Server on a dedicated machine reserved for use as a database server. When FileMaker Server is hosting many clients or a large number of databases, it uses a high level of processor, hard disk, and network capacity. Other processor-intensive software or heavy network traffic on the same machine will cause FileMaker Server to run more slowly and degrade the performance for FileMaker clients.

To improve performance:

• Avoid installing FileMaker Server on a machine that is a user’s primary workstation.
• Avoid using the machine running FileMaker Server as an email, print, or network file server.
• Do not use system or third-party backup software to back up databases hosted by FileMaker Server. Instead, use Admin Console to schedule backups of databases. See Backing up databases.
• Disable screen savers and sleep (or hibernate and standby) mode on the server. These features reduce performance or suspend access to hosted databases.
• Use a fast hard disk, multiple-disk RAID system, or reliable Storage Area Network (SAN) for the hosted databases.
• Turn off operating system indexing services or any third-party file indexing software. These features reduce performance.

See Optimizing your FileMaker Server deployment.

1. Follow your electronic download instructions to download the installation disk image and license certificate file. Place the license certificate in one of the following locations:

   • the default Downloads folder

     Windows: [drive]:\Users\[user]\Downloads

     macOS: /Users/[user]/Downloads

   • the installer folder (the folder where the installer is located)

   • the LicenseFile folder

     Windows: [drive]:\Program Files\FileMaker\FileMaker Server\CStore\LicenseFile, where [drive] is the drive on which FileMaker Server is being installed

     macOS: /Library/FileMaker Server/CStore/LicenseFile on the machine where FileMaker Server is being installed

2. Windows: If you have Bonjour for Windows installed, make sure it is running before you run the FileMaker Server installer.

3. Double-click the installation icon.

   • Windows: If a User Account Control alert appears, click Yes.
   • macOS: If a security message appears, click Continue.
4. Windows: Choose a language.
5. To continue with installation, click Next (Windows) or Continue (macOS).
6. Read the important information displayed. If there is a task you did not do, quit the installer and do the task.
7. Review and accept the end user license agreement.

8. Choose the installation destination.

   Note:In Windows, you can specify a non-default location. See Installation notes.

9. Choose FileMaker Server master.

   

10. Choose an option for the FileMaker Server user account (the account under which you want to run FileMaker Server):

    • To use the default account, choose Local System (Windows) or fmserver (macOS).
    • To use an existing account on this machine, choose User Name, enter the account’s user name and password. You may want to choose this option if you already have an account that has privileges set as you want—for example, to access network-attached storage.

    If the existing user account you specified does not have sufficient privileges for FileMaker Server to run, the installer displays an error message. See Installation notes.

    

11. Assign the user name and password to use whenever you log in to Admin Console as the server administrator. The server administrator is responsible for installing and configuring FileMaker Server as well as managing the FileMaker Pro Advanced databases hosted on FileMaker Server.

    Note: User names are not case sensitive. Passwords are case sensitive.

    Enter a PIN value that can be used to reset the password using the command line interface (CLI).

    Important:The PIN value can be set during installation only. The only way to change the PIN value is to reinstall FileMaker Server.

    

12. Click Install.

    • Windows:

      If you do not have the Microsoft Visual C++ 2017 Redistributable Package (x64) and the Microsoft Application Request Routing (ARR) extension for IIS installed, the FileMaker Server installer installs them.

      If you do not have Bonjour for Windows installed, you are prompted to allow the FileMaker Server installer to install it.

      See Installation notes.

    • macOS:

      Enter your macOS user name and password, then click Install Software.

      If Bonjour is not running, you are prompted to run it. See Installation notes.

    FileMaker Server begins to install. This process may take several minutes.

13. After the software has been successfully installed, open Admin Console.

    • Windows: In the last step of the installer, enable Start Admin Console, then click Finish.
    • macOS: Click Continue.

    If necessary, see Admin Console doesn’t start after installation on the master.

    Optionally, you can stop now and open Admin Console later. To open Admin Console later:

    • Enter http://127.0.0.1:16001/admin-console into a web browser.

    • Use a desktop shortcut. To start Admin Console using a desktop shortcut:

      • Windows: Double-click the FMS Admin Console shortcut on the desktop.
      • Windows versions with the Start menu: Click Start menu > All apps or All Programs > FileMaker Server > FMS Admin Console.
      • Windows versions with the Start screen: Go to the Start screen and click FMS Admin Console.
      • macOS: Double-click the FMS Admin Console shortcut on the desktop.
14. On the Admin Console Sign In page, enter the Admin Console account user name and password that you specified in the installer, then click Sign In.

15. On the Admin Console Security Settings page, decide whether to import an SSL certificate.

    Because data security is important, FileMaker Server asks you to to import an SSL certificate when you first open Admin Console.

    • If you have a custom SSL certificate to import, follow the instructions to import the SSL certificate.
    • If you don't have a custom SSL certificate to import, close Admin Console and request a custom SSL certificate from a trusted CA, or continue without importing an SSL certificate. (Open Admin Console and click the Configuration > SSL Certificate tab to import a custom SSL certificate later.)

16. On the Dashboard page, note the IP address of the server.

    

    Tip:Write down the IP address so that you can start Admin Console from another computer, if needed:

    https://[host]/admin-console

    where [host] is the IP address of the server.

17. If you want to allow technologies such as FileMaker WebDirect, FileMaker Data API, and ODBC and JDBC to access hosted databases, enable the settings on the corresponding tabs in Admin Console.

    To enable	See this Admin Console tab
    FileMaker WebDirect	Connectors > Web Publishing tab
    FileMaker Data API	Connectors > FileMaker Data API tab
    ODBC and JDBC	Connectors > ODBC / JDBC tab

    See FileMaker Server Help.

1. Start Admin Console: see Starting Admin Console.
2. Test your installation: see Testing your deployment.
3. Administer FileMaker Server: see Administering FileMaker Server.
4. Upload databases: see Uploading databases.
5. Get support: see Customer Support and Knowledge Base.

In many environments, a single-machine deployment provides sufficient performance for hosting FileMaker WebDirect solutions. However, if your server regularly has close to 100 FileMaker WebDirect clients, you can deploy FileMaker WebDirect worker machines in a multiple-machine deployment, to allow additional clients to access FileMaker WebDirect solutions or to enhance the security of server components.

If you’re not hosting FileMaker WebDirect solutions, you don’t gain performance improvements from a multiple-machine deployment. But with a multiple-machine deployment, you can place the most sensitive data residing in the Database Server behind the firewall and give clients access to worker machines placed in front of the firewall.

The diagram below shows the major components of FileMaker Server.

In a single-machine deployment of FileMaker Server, the following components are installed on one machine and that single machine is the master machine.

In a multiple-machine deployment, the machine running the Database Server is called the master machine.

• Web Server: in Windows, FileMaker Server requires Internet Information Services (IIS), which is enabled when you install FileMaker Server. In macOS, FileMaker Server uses its own instance of the Apache web server, so you do not need to enable the Apache instance that is installed as part of macOS.
• Web Publishing Engine: provides the Custom Web Publishing services and the FileMaker WebDirect services for databases hosted by FileMaker Server.
• PHP Engine: for Custom Web Publishing with PHP, FileMaker Server requires a PHP engine to respond to requests from the web server and to process PHP code. FileMaker Server includes a PHP engine and the FileMaker API for PHP. When PHP code calls the FileMaker API for PHP, those calls are interpreted and sent to the Web Publishing Engine.
• Database Server: hosts the databases that you share with FileMaker Pro Advanced and FileMaker Go users and publish on the web.
• Admin Console: runs in a web browser on any client computer from which you want to configure and administer FileMaker Server.

In a multiple-machine deployment, you deploy FileMaker WebDirect worker machines that include only two components: a web server and the Web Publishing Engine.

The worker machine does not have Admin Console. The master communicates with the worker to configure the settings on all machines and monitor the status and activity of all components.

The Custom Web Publishing services and the PHP engine are on the master machine. However, a worker machine can handle Custom Web Publishing requests from users because it provides routing services. For best results when hosting solutions that use Custom Web Publishing with PHP, put all the PHP webpage files in the appropriate FileMaker hosting folders (htdocs) on the master machine and on all worker machines.

You can first deploy on one machine and then add worker machines to accommodate more FileMaker WebDirect clients.

Single-machine deployment

You can deploy FileMaker Server on one machine in two ways: Database Server only or Database Server and Web Publishing Engine. For information on installing FileMaker Server in a single-machine configuration, see Installation quick start (single-machine deployment).

Database Server only

When you install FileMaker Server on one machine, web publishing is disabled by default. Without web publishing, you can serve FileMaker Pro Advanced, FileMaker Go, FileMaker Data API, and ODBC and JDBC clients but not FileMaker WebDirect or Custom Web Publishing clients.

Benefits: This is the easiest deployment to set up and administer if you don't need web publishing.

Note:Even when web publishing is disabled, FileMaker Server requires a web server to host the web-based Admin Console application and to handle some data transfer tasks.

Database Server and Web Publishing Engine

When you install FileMaker Server on one machine and enable web publishing, the Web Publishing Engine provides support for FileMaker WebDirect and Custom Web Publishing clients.

Benefits: This is the simplest deployment with web publishing and the one that most FileMaker Server users will use. This configuration is suitable for small deployments (up to 50 FileMaker Pro Advanced and FileMaker Go clients combined) and limited web publishing.

Multiple-machine deployment

You can deploy FileMaker Server on a master machine and then deploy additional FileMaker WebDirect worker machines as needed.

Benefits: Under normal circumstances, a single-machine deployment can only accommodate up to 100 FileMaker WebDirect clients. Each worker machine can accommodate an additional 100 FileMaker WebDirect clients.

You can also enhance the security of your deployment by placing the master machine behind a firewall and placing a worker machine in front of the firewall. When a worker machine receives FileMaker Data API and Custom Web Publishing requests, they are proxied through the worker machine to the master machine. FileMaker WebDirect requests are redirected based on the number of worker machines installed.

Tip:To best accommodate FileMaker WebDirect clients, consider the design of FileMaker WebDirect solutions. See Considering database performance.

Install the FileMaker Server software first on the master machine and then on the worker machines. Then use the Deployment assistant on the worker machine to configure the SSL certificate and to connect to a master machine.

Ports used by FileMaker Server

When running FileMaker Server in an environment that uses a firewall, be sure to configure the firewall on each machine to allow FileMaker Server to communicate. For a complete list of ports, see the FileMaker Knowledge Base.

Note:Not all of the ports listed need to be open to end users or between all machines or end users indicated in the “Used by” column in a FileMaker Server deployment. Ports marked “Available” are used locally on the machine indicated in the “Used by” column; these ports must not be used for anything else but do not need to be opened in a firewall.

FileMaker Server enables port 10050 to allow Zabbix passive checks and port 10051 to support Zabbix active checks. See Monitoring performance with Zabbix.

The following illustration shows the ports that must be open in a firewall in order for FileMaker clients and Admin Console to communicate with FileMaker Server.

• For information on the versions of supporting software that are required, see the FileMaker Server system requirements.

• Windows: You can install FileMaker Server in a non-default location including a non-boot volume, but not on remote network drives or external removable drives. You cannot install FileMaker Server to a Windows Desktop path—for example, [drive]:\Users\[user]\Desktop.

  The path you specify replaces the beginning of the default installation path, \Program Files\FileMaker\FileMaker Server. For example, if you specify the My_Path installation folder, the Databases, Scripts, and Extensions folders are installed as follows:

  • \My_Path\Data\Databases
  • \My_Path\Data\Secure
  • \My_Path\Data\Scripts
  • \My_Path\Database Server\Extensions

  The path you specify must consist of ASCII characters only.

• macOS: Do not install FileMaker Server on a target volume that is formatted as a Mac OS Extended (Journaled, Case-Sensitive) volume. This format is not supported. Format the volume as Mac OS Extended or Mac OS Extended (Journaled) instead.

• During installation, if you specify a FileMaker Server user account other than the default, the specified account must meet the following requirements:

  • Windows: The account must be either a local user account or a Windows domain account. The account must have the same privileges as the Windows system account for local file access.
  • macOS: The account must be a local user account in macOS and have the same permissions as the fmserver account for local file access (including membership in the daemon group). The account must not be from a directory service (for example, Active Directory or Open Directory).
• If you set up additional database or container data folders on remote volumes, the account specified for the FileMaker Server user account must also have full permissions to access these remote folders.

• Bonjour installation:

  • Windows: Bonjour is optional. If Bonjour is not installed, the server cannot be displayed to FileMaker Pro Advanced users in the Hosts dialog box and to FileMaker Go users in the Launch Center.
  • macOS: If Bonjour is not installed and enabled, then you cannot install FileMaker Server.
• FileMaker Server includes the 64-bit version of the Java Runtime Environment on master and worker machines.

• Windows: Do not uninstall the following while FileMaker Server is installed:

  • IIS URL Rewrite Module
  • Microsoft Application Request Routing
  • Microsoft External Cache for IIS
  • Microsoft Visual C++ 2017 Redistributable Package (x64)

1. Start Admin Console: see Starting Admin Console.
2. Test your installation: see Testing your deployment.
3. Administer FileMaker Server: see Administering FileMaker Server.
4. Upload databases: see Uploading databases.
5. Get support: see Customer Support and Knowledge Base.

To test your FileMaker Server deployment, open a hosted database using FileMaker WebDirect or FileMaker Pro Advanced.

1. Open Admin Console and click the Connectors > Web Publishing tab.
2. Verify that the Web Publishing Engine is running and FileMaker WebDirect is enabled.
3. For FileMaker WebDirect, click Open Launch Center.
4. In the Launch Center, select FMServer_Sample.

If FMServer_Sample opens, then your FileMaker Server deployment is working correctly.

1. Open FileMaker Pro Advanced from any networked machine that can reach the machine where FileMaker Server is installed.
2. In the Hosts dialog box, choose the server you want to test, and select FMServer_Sample.

If FileMaker Pro Advanced opens the sample database hosted on FileMaker Server, then the Database Server is working and responding to requests from FileMaker Pro Advanced clients.

Note:Test using a FileMaker Pro Advanced client running on a different machine, not the machine where FileMaker Server is installed.

Admin Console is a web-based application that lets you configure and administer FileMaker Server, work with and monitor hosted databases and clients, and track statistical information.

To administer FileMaker Server, use Admin Console on the computer where FileMaker Server is running or on any computer that has network access to the master machine running FileMaker Server. To secure remote administration, Admin Console uses Secure Sockets Layer (SSL) technology to encrypt HTTPS connections from other computers.

Admin Console supports many FileMaker Server administration tasks. You can:

• configure FileMaker Server application settings
• open—or host—a FileMaker Pro Advanced database, making it available to clients on the network
• view information about the files being hosted, like the number of clients accessing each database
• send messages to connected clients
• close a hosted FileMaker Pro Advanced database, making it unavailable to clients
• download a hosted FileMaker Pro Advanced database to your local system
• disconnect a selected client from all hosted databases
• pause or resume hosted databases
• create scheduled tasks to back up, verify, and clone hosted databases
• create scheduled tasks to run system scripts, FileMaker scripts, and script sequences that contain both system scripts and FileMaker scripts
• start or stop the Database Server
• start, stop, or remove a FileMaker WebDirect worker machine
• start or stop the Web Publishing Engine
• start or stop the FileMaker Data API Engine
• configure settings for ODBC and JDBC
• configure settings for FileMaker Data API
• configure settings for FileMaker WebDirect

For detailed information, see FileMaker Server Help.

Note:To use Admin Console, your remote computer needs a supported web browser; no additional runtime environments or browser plug-ins are required. See Requirements for Admin Console.

To start Admin Console:

1. Open a web browser and enter:

   http://[host]/admin-console

   where [host] is the IP address or host name of the machine running FileMaker Server as a master. This is the address you noted when you installed FileMaker Server.

2. Before the Admin Console Sign In page opens, your web browser may require you to respond to a security message. This is normal behavior for the default SSL certificate that is included with FileMaker Server. Click the option to continue to go to the Sign In page.

   To prevent this message in the future, see Requesting an SSL certificate.

   Tip:Bookmark the Sign In page in your web browser. Come back to this page to sign in to Admin Console or to open Server Help.

3. On the Sign In page, enter the name and password that you chose when you initially deployed FileMaker Server. Click Sign In.

   Note:If your web browser prompts you to save your user name and password, decline unless you are sure that access to your web browser is secure.

   Admin Console starts and displays the Dashboard page.

   The following are alternate ways to start Admin Console directly:

   To access Admin Console from	Go to
   Any computer with network access to the master machine	http://[host]/admin-console (redirects to HTTPS) where [host] is the IP address of the server
   Master machine only	http://127.0.0.1:16001/admin-console From an FMS Admin Console shortcut: Windows: Double-click the FMS Admin Console shortcut on the desktop. Windows versions with the Start menu: Click Start menu > All apps or All Programs > FileMaker Server > FMS Admin Console. Windows versions with the Start screen: Go to the Start screen and click FMS Admin Console. macOS: Double-click the FMS Admin Console shortcut on the desktop.

FileMaker provides two ways to upload databases to FileMaker Server:

• In FileMaker Pro Advanced, use File menu > Sharing > Upload to Host to transfer FileMaker Pro Advanced databases from your computer’s file system to FileMaker Server if both computers are on the same network. FileMaker Pro Advanced uploads databases along with any externally stored container field objects. FileMaker Server copies the databases to the specified database folder and sets file permissions and privileges so that you can access the databases after they are uploaded.
• Manually upload databases to FileMaker Server. Copy the databases and any externally stored container field objects to the proper location. In macOS, change the files’ group ownership to belong to the fmsadmin group. See FileMaker Server Help.

Note:If any of your databases require a plug-in, see FileMaker Server Help to manage plug-ins.

In FileMaker Pro Advanced, you can use the Database Encryption feature to encrypt the contents of a database. Encryption protects the FileMaker database and any temporary files that are written to disk. See FileMaker Pro Advanced Help.

To host an encrypted database on FileMaker Server for FileMaker clients, you can manually upload the database to FileMaker Server or use the Upload to Host menu command in FileMaker Pro Advanced to transfer the file.

When you use FileMaker Pro Advanced to upload encrypted files to the Secure folder, FileMaker Pro Advanced asks you for the encryption password so that FileMaker Server can automatically open the files on the server after they are uploaded. If you upload encrypted files to a folder other than the Secure folder or if you manually upload encrypted files, they must be opened on the server using Admin Console or the fmsadmin command line interface (CLI). See FileMaker Server Help.

Tip:Use the CLI list command to check whether a database is encrypted.

FileMaker Server provides the following ways to perform database backups.

Use a combination of these backup types to create a comprehensive backup strategy for your hosted databases. See FileMaker Server Help.

Note:If you use Time Machine in macOS, exclude FileMaker Server folder items from the Time Machine backup. Use Admin Console to back up your databases.

FileMaker Server creates a restoration log for hosted databases. At startup, before databases are opened for client access, FileMaker Server validates database entries. If databases were not properly closed, startup restoration uses the restoration log to restore the files to their last consistent state.

Startup restoration is not a replacement for database backups. But it may help resolve database integrity issues that occur due to server power loss, hardware failures, or software issues. See FileMaker Server Help.

By default, the restoration log is written to the following folder:

• Windows: [drive]:\Program Files\FileMaker\FileMaker Server\Data\Restoration
• macOS: /Library/FileMaker Server/Data/Restoration

For best results, use the FileMaker Admin API to change the restoration log folder location to a separate disk drive. See FileMaker Admin API Guide.

FileMaker Server can host FileMaker Pro Advanced databases that are connected to external SQL data sources. In FileMaker Pro Advanced, you can work with the ODBC data in much the same way that you work with data in a FileMaker database. For example, you can add, change, delete, and search external data interactively.

See FileMaker Server Help for information on using ODBC and JDBC with FileMaker Server and accessing external ODBC data sources.

Note:You do not need to enable the OBDC/JDBC data source feature of FileMaker Server to host FileMaker Pro Advanced databases that access an external SQL data source via ODBC.

If you work with FileMaker Pro Advanced databases hosted by FileMaker Server that access ODBC data from Microsoft SQL Server, you can configure the master machine to enable single sign-on (SSO). ODBC data source single sign-on allows FileMaker Pro Advanced clients to use their Windows-authenticated login credentials and permissions to access Microsoft SQL Server without logging in.

To enable ODBC data source single sign-on with FileMaker Server, configure the FileMaker Server service on the master machine to log in using the privileged user account. That is, this user account must have the Impersonate a client after authentication privilege enabled, and the account must be an Administrator account and configured in Windows Active Directory on the network.

Before you can enable ODBC data source single sign-on, your Windows domain administrator must:

• configure the Account is trusted for delegation security setting for each user’s Windows user account
• configure the Trust this user for delegation and Use Kerberos only security settings for the privileged user account on the master machine
• enable the Impersonate a client after authentication privilege for the privileged user account on the master machine
• configure the ODBC DSN to use Windows authentication on the master machine
• configure Microsoft SQL Server to use Windows authentication

You can create scheduled tasks to run:

• system-level scripts—for example, Windows batch, Perl, VBScript, and AppleScript
• FileMaker scripts in databases hosted by FileMaker Server
• script sequences that combine a FileMaker script with an optional pre-processing system-level script and an optional post-processing system-level script

See FileMaker Server Help.

The Admin Console Dashboard page displays statistics related to CPU usage, memory usage, network throughput, and disk throughput. These statistics can help you diagnose system hardware issues that may be affecting system performance.

To see a summary of connection and database statistics for FileMaker Server, open the server statistics log (Stats.log) and client statistics log (ClientStats.log). These statistics can help you diagnose performance problems and identify client access issues. You can view:

• the percentage of times FileMaker Server retrieved data from the cache (RAM) rather than the hard disk, percentage of cache unsaved, the amount of data read from disk, data written to disk, and client call times
• client connection information collected during remote calls made by each FileMaker client, all Web Publishing Engine (WPC) clients, and all ODBC and JDBC clients

See FileMaker Server Help.

You can send messages to notify FileMaker Pro Advanced, FileMaker Go, and FileMaker WebDirect clients about important events such as server shutdowns, database maintenance, or deadline reminders. You can send messages to:

• all FileMaker clients or selected FileMaker clients connected to hosted databases
• FileMaker clients connected to any database or selected databases hosted by FileMaker Server

See FileMaker Server Help.

FileMaker Server tracks activity, client access, and other information as it operates and stores this information in log files.

To download log files, open Admin Console and click the Configuration > Logging tab.

See FileMaker Server Help.

You can configure FileMaker Server to send SMTP email notifications about errors. Specify your SMTP mail server settings in Admin Console, including the SMTP server address, the port number, user name and password, and the list of email addresses that will receive the email messages.

See FileMaker Server Help.

FileMaker provides the tool fmsadmin for administering FileMaker Server via the command line interface (CLI). You must be logged on to the computer running FileMaker Server, either directly or using remote desktop software, to use the CLI. The CLI is available via the command prompt (Windows) and the Terminal application (macOS). CLI commands can also be used in a script or batch file.

You can upgrade an existing installation of FileMaker Server 16 or 17 to FileMaker Server 18. You can also move an existing installation of FileMaker Server 18 to other machines.

To change the license of an existing deployment of FileMaker Server 18, see Updating the FileMaker Server license key.

The steps listed below outline the process. See the remaining sections for information about each step.

1. Save the settings for your schedules.
2. Note your existing FileMaker Server settings.
3. Stop FileMaker Server.
4. Make a copy of any databases and shell script files you used with FileMaker Server.
5. Uninstall FileMaker Server.
6. Clear the Java cache and web browser cache to clear information from the previous FileMaker Server installation.
7. Install FileMaker Server 18.
8. Move any databases or script files you used with the previous version of FileMaker Server to the proper folders within the FileMaker Server folder structure.
9. Load the settings for your schedules after installation.
10. Configure FileMaker Server.

If you need to upgrade your machine’s operating system, see Upgrading the operating system on machines running FileMaker Server.

You can save the settings for your schedules that are configured in the current installation.

1. Open Admin Console and click the Configuration > Script Schedules tab.
2. Click Save or Load and choose Save All Schedules. By default, the file is saved in your web browser’s download folder.

After you install FileMaker Server, you can load the schedule settings file to instantly configure them in the new installation.

Note:The default name of the schedule settings file matches the version of FileMaker Server:

• FileMaker Server 16: fms16_settings.settings
• FileMaker Server 17: fms17_settings.settings
• FileMaker Server 18: fms18_settings.settings

You cannot specify a different name when you save the file in Admin Console, but you can change the filename using your operating system tools after you save the file.

Make a note of your existing FileMaker Server settings because you will have to reenter your settings manually later. Some examples are:

• Note the name of your FileMaker Server installation (the name FileMaker Pro Advanced users see in the Hosts dialog box and FileMaker Go users see in the Launch Center).
• Save the schedule settings in a file. See Step 1. Save your schedules.
• Note other settings that you have changed from the defaults and want to reuse in your FileMaker Server 18 deployment.
• If you are using a custom SSL certificate, save a copy of the serverCustom.pem and serverKey.pem files stored in the CStore folder so that you can import your custom SSL certificate later.

Where to note settings for FileMaker Server

Before moving an existing installation of FileMaker Server to another machine, start Admin Console (see Starting Admin Console). Make a note of the settings in the configuration tabs:

• For FileMaker Server 17 and 18, note the settings on the Configuration, Connectors, and Administration tabs.
• For earlier versions, note the settings on the General Settings, Database Server, and Web Publishing tabs.

1. On the Admin Console Connectors > Web Publishing tab, stop any Web Publishing Engine that is running.

   Wait until Web Publishing Engines on master and worker machines have stopped.

2. On the Configuration > General Settings tab, stop the Database Server.

   Wait until the Database Server has stopped.

3. Stop the FileMaker Server service (Windows) or processes (macOS). See FileMaker Server Help.

Make a copy of any databases, shell script files, and plug-ins you used with FileMaker Server. In a default FileMaker Server installation, they are stored on the master machine in the following folders.

Note:When you install FileMaker Server in a non-default location in Windows, the beginning portion of the default path, \Program Files\FileMaker\FileMaker Server, is replaced with the path you specified during installation. For example:

\User-specified location\Data\Databases

After you have noted the settings in your existing installation of FileMaker Server, you can uninstall FileMaker Server.

Note:To uninstall a multiple-machine deployment, uninstall the worker machines first.

Windows:

To uninstall FileMaker Server:

1. Open Control Panel, then click Uninstall a program (or Programs and Features).
2. Select the FileMaker Server product from the list and click Uninstall.
3. Confirm that you want to uninstall.

macOS:

After you uninstall FileMaker Server, the Java cache may retain pointers to FileMaker Server components that have been uninstalled. In addition, your web browser may retain cached versions of artwork and HTML files that have been uninstalled.

Clear the Java cache and web browser cache to clear information from the previous FileMaker Server install.

To install FileMaker Server, use an account with administrative privileges.

• To deploy on a single machine, see Installation quick start (single-machine deployment).
• To deploy across multiple machines, see Deploying FileMaker Server across multiple machines.

The FileMaker Server installer prompts you for some of the settings that you noted in Step 2. Note your FileMaker Server settings.

Move the script files and plug-ins you used with the previous version of FileMaker Server to the proper folders within the FileMaker Server 18 folder structure. See Step 4. Make a copy of databases, scripts, and plug-ins.

Note:You can use FileMaker Pro Advanced to transfer .fmp12 databases to your new FileMaker Server deployment. See Uploading databases. To transfer your databases manually, see FileMaker Server Help.

If you are moving from a previous FileMaker Server 16, 17, or 18 installation, you can load the schedule settings file after installation. See Step 1. Save your schedules.

1. Open Admin Console for the new FileMaker Server 18 installation and click the Configuration > Script Schedules tab.
2. Click Save or Load and choose Load All Schedules.
3. Click Browse and navigate to the folder where you saved the schedule settings file.
4. Select the schedule settings file and click Choose.
5. Click Load to load the schedule settings file into FileMaker Server.
6. Read the message to see how many schedules loaded successful.
7. Open the LoadSchedules.log file in the Logs folder for detailed information about errors that may have occurred and make any necessary corrections.

See FileMaker Server Help.

You can now start Admin Console and configure your FileMaker Server deployment using the settings you noted in Step 2. Note your FileMaker Server settings. See FileMaker Server Help.

As part of the configuration, be sure to import your custom SSL certificate, if you are using SSL.

For information about uploading databases, scheduling backups, and performing other regular tasks, see Administering FileMaker Server.

For a list of supported operating system versions, see the FileMaker Server system requirements.

In all deployments, FileMaker Server uses Internet Information Services (IIS) in Windows or Apache in macOS. The web server serves web publishing clients, hosts the web-based Admin Console application, and handles some data transfer tasks.

This section describes the basics of requesting a custom Secure Socket Layer (SSL) certificate, enabling the web server, and configuring additional IIS authentication settings. For information about configuring the web server, see the documentation for the web server.

FileMaker Server uses SSL technology to encrypt HTTPS connections between the web server and users’ web browsers for Admin Console, FileMaker WebDirect, FileMaker Data API, and Custom Web Publishing. The Database Server can also use SSL encryption for connections with FileMaker Pro Advanced clients, FileMaker Go clients, and the Web Publishing Engine.

SSL uses digital certificates to certify the ownership of the public key used to encrypt data. FileMaker Server provides a standard SSL certificate signed by FileMaker, Inc., that does not verify the server name. This certificate is used by all FileMaker Server components that use SSL. However, because this certificate doesn’t verify the server name, most web browsers will warn users of a problem with the website’s security certificate. For some web browsers, certificate issues can affect performance and functionality as well. The FileMaker default certificate is intended only for test purposes.

A custom SSL certificate is required for production use. If your server does not have a custom SSL certificate, Admin Console will display security warnings.

When you import a custom SSL certificate, FileMaker Server enables all Database Server client connections to use SSL, and web clients are restricted to HTTPS connections.

For information about using secure connections, see FileMaker Server Help.

You can request a custom SSL certificate that matches your specific server name or domain name from a trusted certificate authority (CA) supported by FileMaker, Inc. Use the CLI certificate command to create a certificate signing request (serverRequest.pem), which you send to a CA, and a private key (serverKey.pem), which you keep secret. See Using the CLI certificate command. When you receive your signed certificate from the CA, open Admin Console and click the Configuration > SSL Certificate tab to import the certificate.

The custom SSL certificate file is placed in the CStore folder:

• Windows: [drive]:\Program Files\FileMaker\FileMaker Server\CStore\serverCustom.pem
• macOS: /Library/FileMaker Server/CStore/serverCustom.pem

After updating the custom SSL certificate, restart the Database Server.

When the Database Server starts, if it is unable to find a custom SSL certificate, it will use the default server.pem file.

See FileMaker Server Help for information about securing your data.

Notes

• FileMaker Server supports using a single-domain certificate, a wildcard certificate, or a subject alternative name (SAN) certificate.

The CLI certificate command can create a request for a single-domain certificate or a wildcard certificate. To use a SAN certificate, contact a CA to create the certificate signing request.

• Use FileMaker methods to import the custom SSL certificate: either the Admin Console import certificate feature or the CLI certificate command. Do not use IIS certificate tools or OpenSSL certificate tools to import a custom SSL certificate for the FileMaker Server web server component because the Database Server and the web server component must use the same certificate.
• The custom SSL certificate must use base-64 encoding.
• FileMaker Server does not support validation using a certificate revocation list (CRL validation).
• If you are using a multiple-machine deployment, request custom SSL certificates for the master machine and the worker machines. Import a custom SSL certificate on each machine.
• To remove an imported certificate, use the CLI command fmsadmin certificate delete, and restart FileMaker Server to apply the change. See CLI Help.
• For information about supported certificates, see the FileMaker Knowledge Base.

The IIS web server must be enabled on the master and worker machines in order for FileMaker Server to operate.

If the FileMaker Server installer detects that IIS is not enabled, it will enable IIS. The FileMaker Server installer also installs the Microsoft Application Request Routing (ARR) extension for IIS if it is not present. However, if you need to enable IIS manually, follow the steps below for the supported version of Windows you’re using.

To verify the web server is running, enter the following in a web browser on the web server host machine:

http://127.0.0.1

During installation, the FileMaker Server installer checks whether any existing website is using ports 80 or 443 (the Default Web Site uses port 80 and is enabled when your first enable IIS). If these ports are in use, the installer prompts you to make these ports available. Then, the installer creates its own separate website named FMWebSite and configures it to use port 80 for HTTP and port 443 for HTTPS. On the master machine, the installer also configures FMWebSite to use port 16000 for Admin Console via HTTPS.

For information about IIS, see the Microsoft website.

You do not need to enable the Apache web server that is installed with macOS, and you don't need to have the macOS Server application installed. The FileMaker Server installer creates its own instance of the Apache web server on both the master and worker machines and configures this web server to use port 80 for HTTP and port 443 for HTTPS. On the master machine, the installer also configures its Apache web server to use port 16000 for Admin Console via HTTPS. If you have enabled the Apache web server that is already installed with macOS, the FileMaker Server installer prompts you to make the ports available.

If you use the macOS Server application to enable any HTTP services (for example, websites or a wiki), the existing Apache instance may be reenabled after FileMaker Server is installed. To ensure the Apache instance used by FileMaker Server works normally, you may need to configure any other HTTP services to use different ports from the ports that FileMaker Server uses, disable other HTTP services, or uninstall the macOS Server application.

This section provides tips on selecting the proper hardware, configuring the operating system, identifying issues that help FileMaker Server run efficiently, and monitoring the server’s performance. If your company has an IT group, they might be able to provide support and guidance to keep the server running efficiently.

Before you select hardware for the server, consider how many users are or will be accessing the server. If many users are accessing the database, then the hard drive and processor will probably get heavy usage. A Database Server accessing a great deal of data can take more resources and needs the right equipment.

Consider these key areas when selecting the hardware:

• Disk subsystem: The disk subsystem is a type of disk storage that has an integrated collection of disk drives. This subsystem is the most important factor to consider when purchasing hardware for FileMaker Server because it reads and writes data stored in the database. Having a fast and optimized disk subsystem to effectively handle both reading and writing the data has a significant impact on how the database performs. Regardless of the specific drive type you selected, configure the subsystem to support a Redundant Array of Inexpensive Disks (RAID) or reliable Storage Area Network (SAN) for the hosted databases.
• Processor: FileMaker Server handles many processor intensive operations, such as finding information, evaluating unstored calculations, and resolving relationships; therefore, the processor you choose is almost as important as the disk subsystem. Because FileMaker Server can take advantage of multiple processors, certain database tasks can be handled by different processors.
• Network: The network throughput can be measured using various tools on the system, and the quality of network throughput depends on several factors. These include the type of Network Interface Card (NIC) installed and the network’s physical infrastructure. While the network infrastructure may be outside your control, problems happen due to the network configuration, traffic, and routing. Users can connect to and work with databases over a LAN or a WAN connection. Connecting to a FileMaker Server hosted database over the Internet or a WAN requires that several ports be open for TCP.

• Memory: The amount of memory a database uses depends on the size of the database, the type of database, the number of users, and the database’s complexity. Any one of these factors can require more memory. Another critical factor for FileMaker Server is the cache.

  The maximum allowed database RAM cache size is the smaller positive number of these two formulas:

  • the physical RAM size minus 1024 MB (1 GB)
  • 90% of the physical RAM size

  If Web Publishing is enabled in a single-machine configuration, set the database cache to no more than 50% of the maximum.

  Specify the database cache size using the CLI command set serverconfig cachesize. For example, to set the cache size to 1024 MB, use the command fmsadmin set serverconfig cachesize=1024. See CLI Help.

Note:During deployment, FileMaker Server configures memory use based on the physical RAM size. If you add or remove RAM, you need to change the cache size manually using the CLI command or reinstall FileMaker Server so that FileMaker Server can recalculate optimal memory use for its components.

Keeping the server running reliably and efficiently takes some planning. This section provides information on setting up and configuring the operating system on machines running FileMaker Server.

Database design can impact FileMaker Server’s performance. When you design your databases, consider the clients that will be using the databases and how you might simplify the design for those clients.

• To improve performance for all clients, limit the use of:

  • external tables
  • complex table relationships
  • unstored calculations
  • value lists
  • script triggers
  • the Perform Script on Server script step
• For FileMaker Pro Advanced clients, optimize layout performance, improve search performance, reduce conditional formatting, and disconnect users from the server when they are idle. See FileMaker Pro Advanced Help.
• For FileMaker WebDirect clients, limit the number of portals and panel controls, and limit the number of objects displayed in List View and portals. See FileMaker WebDirect Guide.
• For Custom Web Publishing clients, limit the number of records returned for Find requests and reduce the prevalidation of field data. See FileMaker Server Custom Web Publishing Guide.
• To identify performance issues with hosted databases, use the Top Call Statistics setting in Admin Console. See FileMaker Server Help.
• Startup restoration is enabled by default. Startup restoration improves reliability. It can also improve performance when multiple users access a database. However, startup restoration can slow performance for single users. See FileMaker Server Help.

Monitoring the server is important for recognizing and preventing problems.

• When users report a problem, such as a system crash or very slow performance, you need good monitoring tools to determine what caused the problem.
• By analyzing future hardware needs, taking baseline readings when monitoring a situation, or gaining a better understanding of the server’s health, you can prevent future problems.

• FileMaker Server Help is available on each page of Admin Console. Scroll to the bottom of the page and click Help.
• FileMaker Server documentation is accessible on each page of Admin Console. Scroll to the bottom of the page and click Documentation.
• On the web, go to the Product Documentation Center.

• For help with installation, launch, or reinstallation, visit Support.
• For tips, technical advice, and more information about FileMaker Server, visit the FileMaker Knowledge Base.
• To ask questions and get advice from other users, visit the FileMaker Community.

Note:Information in the FileMaker Knowledge Base and the FileMaker Community may not be available in all languages.

Check for software updates on the Admin Console Configuration > General Settings tab. When a software update is available, for Server Version, click the link to download the update.