Page History

...

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.

...

#JAVA_CMD=java

 to the location of the java 8, that you installed with the prerequisites . If you are using Ubuntu 18.04, the path should be as follows:

JAVA_CMD=/usr/lib/jvm/java-1.8.0-openjdk-oracleamd64/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 listopen the

/var/www/translate5/application/modules/editor/ThirdParty/XliffTermTagger/termtagger-server.conf

file and configure more termTagger instances, as shown there. Then

• open the Zf_configuration table of your translate5 instance
• open the rows, where the column "name" has the values "runtimeOptions.termTagger.url.default", "runtimeOptions.termTagger.url.import" and "runtimeOptions.termTagger.url.gui" and set the column "value" to the URLs of your termTagger instances, as explained in the column "description" of the according row.

By default one termTagger instance uses 2500 MB memory. If you want to decrease or increase that, open the file 

...

 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:

...