Difference between revisions of "Dashboard Installation 5.6.x"

From Lingoport Wiki
Jump to: navigation, search
(Installing the Dashboard Client)
 
(51 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=Lingoport Dashboard Overview=
+
=Lingoport Dashboard Components=
 
The Lingoport Dashboard, built on the [http://www.sonarqube.org/ SonarQube] platform, helps you track and share the progress of your globalization effort company-wide, by displaying both high-level and detailed views of your Globalyzer Project Scan data and your Lingoport Resource Manager (LRM) status information.
 
The Lingoport Dashboard, built on the [http://www.sonarqube.org/ SonarQube] platform, helps you track and share the progress of your globalization effort company-wide, by displaying both high-level and detailed views of your Globalyzer Project Scan data and your Lingoport Resource Manager (LRM) status information.
   
 
The Lingoport Dashboard is composed of two components:
 
The Lingoport Dashboard is composed of two components:
*A <b>Server</b> displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.
+
*A <b>Server</b>, which displays the results of Globalyzer scans and/or the Lingoport Resource Manager status in a web browser.
*A <b>Client</b> analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.
+
*A <b>Client</b>, which analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.
 
<p></p>
 
<p></p>
   
 
=Installing the Dashboard Server =
 
=Installing the Dashboard Server =
  +
  +
'''The recommended method for installing the Lingoport Dashboard is to do it as part of the [[Terms_and_Definitions#stackinstaller|Stack Installer]].''' If that method is not practical, follow the installation steps.
  +
 
The <b>Dashboard Server</b> installation creates a MySQL database which is accessed by the Dashboard Client installations.
 
The <b>Dashboard Server</b> installation creates a MySQL database which is accessed by the Dashboard Client installations.
   
Line 13: Line 16:
 
Before installing the Dashboard Server, check that you have met the following requirements:
 
Before installing the Dashboard Server, check that you have met the following requirements:
 
<OL>
 
<OL>
<LI>Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.</LI>
+
<LI>Read the [[Introduction|Lingoport Suite Installation]] section, which describes how all the Lingoport applications work together. Pay close attention to the the hardware and [[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|software configuration requirements]].</LI>
<LI>Selected a target machine that has a <b>supported Operating System</b>: Windows, Linux, or MacOS</LI>
+
<LI>Select a target machine that has the <b>[[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|supported Linux Operating System]]</b></LI>
<LI>Installed <b>Java 7 or greater JRE</b> on the target machine. You can check your Java version using the command line. At the command prompt enter:<br />
+
<LI>Install [[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|supported <b>Java JDK</b>]] on the target machine. You can check your Java version using the command line. At the command prompt enter:<br>
 
<code>java -version</code><br />
 
<code>java -version</code><br />
The version of Java which you have on your system should be displayed. If you need to install Java, please refer to http://www.java.com/en/download/index.jsp or any Java download page which supplies Java 7 or above.</LI>
+
The version of Java which you have on your system should be displayed. If you need to install Java, please refer to http://www.java.com/en/download/index.jsp or any Java download page which supplies the supported Java version.</LI>
 
<LI>Installed <b>MySQL 5.1 or higher</b> on the Dashboard Server or a separate database server.
 
   
  +
<LI>Install [[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|<b>MySQL</b>]] on the Dashboard Server.
* If the database server is not the same machine as the Dashboard Server, then you will need to install the <b>MySQL 5.x Client</b> (only need Client) on the Dashboard Server so that it can access the database on the separate database server.
 
 
 
 
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:
 
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:
<code>mysql -u <user> -p<password></code>
+
: <code>mysql -u <user> -p<password></code>
   
* If MySQL is installed on your system, information on the version will be displayed after entering a valid username and password. If MySQL is not version 5.1 or higher, please refer to a download site, such as [http://dev.mysql.com/downloads MySQL Download] and install an up-to-date version.
+
* If MySQL is installed on your system, information on the version will be displayed after entering a valid username and password. If MySQL is not at the supported version, please refer to a download site, such as [http://dev.mysql.com/downloads MySQL Download] and install an up-to-date version.
   
  +
* You will need to enter the MySQL credentials (username, password and port number) during the installation.</LI>
* If you are running on Windows, make sure that you have your Environment Path set to MySQL's bin directory. Select <code>Control Panel->System->Advanced System Settings->Advanced->Environment Variables</code> and, if necessary, add an entry similar to this to the Path variable: <code>C:\Program Files\MySQL\MySQL Server 5.5\bin</code>
 
   
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.</LI>
+
<LI> Determine <b>the port</b> you will use for connection to the Dashboard Server; the default is 9000. You will need to enter the connection port during the Dashboard Server installation.</LI>
 
<LI> Determine <b>the port</b> you will use for connection to the Dashboard Server; the default is 9000; on Mac the port is usually 9090. You will need to enter the connection port during the Dashboard Server installation.</LI>
 
   
 
<LI>Download the installer jar file <code>Lingoport_Dashboard_Server-<x.x>-Installer.jar</code> (See support@lingoport.com if you don't have that information. It should have been sent in an email based on your license. )</LI>
 
<LI>Download the installer jar file <code>Lingoport_Dashboard_Server-<x.x>-Installer.jar</code> (See support@lingoport.com if you don't have that information. It should have been sent in an email based on your license. )</LI>
Line 42: Line 41:
 
* Double-click on the <code>Lingoport_Dashboard_Server-<x.x>-Installer.jar</code> file, or
 
* Double-click on the <code>Lingoport_Dashboard_Server-<x.x>-Installer.jar</code> file, or
 
* From the command line, cd to the directory with the installer and type:
 
* From the command line, cd to the directory with the installer and type:
<code>java –jar Lingoport_Dashboard_Server-<x.x>-Installer.jar</code>
+
: <code>java –jar Lingoport_Dashboard_Server-<x.x>-Installer.jar</code>
  +
* Installation steps:
 
  +
** '''Installation Path''': Leave this as the default if possible.[/var/lib/jenkins/lingoport/dashboard-server-x.x.x]
The installation process will set up the Dashboard database as well as install the the Dashboard web server.
 
  +
** '''MySQL Database Connection''': This defaults to the current host but very that port is correct and enter the root username and password
  +
** '''Lingoport Dashboard MySQL Database''': Select (1) this if this is the first installation, otherwise select 0.
  +
** '''MySQL Lingodash Database''': Keep the default values of lingodashuser and lingodashpwd for the new database
  +
** '''Lingoport Dashboard Server Connection''': Leave 9000 and 9001 as the default server connections.
  +
** '''Select Installation Packages''': Install all packages.
   
 
===Updating Your Existing Installation===
 
===Updating Your Existing Installation===
If you are <b>upgrading</b> your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.
 
*Double-click on the Lingoport_Dashboard_Server-<x.x>-Installer.jar file, or
 
*From the command line, cd to the directory with the installer jar file and type:
 
<code>java –jar Lingoport_Dashboard_Server-<x.x>-Installer.jar</code>
 
* In <b>Step 5</b> of the installation process, be sure to <b>uncheck</b> the checkbox labeled <b>Install LINGODASH Database Data</b>.
 
   
  +
# Stop the dashboard:
Follow the steps in the next section to start the Dashboard Server. See the section on <b>Upgrading the Dashboard Client</b> for additional upgrade instructions.
 
  +
#: <code>&lt;dashboard-install-location&gt;/bin/linux_x86_64/sonar.sh stop</code>
  +
# use <code>ps aux | grep "dashboard"</code> to confirm that the dashboard has stopped.
  +
# Back up the database with <code>mysqldump <db_name> --user=<username> --password > <output file name> </code>
  +
# (Version 5.6 only):
  +
## Retrieve a copy of the file 'sonarqube-5.6.3.zip'.
  +
##* This file can be found in the stack installer's components folder. Or requested from Lingoport.
  +
## Unzip the sonarqube-5.6.3.zip file under <code>/var/lib/jenkins/lingoport</code>
  +
## This will create a directory <code>'sonarqube-5.6.3'</code> <code>(/var/lib/jenkins/lingoport/sonarqube-5.6.3)</code>. Rename the directory to be <code>'dashboard-server-5.6.1'</code> <code>(/var/lib/jenkins/lingoport/dashboard-server-5.6.1)</code>.
  +
# From the command line, cd to the directory with the installer jar file and type:
  +
#:<code>java –jar Lingoport_Dashboard_Server-<x.x>-Installer.jar</code>
  +
# Make sure you do not overwrite the dashboard database.
  +
  +
See the section on <b>Upgrading the Dashboard Client</b> for additional upgrade instructions.
   
 
===Running the Dashboard Server===
 
===Running the Dashboard Server===
 
After installation, follow these steps to ensure that the server is running and can be successfully displayed:
 
After installation, follow these steps to ensure that the server is running and can be successfully displayed:
* From the command line, cd to the bin directory of where you installed the Dashboard Server and then cd to the appropriate directory for your specific operating system.
+
* From the command line, cd to the bin directory of where you installed the Dashboard Server and then cd to the appropriate directory for your specific operating system. For example:
  +
* For Windows, enter:
 
  +
> cd /var/lib/jenkins/lingoport/dashboard-server-x.x.x/bin/linux-x86-64/
<code>StartSonar</code>
 
*For Mac or Linux, enter:
+
*On the Linux command line, enter:
<code>./sonar.sh start</code>
+
> ./sonar.sh start
  +
Starting SonarQube...
*Check the sonar.log file under the logs directory to make sure there are no errors. It is possible that the connection port is being used by another process. In this case, you may either keep 9000 or 9090 for the Dashboard Server and kill the other process, or modify the Dashboard port number by adjusting the sonar.web.port property in the sonar.properties file in the conf directory.
 
  +
Started SonarQube.
  +
  +
> ./sonar.sh status
  +
SonarQube is running (5497).
  +
  +
*Check the <code>/var/lib/jenkins/lingoport/dashboard-server-x.x.x/logs/sonar.log</code> file to make sure there are no errors.
  +
** It is possible that the connection port is being used by another process. In this case, you may either keep 9000 or 9090 for the Dashboard Server and kill the other process, or modify the Dashboard port number by adjusting the '''sonar.web.port''' property in the <code>/var/lib/jenkins/lingoport/dashboard-server-5.6.1/conf/sonar.properties</code> file.
  +
sonar.web.port=9000
 
* To start the server, open a browser from the server system or another computer that has access to the server and enter:
 
* To start the server, open a browser from the server system or another computer that has access to the server and enter:
<code>http://<hostname>:<port></code>
+
: <code>http://<hostname>:<port></code>
   
 
For example, displaying the Dashboard on the local system with the default port 9000:
 
For example, displaying the Dashboard on the local system with the default port 9000:
<code>http://localhost:9000</code>
+
: <code>http://localhost:9000</code>
You should see the Lingoport Dashboard web page.
+
You should see the Lingoport Dashboard web page. If, instead, you see the message <i>'Sonarqube is under maintenance. Please check back later'</i>, then you need to follow the migration steps below.
  +
  +
[[File: maintenance.jpg|center|500px]]
  +
  +
  +
*Browse to http://localhost:9000/setup and click the 'upgrade' button
  +
  +
  +
[[File: setup.jpg|center|500px]]
  +
  +
  +
*Analyze your projects with the Dashboard Client in order to get fresh measures.
  +
  +
[[File:dashboard_install.jpg|center|500px]]
  +
  +
At this point, the server has been installed successfully and the Lingoport Dashboard Client can be installed.
   
 
===When You Want to Limit Dashboard Server Access===
 
===When You Want to Limit Dashboard Server Access===
 
By default, the Dashboard Server allows installed Dashboard Clients on other machines to push Globalyzer scan and LRM status information to the Server. If instead you want only the Dashboard Client that is installed on the Dashboard Server local machine to be able to access the Dashboard Server, follow these steps:
 
By default, the Dashboard Server allows installed Dashboard Clients on other machines to push Globalyzer scan and LRM status information to the Server. If instead you want only the Dashboard Client that is installed on the Dashboard Server local machine to be able to access the Dashboard Server, follow these steps:
 
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.
 
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.
<code>mysql -u root -p[password]</code>
+
: <code>mysql -u root -p[password]</code>
 
*Execute this command to remove the wildcard host for the dashboard user:
 
*Execute this command to remove the wildcard host for the dashboard user:
<code>DROP USER '<lingoport dashboard user>'@'%';</code>
+
: <code>DROP USER '<lingoport dashboard user>'@'%';</code>
 
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:
 
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:
<code>select user,host from mysql.user;</code>
+
: <code>select user,host from mysql.user;</code>
   
 
You can also be more specific about which hosts you will allow to remotely run the Dashboard Client and push status to the Dashboard database on the Dashboard Server. The following shows granting privileges to all hosts (i.e. undoing what we did above) – but you can change it to a specific host:
 
You can also be more specific about which hosts you will allow to remotely run the Dashboard Client and push status to the Dashboard database on the Dashboard Server. The following shows granting privileges to all hosts (i.e. undoing what we did above) – but you can change it to a specific host:
<code>GRANT ALL PRIVILEGES ON <database>.* TO '<Dashboard User>'@'%' IDENTIFIED BY '<pwd>';</code>
+
: <code>GRANT ALL PRIVILEGES ON <database>.* TO '<Dashboard User>'@'%' IDENTIFIED BY '<pwd>';</code>
   
 
=Installing the Dashboard Client =
 
=Installing the Dashboard Client =
  +
The best way to install the Lingoport Dashboard Client is with the [[Terms_and_Definitions#stackinstaller|Stack Installer]]. If that is not feasible, follow these manual instructions.
  +
 
Run the client installer after the server is <i>installed and running</i>. Typically, the Dashboard Client is installed on a build system, where it can be run as part of a nightly build, pushing up Globalyzer and LRM status to the Dashboard Server.
 
Run the client installer after the server is <i>installed and running</i>. Typically, the Dashboard Client is installed on a build system, where it can be run as part of a nightly build, pushing up Globalyzer and LRM status to the Dashboard Server.
   
<b>Note</b>: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.
+
<b>Note</b>: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Server.
   
==Pre-requisites ==
+
==Prerequisites ==
 
Before installing the Dashboard Client, check that you have met the following requirements:
 
Before installing the Dashboard Client, check that you have met the following requirements:
 
<OL>
 
<OL>
<LI>Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.</LI>
+
<LI>Read the [[Introduction|Lingoport Suite Installation Overview]] section, which describes how all the Lingoport applications work together and the hardware and [[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|software configuration requirements]].</LI>
<LI>Selected a target machine that has a <b>supported Operating System</b>: Windows, Linux, or MacOS</LI>
+
<LI>Select a target machine that has a [[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|<b>supported Linux Operating System</b>]]</LI>
<LI>Installed <b>Java 7 or greater</b> JRE on the target machine. You can check your Java version using the command line. At the command prompt enter:
+
<LI>Install [[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|<b>Java JDK</b>]] on the target machine. You can check your Java version using the command line. At the command prompt enter:
 
<code>java -version</code>
 
<code>java -version</code>
The version of Java which you have on your system should be displayed. If you need to install Java, please refer to http://www.java.com/en/download/index.jsp or any Java download page which supplies Java 7 or above.</LI>
+
The version of Java which you have on your system should be displayed. If you need to install Java, please refer to http://www.java.com/en/download/index.jsp or any Java download page which supplies Java.</LI>
   
<LI>The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).</LI>
+
<LI>The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above). Start <pre>http://localhost:9000</pre></LI>
   
<LI> Know the Globalyzer Client installation directory, if installed.</LI>
+
<LI> Know the Globalyzer Client installation directory, if installed. Typically, this is <code>/var/lib/jenkins/globalyzer-x.y</code></LI>
   
<LI>Know the LRM Client installation directory, if installed.</LI>
+
<LI>Know the LRM Server installation directory, if installed. This is generally: <code>/var/lib/jenkins/lingoport/lrm-server-x.y</code></LI>
   
<LI>Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.</LI>
+
<LI>Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server. The hostname is '''localhost''' and the port defaults to '''3306'''</LI>
<LI>Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.</LI>
+
<LI>Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server. The default value is '''9000'''.</LI>
 
<LI>Downloaded the installer jar file Lingoport_Dashboard_Client-<x.x>-Installer.jar</LI>
 
<LI>Downloaded the installer jar file Lingoport_Dashboard_Client-<x.x>-Installer.jar</LI>
 
</OL>
 
</OL>
Line 111: Line 148:
 
* Double-click on the <code>Lingoport_Dashboard_Client-<x.x>-Installer.jar</code> file, or
 
* Double-click on the <code>Lingoport_Dashboard_Client-<x.x>-Installer.jar</code> file, or
 
* From the command line, cd to the directory with the installer and type:
 
* From the command line, cd to the directory with the installer and type:
<code>java –jar Lingoport_Dashboard_Client-<x.x>-Installer.jar</code>
+
: <code>java –jar Lingoport_Dashboard_Client-<x.x>-Installer.jar</code>
  +
* Installation items
  +
** '''Target Path''': Keep the default which is <code>/var/lib/jenkins/lingoport/dashboard-client-x.y.z</code>
  +
** '''Dashboard Server Host''': localhost
  +
** '''Dashboard Server Port''': 9000
  +
** '''Globalyzer Settings''': Select Globalyzer Settings if Globalyzer is installed.
  +
** '''Globalyzer Connection Settings''': This is the URL for the Globalyzer Server that hosts your rulesets. If Lingoport hosts your rulesets, this will be: <code>https://www.globalyzer.com/gzserver</code>
  +
** '''Login''': The login that is used to access the rulesets on the Globalyzer Server
  +
** '''Globalyzer Client Path''': The path to the installed Globalyzer client on the current system. Often: <code>/var/lib/jenkins/globalyzer-x.y.z/</code>
  +
** '''Installation Packages''': Install all packages.
 
* Follow instructions in the User's Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.
 
* Follow instructions in the User's Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.
   
Line 119: Line 165:
 
*Double-click on the Lingoport_Dashboard_Client-<x.x>-Installer.jar file, or
 
*Double-click on the Lingoport_Dashboard_Client-<x.x>-Installer.jar file, or
 
*From the command line, cd to the directory with the installer jar file and type:
 
*From the command line, cd to the directory with the installer jar file and type:
<code>java –jar Lingoport_Dashboard_Client-<x.x>-Installer.jar</code>
+
: <code>java –jar Lingoport_Dashboard_Client-<x.x>-Installer.jar</code>
 
* If you are using Jenkins or another application to run the Dashboard Client as part of a continuous integration system, you may need to update the Dashboard references to point to the newly installed Dashboard Client.
 
* If you are using Jenkins or another application to run the Dashboard Client as part of a continuous integration system, you may need to update the Dashboard references to point to the newly installed Dashboard Client.
 
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.
 
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.
  +
<p></p>
   
 
= Next Steps =
 
= Next Steps =

Latest revision as of 15:45, 3 October 2019

Lingoport Dashboard Components

The Lingoport Dashboard, built on the SonarQube platform, helps you track and share the progress of your globalization effort company-wide, by displaying both high-level and detailed views of your Globalyzer Project Scan data and your Lingoport Resource Manager (LRM) status information.

The Lingoport Dashboard is composed of two components:

  • A Server, which displays the results of Globalyzer scans and/or the Lingoport Resource Manager status in a web browser.
  • A Client, which analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.

Installing the Dashboard Server

The recommended method for installing the Lingoport Dashboard is to do it as part of the Stack Installer. If that method is not practical, follow the installation steps.

The Dashboard Server installation creates a MySQL database which is accessed by the Dashboard Client installations.

Prerequisites

Before installing the Dashboard Server, check that you have met the following requirements:

  1. Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together. Pay close attention to the the hardware and software configuration requirements.
  2. Select a target machine that has the supported Linux Operating System
  3. Install supported Java JDK on the target machine. You can check your Java version using the command line. At the command prompt enter:
    java -version
    The version of Java which you have on your system should be displayed. If you need to install Java, please refer to http://www.java.com/en/download/index.jsp or any Java download page which supplies the supported Java version.
  4. Install MySQL on the Dashboard Server.
    • You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:
    mysql -u <user> -p<password>
    • If MySQL is installed on your system, information on the version will be displayed after entering a valid username and password. If MySQL is not at the supported version, please refer to a download site, such as MySQL Download and install an up-to-date version.
    • You will need to enter the MySQL credentials (username, password and port number) during the installation.
  5. Determine the port you will use for connection to the Dashboard Server; the default is 9000. You will need to enter the connection port during the Dashboard Server installation.
  6. Download the installer jar file Lingoport_Dashboard_Server-<x.x>-Installer.jar (See support@lingoport.com if you don't have that information. It should have been sent in an email based on your license. )

Installation

Once you have ensured that all requirements are met, run the Dashboard Server installer.

Installing for the First Time

  • Double-click on the Lingoport_Dashboard_Server-<x.x>-Installer.jar file, or
  • From the command line, cd to the directory with the installer and type:
java –jar Lingoport_Dashboard_Server-<x.x>-Installer.jar
  • Installation steps:
    • Installation Path: Leave this as the default if possible.[/var/lib/jenkins/lingoport/dashboard-server-x.x.x]
    • MySQL Database Connection: This defaults to the current host but very that port is correct and enter the root username and password
    • Lingoport Dashboard MySQL Database: Select (1) this if this is the first installation, otherwise select 0.
    • MySQL Lingodash Database: Keep the default values of lingodashuser and lingodashpwd for the new database
    • Lingoport Dashboard Server Connection: Leave 9000 and 9001 as the default server connections.
    • Select Installation Packages: Install all packages.

Updating Your Existing Installation

  1. Stop the dashboard:
    <dashboard-install-location>/bin/linux_x86_64/sonar.sh stop
  2. use ps aux | grep "dashboard" to confirm that the dashboard has stopped.
  3. Back up the database with mysqldump <db_name> --user=<username> --password > <output file name>
  4. (Version 5.6 only):
    1. Retrieve a copy of the file 'sonarqube-5.6.3.zip'.
      • This file can be found in the stack installer's components folder. Or requested from Lingoport.
    2. Unzip the sonarqube-5.6.3.zip file under /var/lib/jenkins/lingoport
    3. This will create a directory 'sonarqube-5.6.3' (/var/lib/jenkins/lingoport/sonarqube-5.6.3). Rename the directory to be 'dashboard-server-5.6.1' (/var/lib/jenkins/lingoport/dashboard-server-5.6.1).
  5. From the command line, cd to the directory with the installer jar file and type:
    java –jar Lingoport_Dashboard_Server-<x.x>-Installer.jar
  6. Make sure you do not overwrite the dashboard database.

See the section on Upgrading the Dashboard Client for additional upgrade instructions.

Running the Dashboard Server

After installation, follow these steps to ensure that the server is running and can be successfully displayed:

  • From the command line, cd to the bin directory of where you installed the Dashboard Server and then cd to the appropriate directory for your specific operating system. For example:
> cd /var/lib/jenkins/lingoport/dashboard-server-x.x.x/bin/linux-x86-64/
  • On the Linux command line, enter:
> ./sonar.sh start
Starting SonarQube...
Started SonarQube.
> ./sonar.sh status
SonarQube is running (5497).
  • Check the /var/lib/jenkins/lingoport/dashboard-server-x.x.x/logs/sonar.log file to make sure there are no errors.
    • It is possible that the connection port is being used by another process. In this case, you may either keep 9000 or 9090 for the Dashboard Server and kill the other process, or modify the Dashboard port number by adjusting the sonar.web.port property in the /var/lib/jenkins/lingoport/dashboard-server-5.6.1/conf/sonar.properties file.
sonar.web.port=9000
  • To start the server, open a browser from the server system or another computer that has access to the server and enter:
http://<hostname>:<port>

For example, displaying the Dashboard on the local system with the default port 9000:

http://localhost:9000

You should see the Lingoport Dashboard web page. If, instead, you see the message 'Sonarqube is under maintenance. Please check back later', then you need to follow the migration steps below.

Maintenance.jpg



Setup.jpg


  • Analyze your projects with the Dashboard Client in order to get fresh measures.
Dashboard install.jpg

At this point, the server has been installed successfully and the Lingoport Dashboard Client can be installed.

When You Want to Limit Dashboard Server Access

By default, the Dashboard Server allows installed Dashboard Clients on other machines to push Globalyzer scan and LRM status information to the Server. If instead you want only the Dashboard Client that is installed on the Dashboard Server local machine to be able to access the Dashboard Server, follow these steps:

  • Log into MySQL on the system where you installed the Dashboard Server, as the root user.
mysql -u root -p[password]
  • Execute this command to remove the wildcard host for the dashboard user:
DROP USER '<lingoport dashboard user>'@'%';
  • Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:
select user,host from mysql.user;

You can also be more specific about which hosts you will allow to remotely run the Dashboard Client and push status to the Dashboard database on the Dashboard Server. The following shows granting privileges to all hosts (i.e. undoing what we did above) – but you can change it to a specific host:

GRANT ALL PRIVILEGES ON <database>.* TO '<Dashboard User>'@'%' IDENTIFIED BY '<pwd>';

Installing the Dashboard Client

The best way to install the Lingoport Dashboard Client is with the Stack Installer. If that is not feasible, follow these manual instructions.

Run the client installer after the server is installed and running. Typically, the Dashboard Client is installed on a build system, where it can be run as part of a nightly build, pushing up Globalyzer and LRM status to the Dashboard Server.

Note: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Server.

Prerequisites

Before installing the Dashboard Client, check that you have met the following requirements:

  1. Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.
  2. Select a target machine that has a supported Linux Operating System
  3. Install Java JDK on the target machine. You can check your Java version using the command line. At the command prompt enter: java -version The version of Java which you have on your system should be displayed. If you need to install Java, please refer to http://www.java.com/en/download/index.jsp or any Java download page which supplies Java.
  4. The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above). Start
    http://localhost:9000
  5. Know the Globalyzer Client installation directory, if installed. Typically, this is /var/lib/jenkins/globalyzer-x.y
  6. Know the LRM Server installation directory, if installed. This is generally: /var/lib/jenkins/lingoport/lrm-server-x.y
  7. Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server. The hostname is localhost and the port defaults to 3306
  8. Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server. The default value is 9000.
  9. Downloaded the installer jar file Lingoport_Dashboard_Client-<x.x>-Installer.jar

Installation

Installing for the First Time

  • Double-click on the Lingoport_Dashboard_Client-<x.x>-Installer.jar file, or
  • From the command line, cd to the directory with the installer and type:
java –jar Lingoport_Dashboard_Client-<x.x>-Installer.jar
  • Installation items
    • Target Path: Keep the default which is /var/lib/jenkins/lingoport/dashboard-client-x.y.z
    • Dashboard Server Host: localhost
    • Dashboard Server Port: 9000
    • Globalyzer Settings: Select Globalyzer Settings if Globalyzer is installed.
    • Globalyzer Connection Settings: This is the URL for the Globalyzer Server that hosts your rulesets. If Lingoport hosts your rulesets, this will be: https://www.globalyzer.com/gzserver
    • Login: The login that is used to access the rulesets on the Globalyzer Server
    • Globalyzer Client Path: The path to the installed Globalyzer client on the current system. Often: /var/lib/jenkins/globalyzer-x.y.z/
    • Installation Packages: Install all packages.
  • Follow instructions in the User's Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.

Updating Your Existing Installation

If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.

  • Double-click on the Lingoport_Dashboard_Client-<x.x>-Installer.jar file, or
  • From the command line, cd to the directory with the installer jar file and type:
java –jar Lingoport_Dashboard_Client-<x.x>-Installer.jar
  • If you are using Jenkins or another application to run the Dashboard Client as part of a continuous integration system, you may need to update the Dashboard references to point to the newly installed Dashboard Client.
  • For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.

Next Steps

If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application's internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User's Guide, located in the lingoport directory of your Server and Client installations.

Lingoport Customer Support

If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.