Configuration of Allow/Block lists on ID based Floating server

Intro

Allow/Block (White/Black) lists on licensing Floating servers could be configured by using Named License Pools functionality.

Revenera documentation: Allocating Licenses Using Named License Pools

For configuration of Allow/Block lists, Floating server admin should define set of rules and describe them in specific model format. Model could be saved as txt file and uploaded to the server.

Materialise specifics for model definition

Host ID definition within model

Materialise is using string type of Host ID so Admin could use Host ID description with no type specified. Example of the syntax to be used

on hostid (
    "4BE23134-3FF0-3702-4DF9962901550A1DB5",
    "4BE23134-3FF0-4302-4DF9962901550A1DB5",
    "4BE23134-3FF0-3242-4DF9962901550A1DB5"
   )  

instead of

on hostid (
    "4BE23134-3FF0-3702-4DF9962901550A1DB5/STRING",
    "4BE23134-3FF0-4302-4DF9962901550A1DB5/STRING",
    "4BE23134-3FF0-3242-4DF9962901550A1DB5/STRING"
    )  `

Product definition within model

Materialise products contain multiple features. And, unfortunately, there is no option to configure rules on product level. All rules (partitions) should be defined on feature level. That mean that is Admin want to create specific rule for some product access than list of features should be added into particular partition.

1.  Block list
       1.  Entire block (Simple block list)  - Could be done on Host ID level
       2.  Partial block - Should be done on Feature level
2.  Whitelist
       1.  Allowed and any other available (reservation for user) - Should be done on Feature level
       2.  Only allowed - Should be done on Feature level

 

Use cases

-  For blocking access from particular HOST ID or Kicking of users from Floating server Simple Block list could be used. User will be kicked off from the server immediately after uploading of model with an appropriate block list to the server. 
- For providing access only for predefined list of HOST IDs Simple Allow List could be used.
- Other Use Case Examples from Revenera


# Upload model definition

- Upload the Model Definition via command line
- Upload the Model Definition Named via License Pools View on License Server Manager

 

# Reference for additional external documentation:

- FlexNet License Server Manager Guide
- Managing Named License Pools

Was this article helpful?

Can’t find what you’re looking for?

Our customer service team is happy to help!