Altova desktop products
There are three types of desktop user licenses:
|•||Installed: Each license is for a specified number of computers. For example, if you purchase a 10-Installed license, you may install and use the software on up to 10 computers.|
|•||Concurrent-User: A license for n concurrent users allows: (i) installation on 10n computers; (ii) up to n users to use the software concurrently at any given time. For example, if you purchase a 20-Concurrent-User license, then the software may be installed on up to 200 computers and used on up to 20 computers at any given time.|
|•||Named-User: A Named-User license authorizes a specified number of users to use the software.|
|Note:||In the case of Installed licenses and Concurrent-User licenses, LicenseServer uses the hostname or IP address of a machine to assign licenses and keep count of assigned licenses. See Network Information for details of the client identification process.|
|Note:||When the software is registered with LicenseServer, the User Principal Name (UPN) of the user who registered the software is also registered (together with other registration data). Named User licenses are assigned to UPNs. If a UPN receives a license, then the user having this UPN can log in with this UPN to any machine on the network and use the software. With this license, therefore, a user can work on different computers in the network (including in virtual environments), by logging in with his or her UPN. See Network Information for details of the client identification process.|
List of Altova desktop products
Authentic Desktop, DatabaseSpy, DiffDog, MapForce, SchemaAgent, StyleVision, UModel, XMLSpy.
Altova MissionKit licenses
Altova MissionKit is a suite of Altova desktop products. An Altova MissionKit license comprises individual licenses for each of the desktop products in the MissionKit suite. Each of these individual product licenses has a different and unique key code, but the same MissionKit Bundle ID. If you upload an Altova MissionKit license to the license pool, then the individual product licenses are listed in the License Pool (with the Altova MissionKit logo next to each license). If you assign any one of these product licenses to a particular client (machine or named user), then all the other products of that MisisonKit bundle are also assigned to that client. As a result, no other product in that particular MissionKit bundle can be assigned to another client. Of course, if the MissionKit license allows multiple clients, then each client is licensed to use one set of MissionKit products.
List of Altova MissionKit products
DatabaseSpy, DiffDog, MapForce, SchemaAgent, StyleVision, UModel, XMLSpy.
Altova server products
All server product licenses are licensed on the basis of the physical cores of the computer on which the server software is installed.
|•||Each license specifies the number of cores that are licensed|
|•||If the server product is installed on a computer with n number of cores, then the license must authorize n or more cores. For example, if RaptorXML Server is installed on a computer with 8 cores, then the RaptorXML Server license must authorize 8 or more cores.|
|•||Licenses can be combined to reach the required core count. For example, if RaptorXML Server is installed on a computer with 8 cores, then two RaptorXML Server licenses, each with a core count of 4, can be used.|
|Note:||In order to run an Altova server product on a virtual machine: (i) the virtual machine must have a stable IP address or hostname so that it is uniquely identifiable, and (ii) the Altova server product must be licensed for—at a minimum—the number of virtual processors assigned to the virtual machine by the hosting machine.|
List of Altova server products
DiffDog Server, FlowForce Server, MapForce Server, MobileTogether Server, RaptorXML(+XBRL) Server, StyleVision Server.
When to use different LicenseServers
The license pool of a LicenseServer can contain either:
|•||Group 1 licenses: Installed licenses and/or Concurrent-User licenses, or|
|•||Group 2 licenses: Named-User licenses|
If you wish to use licenses from both groups, then you must use a separate LicenseServer for each group. If LicenseServer detects a situation in which licenses from both groups would be present in the license pool, it will prompt you about this and recommend appropriate steps (typically, to move one group of licenses to a separate LicenseServer that will be dedicated to this group).
Highly recommended: separate LicenseServers for separate license types
It is best to use a separate LicenseServer for each of the three license types. This would ensure that an end user, when connected to the appropriate LicenseServer: (i) sees only licenses of the type relevant to that client, and (ii) therefore acquires a license of the correct type.
When to re-register products
When upgrading from a LicenseServer version earlier than 3.0 to LicenseServer 3.0 or later, an older product registration in the license pool might be found to be incompatible with the new registration format (introduced with version 3.0). If this happens, then the older product registration will need to be removed and the product will need to be re-registered. LicenseServer will inform you about this in a message and will prompt you to take the required steps.
© 2019 Altova GmbH