2 posts in this topic
By Richard Fincher
I recently upgraded my Filemaker Server 13 to Filemaker Server 14.
To get the new version to install, I had to downgrade my Java8 from u113 to u67 (separately installing the old Java version, not allowing the FMS installer to install Java itself). I also had to fiddle around to make sure it was running the httpd which comes with FMS and not the one bundled with Mac OS X El Capitan.
My question is, am I now save to upgrade Java back to the latest version. I'm not anticipating needing to install FMS14 anytime soon, but does the "Deployment" part of FMS use Java, and if so, is it similar fussy about which version?
I read that the new 3.01 version does not require Java.
When I run FMPAv16 on my Mac (10.11.6) and use the sample Email database it works just fine and I see nothing related to Java. I had the older v2.12 plugin installed on here and have just updated to v3.01 today.
When I run FMPAv16 on a different Mac (10.11.6) and install the v3.01 plugin (never had the plugin installed on this machine before today) and run the sample database a Java App runs without any windows, Just visible in the lower right dock and its single menu is titled "Java"
Any ideas as to this oddity?
I am working on a project which requires me to make SOAP calls from FileMaker.
I have successfully done that in the past thanks to ScriptMaster ability to handle that. It works beautifully.
The new project now requires me to include a client certificate - issues by the SOAP API provider - in each requests. The documentation on their side is fairly scarce ("Install the certificate on your host" !).
I have no idea how to handle that but something tells me that there is no reason why it would not be possible to "include" the certificate in the Groovy bit of the plugin...
Any idea anyone ?