Why do I consume a RRC Analyst and a RQM Professional License if I work in RTC (/ccm) only
We see a severe issue with license management in a CLM environment.
Example:
Example:
- A user has a RRC Analyst floating, a RTC Developer floating and a RQM professional floating license assigend.
- he connects to the CCM context root with the Web Client /ccm/web and logs in
- he works within CCM. He never goes into RRC nor into RQM
Problem:
Sometime the user borrows a RRC Analyst or a RQM Professional license. I do not know why.
Has anybody understood the mechanism behind the license borrow mechanism? I thought it's action depending, what kind of license I need. So which actions out of RTC needs licenses from other tools?
Accepted answer
Table 1 describes the license overview
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.jazz.repository.web.admin.doc%2Ftopics%2Fc_license_mgmt_over.html
Now an RRC Analyst is need when:
Now that said if the user is logging in new for the day, and only uses floating licenses, the floating license server might be randomly allocating the first license it finds that satisfies an action, for example say the user needs to create a work item, any of the 3 floating licenses satisfies this need so the license server could allocate say an Analyst CAL instead of the Developer CAL. It is only when Developer specific actions like source code access or build is needed will the Developer CAL be allocated instead.
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.jazz.repository.web.admin.doc%2Ftopics%2Fc_license_mgmt_over.html
Now an RRC Analyst is need when:
-
Creating requirements or collections
- Creating custom requirement types in the Requirements Management application
- Creating and editing project and artifact templates for requirements
- Creating and editing graphical requirements artifacts such as screen flows, user interface sketches, and use case diagrams
Now that said if the user is logging in new for the day, and only uses floating licenses, the floating license server might be randomly allocating the first license it finds that satisfies an action, for example say the user needs to create a work item, any of the 3 floating licenses satisfies this need so the license server could allocate say an Analyst CAL instead of the Developer CAL. It is only when Developer specific actions like source code access or build is needed will the Developer CAL be allocated instead.