Vhost applications setup

Actually the Vhosts are working, its the console app that seems to be the problem.

I contact Stefan Richter and he was kind enought to send me some example configuration files from a running fms server. Funny things is that other than the url for the vhost there was no reall (Windows vs Linux) difference in the configuration of our server vs the files he sent. I went ahead and setup apache and dropped the standard sample apps in the vhost. They work perfectly!

The problem is that none of them register on the admin console. We can monitor connections bandwidth etc for the vhost but none of the apps are listed. Yet they work Audio, video, text and graphics no problems.

I've run fms/fcs for 3 years without using vhosts. From everything I read in the documentation what we were doing, what everyone was telling us should work. It was.

But now I'm back to the initial corundum of why I can't see the apps registering in the vhost.

We have an admin folder there but I have not setup any Admin users for the Vhost as we will not be using that functionality.

We have dns entries setup for both the primary server and the vhost. I have also read and followed Stefan Richter's examples in the article you have listed.

One item there that is unclear is where in Server.xml the VirtualHost block should be included. Should this be simply appended to the Server.xml or should it be included inside the roor or server tags? There appear to be some structural differences between the FCS 1.5 Server.xml and the FMS 2.0.4 Server.xml that I am attempting to use. Unfortunately I can not find any example of any of these files for 2.04.

Thanks for responding I hope you can continue to help.

no the server name and Ip, we're not setting up individual Vhost admins. even if we did ti would be the same ip number.

When we log in using the console app here is what we are seeing.

After configuring a directory using the AppsDir tags in Vhost.xml, if we place an application folder inside the specified location the app does not register or display for that vhost. All permissions etc have been checked and are valid.

When we place a folder inside the default applications folder at ~fms/applications the app registers, but shows up in the default and all other vhosts. This is undesirable as we do not want to allow general access to all apps among vhosts.