Robert,
The setup you have in your diagram will work if you ensure that the clients.ini settings are the same on both servers. You will also need to make sure that the stanzas in the witango.ini files on each machine are practically the same for all the witango processes. Also make sure that the license keys are unique or conflicting witango servers will stop responding to user requests.
If you have multiple instances of witango on the same server make sure that the LISTENERPORT, LOGDIR, PIDFILE and VARCACHEPATH do not conflict with each other and are configured correctly.
From the documentation, it seems that the IIS plugin reads the userreference and knows where to send, but I need to be sure. I want to avoid a more complex structure of clustering the IIS servers.
This is correct and is why the clients.ini files need to be the same on each web server.
Another thing to watch out for is if you store the user reference in the database. In a load balancing scenario the userreference will have the IP address and port of the witango server prefixed to it and will go from 24 bytes to 36 bytes in length.
Witango Support
-----Original Message----- From: Robert Garcia [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 9:24 PM To: [email protected] Subject: Witango-Talk: Load Group, Round Robin Question.
My server configuration is growing more complex, and I was wondering if anyone can answer this authoritatively. Please see the image attached to understand what I am referring to. I hope the attachment is ok, just a jpeg.
I currently use one IIS server (WS1) to 2 witango machines in a load group, works great. No issues. But I am moving to 4 witango servers in a load group, and 2 IIS servers. The question is this:
If I use round robin to load balance the requests to the webservers, lets say request A comes in to WS1, and it is assigned to Witango 2 in the load group, and given a user reference. Then (n) requests later, the goes to the other WS2 server in the round robin dns group. I need to verify, that WS2 will read the userreference in the cookie or URL, and know that there is an existing reference on Witango 2, and correctly send it there. And not send to a new Witango server and start a new reference, which will cause the user to lose state.
From the documentation, it seems that the IIS plugin reads the userreference and knows where to send, but I need to be sure. I want to avoid a more complex structure of clustering the IIS servers.
It would be great for Witango Support to answer for me.
Thanks,
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
