Isotropix Forums

So the situation is that we have a number of floating educational licenses and are deploying the Clarisse 4.0 client to Linux (Centos 7) initially in a thin client run from network configuration.

The client launches fine from workstations, however despite defining the ILISE_SERVER environment variable it pops up with "Cannot find the license key file" dialog, with options to open the license manager or run as PLE. Using the licman interface to select floating license and providing the address of the license server works, however we can't expect end users to do this. Not sure if it's relevant, but the License Type is initially set to Node Locked in the interface, so not sure if the env variable is being ignored because it also needs to be told that this is a Floating Remote type?

Any thoughts on how we can implement this correctly? Ideally without using the command-line license server option, or providing a preconfigured config file (since that would need to be deployed to every user account).

Hi!

Indeed, since 4.0 SP1 setting the environment variable ILISE_SERVER no longers forces the license mode to "floating".
And by default floating mode is set to "nodelocked".
Check the "Licensing" section in the 4.0 SP1 release notes for more details.

Without using the command line you can do this:
- edit the file $HOME/.isotropix/Clarisse/<version>/clarisse.env and set ILISE_SERVER=<server_name>[:<port>]
- edit the file $HOME/.isotropix/Clarisse/<version>/clarisse.cfg and find the line that says "floating_license XXX" and set it to "floating_license yes" or add it if missing.

You could, for example, do one install on one machine, configure the files and check that works as expected and uses the correct license server. Then you could copy the edited files clarisse.env and clarisse.cfg on all the user machines.
This is not very convenient I confess.

Using the command line would be straight forward with the following command:

Code: Select all

./clarisse -license_server <server_name>[:<server_port>]

Using the above command line you could create an executable bash script and then make a desktop shortcut to it, for example:

bash code

#!/bin/bash
<full_path_to_clarisse> -license_server <server_name>[:<server_port>]

Let us know if this works for you.

Cheers,

Hi Anthony, thanks for the quick comprehensive response. I must confess I didn't think to check the release notes for the version itself, was just going by the main documentation. But your post gave me everything I needed and is much appreciated.

In this case out of the available options, I definitely didn't want to go any route that involved distributing config files anywhere. So the best way for us was to put an override for our menu system that redirects it to run a clarisse_launcher script based on your example

bash code

#!/bin/bash
exec clarisse -license_server

to force it into floating mode, and then pick up the server address already defined in the environment variable.

Assuming this change is intentional, is it possible to add a second environment variable such as ILISE_LICENSE_TYPE=floating to allow launching directly from the main exe? We use the Modules environment system to pass dedicated variables per application, and it would be great to have this ability if the presence of the ILISE_SERVER variable will no longer be used to define the mode as floating.

But either way we're up and running now, thanks again for the quick assist.

Cheers,

That's a pretty good idea to have a CLARISSE_LICENSE_TYPE environment variable

Glad it worked, and good idea about CLARISSE_LICENSE_TYPE.

Any updates on the CLARISSE_LICENSE_TYPE implementation?

It is terribly inconvenient not to use environment variables in our Clarisse deployment.

Thank you

Hi,

This feature hasn't been added yet. There's no target version yet, but we'll keep you posted when we have more information.
For reference, the feature ID is #9629.

Regards,

Good news, the feature has been released in 4.0 SP5!
The variables are IX_LICENSE_TYPE and IX_LICENSE_FILE. Check the release note for usage details.

Thank you, I will try it