The SuperContainer installer is not yet compatible with FileMaker Server 13. You will need to follow the manual installation instructions from the SuperContainer documentation wiki located here: http://docs.360works.com/index.php/SuperContainer#Manual_Installation_with_FileMaker_Server
You must manually restart the FileMaker Server Apache web server in addition to restarting the Web Publishing Engine after a manual installation in order to pick up the changes. There are instructions for manually restarting the Apache web server at the bottom of the above-linked wiki section.
The link in your post under the "alternative 2" heading is for installing SuperContainer to a separate Tomcat server that is not part of FileMaker Server. This is a good choice for deployment if you want SuperContainer to be separate from FileMaker Server. Please let me know if you have any questions.
Hello, and thank you for the instructions.
I have followed the guide, but get this error when running the sudo command.
========== graceful ==========
Thu May 15 14:50:54 CEST 2014
/usr/sbin/httpd -k graceful -D FILEMAKER -f /Library/FileMaker Server/HTTPServer/conf/httpd.conf
httpd not running, trying to start
(48)Address already in use: make_sock: could not bind to address [::]:80
(48)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
exit code 1
The error message indicates something is already bound to port 80. On a FileMaker Server 13 machine with the web server running, "http://localhost" should display a page with "FileMaker Database Server Website" at the top. Can you reach the FileMaker home page at "http://localhost" from a browser? If you don't see the "FileMaker Database Server Website" text, what do you see?
Hmm. I have changed the permissions on the Supercontainer folder and the underlaying files and folders I put into the /Library/FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/ to read/write for fmadmin and fmserver, restarted the computer.
Now everything seems to work. Was this the problem, or can something else have changed without my notice?
The initial error you reported accessing the FileMaker Server web server would not be fixed by this, but restarting the computer may have fixed it. I do not have a way of determining what the issue was. Restarting the computer is another way of restarting the web server, so maybe it just needed a different method of restarting to get up and running.
I would not expect you to have to alter the permissions for the SuperContainer folder, but it is possible that was the root cause of the issue. The fmserver user would need access to the SuperContainer folder since otherwise it would not be able to load the app. I will add this to our documentation as it never hurts to verify permissions are correct before proceeding. Please let me know if you have any other questions, and email email@example.com if you experience any other issues.