mac Installing FileMaker Server 13 On Mac with Server

[Goetch]

I have been reading through the documentation about installing FileMaker Server 13 on OSX.  I only have one server at my location and that also runs my open directory and internal web services.   Generally I use opendirectory groups for my soultion permissions.  Going by the documentation I do not see a way to install FM Server 13 on this machine since by default Server.app uses ports 80 and 443 for it's own "Server" website. 

 

In the documentation on Page 72 it says my options are to configure the web services on Server.app to use different ports, I do not beleive this can be done, so the other option is to uninstall server.app, also not really an option...  So if I go by this documentation my only real option is to purchase a new machine to be my filemaker server... 

 

 

So is there a way to install FM Server 13 on a Mac with running Server.app and have both function?

[laudmusic]

Same issue here. Been trying to work around it all weekend to no avail.

[Goetch]

I have been able to get both server.app and FMS to work on the same server.  I can not recommend doing this in a production enviornment, but this may be suitable for a development enviornment.   One problem is that server.app and FMS will overwrite the ocnfiguration files if you chnage any settings in either.  For those who would like to teest this out... 

 

In a nutshell, the machine will need 2 static ip address, just go to system prefs and go to network and click the + choose your curretn interface and assign a static ip address. 

 

Create a dns entry something like fiemaker.yourdomain.com and point it to the new ip address.

 

Shut off all server.app websites including profile manager, calendar, websites, and wiki.

 

install FMS allow FMS installer to disable the ports 80 and 443

 

Edit the server.app apache config files to listen on the original ip address I think you need to edit 2 files /Library/Server/Web/config/apache2/httpd_server_app.conf  and /Library/Server/web/config/apache2/sites/virtual_host_global.conf

 

Now you need it edit the FMS config files to listen on your new ip address. 

 

/Library/Filemaker server/HTTPServer/conf/httpd.conf

/Library/Filemaker server/HTTPServer/conf/extra/httpd-ssl.conf

 

For good measure I also edited the file /Library/Filemaker Server/HTTPServer/bin/httpctl and changed the hostname variable to the dns hostname I gave filemaker (example: SERVER_NAME="filemaker.yourdomain.com")

 

Keep a backup copy of the files you editied because both server.app and FMS may overwrite the files if you make any changes to either....

 

go into server.app and restart your web services including, profilemanager, calendar, wiki and web sites. 

 

(you may need to restart) test yourdomain.com should go to your internal sites and filemaker.yourdomain.com should go to the filemaker websites.

 

For php to work with filemaker you may need to edit more configuration files, I am still working on getting PHP to work...  However I ahve been able to test webdirect...

 

There may also be issues with using the server.app sites and they may take up a concurrent connection, I am still testing this... But I think if you go to your profilemanager site it may use a concurrent connection.... 

 

This is posted as-is and is meant for development only.. 

[Larry Goldman]

FMS13/OS X Server conflict is a show-stopper for me.

 

What we need (at minimum) is a way to configure the Filemaker web-direct ports so it can co-exist with other web servers on the same hardware.

[HazMatt]

I installed FileMaker Server 13 the other day and was annoyed when I got the prompt.  I wasn't aware of this requirement, and it makes it all the more difficult because they want you to uninstall the old FileMaker Server before installing the new one (so I'd have to re-install the old FMS if I didn't like it).

 

I ended up going ahead with the installation which disabled OS X Server's web service.  I only had a few pages that weren't that important, but now I have to figure something else out.  

 

On the plus side, no more Java.

[Larry Goldman]

I installed FileMaker Server 13 the other day and was annoyed when I got the prompt.  I wasn't aware of this requirement, and it makes it all the more difficult because they want you to uninstall the old FileMaker Server before installing the new one (so I'd have to re-install the old FMS if I didn't like it).

 

I ended up going ahead with the installation which disabled OS X Server's web service.  I only had a few pages that weren't that important, but now I have to figure something else out.  

 

On the plus side, no more Java.

What you lose by installing FMS 13 is OS X Server's Profile Manager, Wiki, and Websites. Gone with Profile Manager is also the mobile device management functionality.

 

It is not odd that FileMaker, a wholly-owned subsidiary of Apple, sells a product that conflicts with Apple's, so that customers have to choose one or the other?

[HazMatt]

