Does anyone know how I can set up virtual directories and have them Filemaker web publishing extensions enabled for them?

For example, I want www.bob.com/fmi/config to be able to databases for bob.com but also have www.bob2.com/fmi/config to be able to configure bob2.com's databases. Any ideas? When I created a new virtual server in IIS, I'm not sure how to extended filemaker web publishing to the new virtual server.

I'm pretty sure you can't do this if you only have one static IP address for the server.

That's becuase the fmi/config pages look for WPE via the server IPs used when you first configure it. So you'd have to assign your one IP address to each virtual site in IIS, which it doesn't like to do. Usually the default website gets the IP address, which is why FM recommends going to http://youripaddress/fmi/config to admin web publishing.

I haven't played with it though.

Not true, at least not for our OS X server/Apache setup. I have several virtual websites on our server (with one static IP address), and all can be configured with http://www.hostname.domain/fmi/config . However, the configuration is the same for all (for the moment), e.g. it doesn't matter if I call DB1 with stylesheet x from site y or site z.

The problem rather therefore is - as sec39 pointed out - to have different directories (with different .xsl files for CWP), and different configurations of DBs for the virtual sites.

As far as I have understood (for Apache), this would involve

- tweaking the [VirtualHost] entries in the Apache configuration files

- generating individual Tomcat config and worker files

Something I had not time to try out for the moment (i.e. never change a winning horse ...)