aACE Server Installation Guide - FileMaker 11

Pre-installation checklist:

  • A dedicated computer is recommended for hosting FileMaker Server, meeting FileMaker's system requirements.
  • A valid FileMaker Server license.
  • FileMaker Pro licenses for all users.
  • Server must have a static IP address or local domain assigned.
  • FileMaker uses a proprietary network protocol and communicates on ports 5003 and 5353.  No other network services are needed.
  • MAC OS Servers must have automated 'Check for Updates' feature disabled.


Installation checklist:

  • Download any needed software installers at: http://agisllc.com/_software
    • FileMaker Server 11
    • FileMaker Pro 11 Advanced
    • aACE plug-in package
    • aACE4 launcher
  • MAKE SURE YOU HAVE LATEST SOFTWARE INSTALLERS - Cross reference with FM website http://www.filemaker.com/support/downloads/
  • If _software page is not up to date, be sure to make a note of it and update page ASAP.
    • Select single machine configuration.


    • When prompted, run Deployment Assistant.
    • Common server names used are "aACE Server" or local domain name to server computer.
    • If asked, do not enable ODBC/JDBC, nor Web Publishing.
  • Launch Admin Console by navigating to:
  • In Admin Console, configure settings:
    • General Settings > Admin ConsoleDisable 'Enable FileMaker Server to check for updates'.
    • Database Server > FileMaker Pro ClientsEnable 'Allow FileMaker Pro client to download updates automatically'.
    • Database Server > Databases
      • Set 'RAM reserved for database cache' to a multiple of 64, to approximately 80% of the maximum allowed cache size.  (e.g. 80% of 480MB max = 384MB reserved)
      • Set the 'Cache flush distribution interval' so that 64MB of reserved cache RAM is flushed every minute.  (e.g. 384MB reserved ÷ 64 = 00:06 minutes)


    • Database Server > Security - Include the following settings for additional security to your aACE system.
      • Change File Display Filter to 'List only the databases each user is authorized to access'.
      • Check 'Secure Connections to Database Server'.
    • Database Server > Server Plug-InsCheck 'Enable FileMaker Server to use plug-ins'.
  • Install aACE plug-in package


    • Decompress aACE plug-in package.
    • A: Open the AutoUpdate folder from the plugin package
    • B: Open the folder: /FileMaker Server/Data/Databases/AutoUpdate/
    • Copy the entire contents from AutoUpdate folder A to AutoUpdate folder B, so that they are identical.  (Final folder state shown above)
    • Duplicate the plugins 'mailit' and 'PHP' for the current OS (plugins ending in '.fmplugin' is for OS X and '.fmx' for Windows) and install into folder: /FileMaker Server/Database Server/Extensions/
    • IN OS X, update the folder permissions on both AutoUpdate and Extensions folder so that they match the enclosing folders.  To update permissions of a folder:
      • Right-click a folder and select 'Get Info'.
      • In the Sharing & Permissions section, click the lock at the bottom and authenticate when prompted. (shown below)
      • Click the gear icon at the bottom and select 'Apply to enclosed items'.  (shown below)


    • Shut down FileMaker Server by pressing the red database button in the upper left corner of the Admin Console.
    • Start FileMaker Server by pressing the GREEN database button in the upper left corner of the Admin Console.
    • Verify that all server-side plug-ins are enabled in the section Database Server > Server Plug-Ins (as shown)Picture_24.png.


  • Adding the Admin Console to the dock (OS X only).
    • Quit the Admin Console.
    • Clear Java cache files by launching: /Applications/Utilities/Java Preferences
    • Click on Network tab > Delete Files button.


    • Enable all options and press OK.
    • Quit Java Preferences.
    • Launch Admin Console by navigating to:
    • If prompted to save the Admin Console, navigate to the Applications folder and rename to a simpler name such as 'FMS11'.
    • At the Admin Console login prompt, press Cancel (as this Admin Console session is server-hosted, not the one just downloaded).
    • Go to the Applications Folder and drag the 'FMS11' application to the dock.
    • Launch FMS 11 from the dock.
  • Remove default sample database.
    • Navigate to Databases section.
    • Select Action 'Close All'.
    • Highlight, then right-click file 'FMServer_Sample' and select Remove.
    • Highlight, then right-click folder 'Sample' and select Remove.


  • Upload aACE files
    • Decompress ZIP archive containing aACE system.
    • In Admin Console, click Upload Database.
    • Create subfolder 'aACE'.
    • Highlight 'aACE' and click 'Add Database'.
    • Select all databases from decompressed ZIP archive.
  • Determine locations for live and backup databases, on separate drives if possible.
    • When setting up an alternate drive for direct FileMaker backups, create a folder at: 'Your_Second_Drive/FileMaker Server Data/Backups/'.
    • In OS X, verify that the user 'fmserver' has write privileges to the new folder.
  • Create daily backup schedule
    • Type: Backup all databases
    • Name: Daily
    • Location: .../Backups/Daily/
    • Enable both: 'Verify backup integrity' and 'Clone the backup file'.
    • Maximum to keep: 14
    • Frequency: Daily.  Once per day, Start Time 11:30pm.




  • Create manual backup schedule
    • Type: Backup all databases
    • Name: _ManualBackup
    • Location: .../Backups/_ManualBackup/
    • Frequency: Once Only
    • Leave schedule disabled
  • Test all backup schedules
  • Create script schedule 'Automation'
    • Type: FileMaker Script
    • Target: aACEv4v0_Scripts.fp7
    • Account Name: 'management' with associated password assigned by AGIS.
    • Script Name: 'aACE Automation Cycle'
    • Frequency: Every day, every 1 minute between 12:00AM-11:29PM
    • Abort after 4 hours



  • Test automation schedule
  • Enable all schedules (except _ManualBackup).


  • Install FileMaker Pro 11 Advanced on server (for remote aACE maintenance).
  • Download aACE launcher and configure server IP address.
  • Test logging into aACE.
  • Navigate to aACE Preferences / Database Management and verify that the plugin versions match the respective version folder names in the Auto Update folder.
  • Click test on each plugin to insure that the auto update is working correctly.
  • Upload pre-configured launcher into aACE Prefs / Database Prefs.
Have more questions? Submit a request
Powered by Zendesk