Advanced AtomFeed Configuration

Purpose and Benefits

To further configure AtomFeed to suit the needs of your implementation please refer to the config below.

To use Bahmni's inbuilt AtomFeed Console refer to this page.

OpenMRS Atom Feed Configuration

Configuring Relationship Events

• Set atomfeed.publish.eventsForPatientRelationshipChange true in OpenMRS global properties to raise events related to person relationship changes

• Use atomfeed.event.urlPatternForPatientRelationshipChange  OpenMRS global property to configure the object values for the raised events. The default is /openmrs/ws/rest/v1/relationship/%s, where %s represents the relationship uuid.

Configuring Program Events

• Set atomfeed.publish.eventsForPatientProgramStateChange true in OpenMRS global properties to raise events related to person program changes

• Use atomfeed.event.urlPatternForProgramStateChange  OpenMRS global property to configure the object values for the raised events. The default is /openmrs/ws/rest/v1/programenrollment/{uuid}?v=full where {uuid} represents the patientprogram uuid.

OpenERP Atom Feed Configuration

OpenERP Atom Feeds uses the default implementation specified in the Spring configuration files. 

If the implementor wishes to override the default configurations, then they can add entries for the job in 'quartz_cron_scheduler' table in OpenERP database. The jobs that can be configured are as follows:

• customerFeedJobTrigger
• customerFeedfailedJobTrigger
• saleOrderFeedJobTrigger
• saleOrderFeedFailedJobTrigger
• openelisSaleOrderFeedJobTrigger
• openelisSaleOrderFeedFailedJobTrigger
• eventRecordsNumberOffsetMarkerTrigger
• referenceDataFeedJobTrigger
• referenceDataFeedFailedJobTrigger
• openerpDrugFeedQuartzJobTrigger
• openerpDrugFeedQuartzJobFailedTrigger

Sample Configuration

Sample SQL to add a job configuration is:

insert into quartz_cron_scheduler (name, cron_statement, start_delay, enabled) values ('customerFeedJobTrigger','0/15 * * * * ?', 10000,true);