Difference between revisions of "Localyzer Instrumentation"

From Lingoport Wiki
Jump to: navigation, search
(LRM Instrumentation)
(InContext License & Version)
 
(19 intermediate revisions by 3 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.
   
  +
= InContext License & Version =
= LRM version =
 
   
  +
In order to use InContext Server, your system must have a valid license. To check the license, navigate to the Settings page
The easiest way to check your LRM implementation is to run the Jenkins '''<group>.LicenseExpiration''' job and check the console output.
 
   
  +
 [[File:InContextLicense.png|center|500px]]
You should see something that looks like:
 
<pre>
 
=================================================================
 
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
 
 
--- LRM
 
LRM Version 4.2.28
 
   
  +
If the system does not have a valid license, please contact ''support @ lingoport dot com''.
LRM Process Main Version 4.2.04
 
   
Lingoport-FTP Connection Version 4.2.00
 
   
  +
The version of InContext Server must correspond to the version of Command Center.
Lingoport-GlobalLink Connection Version 4.2.03
 
  +
* Command Center 3.1.35
  +
* InContext Server 2.0.9
   
  +
= Next Steps =
Lingoport-Lingotek Connection Version 4.2.00
 
  +
To continue installation of InContext for Translation, proceed with [[InContext_Server_Installation| InContext Server Installation]]
   
  +
To learn more about Localyzer Instrumentation:
Lingoport-Local Connection Version 4.2.01
 
  +
[[LRM_Commands_Reference#Create_Instrumented_files| LRM Instrumentation]]
 
Lingoport-Worldserver Connection Version 4.2.01
 
 
Lingoport Common Version 4.2.07
 
 
LRM Common Version 4.2.00
 
 
 
=================================================================
 
CHECK_LICENSE for GROUP Acme
 
Proj Path
 
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 LRM database:
 
 
Maximum number of projects allowed is `1,000`.
 
Project1
 
Project2
 
Project3
 
Project4
 
Process completed successfully.
 
 
END CHECK_LICENSE
 
==========================================================
 
</pre>
 
 
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 =
 
* 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 '''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.
 
 
Contact '''support@lingoport.com''' for assistance or with questions or concerns.
 
 
= LRM Instrumentation =
 
If there is a valid InContext license for the group, then files can be ''instrumented''. LRM instrumentation is the process of inserting non-printable characters into each resource string. These non-printable characters are used to access information about the key/value/file using either [[About_InContext_QA|InContext QA]] or [[About_InContext_Translation|InContext Translation]].
 
The instrumented files all have a suffix of ''LRM_LQA''. For example, the instrumented file that corresponds to the resource file ''file1-fr-fr.properties'' will have the name ''file1-fr-fr_LRMLQA.properties''. The instrumented files are located in the same location as their corresponding resource file.
 
 
Instrumented files are automatically created during the prep kit process if the project's L10n Vendor configuration file has a valid [[L10n_Vendors#InContext_Server_Configuration.| InContext Server defined.]]
 
If using [[About_InContext_QA|InContext QA]] then instrumentation can occur during the Jenkins Automation job by adding the [[Quick_On-Boarding_Reference#IQA_Instrument_Build_Step_.28Optional.29|IQA Instrument Build Step]].
 

Latest revision as of 13:11, 17 July 2025

Introduction

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

InContext License & Version

In order to use InContext Server, your system must have a valid license. To check the license, navigate to the Settings page

 

InContextLicense.png

If the system does not have a valid license, please contact support @ lingoport dot com.


The version of InContext Server must correspond to the version of Command Center.

  • Command Center 3.1.35
  • InContext Server 2.0.9

Next Steps

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

To learn more about Localyzer Instrumentation: LRM Instrumentation