So to have a task processed by a server-side script you could have had to wait up to a minute. There was no obvious way to run a server-side script on demand, and schedules could not be set up for shorter period than one minute. One of the main drawbacks of server-side scripts has been that they had to be scheduled. FileMaker Server 12 also finally supported multithreading, enabling you to run a labor intensive server-side script without significantly affecting performance of connected clients. But realistically, it was not very easy and safe to use them until the release of FileMaker Server 12, when the server-side scripting engine was completely separated from the database engine to make sure that even a disaster such as plug-in crash does not affect the main database hosting functionality of FileMaker Server. Server-side scripts could also benefit from server-side plug-ins almost from the beginning… Well, officially. One of the few exceptions persisting, probably due to licensing issues, has been the Save as PDF script step, finally made available in FileMaker Server 16. At that time only a limited subset of script steps were compatible with server-side scripting, but some of the robot machines could finally be replaced by this feature.įollowing versions of FileMaker Server were slowly extending the set of script steps supported by server-side scripts, until now, when almost all meaningful script steps can be used server-side. Much better, safer, and correct in principle, solution was introduced with the release of FileMaker Server 9, the first version that allowed creation of server-side script schedules. Robot machine is a stand-alone FileMaker Pro client constantly connected to the FileMaker Server and regularly checking whether there is a task ready to perform. In the history, this need led to implementing a solution well known as a “robot machine”. But it was the FileMaker Server 13 that finally made this idea easy to implement. See Using the command line interface.The idea of being able to off-load time consuming tasks from FileMaker Pro to FileMaker Server is as old as the scripting abilities of FileMaker Pro, which were introduced with the FileMaker Pro 3 release. To change the limit for the number of simultaneous Perform Script on Server script step sessions, use the following CLI command: fmsadmin set serverconfig scriptsessions= number For a script that runs on the server, only 64-bit ODBC drivers are supported. See Viewing and downloading log files.įor server-side FileMaker scripts, the Get(AccountName) function initially returns the account name that the script was run under (specified when the schedule is created).įileMaker Server only: If you run a FileMaker script that uses the import ODBC script with a third-party ODBC driver, you need to use the 64-bit version of the ODBC driver. The Event.log file contains detailed information about errors or script steps that are skipped when FileMaker Server runs FileMaker scripts. Some script steps have options that are skipped, such as an option to show a dialog box. See Disconnecting clients from FileMaker Server. If you do not select this option and a FileMaker script stops responding, you can stop the script on the Databases page by stopping the script shown in the clients list. You can select End the schedule if the timeout is reached to stop the FileMaker script schedule if the script takes longer to run than the specified time limit, or if the Database Server stops. See Hosting databases.įor information about creating FileMaker scripts with script steps that are supported in a FileMaker Server script schedule, and how server-side scripts run, see FileMaker Pro Help. The script schedule you create to run the script must be on the same FileMaker Server deployment as the hosted database file. The script must be defined in a database file that is hosted on FileMaker Server. The script should include only script steps that are supported in a FileMaker Server script schedule. To run a FileMaker script on FileMaker Server: You use the Script Workspace in FileMaker Pro to build scripts by selecting from a list of FileMaker Pro commands, called script steps, and specifying options. Remove duplicate records before a scheduled backup Process and archive new transactions nightly Perform a field recalculation across all records FileMaker scripts that run on FileMaker Server can do simple or complex tasks such as: You create a schedule to run a FileMaker script schedule, specify the database and the FileMaker account to use to run the script, choose a script created in the database, and specify when to run the script. FileMaker Server can run FileMaker scripts that are created in hosted databases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |