Hi Michiel,
Thanks for the answer; There's some food for thought in there.
Of course, we don't use a MySQL server for our Customer data; That
would have been too easy... ;-) So the proxy solution doesn't
apply. (We use a MS-SQL non-clustered backend btw)
My understanding is now the following:
For LDAP:
- The LDAP solution I gave works ok for Auth.pm as a
connection to one of the LDAP servers is initiated at every
agent login (see Kernel::System::Auth::LDAP->Auth()).
- The LDAP solution I gave wouldn't work perfectly for
CustomerUser.pm as a connection to one of the LDAP servers
would be initiated at application startup, and kept open until
application ends (see
Kernel::System::CustomerUser::LDAP->new()). Failover to
another LDAP server would thus require restarting the
application.
For ODBC:
- I can't use 2 data backends as OTRS crashes when any of the
backends is unavailable + it's not efficient (but I don't
really matter about that)
Based on this understanding, I think I'll go for a scripted import
of CustomerUser and CustomerCompany data.
Other options that I'm still considering are:
- Customize OTRS so that it won't die when a CustomerUser
backend isn't available => This doesn't seem doable
- Customize OTRS so that it accepts a 2nd DSN to try to
connect to in case it fails to connect to the primary one at
application startup => Restarting the application would
still be needed in case of backend failure.
- Add DBD::Multiplex support to OTRS => Doesn't seem well
supported (no package in Ubuntu)
((enjoy))
Cyrille
Le 25/04/2013 09:54, Michiel Beijen a écrit :