Dan
I know with Websphere 4.0 you can utilize load balancing and therefore
your WAS/JAS servers should be able to be taken down one at a time for
any work you need to perform, as long as the remaining servers have the
capacity to handle the additional user load.
As far as OW is concerned, it gets a little trickier. The deployment
server, assuming you don't have CO's stored on it, can pretty much be
taken down without affecting users. If you have multiple application
servers, OCM's can be modified so that one of the AS's is removed from
the mix and then can be worked on, though some users who were pointed to
the server being brought down would need to log out of and back into OW
for the change to be cached. As far as the DB is concerned, I don't
think I've seen any way to be able to have a fail over without a small
amount of downtime, again, in the case of OW to log out and back in.
For example, a client of mine has a deployment server, two intel based
application servers, two load balancing WAS/JAS servers, and a clustered
SQL 2000 DB set up. Deployment server maint. is a no brainer. Since they
do have a period nightly when users are off the system (for backups),
when an app server needs work, they change the OCM's to point to the
other AS during this window. For the WAS/JAS, during the backup window,
the affected machine has it's services stopped. And for the DB, if the
active node in the cluster is the machine that needs work, a failover is
performed during the backup window.
I can't wait to see some of the other responses you get to this one.
Jim
On Fri, 28 Feb 2003 12:11:02 -0800 (PST) dan_richards
Has anyone come up with an architecture plan that allows for
One of the challenges
Any ideas would greatly be appreciated!
Thanks!
________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit
www.juno.com
