How to create multiple translation projects based on Trados APIs by using many licenses at the same time to release concurrent cases

Hi,

I am a Trados user for SDL Trados 2019 and 2024 with licenses. I am writing automation exe based on Trados SDK API to make project automated.

When running the project, I find that in same time only one Trados License can be activated and only one Instance is running, for example, If two users want to create two translation projects at the same time, only one user can launch the Trados API-based exe, and the other user must be waiting for the license released.

So I WANT TO KNOW, How can I realize the cocurrent use? For example, I have 4 licenses, and It is possible for us to run 4 projects at the same time by calling the APIs.

Thansks,

Flavio

Parents
  • Hi  , 

    Trados Studio is fundamentally a desktop application, and the Studio APIs are intended for desktop automation scenarios, not for building a scalable server-style processing solution. The Project Automation API documentation also notes that FileBasedProject is not thread-safe and recommends using separate processes, not multiple threads, if you want to create projects simultaneously.

    So, while you may be able to run more than one automation process, running multiple Studio/API-based processes simultaneously on the same machine is not a scalable design pattern and may lead to issues, especially around license allocation/release. For standalone applications that use licensed Project Automation APIs, you must call LicenseManager.ReleaseLicense() when the process exits; otherwise the license can remain blocked for some time after execution ends.

    In short: Studio should be treated as a desktop solution for individual users, not as a multi-user automation server.

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

Reply
  • Hi  , 

    Trados Studio is fundamentally a desktop application, and the Studio APIs are intended for desktop automation scenarios, not for building a scalable server-style processing solution. The Project Automation API documentation also notes that FileBasedProject is not thread-safe and recommends using separate processes, not multiple threads, if you want to create projects simultaneously.

    So, while you may be able to run more than one automation process, running multiple Studio/API-based processes simultaneously on the same machine is not a scalable design pattern and may lead to issues, especially around license allocation/release. For standalone applications that use licensed Project Automation APIs, you must call LicenseManager.ReleaseLicense() when the process exits; otherwise the license can remain blocked for some time after execution ends.

    In short: Studio should be treated as a desktop solution for individual users, not as a multi-user automation server.

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

Children