This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Operations
- :
- FlexNet Operations Knowledge Base
- :
- Best Practices for the CLS instances which are not in use
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Best Practices for the CLS instances which are not in use
Best Practices for the CLS instances which are not in use
Question
What are the best practices for the CLS instances which are no longer in use by any client but still present in FlexNet Operations (FNO).
Answer
One can follow either of below for the redundant CLS instances:
1) Obsolete the CLS instance can be done through webservices (ManageDeviceService, obsoleteHostRequest call) or UI
- The server id will be renamed with suffix to original ID(ex: WS2UFY6GDXXX-OBSOLETE-20230618213543).
- This will remove the licenses mapped and return the count back to the line item pool
- You can still see the history of the server in FNO UI.
- Details of the linked served devices in FNO UI until it makes call to new CLS.
- Cannot call CLS APIs for the obsoleted server as it gets deleted from the CLS database.
2) Deleting the Server(CLS) has to be done using webservices. (ManageDeviceService, deleteDeviceRequest call)
- This will remove the licenses mapped and return the count back to the line item pool.
- You cannot see the previous transaction history nor the served device details. The CLS and its related records are deleted from FNO and CLS database.
- Unless there is a need to retain the unused CLS instances details and it's history, we recommend to delete the instance which keeps the database less bulky.
No ratings