Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS »
Discussion: OpenMRS Talk »
Real-Time: IRC Chat

Projects

Skip to end of metadata
Go to start of metadata

In order to be flexible, Sync should provide the following variables in order to give implementers the flexibility to administer the Sync operations.

List of variables

Variable NameDescriptionDefault Value
General
sync.parent.feedLocationThe location of the Parent atom feed. Required to do any synchronization. If not set (but with Sync enabled), sync log warnings and not read the feeds.

Empty

sync.local.feedLocationThe location of the local event feed for this node. Generally should not change.The default address.
Push
sync.push.enabledBoolean - is pushing data to Parent enabled? If set to false, no data will ever be sent to Parent from this Child and the Child will not be reading its own feed.True
sync.push.scheduleCron schedule reading the local feed - controls how often data will be pushed to Parent.Hourly schedule
sync.push.{classname}.enabledBoolean - controls if the data for the given entity class is pushed to Parent from this node. Affects filtering of the local atom feed.True for classes we want to sync out of the box
Pull
sync.pull.enabledBoolean - is pulling data from Parent enabled? If set to false, no data will ever be retrieved from Parent and this Child will not follow the feed of its Parent.True
sync.pull.scheduleCron schedule reading the Parent feed - controls how often data will be pulled from Parent.Hourly schedule
sync.pull.{classname}.enabledBoolean - controls if the data for the given entity class is pulled from Parent to this node. Affects filtering of the Parent atom feed.True for classes we want to sync out of the box

 

All configuration for error handling described in Auditing and error handling should also be included.

Configuration UI

The Sync configuration from Sync 2.0 configuration variables should be easily configurable by administrators through the UI. The UI should validate the inputs and display errors to the administrators if he tries to submit invalid data. For now inputs can be fairly simple - i.e. we do not need a sophisticated cron picker for schedules, it is a nice to have of course.

  • No labels