On a vanilla Windows Server 2012 I first installed the latest version of 32-bit and 64-bit Java 6, on the understanding that ScriptMaster required 32-bit Java to run.
I then installed Filemaker Server 13 which installs Java 7, required to run the server.
On placing the 360Works_ScriptMaster.fmx64 in the Filemaker Server's Extensions folder and restarting the Filemaker Server I was delighted to see the plugin listed, and I was able to enable the ScriptMaster plugin, see attached screenshot.
All good so far BUT when I try to run a server-side script (either in web browser or with Filemaker client) which invokes a Groovy script using ScriptMaster, the cursor turns to busy and after two or three minutes a dialog pops up "The host's capacity was exceeded, try again later." and any subsequent invocations just pop the dialog straight up.
It's as if the server side is unable to instantiate the ScriptMaster "engine" for want of a better word, presumably because it tries but fails to locate/use Java 6.
When I have the same (or equivalent) setup on a Mac server, it works fine - and a simple Groovy script System.getProperty("java.version") reports 1.6.0_065 (the last release of Java 6 on the Mac).
So it appears as if it is not possible to get ScriptMaster working on a Windows platform with Filemaker Server 13.
Has anyone else reported this? Is it a known issue with some sort of workaround?
Finally , what are the plans for upgrading to Java 7 and 64-bit (for server)?
Great product, but I've run into a brick wall on this one: while I can develop with a Mac server, the production deployment (in March) will be on a Windows Server 2012 platform.