Setting up Sonarqube 7.9.3 LTS as a service on RHEL 7.7

I need to setup Sonarqube 7.9.3 LTS as a service on RHEL 7.7
I read https://docs.sonarqube.org/7.9/setup/operate-server/ and ExecStart is calling the java jar directly, with some java options inline. Would it not be proper to call sonar.sh so that properties in conf directories could be read/honored, or are they still used in this scenario?
Here similar doubts and alternatives are expressed, but I am not sure now what is the right way? Do I even need ExecStop for example? Which is the definite guide?

Thanks in advance for your help.
Dan

Hi @danhersh,

The sonar.properties configuration is still read as usual. sonar.sh additionally bootstraps a wrapper, which loads the wrapper.conf. This has an impact running it as a service, but is mostly useful for certain OS’s or init-style process runners.

I personally don’t have much experience with RHEL or SystemD, but I imagine that both options (java -jar and sonar.sh) would work just fine.

In any case, I’d be curious to know how it goes. Let me know if you run into any issues.

1 Like