Skeleton Key is an open-book management company and active player of the Great Game of Business. In addition to custom databases and applications, we also provide training and coaching for getting the most out of your existing systems and understanding your unruly data. Our team of consultants and developers do this by developing custom-fit software tools and reporting dashboards that help businesses find, use, and understand their data, freeing them to focus on and grow their core business. Skeleton Key helps turn complex, complicated, and outdated systems into true information platforms. This simple change made a significant difference for the website users who no longer encounter that ten-second delay. The same thing could be accomplished in a number of ways, such as the Laravel task scheduler or even a cron job. We then created a schedule in FileMaker Server to run the script every minute. In our case, we simply created a FileMaker script with an “Insert from URL” script step that calls a PHP page that loads a small amount of data from the FileMaker database. When we finally connected the dots and realized what was happening, the solution was obvious…we just needed to keep the database connection open constantly so that users never experience the delay. If additional requests are received while the connection is open, that connection will be reused and the three minute timer starts over. After the request is processed, the WPE will wait three minutes before closing the connection. When the FileMaker Server Web Publishing Engine (WPE) receives an XML or FileMaker API for PHP request, it opens a connection to the database and fulfills the request. As we investigated the reports of intermittent performance issues, we found that the first page a user accessed would sometimes take more than ten seconds to load. However, it turns out that this ten-second delay was also affecting our website. Ten seconds is not a big deal when you’re opening a database once per day. The solution has one of the more complex relationships graphs I’ve seen, and it takes over ten seconds for a FileMaker Pro client to open the hosted file. One particular site we built connects to a legacy FileMaker database that was built years ago by another developer. If you have a website that connects to a FileMaker database, this simple tip might help improve performance.

Need to read a filemaker pro database