These specifications ensure optimal performance, stability, and security for connected users. 

1. System Requirements

FileMaker Server must be installed on a dedicated, supported operating system (OS). Virtual environments (VMs) are supported but must adhere to the same minimum specifications as physical machines.

The full technical specifications for FileMaker Server 22 are available from the Claris website. Below are key tables from that webpage.

Supported Operating Systems

OS Configuration Notes

  • The server OS must be fully updated with the latest security and stability patches.
  • The server must be a dedicated machine; other intensive applications (e.g., mail servers, heavy web servers, database servers like SQL) should run on separate hardware.
  • Required server roles (e.g., IIS on Windows) must be correctly configured before FileMaker Server installation.

Hardware Specifications

Storage Considerations

  • Storage Capacity: Music Monitor rarely requires 200 GB. Exceptions occur when PDFs and other media are uploaded frequently to Music Monitor’s notes and library. Check the capacity of your current server machine for reference.
  • Primary Drive: Use Solid State Drives (SSD) or Non-Volatile Memory Express (NVMe) storage for the operating system and the FileMaker database files. Hard Disk Drives (HDD) are not recommended due to I/O bottlenecks.
  • Backup Drive: A separate, fast storage device (local or network) is required for scheduled backups. This must have capacity for the full database size plus multiple scheduled backup cycles.
  • Performance: Disk I/O speed is often the biggest bottleneck for FileMaker performance. Ensure high sustained read/write speeds.

3. Network and Security Requirements

Networking

  • Static IP Address: The server must have a static IP address for reliable connection and DNS resolution.
  • Ports: Specific ports must be opened and correctly forwarded on any firewalls:
    • 5003: FileMaker Client Connection (TCP) (Alternatively, this traffic can be re-routed through 443 using the “HTTPS Tunnelling Option”.)
    • 443 (HTTPS): WebDirect and Data API access (TCP)
    • 80 (HTTP): Redirects to 443 (TCP - required for initial setup/admin console access)
    • 16000 (Admin Console): Management access (TCP)
  • Latency: Network latency between clients and the server should be minimal (ideally < 50ms).
  • Web Server: FileMaker Server includes its own dedicated web server (based on Apache or IIS) for WebDirect and the Data API. No separate installation is needed, but the required OS web server roles must be enabled.
  • Discovery: Servers on the local network are often automatically displayed in the client's host list. For remote connections, the server's address must be entered manually or the connection must be established via a Favorite Host entry.

Security

  • Firewall: A properly configured firewall is essential to restrict access only to the necessary ports and trusted networks.
  • SSL/TLS: A valid, third-party SSL certificate is mandatory for securing client connections, WebDirect, and Data API access. Self-signed certificates are not recommended for production.
  • User Management: FileMaker Server supports External Authentication through services like Active Directory or Open Directory, allowing users to log in with their existing network credentials. Additionally, OAuth 2.0 Identity Providers (such as Google, Microsoft Azure AD, or Amazon) can be configured, enabling single sign-on (SSO) capabilities and leveraging modern web standards for secure access. External Authentication is not required by Music Monitor.
  • Antivirus Exclusions: Antivirus software is permitted, but specific folders used by FileMaker Server for hosting databases and running backups must be excluded from real-time scanning to prevent performance issues and file corruption.
    • Exclusion list typically includes: Database folders, backup folders, and the FileMaker Server process itself.