Difference between revisions of "Localyzer Instrumentation"
(→Localyzer version) |
(→InContext License & Version) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 12: | Line 12: | ||
The version of InContext Server must correspond to the version of Command Center. |
The version of InContext Server must correspond to the version of Command Center. |
||
| − | * Command Center 3.1. |
+ | * Command Center 3.1.35 |
| − | * InContext Server 2.0. |
+ | * InContext Server 2.0.9 |
| − | |||
| − | = 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 = |
= Next Steps = |
||
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
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
