Dashboard Users Guide

From Lingoport Wiki
Revision as of 17:30, 13 July 2021 by Masnes (talk | contribs) (Removing an Uploaded Lingoport Dashboard Project)
Jump to: navigation, search


About Lingoport Dashboard

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

For more details about Globalyzer and Lingoport Resource Manager please visit: Lingoport Suite.

Dashboard7.8.1 overview.PNG

When to Update the Dashboard Server

You will need to re-run the Lingoport Dashboard Server Installer whenever you upgrade to a later version of the Dashboard. Be sure to retain your current Dashboard database by reusing the database name

For more details, see Updating Your Existing Installation.

When to Update the Dashboard Client

You will need to re-run the Lingoport Dashboard Client Installer whenever you:

  • Set up a new or updated version of Globalyzer
  • Set up a new or updated version of Localyzer
  • Upgrade to a later version of the Lingoport Dashboard Client

Starting the Dashboard Server

Simple Startup

  1. On the system where the Lingoport Dashboard Server was installed, go to the directory <server install directory>/bin.
  2. > cd /var/lib/jenkins/lingoport/dashboard-server-x.y.z/bin/
  3. Choose your platform directory and then run sonar.sh start. To make sure that it started, check the status sonar.sh status.
  4. > cd linux-x86-64
    > ./sonar.sh start
    > ./sonar.sh status
  5. Give it a few minutes and then open a browser and enter http://localhost to see the Dashboard. If you installed with a port such as 9000, use that port after localhost (http://localhost:9000).
  6. If the browser comes up in maintenance mode, the database may need to be upgraded. Enter http://localhost/setup and follow the directions on the page.

Starting as a Service

To run the Sonar process as a service, follow the instructions at SonarQube.

Viewing the Lingoport Dashboard

  1. On your local system, open a browser and enter the host name and port number of the Lingoport Dashboard Server. For example: http://company.net/
  2. Click the Help on Lingoport Dashboard link at the bottom of the page to learn more about the Lingoport Dashboard features.
  3. Read the SonarQube introduction to learn about the capabilities of the SonarQube framework.
  4. For administration features, click LOG IN in the menu bar and enter:
    Login: admin
    Password: admin
    Be sure to change the password. As the Administrator, you will be able to adjust the dashboard configuration, as well as add Users and Groups to fine tune access to your Lingoport Dashboard Projects.

Uploading Project Data to the Lingoport Dashboard

Generate Globalyzer Scan Report

Generate Localyzer Status Report

Upload Globalyzer and Localyzer Data to Dashboard

Removing an Uploaded Lingoport Dashboard Project

Permanently Deleting a Project

Permanently deleting a project entirely removes it from the dashboard. While it may later be re-created, you will lose any historical data associated with the project.

To delete a project, you must have permissions to administer it.

With the project open, select 'Administration[Project]' then Deletion.

Db project delete admin .png

You will be prompted for deletion. Confirm.

Db project delete confirm.png

Bulk project deletion

To bulk hide projects, you must have general administer permission on the dashboard.

To bulk delete projects, first go to Administration[Global] at the black bar. Then under the Administration heading, select Projects->Management.

Db project bulk management goto.png

You will see a list of all projects, with up to 50 entries initially shown.

Db project bulk management list.png

Search and sort the projects as you find most appropriate, then select all that you wish to delete.

Db project search selected.png

Select the red 'Delete' option to the top right. Then confirm the popup.

Db project search delete poppup.png

Hiding the Project

Hiding a project is a non-permanent removal option. The project may later be un-hidden to restore it with existing data intact.

To hide a project, you must have permissions to administer it.

Click on Administration[Project], then Permissions.

Db administer project permissions.png

Select Private, so that the project is only shown to authorized users.

Db project private.png

Then, uncheck all permissions for all users and groups. You may still wish to leave the project visible to sonar-administrators, or you may prefer to hide it entirely.

Db project permissions remove.png

Changing Project Configuration


MySQL Packet Error

A communication packet is a single SQL statement sent to the MySQL server, a single row that is sent to the client, or a binary log event sent from a master replication server to a slave.

The largest possible packet that can be transmitted to or from a MySQL 5.7 server or client is 1GB.

When a MySQL client or the mysqld server receives a packet bigger than max_allowed_packet bytes, it issues an ER_NET_PACKET_TOO_LARGE error and closes the connection. With some clients, you may also get a Lost connection to MySQL server during query error if the communication packet is too large.

Both the client and the server have their own max_allowed_packet variable, so if you want to handle big packets, you must increase this variable both in the client and in the server.

To resolve this issue, please see the steps below:

Set max_allowed_packet in the /etc/my.cnf file. For example, to set the size for the server to 16MB, add the following lines in an option file:

max_allowed_packet = 16M

Stop the service, typically with:

 > sudo service mysqld stop 

verify it's stopped and restart it:

> sudo service mysqld status
> sudo service mysqld start

To verify the packet size allowed has been modified, in MySQL do :

mysql> show variables like 'max_allowed_packet';


Finally, restart sonar so that it picks up the MySQL change:

jenkins: > sonar.sh stop
Stopping SonarQube...
Waiting for SonarQube to exit...
Stopped SonarQube.

jenkins: > sonar.sh start
Starting SonarQube...
Started SonarQube.