It is not odd that FileMaker, a wholly-owned subsidiary of Apple, sells a product that conflicts with Apple's, so that customers have to choose one or the other?

 

Yes, it is odd.  In fact, I hope to be using a Windows server for FileMaker Server in the next couple of months.  Screw OS X Server!  Gosh it makes me sad to type that.

[Ocean West]

I had some issues with my install of FMS - and Mavericks Server, but then I realized that when Mavericks was released I and applied it on top of Mountain Lion.

 

So I decided to format the drive completely and reinstall Mavericks - then installed FMS - Then installed the Server App. so far every thing is working much better.

 

According to FMS install Guide, it said after install you can reactivate the Web Services on server app - however i haven't bothered yet ( as it's just my home server ) plus I plan to reinstall MAMP for that process. 

[Flopper]

Forget about Windows Server 2012, same issue, it wants to take over ports 80 and 443. Nice if you have Exchange server running on it ... NOT!

 

This is insane! Why not let users CHOOSE the port instead of imposing 2 major port without any option, totally unacceptable.

Until remedied, there will be no upgrade for us nor our customers, this is a major mistake by FileMaker!

[fmow]

Glad I found this thread, because I was stuck and taken aback with, what I perceived as, a conflict.

 

Goes without saying this is a major let down and needs to be remedied immediately. I really can't see how in every recommendation they talk about installing fms13 on os x mavericks with the server application, as the ideal environment...

 

I 'll probably go with what Goetch suggested in the meantime, which a hack I 'd rather not be doing in my production/development environment. 

[Macfreq]

This is a show stopper for me too. Apple doesn't make it easy to change the default ports for Mac OS X Server web and wiki services. So I'm stuck with the hacking work around. I agree, Apple dropped the ball on communicating with a company they own and show a total lack of collaboration with FileMaker.

[pfroelicher]

I have been able to get both server.app and FMS to work on the same server.  I can not recommend doing this in a production enviornment, but this may be suitable for a development enviornment.   One problem is that server.app and FMS will overwrite the ocnfiguration files if you chnage any settings in either.  For those who would like to teest this out... 

 

In a nutshell, the machine will need 2 static ip address, just go to system prefs and go to network and click the + choose your curretn interface and assign a static ip address. 

 

Create a dns entry something like fiemaker.yourdomain.com and point it to the new ip address.

 

Shut off all server.app websites including profile manager, calendar, websites, and wiki.

 

install FMS allow FMS installer to disable the ports 80 and 443

 

Edit the server.app apache config files to listen on the original ip address I think you need to edit 2 files /Library/Server/Web/config/apache2/httpd_server_app.conf  and /Library/Server/web/config/apache2/sites/virtual_host_global.conf

 

Now you need it edit the FMS config files to listen on your new ip address. 

 

/Library/Filemaker server/HTTPServer/conf/httpd.conf

/Library/Filemaker server/HTTPServer/conf/extra/httpd-ssl.conf

 

For good measure I also edited the file /Library/Filemaker Server/HTTPServer/bin/httpctl and changed the hostname variable to the dns hostname I gave filemaker (example: SERVER_NAME="filemaker.yourdomain.com")

 

Keep a backup copy of the files you editied because both server.app and FMS may overwrite the files if you make any changes to either....

 

go into server.app and restart your web services including, profilemanager, calendar, wiki and web sites. 

 

(you may need to restart) test yourdomain.com should go to your internal sites and filemaker.yourdomain.com should go to the filemaker websites.

 

For php to work with filemaker you may need to edit more configuration files, I am still working on getting PHP to work...  However I ahve been able to test webdirect...

 

There may also be issues with using the server.app sites and they may take up a concurrent connection, I am still testing this... But I think if you go to your profilemanager site it may use a concurrent connection.... 

 

This is posted as-is and is meant for development only..

goetch

thanks for your nice instructions.

Does you setup with two ip numbers work? Can you use the os10.9 server services? can you host websites? can filemaker server autenticate externally? can you use webdirect?

help appreciated.

Yours

pierre

[kailou]

Like many I have also been struggling with this.  I spent a day on it and finally have FMS working AND OSX Server (10.8.x) web services (including wikis).  I just got it working so there may be issues to still work out. What I did is a twist on Goetch's solution.  

 

