Hi Gary,
Low volume. Since these are the SM's, they will stay connected once booted.
The only time an SQL query would be needed is when something gets added or
changed.
A handful per day.
That's why it isn't really worth trying to duplicate the entire database and
maintain two copies.
On the other hand, do I really want Radius to depend on ACT! as a single
point of failure?
A more robust solution would be to have a couple radius servers,
and a couple database engines on the back end that are in sync for possible
failover.
There is only one ACT! box.
By putting what I need into the Radius system (linux boxen), if ACT! should
fail, Radius won't.
It might not be getting any updates, but it won't bring down the entire
network.
I've come full circle here. I think I need to spend some time with ACT! and
convince it to
trigger an update in the MySQL database (and reboot the SM to force a new
access-request).
Just not sure what I will need on the FreeRadius side, if any.
It might just be only between ACT! and MySQL.
----- Original Message -----
From: "Gary Gatten" <[email protected]>
To: "'FreeRadius users mailing list'"
<[email protected]>
Sent: Tuesday, April 05, 2011 03:52 PM
Subject: RE: Can FreeRadius connect to ACT! database?
Option 4.) Dump data from ACT to a "real" DB, then dump ACT completely?
j/k - sorta... Does ACT support triggers and / or stored procedures? If
so it would be relatively easy to keep a subset of the ACT DB in MySQL (or
whatever) and keep it synchronized.
If ACT is ODBC, I'm sure one could install an ODBC driver and write a
query in SQL ( or whatever ACT uses). At that point it wouldn't be any
different than any other backend data store.
There is probably an option 5 - 10 as well. Is this a high volume
environment? How many requests per sec / minute are we guestimating? I
ask because if it's low you have many more options than if it's high.
G
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
