To my knowledge, you have to create a filemaker file that will connect as a client to your hosted solution and launch the desired script.
We do this kind of thing by installing FileMaker Client on the server hosting the databases (this works well and runs fast due to no network bottlenecks).
We create an empty database (we call it FMBot.fmp12) and create a user account in it using the same credentials as an account in the target hosted DB (we use FMBot as the account and give it [Full Access] privileges). We then set the FMBot db to login automatically with that account and give it a script trigger (OnFirstWindowOpen) to launch a script.
That script then just calls a script in the hosted DB to run our FMServer-incompatible-tasks. Finally, once the script in the hosted DB completes, control returns to the FMBot DB which quits FMP Client.
We trigger this hourly or daily as required using TaskScheduler on PC or a LaunchDaemon job on MacOS, it doesn't require a user to be logged in and will run as a background task.
1 of 1 people found this helpful
To my knowledge, you have to create a filemaker file ...
You don't have to. It's just the way that is easiest to grasp for most FM developers.
There are other ways of doing the same thing from AppleScript on Mac and VBscript/PowerShell on Windows (using the FM ActiveX interface).
These methods are somewhat harder for the average FM developers but they offer more rrore error reporting capabilities for example if the business process is critical.