Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current ·  View Page History

Prerequisite

The only prerequisite for running Sonar is to have Java (Oracle JRE 6 onwards) installed on your machine.

Hardware Requirements

  1. The Sonar web server requires at least 500Mb of RAM to run efficiently.
  2. The amount of disk space you need will depend on how much code you analyze with Sonar. As an example, Nemo the public instance of Sonar, has more than 13 millions Lines of Code under analysis with 4 years of history. Nemo is currently running on a Amazon EC2 small instance, using  about 10 Gb of drive space

Supported Platforms

Java

 

Oracle JRE

(tick) 6
(tick) 7

IBM JRE

(error)

GCJ

(error)

Oracle JRockit(error)

Database

Apache Derby

(tick) Prior to Sonar 3.2. Bundled with Sonar but supported for evaluation use only. Although using the Derby database gives access to a fully functional version, upgrades are disabled. Therefore, before deploying to a production environment, we strongly recommend that you use an enterprise database.

H2(tick) Since Sonar 3.2. Bundled with Sonar but supported for evaluation use only. Although using the H2 database gives access to a fully functional version, upgrades are disabled. Therefore, before deploying to a production environment, we strongly recommend that you use an enterprise database.

Microsoft SQL Server

(tick) 2005 with bundled jTDS driver. Microsoft drivers are not supported. Express Edition is supported.
(tick) 2008 with bundled jTDS driver. Microsoft drivers are not supported. Express Edition is supported.
(warning) Collation must be case-sensitive (CS) and accent-sensitive (AS)

MySQL

(tick) 5.0, 5.1 and 5.5 with the driver packaged with Sonar.
(warning) 5.6 is supported in Sonar 3.5 (see SONAR-4137).

Oracle

(tick) 10G with Oracle 11.2.x drivers
(tick) 11G with Oracle 11.2.x drivers
(tick) XE Editions are supported
(warning) The driver ojdbc14.jar is not supported
(warning) Only the thin mode is supported, not OCI

PostgreSQL

(tick) 8.3
(tick) 8.4
(tick) 9.0
(tick) 9.1

Application Server

Jetty 6

(tick) Bundled with Sonar

Apache Tomcat

(tick) 5.5
(tick) 6.0
(tick) 7.0

JBoss(error)
GlassFish(error)

 Web Browser

To get the full experience Sonar has to offer, you should enable Javascript in your browser.

Microsoft Internet Explorer

(tick) IE7 (not compatible with Views administration console)
(tick) IE8
(tick) IE9

Mozilla Firefox

(tick) Supported

Google Chrome

(tick) Supported

Opera

(warning) Not tested

Safari

(tick) Supported


 

Unable to render {include} The included page could not be found.
Unable to render {include} The included page could not be found.
 
Unable to render {include} The included page could not be found.

How to Upgrade

Note that you can directly upgrade from one version to another. For example, to upgrade from version 3.1 to version 3.5, it is not necessary to first upgrade to version 3.2, then to version 3.3, and so on.

  1. Check compatibility of installed plugins
    • If Sonar is not connected to the Internet, check for minimum required versions listed in this page.
    • If Sonar is connected to the Internet, the Update Center lists all the plugins to upgrade or to uninstall:

  2. Read notes below for each version
  3. Stop Sonar:

  4. Download and unzip Sonar in a fresh directory, let's say {$NEW_SONAR_HOME}
  5. Update the content of the sonar.properties and wrapper.conf files located in the {$NEW_SONAR_HOME}/conf directory according of the content of the related files in the {$OLD_SONAR_HOME}/conf directory
  6. Copy the directories extensions/plugins and extensions/rules from {$OLD_SONAR_HOME} to {$NEW_SONAR_HOME} (if you see problems while starting, try to remove the copied plugins from the extensions/plugins-directory and reinstall the plugins manually via the webinterface)
  7. If a custom JDBC driver is used, copy it into {$NEW_SONAR_HOME}/extensions/jdbc-driver/<dialect>
  8. Doing a database backup is recommended
  9. If Sonar is deployed on a Tomcat or Jetty server, build the WAR file by executing the script {$NEW_SONAR_HOME}/war/build-war
  10. Start server (or deploy war on server):

  11. Browse to http://localhost:9000/setup (replace "localhost:9000" by your own URL) and follow the setup instructions
  12. Analyze your projects to get fresh measures

Upgrading can take a while depending on the size of projects portfolio. To monitor the process, check the logs and the console.

Upgrade is completed when an analysis has been run on project. Only at that point will you get new functionality working for sure.

Release Upgrade Notes

Usually Sonar releases come with some specific recommendations for upgrading from the previous version. You have to read the upgrade notes for all versions between your current version and the target version.

Unable to render {include} The included page could not be found.
Unable to render {include} The included page could not be found.

Labels
  • None