Co-existence for node locked and Floating features

[sreeramanikode]

We recently purchased a floating license with 5 features from OPENECU Vendor. Say the features are A, B, C, D and E

The flexlm server has been hosted and is working as expected for all users who needs all of the features A through E.

In our organization there are few users have node locked license from the same vendor for Features excluding E

How do we setup the users who already have nodelocked licenses from A -D from checking out them from the server.

What should be vendor.lic file look like.

[jberthold · Accepted solution]

Hi @sreeramanikode ,

You can use the license server Options file with the Exclude keyword to prevent the named users with nodelocked licenses from checking out Features A-D.  

 

The Options File is described in Chapter 13 of the License Server Admin Guide.  The current version is here : https://docs.revenera.com/fnp/2023r2/pdf/fnp_LicAdmin.pdf

Best regards,

Jim

 

@sreeramanikode

[jberthold · Accepted solution]

Hi @sreeramanikode ,

You can use the license server Options file with the Exclude keyword to prevent the named users with nodelocked licenses from checking out Features A-D.  

 

The Options File is described in Chapter 13 of the License Server Admin Guide.  The current version is here : https://docs.revenera.com/fnp/2023r2/pdf/fnp_LicAdmin.pdf

Best regards,

Jim

 

@sreeramanikode

[sreeramanikode]

We tried doing that, but the client is always trying to check out all the features from the server and the enduser is unable to use the local-node-locked-licensed features

This is an example of how our user side license file looks

SERVER SEVERNAME 27000 VENDOR vendorname PORT=1290

INCREMENT FEATURE1 vendorname ver expiry uncounted\
.......

INCREMENT FEATURE2 vendorname ver expiry uncounted\
.......

INCREMENT FEATURE3 vendorname ver expiry uncounted\
.......

INCREMENT FEATURE4 vendorname ver expiry uncounted\
.......

[sreeramanikode · Accepted solution]

To conclude the question

Configure your server as mentioned in the license administration guide and on the USER side

Add the licensing file to the environment variables so like
vendor_license_file=path-to-license-file.lic

User's licensing file must look as below

#First line
SERVER SEVERNAME 27000 VENDOR vendorname PORT=1290

INCREMENT FEATURE1 vendorname ver expiry uncounted\
.......

INCREMENT FEATURE2 vendorname ver expiry uncounted\
.......

INCREMENT FEATURE3 vendorname ver expiry uncounted\
.......

INCREMENT FEATURE4 vendorname ver expiry uncounted\
.......



TO-NOTE: Warn users not to have "USE_SERVER" in their file

[jberthold]

Hi @sreeramanikode ,

You have the ability to control the order in which the nodelocked/floating licenses are acquired.   Please refer to "Setting the License Search Path Using an Environment Variable" in the license admin guide.   You will want to specify the location of the local nodelocked licenses first followed by the license server.

Best regards,

Jim