Hi Daniel, Here's a link to the Wiki page for the OpenMRS synchronization module:
https://wiki.openmrs.org/display/docs/Sync+Module The Sync module allows you to set up a network of multiple local servers and have them share a common database. You configure a parent server and then set up networks up child servers; if needed you can set up a hierarchy with parents at multiple levels. You can specify the tables you want to sync, so you don't have to sync tables such as global_properties if you don't want to. The module uses hibernate to do the synchronization. Once installed, you can't make changes to data at the database layer, since these won't be captured by the sync module. The OpenMRS Groovy module can be used to make changes using the API. At this point the sync module is relatively stable if you are using a standard OpenMRS database, but if new objects are added (e.g., through a custom module), it can be a bit buggy. When the sync module encounters a problem it will stop synching, so if you're going to be using it, it's generally a good idea to have a programmer available who could fix bugs relatively quickly (though you can always ping the OpenMRS community for help of couse). Hope this helps, Evan On Nov 9, 2011, at 1:12 AM, Daniel Pepper wrote: Hi Evan, Does the syncing module that you mentioned to me last week enable off-line syncing? If so, that would be very useful for us. Very best, Daniel _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
