On Tue, Apr 19, 2011 at 10:48 AM, Mircea Carasel <[email protected]> wrote: > > > On Tue, Apr 19, 2011 at 6:15 AM, Douglas Hubler <[email protected]> wrote: >> >> Question mostly targeted to Cristi and George, >> >> I extended org.sipfoundry.sipxconfig.admin.TemplateConfigurationFile >> to generate a configuration file for stunnel and another one for >> mongod but I'm not sure how to trigger the file to replicate. I want >> stunnel file to replicate when Location objects are added/removed or >> when locations change their ip addresses. Do i need to listen for >> save/delete events on Location objects then give my file to the >> ReplicationManager? > > Replication triggering in general is spread across contexts.
I thought that this is not not the case anymore for 4.6 and replication is handled by ReplicationTrigger only (that already listen to Location save / delete events and in turn calls ReplicationManagerImpl.replicateLocation / ReplicationManagerImpl.removeLocation). However I noticed we still have LocationsDaoListener so I am a little bit confused. My suggestion is to add that 2 files as supervisor configuration files - check sipxSupervisorService bean and its configurations property inside service.beans.xml. LocationsDaoListener will replicate them as supervisor service config files on save or delete > > >> I also want it to replication when profiles are >> send to a machine for the first time or when admin explicitly pushes >> profiles to a server. >> If you declare that files as config files for supervisor then they will be replicated automatically for the first time or when admin send profiles to server >> Do i need to list them in a process definition xml file? >> You have to list them so supervisor to be aware of (sipxsupervisor-process.xml) George _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
