<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.lingoport.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Lcameron</id>
	<title>Lingoport Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.lingoport.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Lcameron"/>
	<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/Special:Contributions/Lcameron"/>
	<updated>2026-04-30T19:00:21Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.3</generator>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88603</id>
		<title>MVN Plugin</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88603"/>
		<updated>2016-11-17T18:03:56Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Globalyzer has a number of clients: The Workbench, the command line interface, Lite, the Ant client, and the MVN plugin. When using a MVN project, you can add code scanning with Globalyzer using our MVN plugin. &lt;br /&gt;
It is well suited for use within automation routines and Continuous Integration (CI) systems as well as within a typical developer environment, for instance within Integrated Development Environments (IDEs).&lt;br /&gt;
&lt;br /&gt;
The Globalyzer MVN plugin generates scan reports to a directory specified in the pom.xml file. Scan reports are available in a variety of formats. We ask our MVN customers to install the MVN plugin in a private MVN repository for that company. &lt;br /&gt;
&lt;br /&gt;
The steps to use the Globalyzer MVN plugin are the same as any MVN plugin:&lt;br /&gt;
* Install the plugin&lt;br /&gt;
* Configure the pom.xml&lt;br /&gt;
* Run MVN&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Install the Globalyzer MVN Plugin ==&lt;br /&gt;
&lt;br /&gt;
The MVN plugin can be downloaded from the Client Download Page on the Globalyzer Server.&lt;br /&gt;
The file name is globalyzer-maven-plugin-x.y.z.jar where x.y.z is the version for the plugin, for instance 5.3.0. We ask that this jar file be installed in a private MVN repository at the customer&#039;s site.&lt;br /&gt;
&lt;br /&gt;
For example, a developer who wants to install the plugin in their local .m2 repository can use the following installation command, provided for version &amp;lt;code&amp;gt;5.3.0&amp;lt;/code&amp;gt; of the MVN plugin. The same applies to other versions.&lt;br /&gt;
&lt;br /&gt;
  C:\Users\Yourname&amp;gt;&#039;&#039;&#039;mvn install:install-file&#039;&#039;&#039; -Dfile=&amp;quot;C:/Path/to/the/plugin/jarfile/&#039;&#039;&#039;globalyzer-maven-plugin-5.3.0.jar&#039;&#039;&#039;&amp;quot; -DgroupId=&#039;&#039;&#039;com.lingoport.globalyzer.client.maven&#039;&#039;&#039; -DartifactId=&#039;&#039;&#039;globalyzer-maven-plugin&#039;&#039;&#039; -Dversion=&#039;&#039;&#039;5.3.0&#039;&#039;&#039; -Dpackaging=&#039;&#039;&#039;maven-plugin&#039;&#039;&#039;&lt;br /&gt;
  [INFO] Scanning for projects...&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Building Maven Stub Project (No POM) 1&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] --- maven-install-plugin:2.4:install-file (default-cli) @ standalone-pom ---&lt;br /&gt;
  [INFO] Installing C:\Linternal\Installers\install\globalyzer-maven-plugin-5.3.0.jar to C:\Users\Yourname\.m2\repository\com\lingoport\globalyzer\client\maven\globalyzer-maven-plugin\5.3.0\globalyzer-maven-plugin-5.3.0.jar&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] BUILD SUCCESS&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Total time: 0.615 s&lt;br /&gt;
  [INFO] Finished at: 2016-09-09T15:49:59-06:00&lt;br /&gt;
  [INFO] Final Memory: 7M/123M&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
== Configure the Globalyzer MVN Plugin ==&lt;br /&gt;
The &amp;lt;code&amp;gt;&amp;lt;build&amp;gt;&amp;lt;plugins&amp;gt;&amp;lt;/code&amp;gt; section of your module&#039;s pom.xml file must be configured. Here is how:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
  &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
  &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
  &amp;lt;version&amp;gt;5.3.0&amp;lt;/version&amp;gt;&lt;br /&gt;
  &amp;lt;configuration&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-required - &#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;username&amp;gt;joe@company.com&amp;lt;/username&amp;gt;&lt;br /&gt;
           &amp;lt;password&amp;gt;joespw&amp;lt;/password&amp;gt;&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;ruleSetName&amp;gt;Java Rule Set&amp;lt;/ruleSetName&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-optional -&#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings -&#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;serverUrl&amp;gt;&amp;lt;/serverUrl&amp;gt;  (default: https://www.globalyzer.com/gzserver)     &lt;br /&gt;
           &amp;lt;dataDictionaryDir&amp;gt;&amp;lt;/dataDictionaryDir&amp;gt;  ( default: userhome/.globalyzer )&lt;br /&gt;
           &amp;lt;scanTimeout&amp;gt;&amp;lt;/scanTimeout&amp;gt;  ( default: 120 seconds )&lt;br /&gt;
           &amp;lt;filterWithDictionary&amp;gt;&amp;lt;/filterWithDictionary&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;setLog4jProperties&amp;gt;&amp;lt;/setLog4jProperties&amp;gt;  ( default: true )&lt;br /&gt;
           &amp;lt;log4jPropertiesFileDir&amp;gt;&amp;lt;/log4jPropertiesFileDir&amp;gt; ( default: Globalyzer provided )    &lt;br /&gt;
           &amp;lt;enhancedScanning&amp;gt;&amp;lt;/enhancedScanning&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;clearCache&amp;gt;&amp;lt;/clearCache&amp;gt;  ( default: false )&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings -&#039;&#039;&#039;    &lt;br /&gt;
           &amp;lt;projectName&amp;gt;&amp;lt;/projectName&amp;gt;  ( default: project artifact )    &lt;br /&gt;
           &amp;lt;projectDir&amp;gt;&amp;lt;/projectDir&amp;gt;  ( default: project src/main/java )&lt;br /&gt;
           &amp;lt;ruleSetOwner&amp;gt;&amp;lt;/ruleSetOwner&amp;gt;  ( default: username )&lt;br /&gt;
           &amp;lt;scanName&amp;gt;&amp;lt;/scanName&amp;gt;  ( default: auto-generate ) &lt;br /&gt;
           &amp;lt;!-- choices:                     --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedXML        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedExcel      --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedCSV        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryHtml        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryText        --&amp;gt;&lt;br /&gt;
           &amp;lt;reportType&amp;gt;&amp;lt;/reportType&amp;gt;  ( default: ScanDetailedXML )&lt;br /&gt;
           &amp;lt;reportPath&amp;gt;&amp;lt;/reportPath&amp;gt;  ( default: target/i18n )        &lt;br /&gt;
  &amp;lt;/configuration&amp;gt;&lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Notes: &lt;br /&gt;
* The &amp;lt;b&amp;gt;&amp;lt;code&amp;gt;session level settings &amp;lt;/code&amp;gt;&amp;lt;/b&amp;gt; are set once per MVN invocation. Whichever scan / project goal is executed first, its configuration will be set for all the subsequent scans&lt;br /&gt;
* The &amp;lt;code&amp;gt;log4jPropertiesFileDir&amp;lt;/code&amp;gt; is precisely that: which log4j &amp;lt;b&amp;gt;configuration&amp;lt;/b&amp;gt; file to use if &amp;lt;code&amp;gt;setLog4jProperties&amp;lt;/code&amp;gt; is set to true. For example, if that setting points to &amp;lt;code&amp;gt;/path/to/log4j.properties&amp;lt;/code&amp;gt; and in that configuration, the appender points to &amp;lt;code&amp;gt;/path/to/globalyzer/log&amp;lt;/code&amp;gt;, that&#039;s where the logs will be written out.&lt;br /&gt;
* Best would be to have the &amp;lt;b&amp;gt;exact same configuration&amp;lt;/b&amp;gt; for all Globalyzer goals to make sure one configuration is not taking over the other ones.&lt;br /&gt;
* By default, &amp;lt;code&amp;gt;enhancedScanning&amp;lt;/code&amp;gt; takes place. However, this detailed scanning takes a lot of memory. If you find that you are running out of memory when scanning, try setting this to false.&lt;br /&gt;
* By default, &amp;lt;code&amp;gt;clearCache&amp;lt;/code&amp;gt; is set to false. This attribute only makes sense if &amp;lt;code&amp;gt;enhancedScanning&amp;lt;/code&amp;gt; is set to true. It&#039;s a way to try to reduce the amount of memory used when performing detailed scanning.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Running Globalyzer MVN Plugin From The Command Prompt / Shell ==&lt;br /&gt;
&lt;br /&gt;
Globalyzer MVN Plugin can be executed from a command prompt or shell via the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn com.lingoport.globalyzer.client.maven:globalyzer-maven-plugin:5.3.0:scan&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After MVN finishes each scan, a Globalyzer report per scan is created at the location specified in the pom.xml report path. The default location for the reports are target/i18n for each MVN module.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have configured the execution to be in the &amp;lt;code&amp;gt;validate&amp;lt;/code&amp;gt; phase, you can run the simpler command: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn validate&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(See the multi-scan example below)&lt;br /&gt;
&lt;br /&gt;
== Multi-Threaded Support ==&lt;br /&gt;
The Globalyzer MVN plugin does not support multi-threaded invocation. &lt;br /&gt;
&lt;br /&gt;
== Multi-Scan Projects ==&lt;br /&gt;
&lt;br /&gt;
To execute more than one scan on a MVN project, use as many &amp;quot;execution&amp;quot; as you have rule sets to apply to scan the code. For instance, two scans will be performed with the following snippet, one using the &amp;lt;code&amp;gt;testjava&amp;lt;/code&amp;gt; rule set, the other using the &amp;lt;code&amp;gt;testjavascript&amp;lt;/code&amp;gt; rule set:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
        &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
        &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
        &amp;lt;version&amp;gt;5.3.0&amp;lt;/version&amp;gt;&lt;br /&gt;
        &amp;lt;executions&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
            &#039;&#039;&#039;&amp;lt;id&amp;gt;execution1&amp;lt;/id&amp;gt;&lt;br /&gt;
            &amp;lt;phase&amp;gt;validate&amp;lt;/phase&#039;&#039;&#039;&amp;gt;&lt;br /&gt;
              &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjava&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;java-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
              &amp;lt;/configuration&amp;gt;&lt;br /&gt;
               &amp;lt;goals&amp;gt;&lt;br /&gt;
                  &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;/goals&amp;gt;            &lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
          &#039;&#039;&#039;&amp;lt;id&amp;gt;execution2&amp;lt;/id&amp;gt;&lt;br /&gt;
           &amp;lt;phase&amp;gt;validate&amp;lt;/phase&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
            &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjavascript&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;javascript-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
             &amp;lt;/configuration&amp;gt;&lt;br /&gt;
             &amp;lt;goals&amp;gt;&lt;br /&gt;
               &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
             &amp;lt;/goals&amp;gt;&lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
        &amp;lt;/executions&amp;gt;                  &lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sharing pom.xml Files Between IDEs and Build Systems ==&lt;br /&gt;
&lt;br /&gt;
It is common to check in a single &amp;lt;code&amp;gt;pom.xml&amp;lt;/code&amp;gt; per code repository. However, some configuration on a developer&#039;s laptop may be different from a build system.&lt;br /&gt;
&lt;br /&gt;
A possibility to bridge the environment is to keep the most Globalyzer specific configuration only in the pom.xml file and to move the system side in the settings.xml file.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88602</id>
		<title>MVN Plugin</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88602"/>
		<updated>2016-11-17T17:59:40Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Globalyzer has a number of clients: The Workbench, the command line interface, Lite, the Ant client, and the MVN plugin. When using a MVN project, you can add code scanning with Globalyzer using our MVN plugin. &lt;br /&gt;
