Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Floating license server restrict access

In RQM 2.0 is there a way to stop someone from connecting to a floating license server that is setup on an RQM instance from another RQM instance? In other words I would like to restrict people from installing there own RQM server instance and be able to connect to a main floating license server within the same domain

Thanks,

Chris

0 votes



3 answers

Permanent link
Is what you would like to see a way for a license server to have to
"accept" an RQM server, similar to the way one Jazz server has to accept
another Jazz server as a "friend" (for C/ALM cross repository link support)?

Just for interest's sake, could you say a bit more about why you want to
prevent this? In the floating license server, you can specify what
users are allowed to use a floating license. So you can control who can
use a floating license. If you have given someone permission to use an
RQM floating license, why do you care what RQM server they are using?

Cheers,
Geoff

cthompson116 wrote:
In RQM 2.0 is there a way to stop someone from connecting to a
floating license server that is setup on an RQM instance from another
RQM instance? In other words I would like to restrict people from
installing there own RQM server instance and be able to connect to a
main floating license server.

Thanks,

Chris

0 votes


Permanent link
Actually, I need to correct my statement below. You cannot specify in
the license server what users are allowed to use a floating license ...
that is done in the Jazz Team Server. So I understand your request.
I've filed work item 110052 requesting this functionality:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/110052

Please feel free to review this work item and verify that I've captured
your requirement correctly.

Cheers,
Geoff

Geoffrey Clemm wrote:
Is what you would like to see a way for a license server to have to
"accept" an RQM server, similar to the way one Jazz server has to accept
another Jazz server as a "friend" (for C/ALM cross repository link
support)?

Just for interest's sake, could you say a bit more about why you want to
prevent this? In the floating license server, you can specify what
users are allowed to use a floating license. So you can control who can
use a floating license. If you have given someone permission to use an
RQM floating license, why do you care what RQM server they are using?

Cheers,
Geoff

cthompson116 wrote:
In RQM 2.0 is there a way to stop someone from connecting to a
floating license server that is setup on an RQM instance from another
RQM instance? In other words I would like to restrict people from
installing there own RQM server instance and be able to connect to a
main floating license server.

Thanks,

Chris

0 votes


Permanent link
Thats it. Thank you sir

Chris

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Mar 25 '10, 12:52 p.m.

Question was seen: 5,416 times

Last updated: Mar 25 '10, 12:52 p.m.

Confirmation Cancel Confirm