Introduction
This article describes how to install and configure a TRM (Translation Resource Monitor) on an remote computing node, for an existing SES8 installation.
Description
To improve performance sometimes we may consider to add a different computing node and move the Systran Translation Resource Monitor. This procedure explains how to install and configure TRM on another computing node to communicate to TRS Console, RabbitMQ server & SES Console.
Installation
Update firewall rules on SES Frontend (RabbitMQ server host)
CentOS/RedHat 7
firewall-cmd --permanent --zone=public --add-port=5672/tcp firewall-cmd --permanent --zone=public --add-port=3445/tcp
firewall-cmd --permanent --zone=public --add-port=8889/tcp
firewall-cmd --permanent --zone=public --add-port=8892/tcp firewall-cmd --reload
CentOS/RedHat 6
Edit /etc/sysconfig/iptables by adding following lines
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5672 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 3445 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 8892 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 8889 -j ACCEPT
Open TRM port on new computing node
CentOS/RedHat 7
firewall-cmd --permanent --zone=public --add-port=8888/tcp firewall-cmd --reload
CentOS/RedHat 6
Edit /etc/sysconfig/iptables by adding following lines
-A INPUT -m state --state NEW -m tcp -p tcp --dport 8888 -j ACCEPT
Create ulimits conf file on new computing node
Create the /etc/security/limits.d/systran_ses_limits.conf file
* hard nofile 65536
* soft nofile 16384
* - nproc unlimited
root - nproc unlimited
systran - nproc unlimited
Add Systran Repository on new computing node
Create the /etc/yum.repos.d/systranrpm.repo file by adding the following content:
[systran-ses]
name=Systran RPM Repository
baseurl=https://repo.systran.net/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/systran_rpm/ses/8.6/centOS7/$basearch
enabled=1
gpgcheck=1
gpgkey=https://repo.systran.net/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/systran_rpm/GPG-KEY-systranreporpm
Change the xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx string by your TRS key.
Install Systran Translation Resources Monitor
yum install systran-translation-resource-monitor
CentOS/RedHat 7
systemctl enable systran-translation-resource-monitor systemctl restart systran-translation-resource-monitor
CentOS/RedHat 6
chkconfig systran-translation-resource-monitor on service systran-translation-resource-monitor restart
Configuration
On computing node, edit the /opt/systran/translation-resource-monitor/etc/trm.cfg file and change the following line:
broker = amqp://systran:SESpassword@localhost:5672
by
broker = amqp://systran:SESpassword@<RabbitMQ_server_host_ip_or_name>:5672
Then edit the /opt/systran/translation-resource-monitor/etc/source.http.cfg file and change the following line:
trsurl=https://localhost:3445
by
trsurl=https://<SES_FrontEnd_host_ip_or_name>:3445
Then restart the Translation Resource Monitor on new computing node
CentOS/RedHat 7
systemctl restart systran-translation-resource-monitor
CentOS/RedHat 6
service systran-translation-resource-monitor restart
Computing node registration
Last step consists of registering this computing node in your Systran Server.
- In the SES console, go to Administration / Environments, then for the targeted environment (e.g : production), click on Computing Nodes, fill the host IP or name field then click on Register:
After some seconds, the status for this new registered Computing Node should be Running.
Restart Systran Routing & Dispatcher on Front-End:
CentOS/RedHat 7
systemctl restart systran-routing.service && systemctl restart systran-translation-dispatcher.service
CentOS/RedHat 6
service systran-translation-resource-monitor restart && service systran-translation-dispatcher restart
Check
After registering the new computing node, by clicking on Refresh button, you should see the new computing node listed with status running.
This can be checked too into Administration > Service Monitoring then check the new computing node is listed with green state.
Test
The test consists of import & install a new Translation Resource on this new computing node, instantiate it then check if translation runs fine.