It didn’t used to take 3 days, but that’s how long I’ve been working on it so far, on a fresh stock OS install, and still do not have a usable installation. It’s really becoming frustrating that Claris made setting up FMS this hard. Obviously there is something more to it than the instructions provided here. Restarting WPE, or even the whole machine, doesn’t help. It replies immediately showing that those commands are still their old values, and “fmsadmin GET CWPCONFIG” confirms it. These instructions don’t work at all for FMS18 or FMS19.Įvery time I issue an “fmsadmin set cwpconfig enablephp=true” or “fmsadmin set cwpconfig usefmphp=false” command, those settings don’t change, it just ignores me.
If you wish to enable the FileMaker provided version of PHP (as shown above) use fmsadmin SET CWPCONFIG USEFMPHP=true but given that FileMaker server is still shipping PHP 5.6 which reached end-of-life at the end of December 2018 and is no-longer supported (not even security fixes) you really, really, really shouldn’t be doing that! You can check the status of the CWP config using fmsadmin GET CWPCONFIG which will return something like this: EnablePHP = true fmsadmin SET CWPCONFIG ENABLEXML=trueĪnd you should now be ‘good to go’. So here’s what you need to do if you want to enable both PHP and XML.
In this post I’m looking at using the later because that’s how were working towards automating the deployment of an FMS using Ansible – I’ll post more on that once we’ve got the process solid, right now there are a still a few kinks to iron out when deploying to Windows! This leaves us with two options – the Admin API, or the fmsadmin CLI. One of the casualties of this process is there’s now no way to enable or disable XML or PHP from the admin console. At the same time they’re also rebuilding the FileMaker Server admin console. FileMaker is in the process of moving away from the XML and PHP interfaces and replacing them with the FileMaker Data API.
0 kommentar(er)
