RWS Offline Language Translation
FTK Core and FTK Plus now allow users to integrate RWS Language Translation to enhance translation capabilities with machine learning. While the integration comes at a cost, it ensures users can see improvements in accuracy as well as processing times.
TABLE OF CONTENTS
- RWS Offline Language Translation
Support for FTK Central will be available soon.
Supported Languages
|
|
Minimum System Requirements
RWS Language Weaver – Master Host
- 1 CPU Core
- 1GB RAM
- 4GB Storage
Language Pair – Translation Engine
Actual requirements are proportional to the number of language pairs to be installed.
- 1-4 CPU Cores [Increase core count for best performance]
- 4GB RAM
- 30GB Storage
- 2GB GPU RAM [If utilising Neural Language Pairs ONLY]
Supported Operating Systems
Windows x64 | Linux x64 |
Windows 10 | CentOS 7 |
Windows 8.1 | CentOS 8 |
Windows 8 | Ubuntu 14.04 |
Windows 7 SP1 | Ubuntu 16.04 |
Windows Server 2012 | Ubuntu 18.04 |
Windows Server 2016 | Ubuntu 20.04 |
Windows Server 2019 | Red Hat Enterprise Linux (RHEL) 7 |
Red Hat Enterprise Linux (RHEL) 8 |
Firewall Rules
TCP Port | Descriptions | Required |
8000 | The Host/Server listens on the port for incoming client/browser HTTP(S) connections to the Language Weaver Edge WEB UI. | Yes |
8001 | The Host/Server listens on the port for incoming client HTTP(S) connections to the Language Weaver Edge REST API. | Yes |
5671 | The Host/Server listens on the port for incoming worker connections to the Language Weaver Edge Message Broker component. | Yes |
5673 | The Host/Server listens on the port for incoming worker connections to the Language Weaver Edge Message Broker component. | Yes |
4637 | The Host/Server listens on the port for incoming client connections to the Language Weaver Edge Host Agent API component. | Yes |
Installation
While installing Language Weaver Edge, a domain-level service account with local administration rights is required in a distributed environment.
The installer has two installation modes:
- Master Host: Serves REST API, Web GUI, and optionally Job Engine(s) and/or Translation Engine(s)
- Worker Host: Serves Job Engine(s) and/or Translation Engine(s)
Installing Language Weaver Edge – Master Host or Worker Host
- Locate the Language Weaver Edge installer and Run as Administrator.
- Click Next.
- Review and Accept to the License Agreement. Click Next.
- Select an Installation Directory and click Next.
- Select As a master host and click Next.
- Select As a worker host if installing as a Translation Engine.
- Select No when prompt to install the embedded API components and click Next.
- Enter administrator details:
- Username (Email Address)
- Display Name
- Password
- Click Next.
- Select Do not use HTTPS/TLS.
- If required you can select either, Use user-provided certificates or Use self-signed certificates automatically generated by Language Weaver Edge.
- Click Next.
- Select the default server port. The default web server port is 8000.
- Click Next.
- Click Next again to start the installation process.
- When prompt, Allow Access for ets-initial-setup.exe.
- Click Finishwhen the installation is complete.
- The Language Weaver Edge UI will appear in your default browser.
- Enter the login credentials created during installation to test.
Installing Language Pairs
- Locate the Language Pair setup installer and Run as Administrator.
- Click Next.
- Review and Accept to the License Agreement. Click Next.
- Select an Installation Directory and click Next.
- Click Next again to start the installation process.
- Click Finish.
Configuration
With a Master Host and Language Pair installed, you must configure the job engines and the related translation engines.
Adding a Job Engine
- Go to <MasterHost>:8000
- Click Edit in the top-right corner.
- Click Manage > Deployment.
- Click Add in the Job Engines column.
- Enter a Host.
- Click Add.
- Click Done Editing in the top-right corner.
Adding a Translation Engine
- Go to <MasterHost>:8000
- Login with the credentials created during installation.
- Click Edit in the top-right corner.
- Click Manage > Deployment.
- Click Add in the Translation Engines column.
- Enter a Host.
- This is the Job Engine address.
- Select the Mode as Auto-detect.
- The language Pair can be selected but will not populate without a License.
- If you are sure of the language pairs being assigned to a job engine, then provide the language pair details respectively.
- Click Add.
- Click Done Editing in the top-right corner.
Obtaining a License from RWS
- Go to <Hostname>:8000
- Login with the credentials created during installation.
- Click on Entitlements.
- Click Download Entitlements Profile.
- Myhost.json will be downloaded.
- Contact SDLMT Support Team to get a license file.
- Go to https://gateway.sdl.com
- Click Login for Support.
- Enter the assigned SDL Administrator credentials.
- Click on My Support.
- Click Log a Case.
- Within the form provided, provide basic details such as, email addresses, description of the languages required and upload the resultant myhosts.json file.
- Click Submit Case.
- Please note, the resultant license file will be sent to you in 1-3 days.
Adding a License
- Go to <MasterHost>:8000
- Login with the credentials created during installation.
- Click on Entitlements.
- Click Upload License File.
- Locate the license file provided by RWS and click OK.
- You may be prompt about unassigned language pairs. If you have not assigned a language pair to a job engine, then you will need to do so by navigating to the Hosts page.
Starting/Stopping Job or Translation Engines
- Go to <MasterHost>:8000
- Login with the credentials created during installation.
- Click on Hosts.
- Click the Stop/Start button to stop or start an engine.
Verifying Translation Service
- Go to <MasterHost>:8000
- Login with the credentials created during installation.
- Click Translate.
- Select an input language and enter some text.
- Select an output Language.
- The results should be displayed. If they are not, please ensure the SDL MTE Manager service is running.
Obtaining the RWS API Key
- Go to <MasterHost>:8000
- Login with the credentials created during installation.
- Click on My Account in the top-right corner.
- Copy the API key and save it in a text file for reference.
- Copy the API Base URL.
Adding the Translation Server in FTK Plus
- Do one of the following:
- For new cases, in the Add/Import Evidence > Processing Options dialog click Customize.
- For existing cases, in the Examiner, click Evidence > Additional Analysis.
- Check Language Translation.
- Click Language Translation Options.
- Click Configure.
- Enter the following:
- Server URL
- Port Number
- API Key
- Click OK.
- Select the Types to Process.
- Documents
- Presentations
- Spreadsheets
- Graphics
Adding the Translation Server in FTK Suite
- Do one of the following:
- For new cases, in the New Case Options dialog click Customize.
- For existing cases, in the Examiner, click Evidence > Additional Analysis.
- Check Language Translation.
- Click Language Translation Options.
- Click Configure.
- Enter the following:
- Server URL
- Port Number
- API Key
- Click OK.
- Select the Types to Process.
- Documents
- Presentations
- Spreadsheets
- Graphics
- Select a Target Language.
- Click OK.
Multi-server Deployment Example
The diagram below is an example of a hypothetical multi-server deployment with FTK Enterprise, it includes the following:
- 1 x FTK Enterprise Machine
- 1 x Worker Host
- 1 x Job Engine with 2 x Translation Engines.
- 1 x Job Engine with 1 x Translation Engines.
Hostname | Master Host | Worker Host | CPU | RAM | Storage | Language Pairs Installed |
Fiona | Yes | No | 4 Core | 4GB | 60GB | None |
Penelope | No | Yes | 8 Core | 16GB | 60GB | French to English Spanish to English |
Hercule | No | Yes | 4 Core | 8GB | 40GB | German to English |
Host Penelope has been assigned more resources in this example as it will be handling an additional translation engine as well as it being expected to have higher usage.