I don't have an answer for your question but would like to know if you have any documentation on how to did the load balancing?
Sorry must have missed this when it was originally posted.
The only thing we have is a .htm on each web server with the following code:
<TITLE>This is server 3</TITLE>
We have it saved in wwwroot folder
Obviously changing the "This is server 3" depending on what server it's on. Sending the link to the user and getting them to click on it brings up what server they connect to. Ok not the greatest option but at least if we've had problems we've been able to identify if it's been 1 server or both and not have to hit both servers with the dreaded IIS reset during live operations.
That's a good idea. but would it necessarily be the same session that the console would be using?
i.e. would it connect the user as a new session and therefore assign a connection to a server that may no be the one that the current console connection is using?
These helped me when learning about the load balancing generally
Then it's just a case of using your new 'server name' and virtual directory in the console.exe.config
you can also mess about with DNS as well if you use webdesk\self service for a nicer domain name
works pretty seamlessly so far
As far as I'm aware (please don't take me to court on this though lol) console and webdesk/self service will use the same load balanced server. I've certainly found that I stay on the same server. I know that when I've had an issue logging into console and the same thing has happened in webdesk at the same time, I have been able to target logging directly onto the other web server (as long as it was up and running ok) and have got logged in ok The only time it changed (again I think!!) was when we'd had a major issue and there were reboots done all the servers lots of times I switched from Server 3 to Server 4 but have remained on 4 ever since.
That was a load of waffle really wasn't it!!!
1 of 1 people found this helpful
I believe the affinity will be based on the IP address and not which session in IIS you're connecting to so going to a test page at the root of the site should be the same server your Web Access or Console session is connecting to. The only suggestion I can make to the original question is to enable some TPS logging on both servers and see which one creates a log file for that username.
Another great document to add to Jason's list is this one (and my opinion on it is no way biased): Using Service Desk with Network Load Balancing (NLB).
Quite right! I did use that as well Stu
It was very helpful