Re: Traveler on i and HADR options -- DOMINO400

(Thanks Walt and Chris... something told me you two very well might chime
in on this one...)

I got the same vibe from reading Ed Brill's comments on his blog about why
it ended up in DB2 instead of .nsf... maybe it will trickle down to be
simpler for more of the user base in the future...( HINT HINT)

Front ending the servers at the HTTP level will be a pretty simple setup
for us (and one that we use currently for other functions like iNotes). We
will always use the same external IP address/URL from the mobile Traveler
devices and then switch which server 'answers' by updating static NAT
statements within the firewall. Has always worked like a charm for our
setup and supports our simple needs and desire to 'switch' between the
connectivity rather than have them both addressable from the outside at all
times.

From: Chris Whisonant <chris.whisonant@xxxxxxxxx>
To: "Lotus Domino on the IBM i (AS/400 and iSeries)"
<domino400@xxxxxxxxxxxx>
Date: 08/27/2013 11:59 AM
Subject: Re: Traveler on i and HADR options
Sent by: domino400-bounces@xxxxxxxxxxxx

"It is a real shame that IBM/Lotus didn't make this part of the
functionality actually work WITHIN the Domino infrastructure..."

I was once in this mindset too, but there are a couple of reasons for this,
which I'm not sure I can fully dive into since I expressed my concerns with
this to IBM during the beta periods and via one-on-one discussions at
Lotusphere. I'm not sure at which point some of my discussions were NDA,
but suffice it to say that I believe that where IBM has taken Traveler HA
is great and is working for them.

With regards to the single point of failure on the DB side, yes that can be
a pain point. However, IBM DOES support utilizing the DB vendor's HADR
facilities with the stipulation that the HA replica of the DB is in the
same physical datacenter. This way you don't still have that single point
of failure. I know how that could play out with DB2 using HADR, but I'm not
sure how that would translate into IBM i DB2 HA...

I'm also curious as to what you'll be doing to frontend your Traveler
servers in HA? What HTTP load balancing mechanism will you be using?

---------------------------------------------------

Thanks,
Chris
Personal Blog: http://cwhisonant.gotdns.com
Work Blog: http://www.bleedyellow.com/blogs/lotusnut

On Tue, Aug 27, 2013 at 11:43 AM, <ChadB@xxxxxxxxxxxxxxxxxxxx> wrote:

It is a real shame that IBM/Lotus didn't make this part of the
functionality actually work WITHIN the Domino infrastructure...

From: ChadB@xxxxxxxxxxxxxxxxxxxx
To: "Lotus Domino on the IBM i \(AS/400 and iSeries\)"
<domino400@xxxxxxxxxxxx>
Date: 08/27/2013 11:40 AM
Subject: Traveler on i and HADR options
Sent by: domino400-bounces@xxxxxxxxxxxx

We've had great results with Domino 9 so far the week that we've been on
it.

I'm now testing Traveler on i (we have always run it on a Windows server
that was leftover from a phased out Blackberry BES oriented Domino

Server).

The Traveler functions seem to work great with our test devices so far,

but

i'm finding that setting it up to be highly available is going to be a

bit

of a mess...

We have 2 clustered Domino servers that support mail users and have no
problem getting the external URL that the Traveler mobile devices access

switch between whichever mail server we want to 'answer' at any given

time.

The challenge is that the Traveler portion of the data (when configured

for

HADR) is moved to a DB2 database... it's an easy conversion and works

well,

but the data needed by the Traveler server and devices is in ONE

location.

If that location is down, effectively so is Traveler functionality.

BOTH of the Traveler servers (when converted to HADR) can be pointed to

the

backend DB2 database with no trouble, but the single point of failure
remains.

All of the documentation I can find mentions that the backend DB2

database

can be made highly available between servers, but so far I have not found
an easy way to do this on the IBM i. What sort of replication would keep
this backend DB2 database in synch so that either Traveler server could

use

it from either location of the DB2 backend?

Has anyone tackled this type of setup yet?
_______________________________________________
This is the Lotus Domino on the IBM i (AS/400 and iSeries) (Domino400)
mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_____________________________________________________________________________

Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit
http://www-935.ibm.com/services/us/index.wss/offerfamily/iss/a1026954

_____________________________________________________________________________

_______________________________________________
This is the Lotus Domino on the IBM i (AS/400 and iSeries) (Domino400)
mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_______________________________________________
This is the Lotus Domino on the IBM i (AS/400 and iSeries) (Domino400)
mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_____________________________________________________________________________

Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit
http://www-935.ibm.com/services/us/index.wss/offerfamily/iss/a1026954
_____________________________________________________________________________