Difference between revisions of "Localyzer Installation"

From Lingoport Wiki
Jump to: navigation, search
(→‎Setting up a Client)
 
(150 intermediate revisions by 4 users not shown)
Line 1: Line 1:
  +
== Stack Installer/Updater ==
−
== Resource Manager Installation ==
  
  +
The recommended way to install Localyzer is via the [[Installation and Configuration|Stack Installer]] or the Stack Updater.
  +
This page is kept in case a Localyzer patch for an existing version of the Lingoport Suite is needed.
   
  +
== Localyzer Overview ==
−
The Lingoport Resource Manager is composed of three items:
  
  +
Localyzer or as formerly known, the Lingoport Resource Manager System, is composed of several items that work together. (See the diagram at [[Components Diagram]]):
−
<UL><LI>the Resource Manager Server: many users can interact with the Resource Manager for the same projects. The Server keeps track of all the actions and the expected results. The server is best located on one central system accessible by all clients.
 
  +
# '''Localyzer''': The [[Terms_and_Definitions#LRMServer|Localyzer]] 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 Localyzer. The '''[[Terms_and_Definitions#LRMDatabase|Localyzer Database]]''' is created during the Localyzer installation.
−
</LI>
  
−
<LI>the Resource Manager Client: each user who interacts with the Resource Manager needs a client to execute the commands, such as verifying files to be sent for translation. The client is a light Java application and needs to communicate with the server.</LI>
 +
# '''Jenkins''': [[Terms_and_Definitions#Jenkins|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 Localyzer. The Jenkins setup is the subject of another guide.
−
<LI> the Dashboard: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.</LI>
 +
# '''Dashboard''': the [[Terms_and_Definitions#LingoportDashboard|Lingoport Dashboard]] aggregates and displays data from both the Resource Manager and [[Terms_and_Definitions|Globalyzer]]. Its installation is the subject of another guide.
−
</UL>
  
   
  +
