I'm helping my team working on trying to configure ldap settings in
openfire to connect directly to ldap server.  openfire loads the ldap
settings the first time from conf/openfire.xml, but then subsequently
just looks at the database.   I think i found a way to trigger
openfire to load new ldap settings w/o dropping the db, at least not
entirely.

If we call
  delete from ofproperty where name like 'ldap.%';
then restart openfire, it reloads ldap settings from xml into
database. I discovered this by reading JiveGlobals how it "migrates"
values from xml to database on first load.

What do you think?  We rely on a little internal knowledge about
openfire but not that much.

I'm not familiar w/supervisor project yet, if we add to sipx-openfire a command

  sipxopenfire.sh --dropldap

then can we add that as a command to

  sipxopenfire-process.xml

that we call on config reload?
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to