These questions may be redundant, but I can’t seem to find any clear threads or documentation. Here are my Questions/situation…
My original Openfire server is at a a centralized location where multiple satellite offices connect and everything works fine. The other day, our Co-location had an internet outage and I soon discovered that our employees have grown to rely on IM capabilities for quick communication. To stop such events from “slowing down” communication in the future, I was thinking about creating either a connection manager in each location or a separate Openfire server then using s2s so everyone can communicate.
End Goal: To have each user login and communicate locally then be able to communicate with other offices, that way if internet connectivity between offices goes down, the local users could still communicate with each other.
Will a Connection manager function like a normal openfire server? or will it merely process logins so there aren’t too many requests at one time to the openfire server?
Is there any detailed documentation for configuring a connection manager?
I have a feeling the s2s will be the “best” solution but how will that effect pre-populated roster’s? Can I edit the .XML roster files in the users profile folder and push that out to users? or will they have to manually add contacts from the other office’s Server?
Anybody else have a similar setup and care to share what they did?
Can this even be done with the free version? or is the enterprise version better suited for this type of setup?