[ipac] RE: Load Balancing (Casey Durfee) - ipac Digest, Vol 32, Issue 13

[Brad Bates]

Thanks Casey!

Brad Bates
PCLC


   1. Load Balancing (Casey Durfee)

Message: 1
Date: Fri, 18 Aug 2006 12:28:58 -0700
From: "Casey Durfee" <Casey.Durfee at spl.org>
Subject: [ipac] Load Balancing
To: <ipac at lists.tblc.org>
Message-ID: <44E5B289.8089.005D.0 at spl.org>
Content-Type: text/plain; charset="us-ascii"

You don't need multiple ipacadmin.gdb databases for multiple HIP servers any
more than you need a separate Horizon database for each machine with a
Horizon staff client.

There's no reason why you can't have just one ipacadmin.gdb database used by
multiple HIP servers (assuming they're all identical as far as
configuration, of course).  You just need to change the file
"10firebird-ds.xml" in the jboss/server/default/deploy directory.  Out of
the box there will be a line in the file like:

<connection-url>jdbc:firebirdsql://localhost:3050/C:/dynix-horizon/appserver
/jboss/server/default/data/ipacadmin.gdb</connection-url>

If you instead wanted this HIP to use an admin database on a remote server
at "10.1.1.1" you could change that line to:

<connection-url>jdbc:firebirdsql://10.1.1.1:3050/C:/dynix/appserver/jboss/se
rver/default/data/ipacadmin.gdb</connection-url>

That means that if one day someone is going against hip server #1 and they
put something on a booklist, it will still be there tomorrow when they hit
hip server #2.  And if you change the config on one server it will also
change it on the other without having to repeat yourself.

Of course the ipacadmin.gdb file has to be in the path referred to
(C:/dynix/appserver/jboss/server/default/data/ipacadmin.gdb) on the remote
server.

We've been running this way for quite a while and have had no problems,
though I can't promise it won't mess with statistics (since stats from both
servers will be stored in the same tables in the ipacadmin database).