So -- Server 14 -- does it now do these things?
1) Support Java 8 -- and any subsequent updates to Java?
2) Actually allow you to install it on an OS X server?
Thank you for your post.
FileMaker Server 14 will support Java 8, but OS X Server is not supported. For more information, see our Technical Specifications page at:
Really. After all this time, FMS 14 could not be designed so that it could be easily configured to run over some other ports (which would allow it to run on OS X Server?) Seriously?
Wait... maybe this *will* work? As I look through the install guide it states that the installer can let you specify different ports for the web service?
And -- from the guide -- it implies that server might work if you do this?
You do not need to enable the Apache web server that is installed with OS X, nor do you need to have the OS X Server application installed. In fact, the FileMaker Server installer creates its own instance of the Apache web server on both the master and worker machines and configures this web server to use port 80 for HTTP and port 443 for HTTPS (or the alternative ports you specify); on the master machine, the installer also configures its Apache web server to use port 16000 for Admin Console via HTTPS. If you have enabled the Apache web server that is already installed with OS X, the FileMaker Server installer prompts you to let it disable any existing website using port 80 or 443, or to specify alternative ports, before it can continue.
If you have the OS X Server application installed and use it to enable any HTTP services (for example, websites or the wiki), the existing Apache instance may be re-enabled after
FileMaker Server is installed. Therefore to ensure the Apache instance used by FileMaker Server works normally, you may need to configure any other HTTP services to use different ports from the ports that FileMaker Server uses, disable other HTTP services, or uninstall the OS X Server application.
Does Filemaker Server 14 allow the installation/use of intermediate SSL certificates?
Ooh, excellent question that I forgot about -- I'd like to know that, too. The "getting started" document does not address that one way or the other (unless I missed that...)
Julian Chapa and maser:
Nothing has changed in relation to certificates. The list of supported certificates remain the same. For the recent list of supported certificates, see Knowledge Base Article #11413:
The only change is that you can now import a certificate via the Admin Console, and if it is not one of the supported certificates, then an error code is generated.
Retrieving data ...