|
Home > Archive > WebSphere Edge Server > June 2004 > Coming to terms with Edge Server HA
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Coming to terms with Edge Server HA
|
|
| Balasubramanian Mangalaganesh 2004-06-02, 7:50 am |
| Hi,
(i) I would like to know what the Synchronized in HA terms mean?
Does that mean the Configurations woudl be synched up or do i need to do
the same configurations as the Primary on the Standby machine as well?
If the Synchronization does not do this what else does it to?
(ii) Is there any log file that tells me when the goActive and goStandby
were invoked?
(iii) In a co-location configuration (Primary wiht one Web Server and
Standby with another Web Server) should i identify that the co-location
flag in the configuraton files or is the edge server smart enough to
figure this out on its own.
This is an URGENT Request. I would be glad to receive any assistance.
Thanks
Manglu
| |
|
| > (i) I would like to know what the Synchronized in HA terms mean?
That there are two Dispatcher hosts (Primary / Backup) and the Backup can
take-over the job when it notices the Primary has failed. Shame on the
product, the Primary won't replicate its configuration to the Backup and you
have to do the configuration job twice.
> (ii) Is there any log file that tells me when the goActive and goStandby
> were invoked?
No, but as it is shell scripts, I added log statements to a file of myself
to track what happened when. Combined with server.log log, I found I had
then enough information to track events.
> (iii) In a co-location configuration (Primary wiht one Web Server and
> Standby with another Web Server) should i identify that the co-location
> flag in the configuraton files or is the edge server smart enough to
> figure this out on its own.
I have not investiguated co-location stuff, but I have a 'Sorry' web server
on each Dispatcher and didn't have to play with co-location flags (KCBR
forwarding method).
Ben.
| |
|
|
>
> No, but as it is shell scripts, I added log statements to a file of myself
> to track what happened when. Combined with server.log log, I found I had
> then enough information to track events.
I know this went into the Load Balancer v5 code (might be in v4 as
well), but there are now several user-exit points in the code. Several
of them are for HA related items, such as state changes (standby,
active, etc). I don't remember the syntax anymore so look in your doc
for user exits, but if the particular script is found on the hard drive
then it'll be called during the matching scenario. Yes, the
goActive/goStandby scripts can do the same things but several of the
other user exit points have no existing script (such as manager marking
all servers down). You can put whatever you want in these scripts, some
of the samples send emails I believe.
>
>
> I have not investiguated co-location stuff, but I have a 'Sorry' web server
> on each Dispatcher and didn't have to play with co-location flags (KCBR
> forwarding method).
If the server address matchs the NFA defined on the executor (or the NFA
that was "discovered" internally), then yes, the Load Balancer will
"know" it is a colocated server. It doesn't hurt to add the flag
explicitly just so there's no confusion by anyone looking at the config
-- saving the configuration may also add that flag all the time.
Jeff
|
|
|
|
|