Message-ID: <682281704.2131.1432583895615.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2130_1751427419.1432583895614" ------=_Part_2130_1751427419.1432583895614 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The SonarQube platform is made of 3 components:
Several database engines are s= upported.
Create an empty schema and a sonarqube user. Grant this sonarqube user p= ermissions to create, update and delete objects for this schema. The charse= t of the database has to be set to "UTF-8" and the language (data= base and user) to "English". Here is a sample script for MySQL.
Note that collation must be case-sensitive (CS) and accent-sensiti= ve (AS).
There are two well-known engines that can be used in MySQL: MyISAM and I= nnoDB. MyISAM is the oldest of the two engines and is being progressively r= eplaced by InnoDB. InnoDB is clearly faster and scales better with Son= arQube as the number of projects under quality control increases. If you we= re an early adopter of SonarQube, you probably have a series of table that = are still using MyISAM. To improve performances, you should change the engi= ne for all tables to InnoDB.
Once all SonarQube tables are using the InnoDB engine, the first thing t=
o do is allocate a maximum amount of RAM to your MySQL instance with the
query_cache_size parameter. Read this article about InnoDB Performa=
nce Optimization Basics for more information.
When having two SonarQube schemas on the same Oracle instance, especiall= y if they are of two different versions, SonarQube gets confused and picks = the first it finds. To fix this issue:
Or a trigger should be defined on Oracle side to automatically alter= the SonarQube Oracle user session when establishing a new connection:
If you want to use a custom schema and not the default "public"=
; one, the PostgreSQL
search_path property must be set:
First, check the requiremen= ts.
<install_directory>= (below) refers to the path to the directory where the SonarQube distributi= on has been unzipped.
Edit <install_directory>/conf/sonar.properties t= o configure the database settings. Templates are available for every suppor= ted database. Just uncomment and configure the template you need and commen= t out the lines dedicated to H2:
Drivers for the supported databases (except Oracle) are already provided= . Do not replace the provided drivers; they are the only ones supported.
For Oracle, copy the JDBC driver into <install_directory>= /extensions/jdbc-driver/oracle.
The default port is "9000" and the context path is "/&quo= t;. These values can be changed in <install_directory>/c= onf/sonar.properties:
Execute the following script to star= t the server:
By default, SonarQube is configured to run on any computer with a simple= Java JRE.
For better performance, the first thing to do when installing a producti= on instance is to use a Java JDK and activate the server mode by uncommenti= ng/setting the following line in <install_directory>/con= f/sonar.properties:
To change the Java JVM used by SonarQube, simply edit <install_di= rectory>/conf/wrapper.conf and update the following line:<= /p>
Multiple analyzers are available:
We do not recommend to use an anti= virus on the machine where a SonarQube analysis runs, it could generate unp= redictable behavior.
This error happens when the temporary file path specified for the Local = System doesn't exist. Assuming that environment variables have their defaul= t settings and that Windows is installed on the C drive, the following path= s should exist:
In most cases, the Temp folder is missing and should = be created. See SONAR-2660.
By default, remote access to MySQL database server is disabled for secur= ity reasons. If you want to remotely access the database server from the So= nar Maven plugin, you need to follow this quick guide.
SonarQube seems unable to start when installed under the Program Fil= es directory on Windows Vista. It should therefore not be installed th= ere.
When another(s) USERS table exists in the Oracle DB, if the sonarqube us= er has read access on this other USERS table, the SonarQube web server can'= t start and an exception like the following one is thrown:
To fix this issue,= the rights of the sonarqube Oracle user must be decreased to remove read a= ccess on the other(s) USERS table(s).
Double check that settings for proxy in file SONARQUBE_HOME/conf/son=
ar.properties are correctly set.
Note that if your username = contains "\" (backslash), then it should be escaped - for example= username "domain\user" in file should look like:
For some proxies, exception "java.net.ProtocolException: Server red= irected too many times" might mean incorrect username or password.