We download the sonar-2.12.zip (from this page<\/a>) and unzip it. This creates a sonar-2.12<\/strong> directory.<\/p>\n In this directory, go to the \\conf<\/strong> sub-directory and edit the sonar.properties<\/strong> file. Here, the credentials for a sonar<\/strong> user are already defined:<\/p>\n sonar.jdbc.username: sonar<\/strong> We don’t want to use the default Derby database so, as indicated, we comment the following lines:<\/p>\n # Comment the following lines to deactivate the default embedded database. And we look to the section dedicated to Oracle to define the access to our Oracle database:<\/p>\n sonar.jdbc.url: jdbc:oracle:thin:@localhost:1521\/JPORA11<\/strong> And that’s all for the Sonar configuration.<\/p>\n Now, we need to find the Oracle JDBC driver (thin client) \u2018ojdbc6.jar\u2019 (look into \\jdbc\\lib into your Oracle installation) and copy it to the directory \\extensions\\jdbc-driver\\oracle<\/strong>.<\/p>\n Last step: build the sonar.war file that we will use to deploy Sonar in Tomcat. But first, I recommand you to download (from this page<\/a>) all the Sonar plugins that you want to install. Just put them into the Sonar directory \\extensions\\plugins<\/strong>. It is not mandatory to do it now, you can wait. But if you do it later, you will have to start again Sonar in order to load the plugin, so better do it now.<\/p>\n Just run the build-war.bat<\/strong> file from the \\war<\/strong> directory and soon you will have the sonar.war file created.<\/p>\n We can now deploy it under Tomcat. I just copy it under C:\\Program Files (x86)\\Apache Software Foundation\\Tomcat 7.0\\webapps<\/strong>. Start Tomcat, and it will create a new \\sonar<\/strong> directory with all the contents of the .war file.<\/p>\n Ah, don’t forget to configure the Tomcat Java pool to 512 Mb, as seen in the Sonar – Our environment<\/a> page.<\/p>\n We download the sonar-runner-1.1.zip directly from the Java Runner documentation page on Sonar site<\/a> and unzip it. We now have a sonar-runner-1.1<\/strong> directory.<\/p>\n In this directory, we go to the \\conf<\/strong> directory and edit the sonar-runner.properties<\/strong> file.<\/p>\n We do not want to use this file to define parameters specific to an analysis, as for example the source directory. So we comment the first lines:<\/p>\n #—– Default directory layout<\/strong> We want to dedicate this file only to the connection with the Sonar ‘server’ which is in fact our Sonar webapp under Tomcat. So, we just indicate its url:<\/p>\n #—– Default Sonar server<\/strong> And the informations to connect to our Oracle database, as previously indicated during the Sonar installation.<\/p>\n #—– Oracle #—– Global database settings And that’s it. To launch the Java Runner, we just have to run the sonar-runner.bat<\/strong> which is located into the \\sonar-runner-1.1\\bin<\/strong> directory. But this will the subject of our next post about our 1st analysis with Sonar<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" The objectives of this post are to describe the installation of Sonar. We also want to install the Sonar Java Runner, to show that we can use Sonar without Maven or Ant.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-71","post","type-post","status-publish","format-standard","hentry","category-sonar-installation"],"_links":{"self":[{"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/posts\/71"}],"collection":[{"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/comments?post=71"}],"version-history":[{"count":2,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/posts\/71\/revisions"}],"predecessor-version":[{"id":73,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/posts\/71\/revisions\/73"}],"wp:attachment":[{"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/media?parent=71"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/categories?post=71"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/tags?post=71"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n sonar.jdbc.password: sonar<\/strong><\/p>\n
\nsonar.jdbc.url: jdbc:derby:\/\/localhost:1527\/sonar;create=true<\/strong>
\nsonar.jdbc.driverClassName: org.apache.derby.jdbc.ClientDriver<\/strong><\/p>\n
\nsonar.jdbc.driverClassName: oracle.jdbc.driver.OracleDriver<\/strong><\/p>\n![\"\"](\"http:\/\/qualilogy.com\/wp-content\/uploads\/2011\/12\/Sonar_url.jpg\" "\\"Sonar_url\\"")
<\/a>Now, from my browser, I can access Sonar at the url corresponding to this web application under Tomcat.<\/p>\nJava Runner Installation<\/span><\/h3>\n
\n#<\/strong>sources=src\/main\/java<\/strong>
\n#<\/strong>tests=src\/test\/java<\/strong>
\n#<\/strong>binaries=target\/classes<\/strong><\/p>\n
\nsonar.host.url=http:\/\/localhost:8888\/sonar\/<\/strong><\/p>\n
\nsonar.jdbc.url: jdbc:oracle:thin:@localhost:1521\/JPORA11<\/strong>
\nsonar.jdbc.driverClassName: oracle.jdbc.driver.OracleDriver<\/strong><\/p>\n
\nsonar.jdbc.username: sonar<\/strong>
\nsonar.jdbc.password: sonar<\/strong><\/p>\n