I'm getting close to where I will need web farm support. Joe, I know this has been on your roadmap. Just wondering if it's something you are looking to do in the near future, if not, what it may take to sponsor (you could contact me directly on that one), and if neither of these are possible, what are the areas I need to look to update to code it myself? I'm thinking the issues are around the DB caching but am not sure. I could also use a load balancer that forces sticky sessions. Would that solve many of the issues?

Thanks

Hi David,

I Did some "digging" in Developers Forums but found no recent news about WebFarm support for mojoportal. Did you make any progress? What exactly is/was your bottleneck (cpu, memory, database)?

So. it's months later and it's time for me to implement web farm support. Couple of questions as I go about this:

1) is there a setting in web config or elsewhere that allows me to point the data directory somewhere else (like a network share)? This would allow all servers to access the same data directory.

2) When using a web farm, the SSL is placed on the Load Balancer, and the request, even if secure from the outside to the LB is sent in clear text on the local network. I believe, but have yet to test this. If my assumption is correct, the local server will think the request was not secure even though it is. Is there a way to disable the SSL message (other than to just blank it out) in the web store if no SSL is present on the local server?

Thanks

Joe,

I'm running into the same issues with the web farm, but thanks to being able to point a virtual Data directory to a folder on a shared drive, mojoPortal works.  My question is if it is only the cache dependency file that need to be deleted, can I just have a virtual directory for "system files" pointing to: ~\Data\Sites\1\systemfiles? 

I'm not sure if having this structure will affect any other parts of the site.  We have an automated build that replaces our skins, so we don't want to have the whole Data directory as shared.

Hi!

I just want to share the farm configuration I use with mojoPortal and also other CMS-systems.

I did the infrastructure design for a web-hotel and they now run over 600 websites in this configuration and has done so for more than a year now and it works absolutely great!

There are 2 very powerful physical 2008 R2/IIS 7.5 webservers running in a NLB-cluster. 10 IP-adresses are load-balanced and also there are FTP-sites for each customer that are running in the same NLB-cluster, but with single node failover mode.

Data are replicated between the servers with File Replication Service.

So nice, just upload files to any node and they are instantly replicated across.

mojoportal works flawlessly in this configuration. Some DNN-sites had problems because of some caching issues so the site on one node where not aware of new files that had replicated there, but the DNN-guys fixed that (not sure about what was the problem).

FRS is really nice and with a dedicated Gb-network between the nodes it is rellay quick as well and handles all kind of conflicts.

This is a rather special infrastructure setup and we have created a comprehensive set of custom managing-scripts so they can easily provision new sites and force replication and so on.

/Mats

Hi Mats,

That's good stuff! I've been surprised how many people are already running mojoPortal in various web farm configurations. That is why I decided its time to work on officially supporting web farms, and that is what I'm focused on right now. I'll be working on documentation also for web farm configurations and would be glad to have help if any community members would like to write tutorials about how they have configured things.

Best,

Joe