It is well suited for use within automation routines and Continuous Integration (CI) systems as well as within a typical developer environment, for instance within Integrated Development Environments (IDEs).&lt;br /&gt;
&lt;br /&gt;
The Globalyzer MVN plugin generates scan reports to a directory specified in the pom.xml file. Scan reports are available in a variety of formats. We ask our MVN customers to install the MVN plugin in a private MVN repository for that company. &lt;br /&gt;
&lt;br /&gt;
The steps to use the Globalyzer MVN plugin are the same as any MVN plugin:&lt;br /&gt;
* Install the plugin&lt;br /&gt;
* Configure the pom.xml&lt;br /&gt;
* Run MVN&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Install the Globalyzer MVN Plugin ==&lt;br /&gt;
&lt;br /&gt;
The MVN plugin can be downloaded from the Client Download Page on the Globalyzer Server.&lt;br /&gt;
The file name is globalyzer-maven-plugin-x.y.z.jar where x.y.z is the version for the plugin, for instance 5.3.0. We ask that this jar file be installed in a private MVN repository at the customer&#039;s site.&lt;br /&gt;
&lt;br /&gt;
For example, a developer who wants to install the plugin in their local .m2 repository can use the following installation command, provided for version &amp;lt;code&amp;gt;5.3.0&amp;lt;/code&amp;gt; of the MVN plugin. The same applies to other versions.&lt;br /&gt;
&lt;br /&gt;
  C:\Users\Yourname&amp;gt;&#039;&#039;&#039;mvn install:install-file&#039;&#039;&#039; -Dfile=&amp;quot;C:/Path/to/the/plugin/jarfile/&#039;&#039;&#039;globalyzer-maven-plugin-5.3.0.jar&#039;&#039;&#039;&amp;quot; -DgroupId=&#039;&#039;&#039;com.lingoport.globalyzer.client.maven&#039;&#039;&#039; -DartifactId=&#039;&#039;&#039;globalyzer-maven-plugin&#039;&#039;&#039; -Dversion=&#039;&#039;&#039;5.3.0&#039;&#039;&#039; -Dpackaging=&#039;&#039;&#039;maven-plugin&#039;&#039;&#039;&lt;br /&gt;
  [INFO] Scanning for projects...&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Building Maven Stub Project (No POM) 1&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] --- maven-install-plugin:2.4:install-file (default-cli) @ standalone-pom ---&lt;br /&gt;
  [INFO] Installing C:\Linternal\Installers\install\globalyzer-maven-plugin-5.3.0.jar to C:\Users\Yourname\.m2\repository\com\lingoport\globalyzer\client\maven\globalyzer-maven-plugin\5.3.0\globalyzer-maven-plugin-5.3.0.jar&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] BUILD SUCCESS&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Total time: 0.615 s&lt;br /&gt;
  [INFO] Finished at: 2016-09-09T15:49:59-06:00&lt;br /&gt;
  [INFO] Final Memory: 7M/123M&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
== Configure the Globalyzer MVN Plugin ==&lt;br /&gt;
The &amp;lt;code&amp;gt;&amp;lt;build&amp;gt;&amp;lt;plugins&amp;gt;&amp;lt;/code&amp;gt; section of your module&#039;s pom.xml file must be configured. Here is how:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
  &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
  &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
  &amp;lt;version&amp;gt;5.3.0&amp;lt;/version&amp;gt;&lt;br /&gt;
  &amp;lt;configuration&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-required - &#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;username&amp;gt;joe@company.com&amp;lt;/username&amp;gt;&lt;br /&gt;
           &amp;lt;password&amp;gt;joespw&amp;lt;/password&amp;gt;&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;ruleSetName&amp;gt;Java Rule Set&amp;lt;/ruleSetName&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-optional -&#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings -&#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;serverUrl&amp;gt;&amp;lt;/serverUrl&amp;gt;  (default: https://www.globalyzer.com/gzserver)     &lt;br /&gt;
           &amp;lt;dataDictionaryDir&amp;gt;&amp;lt;/dataDictionaryDir&amp;gt;  ( default: userhome/.globalyzer )&lt;br /&gt;
           &amp;lt;scanTimeout&amp;gt;&amp;lt;/scanTimeout&amp;gt;  ( default: 120 seconds )&lt;br /&gt;
           &amp;lt;filterWithDictionary&amp;gt;&amp;lt;/filterWithDictionary&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;setLog4jProperties&amp;gt;&amp;lt;/setLog4jProperties&amp;gt;  ( default: true )&lt;br /&gt;
           &amp;lt;log4jPropertiesFileDir&amp;gt;&amp;lt;/log4jPropertiesFileDir&amp;gt; ( default: Globalyzer provided )    &lt;br /&gt;
           &amp;lt;enhancedScanning&amp;gt;&amp;lt;/enhancedScanning&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;clearCache&amp;gt;&amp;lt;/clearCache&amp;gt;  ( default: false )&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings -&#039;&#039;&#039;    &lt;br /&gt;
           &amp;lt;projectName&amp;gt;&amp;lt;/projectName&amp;gt;  ( default: project artifact )    &lt;br /&gt;
           &amp;lt;projectDir&amp;gt;&amp;lt;/projectDir&amp;gt;  ( default: project src/main/java )&lt;br /&gt;
           &amp;lt;ruleSetOwner&amp;gt;&amp;lt;/ruleSetOwner&amp;gt;  ( default: username )&lt;br /&gt;
           &amp;lt;scanName&amp;gt;&amp;lt;/scanName&amp;gt;  ( default: auto-generate ) &lt;br /&gt;
           &amp;lt;!-- choices:                     --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedXML        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedExcel      --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedCSV        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryHtml        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryText        --&amp;gt;&lt;br /&gt;
           &amp;lt;reportType&amp;gt;&amp;lt;/reportType&amp;gt;  ( default: ScanDetailedXML )&lt;br /&gt;
           &amp;lt;reportPath&amp;gt;&amp;lt;/reportPath&amp;gt;  ( default: target/i18n )        &lt;br /&gt;
  &amp;lt;/configuration&amp;gt;&lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Notes: &lt;br /&gt;
* The &amp;lt;b&amp;gt;&amp;lt;code&amp;gt;session level settings &amp;lt;/code&amp;gt;&amp;lt;/b&amp;gt; are set once per MVN invocation. Whichever scan / project goal is executed first, its configuration will be set for all the subsequent scans&lt;br /&gt;
* The &amp;lt;code&amp;gt;log4jPropertiesFileDir&amp;lt;/code&amp;gt; is precisely that: which log4j &amp;lt;b&amp;gt;configuration&amp;lt;/b&amp;gt; file to use if &amp;lt;code&amp;gt;setLog4jProperties&amp;lt;/code&amp;gt; is set to true. For example, if that setting points to &amp;lt;code&amp;gt;/path/to/log4j.properties&amp;lt;/code&amp;gt; and in that configuration, the appender points to &amp;lt;code&amp;gt;/path/to/globalyzer/log&amp;lt;/code&amp;gt;, that&#039;s where the logs will be written out.&lt;br /&gt;
* Best would be to have the &amp;lt;b&amp;gt;exact same configuration&amp;lt;/b&amp;gt; for all Globalyzer goals to make sure one configuration is not taking over the other ones.&lt;br /&gt;
* By default, &amp;lt;code&amp;gt;enhancedScanning&amp;lt;/code&amp;gt; takes place. However, this detailed scanning takes a lot&lt;br /&gt;
of memory. If you find that you are running out of memory when scanning, try setting this to false.&lt;br /&gt;
* By default, &amp;lt;code&amp;gt;clearCache&amp;lt;/code&amp;gt; is set to false. This attribute only makes sense if&lt;br /&gt;
&amp;lt;code&amp;gt;enhancedScanning&amp;lt;/code&amp;gt; is set to true. It&#039;s a way to try to reduce the amount of memory used&lt;br /&gt;
when performing detailed scanning.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Running Globalyzer MVN Plugin From The Command Prompt / Shell ==&lt;br /&gt;
&lt;br /&gt;
Globalyzer MVN Plugin can be executed from a command prompt or shell via the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn com.lingoport.globalyzer.client.maven:globalyzer-maven-plugin:5.3.0:scan&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After MVN finishes each scan, a Globalyzer report per scan is created at the location specified in the pom.xml report path. The default location for the reports are target/i18n for each MVN module.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have configured the execution to be in the &amp;lt;code&amp;gt;validate&amp;lt;/code&amp;gt; phase, you can run the simpler command: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn validate&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(See the multi-scan example below)&lt;br /&gt;
&lt;br /&gt;
== Multi-Threaded Support ==&lt;br /&gt;
The Globalyzer MVN plugin does not support multi-threaded invocation. &lt;br /&gt;
&lt;br /&gt;
== Multi-Scan Projects ==&lt;br /&gt;
&lt;br /&gt;
To execute more than one scan on a MVN project, use as many &amp;quot;execution&amp;quot; as you have rule sets to apply to scan the code. For instance, two scans will be performed with the following snippet, one using the &amp;lt;code&amp;gt;testjava&amp;lt;/code&amp;gt; rule set, the other using the &amp;lt;code&amp;gt;testjavascript&amp;lt;/code&amp;gt; rule set:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
        &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
        &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
        &amp;lt;version&amp;gt;5.3.0&amp;lt;/version&amp;gt;&lt;br /&gt;
        &amp;lt;executions&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
            &#039;&#039;&#039;&amp;lt;id&amp;gt;execution1&amp;lt;/id&amp;gt;&lt;br /&gt;
            &amp;lt;phase&amp;gt;validate&amp;lt;/phase&#039;&#039;&#039;&amp;gt;&lt;br /&gt;
              &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjava&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;java-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
              &amp;lt;/configuration&amp;gt;&lt;br /&gt;
               &amp;lt;goals&amp;gt;&lt;br /&gt;
                  &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;/goals&amp;gt;            &lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
          &#039;&#039;&#039;&amp;lt;id&amp;gt;execution2&amp;lt;/id&amp;gt;&lt;br /&gt;
           &amp;lt;phase&amp;gt;validate&amp;lt;/phase&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
            &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjavascript&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;javascript-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
             &amp;lt;/configuration&amp;gt;&lt;br /&gt;
             &amp;lt;goals&amp;gt;&lt;br /&gt;
               &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
             &amp;lt;/goals&amp;gt;&lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
        &amp;lt;/executions&amp;gt;                  &lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sharing pom.xml Files Between IDEs and Build Systems ==&lt;br /&gt;
&lt;br /&gt;
It is common to check in a single &amp;lt;code&amp;gt;pom.xml&amp;lt;/code&amp;gt; per code repository. However, some configuration on a developer&#039;s laptop may be different from a build system.&lt;br /&gt;
&lt;br /&gt;
A possibility to bridge the environment is to keep the most Globalyzer specific configuration only in the pom.xml file and to move the system side in the settings.xml file.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88601</id>
		<title>MVN Plugin</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88601"/>
		<updated>2016-11-16T19:37:53Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Globalyzer has a number of clients: The Workbench, the command line interface, Lite, the Ant client, and the MVN plugin. When using a MVN project, you can add code scanning with Globalyzer using our MVN plugin. &lt;br /&gt;
It is well suited for use within automation routines and Continuous Integration (CI) systems as well as within a typical developer environment, for instance within an Integrated Development Environments (IDEs).&lt;br /&gt;
&lt;br /&gt;
The Globalyzer MVN plugin generates scan reports to a directory specified the pom.xml file. Scan reports are available in a variety of formats. We ask our MVN customers to install the MVN plugin in a private MVN repository for that company. &lt;br /&gt;
&lt;br /&gt;
The steps to use the Globalyzer MVN plugin are the same as any MVN plugin:&lt;br /&gt;
* Install the plugin&lt;br /&gt;
* Configure the pom.xml&lt;br /&gt;
* Run MVN&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Install the Globalyzer MVN Plugin ==&lt;br /&gt;
&lt;br /&gt;
For those customers who require the MVN plugin, we make the globalyzer-maven-plugin-x.y.z-jar-with-dependencies.jar file available for download where x.y.z is the version for the plugin, for instance 5.2.1. We ask that this jar file be installed in a private MVN repository at the customer&#039;s side.&lt;br /&gt;
You first need to get the file from a secure FTP location, which will be sent to customers who request it. Lingoport customers can request the MVN plugin by sending an email to &amp;lt;code&amp;gt;support at lingoport dot com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, a developer who wants to install the plugin in their local .m2 repository can use the following installation command, provided for a version &amp;lt;code&amp;gt;5.3.0&amp;lt;/code&amp;gt; of the MVN plugin. The same applies to other versions.&lt;br /&gt;
&lt;br /&gt;
  C:\Users\Yourname&amp;gt;&#039;&#039;&#039;mvn install:install-file&#039;&#039;&#039; -Dfile=&amp;quot;C:\Path\to\the\plugin\jarfile\&#039;&#039;&#039;globalyzer-maven-plugin-5.3.0-jar-with-dependencies.jar&#039;&#039;&#039;&amp;quot; -DgroupId=&#039;&#039;&#039;com.lingoport.globalyzer.client.maven&#039;&#039;&#039; -DartifactId=&#039;&#039;&#039;globalyzer-maven-plugin&#039;&#039;&#039; -Dversion=&#039;&#039;&#039;5.3.0&#039;&#039;&#039; -Dpackaging=&#039;&#039;&#039;maven-plugin&#039;&#039;&#039;&lt;br /&gt;
  [INFO] Scanning for projects...&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Building Maven Stub Project (No POM) 1&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] --- maven-install-plugin:2.4:install-file (default-cli) @ standalone-pom ---&lt;br /&gt;
  [INFO] Installing C:\Linternal\Installers\install\globalyzer-maven-plugin-5.3.0.jar to C:\Users\Yourname\.m2\repository\com\lingoport\globalyzer\client\maven\globalyzer-maven-plugin\5.3.0\globalyzer-maven-plugin-5.3.0.jar&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] BUILD SUCCESS&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Total time: 0.615 s&lt;br /&gt;
  [INFO] Finished at: 2016-09-09T15:49:59-06:00&lt;br /&gt;
  [INFO] Final Memory: 7M/123M&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
