This is Vishal from Dallas, TX with 15+ years of working experience as Technical/Solution architect for web-based applications. Highly skilled with Java, Spring-Boot, Microservices, Kubernetes, Cloud Services etc. New to OpenMRS and was going through developers & contributors guide. Trying to get my first step in the world of OpenMRS contributors community, if someone can guide me through on where to start would be helping hand.
Thank you. Will be look forward to connect and work together.
I should point out this documentation is a bit out-of-date; if running jdk8 you are only allowed to install reference application 2.x ; you have to run jdk 11 as a minimum to install reference app 3.x (O3) which is the current version. Once more I believe you need to add documentation on how to deploy and setup a local tomcat distribution for testing in addition to the docker setup; many developers are limited to that versus running in a container.
have read until 3.C which looks pretty good. And then following these links here at this Issue Filter
land on 404 pages. I did try opening Good-First-Issues link, getting 404.
thank you for the reply - I have been following that; currently O3 is experimental at best until it can run under JDK17 properly and the openmrs-sdk:setup works with O3 3.4 and platform 2.7.0 at least; I’m looking to see if I need to re-write a bunch of stuff to get it work on these versions. The main concern for this to be offered as a solution is ability to run under JDK17. Once more the data for 2.7.0 platform does not work with platform 2.6.0 as we are currently using JDK11, 2.6.0 and O3 3.2.1 which is limited from running in a production system due to security restrictions. I do notice that I can install 2.7.0 but the reference app will not load for any O3 version; bahmni seems to be the issue.
I am not sure about the backwards compatibility of the data since the Docker reference app setup I just shared has got the latest versions of the modules. @dkayiwa could advise.
There are table differences between 2.6.14 and 2.7.x; the distributed data file deletes and recreates the tables which then render the application non-functional; we opted to just generate our own data and import it for now.
Actually I’m documenting the installation of 3.2.1 and 2.6.14 for our team so re-evaluating the process; we will deal with data as a second step - fyi, we don’t use and cannot use docker; when we move to a container it would be into AWS EKS instead. We have two other systems to integrate so we need it running on a basic server. We will have to stay with 3.2.1 and 2.6.14 since this is the only platform that works under JDK11 and JDK17 using the openmrs-sdk:setup (all other versions fail and I will look at re-developing to resolve the issues = namely bahmni fails in 3.4.0 and 2.7.x)
One other issue I found is the frontend and backend get disconnected if there are updates to the database; but don’t have time to look at that this week.
Yes that is a requirement along with SNOMED and HL7 - we are actually planning to distribute openmrs in Africa - by the way; specifically Nigeria for now and Namibia is next on the list.
Here is what I did for our tomcat test: we ran openmrs-sdk:setup and openmrs-sdk:run to configure and run a local installation; then we wanted to use tomcat so we copied over the openmrs-2.6.14.war to openmrs.war and copied the distribution over to the .OpenMRS directory in our tomcat server - we run the war and used the same database we had generated from the sdk; now we get no user interface modules are installed ; how to we get these recognized if they are already places in .OpenMRS directory? will look deeper into this or let me know what you think is wrong - its our first step to move the reference app to the tomcat server
,