openTMStermTagger Configuration
openTMStermTagger is not part of translate5, but translate5 builds on it to find and highlight terminology.
First some permissions has to be corrected:
sudo chmod 775 /var/www/translate5/application/modules/editor/ThirdParty/XliffTermTagger/startServer.sh sudo chmod 775 /var/www/translate5/application/modules/editor/ThirdParty/XliffTermTagger/stopServer.sh
The next step might not be necessary on most/some of the systems. If Oracle Java is not your only installed Java version you have to do the next step. In all other cases it is still recommended to avoid problems.
Open the file
/var/www/translate5/application/modules/editor/ThirdParty/XliffTermTagger/termtagger-server.confand change the following line
#JAVA_CMD=java
to
JAVA_CMD=/usr/lib/jvm/java-8-oracle/bin/java
Attention: This should be the path to your Oracle Java, if you did follow the translate5 Ubuntu installation manual. If you did install your Java in another location, you have to customize the path accordingly.
By default translate5 uses only one termTagger instance running on port 9001. For better performance for big data you can use as many termTagger instances as you want with one translate5 instance. If you want to do that, please ask for help at translate5 mailing list.
By default one termTagger instance uses 2500 MB memory. If you want to decrease or increase that, open the file
/var/www/translate5/application/modules/editor/ThirdParty/XliffTermTagger/termtagger-server.confand change the following line
TERM_TAGGER_MEMORY_USAGE=2500M
to another value (2500M equals 2,5GB of main memory; value is per termTagger instance)
After that openTMStermTagger can be started as normal user, by calling the startServer script:
sudo -u www-data /var/www/translate5/application/modules/editor/ThirdParty/XliffTermTagger/startServer.sh
To stop the server call the stopServer script accordingly.
You can also create a init.d script to ensure that the openTMSTermTagger Server is started automatically.