Filemaker Server 18 Requirements

Posted By admin On 27/11/21

Product Version: Release Date. System Requirements: FileMaker Server: 19.1.2: 10/2020: Windows Server 2019 Standard Edition (with Desktop Experience) Windows Server 2019 Datacenter (with Desktop Experience).

FileMaker Server 19 Network Install Setup Guide

This document explains how to configure the installation of Claris® FileMaker Server™ 19.1 for Windows, macOS, or Linux over a network.

Your electronic download contains FileMaker Server installers for Windows, macOS, and Linux. All use of this software is subject to the terms of your license agreement.

FileMaker 18 Security Guide: Best Practices for Configuring Security Options. System requirements. Enable plug-ins in FileMaker Server and FileMaker Cloud for AWS. In FileMaker 17, the import action choices appear in the lower left of the window, which is not a location that gets your immediate attention. Since this is likely the first choice you will make, it ought to be more prominent. FileMaker 18 improves on the situation by placing the Import Action at the top of the screen above the actual data map. On this site we promote, share and showcase material from some of the brightest minds in FileMaker. We encourage you to visit their sites and to inquire about their services. FMT is proud to deliver and promote FileMaker Developers Worldwide since 1997. Our Forum The Original FileMaker Forum has 45,500+ members. FileMaker Pro 18 Advanced can connect to the following hosts: FileMaker Server 18, 17 and 16 FileMaker Pro 18, 17 and 16 Advanced FileMaker Pro 16 FileMaker Cloud 1.18 and 1.17 The latest updates must be applied to the above software before hosting FileMaker Pro 18 Advanced apps. Additional requirements.

Before you configure your installation

  • Find the license certificate for your software.

    FileMaker Server uses a license certificate to set the license key. The person who purchased the FileMaker Server license received an email message with a link to a software download page. Information about the license certificate is on that page. The license certificate is customized for your organization.

    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.

    See FileMaker Server Installation and Configuration Guide.

    Important:When installing software, enter the organization name exactly as it appears on the software download page, including capitalization.

  • Determine how personalized information will be entered when users install FileMaker Server. There are two ways to enter this information:

    • (Recommended method) You can set up an assisted installation, which uses a personalization file named Assisted Install.txt, to supply information to the installer and standardize your FileMaker Server installations. This method lets you customize the installation.
    • Users can personalize the software by entering information when installing FileMaker Server on their computers.

    Important:To install FileMaker Server, users must have administrator privileges for the operating system they are installing on.

Where to find Claris product documentation

  • FileMaker Server Help is available on each page of FileMaker Server Admin Console. Scroll to the bottom of the page and click Help.
  • FileMaker Server product documentation is accessible on each page of Admin Console. Scroll to the bottom of the page and click Documentation.
  • To learn about, view, or download additional Claris product documentation, visit the Product Documentation Center.

For information about the product or deploying FileMaker Server, see FileMaker Server Installation and Configuration Guide.

About assisted installations

Assisted installation makes it easier to install multiple deployments of FileMaker Server. You enter required information (such as an organization name) in a personalization file and then make the file available on your network. The file is used to install FileMaker Server on computers in your organization.

You can also set up a silent (unattended) installation, which suppresses display of the installation screens. See About silent assisted installations (Windows), About silent assisted installations (macOS) or About silent assisted installations (Linux).

After you edit the personalization file and make it and the FileMaker Server installation files available on the network, users can perform an assisted installation. See How users perform an assisted installation.

After an assisted installation of FileMaker Server, users must use Admin Console on the master machine and the Deployment assistant on worker machines to set up their multiple-machine deployments of FileMaker Server. Instruct users to see FileMaker Server Installation and Configuration Guide.

Set up assisted installations

To set up a networked volume so that users can install FileMaker Server for Windows, macOS, and Linux, perform the steps in the following sections.

