JobRunner and FloorManager System and Network Requirements

JobRunner and FloorManager run on the Claris FileMaker platform. This article outlines the system and network requirements for running JobRunner, FloorManager, or both applications.

Systems that deviate from these requirements may result in reduced performance.

In this article

• Overview
• Bare Metal Servers versus Virtualized Servers
• Cloud Servers
• Server Lifecycle
• Server Exclusivity
• Server Sizing
• Server Specification Baseline Requirements
• Server Networking
• WAN, LANs, and VPNs
• Server Firewall Requirements
• Workstation Requirements
• Printers
• Hardware and OS Deviation Agreement
• JobRunner and FloorManager Server Best Practices
• Need Assistance?

Overview

Pacific Solutions bases these requirements on:

• Claris FileMaker baseline recommendations
• Internal development and testing
• Real-world production performance review

Pacific Solutions recommends that servers be designed with business use in mind and include a three-year extended onsite warranty.

Bare Metal Servers versus Virtualized Servers

Pacific Solutions supports both bare metal and virtualized servers. For optimal performance, a bare metal, non-virtualized environment is recommended.

In a virtualized environment, the virtual machine running the JobRunner/FloorManager server competes with the host hypervisor and other virtual machines for the host's available resources.

In a bare metal environment, all host resources are available to the JobRunner/FloorManager server, providing optimal performance.

Claris provides general baseline hardware and operating system recommendations, but the customer is ultimately responsible for providing and maintaining adequate hardware and monitoring the system to determine the load being placed on the physical hardware.

Based on Pacific Solutions testing and production experience, the server, workstation, and network requirements outlined in this article should be followed.

Cloud Servers

Cloud server instances such as Microsoft Azure, Amazon Web Services, Oracle Cloud, Google Cloud, and similar platforms are supported when they meet the applicable:

1. Server requirements
2. Workstation requirements
3. Network requirements

Server Lifecycle

Pacific Solutions bases its server specifications on an expected lifecycle of approximately three to five years.

A server may continue operating for years beyond this lifecycle but may no longer provide optimal performance.

Depending on the server design, individual components such as storage drives, memory, or the operating system may be upgraded or replaced to extend the life of the existing server while maintaining JobRunner/FloorManager performance.

Other components, most notably the processor, may not be practical to upgrade and may require replacement of the server.

Server Exclusivity

The JobRunner/FloorManager server is resource intensive.

To ensure optimal performance, Pacific Solutions recommends that the server not be used to host unrelated applications such as:

• Microsoft Exchange
• ProSeries
• Microsoft SQL Server
• Other resource-intensive applications

If a physical host will be used both as the FileMaker Server and as a Remote Desktop environment for users, Pacific Solutions recommends configuring a dedicated physical server or virtual machine for the Remote Desktop Session Host.

The FileMaker Server environment and the FileMaker user desktop environment should remain isolated from one another.

This is especially important for organizations using integrations such as Tableau or JotForm. A shared environment may result in interruptions of service.

Server Sizing

Pacific Solutions categorizes JobRunner/FloorManager servers as follows:

The peak, or maximum concurrent, number of users is the first criteria evaluated.

The total number of ledger entries and the size of the JobRunner/FloorManager database set are then reviewed to determine whether the server should be sized upward.

A server should be sized up when either the ledger count or database size requires a larger category. Pacific Solutions does not recommend sizing a server down.

If your company is new to JobRunner/FloorManager, ledger count and database size will generally not affect the initial server size because the number of ledger entries and database size will initially be relatively small.

Peak Number of Users

The peak number of users is the maximum number of users who will be accessing JobRunner/FloorManager at any one time.

For example, your company may have 15 JobRunner/FloorManager user licenses, but if only five users are normally accessing the system at the same time, your company's peak number of users is five.

It is important not to underestimate the peak number of users because doing so may affect JobRunner/FloorManager performance.

For example, a Small server may be appropriate for five concurrent users. If 10 users regularly access JobRunner/FloorManager at the same time, a Medium server would provide better performance based on user count alone.

Total Number of Ledger Entries

The total number of ledger entries is one of the factors used to determine whether a company should size up its server.

For assistance determining the total number of ledger entries in your environment, contact Pacific Solutions Support.

Size of Database Set

The size of the database set is the amount of disk space occupied by the full set of JobRunner/FloorManager databases.

For most companies, the daily offsite backup directory is located at:

C:\FMCloud

1. Open File Explorer and locate C:\FMCloud.
2. Right-click the folder and select Properties.
3. Review the Size on disk value.
4. Select Cancel to close the Properties window.

Your company may need to size up the JobRunner/FloorManager server if the database set size requires a larger server category.

Server Sizing Examples

Example One

If your company has 10 concurrent users, a Medium server would normally be recommended. If the database set is 30 GB, a Large server would be required instead.

Example Two

If your company has five concurrent users, a Small server would normally be recommended. If the total ledger count is 200,000, a Small server would still be appropriate. If the database set is 15 GB, sizing up to a Medium server should be considered for optimal performance.

Example Three

If your company has five concurrent users, a Small server would normally be recommended. If the total ledger count is 500,000, a Medium server would be recommended. If the database set is 16 GB, a Medium server would still be appropriate.

Usually, the ledger count and database size align closely. When they do not, the server does not need to be sized up twice.

Server Specification Baseline Requirements

