I may not be understanding things properly so go easy on a newbie

We have a database hosted on FMP Server Advanced. We also have remote clients (FMPro) and mobile clients (FMGo) connecting to it.

We have developed a plugin that we need to run against the database hosted on the server. This plugin provides some discrete functionality relating to JMS queues. Works great when running in FMPro on the desktop.

Question: I assume that in the Server scenario the plugin runs on the client even though the DB is loaded remotely (since the plugin is not using scheduled actions).

Problem: In this case are my Go clients Out Of Luck? Meaning, Go Clients do not have access to the Plugin Provided APIs?

Would a solution be to have Server->FMPro->Go client (have go clients connect to fmpro which is serving the DB from the server)? In this case the plugin would be running on the FMPro client rather then the server and the plugin would be available.

Tx, this is vexing me.

John-

Plugins always run on the client. FileMaker Go does not support plugins, and so your users would not be able to use scriptmaster functions in filemaker go.

Depending on what you are doing, it may be possible to set up your scripts which use scriptmaster as server scheduled scripts, and then have filemaker go set flags in the records to tell the server which records to execute the scripts on when the schedule runs.

Aren't calculated fields that rely on a plug-in, calculated on the server? For example, the Demo::id field in ScriptMaster.fp7 Wouldn't this work if a new record was created via Go, as long as the server had ScriptMaster plug-in installed?

This is our chosen way forward I think. I don't like making FMP records stateful but in this case I think its our only option.

Everything else will still use the existing plugin to integrate FMP and our JMS queues and we'll just carefully curate what the Go Clients can do.

Tx!

John-

Depending on what you are doing, it may be possible to set up your scripts which use scriptmaster as server scheduled scripts, and then have filemaker go set flags in the records to tell the server which records to execute the scripts on when the schedule runs.

The server only supports scheduled action plugin workflow, not realtime calculations (that I can see) sine those only run on the client.

maybe.. Feeling my way around in the dark on this.

J

Aren't calculated fields that rely on a plug-in, calculated on the server? For example, the Demo::id field in ScriptMaster.fp7 Wouldn't this work if a new record was created via Go, as long as the server had ScriptMaster plug-in installed?

The server only supports scheduled action plugin workflow, not realtime calculations (that I can see) sine those only run on the client.

That is correct, I was suggesting that you use a server scheduled script to perform the calculations. It won't be real time, but the calculations may be evaluated every minute, five minutes, hour, twice a day, or however often you set it to run.

When you are performing a find in filemaker pro the calculation is done on the server. When you are just browsing a record or running a script it is calculated on the client. Server scheduled script calculations are performed on the server, and IWP and CWP calculations are performed in the WPE, which is a separate plugin deployment.

Sounds like the right path. For now we are going to cron a tool that checks for a set status field from the few stories that the mobile client participates. Our deadlines loom but we'll move to scheduled actions in a month or two once the rest of the kinks are ironed out.

For what its worth: JMS + FMP has been a big win for us, highly recommended.

Tx everyone

John-

That is correct, I was suggesting that you use a server scheduled script to perform the calculations. It won't be real time, but the calculations may be evaluated every minute, five minutes, hour, twice a day, or however often you set it to run.

When you are performing a find in filemaker pro the calculation is done on the server. When you are just browsing a record or running a script it is calculated on the client. Server scheduled script calculations are performed on the server, and IWP and CWP calculations are performed in the WPE, which is a separate plugin deployment.