== Configure the Globalyzer MVN Plugin ==&lt;br /&gt;
The &amp;lt;code&amp;gt;&amp;lt;build&amp;gt;&amp;lt;plugins&amp;gt;&amp;lt;/code&amp;gt; section of your module&#039;s pom.xml file must be configured. Here is how:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
  &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
  &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
  &amp;lt;version&amp;gt;5.3.0&amp;lt;/version&amp;gt;&lt;br /&gt;
  &amp;lt;configuration&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-required - &#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;username&amp;gt;joe@company.com&amp;lt;/username&amp;gt;&lt;br /&gt;
           &amp;lt;password&amp;gt;joespw&amp;lt;/password&amp;gt;&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;ruleSetName&amp;gt;Java Rule Set&amp;lt;/ruleSetName&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-optional -&#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings -&#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;serverUrl&amp;gt;&amp;lt;/serverUrl&amp;gt;  (default: https://www.globalyzer.com/gzserver)     &lt;br /&gt;
           &amp;lt;dataDictionaryDir&amp;gt;&amp;lt;/dataDictionaryDir&amp;gt;  ( default: userhome/.globalyzer )&lt;br /&gt;
           &amp;lt;scanTimeout&amp;gt;&amp;lt;/scanTimeout&amp;gt;  ( default: 120 seconds )&lt;br /&gt;
           &amp;lt;filterWithDictionary&amp;gt;&amp;lt;/filterWithDictionary&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;setLog4jProperties&amp;gt;&amp;lt;/setLog4jProperties&amp;gt;  ( default: true )&lt;br /&gt;
           &amp;lt;log4jPropertiesFileDir&amp;gt;&amp;lt;/log4jPropertiesFileDir&amp;gt; ( default: Globalyzer provided )    &lt;br /&gt;
           &amp;lt;enhancedScanning&amp;gt;&amp;lt;/enhancedScanning&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;clearCache&amp;gt;&amp;lt;/clearCache&amp;gt;  ( default: false )&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings -&#039;&#039;&#039;    &lt;br /&gt;
           &amp;lt;projectName&amp;gt;&amp;lt;/projectName&amp;gt;  ( default: project artifact )    &lt;br /&gt;
           &amp;lt;projectDir&amp;gt;&amp;lt;/projectDir&amp;gt;  ( default: project src/main/java )&lt;br /&gt;
           &amp;lt;ruleSetOwner&amp;gt;&amp;lt;/ruleSetOwner&amp;gt;  ( default: username )&lt;br /&gt;
           &amp;lt;scanName&amp;gt;&amp;lt;/scanName&amp;gt;  ( default: auto-generate ) &lt;br /&gt;
           &amp;lt;!-- choices:                     --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedXML        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedExcel      --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedCSV        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryHtml        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryText        --&amp;gt;&lt;br /&gt;
           &amp;lt;reportType&amp;gt;&amp;lt;/reportType&amp;gt;  ( default: ScanDetailedXML )&lt;br /&gt;
           &amp;lt;reportPath&amp;gt;&amp;lt;/reportPath&amp;gt;  ( default: target/i18n )        &lt;br /&gt;
  &amp;lt;/configuration&amp;gt;&lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Notes: &lt;br /&gt;
* The &amp;lt;b&amp;gt;&amp;lt;code&amp;gt;session level settings &amp;lt;/code&amp;gt;&amp;lt;/b&amp;gt; are set once per MVN invocation. Whichever scan / project goal is executed first, its configuration will be set for all the subsequent scans&lt;br /&gt;
* The &amp;lt;code&amp;gt;log4jPropertiesFileDir&amp;lt;/code&amp;gt; is precisely that: which log4j &amp;lt;b&amp;gt;configuration&amp;lt;/b&amp;gt; file to use is the &amp;lt;code&amp;gt;setLog4jProperties/code&amp;gt; is set to true. For for example, if that setting points to &amp;lt;code&amp;gt;/path/to/log4j.properties&amp;lt;/code&amp;gt; and in that configuration, the appender points to &amp;lt;code&amp;gt;/path/to/globalyzer/log&amp;lt;/code&amp;gt;, that&#039;s where the logs will be written out.&lt;br /&gt;
* Best would be to have the &amp;lt;b&amp;gt;exact same configuration&amp;lt;/b&amp;gt; for all Globalyzer goals to make sure one configuration is not taking over the other ones.&lt;br /&gt;
&lt;br /&gt;
== Running Globalyzer MVN Plugin From The Command Prompt / Shell ==&lt;br /&gt;
&lt;br /&gt;
Globalyzer MVN Plugin can be executed from a command prompt or shell via the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn com.lingoport.globalyzer.client.maven:globalyzer-maven-plugin:5.3.0:scan&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After MVN finishes each scan, a Globalyzer report per scan is created at the location specified in the pom.xml report path. The default location for the reports are target/i18n for each MVN module.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have configured the execution to be in the &amp;lt;code&amp;gt;validate&amp;lt;/code&amp;gt; phase, you can run the simpler command: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn validate&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(See the multi-scan example below)&lt;br /&gt;
&lt;br /&gt;
== Multi-Threaded Support ==&lt;br /&gt;
The Globalyzer MVN plugin does not support multi-threaded invocation. &lt;br /&gt;
&lt;br /&gt;
== Multi-Scan Projects ==&lt;br /&gt;
&lt;br /&gt;
To execute more than one scan on a MVN project, use as many &amp;quot;execution&amp;quot; as you have rule sets to apply to scan the code. For instance, two scans will be performed with the following snippet, one using the &amp;lt;code&amp;gt;testjava&amp;lt;/code&amp;gt; rule set, the other using the &amp;lt;code&amp;gt;testjavascript&amp;lt;/code&amp;gt; rule set:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
        &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
        &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
        &amp;lt;version&amp;gt;5.3.0&amp;lt;/version&amp;gt;&lt;br /&gt;
        &amp;lt;executions&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
            &#039;&#039;&#039;&amp;lt;id&amp;gt;execution1&amp;lt;/id&amp;gt;&lt;br /&gt;
            &amp;lt;phase&amp;gt;validate&amp;lt;/phase&#039;&#039;&#039;&amp;gt;&lt;br /&gt;
              &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjava&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;java-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
              &amp;lt;/configuration&amp;gt;&lt;br /&gt;
               &amp;lt;goals&amp;gt;&lt;br /&gt;
                  &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;/goals&amp;gt;            &lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
          &#039;&#039;&#039;&amp;lt;id&amp;gt;execution2&amp;lt;/id&amp;gt;&lt;br /&gt;
           &amp;lt;phase&amp;gt;validate&amp;lt;/phase&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
            &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjavascript&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;javascript-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
             &amp;lt;/configuration&amp;gt;&lt;br /&gt;
             &amp;lt;goals&amp;gt;&lt;br /&gt;
               &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
             &amp;lt;/goals&amp;gt;&lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
        &amp;lt;/executions&amp;gt;                  &lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sharing pom.xml Files Between IDEs and Build Systems ==&lt;br /&gt;
&lt;br /&gt;
It is common to check in a single &amp;lt;code&amp;gt;pom.xml&amp;lt;/code&amp;gt; per code repository. However, some configuration on a developer&#039;s laptop may be different from a build system.&lt;br /&gt;
&lt;br /&gt;
A possibility to bridge the environment is to keep the most Globalyzer specific configuration only in the pom.xml file and to move the system side in the settings.xml file.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88600</id>
		<title>MVN Plugin</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88600"/>
		<updated>2016-11-16T18:35:34Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Globalyzer has a number of clients: The Workbench, the command line interface, Lite, the Ant client, and the MVN plugin. When using a MVN project, you can add code scanning with Globalyzer using our MVN plugin. &lt;br /&gt;
It is well suited for use within automation routines and Continuous Integration (CI) systems as well as within a typical developer environment, for instance within an Integrated Development Environments (IDEs).&lt;br /&gt;
&lt;br /&gt;
The Globalyzer MVN plugin generates scan reports to a directory specified the pom.xml file. Scan reports are available in a variety of formats. We ask our MVN customers to install the MVN plugin in a private MVN repository for that company. &lt;br /&gt;
&lt;br /&gt;
The steps to use the Globalyzer MVN plugin are the same as any MVN plugin:&lt;br /&gt;
* Install the plugin&lt;br /&gt;
* Configure the pom.xml&lt;br /&gt;
* Run MVN&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Install the Globalyzer MVN Plugin ==&lt;br /&gt;
&lt;br /&gt;
For those customers who require the MVN plugin, we make the globalyzer-maven-plugin-x.y.z-jar-with-dependencies.jar file available for downloadm where x.y.z is the version for the plugin, for instance 5.2.1. We ask that this jar file be installed in a private MVN repository at the customer&#039;s side.&lt;br /&gt;
You first need to get the file from a secure FTP location, which will be sent to customers who request it. Lingoport customers can request the MVN plugin by sending an email to &amp;lt;code&amp;gt;support at lingoport dot com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, a developer who wants to install the plugin in their local .m2 repository can use the following installation command, provided for a version &amp;lt;code&amp;gt;5.2.1&amp;lt;/code&amp;gt; of the MVN plugin. The same applies to other versions.t&lt;br /&gt;
&lt;br /&gt;
  C:\Users\Yourname&amp;gt;&#039;&#039;&#039;mvn install:install-file&#039;&#039;&#039; -Dfile=&amp;quot;C:\Path\to\the\plugin\jarfile\&#039;&#039;&#039;globalyzer-maven-plugin-5.2.1-jar-with-dependencies.jar&#039;&#039;&#039;&amp;quot; -DgroupId=&#039;&#039;&#039;com.lingoport.globalyzer.client.maven&#039;&#039;&#039; -DartifactId=&#039;&#039;&#039;globalyzer-maven-plugin&#039;&#039;&#039; -Dversion=&#039;&#039;&#039;5.2.1&#039;&#039;&#039; -Dpackaging=&#039;&#039;&#039;maven-plugin&#039;&#039;&#039;&lt;br /&gt;
  [INFO] Scanning for projects...&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Building Maven Stub Project (No POM) 1&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] --- maven-install-plugin:2.4:install-file (default-cli) @ standalone-pom ---&lt;br /&gt;
  [INFO] Installing C:\Linternal\Installers\install\globalyzer-maven-plugin-5.2.1.jar to C:\Users\Yourname\.m2\repository\com\lingoport\globalyzer\client\maven\globalyzer-maven-plugin\5.2.1\globalyzer-maven-plugin-5.2.1.jar&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] BUILD SUCCESS&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Total time: 0.615 s&lt;br /&gt;
  [INFO] Finished at: 2016-09-09T15:49:59-06:00&lt;br /&gt;
  [INFO] Final Memory: 7M/123M&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
