aACE Server Installation Guide - FileMaker 13

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: Technical Specifications for FileMaker Server 13.
    • If applicable: confirm that the operating system for OS X is the minimum required for FileMaker Server 13: OS X 10.8.5
    • Confirm that all Mac software and server updates have been applied
  • Confirm you have the administrator password to the computer as it will need to be entered several times throughout the process.
  • Confirm that you have a valid FileMaker Server license.
  • Confirm that you have FileMaker Pro licenses for all users.
  • Server must have a static IP address or local domain assigned.
  • Java must be installed and current. www.java.com
  • 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.
  • Download any needed software installers by clicking the appropriate link here. You will need the following for this install:
    • FileMaker Server 13
    • FileMaker Pro 13 Advanced
    • FileMaker Server 12 (If you are upgrading to FM13 you will need the FM12 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.

Installation procedure:

  • If you are installing FileMaker 13 onto the same machine that hosted FileMaker 12 databases, you must:
    • Backup your existing FileMaker databases and archive them.
      • Log into the Admin Console and stop FileMaker Server by clicking the red "Stop Server" button in the top left. Proceed when the green "Start Server" button is no longer grayed out. Do not start the server again; this indicates the server is fully stopped.
      • Navigate to /Library/FileMaker Server/Database Server/Data/ and archive the entire Databases folder.
    • Uninstall FileMaker Server 12. You will need to download the FileMaker Server 12 installer for the uninstall process.
  • If FileMaker Pro is open, quit. (For example, a client timer may be running, so press Stop and close out of FileMaker Pro before proceeding.)
  • Install FileMaker Server 13 per FileMaker's documentation: http://www.filemaker.com/support/product/documentation.html
    • Select single machine configuration.
    • Select "fmserver" for the FMS user account, unless your implementation requires otherwise.
    • When prompted, run Deployment Assistant.
    • Please provide AGIS with the user name and password for logging into the Admin Console.
      • Unless otherwise noted, please use "Administrator" for the user name.
      • Unless otherwise noted, please use a tool such as http://passwordsgenerator.net to generate the password. Password length: 15; no symbols; include lowercase letters; include uppercase letters; include numbers; exclude similar characters; generate on the client.
    • 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, FMS13 Admin Console will launch automatically.
  • If the Admin Console is not open, launch the Admin Console by navigating to: http://localhost:16001/
  • 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.
      • Check 'Require secure connections'.
      • Check 'Enable progressive downloading'.
    • Database Server > Server Plug-Ins
      • Check 'Enable FileMaker Script Engine (FMSE) to use plug-ins'.
      • Check 'Allow Install Plug-in File script step to update server plug-ins'
      • Decompress the archive containing the Plug-in Pack and place the OS-specific versions of each plug-in in /Library/FileMaker Server/Database Server/Extensions. (In other words, Mac versions of the plug-ins [.fmplugin] on Mac servers; Windows plug-ins [.fmx] on Windows.) 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.
      • Enable each plug-in that appears in the list.
  • Remove default sample database.
    • Navigate to Activity > Databases .
    • Select the folder icon in the top right and choose 'Close All'.
    • Highlight 'FMServer_Sample'. Then select the folder icon in the top right and choose 'Close'. Then select the garbage icon and choose 'Remove'. Also remove the 'Sample' folder.
  • Install FileMaker 13 Advanced and upload aACE files
    • If using AGIS's license enter "For AGIS, LLC Use Only" as the user name.
    • Add FileMaker 13 Advanced to dock.
    • Decompress ZIP archive containing aACE system.
    • In FileMaker, select File > Sharing > Upload to FileMaker Server, and select the host.
    • By default the files will be uploaded to 'MainDB'. Create a sub-folder called 'aACE' and select this for the upload.
    • Choose the uncompressed files and select Upload.
  • 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.
    • In the Admin Console, navigate to Schedules.
    • Type: Back up databases
    • Databases: All databases
    • Backup Options:
      • Location: .../Backups/Daily/
      • Maximum number of backups to keep: 7
      • Enable 'Verify backup integrity'
      • Enable 'Clone the backup file'
    • Details:
      • Frequency: Daily
      • Schedule Details: Start Date should be the current date; do not set an end date.
      • Repeat Settings: Start Time should be 11:30PM; do not repeat the task.
    • Options: Schedule Name: 'Daily'; Do not send email notification; Enable the schedule.
  • Create manual backup schedule
    • Type: Back up databases
    • Databases: All databases
    • Backup Options:
      • Location: .../Backups/_ManualBackup/
      • Maximum number of backups to keep: 1
      • Do not enable 'Verify backup integrity'
      • Do not enable 'Clone the backup file'
    • Details:
      • Frequency: Once Only
    • Options: Schedule Name: _ManualBackup; Do not send email notification; Do not enable the schedule.
  • Test all backup schedules
  • Create script schedule 'Automation Cycle A'
    • Type: FileMaker Script
    • Database: aACEv4v0_Scripts.fmp12; Account Name: 'management' with associated password assigned by AGIS.
    • FileMaker Script: Automation Cycle; Set a time limit of 120 minutes and enable "Abort schedule if..."
    • Details:
      • Frequency: Daily
      • Schedule Details: Start Date should be the current date; do not set an end date.
      • Repeat Settings: Start Time should be 12:00AM; repeat the task every 1 minute; continue until 11:14PM.
    • Options: Schedule Name: 'Automation Cycle A'; Do not send email notification; Enable the schedule.
    • Duplicate twice for 'Automation Cycle B' and 'Automation Cycle C', which will be identical except for the name.
  • Create script schedule 'Automation HALT'
    • Type: FileMaker Script
    • Database: aACEv4v0_Scripts.fmp12, Script Name: Automation HALT; Account Name: 'management' with associated password assigned by AGIS.
    • Details:
      • Frequency: Once Only
    • Options: Schedule Name: Automation HALT; Do not send email notification; Do not enable the schedule
  • Test automation schedule by running it and confirming that it ends and updates the next run time.
  • Confirm Automation Cycle A, Automation Cycle B, Automation Cycle C, and Daily are enabled. Confirm 'Allow enabled schedules to run' is checked.
  • Turn off FileMaker Server and restart machine.
  • Check the schedules to see if they still show 12:00am as the start. If they don’t, turn off FileMaker server and restart machine again.

 

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