ComposerIs it possible to serve TurboFloat licenses from different machines (IP addresses)? There are two cases, one is a different product from each machine, the other is the same product on different machines.The latter seems to not be possible, only one machine may be used to serve a given product (LimeLM version).However, in testing it seems that only one machine may be used to serve any and all TurboFloat licenses.Is that the case? Or is there a bug somewhere (hopefully, not in LimeLM)?
You can can multiple TurboFloat Server instance on the same machine provided they meet the following conditions:
1. They use different ports.2. They're serving license leases for different LimeLM product versions. (i.e. you can't have multiple instance serving license leases for the same product version on the same machine).
ComposerTrue, but one cannot have different machines running servers even if the products are different on each server. Correct?
I don't understand the question. A product key for a TurboFloat Server instance can only be activated on a single machine. That's by design. If you want to allow customers to mover the key to another computer you can choose to allow it: https://wyday.com/limelm/help/activations/#deactivate
ComposerAh, ok, not clear. What was meant was multiple products, each requiring a separate server, with each server potentially on a separate host computer. A user could launch one app using one server, and a second app when launched would access another server for authentication.
Each server could potentially be all on one machine, or potentially, the servers could be on separate machines. This could happen, for example, if one department of a large organization bought the first product for its production, while another department in the same company bought the second app, which uses a different GUID, and authenticates it using a server on a machine under its own control.
This way, multiple machines could end up serving different products. This would not necessarily be a problem until a worker from the first department needs to access the software that the second department in this example has a license for, or vice versa.
Initial tests of this scenario have been mixed, and it was a question whether this is a supported scenario.
>> "What was meant was multiple products, each requiring a separate server, with each server potentially on a separate host computer. A user could launch one app using one server, and a second app when launched would access another server for authentication."
Yes, that's supported out of the box.
>> "Initial tests of this scenario have been mixed, and it was a question whether this is a supported scenario."
Yes, this is fully supported. If you're having problem please let us know exactly what they are.
