Without there being a conflict when activating each license.
how to handle different # users for different featuresAnswered
Ok. My product has 3 key features. My client wants 2 floating licenses of feature A, 2 of feature B, and 5 users for feature C. They want a single server computer to handle the licensing. How can I set up multiple floating licenses on the same server?
Is it possible to set a single license code for 5 users and then check how many users are active when the user selects the features that have only 2 allowed users?
Answer
Hey Ann,
There's no way to split TurboFloat Server license leases in such a way *from a single server*.
Why? Because there's no way for the the requesting app to know if it “gets” the “A”, “B”, or “C” set of features. And it's a bad user-experience if they need “A” feature set and they get allocated “C”.
So, the solution is to have 3 separate TurboFloat Server instances. One serves licenses for “A”, one serves licenses for “B”, and once serves licenses for “C”.
This way, the user using your app can connect to the correct server and get the licenses they expect.
Does that make sense?
Yes. However, they are using an air gap server. If all features have same .dat file, can they install 3 licenses on the same server? I assume that they will need to create 3 separate folders and activate that way?
They don't want to use 3 different servers for the licensing
I have client side worked out. I need to provide the correct instructions to customer for activating 3 licenses on the same server. I assume that this is how?
I assume that a single running instance of TurboFloatServer.exe cannot hold two active keys simultaneously. To set this up without them fighting over the same files and ports, use this directory structure and configuration:
1. Duplicate the Folders
Create three entirely separate directories on your server. Copy the exact same .dat file and TurboFloatServer.exe into both.
- C:\TurboFloat\LicensePool_A\
- C:\TurboFloat\LicensePool_B\
- C:\TurboFloat\LicensePool_C\
2. Change the Port in the Second Config
An application bind error will occur if both instances try to use the default port.
- Open C:\TurboFloat\LicensePool_B\TurboFloatServer-config.xml.
- Change the <bind port="X" /> tag to a different port number (e.g., if Pool A uses 13, set Pool B to 14 or 1234, etc..
3. Activate and Isolate via Command Line
Because the .dat files have identical internal product GUIDs, you must use explicit flags when activating them. This forces each instance to keep its activation state separate, preventing them from overwriting each other's registry paths.
Open your command prompt as an Administrator and run:
For Pool A:
DOS
cd C:\TurboFloat\LicensePool_A
TurboFloatServer.exe -a="KEY-AAAA-AAAA-AAAA" -pdets="TurboActivate.dat" -config="TurboFloatServer-config.xml"
For Pool B:
DOS
cd C:\TurboFloat\LicensePool_B
TurboFloatServer.exe -a="KEY-BBBB-BBBB-BBBB" -pdets="TurboActivate.dat" -config="TurboFloatServer-config.xml"
For Pool C:
DOS
cd C:\TurboFloat\LicensePool_C
TurboFloatServer.exe -a="KEY-CCCC-CCCC-CCCC" -pdets="TurboActivate.dat" -config="TurboFloatServer-config.xml"
4. Running them as Services
If you install them as Windows services (-i flag), ensure you point the service arguments directly to their respective directories so the Windows Service Manager knows they are completely distinct processes.