Salesforce

WorldServer - in a non-live TM environment, uploading a Return package from Trados Studio updates the Translation Memory

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Trados Studio
Symptoms/Context
When we upload Return packages to our WorldServer non-live TM environment directly (via server connection), sporadically the TM gets updated. More precisely: the first upload does not update the TM. In fact, the Task History on the User Interface confirms this with an entry like:

Imported asset(s) from Trados Studio. Translation Memory was not updated.

However, when we import the Return package a second time, for instance after making some changes to the translation, the new import does update the TM. In fact, after the import, we can see this message in the User Interface

Imported asset(s) from Trados Studio. Translation Memory "TM_NAME" was updated.

When checking the relevant TM, we can see that it has indeed been updated with the translation from the second Return package import. This issue does not happen when creating local WorldServer Return packages and uploading/importing them manually into WorldServer, making sure that the option Update the translation memory using imported assets is not selected.

Why is the TM getting updated when uploading from Trados Studio and how can this be avoided?
Resolution
This issue happens when on the server, the tm.properties file containing the setting that sets the environment as non-live TM

enable_live_translation_memory = false

is set under WS_CONFIG/ws-legacy only. By doing so, the setting is not set under the other subfolders WS_CONFIG/ws and WS_CONFIG/ws-api.

To avoid this issue, place the tm.properties file under the "parent" folder WS_CONFIG only. By doing so, its settings will be inherited by all the other subfolders (components) ws-legacy, ws and ws-api. There is no need to copy the tm.properties to the 3 subfolders once it is present under WS_CONFIG.

If you work in a clustered environment, make sure to apply these settings on all servers where the Idiom Service is running. 
Restart the Idiom service for the change to take effect. after this change, Return packages uploaded from Trados Studio will no longer update the TM in a non-live TM environment.

 
Root Cause
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by