Copy installation files to a networked volume

  1. Create a folder on a networked volume for the FileMaker Server installer files.
  2. Locate the following folders and files, and copy them to the folder you created on your networked volume.

    • Windows: The Files folder, which contains the personalization file, Assisted Install.txt; the License Agreements folder; and other required installation files.
    • macOS: The FileMaker Server installer application; the personalization file, Assisted Install.txt; and the License Agreements folder.
    • Linux: The FileMaker Server RPM (RPM Package Manager) installer; the personalization file, Assisted Install.txt; and the License Agreements folder, and the README_Installation.txt with companion installation instructions.
  3. To use a personalization file, continue with Customize the personalization file. If you don’t want to use a personalization file, continue with How users perform an assisted installation.

Customize the personalization file

  1. Use a text editor to open the Assisted Install.txt file on your networked volume.

    Note:The Assisted Install.txt file is a cross-platform file. The same Assisted Install.txt file can be used for installing on Windows, macOS, and Linux systems.

  2. Modify the following variable settings as needed.

    ToDo this
    Accept or don't accept the End User License Agreement (EULA)

    For silent installations only, type one of the following after License Accepted=

    • 1 (one) to accept the EULA terms
    • 0 (zero) not to accept the EULA terms (default)

    See About silent assisted installations (Windows), About silent assisted installations (macOS) or About silent assisted installations (Linux).

    Important:If you keep the default of 0 (zero), the installation will stop.

    Windows and macOS: Enter an organization name for all installations

    Type a name after Organization=

    When specifying a variable for Organization=, type the organization name exactly as it appears on the software download page.

    Windows: If you enter no value, the installer defaults to the name that was used to register Windows.

    Specify the deployment options

    Type one of the following after Deployment Options=

    • 0 (zero) to install a server machine (default)
    • 1 (one) to install a Claris FileMaker WebDirect worker machine

    If you are setting up a multiple-machine deployment, you need to provide an Assisted Install.txt file for installing on the master machine and an Assisted Install.txt file for installing on the Claris FileMaker WebDirect™ worker machines.

    Windows and macOS: Specify the FileMaker Server user account

    Type one of the following after FileMaker Server User=

    • 0 (zero) to run FileMaker Server under the default account (Local System for Windows, fmserver for macOS)
    • 1 (one) to run FileMaker Server under a different account

    If you specify FileMaker Server User=1 for a silent installation, the installation will stop. See About silent assisted installations (Windows) and About silent assisted installations (macOS).

    Specify the Admin Console user name

    Type the user name to be used for signing in to Admin Console as the server administrator after Admin Console User=

    The user name is not case sensitive.

    If you enter no value, the default user name admin is used.

    Specify the Admin Console password

    Type the password to be used for signing in to Admin Console as the server administrator after Admin Console Password=

    The password is case sensitive.

    Specify the Admin Console PIN

    Type the four-digit PIN value to be used in the command line interface (CLI) for resetting the Admin Console password after Admin Console PIN=

    Windows and macOS: Specify whether, after installation, Admin Console automatically opens on the master machine, and whether the Deployment assistant automatically starts on worker machines

    Type one of the following after Launch Deployment Assistant=

    • 0 (zero) to suppress opening Admin Console (master machine) and starting the Deployment assistant (worker machine)
    • 1 (one) to open Admin Console (master machine) and start the Deployment assistant (worker machine) after installation (default)
    Specify the path for the FileMaker® license certificate

    Type the fully qualified path for the license certificate file after License Certificate Path=

    For example:

    • Windows: C:Usersuser nameDownloadsLicenseCert.fmcert
    • macOS: /Users/user name/Downloads/LicenseCert.fmcert
    • Linux: /home/user name/Downloads/LicenseCert.fmcert

    Notes:

    • Windows: Use only ASCII characters for the folder location of the license certificate.
    • If you omit the path for the FileMaker license certificate, the installer looks for a file with the filename extension .fmcert in the following paths:
      • the default Downloads folder on the machine where the installer is located
        • Windows: C:Usersuser nameDownloads
        • macOS: /Users/user name/Downloads
        • Linux: /home/user name/Downloads
      • the installer folder (the folder where the installer is located)
      • the LicenseFile folder
        • Windows: drive:Program FilesFileMakerFileMaker ServerCStoreLicenseFile, 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
        • Linux: /opt/FileMaker/FileMaker Server/CStore/LicenseFile on the machine where FileMaker Server is being installed
    Windows and macOS: Suppress or display the Customer Information, Deployment Options, User Account, and Admin Console Account dialog boxes during installation

    Type one of the following after Skip Dialogs=

    • 0 (zero) to display the dialog boxes during installation
    • 1 (one) to suppress the dialog boxes

    When you specify 1 (one), users don't have to enter information in the installer.

    If you entered FileMaker Server User=1 (and Deployment Options=0) above, the FileMaker Server User Account dialog box still displays.

    If you entered no value for Admin Console Password= or Admin Console PIN= above, the Admin Console Account dialog box still displays.

  3. Save the changes you have made to Assisted Install.txt as plain text.

    • Windows: Assisted Install.txt and Setup.exe must be in the Files folder during installation.
    • macOS: Assisted Install.txt must be in the same folder as the FileMaker Server installer application during installation.
    • Linux: Assisted Install.txt must be in the same folder as the FileMaker Server rpm installer during installation.