DISCLAIMER: I'm providing this info purely as a case study; I would not recommend doing this in a production environment; if you choose to try this you do so entirely at your own risk, I am not responsible in any way.

 

I'm hoping others will be willing to try this and return here with their findings.

 

I'm using named virtual hosts as opposed to multiple static addresses.  You will have to start off by making 2 new aliases in your DNS that will allow your OSX Server to respond to more than one hostname.  for the sake of this write up I will call my hostnames 'osx-www', 'fmwebd' and 'fmsadmin'.  osx-www is whatever existing hostname your server currently listens on, the other 2 are the new ones.

 

- FWIW, FMS does not actually install its own instance of apache.  It uses the builtin OSX apache.  What FMS does do is use its own set of conf files when starting up apache

- As several have pointed out, in theory you could have FMS be the web server and move any of your own OSX web services into the FMS conf files OR vice-versa.  To me it seemed more appropriate to move FMS stuff into the OSX conf files, that way I could more easily preserve OSX server functionality, including wikis etc.

 

Brief summary of activities:

- Turn off OSX Server web stuff, as indicated, and install and configure FMS

- Once FMS is configured, turn off webdirect.  make sure no httpd is running.

- Configure new FMS apache conf files for webd and fmsadminconsole

- Modify (slightly) your OSX Server httpd conf.

- In OSX Server app restart your webservices.

 

I created 4 new apache conf files for FMS.  I placed these in /Library/Server/Web/Config/apache2/FileMaker.

1) vhost.conf so httpd listens also on fmsadminconsole port.  It has only these 2 lines:

Listen *:16000

NameVirtualHost *:16000

2) fmwebd_80.conf for webd port *:80

3) fmwebd_443.conf for webd port *:443

4) fmsadmin_16000.conf for fmsadminconsole port *:1600

^^ I've pasted cleansed versions of these files at bottom of post.

 

For 2,3 & 4 I started of by first using the OSX Server.app to create 3 new virtual hosts using the ports and associated virtual hostname.  This created the base config files in /Library/Server/Web/Config/apache2/sites.  Then I turned off webservices in the OSX Server.app.  I *moved* the new conf files out of the 'sites' directory and into my 'FileMaker' directory.  You have to move these out of the sites directory otherwise the OSX Server.app will step on them.

 

You will need to get some information out of the FMS apache conf files.  These are located in /Librbary/FileMaker Server/HTTPServer/conf and /Librbary/FileMaker Server/HTTPServer/conf/extra

FMServer adminconsole: relevant FMS conf file: httpd-fmsadminserver.conf

WebDirect: relevant FMS conf files: httpd.conf and httpd-ssl.conf

 

FMS has a number of its own includes that you will need to add to the bottom of your fmwebd_80.conf and fmwebd_443.conf files.  At the very bottom of the FMS httpd.conf you'll find a number of include conf files.  You don't need all of them.

 

I've attached my cleansed fmwebd_80.conf, fmwebd_443 and fmsadmin_16000.conf files at bottom; this will show you where I placed things.

 

Once you've got your FMS conf files created then you will need to edit your OSX httpd.conf file (/Library/Server/Web/Config/apache2/http_server_app.conf).  I did not need to modify any of my existing services, but I did need to load some additional modules and also add a line at the bottom to Include my new FMS conf files.  This is the only line I added at the bottom of http_server_app.conf: - Include /Library/Server/Web/Config/apache2/FileMaker/*.conf - 

If you compare the FMS httpd.conf and the OSX httpd_server_app.conf you'll note that there about a dozen or more modules that FMS loads that your OSX Server may not be loading by default.  Most of these, for me, were the proxy modules.  Your OSX Server will need to load ALL the same proxy modules that the FMS httpd.conf loads, so uncomment them in httpd_server_app.conf if you need to.  I also found that FMS was loading all the auth modules, so I uncommented those in OSX as well.

 

That should be it for the httpd_server_app.conf.

 

That's it.  Restart webservices using Server.app. 

You should now be able to access all your existing OSX webstuff, including wikis, just as you did before.

The fmsadmin console would be accessible at https://fmsadmin.domain.com:16000

FM WebDirect should be available at https://fmwebd.domain.com/fmi/webd

 