The [[Terms_and_Definitions#LingoportDashboardClient|Dashboard Client]] typically needs to have access to the <code>lrm-cli.jar</code> files in order to generate the XML report files and subsequently push the files over to the [[Terms_and_Definitions#LingoportDashboardServer|Dashboard Server]].
−
The Resource Manager server must be installed before starting each individual Resource Manager installation.
  
   
  +
== Install using the Stack Installer ==
  +
The easiest way to install Localyzer on a typical system is to use the [[Terms_and_Definitions#stackinstaller|Stack Installer]]. It will install and configure Localyzer and its supporting components. Once the Stack Installer has completed, continue to [[LRM_Installation#Next_Steps|Next Steps]].
   
  +
If you cannot use the [[Terms_and_Definitions#stackinstaller|Stack Installer]], follow the instructions below.
−
=== Server Installation ===
  
−
Before installing the server, the following pre-requisites are necessary:
  
   
−
==== Pre-requisites ====
 +
== Install Jenkins==
  +
Localyzer should be installed with under the Jenkins user. If you have not done so yet, install Jenkins from [https://jenkins-ci.org/ jenkins-ci.org], install it, and start it as a daemon.
  +
  +
Check that the location of the 'workspace' is <b>${JENKINS_HOME}/jobs/${ITEM_FULLNAME}/workspace</b>. This location can be found by going to <code>Jenkins -> Manage Jenkins</code> select <code>Configure System</code> and click on <code>Advanced...</code> near the top right page. Look for <code>Workspace Root Directory</code>.
  +
  +
<em>This is very important</em>. A different Workspace Root Directory will cause real problems!
  +
  +
Check which <b>Unix user is running the Jenkins job</b>. Check the System Information by selecting <code>Manage Jenkins -> System Information</code> and search for USER.
  +
  +
== Installing Localyzer ==
  +
  +
===Prerequisites ===
  +
Before continuing see [[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|current supported software versions]]. These are the versions that need to be on the Localyzer Server. Review the [[Lingoport Suite Installation]], which describes how all the Lingoport applications work together and the hardware and software configuration requirements,
 
<OL>
  
<OL>
  +
<LI><b>Linux</b>: The supported Operating system is Linux, preferably CentOS. Verify that the correct version is running on the server. </LI>
−
<LI>Supported OS: Windows, Linux, MacOS</LI>
  
  +
<LI><b>Java</b>: Install the supported version of the <b>Java JDK</b> on the target machine. You can check the Java version using the command line. At the command prompt enter:
−
<LI>Installer jar file: you must have the Lingoport_Resource_Manager_Server-<x.x>-Installer.jar file.</LI>
  
  +
:<code>java -version</code>
−
<LI>License: Lingoport must have sent you an email with the licensing information. You must have that information ready before installing the server. If you do not have the licensing information of the jar file, please contact support@lingoport.com. </LI>
  
−
<LI>JVM: you must have a Java 6 or above JVM. To verify you do, simply type “java –version” at the command line and check the version. If you need to install Java, refer to the Java download page, for instance http://www.java.com/en/download/index.jsp </LI>
 +
The version of Java which you have on your system should be displayed. If you need to install Java, please refer to http://www.java.com/en/download/index.jsp or any Java download page which supplies the supported version of Java or above.</LI>
  +
−
<LI>MySQL: you must have a MySQL 5.1 or above database instance running and access to it. To verify this installation, type “mysql –u <username> -p<password> “at the command prompt. If you don’t have mysql installed or if mysql is not on your path, you may need to refer to MySql download and installation, for instance http://dev.mysql.com/downloads/.</LI>
  
  +
<LI><b>MySQL</b>: Install the supported version <b>MySQL </b> on a database server. If the database server is not the same machine as the Localyzer Server, then you will need to install the MySQL Client (only need Client) on the Localyzer Server so that it can access the database on the separate database server.
−
<LI>MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is 'MST' whereas 'America/Denver' is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately.
 
  +
−
<UL>
 
  +
* You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:
−
<LI>For Window, you should be able to type <code>SET GLOBAL time_zone = 'America/Denver’</code> at the MySQL prompt.</LI>
  
  +
:<code>mysql -u <user> -p<password></code>
−
<LI>For Linux, you could for instance type <code>mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p</code> from the command line and then <code>SET GLOBAL time_zone = 'America/Denver’</code> at the MySQL prompt.</LI>
  
  +
−
<LI>For MacOS, you may for instance type <code>mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -D mysql -u root mysql -p</code> from the command line and then <code>SET GLOBAL time_zone = 'America/Denver’</code> at the MySQL prompt.</LI>
  
  +
* 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 the supported version or higher, please refer to a download site, such as [http://dev.mysql.com/downloads MySQL Download] and install an up-to-date version.
−
</UL>
  
  +
  +
* You will need to enter the MySQL credentials (host, username, password and port number) during the installation.</LI>
  +
  +
<LI><b>Jenkins</b>: The latest version should be installed. See [[#Install Jenkins]]. Complete the installation of Jenkins and identify its user before attempting to install Localyzer.</LI>
  +
<LI><b>Localyzer Licensing information</b>: When your company purchased Localyzer you should have been sent an email containing the licensing information. The licensing information will include the following:
  +
* group name
  +
* number of licenses in the license
  +
* expiration date for the license
  +
* license key. This is a 10-digit number generated by Lingoport.
  +
This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact <code>support@lingoport.com</code>. Please keep it handy while you perform the install.</LI> You may have many licenses, one per group. This must have been specified during the sales process.
  +
  +
<LI><b>Installer jar file</b>: You must have the <b>Lingoport_Resource_Manager_Server-<x.x>-Installer.jar</b> file. Where <b><x.x></b> is the current supported version of Localyzer</LI>
  +
  +
<LI><b>MySQL Time Zone</b>: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is 'MST' whereas 'America/Denver' is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately.
  +
  +
For Linux, type <br><code>mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p</code><br> from the command line and then <br><code>SET GLOBAL time_zone = 'America/Denver’</code><br> at the MySQL prompt.
  +
 
</LI>
  
</LI>
 
</OL>
  
</OL>
   
  +
===Installing Localyzer ===
−
==== Setting up the Server ====
  
  +
Once you have retrieved your licensing information and ensured that all requirements are met (see previous section), log into the server as the <b>Unix user who will be running the Jenkins jobs</b>. This is usually the Jenkins user.
−
Run the installer by either:
  
−
<UL>
  
−
<LI>double clicking on the Lingoport_Resource_Manager_Server-<x.x>-Installer.jar</LI>
  
−
<LI>running “java –jar Lingoport_Resource_Manager_Server-<x.x>-Installer.jar“ at the command prompt.</LI>
  
−
</UL>
  
−
The Lingoport Resource Manager will then prompt you for license information and database settings to create the database tables in MySQL. Please note that the connection settings and the company ID in the server installation will be used in the subsequent client installations.
  
   
  +
* <b>IMPORTANT:</b> Which Unix user will do all the installation?
−
=== Client Installations ===
  
  +
** <b>Unix user who will be running the Jenkins jobs</b>
−
Before starting an individual client installation, the following pre-requisites are necessary:
  
  +
−
==== Pre-requisites ====
  
  +
There are two variations to the install.
−
<OL>
  
  +
# '''Initial Localyzer Installation''': The Localyzer installer will create the Localyzer Database and the <code>Lingoport_Data/L10nStreamlining</code> directory. The path to the <code>Lingoport_Data/LRM</code> will be established.
−
<LI>Supported OS: Windows, Linux, MacOS</LI>
  
  +
# '''Upgrading Localyzer''': Use this when upgrading your Localyzer to a newer version, this will make sure the existing Localyzer Database is not overwritten.
−
<LI>Installer jar file: you must have the Lingoport_Resource_Manager_Client-<x.x>-Installer.jar file.</LI>
  
  +
−
<LI>Server installed: the Resource Manager Server must have been installed.</LI>
  
  +
−
<LI>JVM: you must have a Java 6 or above JVM. To verify you do, simply type “java –version” at the command line and check the version. If you need to install Java, refer to the Java download page, for instance http://www.java.com/en/download/index.jsp . </LI>
  
  +
A '''headless installation''' is used to installLocalyzer without a windowing system. An XML installation file with the correct options specified is used from the command line.
−
<LI>MySQL: you must have access to the Lingoport Resource Manager MySQL 5.1 instance where the <B>server</B> installation was run.</LI>
  
  +
−
</OL>
  
  +
Please note that '''<code><x.x></code>''' is used in these instructions as a placeholder for the current version of Localyzer. To see the current version see [[Introduction#Current_versions_of_Lingoport_products_and_supporting_applications|current supported software versions]].
  +
  +
====Initial Localyzer Installation====
  +
  +
Verify that you are logged in as the <b>Unix user who will be running the Jenkins jobs</b>.
  +
  +
* Double-click on the <code>Lingoport_Resource_Manager_Server-<x.x>-Installer.jar</code> file, or
  +
* From the command line, cd to the directory with the installer jar file and type:
  +
::<code>java –jar Lingoport_Resource_Manager_Server-<x.x>-Installer.jar</code>
  +
  +
The installer will prompt you for the install location, license information and database settings to create the MySQL Localyzer database.
  +
The installer will also prompt you for the Localyzer and the L10nStreamlining directory location. These will default to <code><home>/Lingoport_Data/LRM</code> and <code><home>/Lingoport_Data/L10nStreamlining</code>. When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first [[Terms_and_Definitions#LRMproject|Localyzer project]] is generated.
  +
  +
To verify the installation, from the command line:
  +
<pre>
  +
> java -jar <install location>/lrm-cli.jar --version
  +
> java -jar <install location>/lrm-cli.jar --help
  +
</pre>
  +
This should show the current version of Localyzer and the help text. If either of these commands errors, something is incorrect and must be fixed before moving on.
  +
  +
====Updating An Existing Localyzer Installation====
  +
Verify that you are logged in as the <b>Unix user who will be running the Jenkins jobs</b>.
  +
  +
If you are upgrading your Localyzer to a newer version, make sure that you do not overwrite the existing database.
  +
*Double-click on the <code>Lingoport_Resource_Manager_Server-<x.x>-Installer.jar</code> file, or
  +
*From the command line, cd to the directory with the installer jar file and type:
  +
::<code>java –jar Lingoport_Resource_Manager_Server-<x.x>-Installer.jar</code>
  +
  +
On the Type of Installation page, be sure to select <b>Update Server</b>.
  +
  +
To verify the installation, from the command line:
  +
<pre>
  +
> java -jar <install location>/lrm-cli.jar --version
  +
> java -jar <install location>/lrm-cli.jar --help
  +
</pre>
  +
This should show the current version of Localyzer and the help text. If either of these commands errors, something is incorrect and must be fixed before moving on.
  +
  +
====Headless Installation====
  +
Verify that you are logged in as the <b>Unix user who will be running the Jenkins jobs</b>.
  +
  +
To install or update Localyzer without a windowing system or from a command line, 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 [[Terms_and_Definitions#headless|headless installation]], from the command line, cd to the directory with the installer and type:
  +
:<code>java –jar Lingoport_Resource_Manager_Server-<x.x>-Installer.jar headlessinstaller.xml</code>
  +
  +
To verify the installation, from the command line:
  +
<pre>
  +
> java -jar <install location>/lrm-cli.jar --version
  +
> java -jar <install location>/lrm-cli.jar --help
  +
</pre>
  +
This should show the current version of Localyzer and the help text. If either of these commands errors, something is incorrect and must be fixed before moving on.
  +
  +
===Adding or Updating the License===
  +
Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license.
  +
To update or add a new license to your current installation, open a command prompt and type:
  +
*'''Update an existing license''' for a group:
  +
:<code>java -jar <LRM_INSTALLATION_PATH>lrm-cli.jar --update-license --group-name <group> --number-of-licenses <number> --date <YYYY-MM-DD> --license-key <key> </code>
  +
* '''Add a new license''' for a group:
  +
:<code>java -jar <LRM_INSTALLATION_PATH>/lrm-cli.jar --create-group <groupname> --number-of-licenses <number> --date <YYYY-MM-DD> --license-key <key> </code>
  +
* '''Verify''' that the new license has been installed with the correct information:
  +
:<code>java -jar <LRM_INSTALLATION_PATH>/lrm-cli.jar --list-groups</code>
  +
  +
===Group Name===
  +
The group name must be established before Lingoport can issue a license key.
  +
A group name <b>must conform</b> to the following specification:
  +
A set of alphanumeric characters without the following special characters:
  +
  +
* < (less than)
  +
* > (greater than)
  +
* : (colon)
  +
* " (double quote)
  +
* / (forward slash)
  +
* \ (backslash)
  +
* | (vertical bar or pipe)
  +
* ? (question mark)
  +
* * (asterisk)
  +
* (space)
  +
* % (percentage)
  +
  +
= Next Steps =
  +
After the installation, there is a
  +
  +
If this is a new installation, you will need to configure your [[Terms_and_Definitions#LRMProject|Localyzer Project]] and start managing your application's [[Terms_and_Definitions#resourcefiles|resource files]]. This involves configuring [[Terms_and_Definitions#Jenkins|Jenkins]] with tabs, the jobs, the users, and the authorizations. See [[LRM Jenkins Configure System| Localyzer Jenkins Configure System]].
  +
  +
Localyzer works with the [[Terms_and_Definitions#LingoportDashboard|Lingoport Dashboard]]. If you have the Dashboard currently installed, make sure it is configured to point to the current Localyzer installation. You may want to update the Dashboard installation to do so. If you are going to install the Dashboard later, then don't worry for now. This will be part of the Dashboard installation process.
   
  +
<b>Important MySQL Configuration Note: </b>
−
==== Setting up a Client ====
  
  +
If you see the following error when running Localyzer commands: <b>Packet for query is too large</b>
−
Run the installer by either:
  
  +
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.
−
<UL><LI>double clicking on the Lingoport_Resource_Manager_Client-<x.x>-Installer.jar</LI>
  
−
<LI>running <CODE>java –jar Lingoport_Resource_Manager_Client-<x.x>-Installer.jar</CODE> at the command prompt.</LI>
  
−
</UL>
  
−
The Lingoport Resource Manager will then prompt you for which database to use for the client.
  
   
  +
= Lingoport Customer Support =
−
Proceed to the Getting Started portion of this FAQ.
  
  +
If you experience difficulties during the installation or update of the Lingoport Resource Manager, please contact '''support@lingoport.com'''.

Latest revision as of 14:11, 12 July 2021

Stack Installer/Updater

The recommended way to install Localyzer is via the Stack Installer or the Stack Updater. This page is kept in case a Localyzer patch for an existing version of the Lingoport Suite is needed.

Localyzer Overview

Localyzer or as formerly known, the Lingoport Resource Manager System, is composed of several items that work together. (See the diagram at Components Diagram):

  1. Localyzer: The Localyzer 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 Localyzer. The Localyzer Database is created during the Localyzer installation.
  2. Jenkins: 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 Localyzer. The Jenkins setup is the subject of another guide.
  3. Dashboard: the Lingoport Dashboard aggregates and displays data from both the Resource Manager and Globalyzer. Its installation is the subject of another guide.

The Dashboard Client typically needs to have access to the lrm-cli.jar files in order to generate the XML report files and subsequently push the files over to the Dashboard Server.

Install using the Stack Installer

The easiest way to install Localyzer on a typical system is to use the Stack Installer. It will install and configure Localyzer and its supporting components. Once the Stack Installer has completed, continue to Next Steps.

If you cannot use the Stack Installer, follow the instructions below.

Install Jenkins

Localyzer should be installed with under the Jenkins user. If you have not done so yet, install Jenkins from jenkins-ci.org, install it, and start it as a daemon.

Check that the location of the 'workspace' is ${JENKINS_HOME}/jobs/${ITEM_FULLNAME}/workspace. This location can be found by going to Jenkins -> Manage Jenkins select Configure System and click on Advanced... near the top right page. Look for Workspace Root Directory.

This is very important. A different Workspace Root Directory will cause real problems!

Check which Unix user is running the Jenkins job. Check the System Information by selecting Manage Jenkins -> System Information and search for USER.

Installing Localyzer

Prerequisites

Before continuing see current supported software versions. These are the versions that need to be on the Localyzer Server. Review the Lingoport Suite Installation, which describes how all the Lingoport applications work together and the hardware and software configuration requirements,

  1. Linux: The supported Operating system is Linux, preferably CentOS. Verify that the correct version is running on the server.
  2. Java: Install the supported version of the Java JDK on the target machine. You can check the Java version using the command line. At the command prompt enter:
    java -version
    The version of Java which you have on your system should be displayed. If you need to install Java, please refer to http://www.java.com/en/download/index.jsp or any Java download page which supplies the supported version of Java or above.
  3. MySQL: Install the supported version MySQL on a database server. If the database server is not the same machine as the Localyzer Server, then you will need to install the MySQL Client (only need Client) on the Localyzer Server so that it can access the database on the separate database server.
    • You can verify that you have a sufficiently up-to-date version of MySQL using the command prompt. In the command prompt type:
    mysql -u <user> -p<password>
    • If MySQL is installed on your system, information on the version will be displayed after entering a valid username and password. If MySQL is not the supported version or higher, please refer to a download site, such as MySQL Download and install an up-to-date version.
    • You will need to enter the MySQL credentials (host, username, password and port number) during the installation.
  4. Jenkins: The latest version should be installed. See #Install Jenkins. Complete the installation of Jenkins and identify its user before attempting to install Localyzer.
  5. Localyzer Licensing information: When your company purchased Localyzer you should have been sent an email containing the licensing information. The licensing information will include the following:
    • group name
    • number of licenses in the license
    • expiration date for the license
    • license key. This is a 10-digit number generated by Lingoport.
    This licensing information will be required for the server installation. If you do not have the licensing information of the jar file, please contact support@lingoport.com. Please keep it handy while you perform the install.
    6. You may have many licenses, one per group. This must have been specified during the sales process.
  6. Installer jar file: You must have the Lingoport_Resource_Manager_Server-<x.x>-Installer.jar file. Where <x.x> is the current supported version of Localyzer
  7. MySQL Time Zone: MySQL time zone must be non-ambiguous. An example of an ambiguous time zone is 'MST' whereas 'America/Denver' is a non-ambiguous time zone. Refer to MySQL documentation for your specific OS to set time zones appropriately. For Linux, type
    mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p
    from the command line and then
    SET GLOBAL time_zone = 'America/Denver’
    at the MySQL prompt.

Installing Localyzer

Once you have retrieved your licensing information and ensured that all requirements are met (see previous section), log into the server as the Unix user who will be running the Jenkins jobs. This is usually the Jenkins user.

  • IMPORTANT: Which Unix user will do all the installation?
    • Unix user who will be running the Jenkins jobs

There are two variations to the install.

  1. Initial Localyzer Installation: The Localyzer installer will create the Localyzer Database and the Lingoport_Data/L10nStreamlining directory. The path to the Lingoport_Data/LRM will be established.
  2. Upgrading Localyzer: Use this when upgrading your Localyzer to a newer version, this will make sure the existing Localyzer Database is not overwritten.


A headless installation is used to installLocalyzer without a windowing system. An XML installation file with the correct options specified is used from the command line.

Please note that <x.x> is used in these instructions as a placeholder for the current version of Localyzer. To see the current version see current supported software versions.

Initial Localyzer Installation

Verify that you are logged in as the Unix user who will be running the Jenkins jobs.

  • Double-click on the Lingoport_Resource_Manager_Server-<x.x>-Installer.jar file, or
  • From the command line, cd to the directory with the installer jar file and type:
java –jar Lingoport_Resource_Manager_Server-<x.x>-Installer.jar

The installer will prompt you for the install location, license information and database settings to create the MySQL Localyzer database. The installer will also prompt you for the Localyzer and the L10nStreamlining directory location. These will default to <home>/Lingoport_Data/LRM and <home>/Lingoport_Data/L10nStreamlining. When installation completes, the L10nStreamlining directory will have been created, but the LRM directory is created when the first Localyzer project is generated.

To verify the installation, from the command line: 

> java -jar <install location>/lrm-cli.jar --version
> java -jar <install location>/lrm-cli.jar --help

This should show the current version of Localyzer and the help text. If either of these commands errors, something is incorrect and must be fixed before moving on.

Updating An Existing Localyzer Installation

Verify that you are logged in as the Unix user who will be running the Jenkins jobs.

If you are upgrading your Localyzer to a newer version, make sure that you do not overwrite the existing database.

  • Double-click on the Lingoport_Resource_Manager_Server-<x.x>-Installer.jar file, or
  • From the command line, cd to the directory with the installer jar file and type:
java –jar Lingoport_Resource_Manager_Server-<x.x>-Installer.jar

On the Type of Installation page, be sure to select Update Server.

To verify the installation, from the command line: 

> java -jar <install location>/lrm-cli.jar --version
> java -jar <install location>/lrm-cli.jar --help

This should show the current version of Localyzer and the help text. If either of these commands errors, something is incorrect and must be fixed before moving on.

Headless Installation

Verify that you are logged in as the Unix user who will be running the Jenkins jobs.

To install or update Localyzer without a windowing system or from a command line, 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:

java –jar Lingoport_Resource_Manager_Server-<x.x>-Installer.jar headlessinstaller.xml

To verify the installation, from the command line: 

> java -jar <install location>/lrm-cli.jar --version
> java -jar <install location>/lrm-cli.jar --help

This should show the current version of Localyzer and the help text. If either of these commands errors, something is incorrect and must be fixed before moving on.

Adding or Updating the License

Depending on your licensing agreement, you will have a license for one or more groups. Each group must have a license. To update or add a new license to your current installation, open a command prompt and type:

  • Update an existing license for a group:
java -jar <LRM_INSTALLATION_PATH>lrm-cli.jar --update-license --group-name <group> --number-of-licenses <number> --date <YYYY-MM-DD> --license-key <key>
  • Add a new license for a group:
java -jar <LRM_INSTALLATION_PATH>/lrm-cli.jar --create-group <groupname> --number-of-licenses <number> --date <YYYY-MM-DD> --license-key <key>
  • Verify that the new license has been installed with the correct information:
java -jar <LRM_INSTALLATION_PATH>/lrm-cli.jar --list-groups

Group Name

The group name must be established before Lingoport can issue a license key. A group name must conform to the following specification: A set of alphanumeric characters without the following special characters:

  • < (less than)
  • > (greater than)
  •  : (colon)
  • " (double quote)
  • / (forward slash)
  • \ (backslash)
  • | (vertical bar or pipe)
  •  ? (question mark)
  • * (asterisk)
  • (space)
  •  % (percentage)

Next Steps

After the installation, there is a

If this is a new installation, you will need to configure your Localyzer Project and start managing your application's resource files. This involves configuring Jenkins with tabs, the jobs, the users, and the authorizations. See Localyzer Jenkins Configure System.

Localyzer works with the Lingoport Dashboard. If you have the Dashboard currently installed, make sure it is configured to point to the current Localyzer installation. You may want to update the Dashboard installation to do so. If you are going to install the Dashboard later, then don't worry for now. This will be part of the Dashboard installation process.

Important MySQL Configuration Note: If you see the following error when running Localyzer commands: Packet for query is too large 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.

Lingoport Customer Support

If you experience difficulties during the installation or update of the Lingoport Resource Manager, please contact support@lingoport.com.

Retrieved from "http://wiki.lingoport.com/index.php?title=Localyzer_Installation&oldid=95474"