How users perform an assisted installation (Windows and macOS)

To install FileMaker Server, instruct users to mount the volume containing the installation files, then double-click Setup.exe (Windows) or the FileMaker Server installer application (macOS).

Windows: Instruct users who see the Open File – Security Warning dialog box to click Run to continue installing.

If the file, Assisted Install.txt, is present in the same folder as the installer, the installer uses information in the file during installation. If this file is not present or is incomplete, users have to supply required information.

After installation is complete, users must use Admin Console on the master machine and the Deployment assistant on worker machines to set up their multiple-machine deployments of FileMaker Server. In the Assisted Install.txt file, you can specify whether the Deployment assistant starts automatically after installation on worker machines. If you choose to suppress starting the Deployment assistant, then instruct users to open the Deployment assistant manually by using a shortcut (Windows) or alias (macOS), or using a web browser:

  • On the master machine, open a web browser and enter http://localhost:16001/admin-console to open Admin Console.
  • On a worker machine, open a web browser and enter http://localhost:16003 to open the Deployment assistant.

Windows: A shortcut pointing to the Admin Console Sign In page (master machine) or FileMaker WebDirect Worker Deployment Assistant (worker machine) is created in Start menu > All Programs or All apps > FileMaker Server, or Start menu > Programs > FileMaker Server. In Windows versions that have the Start screen, the shortcut is available on the Windows Start screen. In all versions, a shortcut is also created on the desktop.

macOS: An alias pointing to the Admin Console Sign In page (master machine) or FileMaker WebDirect Worker Deployment Assistant (worker machine) is created on the desktop.

Notes

  • To install FileMaker Server, users must have administrator privileges.
  • In Windows, you can choose the language displayed in the installer. In macOS, the installer displays in the same language as the current macOS system language. In Windows and macOS, the language that users see when they use FileMaker Server Admin Console is the same as the language of the base operating system installation on the master machine.

About silent assisted installations (Windows)

During a silent (unattended) installation, user interaction with the FileMaker Server installer is kept to a minimum. Required installation information is read from the personalization file, Assisted Install.txt, and installation screens are not displayed. See Customize the personalization file.

Important:If you choose to perform a silent installation, the installation screens do not display. However, you are still required to accept the terms that are stated on the installation screens. Specifically, if the End User License Agreement (EULA) screen will not be displayed, then in the Assisted Install.txt file, you are required to set License Accepted= to either 1 (yes) or 0 (no). The default value is 0. If you set License Accepted= to 1, this signifies your acceptance of the EULA text on the EULA screen.

There are two ways to perform a silent installation. Users can:

  • Double-click the Setup.exe file, which is located on the mounted volume. This method requires that you modify the Setup.ini file. See Modify Setup.ini for silent installation (Windows).
  • Type the installation command and applicable options at the command line. See Perform a silent installation using the command line (Windows).

