Strange behaviour occurs on JTS license server.
This JTS is configured as a floating license server which has been used by local registered users(l_users) and also shared by users(r_users) who are managed by another JTS server. Rhapsody DM application are running above JTS.
The license server should function well as users from a separated JTS have no problem to request and check out a free license from the server with any user operation.
But there are some strange phenomenon occurs to local users(l_users).
When l_users performing some operations like creating OSLC links or project areas, there's no permission error occurs which means floating license could be successfully checked out from the server.
But when l_user performing other operations like importing model or creating review, permission would be denied and it's looked like the license server is refused to grant a free license to the client.
Above behaviour is strange, as l_users was only assigned with Rhapsody Design Manager floating license which is the highest level of RDM license type. Any user operation done on RDM should be all permitted with the highest permission of license.
We didn't see any problematic info from the JTS admin page, every settings verified from the web client looks good.
(1) Is that possible the license info stored in the dabebase@JTS for l_users was wrong?
(2) How to check what kind of license or license related info directly from Derby database?
(3) How to explain the above phenomenon. Notice l_users has been granted with full project roles/permissions already.
Has been stuck in this issue for nearly 2 months, you any idea and hints would be highly appreciated.
Best Regards
One answer
Creating a project area or creating OSLC links is using repository permissions.
When the user attempts the operations for importing a model etc, this would use the CAL. Does the error say there are no licenses to check out? If so, then they may all be consumed.
With regards to your questions:
When the user attempts the operations for importing a model etc, this would use the CAL. Does the error say there are no licenses to check out? If so, then they may all be consumed.
With regards to your questions:
(1) Is that possible the license info stored in the dabebase@JTS for l_users was wrong?
I highly doubt it since we have not seen any defects here in some time.
I highly doubt it since we have not seen any defects here in some time.
(2) How to check what kind of license or license related info directly from Derby database?
We don't typically recommend accessing the DB directly for this information.
We don't typically recommend accessing the DB directly for this information.
(3) How to explain the above phenomenon. Notice l_users has been granted with full project roles/permissions already.
I would check the log files for JTS, you can also run a floating licenses usage report and determine if you are running out of licenses.
I would check the log files for JTS, you can also run a floating licenses usage report and determine if you are running out of licenses.