mac Upgrading from 10.6 to 10.8 while keeping FMSA 11v5 installed

[xochi]

I recently upgraded two servers running OS X 10.6.8 to OS X 10.8.5, while keeping FMSA 11v5 installed.   It was not terribly easy, so here are some notes I made.  I hope this helps others:

• Before the upgrade, go into Server Admin and document all your settings and export the settings.  Your settings will be wiped out during the upgrade most likely.
• Make a backup of your server drive just in case
• 
  
• Upgrade to 10.8.5, do all additional mac software updates (if any) then reboot.
• 
  
• Uninstall FMServer using the FMS11v5 installer.
• 
  
• Reboot
• 
  
• Install FMServer 11v5 : note, as part of the install you will have to install Java 6
• 
  
• Install Java 7 as well
• 
  
• Try to launch server admin : most likely, it won't work, because [A] apache is off, and  apache can't start since the configuration file is wrong.  Fix it as follows:

1. In the terminal, enter the following command:  

sudo apachectl -t
This will test the configuration file located at /etc/apache2/httpd.conf and report errors (typically, modules which FMS is trying to load which are not yet on your disk, because the server hasn't been deployed yet).
Use a text editor (BBEdit) and comment out the offending lines by putting "#" at the line start.  Save the file.
use "sudo apachectl -t" to see if it works.  Keep fixing errors until it passes the test.  I had to comment out about 5 lines total. 
Once it works, enter the command: "sudo apachectl restart"

• Now, open safari and try http://localhost:1600/   and you should get to the server start page, at which point you can download the Admin app.   However, the admin app may not work for security reasons.  Solution:  Find the downloaded file, and right-click it in the finder and choose "Open".   This should open it.  You'll get a Java 7 warning, which you should also enable (and click the option to "always trust apps with this signature")

Now, you should be up & running with the Admin java app.  You'll need to re-deploy the server (which fixes the problems in httpd.conf ) and then you should be up & running.
Since uninstalling FMS removes the filemaker server user, I had to go back in an add the FMServer user to a bunch of folders (alternate backups folders, shell scripts, and plugins).
Edited November 26, 2013 by xochi