The OSX Server app now controls all your webservices, including FMS.  Turning off web services in OSX Server.app will also shutdown WebDirect and the fmsadminconsole.

 

I look forward to hearing more from others on this topic.

 

#----------------------------------------------------------------------------#

 

fmsadmin_16000.conf

<VirtualHost *:16000>

ServerName fmsadmin.domain.com

ServerAdmin [email protected]

    DocumentRoot "/Library/FileMaker Server/HTTPServer/htdocs/httpsRoot"

# Setup the logs the way you'd like

    LogLevel warn

    CustomLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmsadminserver_access_log" 1209600 -420' "%h %l %u %t "%r" %>s %b"

    ErrorLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmsadminserver_error_log" 1209600 -420'

    TransferLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmsadminserver_transfer_log" 1209600 -420'

    <IfModule mod_ssl.c>

        # If you started creating this file by creating a basic vhost

        # using the Server.app then this section would contain your SSL info.

        # You could also copy/paste it out of any existing SSL using site.conf

        $ you may have

    </IfModule>

# Everything from this point down came from the FMS

# httpd_fmsadminserver.conf

    <FilesMatch ".(cgi|shtml|phtml|php)$">

        SSLOptions +StdEnvVars

    </FilesMatch>

    <Directory "/Library/FileMaker Server/HTTPServer/cgi-bin">

        SSLOptions +StdEnvVars

    </Directory>

    BrowserMatch ".*MSIE.*"

             nokeepalive ssl-unclean-shutdown

             downgrade-1.0 force-response-1.0

    ProxyRequests off

    <Proxy *>

      Order deny,allow

      Allow from all

    </Proxy>

    <Location />

       ProxyPass http://localhost:16001/

       ProxyPassReverse http://localhost:16001/

    </Location>

</VirtualHost>

 

#----------------------------------------------------------------------------#

 

fmwebd_80.conf

<VirtualHost *:80>

ServerName fmwebd.domain.com

ServerAdmin [email protected]

DocumentRoot "/Library/FileMaker Server/HTTPServer/htdocs"

    # Setup the logs the way you'd like

    LogLevel warn

    CustomLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmweb_access_log" 1209600 -420' "%h %l %u %t "%r" %>s %b"

    ErrorLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmweb_error_log" 1209600 -420'

    TransferLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmweb_transfer_log" 1209600 -420'

<IfModule mod_ssl.c>

SSLEngine Off

SSLCipherSuite "ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM"

SSLProtocol -ALL +SSLv3 +TLSv1

SSLProxyEngine On

SSLProxyProtocol -ALL +SSLv3 +TLSv1

</IfModule>

# Everything below came from the FMS httpd.conf

# I actually don't think any of this is really needed, especially since

# I'm using SSL

    <FilesMatch "^.([Hh][Tt]|[Dd][ss]_[ss])">

        Order allow,deny

        Deny from all

        Satisfy All

    </FilesMatch>

 

    #

    # Apple specific filesystem protection.

    #

    <Files "rsrc">

        Order allow,deny

        Deny from all

        Satisfy All

    </Files>

    <DirectoryMatch ".*..namedfork">

        Order allow,deny

        Deny from all

        Satisfy All

    </DirectoryMatch>

    ScriptAlias /cgi-bin/ "/Library/FileMaker Server/HTTPServer/cgi-bin/"

    <IfModule cgid_module>

        #

        # ScriptSock: On threaded servers, designate the path to the UNIX

        # socket used to communicate with the CGI daemon of mod_cgid.

        #

        Scriptsock log/cgisock

    </IfModule>

</VirtualHost>

 

#----------------------------------------------------------------------------#

 

fmwebd_443.conf

<VirtualHost *:443>

ServerName fmwebd.domain.com

ServerAdmin [email protected]

DocumentRoot "/Library/FileMaker Server/HTTPServer/htdocs/httpsRoot"

    # Setup the logs the way you'd like

    LogLevel warn

    CustomLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmweb_access_log" 1209600 -420' "%h %l %u %t "%r" %>s %b"

    ErrorLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmweb_error_log" 1209600 -420'

    TransferLog '|/usr/sbin/rotatelogs "/var/log/apache2/fmweb_transfer_log" 1209600 -420'

    <IfModule mod_ssl.c>

        # If you started creating this file by creating a basic vhost

        # using the Server.app then this section would contain your SSL info.

        # You could also copy/paste it out of any existing SSL site.conf

        $ you may have.  Same as the fmsadmin.conf

    </IfModule>

