Trouble setting up the standalone


I have downloaded the Platform 2.2.0 Standalone Edition of Openmrs. After the server is set up am of-course taken to the page that says

If you are seeing this page, it means that the OpenMRS Platform is running successfully, but no user interface module is installed

I am having trouble getting to have the UI installed since I copied the .omod file (legacyui-{versionNumber}.omod) into the modules directory of the OpenMRS app data folder in the Standalone folder. What could I be missing because it won’t start with the UI as before? Am also following this link as well but still.

Any help @dkayiwa @mozzy @ruhanga

Why don’t you use the SDK?

Yes I do have the SDK as well but would it be a problem having the two? Not running at the same time but so as to get to see effects of code change more easily since am working on a legacyUI ticket whose effect I need to know is implemented?

For some things, you do not need to ask before trying out yourself to see what happens.

Reason why I wanted to install the Standalone version although setting up the UI has held me back a bit which I need some clarification on

You can still set up the UI using the SDK.

1 Like

I have a quick inquiry, when building the .OMOD file manually, running mvn clean install -Dmaven.test.skip=true is done under the directory C:\Users\Admin\legacyui> or generally under C:\Users\Admin> in the terminal because I did a copy and paste of legacyui-1.6.0-SNAPSHOT.OMOD file into the modules folder in the referenceapplication-package-2.6.0

I thought you are just starting by reproducing the problem reported on the ticket? In that case, running the SDK and choose the reference application distribution option would be enough to give you a platform with modules including the legacyui.

That then means seeing the effect of any code changes would just require a page refresh under openmrs/options.form in the ReffApp because doing that, I haven’t seen any effect of any changes made in the code

Can you read my previous post once again?

Yes I do have distribution running, and I see the legacyui module is there as well. As for reproducing the reported problem via the ticket, what I needed note of is seeing effect of the code change I made over the ReffApp on the required page.

Reproducing the reported problem does not require making any code change.

Oh yes, I have it reproduced with

After making the code changes, did you compile and redeploy the module?

That is what am not so sure doing

Is this of help?

1 Like

@dkayiwa there seems to be a new problem, starting the server and here is a pastebin error I receive trying to access via the browser not sure why though and here are the server logs. What is not happening because I haven’t actually compiled or redeployed the module, still going through the link

Can you just set up a new version of the reference application distribution using the SDK?

OK! just set-up the ReffApp anew let me then compile and redeploy the module

I compiled the legacyui module I have with the command mvn clean install -Dmaven.test.skip=true and then in the RefApp went to Add module and browsed for the .OMOD file under legacyui/omod/target/legacyui-1.6.0-SNAPSHOT.omod but I get the following ERROR