A Forum reader recently asked:
"We are run GroupWise 7 and have installed the 7r1 patches. We are creating a second WebAccess agent and I would like to know how to load balance between this agent and the current one we have running. Any information would be helpful."
And here's the response from Robert Mahar ...
We have several WebAccess servers, and our official links to them are built dynamically. It's something like this ...
var linkString="Groupwise WebAccess";
document.write( "<a href=" + "https://" + hostPrefix + ( new
Date().getSeconds() % 3 ) + domainSuffix">" + linkString + "</a>");
This will sort of randomly select links:
If you cannot calculate the URL, use a hard-coded array and use
( new Date().getSeconds() % 3 )
as the index into the array.
We find that this spreads the load very evenly. For example, right now we have 101, 97, and 105 users currently using the three servers, respectively. And that's pretty decent load balancing.
See also the Cool Solutions GroupWise 6.5 Best Practices Guide at:
for additional guidelines on load balancing techniques.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.