#----- FMS from httpd-ssl.conf -----#

    <FilesMatch ".(cgi|shtml|phtml|php)$">

        SSLOptions +StdEnvVars

    </FilesMatch>

    <Directory "/Library/FileMaker Server/HTTPServer/cgi-bin">

        SSLOptions +StdEnvVars

    </Directory>

 

    BrowserMatch ".*MSIE.*"

             nokeepalive ssl-unclean-shutdown

             downgrade-1.0 force-response-1.0

#

# These includes are from the bottom of the FMS httpd.conf

#

    # Fancy directory listings

    Include '/Library/FileMaker Server/HTTPServer/conf/extra/httpd-autoindex.conf'

    # Reverse Proxy configuration

    Include '/Library/FileMaker Server/HTTPServer/conf/extra/httpd-proxy.conf'

    # Rewrite settings

    Include '/Library/FileMaker Server/HTTPServer/conf/extra/httpd-rewrite.conf'

    Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf'

    Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_proxy.conf'

    Include '/Library/FileMaker Server/Web Publishing/publishing-engine/php/mountain lion/httpd.conf.php'

    #Include '/Library/FileMaker Server/HTTPServer/conf/extra/httpd-rewrite-fmiwebd.conf'

</VirtualHost>

[Larry Goldman]

Since FMS13 uses its own instance of apache web server, I found a way to get it running with Mac OS X Server:

 

Caveat: experiment with a test installation of OS X Server/FMS13.

 

Steps:

 

0) On an OS X Server machine, open a Terminal window and begin a super user session:

sudo -s
<password>

1) Stop the OS X Server apache instance:

apachectl stop

2) Confirm that ports 80 and 443 are clear:

lsof -i -P | grep "LISTEN"

3) Install and deploy FMS13, including WebDirect.

 

4) Patch the FMS13 apache files as follows:

     In /Library/FileMaker Server/HTTPServer/conf/httpd.conf: change "Listen 80" to "Listen 81".

     In /Library/FileMaker Server/HTTPServer/conf/extra/httpd-rewrite-fmiwebd.conf: change the destination of the rewrite rule from "443" to "444".

     In Library/FileMaker Server/HTTPServer/conf/extra/httpd-ssl.conf: Change all (3) relevant occurrences of "443" to "444".

 

Modified files are attached to this posting.

 

5) Restart the machine. If necessary, restart Mac OS X apache (apachtctl start) and confirm that now ports 80, 443 as well as ports 81 and 444 are open for business.

 

6) Finally, to complete the integration of FMS and OS X Server, create a OS X Server webapp by installing the attached files. The .plist belongs in "/Library/Server/Web/config/apache2/webapps", and the .conf file belongs in "/Library/Server/Web/config/apache2". Then, in OS X Server.app -> Websites -> yourCustomDomain.com -> Edit Advanced Settings: enable the FMS13Webapp.

 

To access the admin console, browse to:

 

http://www.yourCustomDomain.com/admin-console

 

WebDirect:

 

http://www.yourCustomDomain.com/fmi/webd

 

One advantage of this approach is that you only need to open ports 80 and 443 to the outside world because the "reverse proxy" is internal to the server machine. But, if you also have a firewall installed on the server, you will have to open all of the appropriate FMS 13 server ports on that machine, which is another story.

 

Does it work?

 

FMS13 Modified Files.zip

FMS13WebApp.zip

[dead-min]

Doest it work? It works like Hell! Great Job!

Now I can restrict a webs website to ssl via selecting the web app in ssl site and deselect it in the http site!

 

Is it possible to have separate webapps for the admin-console, xml-php and webd?

 

Thanks a lot!!

[Claus Lavendt]

First of all, if you read FMI documentation, they clearly state that you should only use dedicated server for FMS. That has been the statement for years. And with very good reasons.

However, the reality is that people have one server, that is used for all sorts of things, as the above posts clearly shows.

FMS is using it's own instance of Apache, which is why it needs the standard ports 80 and 443. You can not, via the Server Admin, change the default sites to use other ports. Then you will need to digg down into configuration files or terminal.

Another way, that is not nearly as complicated as the suggestions by Larry and kailou, is to use virtual host under the instance of FMS.

I have created a white paper and a config tool, that is currently in testing stage.

It will be released to the community, when it is ready.

[fmow]

First of all, if you read FMI documentation, they clearly state that you should only use dedicated server for FMS. That has been the statement for years. And with very good reasons.

However, the reality is that people have one server, that is used for all sorts of things, as the above posts clearly shows.

 

The problem is their documentation is contradictory, because they suggest you run fms on os x server mavericks, not on os x mavericks. By default that means that some services might run from the server. In such a case they should offer some provision to avoid conflicts. Otherwise why on earth suggest to run fms on os x server 10.9 or 3.0(for server)? They should be suggesting instead NOT to run it on os x server because if you use some of the services of the later that will cause problems.

 

They need to fix this and pronto.

[pbail]

J'ai découvert votre discussion avec beaucoup d'intérêt. J'étais désespéré et fâché d'être l'otage de Filemaker. Le prix FMS 13 est élevé et on peut attendre mieux de leur part.

J'ai appliqué la méthode de Larry et tout semble fonctionner.  MERCI BEAUCOUP.

J'attends avec impatience le document promu par Claus Lavendt.

 

I found your discussion with great interest. I was desperate and angry to be hostage to Filemaker. FMS 13 price is high and you can expect more from them. 

I applied the method of Larry and everything seems to work. THANK YOU VERY MUCH.     

I look forward to the document promoted by Claus Lavendt.

[Claus Lavendt]

Virtual Host guide is now published on TechNet forum

 

https://fmdev.filemaker.com/thread/75138

[Claus Lavendt]

Sorry, somehow I have gotten into my head that every FM developer also was a technet member….

 

However, I have just put the file on my own webserver as well: http://www.datamanix.com/FMS_VirtualHost_Config_Tools.zip

[fmow]

thanks Claus!

[Steven H. Blackwell]

 

The problem is their documentation is contradictory, because they suggest you run fms on os x server mavericks, not on os x mavericks. By default that means that some services might run from the server.

Actually, what this means, as is the case with Windows Server 2008, is that you must adjust the services/daemons running to provide the optimal environment for FileMaker Server. For example, turn off Spotlight, just as you would turn off Disk Indexing in Windows. The general rule is to turn off all unneeded services/daemons.

 

The SE's have an extensive White Paper on proper FMS configuration.  I'd recommend it.

 

Steven

[hbrendel]

Hi Claus,

 

I'm doing now what you describe, but I encounter an issue:

 

On page 4 of your Guide file you state the following:

While the server seems to work fine with the permission that will be set on this file, after you saved it to the desktop, you should change permissions to the default, which is fmsadmin as user with read&write, fmserver as group with read and everyone with read permissions. In general, you should set all permissions correct for all the files you work with. 
After you have changed the lines in the copy of httpd.conf file, you must replace the original with this copy.

However when I look at the current permissions of the existing httpd.conf file I see that the user is fmserver and the group is fmsadmin. (just the other way around)

 

Could this be a mistake in your Guide file?

[Claus Lavendt]

Hi Henk

 

Thanks a lot, it was an error in my guide…. I have changed it in my original, but have not released an update yet.

However, as you have seen, fmserver is a user and fmsadmin is a group. You can not set a group as owner, so you are pretty much forced to set it correctly, in spite of my error.

 

Thanks anyway. Hope it is helpful for you...

[hbrendel]

Maybe you can also help me with this. When I try to change the group I found that fmsadmin is not available in the picklist. I solved this by choosing the directory 'conf' and there - in permissions - I used 'apply to enclosed objects' (if this is the right translation for what I see in Dutch).

 

If there is a way to add fmsadmin to the userlist, maybe you can add this to the Guide too.

 

BTW: This guide is aweful. In the positive meaning of the word.

[Claus Lavendt]

Hi Henk

 

The user and group is created by the FMS installer, so you should not create them manually.

It could be that the list you see is from OD, while the fmserver and fmsadmin is local system.

 

I use a great tool called BatchMod to change permissions. It works every time, opposed to Mac's built-in settings. (it is free donation ware)

And yes, propagate to enclosing folders is an easy way to ensure that all files and folders have the same privileges. (this is, if they are supposed to)

 

I will consider adding a section in the guide about privileges and maybe refer to BatchMod...

 

Thanks for your interest and kind words about the guide. Hope it will help the community.

[fmow]

Actually, what this means, as is the case with Windows Server 2008, is that you must adjust the services/daemons running to provide the optimal environment for FileMaker Server. For example, turn off Spotlight, just as you would turn off Disk Indexing in Windows. The general rule is to turn off all unneeded services/daemons.

 

The SE's have an extensive White Paper on proper FMS configuration.  I'd recommend it.

 

Steven

Thanks Steve, I 've read said documentation and with the occasional exception of spotlight I too try to follow it as closely as I can. Having said that it's always a good idea to go over and remember some of the server stuff since, in my development work, it's the least visited topic probably, although I am currently administering one. Probably that's a good thing too, cause it seems things are running smoothly without too much of my input, which has of course been ample so far when I was setting it up. Yet they do state that they recommend you run os x server on mavericks, and not solely mavericks, without due care for this conflict. It's understandable of course that's such inconsistencies will happen even in such as close knit group  as fm and apple.

 

Having said that I wish apple could get off their butt, have a couple of folks from one side speak to a couple on the other at the cafeteria, and get them together on afternoon to fix this pita. I have yet to follow Claus's instructions as I am still debugging web direct in my apps, and I am really  hoping I won't have to, as I shouldn't, in the next month or so. 

[Rick Whitelaw]

I for one don't see any advantage to running FMS on OS X Server as opposed to plain Mavericks. Most of the features of OS X server must be disabled anyway to make it work. I, of course, stand to be corrected.

[fmow]

for the time being filemaker's documentation stands to be corrected, the only reason they suggest mavericks with server, is for a very hazy "on principle", I bet they 'd never run it side by side as they printed said documentation.

[kickniko]

Hi everybody!

 

Just signed into the forum - great place for competent info and help for FMS in real world situations! (And not in the usual idealized world of FM Inc. >:-D )

 

I had exactly the same "friction" between the OS X Server (Mavericks) and FM Server 13, but it was the other way around, namely installing OS X Server on the same machine that already run FM Server 13. And I found a quick and dirty solution, which may be naive but it seems to work OK. (At least on my machine until now, that is.)

 

So the situation was: FM Server 13 was already running (with WebDirect activated too) for quite a time, and everything worked fine. Then I had to have mail service in my domain too, and so I decided to purchase and install OS X Server.

 

I kept FM Server running while the installation of OS X Server took place, and after restarting the machine I configured OS X Server for mail service only. (No web pages.) It worked fine up to that point. I could reach the DBs both from the FM network as also from the Web, and I could send and receive emails with the OS X mail service.

 

After some days I restarted the machine and tried to access the served DBs over WebDirect. It was then that I got the message that no web pages were active. It seems to me that after restarting the machine the OS X Server had stollen ports 80 and 443 from FMS.

 

Now, I read the very well founded solutions here (thanks a lot guys!) but I really do not have the will nor the time to go through all that additional work just because some monsieurs and madames at Apple and FM think that I do all that for fun! (Except of course if they are going to pay my living and the bills of my company.)

 

So, I just moved the OS X Server to the dustbin in the hope to get rid of it and go for some other way to use the mail services of the OS X. At that point I got the message that the OS X Services were stopped but the configuration data were saved.

 

I restarted the machine, and voila! FMS was accessible again over WebDirect. Then I took the OS X Server out of the dustbin and double clicked it. It started the configuration procedure again but it used the already saved data, and so I just had to confirm all dialogs without changing anything. The result was then that both the mail service of OS X and FMS were doing what they are supposed to do side by side again.

 

I guess that this will only hold until the next restart, but it is an easy procedure to go through then. And I guess that it must work with (almost?) all other services of the OS X Server except web services.

 

So if you install OS X Server on a machine with FMS already running, and you do not need the web serviced of OS X:

 

1) Don't stop FMS.

2) Install OS X Server.

3) Configure your OS X services (other than web).

 

 

When you have to restart the machine:

 

1) Through the OS X Server into the dustbin.

2) Restart the machine.

3) Make sure FMS runs and WebDirect is OK again.

4) Get OS X Server out of the dustbin.

5) Double click it and confirm all dialogs.

 

That was it. I hope I didn't make any terrible mistake, but only time can tell. (And of course all experienced guys here too.)

 

Ciao,

 

Nick

[fmow]

Hi Nick, great post, I 've done quite a few things every time the problem popped up, until I completely uninstalled os x server.

 

I seem to remember that after os x server claimed the ports, there was no way I could have fms claim them back, dustbin or not.

 

I'll definitely give your option a try on a back up installation though because I am not sure about the sequence of my, many, actions to get this to work. 

[kickniko]

Hi fmow!

 

I seem to remember that after os x server claimed the ports, there was no way I could have fms claim them back, dustbin or not.

 

I'll definitely give your option a try on a back up installation though because I am not sure about the sequence of my, many, actions to get this to work. 

 

Just out of curiosity (which admittedly killed some few cats ;-)), can you remember if you also restarted the machine after having thrown the OS X Server into the dustbin? I am asking because I could also not convince FMS to get back to work on ports 80 and 443 without restarting the machine. Simply quitting and restarting FMS would not do.

 

And this is a bit strange to me since the message from OS X said that the services were stopped, which means that ports 80 and 443 should be free again. Or should they? :-/ So, if FMS quits and starts again it should find the ports free and work OK. Conclusion of a naive, that is, but could anybody explain to me why restarting the machine is necessary??

 

Anyway, FMS and OS X mail service still running happily side by side on my machine some days after my "solution". So no reason up to now to start with adventurous configurations and re-configurations of re-re-configurations.

 

BTW, wasn't that one of the main arguments pro Apple? Now, how I see that? Is it "Jobs not there => Apple not there too anymore?"

 

Back to subject. Fmow, wish you all luck of the world with that and happy serving again! If you have the time just drop us a line and say if it works again for you too. (In case it doesn't just blame it on me.)

 

Ciao,

 

Nick

[Claus Lavendt]

Both OSX instance of apache and FMS instance of apache, claims port 80 and 443 in the launch services. So, normally, you should install Mac OSX Server first, turn off web services and install FMS. When FMS installs, it writes a launch service file, where it claims these ports. If you turn on web services in OSX server, it will re-claim the ports to OSX server's instance of Apache.

You don't need to trash the OSX server admin application. Just turn off web services (web+wiki+profile manager) and run this command in the Terminal:sudo /Library/FileMaker Server/HTTPServer/bin/httpdctl graceful

 

This command will restart the FMS instance of apache, re-claiming the ports.

[fmow]

Excellent Claus thanks. Nick, I ll get back to you soon today as I get the time.

 

This is a long stading issue and it's been gaining traction in fmi forums too. I hope an update is around the corner, although to be fair two machines for server and fmserver are probably the only way to go. 

[kickniko]

Hi Claus, fmow!

 

Both OSX instance of apache and FMS instance of apache, claims port 80 and 443 in the launch services. So, normally, you should install Mac OSX Server first, turn off web services and install FMS. When FMS installs, it writes a launch service file, where it claims these ports. If you turn on web services in OSX server, it will re-claim the ports to OSX server's instance of Apache.

You don't need to trash the OSX server admin application. Just turn off web services (web+wiki+profile manager) and run this command in the Terminal:sudo /Library/FileMaker Server/HTTPServer/bin/httpdctl graceful

 

This command will restart the FMS instance of apache, re-claiming the ports.

 

That was it, thanks a lot Claus! I do not use any web related service of the OS X server anyway, but I was just trying to get FMS back on the web again by just using the admin console (from the browser) or the FMS control. Both of them didn't work in this case. But the terminal command worked very well. Thanks a bunch!

 

Of course the next question is, why that (browser) admin console does not issue this command, but never mind.

 

Excellent Claus thanks. Nick, I ll get back to you soon today as I get the time.

 

This is a long stading issue and it's been gaining traction in fmi forums too. I hope an update is around the corner, although to be fair two machines for server and fmserver are probably the only way to go. 

 

I don't have any big hopes about such an update, fmow. Some guys seem to be wanting to sell more machines, I guess. ;-)

 

But I am definitely not going to buy yet another machine just for running my services accordingly to Apple's or FM's ideas about what I should be doing. (Especially now that I have that command. ;-))

 

Cheers,

 

Nick