When you execute a script server-side, either through Perform Script On Server or through a server-side script schedule, FileMaker Server will add an entry to its Event.log for every script error that it encounters while running the script.
Scripts that you run through the FMSE script engine (used by the Perform Script on Server script step and by server-side schedules) now support the Set Error Logging script step.
The setting is on by default, meaning that your server will allow the logging initiated by the script step. If you want to prevent scripts from using the logging script step, then you can toggle the setting off.
Sync multiple FileMaker Servers for load balancing and clustering or to speed up slow connection to FileMaker Server. Using MirrorSync to cluster FileMaker Servers running side-by-side can increase server availability for your mission critical solution. Through data replication, you can ensure server reliability by balancing loads and handling server failure.
MirrorSync can sync directly between FileMaker Go and any supported server database, including MySQL, Sequel Server, Oracle, DynamoDB, Amazon RedShift, Salesforce, and any JDBC-compatible database. You will need FileMaker Server running for the configuration process, but the actual synchronization script will communicate from FileMaker Go MirrorSync server Any supported database server. Even container fields are supported; they are stored as BLOB data on an SQL server, or on S3 for DynamoDB.
Almost none; the Data API is used to initiate the MirrorSync script on the server. After that the actual data transfer is done between the MirrorSync script on FileMaker Server and the MirrorSync web application using the Insert from URL script step.
IS&T offers cost-effective managed FileMaker hosting for departments, labs, and centers through its Managed Servers service. IS&T strongly recommends using IS&T-managed servers for your FileMaker hosting needs at MIT, particularly for those without server administration skills or resources.
FileMaker is a cross-platform relational database application from Claris International, a subsidiary of Apple Inc. It integrates a database engine with a graphical user interface (GUI) and security features, allowing users to modify a database by dragging new elements into layouts, screens, or forms. It is available in desktop, server, iOS and web-delivery configurations.
Version 4.0, introduced in 1997, added a plug-in architecture much like that of Adobe Photoshop, which enabled third-party developers to add features to FileMaker. A bundled plug-in, the Web Companion, allowed the database to act as a web server. Other plug-ins added features to the interface and enabled FileMaker to serve as an FTP client, perform external file operations, and send messages to remote FileMaker files over the Internet or an intranet.
On September 27, 2016, FileMaker Cloud was introduced, including a Linux server (CentOS), which was offered exclusively through the Amazon Marketplace. In November 2019, FileMaker Cloud was reintroduced as a software as a service product offered directly from Claris for FileMaker Pro 18.0.3 using FileMaker Server Cloud 2.18 service on Amazon servers, but managed by Claris instead of through the Amazon Marketplace, and making use of the new FileMaker ID authentication.
PCI maintains a healthy stable of compatibility for FileMaker versions 11 through 14 and our customers always get the choice as to which server version they would like to be on and in what part of the country for their maximum benefit. PCI has long been known for providing the highest level of personalized hosting support for our customers using the latest technologies while tirelessly ensuring that our machines are running the latest versions of server and the OS and with the best in class hardware/software available.
aa06259810