![]() ![]() It seems that the on-premise Linux version of FileMaker Server definitely deserves some attention from the performance perspective, especially for larger deployments with many concurrent users. And that’s where it starts to be interesting… What is the most important for a server software, however, is how it performs for multiple users. When I executed the test on server, it started showing that FileMaker Server may be performing slightly better on Linux than it is on Windows. Running the test over LAN from a 13-inch MacBook Pro (late 2015) took about the same time with both Linux and Windows version of FileMaker Server:īut it seems that here most of the execution time was consumed by the client, which was still the same. The test where I could find the biggest differences was modifying all the 1000 records either via Replace Field Contents, or using Set Field in a loop. Most of my tests did not reveal any significant difference between Linux and Windows yet, but I have to admit that 1000 records was too small data set to actually show something as many tests completed in less than a second. In addition to being better priced than Windows especially for hosting providers, Linux has some advantages for technically savvy server administrators, such as command-line control over SSH, not mentioning some core technologies the system is based on. Specifically, the distribution supported and recommended for this version is CentOS Linux 7.8. One of the long awaited features that FileMaker Server 19.1.2 finally turned to reality is the support for on-premise Linux installations. I just could not include the macOS version of FileMaker Server any more, because the minimum maOS version supported by FileMaker Server 19 is 10.14 Mojave and the latest version I could make reliably work on that machine was 10.13 High Sierra.įor now I have performed just a short series of tests, mostly with just 1000 records, using FileMaker Server 18v4 and later, but once I have the complete full test done, I will make the comparison with the old results as well, comparing the latest version of FileMaker with all the previous versions back to FileMaker 12. In order to be able to compare my test results even with the oldest results of my tests I performed on previous versions of FileMaker, I kept using the same test machine as in previous years, the Mac Pro (early 2008). Linux version seems slightly faster than Windows version, JavaScript is way faster than FileMaker calculation engine, and sorting on server can surprise you as much as it has surprised me. I have added these new versions to my performance lab and here are my first test results. It also finally brings version for Linux. ![]() The new FileMaker Pro brings some great new features and the new version of FileMaker Server is supposed to be more stable and faster. ![]() Please contact us if you’d like to discuss adding server-side automation to your FileMaker Pro solution.Claris has recently released FileMaker Pro 19.1.3 and FileMaker Server 19.1.2. NRG Software has utilized Snapshot Links to automate server-side reminders for common business needs like Reorder Emails, CRM follow-ups, etc. Problem solved! Using FileMaker Data File script steps to fix the Snapshot Link file ![]() We then write the file back to disk and send it out as an email attachment. The contents then have a simple subsitute to replace 127.0.0.1 with the valid FQDN of the host. Once saved, we open the file and read the contents. In the sample script below, we first go to the proper layout, record and sort order that we want the user to be on when they open the Snapshot Link. Using the Data File script steps that have been available since FileMaker 18, you can easily read in the Snapshot Link file, replace the IP number for 127.0.0.1, and then send the Snapshot Link in an email from a server script. Snippet from a Snapshot Link file showing the internal IP numbers Snapshot Links created using the FileMaker Pro application don’t have this issue because the links are built using the host used to access the database file, which should be a fully-qualified domain name (FQDN) if you’re using best practices. When these Snapshot Links are emailed to users, they throw an error when they try to open them. Often, the host IP is an internal IP number which is not accessible to the outside world. Have you tried to create Snapshot Links in your server scripts but they fail when users try to open them? When creating Snapshot Links with server-side scripts, the IP of the host is used to create them which leads to invalid Snapshot Links for clients running outside the local network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |