Difference between revisions of "Localyzer Instrumentation"

From Lingoport Wiki
Jump to: navigation, search
(LRM InContext License)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= Introduction =
 
= Introduction =
To begin working with InContext Translation and InContext QA, the LRM version and license must be correct.
+
To begin working with InContext Translation and InContext QA, the Localyzer version and license must be correct.
   
= LRM version =
+
= Localyzer version =
   
The easiest way to check your LRM implementation is to run the Jenkins '''<group>.LicenseExpiration''' job and check the console output.
+
The easiest way to check your Localyzer implementation is to run the Jenkins '''<group>.LicenseExpiration''' job and check the console output.
   
 
You should see something that looks like:
 
You should see something that looks like:
Line 18: Line 18:
 
mysql Ver 14.14 Distrib 5.7.24, for Linux (x86_64) using EditLine wrapper
 
mysql Ver 14.14 Distrib 5.7.24, for Linux (x86_64) using EditLine wrapper
 
 
--- LRM
+
--- Localyzer
LRM Version 4.2.28
+
Localyzer Version 4.2.28
   
LRM Process Main Version 4.2.04
+
Localyzer Process Main Version 4.2.04
   
 
Lingoport-FTP Connection Version 4.2.00
 
Lingoport-FTP Connection Version 4.2.00
Line 35: Line 35:
 
Lingoport Common Version 4.2.07
 
Lingoport Common Version 4.2.07
 
 
LRM Common Version 4.2.00
+
Localyzer Common Version 4.2.00
   
   
Line 51: Line 51:
 
Number of projects on-boarded: 4
 
Number of projects on-boarded: 4
 
-------------------------------------------------------
 
-------------------------------------------------------
Detail of projects in the LRM database:
+
Detail of projects in the Localyzer database:
   
 
Maximum number of projects allowed is `1,000`.
 
Maximum number of projects allowed is `1,000`.
Line 67: Line 67:
 
In order to do instrumentation, the '''InContext Expiration Date''' must be populated and the date in the future. If not, please contact Lingoport support: support@lingoport.com.
 
In order to do instrumentation, the '''InContext Expiration Date''' must be populated and the date in the future. If not, please contact Lingoport support: support@lingoport.com.
   
= LRM InContext License =
+
= Localyzer InContext License =
* If the '''LRM Common Version''' is not 4.2 or higher, LRM on the system needs to be updated and new license installed.
+
* If the '''Localyzer Common Version''' is not 4.2 or higher, Localyzer on the system needs to be updated and new license installed.
* If the '''LRM InContext Expiration Date''' and '''Number of InContext QA days''' are blank or non-existent, then the Jenkins '''ManageLicenses''' job needs to be run with a license that includes InContext QA. Running the Jenkins '''<group>.LicenseExpiration''' job afterward will verify that the license exists.
+
* If the '''Localyzer InContext Expiration Date''' and '''Number of InContext QA days''' are blank or non-existent, then the Jenkins '''ManageLicenses''' job needs to be run with a license that includes InContext QA. Running the Jenkins '''<group>.LicenseExpiration''' job afterward will verify that the license exists.
   
 
Contact '''support@lingoport.com''' for assistance or with questions or concerns.
 
Contact '''support@lingoport.com''' for assistance or with questions or concerns.
   
  +
= Next Steps =
'''Next:''' To continue installation of InContext for Translation, proceed with [[InContext_Server_Installation| InContext Server Installation]]
 
  +
To continue installation of InContext for Translation, proceed with [[InContext_Server_Installation| InContext Server Installation]]
   
= LRM Instrumentation =
+
To learn more about Localyzer Instrumentation:
 
To learn more about LRM Instrumentation:
 
 
[[LRM_Commands_Reference#Create_Instrumented_files| LRM Instrumentation]]
 
[[LRM_Commands_Reference#Create_Instrumented_files| LRM Instrumentation]]

Latest revision as of 20:30, 23 February 2021

Introduction

To begin working with InContext Translation and InContext QA, the Localyzer version and license must be correct.

Localyzer version

The easiest way to check your Localyzer implementation is to run the Jenkins <group>.LicenseExpiration job and check the console output.

You should see something that looks like:

================================================================= 
 GENERAL INFORMATION
 
--- System
Linux ip-172-31-54-161.ec2.internal 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
openjdk version "1.8.0_201"
OpenJDK Runtime Environment (build 1.8.0_201-b09)
OpenJDK 64-Bit Server VM (build 25.201-b09, mixed mode)
mysql  Ver 14.14 Distrib 5.7.24, for Linux (x86_64) using  EditLine wrapper
 
--- Localyzer 
Localyzer Version 4.2.28

Localyzer Process Main Version 4.2.04

Lingoport-FTP Connection Version 4.2.00

Lingoport-GlobalLink Connection Version 4.2.03

Lingoport-Lingotek Connection Version 4.2.00

Lingoport-Local Connection Version 4.2.01

Lingoport-Worldserver Connection Version 4.2.01

Lingoport Common Version 4.2.07
 
Localyzer Common Version 4.2.00


================================================================= 
 CHECK_LICENSE for GROUP Acme

  Email Renewal Threshold:         30 days
  License Expiration Date:         2020-01-15
  Number of days left on license:  291 days
  InContext Expiration Date:       2020-01-15
  Number of InContext QA days:     291 days
  
  Number of projects licensed:     1000
  Number of projects remaining:    996
  Number of projects on-boarded:   4
-------------------------------------------------------
Detail of projects in the Localyzer database: 

  Maximum number of projects allowed is `1,000`.
  Project1
  Project2
  Project3
  Project4
Process completed successfully.

 END CHECK_LICENSE
 ========================================================== 


In order to do instrumentation, the InContext Expiration Date must be populated and the date in the future. If not, please contact Lingoport support: support@lingoport.com.

Localyzer InContext License

  • If the Localyzer Common Version is not 4.2 or higher, Localyzer on the system needs to be updated and new license installed.
  • If the Localyzer InContext Expiration Date and Number of InContext QA days are blank or non-existent, then the Jenkins ManageLicenses job needs to be run with a license that includes InContext QA. Running the Jenkins <group>.LicenseExpiration job afterward will verify that the license exists.

Contact support@lingoport.com for assistance or with questions or concerns.

Next Steps

To continue installation of InContext for Translation, proceed with InContext Server Installation

To learn more about Localyzer Instrumentation: LRM Instrumentation