Filemaker Instant Web Publishing server document root?

If someone could help me wrap my head around this, I'd be most appreciative.

I have an OS X server (10.6), and the Apache document root is the default /Library/WebServer/Documents. For example, a request for http://domain.name/index.html will return /Library/WebServer/Documents/index.html.

My Filemaker instant web publishing URL is http://domain.name/fmi/iwp/res/iwp_home.html, but there is no /Library/WebServer/Documents/fmi/ directory on the server.

How does this even work?
IanJBlackburnAsked:
Who is Participating?
 
ErikCayreConnect With a Mentor Commented:
IWP is handled by Apache Tomcat.

In /private/etc/httpd/httpd.conf you will find
Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_jk.conf'

Inside that file you will find, among other things:

JkFmMount /fmi/iwp wpc
JkFmMount /fmi/iwp/* wpc

...so this is where you see the fmi/iwp component of the URL being defined.

The document root for IWP is actually the webserver root:
/Library/WebServer/Documents/

You did not mention why you need this explained.

If you need to serve images from file references in FMP, you must use relative file paths inside the FM DB, and store the images in the doc root.

If you wish to hack IWP, you're in for a challenge. IWP is built as a 'set and forget' feature. FMI never intended for anyone to have any flexibility with IWP, apart from what you define in Filemaker client.

I hope this answers your question so far.
0
 
mac_guruCommented:
Perhaps this is related to this ?

http://eridanus.net/blog/archives/443

Check your Apache log, see if it is having issue writing to /Library/WebServer/Documents

If so, you need to add the fmserver user to the admin group, as describe in the link.
0
 
IanJBlackburnAuthor Commented:
Thanks - that's not quite the root of this problem, but that is very useful info.

Turns out what's happening is that when you install FMS, it sticks a bunch of includes into the httpd.conf file that map some FM-specific directories located elsewhere.
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
lesouefCommented:
apache is not needed for IWP, only fm server advanced needs that.
if using a stand alone fm, it's using its own server, and the url to access it is not physical, but is decoded by the web server as a command (cgi like). if you already run an apache server on this machine, turn it off or shift the fm web port to something other than 80 to avoid conflicting with the regular osx apache.
the fm physical root folder is inside the fm folder or in a /lib/fm folder somewhere as far as I can remember (I am on windows). I can power up my old mac too-morrow if you can't locate it.
0
 
IanJBlackburnAuthor Commented:
Sorry, I should've clarified. We are running FMSA. It just modifies the httpd.conf file to handle its own web-related directories.
0
 
lesouefCommented:
in this case, you should find <directory> entries in it for fm if it needs a physical folder, and a loadmodule entry to handle the requests to the fm engine, a bit like php. difficult to s
0
 
lesouefCommented:
gone too fast...
... to say more, as it uses IIS on windows, and I have only been using the php interface with it.
as far as I can see in a former windows fm9 server installation, it is under the fm server/web publishing/iwp folder, so probably the same under osX, and not the the lib folder.
0
 
ErikCayreCommented:
PS.

/Library/FileMaker Server//Web Publishing/publishing-engine/wpc/FM Web Publishing.app/Contents/Resources/iwpres/iwp_home.html

is the path to iwp_home.html

Although I never hacked these files myself, I know of others who have had some success with it. YMMV:)
0
 
IanJBlackburnAuthor Commented:
>You did not mention why you need this explained.

I just wanted to understand how it worked.

>Although I never hacked these files myself, I know of others who have had some success with it.

You can edit iwp_home.html and it works just fine. Funny how much harder it is to locate that file on an OS X install than on Windows Server, though. I guess FM intended the IWP index page to be "set and forget" too.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.