Content:
- Exports Overview
- Background Job to generate the exports
- Scheduling the background Job
- Reading the error Log
Exports Overview:
For endTB we need to regularly export all of the data in the system so that analysis can be performed on it. We can model this export as a set of CSVs that would have all of the data. These CSVs would be linkable through identifier columns in them. The data managers at the local sites would be able to generate these exports and send them to the central location for analysis, as and when needed. The patient information would NOT be exported as a part of this.
Background Job to generate the exports:
Since the exports would take some time to generate (depending on the amount of data in the system), it makes sense to have a background job to generate these exports so that they are readily available for the end user and can be quickly and easily downloaded. Thus we have provided a background job "bahmni_batch" that would generate the exports. This background job's schedule and it's frequency can be adjusted as per the need of the implementation.
Once the frequency is set, the job would run everyday according to that frequency and generate the exports at a prefixed location. These exports would be accessible for the end user through the bahmni application. The user would be able to see the last 20 instance of the exports on the application.
The exports would lie in the following directory in the system:
/home/bahmni/endtb_export
The export can be run at any time by following these steps:
- Login to the server system and open terminal.
Change the user to 'bahmni' by typing in the following command :"sudo su bahmni". This must change your user to bahmni.
Now execute the command '/usr/bin/bahmni-batch'
- The system should show "Running bahmni-batch..."
- When the export is generated the system would give a message "Done"
- Now the export can be accessed at the file location mentioned above
Scheduling the background job:
- Step 1: