I am in the process of understanding the features of the latest OpenMRS Platform 2.6.11 which I got installed in MAC using the OpenMRS SDK.
As I am not aware of the flows to test, I was planning to try out with the demo data available in the following link:
https://openmrs.atlassian.net/wiki/spaces/docs/pages/26273323/Demo+Data
I am using MySQL DB V9.0.1 and was trying out to use the latest demo data (large-demo-data-2-2-1.sql.gz).
Behavior of demo data with Platform V2.6.11
The demo data gets installed in DB successfully.
After the DB update, the UI doesn’t seem to work well due to the schema differences between the demo data and the 2.6.11 platform’s schema.
So, I tried utilizing the demo data with Platform V2.2.x.
Behavior of demo data with Platform V2.2.x
Code: openmrs-core (Branch: 2.2.x)
OpenMRS Platform 2.2.x requires MySQL 5.7 which is not installable in MAC (as it has reached EndOfLife in Oct2023).
Code gets compiled (mvn clean package)
When trying to run after compilation:
Starting Jetty Server (mvn jetty:run)
Visit http://localhost:8080/openmrs/initialsetup in browser; during which the following error occurs (after which we are not able to proceed):
Unable to create the database. The password might be incorrect or the database is not started.???Error executing sql: create database if not exists ? default character set utf8 - Could not create connection to database server. Attempted reconnect 3 times. Giving up.???
Can somebody please help me out to utilize the demo data (large-demo-data-2-2-1.sql.gz) with OpenMRS Platform 2.6.11(or) point me to the demo data that works well with OpenMRS Platform 2.6.11?
Hi @dkayiwa , I tried utilizing the demo data for platform 2.7.0 in the O3 Distribution deployment that I performed using the OpenMRS SDK. In the O3 distribution, I could see that the OpenMRS platform 2.6.11 got deployed and I installed Reference Application 3.3.0-SNAPSHOT. In order to use 2.7.0 demo data you uploaded today, I did the following steps:
1. Directly updated the DB with 2.7.0 demo data by importing the openmrs-2-7-0.sql.
2. Executed “mvn openmrs-sdk:run” - this got executed with some errors while starting some modules.
3. Once, the application came up, I couldn’t login with “admin/Admin123”. Instead, the login worked with “admin/test”.
4. When I tried to to select “Manage Modules” in Admin section (), I could see that the following modules had start-up errors:
- There was an error starting the module: FHIR2
- There was an error starting the module: Open Concept Lab Module
- There was an error starting the module: Queue
- There was an error starting the module: Metadata Mapping
- There was an error starting the module: Bed Management Module
- There was an error starting the module: Reporting
- There was an error starting the module: EMR API Module
- There was an error starting the module: Reporting REST
- There was an error starting the module: ID Generation
- There was an error starting the module: OpenHMIS Billing Module
- There was an error starting the module: Bahmni Appointment Scheduling
- There was an error starting the module: Reference Demo Data Module
With the behavior noticed after the DB update, I doubt the way I updated the DB with the 2.7.0 demo data (ie., importing openmrs-2-7-0.sql into the DB directly).
Can you please help me out with the correct method to make the 2.7.0 demo data available for the platform (2.6.11) / app (3.3.0-SNAPSHOT) installed using the OpenMRS SDK?
Thanks for the reply @dkayiwa. I could that by default the value of " referencedemodata.createDemoPatientsOnNextStartup" appears as 50 which works fine when deploying O3 Distribution using the OpenMRS SDK. With the default setup, the application gets started successfully.
But, When I tried setting that value as 55 and then restart the OpenMRS app, I could see that the “patients” table in the DB gets updated when extra 55 patients (with total patients in the table summing up to 105). The application never starts up after this change. I could see the following logs in the console:
https://pastebin.com/dU9hwm2Q.
NOTE: Today, I performed the following steps:
Deployed O3 distribution using the OpenMRS SDK (Build deployed: OpenMRS Platform 2.6.12.ad24d7d))
Updated referencedemodata.createDemoPatientsOnNextStartup to 55 and restarted the app.
Didn’t imported openmrs-2-7-0.sql into the DB.
Can you please guide me on the following:
Why the application is failing to start after updating referencedemodata.createDemoPatientsOnNextStartup value?
How to use openmrs-2-7-0.sql once O3 Distribution is deployed using the OpenMRS SDK?
I could see some demo data being added by default when deploying the O3 Distribution using the OpenMRS SDK. Is that demo data the same as the demo data present in openmrs-2-7-0.sql?