SDL Trados GroupShare 2017, MultiTerm Server
The license enforcement code itself, and therefore its logic, resides within the SDL Trados GroupShare Application Service. The following parameters are evaluated within the license enforcement code.
- Expiration Date: At each login the license expiry date is checked. This overrules any of the checks below - if an expiry date has passed, the feature set of SDL Trados GroupShare is no longer fully available.
- MultiTerm Online: Upon login, the server checks whether requests coming from SDL MultiTerm Online are allowed based on the active license.
- Number of concurrent MultiTerm Editor and MultiTerm Viewer access licenses: Upon login to MultiTerm Server, it checks whether an additional user is allowed to login. If not, the login fails and the message "Too Many Concurrent Users" is displayed.
- On logging in, each user checks out a Viewer license by default. This license stays checked out until the application is closed, or the user changes to an editor license.
- If a user wants to edit data, they need to have application rights to do so. If that is the case, the server checks out an Editor license, and checks in their Viewer license.
If somebody is editing data within MultiTerm Desktop or any other client application they are always and immediately checking out an Editor license, even when they decide to discard the changes and cancel the editing action. - The maximum number of users that can log in is the combined number of MultiTerm Viewer and Editor seats.
- If somebody wants to edit or add data, but the maximum number of concurrent MultiTerm Editor access licenses has already been reached, the edit action is denied and a message displayed.
- If a user attempts to log in, and no viewer licenses are available, then, if available, an Editor license will be checked out instead.
Web client's counting logic: Each login from MultiTerm Online is treated as one checked out license - even if more than one browser is running simultaneously on the same client machine. It is released again ("checked in") either by clicking the Logout button or after 5 minutes of inactivity.
Rich clients' counting logic: Non-web based logins from one machine (session) only check out one licence - even if more than one instance of the same application is accessing the server. A license like this is checked in after the last instance of the same application that is accessing the server is closed. In case of connection loss, the license is release after 5 minutes. All connections from the same machine (session) and the same application have the same quality - for example, if one connection checked out an Editor licence, all other connections from the same application share this immediately and do not check out further licenses.
If you use two different applications (e.g. Studio and MultiTerm Desktop), you will use a license for each application, rather than just one shared among all applications.
SDL Studio GroupShare 2011 to 2015, MultiTerm Server
The license enforcement code itself, and therefore its logic, resides within the MultiTerm Server's Application Service. The following parameters are evaluated within the license enforcement code.
- Expiration Date: At each login the license expiry date is checked. This overrules any of the checks below - if an expiry date has passed, MultiTerm Server no longer runs.
- MultiTerm Online: Upon login, the server checks whether requests coming from SDL MultiTerm Online are enabled.
- Number of concurrent MultiTerm Editor and MultiTerm Viewer access licenses: Upon login MultiTerm Server checks whether an additional user is allowed to login. If not, the login fails and a message is displayed.
- On logging in, each user checks out a Viewer license by default. This license stays checked out until the application is closed, or the user changes to an editor license.
- If a user wants to edit data, they need to have application rights to do so. If that is the case, the server checks out an Editor license, and checks in their Viewer license.
If somebody is editing data within MultiTerm Desktop or any other client application they are always and immediately checking out an Editor license, even when they decide to discard the changes and cancel the editing action. - The maximum number of users that can log in is the combined number of MultiTerm Viewer and Editor seats.
- If somebody wants to edit or add data, but the maximum number of concurrent MultiTerm Editor access licenses has already been reached, the edit action is denied and a message displayed.
- If a user attempts to log in, and no viewer licenses are available, MultiTerm Server will determine if the user logging in has any editing rights on any termbases. If this is the case, then an Editor license will be checked out instead.
Super User account: The super account is installed by default and cannot be deleted. It does not use any Viewer or Editor access licenses, so logins via the Super User account are not counted. Whereas other accounts such as guest can be shared, the Super User account cannot be shared. You cannot log in from MultiTerm Online with the Super User account. Only one Super User account is able to log in at any one time. If the Super User is already logged in on a single machine, then attempting to log in with the Super User account on a different machine will result in an the log-in being denied. If an attempt is made to login with the Super User again from the same machine, then the other Super User login will be automatically disconnected and a new session created.
It is recommended to change the account's default password immediately after installation. The Super User account should only be used to create other administrative users. All further logins requiring administrative rights should use one of these user accounts.
Guest account: The guest account is installed by default and cannot be deleted. Otherwise it is a normal user account with no special rights or restrictions.
It is recommended to change this account's default password immediately after installation.
Web client's counting logic: Each login from MultiTerm Online is treated as one checked out license - even if more than one browser is running simultaneously on the same client machine. It is released again ("checked in") either by clicking the Logout button or after the set time-out period of inactivity.
Rich clients' counting logic: Non-web based logins from one machine only check out one licence - even if more than one instance of the same application is accessing the server. A licence like this is checked in after the last instance of the same application that is accessing the server is closed. All connections from the same machine and the same application have the same quality - for example, if one connection checked out an Editor licence, all other connections from the same application share this immediately and do not check out further licenses.
If you use two different applications (e.g. Studio and MultiTerm Desktop), you will use a license for each application, rather than just one shared among all applications.
MultiTerm Server iX 6.2 to MultiTerm 2009 SP3
The license enforcement code itself, and therefore its logic, resides within the MultiTerm Server's so-called SDL MultiTerm Database Service. The following parameters are evaluated within the license enforcement code.
- Expiration Date: At each login the license expiry date is checked. Technically, it is actually the FLEXlm application that checks whether the licence certificate has expired or not.
This overrules any of the checks below - if an expiry date has passed, MultiTerm Server no longer runs. - MultiTerm Online: Upon login FLEXlm checks whether requests coming from SDL MultiTerm Online are enabled.
- MultiTerm Anywhere: Upon login FLEXlm checks whether requests coming from SDL MultiTerm Anywhere are enabled.
- Number of concurrent MultiTerm Editor and MultiTerm Viewer access licences: Upon login FLEXlm checks whether an additional user is allowed to login. If not, the login fails and a message is displayed.
- On logging in, each user checks out a Viewer license by default. This licence stays checked out until the application is closed.
- If a user wants to edit data, FLEXlm verifies whether they have application rights to do so, and - if successful - additionally checks out an Editor license.
If somebody is editing data within MultiTerm Desktop or any other client application they are always and immediately checking out an Editor license, even when they decide to discard the changes and cancel the editing action.
This Editor license stays checked out until the application is closed. - The maximum number of users that can check out Viewer licences - i.e., maximum number of users that can log in - is the sum of licenced MultiTerm Viewer plus MultiTerm Editor seats.
- If somebody wants to edit or add data, but the maximum number of concurrent MultiTerm Editor access licences has already been reached, the edit action is denied and a message displayed.
Super user account: The Super User account does not use any Viewer or Editor access licences, so logins via the superuser account are not counted. Whereas other accounts such as guest can be shared, the superuser account cannot be shared.
Web client's counting logic: Each login from MultiTerm Online is treated as one checked out licence - even if more than one browser is running simultaneously on the same client machine. It is released again ("checked in") either by clicking the Logout button or after the set time-out period of inactivity.
Rich clients' counting logic: Non-web based logins from one machine only check out one licence - even if more than one instance of the same application is accessing the server. A licence like this is checked in after the last instance of the same application that is accessing the server is closed. All connections from the same machine and the same application have the same quality - for example, if one connection checked out an Editor licence, all other connections from the same application share this immediately and do not check out further licenses.
If you use two different applications (e.g. Studio and MultiTerm Desktop), you will use a license for each application, rather than just one shared among all applications.
Technically, FLEXlm/MultiTerm Server also evaluates the items below. They are usually set to unlimited.
- Maximum Number of Termbases: During the creation of a new termbase, FLEXlm checks whether an additional termbase can be added.
This is usually unlimited. - Maximum Number of Indexes: During the creation and modification of a termbase, FLEXlm checks whether an additional index/language can be added.
This is usually unlimited. - Maximum Number of Hits/Day and Hits/Year: FLEXlm checks whether the amount of hits per day and/or hits per year has been exceeded. If so, a warning message is displayed. MultiTerm Server still continues to run.
This is usually unlimited.
Extract from a sample license file:
The code below is a condensed extract of the key information in a MultiTerm Server licence file - for example, MultiTerm Server with MultiTerm Online and Anywhere, for 2 MultiTerm Viewers and 1 MultiTerm Editor licenses.
SERVER work0265 000ae651c891
VENDOR trados
USE_SERVER
INCREMENT mtseditors trados 6.0 permanent 1
INCREMENT mtserver trados 6.0 permanent 1 VENDOR_STRING=<...>,mtsonline=1,mtsanywhere=1
INCREMENT mtstotalusers trados 6.0 permanent 3
- Line 1
SERVER ... specifies that this license file is being used on a server work0265 with Ethernet ID 000ae651c891. - Line 2
VENDOR ... specifies that this license file is being served by the vendor daemon trados and not by any other company that also uses FLEXlm technology. - Line 3
USE_SERVER just specifies that server license hosting overrides any client-side, node-locked licence files. - Line 4
INCREMENT mtseditors ... specifies that the amount of MultiTerm Editor seats (mtseditors) for vendor trados of the licensed version 6.0 equals 1; permanent means that a license never expires. - Line 5
INCREMENT mtserver ... specifies that the amount of MultiTerm Servers (mtserver) for vendor trados of licensed version 6.0 equals 1. The VENDOR string line further specifies that the mtserver is further equipped with MultiTerm Online (mtsonline=1) and MultiTerm Anywhere (mtsanywhere=1). - Line 6
INCREMENT mtstotalusers ... specifies that the amount of total users/logins (mtstotalusers) for vendor trados of the licensed version 6.0 equals 3. - Lines 4 and 6 work together: The number of distinct MultiTerm Viewer licenses is the subtraction of
mtstotalusers minus mtseditors, in other words - the sum of MultiTerm Editor access licenses plus MultiTerm Viewer access licences constitute the value of the mtstotalusers line.
Usually a license file sees more than one line of a given feature (for example, when somebody ordered additional licences later). In this situation, FLEXlm adds sums up all licences.
SDL MultiTerm Server 2011
You view the details of a license by starting the MultiTerm Server Console on the server. Click on the Environment node, and then on the Show License Console button.
