Forum Discussion
What_Lies_Bene1
Jan 24, 2013Cirrostratus
OK, got that. So, this is actually quite simple to implement;
1) Don't enable any kind of Persistence on the Virtual Server
2) Ensure OneConnect is not enabled on the Virtual Server
3) Have a HTTP profile assigned to the Virtual Server
With that configuration, each individual TCP connection will be load balanced individually to one Pool Member or another yet the requests within each connection will be sent to only the Pool Member initially selected for that TCP connecction; any new connections from the same BPM host will be load balanced uniquely from any existing ones and again, the requests within each will all go to the Pool Member selected on inital connection. Hope that makes sense.