Small Server

The operating system drive must maintain at least 20% free space.

For virtualized environments, the virtual disk should be configured as Thick Provision Lazy Zeroed.

Pacific Solutions supports VMware ESXi 7.0u2 or later for virtualized JobRunner/FloorManager server environments. Hyper-V and Proxmox are not recommended for this deployment.

Windows Server Datacenter is compatible with FileMaker Server 20 (FileMaker 2023) but has not been fully tested by Pacific Solutions.

Medium Server

The operating system drive must maintain at least 20% free space. For virtualized environments, the virtual disk should be configured as Thick Provision Lazy Zeroed.

Large Server

The operating system drive must maintain at least 20% free space. For virtualized environments, the virtual disk should be configured as Thick Provision Lazy Zeroed.

Extra Large Server

For companies with more than 30 peak concurrent users or more than 1,600,000 ledger entries, contact Pacific Solutions for assistance determining the appropriate server specifications.

An Extra Large server may be required.

Server Networking

Speed

Pacific Solutions recommends reliable internet service with:

• At least 25 Mbps download speed
• At least 10 Mbps upload speed

Network Switches

If a network switch is part of your company's network environment, it should support Gigabit Ethernet.

For new network cabling, Pacific Solutions recommends Category 6 or higher cabling.

Wired and Wireless Networks

For local network stability and performance, Pacific Solutions recommends wired network connections rather than wireless connections.

If wireless networking is required, Pacific Solutions recommends Wi-Fi 6 certified routers or access points.

For larger facilities, consider a properly designed mesh or multi-access-point wireless system.

Pacific Solutions does not recommend Wi-Fi range extenders because they may reduce network performance and introduce radio interference.

Workstations using Wi-Fi should support at least Wi-Fi 5, also known as 802.11ac.

WAN, LANs, and VPNs

JobRunner/FloorManager performance is limited across WAN connections.

The desktop JobRunner/FloorManager application should be launched from a system located on the same physical LAN as the JobRunner/FloorManager server.

If working remotely or from a different facility than the JobRunner/FloorManager server, use one of the following methods:

1. Remote into an office workstation that resides on the same physical LAN as the JobRunner/FloorManager server, then run JobRunner/FloorManager from that workstation.
2. Remote into a Remote Desktop Session Host that resides on the same physical LAN as the JobRunner/FloorManager server, then run JobRunner/FloorManager from that server.

Cloud Networks

For companies using a cloud-hosted server, Pacific Solutions cannot guarantee application performance when FileMaker traffic crosses a virtual private network or other WAN connection.

Confirm with your cloud provider that the virtual network, such as an Azure VNet or AWS VPC, provides appropriate LAN performance and does not introduce bottlenecks between the FileMaker Server and user environment.

Server Firewall Requirements

JobRunner/FloorManager Server requirements follow the applicable FileMaker Server firewall requirements.

FileMaker Server uses several ports for web services, Admin Console access, FileMaker client communication, ODBC/JDBC connectivity, and internal communication.

Workstation Requirements

The JobRunner and FloorManager user environment must run on individual workstations or supported Remote Desktop hosts that are separate from the FileMaker Server.

Workstations that do not meet these requirements may experience reduced performance.

Windows Workstations

Mac Workstations

Printers

The use of printers is optional.

Pacific Solutions recommends using an HP inkjet or laser printer where possible. HP ink and toner are widely available, and HP printers generally provide reliable network printing.

The printer should support use in a network environment.

Hardware and OS Deviation Agreement

The agreement allows JobRunner/FloorManager to be used on the selected hardware or operating system while acknowledging that the environment does not meet Pacific Solutions recommendations.

When a deviation exists, Pacific Solutions may be unable to support underlying FileMaker database or performance issues until compliant hardware and operating system conditions are restored.

JobRunner and FloorManager Server Best Practices

Windows Updates

Pacific Solutions recommends the following:

1. Querying, downloading, and installing Windows updates should occur outside normal business hours.
2. Before applying operating system updates or restarting the server, confirm that FileMaker Server and its hosted databases are protected and follow your established FileMaker Server maintenance procedure.
3. Confirm that FileMaker Server services and hosted databases are operating normally after maintenance is complete.

FileMaker Updates

Do not install FileMaker Server updates unless instructed by Pacific Solutions.

Pacific Solutions tests FileMaker updates for compatibility with JobRunner and FloorManager before recommending deployment.

If you receive a FileMaker update notification, select Skip this version and contact Pacific Solutions if you have questions.

Virus Scanners

Exclude the following directories and their child directories from live antivirus scanning:

• C:\Pacific
• C:\Program Files\FileMaker Server
• C:\conf

Review antivirus exclusions with your IT provider and Pacific Solutions before implementing changes.

Backups

After-hours backups of the JobRunner and FloorManager server should occur daily.

Pacific Solutions recommends following the 3-2-1 backup rule whenever possible.

At minimum, maintain:

1. A local backup of:
   • C:\conf
   • C:\FMCloud
2. An offsite backup of:
   • C:\conf
   • C:\FMCloud

Backup jobs should be monitored regularly to confirm that backups are completing successfully.

Need Assistance?

If you need assistance determining the appropriate server size, reviewing an existing environment, or confirming JobRunner/FloorManager system requirements, contact Pacific Solutions Support at pacificsolutions-support@cyncly.com.