Deploying Custom Apps Flashcards
A scheduled back up can be set to run every hour during the day. What does FileMaker Server do with a file that has not changed between consecutive backups?
A scheduled backup checks to see if a file has been changed. If not, the schedule creates a hard link to a previous backup.
Progressive backups are a type of backup that can reduce the impact of backups on FileMaker Server performance. How does this backup type accomplish that?
Progressive backups start by making a complete backup of all databases and are stored in a folder of your choice. After that, the schedule only copies changed blocks from the hosted file to the backup folder every time it is run. A progressive backup keeps two backups—a timestamped file available for use and an in-progress copy that accumulates the changes.
FileMaker server can be installed on multiple machines: a master and one or many worker machines. In a multiple machine configuration, which elements of FileMaker Server are installed on the master machine? Which elements are installed on the worker(s)?
The components of FileMaker Server are: The Web Server, the Web Publishing Engine, Database Server, and the Admin Server. During a multiple-machine deployment, all the components are installed on the master machine, and the Web Server and the Web Publishing Engine are installed on each worker machine.
What information can be found by looking at the Top Call Statistics?
The Top Call Statistics log describes the 25 slowest client requests. You can see what a specific user was doing and how long it took to process the request in microseconds.
A script called “Process Data” performs some operation on the found set of data. It is called from a parent script called “Update Report”. The subscript runs as expected in FileMaker Pro Advanced using the Perform Script [Process Data] script step, but fails when it runs on the server using Perform Script on Server [Process Data; Wait for Completion]. It does not return the calculated data for the report. What might cause the script to run differently using Perform Script on Server?
When a script is run using Perform Script on Server, FileMaker Server opens a session and runs the script. This opening procedure will open to the layout specified in the File Options menu, as well as run any onFirstWindowOpen script triggers before running the actual “Process Data” script. If the script does not have a Go to Layout script step as well as the correct found record or set of records, it will attempt
to perform the steps on the layout and with the records the script lands on. To fix this, ensure that the subscript contains steps that navigate to the correct layout and find the correct records. To return data to the parent script, use the Exit Script step and pass the data as a Script Result.
When installing FileMaker Server in a multi-machine deployment, which do you install and configure first, the master or the worker(s)?
The master machine must be configured first.
What are the choices for deploying a custom app to FileMaker Go?
A custom app can be deployed in the following ways:
a. Hosted on FileMaker Server
b. Transferred to the device using iTunes
c. Transferred to the device using a sharing option such as Mail, AirDrop, iCloud Sharing or other third-
party sharing methods.