== Configure the Globalyzer MVN Plugin ==&lt;br /&gt;
The &amp;lt;code&amp;gt;&amp;lt;build&amp;gt;&amp;lt;plugins&amp;gt;&amp;lt;/code&amp;gt; section of your module&#039;s pom.xml file must be configured. Here is how:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
  &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
  &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
  &amp;lt;version&amp;gt;5.2.1&amp;lt;/version&amp;gt;&lt;br /&gt;
  &amp;lt;configuration&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-required - &#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;username&amp;gt;joe@company.com&amp;lt;/username&amp;gt;&lt;br /&gt;
           &amp;lt;password&amp;gt;joespw&amp;lt;/password&amp;gt;&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;ruleSetName&amp;gt;Java Rule Set&amp;lt;/ruleSetName&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-optional -&#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings -&#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;serverUrl&amp;gt;&amp;lt;/serverUrl&amp;gt;  (default: https://www.globalyzer.com/gzserver)     &lt;br /&gt;
           &amp;lt;dataDictionaryDir&amp;gt;&amp;lt;/dataDictionaryDir&amp;gt;  ( default: userhome/.globalyzer )&lt;br /&gt;
           &amp;lt;scanTimeout&amp;gt;&amp;lt;/scanTimeout&amp;gt;  ( default: 120 seconds )&lt;br /&gt;
           &amp;lt;filterWithDictionary&amp;gt;&amp;lt;/filterWithDictionary&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;setLog4jProperties&amp;gt;&amp;lt;/setLog4jProperties&amp;gt;  ( default: true )&lt;br /&gt;
           &amp;lt;log4jPropertiesFileDir&amp;gt;&amp;lt;/log4jPropertiesFileDir&amp;gt; ( default: Globalyzer provided )    &lt;br /&gt;
           &amp;lt;enhancedScanning&amp;gt;&amp;lt;/enhancedScanning&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;clearCache&amp;gt;&amp;lt;/clearCache&amp;gt;  ( default: false )&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings -&#039;&#039;&#039;    &lt;br /&gt;
           &amp;lt;projectName&amp;gt;&amp;lt;/projectName&amp;gt;  ( default: project artifact )    &lt;br /&gt;
           &amp;lt;projectDir&amp;gt;&amp;lt;/projectDir&amp;gt;  ( default: project src/main/java )&lt;br /&gt;
           &amp;lt;ruleSetOwner&amp;gt;&amp;lt;/ruleSetOwner&amp;gt;  ( default: username )&lt;br /&gt;
           &amp;lt;scanName&amp;gt;&amp;lt;/scanName&amp;gt;  ( default: auto-generate ) &lt;br /&gt;
           &amp;lt;!-- choices:                     --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedXML        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedExcel      --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedCSV        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryHtml        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryText        --&amp;gt;&lt;br /&gt;
           &amp;lt;reportType&amp;gt;&amp;lt;/reportType&amp;gt;  ( default: ScanDetailedXML )&lt;br /&gt;
           &amp;lt;reportPath&amp;gt;&amp;lt;/reportPath&amp;gt;  ( default: target/i18n )        &lt;br /&gt;
  &amp;lt;/configuration&amp;gt;&lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Notes: &lt;br /&gt;
* The &amp;lt;b&amp;gt;&amp;lt;code&amp;gt;session level settings &amp;lt;/code&amp;gt;&amp;lt;/b&amp;gt; are set once per MVN invocation. Whichever scan / project goal is executed first, its configuration will be set for all the subsequent scans&lt;br /&gt;
* The &amp;lt;code&amp;gt;log4jPropertiesFileDir&amp;lt;/code&amp;gt; is precisely that: which log4j &amp;lt;b&amp;gt;configuration&amp;lt;/b&amp;gt; file to use is the &amp;lt;code&amp;gt;setLog4jProperties/code&amp;gt; is set to true. For for example, if that setting points to &amp;lt;code&amp;gt;/path/to/log4j.properties&amp;lt;/code&amp;gt; and in that configuration, the appender points to &amp;lt;code&amp;gt;/path/to/globalyzer/log&amp;lt;/code&amp;gt;, that&#039;s where the logs will be written out.&lt;br /&gt;
* Best would be to have the &amp;lt;b&amp;gt;exact same configuration&amp;lt;/b&amp;gt; for all Globalyzer goals to make sure one configuration is not taking over the other ones.&lt;br /&gt;
&lt;br /&gt;
== Running Globalyzer MVN Plugin From The Command Prompt / Shell ==&lt;br /&gt;
&lt;br /&gt;
Globalyzer MVN Plugin can be executed from a command prompt or shell via the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn com.lingoport.globalyzer.client.maven:globalyzer-maven-plugin:5.2.1:scan&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After MVN finishes each scan, a Globalyzer report per scan is created at the location specified in the pom.xml report path. The default location for the reports are target/i18n for each MVN module.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have configured the execution to be in the &amp;lt;code&amp;gt;validate&amp;lt;/code&amp;gt; phase, you can run the simpler command: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn validate&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(See the multi-scan example below)&lt;br /&gt;
&lt;br /&gt;
== Multi-Threaded Support ==&lt;br /&gt;
The Globalyzer MVN plugin supports multi-threaded invocation. For instance, on multi-module projects, use the -T option. For instance:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn com.lingoport.globalyzer.client.maven:globalyzer-maven-plugin:5.2.1:scan -Pglobalyzer -T1.0C&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have configured the execution to be in the &amp;lt;code&amp;gt;validate&amp;lt;/code&amp;gt; phase, you can run the simpler command: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn validate -T1.0C&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(See the multi-scan example below)&lt;br /&gt;
&lt;br /&gt;
== Multi-Scan Projects ==&lt;br /&gt;
&lt;br /&gt;
To execute more than one scan on a MVN project, use as many &amp;quot;execution&amp;quot; as you have rule sets to apply to scan the code. For instance, two scans will be performed with the following snippet, one using the &amp;lt;code&amp;gt;testjava&amp;lt;/code&amp;gt; rule set, the other using the &amp;lt;code&amp;gt;testjavascript&amp;lt;/code&amp;gt; rule set:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
        &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
        &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
        &amp;lt;version&amp;gt;5.2.1&amp;lt;/version&amp;gt;&lt;br /&gt;
        &amp;lt;executions&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
            &#039;&#039;&#039;&amp;lt;id&amp;gt;execution1&amp;lt;/id&amp;gt;&lt;br /&gt;
            &amp;lt;phase&amp;gt;validate&amp;lt;/phase&#039;&#039;&#039;&amp;gt;&lt;br /&gt;
              &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjava&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;java-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
              &amp;lt;/configuration&amp;gt;&lt;br /&gt;
               &amp;lt;goals&amp;gt;&lt;br /&gt;
                  &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;/goals&amp;gt;            &lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
          &#039;&#039;&#039;&amp;lt;id&amp;gt;execution2&amp;lt;/id&amp;gt;&lt;br /&gt;
           &amp;lt;phase&amp;gt;validate&amp;lt;/phase&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
            &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjavascript&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;javascript-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
             &amp;lt;/configuration&amp;gt;&lt;br /&gt;
             &amp;lt;goals&amp;gt;&lt;br /&gt;
               &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
             &amp;lt;/goals&amp;gt;&lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
        &amp;lt;/executions&amp;gt;                  &lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sharing pom.xml Files Between IDEs and Build Systems ==&lt;br /&gt;
&lt;br /&gt;
It is common to check in a single &amp;lt;code&amp;gt;pom.xml&amp;lt;/code&amp;gt; per code repository. However, some configuration on a developer&#039;s laptop may be different from a build system.&lt;br /&gt;
&lt;br /&gt;
A possibility to bridge the environment is to keep the most Globalyzer specific configuration only in the pom.xml file and to move the system side in the settings.xml file.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88599</id>
		<title>MVN Plugin</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=MVN_Plugin&amp;diff=88599"/>
		<updated>2016-11-16T18:34:45Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Globalyzer has a number of clients: The Workbench, the command line interface, Lite, the Ant client, and the MVN plugin. When using a MVN project, you can add code scanning with Globalyzer using our MVN plugin. &lt;br /&gt;
It is well suited for use within automation routines and Continuous Integration (CI) systems as well as within a typical developer environment, for instance within an Integrated Development Environments (IDEs).&lt;br /&gt;
&lt;br /&gt;
The Globalyzer MVN plugin generates scan reports to a directory specified the pom.xml file. Scan reports are available in a variety of formats. We ask our MVN customers to install the MVN plugin in a private MVN repository for that company. &lt;br /&gt;
&lt;br /&gt;
The steps to use the Globalyzer MVN plugin are the same as any MVN plugin:&lt;br /&gt;
* Install the plugin&lt;br /&gt;
* Configure the pom.xml&lt;br /&gt;
* Run MVN&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Install the Globalyzer MVN Plugin ==&lt;br /&gt;
&lt;br /&gt;
For those customers who require the MVN plugin, we make the globalyzer-maven-plugin-x.y.z-jar-with-dependencies.jar file available for downloadm where x.y.z is the version for the plugin, for instance 5.2.1. We ask that this jar file be installed in a private MVN repository at the customer&#039;s side.&lt;br /&gt;
You first need to get the file from a secure FTP location, which will be sent to customers who request it. Lingoport customers can request the MVN plugin by sending an email to &amp;lt;code&amp;gt;support at lingoport dot com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, a developer who wants to install the plugin in their local .m2 repository can use the following installation command, provided for a version &amp;lt;code&amp;gt;5.2.1&amp;lt;/code&amp;gt; of the MVN plugin. The same applies to other versions.t&lt;br /&gt;
&lt;br /&gt;
  C:\Users\Yourname&amp;gt;&#039;&#039;&#039;mvn install:install-file&#039;&#039;&#039; -Dfile=&amp;quot;C:\Path\to\the\plugin\jarfile\&#039;&#039;&#039;globalyzer-maven-plugin-5.2.1-jar-with-dependencies.jar&#039;&#039;&#039;&amp;quot; -DgroupId=&#039;&#039;&#039;com.lingoport.globalyzer.client.maven&#039;&#039;&#039; -DartifactId=&#039;&#039;&#039;globalyzer-maven-plugin&#039;&#039;&#039; -Dversion=&#039;&#039;&#039;5.2.1&#039;&#039;&#039; -Dpackaging=&#039;&#039;&#039;maven-plugin&#039;&#039;&#039;&lt;br /&gt;
  [INFO] Scanning for projects...&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Building Maven Stub Project (No POM) 1&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO]&lt;br /&gt;
  [INFO] --- maven-install-plugin:2.4:install-file (default-cli) @ standalone-pom ---&lt;br /&gt;
  [INFO] Installing C:\Linternal\Installers\install\globalyzer-maven-plugin-5.2.1.jar to C:\Users\Yourname\.m2\repository\com\lingoport\globalyzer\client\maven\globalyzer-maven-plugin\5.2.1\globalyzer-maven-plugin-5.2.1.jar&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] BUILD SUCCESS&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
  [INFO] Total time: 0.615 s&lt;br /&gt;
  [INFO] Finished at: 2016-09-09T15:49:59-06:00&lt;br /&gt;
  [INFO] Final Memory: 7M/123M&lt;br /&gt;
  [INFO] ------------------------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
== Configure the Globalyzer MVN Plugin ==&lt;br /&gt;
The &amp;lt;code&amp;gt;&amp;lt;build&amp;gt;&amp;lt;plugins&amp;gt;&amp;lt;/code&amp;gt; section of your module&#039;s pom.xml file must be configured. Here is how:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
  &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
  &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
  &amp;lt;version&amp;gt;5.2.1&amp;lt;/version&amp;gt;&lt;br /&gt;
  &amp;lt;configuration&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-required - &#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;username&amp;gt;joe@company.com&amp;lt;/username&amp;gt;&lt;br /&gt;
           &amp;lt;password&amp;gt;joespw&amp;lt;/password&amp;gt;&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings - &#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;ruleSetName&amp;gt;Java Rule Set&amp;lt;/ruleSetName&amp;gt;&lt;br /&gt;
      &#039;&#039;&#039;-optional -&#039;&#039;&#039;&lt;br /&gt;
           &#039;&#039;&#039;- session level settings -&#039;&#039;&#039;&lt;br /&gt;
           &amp;lt;serverUrl&amp;gt;&amp;lt;/serverUrl&amp;gt;  (default: https://www.globalyzer.com/gzserver)     &lt;br /&gt;
           &amp;lt;dataDictionaryDir&amp;gt;&amp;lt;/dataDictionaryDir&amp;gt;  ( default: userhome/.globalyzer )&lt;br /&gt;
           &amp;lt;scanTimeout&amp;gt;&amp;lt;/scanTimeout&amp;gt;  ( default: 120 seconds )&lt;br /&gt;
           &amp;lt;filterWithDictionary&amp;gt;&amp;lt;/filterWithDictionary&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;setLog4jProperties&amp;gt;&amp;lt;/setLog4jProperties&amp;gt;  ( default: true )&lt;br /&gt;
           &amp;lt;log4jPropertiesFileDir&amp;gt;&amp;lt;/log4jPropertiesFileDir&amp;gt; ( default: Globalyzer provided )    &lt;br /&gt;
           &amp;lt;enhancedScanning&amp;gt;&amp;lt;/enhancedScanning&amp;gt; ( default: true )&lt;br /&gt;
           &amp;lt;clearCache&amp;gt;&amp;lt;/clearCache&amp;gt;  ( default: false)&lt;br /&gt;
           &#039;&#039;&#039;- scan level settings -&#039;&#039;&#039;    &lt;br /&gt;
           &amp;lt;projectName&amp;gt;&amp;lt;/projectName&amp;gt;  ( default: project artifact )    &lt;br /&gt;
           &amp;lt;projectDir&amp;gt;&amp;lt;/projectDir&amp;gt;  ( default: project src/main/java )&lt;br /&gt;
           &amp;lt;ruleSetOwner&amp;gt;&amp;lt;/ruleSetOwner&amp;gt;  ( default: username )&lt;br /&gt;
           &amp;lt;scanName&amp;gt;&amp;lt;/scanName&amp;gt;  ( default: auto-generate ) &lt;br /&gt;
           &amp;lt;!-- choices:                     --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedXML        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedExcel      --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanDetailedCSV        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryHtml        --&amp;gt;&lt;br /&gt;
           &amp;lt;!--       ScanSummaryText        --&amp;gt;&lt;br /&gt;
           &amp;lt;reportType&amp;gt;&amp;lt;/reportType&amp;gt;  ( default: ScanDetailedXML )&lt;br /&gt;
           &amp;lt;reportPath&amp;gt;&amp;lt;/reportPath&amp;gt;  ( default: target/i18n )        &lt;br /&gt;
  &amp;lt;/configuration&amp;gt;&lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Notes: &lt;br /&gt;
* The &amp;lt;b&amp;gt;&amp;lt;code&amp;gt;session level settings &amp;lt;/code&amp;gt;&amp;lt;/b&amp;gt; are set once per MVN invocation. Whichever scan / project goal is executed first, its configuration will be set for all the subsequent scans&lt;br /&gt;
* The &amp;lt;code&amp;gt;log4jPropertiesFileDir&amp;lt;/code&amp;gt; is precisely that: which log4j &amp;lt;b&amp;gt;configuration&amp;lt;/b&amp;gt; file to use is the &amp;lt;code&amp;gt;setLog4jProperties/code&amp;gt; is set to true. For for example, if that setting points to &amp;lt;code&amp;gt;/path/to/log4j.properties&amp;lt;/code&amp;gt; and in that configuration, the appender points to &amp;lt;code&amp;gt;/path/to/globalyzer/log&amp;lt;/code&amp;gt;, that&#039;s where the logs will be written out.&lt;br /&gt;
* Best would be to have the &amp;lt;b&amp;gt;exact same configuration&amp;lt;/b&amp;gt; for all Globalyzer goals to make sure one configuration is not taking over the other ones.&lt;br /&gt;
&lt;br /&gt;
== Running Globalyzer MVN Plugin From The Command Prompt / Shell ==&lt;br /&gt;
&lt;br /&gt;
Globalyzer MVN Plugin can be executed from a command prompt or shell via the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn com.lingoport.globalyzer.client.maven:globalyzer-maven-plugin:5.2.1:scan&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After MVN finishes each scan, a Globalyzer report per scan is created at the location specified in the pom.xml report path. The default location for the reports are target/i18n for each MVN module.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have configured the execution to be in the &amp;lt;code&amp;gt;validate&amp;lt;/code&amp;gt; phase, you can run the simpler command: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn validate&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(See the multi-scan example below)&lt;br /&gt;
&lt;br /&gt;
== Multi-Threaded Support ==&lt;br /&gt;
The Globalyzer MVN plugin supports multi-threaded invocation. For instance, on multi-module projects, use the -T option. For instance:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn com.lingoport.globalyzer.client.maven:globalyzer-maven-plugin:5.2.1:scan -Pglobalyzer -T1.0C&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have configured the execution to be in the &amp;lt;code&amp;gt;validate&amp;lt;/code&amp;gt; phase, you can run the simpler command: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mvn validate -T1.0C&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(See the multi-scan example below)&lt;br /&gt;
&lt;br /&gt;
== Multi-Scan Projects ==&lt;br /&gt;
&lt;br /&gt;
To execute more than one scan on a MVN project, use as many &amp;quot;execution&amp;quot; as you have rule sets to apply to scan the code. For instance, two scans will be performed with the following snippet, one using the &amp;lt;code&amp;gt;testjava&amp;lt;/code&amp;gt; rule set, the other using the &amp;lt;code&amp;gt;testjavascript&amp;lt;/code&amp;gt; rule set:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;plugin&amp;gt;&lt;br /&gt;
        &amp;lt;groupId&amp;gt;com.lingoport.globalyzer.client.maven&amp;lt;/groupId&amp;gt;&lt;br /&gt;
        &amp;lt;artifactId&amp;gt;globalyzer-maven-plugin&amp;lt;/artifactId&amp;gt;&lt;br /&gt;
        &amp;lt;version&amp;gt;5.2.1&amp;lt;/version&amp;gt;&lt;br /&gt;
        &amp;lt;executions&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
            &#039;&#039;&#039;&amp;lt;id&amp;gt;execution1&amp;lt;/id&amp;gt;&lt;br /&gt;
            &amp;lt;phase&amp;gt;validate&amp;lt;/phase&#039;&#039;&#039;&amp;gt;&lt;br /&gt;
              &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjava&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;java-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
              &amp;lt;/configuration&amp;gt;&lt;br /&gt;
               &amp;lt;goals&amp;gt;&lt;br /&gt;
                  &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;/goals&amp;gt;            &lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
          &amp;lt;execution&amp;gt;&lt;br /&gt;
          &#039;&#039;&#039;&amp;lt;id&amp;gt;execution2&amp;lt;/id&amp;gt;&lt;br /&gt;
           &amp;lt;phase&amp;gt;validate&amp;lt;/phase&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
            &amp;lt;configuration&amp;gt;&lt;br /&gt;
              &amp;lt;username&amp;gt;bob@yourcompany.com&amp;lt;/username&amp;gt;&lt;br /&gt;
              &amp;lt;password&amp;gt;bobpassword&amp;lt;/password&amp;gt;&lt;br /&gt;
              &#039;&#039;&#039;&amp;lt;ruleSetName&amp;gt;testjavascript&amp;lt;/ruleSetName&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
              &amp;lt;scanName&amp;gt;javascript-report&amp;lt;/scanName&amp;gt;&lt;br /&gt;
             &amp;lt;/configuration&amp;gt;&lt;br /&gt;
             &amp;lt;goals&amp;gt;&lt;br /&gt;
               &#039;&#039;&#039;&amp;lt;goal&amp;gt;scan&amp;lt;/goal&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
             &amp;lt;/goals&amp;gt;&lt;br /&gt;
          &amp;lt;/execution&amp;gt;&lt;br /&gt;
        &amp;lt;/executions&amp;gt;                  &lt;br /&gt;
  &amp;lt;/plugin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sharing pom.xml Files Between IDEs and Build Systems ==&lt;br /&gt;
&lt;br /&gt;
It is common to check in a single &amp;lt;code&amp;gt;pom.xml&amp;lt;/code&amp;gt; per code repository. However, some configuration on a developer&#039;s laptop may be different from a build system.&lt;br /&gt;
&lt;br /&gt;
A possibility to bridge the environment is to keep the most Globalyzer specific configuration only in the pom.xml file and to move the system side in the settings.xml file.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87146</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87146"/>
		<updated>2015-06-16T20:27:49Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Next Steps */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Lingoport Resource Manager Overview ==&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
== Installing LRM ==&lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Headless Installation====&lt;br /&gt;
To install LRM without a windowing system, use an xml installation file. The xml installation files can be generated from a first installation or an update using a windowing system on the last page of the installer. That file can be modified to fit other installations. To run a headless installation, from the command line, cd to the directory with the installer and type:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar headlessinstaller.xml&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding or Updating the License===&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Group Name===&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your LRM Project and start managing your application&#039;s resource files. This involves configuring Jenkins with tabs, the jobs, the users, and the authorizations. See [[LRM Jenkins Configure System]]. &lt;br /&gt;
&lt;br /&gt;
LRM works with the Lingoport Dashboard. Make sure the Dashboard is configured to point to the current LRM installation. You may want to update the Dashboard installation to do so.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Important MySQL Configuration Note&amp;lt;/b&amp;gt;&lt;br /&gt;
If you see the following error when running LRM commands: &amp;lt;b&amp;gt;Packet for query is too large&amp;lt;/b&amp;gt;&lt;br /&gt;
you will need to increase the max_allowed_packet variable of your MySQL database server to either 16 or 32 megabytes in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Resource Manager, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87145</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87145"/>
		<updated>2015-06-16T20:24:09Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Next Steps */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Lingoport Resource Manager Overview ==&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
== Installing LRM ==&lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Headless Installation====&lt;br /&gt;
To install LRM without a windowing system, use an xml installation file. The xml installation files can be generated from a first installation or an update using a windowing system on the last page of the installer. That file can be modified to fit other installations. To run a headless installation, from the command line, cd to the directory with the installer and type:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar headlessinstaller.xml&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding or Updating the License===&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Group Name===&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your LRM Project and start managing your application&#039;s resource files. This involves congfiguring Jenkins with tabs, the jobs, the users, and the authorizations. For instructions on these and other capabilities, see the Lingoport LRM Wiki.&lt;br /&gt;
&lt;br /&gt;
LRM works with the Lingoport Dashboard. Make sure the Dashboard is configured to point to the current LRM installation. You may want to update the Dashboard installation to do so.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Important MySQL Configuration Note&amp;lt;/b&amp;gt;&lt;br /&gt;
If you see the following error when running LRM commands: &amp;lt;b&amp;gt;Packet for query is too large&amp;lt;/b&amp;gt;&lt;br /&gt;
you will need to increase the max_allowed_packet variable of your MySQL database server to either 16 or 32 megabytes in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Resource Manager, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87144</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87144"/>
		<updated>2015-06-16T20:21:06Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Lingoport Resource Manager Overview ==&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
== Installing LRM ==&lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Headless Installation====&lt;br /&gt;
To install LRM without a windowing system, use an xml installation file. The xml installation files can be generated from a first installation or an update using a windowing system on the last page of the installer. That file can be modified to fit other installations. To run a headless installation, from the command line, cd to the directory with the installer and type:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar headlessinstaller.xml&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding or Updating the License===&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Group Name===&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your LRM Project and start managing your application&#039;s resource files. For instructions on these and other capabilities, see the Lingoport LRM Wiki).&lt;br /&gt;
&lt;br /&gt;
LRM works with the Lingoport Dashboard. Make sure the Dashboard is configured to point to the current LRM installation. You may want to update the Dashboard installation to do so.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Important MySQL Configuration Note&amp;lt;/b&amp;gt;&lt;br /&gt;
If you see the following error when running LRM commands: &amp;lt;b&amp;gt;Packet for query is too large&amp;lt;/b&amp;gt;&lt;br /&gt;
you will need to increase the max_allowed_packet variable of your MySQL database server to either 16 or 32 megabytesin the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Resource Manager, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87143</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87143"/>
		<updated>2015-06-16T20:15:25Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Resource Manager Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== LRM Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Headless Installation====&lt;br /&gt;
To install LRM without a windowing system, use an xml installation file. The xml installation files can be generated from a first installation or an update using a windowing system on the last page of the installer. That file can be modified to fit other installations. To run a headless installation, from the command line, cd to the directory with the installer and type:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar headlessinstaller.xml&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding or Updating the License===&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Group Name===&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your LRM Project and start managing your application&#039;s resource files. For instructions on these and other capabilities, see the Lingoport LRM Wiki).&lt;br /&gt;
&lt;br /&gt;
LRM works with the Lingoport Dashboard. Make sure the Dashboard is configured to point to the current LRM installation. You may want to update the Dashboard installation to do so.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Important MySQL Configuration Note&amp;lt;/b&amp;gt;&lt;br /&gt;
If you see the following error when running LRM commands: &amp;lt;b&amp;gt;Packet for query is too large&amp;lt;/b&amp;gt;&lt;br /&gt;
you will need to increase the max_allowed_packet variable of your MySQL database server to either 16 or 32 megabytesin the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Resource Manager, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87142</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87142"/>
		<updated>2015-06-16T20:13:49Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Headless Installation====&lt;br /&gt;
To install LRM without a windowing system, use an xml installation file. The xml installation files can be generated from a first installation or an update using a windowing system on the last page of the installer. That file can be modified to fit other installations. To run a headless installation, from the command line, cd to the directory with the installer and type:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar headlessinstaller.xml&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding or Updating the License===&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Group Name===&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your LRM Project and start managing your application&#039;s resource files. For instructions on these and other capabilities, see the Lingoport LRM Wiki).&lt;br /&gt;
&lt;br /&gt;
LRM works with the Lingoport Dashboard. Make sure the Dashboard is configured to point to the current LRM installation. You may want to update the Dashboard installation to do so.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Important MySQL Configuration Note&amp;lt;/b&amp;gt;&lt;br /&gt;
If you see the following error when running LRM commands: &amp;lt;b&amp;gt;Packet for query is too large&amp;lt;/b&amp;gt;&lt;br /&gt;
you will need to increase the max_allowed_packet variable of your MySQL database server to either 16 or 32 megabytesin the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Resource Manager, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87141</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87141"/>
		<updated>2015-06-16T20:11:13Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Headless Installation====&lt;br /&gt;
To install LRM without a windowing system, use an xml installation file. The xml installation files can be generated from a first installation or an update using a windowing system on the last page of the installer. That file can be modified to fit other installations. To run a headless installation, from the command line, cd to the directory with the installer and type:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar headlessinstaller.xml&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding or Updating the License===&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Group Name===&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your LRM Project and start managing your application&#039;s resource files. For instructions on these and other capabilities, see the Lingoport LRM Wiki).&lt;br /&gt;
&lt;br /&gt;
LRM works with the Lingoport Dashboard. Make sure the Dashboard is configured to point to the current LRM installation. You may want to update the Dashboard installation to do so.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Important MySQL Configuration Note&amp;lt;/b&amp;gt;&lt;br /&gt;
If you see the following error when running LRM commands: Packet for query is too large&lt;br /&gt;
you will need to increase the max_allowed_packet variable of your MySQL database server to either 16 or 32 megabytesin the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Resource Manager, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87140</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87140"/>
		<updated>2015-06-16T20:05:39Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Resource Manager Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Headless Installation====&lt;br /&gt;
To install LRM without a windowing system, use an xml installation file. The xml installation files can be generated from a first installation or an update using a windowing system on the last page of the installer. That file can be modified to fit other installations. To run a headless installation, from the command line, cd to the directory with the installer and type:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar headlessinstaller.xml&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding or Updating the License===&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Group Name===&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87139</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87139"/>
		<updated>2015-06-16T20:03:21Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Resource Manager Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Adding or Updating the License====&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Group Name====&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;br /&gt;
&lt;br /&gt;
====Headless Installation====&lt;br /&gt;
To install LRM without a windowing system, use an xml installation file. The xml installation files can be generated from a first installation or an update using a windowing system on the last page of the installer. That file can be modified to fit other installations. To run a headless installation, from the command line, cd to the directory with the installer and type:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar headlessinstaller.xml&amp;lt;/code&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87138</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87138"/>
		<updated>2015-06-16T19:58:10Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Adding or Updating the License====&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Group Name====&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87137</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87137"/>
		<updated>2015-06-16T19:52:11Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* LRM Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation ===&lt;br /&gt;
Run the installer, as the user Jenkins who runs the jobs, by either:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;double clicking on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;running “java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar“ at the command prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
The Lingoport Resource Manager will then prompt you for license information and database settings to create the database tables in MySQL. &lt;br /&gt;
&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, run the LRM Server installer.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Adding or Updating the License====&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Group Name====&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87136</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87136"/>
		<updated>2015-06-16T19:50:52Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== LRM Installation ===&lt;br /&gt;
Run the installer, as the user Jenkins who runs the jobs, by either:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;double clicking on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;running “java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar“ at the command prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
The Lingoport Resource Manager will then prompt you for license information and database settings to create the database tables in MySQL. &lt;br /&gt;
&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, run the LRM Server installer.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Adding or Updating the License====&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Group Name====&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87135</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87135"/>
		<updated>2015-06-16T19:49:05Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Resource Manager Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
===Overview===&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [http://wiki.lingoport.com/index.php5?title=Lingoport_Suite_Installation Lingoport Suite Installation], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== LRM Installation ===&lt;br /&gt;
Run the installer, as the user Jenkins who runs the jobs, by either:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;double clicking on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;running “java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar“ at the command prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
The Lingoport Resource Manager will then prompt you for license information and database settings to create the database tables in MySQL. &lt;br /&gt;
&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, run the LRM Server installer.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Adding or Updating the License====&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Group Name====&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87134</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87134"/>
		<updated>2015-06-16T19:47:40Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the [http://wiki.lingoport.com/index.php5?title=Lingoport_Suite_Installation Lingoport Suite Installation], which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== LRM Installation ===&lt;br /&gt;
Run the installer, as the user Jenkins who runs the jobs, by either:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;double clicking on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;running “java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar“ at the command prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
The Lingoport Resource Manager will then prompt you for license information and database settings to create the database tables in MySQL. &lt;br /&gt;
&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, run the LRM Server installer.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Adding or Updating the License====&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Group Name====&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87133</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87133"/>
		<updated>2015-06-16T19:44:08Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation wiki, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== LRM Installation ===&lt;br /&gt;
Run the installer, as the user Jenkins who runs the jobs, by either:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;double clicking on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;running “java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar“ at the command prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
The Lingoport Resource Manager will then prompt you for license information and database settings to create the database tables in MySQL. &lt;br /&gt;
&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, run the LRM Server installer.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Adding or Updating the License====&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Group Name====&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87132</id>
		<title>Localyzer Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Localyzer_Installation&amp;diff=87132"/>
		<updated>2015-06-16T19:41:22Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Resource Manager Installation ==&lt;br /&gt;
The Lingoport Resource Manager System is composed of three items (See the diagram at [[Components Diagram]]):&lt;br /&gt;
# &#039;&#039;&#039;Lingoport Resource Manager&#039;&#039;&#039;: The Server keeps track of all the actions and the expected results. The server is best located on one central system. This section describes the installation of LRM. &lt;br /&gt;
# &#039;&#039;&#039;Jenkins&#039;&#039;&#039;: Jenkins orchestrates the execution of the commands, such as verifying files to be sent for translation via a light Java application. Jenkins needs to communicate with the Lingoport Resource Manager server and is best co-located with LRM. The Jenkins setup is the subject of another guide.&lt;br /&gt;
# &#039;&#039;&#039;Dashboard&#039;&#039;&#039;: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Dashboard typically needs to have access to the &amp;lt;code&amp;gt;lrm-cli.jar&amp;lt;/code&amp;gt; files in order to generate the xml report files and use those xml to push the files over to the Dashboard.  &lt;br /&gt;
&lt;br /&gt;
===Prerequisites ===&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Supported OS: &amp;lt;b&amp;gt;Linux&amp;lt;/b&amp;gt;&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
&amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;&amp;lt;b&amp;gt;Jenkins&amp;lt;/b&amp;gt;, the latest version. See the [https://jenkins-ci.org/ Jenkins download] site to get the latest version.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Received the &amp;lt;b&amp;gt;Licensing information&amp;lt;/b&amp;gt; from Lingoport. When your company purchased LRM you should have been sent an email containing the licensing information. The licensing information will include the following:&lt;br /&gt;
* group name&lt;br /&gt;
* number of licenses in the license&lt;br /&gt;
* expiration date for the license&lt;br /&gt;
* license key.  This is a 10-digit number generated by Lingoport.&lt;br /&gt;
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact &amp;lt;code&amp;gt;support@lingoport.com&amp;lt;/code&amp;gt;. Please keep it handy while you perform the install.&amp;lt;/LI&amp;gt; You may many licenses, one per group. This must have been specified during the sales process.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installer jar file: you must have the &amp;lt;b&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/b&amp;gt; file.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is &#039;MST&#039; whereas &#039;America/Denver&#039; is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. &lt;br /&gt;
&amp;lt;UL&amp;gt; &lt;br /&gt;
&amp;lt;LI&amp;gt;For Windows, you should be able to type &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For Linux, you could for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;For MacOS, you may for instance type &amp;lt;code&amp;gt;mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p&amp;lt;/code&amp;gt; from the command line and then &amp;lt;code&amp;gt;SET GLOBAL time_zone = &#039;America/Denver’&amp;lt;/code&amp;gt; at the MySQL prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== LRM Installation ===&lt;br /&gt;
Run the installer, as the user Jenkins who runs the jobs, by either:&lt;br /&gt;
&amp;lt;UL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;double clicking on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;running “java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar“ at the command prompt.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/UL&amp;gt;&lt;br /&gt;
The Lingoport Resource Manager will then prompt you for license information and database settings to create the database tables in MySQL. &lt;br /&gt;
&lt;br /&gt;
Once you have retrieved your licensing information and ensured that all requirements are met, run the LRM Server installer.&lt;br /&gt;
&lt;br /&gt;
====Installing for the First Time====&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installer will prompt you for license information and database settings to create the MySQL LRM database.&lt;br /&gt;
The installer will also prompt you for the LRM and the L10nStreamlining directory location.  These will default to &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/LRM&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;lt;home&amp;gt;/Lingoport_Data/L10nStreamlining&amp;lt;/code&amp;gt;.  When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first project is generated.&lt;br /&gt;
&lt;br /&gt;
====Updating Your Existing Installation====&lt;br /&gt;
If you are upgrading your LRM Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Resource_Manager_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the Type of Installation page, be sure to select &amp;lt;b&amp;gt;Update Server&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====Adding or Updating the License====&lt;br /&gt;
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. &lt;br /&gt;
To update or add a new license to your current installation, open a command prompt and type:&lt;br /&gt;
* To update an existing license for a group&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar &amp;lt;LRM_INSTALLATION_PATH&amp;gt;lrm-cli.jar --update-license --group-name &amp;lt;group&amp;gt; --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To add a new license for a group:&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --create-group &amp;lt;groupname&amp;gt;  --number-of-licenses &amp;lt;number&amp;gt; --date &amp;lt;YYYY-MM-DD&amp;gt; --license-key &amp;lt;key&amp;gt; &amp;lt;/code&amp;gt;&lt;br /&gt;
* To verify that the new license has been installed with the correct information&lt;br /&gt;
&amp;lt;code&amp;gt;java -jar  &amp;lt;LRM_INSTALLATION_PATH&amp;gt;/lrm-cli.jar --list-groups&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Group Name====&lt;br /&gt;
A group name &amp;lt;b&amp;gt;must conform&amp;lt;/b&amp;gt; to the following specification:&lt;br /&gt;
A set of alphanumeric characters without the following special characters:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt; (less than)&lt;br /&gt;
* &amp;gt; (greater than)&lt;br /&gt;
* : (colon)&lt;br /&gt;
* &amp;quot; (double quote)&lt;br /&gt;
* / (forward slash)&lt;br /&gt;
* \ (backslash)&lt;br /&gt;
* | (vertical bar or pipe)&lt;br /&gt;
* ? (question mark)&lt;br /&gt;
* * (asterisk)&lt;br /&gt;
* (space)&lt;br /&gt;
* % (percentage)&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Installation&amp;diff=87131</id>
		<title>Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Installation&amp;diff=87131"/>
		<updated>2015-06-16T17:50:14Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: Lcameron moved page Installation to Dashboard Installation&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Dashboard Installation]]&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87130</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87130"/>
		<updated>2015-06-16T17:50:14Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: Lcameron moved page Installation to Dashboard Installation&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is &amp;lt;i&amp;gt;installed and running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Server.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Linux (required for LRM), Windows, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Server installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87129</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87129"/>
		<updated>2015-06-16T17:39:52Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is &amp;lt;i&amp;gt;installed and running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Server.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Linux (required for LRM), Windows, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Server installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87128</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87128"/>
		<updated>2015-06-16T17:38:22Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Dashbord Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is &amp;lt;i&amp;gt;installed and running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Server.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Linux (required for LRM), Windows, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Server installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87127</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87127"/>
		<updated>2015-06-16T17:08:51Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* The Build Server */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration for a Continuous Globalization System, where both internationalization and localization progress is tracked, managed and displayed in an automated and reliable process.&lt;br /&gt;
&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build Server==&lt;br /&gt;
The Build Server is where you install many of the Lingoport Suite applications. It is the heart of the Continuous Globalization system, since this is where the automation occurs that keeps globalization status up-to-date. We call it the Build Server to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer Machine ==&lt;br /&gt;
The individual Developer machine is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87126</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87126"/>
		<updated>2015-06-16T17:08:02Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* The Build Server */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration for a Continuous Globalization System, where both internationalization and localization progress is tracked, managed and displayed in an automated and reliable process.&lt;br /&gt;
&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build Server==&lt;br /&gt;
The Build Server is where you install many of the Lingoport Suite applications, and is the heart of the Continuous Globalization system, since this is where the automation occurs that keeps globalization status up-to-date. We call it the Build Server to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer Machine ==&lt;br /&gt;
The individual Developer machine is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87125</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87125"/>
		<updated>2015-06-16T17:04:47Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* The Developer Machine */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration for a Continuous Globalization System, where both internationalization and localization progress is tracked, managed and displayed in an automated and reliable process.&lt;br /&gt;
&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build Server==&lt;br /&gt;
The Build Server is where you install many of the Lingoport Suite applications and is the heart of the Continuous Globalization system. We call it the Build Server to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer Machine ==&lt;br /&gt;
The individual Developer machine is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87124</id>
		<title>File:Lingoportsuite config.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87124"/>
		<updated>2015-06-16T17:03:29Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: Lcameron uploaded a new version of &amp;amp;quot;File:Lingoportsuite config.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87123</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87123"/>
		<updated>2015-06-16T17:01:08Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* The Build Server */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration for a Continuous Globalization System, where both internationalization and localization progress is tracked, managed and displayed in an automated and reliable process.&lt;br /&gt;
&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build Server==&lt;br /&gt;
The Build Server is where you install many of the Lingoport Suite applications and is the heart of the Continuous Globalization system. We call it the Build Server to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer System ==&lt;br /&gt;
The individual Developer system is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87122</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87122"/>
		<updated>2015-06-16T17:00:37Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* The Build System */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration for a Continuous Globalization System, where both internationalization and localization progress is tracked, managed and displayed in an automated and reliable process.&lt;br /&gt;
&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build Server==&lt;br /&gt;
The Build Server is where you install many of the Lingoport Suite applications and is the heart of the Continuous Globalization system. We call it the Build System to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer System ==&lt;br /&gt;
The individual Developer system is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87121</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87121"/>
		<updated>2015-06-16T16:58:55Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* The Globalyzer Server System */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration for a Continuous Globalization System, where both internationalization and localization progress is tracked, managed and displayed in an automated and reliable process.&lt;br /&gt;
&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build System==&lt;br /&gt;
The Build System is where you install many of the Lingoport Suite applications and is the heart of the Continuous Globalization system. We call it the Build System to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer System ==&lt;br /&gt;
The individual Developer system is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87120</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87120"/>
		<updated>2015-06-16T16:58:00Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Systems Configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration for a Continuous Globalization System, where both internationalization and localization progress is tracked, managed and displayed in an automated and reliable process.&lt;br /&gt;
&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server System==&lt;br /&gt;
The Globalyzer Server System is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build System==&lt;br /&gt;
The Build System is where you install many of the Lingoport Suite applications and is the heart of the Continuous Globalization system. We call it the Build System to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer System ==&lt;br /&gt;
The individual Developer system is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87119</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87119"/>
		<updated>2015-06-16T16:47:32Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Systems Configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration for a Continuous Globalization System.&lt;br /&gt;
&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server System==&lt;br /&gt;
The Globalyzer Server System is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build System==&lt;br /&gt;
The Build System is where you install many of the Lingoport Suite applications and is the heart of the Continuous Globalization system. We call it the Build System to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer System ==&lt;br /&gt;
The individual Developer system is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87118</id>
		<title>Lingoport Suite Installation - Obsolete</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Lingoport_Suite_Installation_-_Obsolete&amp;diff=87118"/>
		<updated>2015-06-16T16:46:08Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* The Build System or Continuous G11n System */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Lingoport Suite Overview=&lt;br /&gt;
The Lingoport Suite is comprised of three applications:&lt;br /&gt;
* &#039;&#039;&#039;Globalyzer&#039;&#039;&#039;, to detect and fix internationalization issues in your source code.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Resource Manager (LRM)&#039;&#039;&#039;, to track and manage the localization of your translatable resource files.&lt;br /&gt;
* &#039;&#039;&#039;Lingoport Dashboard&#039;&#039;&#039;, to 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.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Hardware &amp;amp; Software Requirements=&lt;br /&gt;
The following sections describe the hardware and software requirements for each of the Lingoport Suite applications.&lt;br /&gt;
==Globalyzer Server==&lt;br /&gt;
The Globalyzer Server is where all your Globalyzer account information and rule sets are stored. Lingoport&#039;s hosted server is at [https://www.globalyzer.com] &lt;br /&gt;
&lt;br /&gt;
The following table lists the system specifications for installing the Globalyzer Server on a dedicated Windows or Linux machine. The disk size assumes that the database is also installed on the machine; it could be less if the database is on a separate server. If the server machine is running more than the Globalyzer Server, we recommend increasing CPU and memory.&lt;br /&gt;
&lt;br /&gt;
===Hardware requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended&lt;br /&gt;
! Up to&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 || 4&lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
| 8 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
| 500 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Recommended&lt;br /&gt;
|-&lt;br /&gt;
! Operating System&lt;br /&gt;
| Linux or Windows, 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
| MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Server&lt;br /&gt;
| Tomcat  6.x&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
| Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Database ==&lt;br /&gt;
The LRM MySQL Database is where all your resource file tracking and management status is stored. When the LRM Server is installed, you will enter the connection to the LRM database.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Lingoport Resource Manager Server ==&lt;br /&gt;
The LRM Server provides a command line interface, run via Jenkins jobs, that you use to configure, manage and track the localization of your application&#039;s resource files. LRM must be installed on machines that will also have the Dashboard Client installed, such as a build machine, where the source code is available. The LRM MySQL Database is not required to be on this machine.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the LRM Server.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 4 GB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Software requirements===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lingoport Dashboard Server ==&lt;br /&gt;
The Dashboard Server displays the results of Globalyzer scans and/or the Resource Manager status in a web browser. The hardware requirements assume that the MySQL database is on the Dashboard Server machine; if the database is on a different server, then the disk size can be less, but you will still need the MySQL Client installed on the Dashboard Server machine.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| &amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Windows: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Linux: 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Mac OS X: Power PC, 64 bit, 32 bit&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! MySQL Database&lt;br /&gt;
|MySQL 5.1 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Lingoport Dashboard Client==&lt;br /&gt;
The Dashboard Client analyzes source code with Globalyzer and/or with LRM and displays the information on the Dashboard server. The client must be installed on a machine where the source code resides and both the Globalyzer Client and the LRM Server have been installed. Although you can run the Dashboard scripts directly, using an application such as Jenkins, allows you to have a continuous integration system that will update your application&#039;s source code, execute Dashboard scripts to call Globalyzer and LRM to generate internationalization and localization status, and then push those results to the Dashboard Server. This entire process can be set up and then scheduled to run nightly using Jenkins&#039; web-based interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: A Linux OS system is required by the Dashboard Client to run LRM&#039;s automated scripts.&lt;br /&gt;
&lt;br /&gt;
=== Hardware Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Element&lt;br /&gt;
! Recommended Minimum&lt;br /&gt;
|-&lt;br /&gt;
! CPU&lt;br /&gt;
| 2 &lt;br /&gt;
|-&lt;br /&gt;
! Memory&lt;br /&gt;
| 500 MB&lt;br /&gt;
|-&lt;br /&gt;
! Disk&lt;br /&gt;
| 160 GB&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Software Requirements ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width=50%&amp;quot;&lt;br /&gt;
! Software&lt;br /&gt;
! Supported&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! Operating Systems&lt;br /&gt;
| Linux: 64 bit (or Windows, Mac if no LRM)&lt;br /&gt;
|-&lt;br /&gt;
! Java Standard Edition&lt;br /&gt;
| Java SDK 1.7 or later&lt;br /&gt;
|-&lt;br /&gt;
! Web Browser&lt;br /&gt;
|Any more recent browser&lt;br /&gt;
|-&lt;br /&gt;
! Jenkins&lt;br /&gt;
|1.6 or greater&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Systems Configuration=&lt;br /&gt;
The Lingoport Suite can be configured in a variety of ways. The following describes our recommended configuration.&lt;br /&gt;
[[File:lingoportsuite_config.png]]&lt;br /&gt;
&lt;br /&gt;
==The Globalyzer Server System==&lt;br /&gt;
The Globalyzer Server System is where your Account and Rule Set information are stored. Lingoport provides the Globalyzer Server at [www.globalyzer.com]. However, depending on licensing, you may install the server on your own system. Follow the detailed installation instructions that come with your Globalyzer Server installation files.&lt;br /&gt;
&lt;br /&gt;
==The Dashboard Server System==&lt;br /&gt;
The Dashboard Server System is where you view internationalization and localization status for your projects in a sonar-powered dashboard. It contains the MySQL databases for both Dashboard and LRM and the scripts to start the Dashboard Server. In this configuration, we have separated the client applications from the server applications, though they are often combined on a single machine.&lt;br /&gt;
* Install MySQL 5.1 or greater.&lt;br /&gt;
* Install Java 7 JRE or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt;. See the DashboardInstallationGuide document for details.&lt;br /&gt;
* The LRM database will be created and initialized when you install the LRM Server on the Build System (see next).&lt;br /&gt;
&lt;br /&gt;
==The Build System==&lt;br /&gt;
The Build System is where you install many of the Lingoport Suite applications and is the heart of the Continuous Globalization system. We call it the Build System to distinguish it from a Developer machine and to imply that it could have source code for multiple applications, but it does not need to actually build executables. It just needs to run the Dashboard, Globalyzer, and LRM scripts on the latest source code; the Dashboard scripts will call the Globalyzer Client to scan the source code for internationalization issues, LRM to check for localization status, and then it will push those results to the Dashboard Server. &lt;br /&gt;
&lt;br /&gt;
Starting with LRM 2.0, Jenkins, a continuous integration tool, is required. In addition to support for nightly scanning and scheduled Dashboard updates, Jenkins scripts are added as part of its LRM configuration that result in round-trip automation in the management of resource files.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* Install Jenkins 1.5 or greater.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;LRM Server&amp;lt;/b&amp;gt; - as part of installation, will enter connection to the LRM Server database. See the LRMInstallationGuide document for details.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Dashboard Client&amp;lt;/b&amp;gt;. See the Dashboard Installation section for details.&lt;br /&gt;
&lt;br /&gt;
== The Developer System ==&lt;br /&gt;
The individual Developer system is where you install the Globalyzer Workbench so that internationalization and localization issues can be addressed.&lt;br /&gt;
* Install Java 7 JDK or greater. The JDK is required by Globalyzer.&lt;br /&gt;
* The Globalyzer Client requires either MySQL or HSQLDB. If you choose MySQL, you will need to install MySQL 5.1 or greater.&lt;br /&gt;
* Install the &amp;lt;b&amp;gt;Globalyzer Client&amp;lt;/b&amp;gt;.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installation and Upgrade Order =&lt;br /&gt;
&lt;br /&gt;
When installing or upgrading the Lingoport Suite, be sure to follow this order:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Server: Follow the instructions in the Globalyzer_Server_Setup&amp;amp;Admin_&amp;lt;version&amp;gt;.doc file included with the Globalyzer Server installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Globalyzer Client: Log in to the Globalyzer Server and click on the Client download link at the bottom of the page.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the LRM Server: Follow the instructions in the LRM Installation Guide HTML file included with your LRM installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Server: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Install/Upgrade the Dashboard Client: Follow the instructions in the Dashboard Installation Guide HTML file included with your Dashboard installation files.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Suite, please contact &amp;lt;i&amp;gt;support@lingoport.com&amp;lt;/i&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87117</id>
		<title>File:Lingoportsuite config.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87117"/>
		<updated>2015-06-16T16:42:20Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: Lcameron uploaded a new version of &amp;amp;quot;File:Lingoportsuite config.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87116</id>
		<title>File:Lingoportsuite config.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87116"/>
		<updated>2015-06-16T15:36:34Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: Lcameron uploaded a new version of &amp;amp;quot;File:Lingoportsuite config.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87115</id>
		<title>File:Lingoportsuite config.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87115"/>
		<updated>2015-06-16T15:36:31Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: Lcameron uploaded a new version of &amp;amp;quot;File:Lingoportsuite config.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87114</id>
		<title>File:Lingoportsuite config.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=File:Lingoportsuite_config.png&amp;diff=87114"/>
		<updated>2015-06-16T15:32:19Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: Lcameron uploaded a new version of &amp;amp;quot;File:Lingoportsuite config.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87113</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87113"/>
		<updated>2015-06-11T23:03:19Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is &amp;lt;i&amp;gt;installed and running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Server.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Linux (required for LRM), Windows, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Server installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87112</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87112"/>
		<updated>2015-06-11T23:01:46Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Updating Your Existing Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is &amp;lt;i&amp;gt;installed and running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Server.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Server installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87111</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87111"/>
		<updated>2015-06-11T23:01:03Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Installing the Dashboard Client */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is &amp;lt;i&amp;gt;installed and running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Server.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Server installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87110</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87110"/>
		<updated>2015-06-11T22:59:26Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is &amp;lt;i&amp;gt;installed and running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87109</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87109"/>
		<updated>2015-06-11T22:58:47Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Installing the Dashboard Client */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is &amp;lt;i&amp;gt;installed and running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87108</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87108"/>
		<updated>2015-06-11T22:55:45Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  &lt;br /&gt;
&lt;br /&gt;
* If the database server is not the same machine as the Dashboard Server, then you will need to install the &amp;lt;b&amp;gt;MySQL 5.x Client&amp;lt;/b&amp;gt; (only need Client) on the Dashboard Server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is installed and &amp;lt;i&amp;gt;running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87107</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87107"/>
		<updated>2015-06-11T22:53:28Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on the Dashboard Server or a separate database server.  If the database server is not the same machine as the Dashboard server, then you will need to install the MySQL 5.x Client (only need Client) on the Dashboard server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is installed and &amp;lt;i&amp;gt;running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87106</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87106"/>
		<updated>2015-06-11T22:48:25Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is installed and &amp;lt;i&amp;gt;running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87105</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87105"/>
		<updated>2015-06-11T22:47:19Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater JRE&amp;lt;/b&amp;gt; on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is installed and &amp;lt;i&amp;gt;running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87104</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87104"/>
		<updated>2015-06-11T22:45:34Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is installed and &amp;lt;i&amp;gt;running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87103</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87103"/>
		<updated>2015-06-11T22:43:57Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Lingoport Dashboard Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is installed and &amp;lt;i&amp;gt;running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
	<entry>
		<id>https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87102</id>
		<title>Dashboard Installation 5.6.x</title>
		<link rel="alternate" type="text/html" href="https://wiki.lingoport.com/index.php?title=Dashboard_Installation_5.6.x&amp;diff=87102"/>
		<updated>2015-06-11T22:43:33Z</updated>

		<summary type="html">&lt;p&gt;Lcameron: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Lingoport Dashboard Overview=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The Lingoport Dashboard is composed of two components:&lt;br /&gt;
*A &amp;lt;b&amp;gt;Server&amp;lt;/b&amp;gt; displays the results of Globalyzer scans and/or the Resource Manager status in a web browser.&lt;br /&gt;
*A &amp;lt;b&amp;gt;Client&amp;lt;/b&amp;gt; analyzes source code with Globalyzer and/or with LRM and uploads the information to the Dashboard Server for display.&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Server =&lt;br /&gt;
The &amp;lt;b&amp;gt;Dashboard Server&amp;lt;/b&amp;gt; installation creates a MySQL database which is accessed by the Dashboard Client installations.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Server, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;MySQL 5.1 or higher&amp;lt;/b&amp;gt; on a database server. [http://www.mysql.com/downloads MySQL Download] site.  If the database server is not the same machine as the LRM server, then you will need to install the MySQL 5.x Client (only need Client) on the LRM server so that it can access the database on the separate database server.&lt;br /&gt;
 &lt;br /&gt;
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u &amp;lt;user&amp;gt; -p&amp;lt;password&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* If you are running on Windows, make sure that you have your Environment Path set to MySQL&#039;s bin directory. Select  &amp;lt;code&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced System Settings-&amp;gt;Advanced-&amp;gt;Environment Variables&amp;lt;/code&amp;gt; and, if necessary, add an entry similar to this to the Path variable: &amp;lt;code&amp;gt;C:\Program Files\MySQL\MySQL Server 5.5\bin&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Determine &amp;lt;b&amp;gt;the port&amp;lt;/b&amp;gt; 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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Download the installer jar file &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; (See support@lingoport.com if you don&#039;t have that information. It should have been sent in an email based on your license. )&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
Once you have ensured that all requirements are met, run the Dashboard Server installer.&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The installation process will set up the Dashboard database as well as install the the Dashboard web server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are &amp;lt;b&amp;gt;upgrading&amp;lt;/b&amp;gt; your Dashboard Server to a newer version, make sure that you do not overwrite the existing database.&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Server-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* In &amp;lt;b&amp;gt;Step 5&amp;lt;/b&amp;gt; of the installation process, be sure to &amp;lt;b&amp;gt;uncheck&amp;lt;/b&amp;gt; the checkbox labeled &amp;lt;b&amp;gt;Install LINGODASH Database Data&amp;lt;/b&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Follow the steps in the next section to start the Dashboard Server. See the section on &amp;lt;b&amp;gt;Upgrading the Dashboard Client&amp;lt;/b&amp;gt; for additional upgrade instructions.&lt;br /&gt;
&lt;br /&gt;
===Running the Dashboard Server===&lt;br /&gt;
After installation, follow these steps to ensure that the server is running and can be successfully displayed:&lt;br /&gt;
* 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.&lt;br /&gt;
* For Windows, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;StartSonar&amp;lt;/code&amp;gt;&lt;br /&gt;
*For Mac or Linux, enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;./sonar.sh start&amp;lt;/code&amp;gt;&lt;br /&gt;
*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.&lt;br /&gt;
* To start the server, open a browser from the server system or another computer that has access to the server and enter:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://&amp;lt;hostname&amp;gt;:&amp;lt;port&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, displaying the Dashboard on the local system with the default port 9000:&lt;br /&gt;
    &amp;lt;code&amp;gt;http://localhost:9000&amp;lt;/code&amp;gt;&lt;br /&gt;
You should see the Lingoport Dashboard web page.&lt;br /&gt;
&lt;br /&gt;
===When You Want to Limit Dashboard Server Access===&lt;br /&gt;
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:&lt;br /&gt;
* Log into MySQL on the system where you installed the Dashboard Server, as the root user.&lt;br /&gt;
    &amp;lt;code&amp;gt;mysql -u root -p[password]&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to remove the wildcard host for the dashboard user:&lt;br /&gt;
    &amp;lt;code&amp;gt;DROP USER &#039;&amp;lt;lingoport dashboard user&amp;gt;&#039;@&#039;%&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
*Execute this command to make sure you now see just the Lingoport Dashboard user for localhost:&lt;br /&gt;
    &amp;lt;code&amp;gt;select user,host from mysql.user;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
    &amp;lt;code&amp;gt;GRANT ALL PRIVILEGES ON &amp;lt;database&amp;gt;.* TO &#039;&amp;lt;Dashboard User&amp;gt;&#039;@&#039;%&#039; IDENTIFIED BY &#039;&amp;lt;pwd&amp;gt;&#039;;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Installing the Dashboard Client =&lt;br /&gt;
Run the client installer after the server is installed and &amp;lt;i&amp;gt;running&amp;lt;/i&amp;gt;. 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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Note&amp;lt;/b&amp;gt;: You will need to rerun the Dashboard Client installer whenever you upgrade the Globalyzer Client and/or the LRM Client.&lt;br /&gt;
&lt;br /&gt;
==Pre-requisites ==&lt;br /&gt;
Before installing the Dashboard Client, check that you have met the following requirements:&lt;br /&gt;
&amp;lt;OL&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Read the Lingoport Suite Installation Overview section, which describes how all the Lingoport applications work together and the hardware and software configuration requirements.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Selected a target machine that has a &amp;lt;b&amp;gt;supported Operating System&amp;lt;/b&amp;gt;: Windows, Linux, or MacOS&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Installed &amp;lt;b&amp;gt;Java 7 or greater&amp;lt;/b&amp;gt; JRE on the target machine. You can check your Java version using the command line. At the command prompt enter: &lt;br /&gt;
&amp;lt;code&amp;gt;java -version&amp;lt;/code&amp;gt;&lt;br /&gt;
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.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;The Dashboard Server has been started and is accessible from the target machine (see the Running the Dashboard Server section above).&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt; Know the Globalyzer Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the LRM Client installation directory, if installed.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Host name and Port number to access the Dashboard database you set up when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Know the Dashboard Server connection port number that you entered when you installed the Dashboard Server.&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;LI&amp;gt;Downloaded the installer jar file Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/LI&amp;gt;&lt;br /&gt;
&amp;lt;/OL&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
===Installing for the First Time===&lt;br /&gt;
* Double-click on the &amp;lt;code&amp;gt;Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt; file, or&lt;br /&gt;
* From the command line, cd to the directory with the installer and type: &lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* Follow instructions in the User&#039;s Guide (see Next Steps) to create a Dashboard project and upload data to the Dashboard Server.&lt;br /&gt;
&lt;br /&gt;
===Updating Your Existing Installation===&lt;br /&gt;
If you are upgrading your Dashboard Client to a newer version, make sure that you update any scripts referencing the old version.&lt;br /&gt;
&lt;br /&gt;
*Double-click on the Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar file, or&lt;br /&gt;
*From the command line, cd to the directory with the installer jar file and type:&lt;br /&gt;
    &amp;lt;code&amp;gt;java –jar Lingoport_Dashboard_Client-&amp;lt;x.x&amp;gt;-Installer.jar&amp;lt;/code&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
* For each Dashboard Project, rerun the scripts to scan with Globalyzer and/or LRM and reload the data to the Dashboard.&lt;br /&gt;
&lt;br /&gt;
= Next Steps = &lt;br /&gt;
If this is a new installation, you will need to configure your Dashboard Project and start displaying the status of your application&#039;s internationalization and localization efforts. For instructions on these and other capabilities, see the Dashboard User&#039;s Guide, located in the lingoport directory of your Server and Client installations.&lt;br /&gt;
&lt;br /&gt;
= Lingoport Customer Support =&lt;br /&gt;
If you experience difficulties during the installation of the Lingoport Dashboard, please contact support@lingoport.com.&lt;/div&gt;</summary>
		<author><name>Lcameron</name></author>
	</entry>
</feed>