aACE Server Installation Guide - FileMaker 12

Pre-installation checklist:

  • A dedicated computer is required for hosting FileMaker Server for two reasons: 1) performance will be impacted if the server is responsible for multiple functions and 2) AGIS will need full access to the machine for ongoing support and development. Additional server requirements can be found here: System Requirements for FileMaker Server 12.
  • 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 port 5003. Depending on the implementation or if additional FileMaker-based solutions are being used, additional ports may be needed. Please note that port 5003 needs to be directed to the specific database-hosting computer within the firewall.
  • MAC OS Servers must have automated 'Check for Updates' feature disabled.
  • If you are installing FileMaker 12 onto same machine that hosted FileMaker 11 databases, you must:
    • Backup your existing FileMaker databases and archive them.
    • Uninstall FileMaker Server 11. You will need to download the FileMaker Server 11 installer for the uninstall process.

 

Installation checklist:

  • Download any needed software installers by clicking the appropriate link here. You will need the following for this install:
    • FileMaker Server 12
    • FileMaker Pro 12 Advanced
    • FileMaker Server 11 (If you are upgrading to FM12 you will need the FM11 installer to uninstall the older version.)
    • MAKE SURE YOU HAVE THE LATEST SOFTWARE INSTALLERS - Cross reference with FM website http://www.filemaker.com/support/downloads/
  • Download the plug-in pack here.
  • Confirm you have a ZIP archive containing the aACE system. This should be provided by your FileMaker developer if that is not AGIS.
  • Confirm you have the "management" password to your copy of aACE. This should be provided by your FileMaker developer if that is not AGIS.
  • Install FileMaker Server 12 per FileMaker's documentation: http://www.filemaker.com/support/product/documentation.html
    • Select single machine configuration.
    • When prompted, run Deployment Assistant.
    • Unless you're re-installing FileMaker Server, choose "No, perform a clean installation".
    • Please provide AGIS with the user name and password for logging into the Admin Console.
    • Common server names used are "aACE Server" or local domain name to server computer.
    • When prompted do not enable ODBC/JDBC, unless your implementation requires it.
    • When prompted do not enable Web Publishing, unless your implementation requires it.
After you have finished with Deployment Assistant, FMS12 Admin Console will launch automatically. You will be prompted to register Filemaker Server and test the deployment.
  • Launch Admin Console by navigating to: http://localhost:16000/
  • In Admin Console, configure settings:
    • General Settings > Admin Console - Disable 'Enable FileMaker Server to check for updates'.
    • 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)
    • 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-Ins
      • Decompress the archive containing the Plug-in Pack and place the entire contents in the Extensions folder of the FileMaker Server > Database Server directory. The plug-ins should be placed directly in this folder with no additional folder structure.
      • Restart FileMaker Server. Note this does not require restarting the machine.
      • Check 'Enable FileMaker Server to use plug-ins'.
      • Check 'Allow Install Plug-in File script step to update server plug-ins'
      • Enable every plug-in the appears in the list.
  • 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.
  • Restart the machine. When the machine is restarted, re-launch the Admin Console and continue with what follows.
  • 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. A Daily backup schedule is generated automatically upon install, however it will need to be adjusted with the settings outlined below. Additional backup schedules can also be created if necessary. Depending on how active the database is and how catastrophic a failure would be, morning and mid-day backups may be needed. Keep in mind that performance is impacted by several factors, including the frequency of backups, but a robust server may be able to successfully handle backups as frequently as every 30 minutes.
    • 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 by running it and confirming that it ends and updates the next run time. Additional automation schedule testing will be required below once FileMaker Pro is installed on the machine.
  • Enable all schedules except "_ManualBackup".

 

Post-installation checklist:

The server-side installation is now complete, but the following must also be completed in order for ease-of-use (client-side requirements) and ease-of-mind (offsite backups).

Have more questions? Submit a request
Powered by Zendesk