Page tree
Skip to end of metadata
Go to start of metadata

For this setup we recommend using a server, that has at least 4 CPUs available for usage by translate5 and its dependencies.

This setup is the default setup, if you do not change anything to a default translate5 installation.

Why this setup is recommended

This setup sets up 3 TermTagger instances.

2 of these instances are reserved for imports (tagging terms during the import in translate5) and 1 is reserved for tagging terms while saving segments through the GUI by users.

This setup ensures, that

  • the import is faster, because 2 TermTagger do the work instead of one
  • saving of segments in the GUI is not slowed down by running imports

How to setup this set up

Edit your termTagger configuration, which you find in

 /application/modules/editor/ThirdParty/XliffTermTagger/termtagger-server.conf

Ensure, that in this file the following line exists and is NOT commented out:

SERVERS=("http://localhost:9001" "http://localhost:9002" "http://localhost:9003")

Configure translate5 to use 2 termTaggers for imports and one for the GUI by executing the following SQL on your translate5 database

UPDATE `Zf_configuration` SET` value` = '["http://localhost:9001", "http://localhost:9002"]' WHERE `Zf_configuration`.`name` = 'runtimeOptions.termTagger.url.default';
UPDATE `Zf_configuration` SET` value` = '["http://localhost:9001", "http://localhost:9002"]' WHERE `Zf_configuration`.`name` = 'runtimeOptions.termTagger.url.import';
UPDATE `Zf_configuration` SET` value` = '["http://localhost:9003"]' WHERE `Zf_configuration`.`name` = 'runtimeOptions.termTagger.url.gui';

Restart your termTagger, if you run termTagger as a service.

  • No labels