Important

  • FileMaker Server requires that ports 80 and 443 be available on the user’s machine. If they are not available, the software will not install.
  • FileMaker Server requires the following components:

    • Java Runtime Environment
    • Bonjour for Windows
    • Microsoft Visual Studio C++ Redistributable Package

    FileMaker Server installer automatically installs these components if they are not on the user's machine. For information about FileMaker Server hardware and software requirements, see the FileMaker Server system requirements.

Modify Setup.ini for silent installation (Windows)

If you make the following changes to the Setup.ini file, a silent installation begins when users mount the networked volume and double-click Setup.exe.

Filemaker Server 18 Require Password-protected Databases Is Enabled

  1. Locate the Setup.ini file in the Files folder inside the FileMaker Server folder.
  2. Open Setup.ini using a text editor.
  3. Locate the [Startup] section. Then:

    ToAdd the options as shown after CmdLine=
    Install FileMaker Server without a user interface (silent install)CmdLine=/q
    Display a progress bar and Cancel button during installationCmdLine=/qb
  4. Save and close the Setup.ini file.

Perform a silent installation using the command line (Windows)

Users can install FileMaker Server from the command line. When you use this method, the installer can inform users whether installation was successful.

A command line silent installation requires you to run the Command Prompt as administrator.

  • To run as administrator on Windows versions with the Start menu:

    1. Choose Start menu > All Programs > Accessories, or Start menu > Programs > Accessories, or Start menu > Windows System.
    2. Right-click Command Prompt, then choose Run as administrator.
  • To run as administrator on Windows versions with the Start screen:

    1. Right-click the Start screen, and choose All apps.
    2. Right-click Command Prompt, and choose Run as administrator.
  • To run as administrator on Windows Server, right-click the Start menu, and choose Command Prompt (Admin).

The following table describes options you have when performing an assisted installation from the command line.

Filemaker Server 18 Requirements
ToInstruct users to open a command window, then type
Install FileMaker Server without a user interface (silent install)'pathnamesetup.exe' /s /v/qn
Display a dialog box indicating whether FileMaker Server was successfully installed'pathnamesetup.exe' /s /v/qn+
Display a progress bar and Cancel button during installation'pathnamesetup.exe' /s /v/qb
Uninstall FileMaker Server without a user interface (silent uninstall)'pathnamesetup.exe' /s /x /v/qn

Note:pathname is the location of the installer folder you created on the networked volume.

About silent assisted installations (macOS)

Important:If you choose to perform a silent installation, the installation screens do not display. However, you are still required to accept the terms that are stated on the installation screens. Specifically, if the End User License Agreement (EULA) screen will not be displayed, then in the Assisted Install.txt file, you are required to set License Accepted= to either 1 (yes) or 0 (no). The default value is 0. If you set License Accepted= to 1, this signifies your acceptance of the EULA text on the EULA screen.

Users can perform a silent installation using the Terminal application.

Filemaker server 18 upgrade

Filemaker Server 18 Hardware Requirements

  1. Create the Assisted Install.txt file with your preferences, and place it in the same folder as the FileMaker Server installer. See Customize the personalization file.
  2. In the Terminal application, enter the macOS installer command:

    sudo installer -pkg FileMaker Server 19.pkg -target /

Important:FileMaker Server requires that ports 80 and 443 be available on the user’s machine. If they are not available, the software will not install.

About silent assisted installations (Linux)

Filemaker Server 18 Installation Guide

After you update the customized personalization file, the assisted installation is launched from the Linux CLI.

  1. Create the Assisted Install.txt file with your preferences. See Customize the personalization file.
  2. To begin the assisted installation, enter:

    sudo FM_ASSISTED_INSTALL=[path/filename] yum install [filemaker_server.rpm]

    where:

    path is the directory path to the customized personalization file

    filename is the name of the customized personalization file

    [filemaker_server.rpm] is the name of the FileMaker Server for Linux installer

    Note: The command defaults to 'Assisted Install.txt' if you do not specify a filename.

Filemaker Server 19 Requirements

Important:FileMaker Server requires that ports 80 and 443 be available on the user’s machine. If they are not available, the software will not install.