Round-robin DNS is a bit tricky with the browser-based webtop - the
problem is that the links on your webtop reference the RR name, and so
application launches may, in fact, go to a different hostname than where
you've authenticated. This is probably the source of your error.
One way around this is to have a refresh/redirect on each of your SGD
servers, to "redirect" the connection from the RR name to the "real"
server name, like:
Redirect /index.html http://realservername/sgd
This can get a little tricky wrt server hostnames and X.509 certificates
when using SSL, but there are ways around that.
The "supported" way to do tier 1 load-balancing is to use the swcd
load-balancing script for load-distribution - the script is pretty
self-documenting. Be aware, though, that the version included in 4.30
needs a bit of fixing - it's the 4.20 version (oops). The fixes are:
1. In swcd.jsp comment out line 4 :
<!%@ include file="/resources/jsp/utilities.jsp" %>
2. In standard.jsp add the following line at the beginning:
<%@ include file="/resources/jsp/localeutils.jsp" %>
hope this helps,
Rick
Christian McHugh wrote:
On Wednesday 02 May 2007 11:28:25 David W. Fong wrote:
Not sure if this would resolve your issue, but have you checked to make
sure that the peer DNS names of your array are resolvable forward and
reverse on both servers?
Well that brings up the issue of how this array was built. I'm not exactly
sure this is the right, but here goes. There are two servers iego.domain and
rishi.domain. We added External DNS entries for sgd.domain, and set up round
robin dns to point to both servers. Opening a webbrowser to sgd.domain works,
users log in, lauch apps etc.
Everything appeared fine.
We had heard that it would be better to run the web portion secured as well,
so we set up certs on both servers for sgd.domain, and changed the sgd
website login links to run https://sgd.domain/sgd/index.jsp. After that we
had occurrences of the before mentioned soap error. The error seemed to go
away after changing the links back to just http:// and we figured all was
well.
So all of this to say that yes, sgd.domain, rishi.domain, and iego.domain all
resolve in both directions, but sgd.domain is round robbin. Is there a better
solution or a recommended way to go about this type of setup?
Possibly related, when we had just a single server we set up pdf unix
printing. Users could then run the lp command described in the sgd docs and
get their results "printed" to a locally running pdf viewer. After setting up
the array this printing functionality only seems to function if you are
connected via one of the servers (I forget which off the top of my head). If
you try to print from the non-functional one, you see the job in your webtop
print queue, but your pdf viewer never opens. The only thing to do seems to
cancel that job and try logging back in, hoping you get a "good" connection
the next time.
Thanks everybody,
Christian
_______________________________________________
SGD-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sgd-users
--
Rick Butland
E-Mail: [EMAIL PROTECTED]
AccessLine: (703) 579-1947 x53261
Direct: (703) 444-9398
Mobile: (703) 328-8130
_______________________________________________
SGD-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sgd-users
