Permissions needed to run RFT Adapter in RQM

Hi,
Can someone detail specifically what permissions are needed to run the RFT adapter in RQM?
I have the two permissions identified in RQM for the Adapter:
1-Register Tool Adapter
2-Save Adapter Request
however I am not able to connect successfully. The RFT Adapter constantly reconnects and cycles this without ever connecting nor generating an error.
In RQM, the machine name is seen in the Adapter console but it has a red box stating it is unhealthy.
Can someone detail specifically what permissions are needed to run the RFT adapter in RQM?
I have the two permissions identified in RQM for the Adapter:
1-Register Tool Adapter
2-Save Adapter Request
however I am not able to connect successfully. The RFT Adapter constantly reconnects and cycles this without ever connecting nor generating an error.
In RQM, the machine name is seen in the Adapter console but it has a red box stating it is unhealthy.
2 answers

Hi, I have been using RFT and RQM as administrator and haven't have an issue with permission. Also, you might wanna check your firewall settings two allow RFT communicates with RQM if they are not on the same machine.
Hi,
Can someone detail specifically what permissions are needed to run the RFT adapter in RQM?
I have the two permissions identified in RQM for the Adapter:
1-Register Tool Adapter
2-Save Adapter Request
however I am not able to connect successfully. The RFT Adapter constantly reconnects and cycles this without ever connecting nor generating an error.
In RQM, the machine name is seen in the Adapter console but it has a red box stating it is unhealthy.

I'm unaware of the minimum set of permissions needed to run an adapter. But I'm sure it's a lot more than the 2 you listed. The adapter needs to be able to save lab resource (during registration it creates a machine), save execution results and several other permissions. Also this is tricky because it depends on how you use the adapter. For example, if you also use the adapter to run test cases inside a test suite, then it will need to have test suite related permissions. Of if used in Execution Schedules, it will need additional permissions.
This isn't the first time I've heard this question and I would recommend that you open an enhancement request against RQM to provide an adapter role out-of-box, that defines such minimum set. The dev team has some ideas on defining this role, but this is also just as much a test effort to ensure we properly cover all scenarios. Here's the link to open this request:
http://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.newWorkItem
In the mean time you can simply define a role to be used that pretty much has all permissions, but only assign the user(s) you plan to use when configuring the adapter. These users should have a Connector Client Access License (not QM license). This will prevent them from logging into the RQM UI.
This isn't the first time I've heard this question and I would recommend that you open an enhancement request against RQM to provide an adapter role out-of-box, that defines such minimum set. The dev team has some ideas on defining this role, but this is also just as much a test effort to ensure we properly cover all scenarios. Here's the link to open this request:
http://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.newWorkItem
In the mean time you can simply define a role to be used that pretty much has all permissions, but only assign the user(s) you plan to use when configuring the adapter. These users should have a Connector Client Access License (not QM license). This will prevent them from logging into the RQM UI.