[Openroad-users] (no subject)

[Neil.Warnock at luminary.co.uk]

Jonathan, your plan sounds good. You are doing client load balancing using the webserver cluster. Great. There are other ways to skin that cat but what you suggest sounds reasonable and has the pros and cons you have identified. If I read your plan correctly this 'parallel' approach means you may be able to avoid the webservers having to automatically sync client session state too, but that's more to do with how your client(webserver) app is written.

Pete mentions the use of alternate nameserver lists in the clients (ie your webservers)  - it might be a good idea to employ that too, with client(webserver) A normally using AppServer A but failing over to B if unavailable... and vice versa.

HTH

Neil Warnock
Luminary Solutions
Tel: +44 (0)845 371 4090
Mob: +44 (0)771 265 0291
Email: Neil.Warnock at luminary.co.uk

For more information on Luminary go to http://www.luminary.co.uk<http://www.luminary.co.uk/>
Luminary Solutions Limited Registered in England No 4854134 VAT Reg No. 829 3166 13
Registered Office: 16/17 Pavilion Business Park, Royds Hall Road, Leeds LS12 6AJ



________________________________
From: openroad-users-bounces at peerlessit.com [mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Jonathan Barton
Sent: Wednesday, September 19, 2007 9:50 AM
To: International OpenROAD Users
Subject: [Openroad-users] (no subject)

Hi all

I am looking for a bit of advice OR App Server architecture deisgn.

We have two web servers (resiliance/load balancing with .net Web Services) both of which communicate with an OpenROAD Application Server, and all is well.

I have been testing the use of an additional OR App Server using remote nameserver entries on the primary OR App Server for resiliance purposes and I am ready to deploy the new server to the live environment.  But I am concerned about practicalities of effective resiliance and software releases requiring down-time.

Is there any benefit of not using the remote nameserver entries on the Primary OR App Server, but rather have a designated App Server for each web server?  This would enable us to deploy new software without taking the system off-line by simply draining a web server from our nlb (Windows 2003 Network Load Balancing).  Although this would not be true load balancing as far as the App Server is concerned.

Any experience shared would be greatly appreciated.

Many thanks.

JONATHAN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"University of the West of England"
+ Work Email:         jonathan.barton at uwe.ac.uk<mailto:Jonathan.barton at uwe.ac.uk>
( Work No:             0117 3281075

P Please consider the environment before printing.


________________________________
This email was independently scanned for viruses by McAfee anti-virus software and none were found
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.peerlessit.com/pipermail/openroad-users/attachments/20070919/a7742bdd/attachment.html