RFT 8.2.0.1 adapter fails to remain connected to RQM 3.0.1
We have installed RQM3.0.1 and are trying to integrate it with RFT 8.2.0.1.
The adapter launches, connects with RQM (the adapter console shows the adapter with good health). Then after a few seconds the adapter console window continually states "Reconnecting to the server " and the adapter console shows the adapter as unresponsive.
I have deleted RQMAdapterOptions.pref and rqmadapter.ini.
The connecting user has Quality Professional CAL (and JazzAdmins permissions)
The connecting user is a member of the project area (and has a Test Team Member process role)
I then tried the command line adapter to see if it might work or shed some light on what is going wrong (I couldn't get the RFT adapter logging to work). Same results regarding RQM - it initially connects but then fails after a short period of time. The output from CommandLineAdapter.log is below.
11:03:17,826 INFO com.ibm.rqm.adapter.commandline - Adapter is reconnecting. Using saved configuration information from Config.ini
11:03:18,366 INFO com.ibm.rqm.adapter.library - Successfully created an HTTP client
11:03:19,226 INFO com.ibm.rqm.adapter.library - The adapter is now connected
11:03:27,619 WARN com.ibm.rqm.adapter.commandline - Failed to save configuration file for the command line adapter
11:03:27,619 DEBUG com.ibm.rqm.adapter.commandline - com.ibm.rqm.adapter.library.data.AdapterException: Failed to retrieve adapter information
11:03:27,629 INFO com.ibm.rqm.adapter.commandline - Created Command Line Adapter
11:03:27,629 DEBUG com.ibm.rqm.adapter.library - Adapter polling RQM server for instructions.
11:03:28,039 INFO com.ibm.rqm.adapter.library - Stored configuration is out of sync. Adapter is re-registering.
11:03:28,989 DEBUG com.ibm.rqm.adapter.library - Adapter process going for sleep for: 5 seconds.
11:03:33,991 DEBUG com.ibm.rqm.adapter.library - Adapter polling RQM server for instructions.
11:03:34,401 INFO com.ibm.rqm.adapter.library - Stored configuration is out of sync. Adapter is re-registering.
11:03:35,331 DEBUG com.ibm.rqm.adapter.library - Adapter process going for sleep for: 5 seconds.
11:03:40,343 DEBUG com.ibm.rqm.adapter.library - Adapter polling RQM server for instructions.
11:03:40,943 INFO com.ibm.rqm.adapter.library - Stored configuration is out of sync. Adapter is re-registering.
11:03:41,874 DEBUG com.ibm.rqm.adapter.library - Adapter process going for sleep for: 5 seconds.
11:03:46,875 DEBUG com.ibm.rqm.adapter.library - Adapter polling RQM server for instructions.
and so on...
Environment
Client: Window XP SP3
RFT 8.2.0.1
Server: RHEL 5.5/DB2 9.7
RQM 3.0.1
Our RQM instance resides on the cloud. The RFT adapters require a proxy to access it. We achieve this by using cntlm to tunnel to the cloud.
This all worked with RQM v2.
Any ideas what is going wrong?
The adapter launches, connects with RQM (the adapter console shows the adapter with good health). Then after a few seconds the adapter console window continually states "
I have deleted RQMAdapterOptions.pref and rqmadapter.ini.
The connecting user has Quality Professional CAL (and JazzAdmins permissions)
The connecting user is a member of the project area (and has a Test Team Member process role)
I then tried the command line adapter to see if it might work or shed some light on what is going wrong (I couldn't get the RFT adapter logging to work). Same results regarding RQM - it initially connects but then fails after a short period of time. The output from CommandLineAdapter.log is below.
11:03:17,826 INFO com.ibm.rqm.adapter.commandline - Adapter is reconnecting. Using saved configuration information from Config.ini
11:03:18,366 INFO com.ibm.rqm.adapter.library - Successfully created an HTTP client
11:03:19,226 INFO com.ibm.rqm.adapter.library - The adapter is now connected
11:03:27,619 WARN com.ibm.rqm.adapter.commandline - Failed to save configuration file for the command line adapter
11:03:27,619 DEBUG com.ibm.rqm.adapter.commandline - com.ibm.rqm.adapter.library.data.AdapterException: Failed to retrieve adapter information
11:03:27,629 INFO com.ibm.rqm.adapter.commandline - Created Command Line Adapter
11:03:27,629 DEBUG com.ibm.rqm.adapter.library - Adapter polling RQM server for instructions.
11:03:28,039 INFO com.ibm.rqm.adapter.library - Stored configuration is out of sync. Adapter is re-registering.
11:03:28,989 DEBUG com.ibm.rqm.adapter.library - Adapter process going for sleep for: 5 seconds.
11:03:33,991 DEBUG com.ibm.rqm.adapter.library - Adapter polling RQM server for instructions.
11:03:34,401 INFO com.ibm.rqm.adapter.library - Stored configuration is out of sync. Adapter is re-registering.
11:03:35,331 DEBUG com.ibm.rqm.adapter.library - Adapter process going for sleep for: 5 seconds.
11:03:40,343 DEBUG com.ibm.rqm.adapter.library - Adapter polling RQM server for instructions.
11:03:40,943 INFO com.ibm.rqm.adapter.library - Stored configuration is out of sync. Adapter is re-registering.
11:03:41,874 DEBUG com.ibm.rqm.adapter.library - Adapter process going for sleep for: 5 seconds.
11:03:46,875 DEBUG com.ibm.rqm.adapter.library - Adapter polling RQM server for instructions.
and so on...
Environment
Client: Window XP SP3
RFT 8.2.0.1
Server: RHEL 5.5/DB2 9.7
RQM 3.0.1
Our RQM instance resides on the cloud. The RFT adapters require a proxy to access it. We achieve this by using cntlm to tunnel to the cloud.
This all worked with RQM v2.
Any ideas what is going wrong?
4 answers
When specifying the URL for the adapters be sure that you are using the Public URI of your server. Not the servers IP address or short name alias. You can confirm your public URI via the QM server admin page, by default that would be here:
https://servername:9443/qm/admin
If for some reason the machine from which the adapter is running cannot resolve the server by name (as defined in public URI). Then place an entry in your systems hosts file, so that it can be resolved by servername.
https://servername:9443/qm/admin
If for some reason the machine from which the adapter is running cannot resolve the server by name (as defined in public URI). Then place an entry in your systems hosts file, so that it can be resolved by servername.
When specifying the URL for the adapters be sure that you are using the Public URI of your server. Not the servers IP address or short name alias. You can confirm your public URI via the QM server admin page, by default that would be here:
https://servername:9443/qm/admin
If for some reason the machine from which the adapter is running cannot resolve the server by name (as defined in public URI). Then place an entry in your systems hosts file, so that it can be resolved by servername.
Kurtis, thanks for the reply.
In our environment we don't specify the uri of the RQM server. Our RQM server resides on the cloud. Our farm machines (with the RFT adapters) reside locally. We need to use a proxy to connect to the internet. As far as I am aware, the RFT adapter doesn't support this so we use a third-party tool (cntlm) to automatically redirect all of our RQM traffic to the server. We specify the machine on which cntlm is running in the adapter. This used to work in RQM v2.
Several of the adapters including RFT use a library that was somewhat rewritten in RQM 3.0.1. RFT 8.2 and above is built on the newer library and I believe that is related to the change in behavior you are experiencing. The command-line adapter supports HTTP proxy, but RFT adapter doesn't.
I'm surprised there's no means of you creating a VPN connection to the cloud so that you don't have to use a third-party tool to redirect request to it. In either case, try adding an entry to your host file that uses the machine name that is configured for your servers public URI, but the IP that it will map to will be the IP of your cntlm server that will redirect it to the real server. I'm just trying to look for a way to configure the adapter with the public URI defined for your server, even if that involves tricking it using the host file or some other means.
I'm surprised there's no means of you creating a VPN connection to the cloud so that you don't have to use a third-party tool to redirect request to it. In either case, try adding an entry to your host file that uses the machine name that is configured for your servers public URI, but the IP that it will map to will be the IP of your cntlm server that will redirect it to the real server. I'm just trying to look for a way to configure the adapter with the public URI defined for your server, even if that involves tricking it using the host file or some other means.
Several of the adapters including RFT use a library that was somewhat rewritten in RQM 3.0.1. RFT 8.2 and above is built on the newer library and I believe that is related to the change in behavior you are experiencing. The command-line adapter supports HTTP proxy, but RFT adapter doesn't.
I'm surprised there's no means of you creating a VPN connection to the cloud so that you don't have to use a third-party tool to redirect request to it. In either case, try adding an entry to your host file that uses the machine name that is configured for your servers public URI, but the IP that it will map to will be the IP of your cntlm server that will redirect it to the real server. I'm just trying to look for a way to configure the adapter with the public URI defined for your server, even if that involves tricking it using the host file or some other means.
Thanks Kurtis. Making an entry in the hosts file with the cntlm ip and the rqm server host name fooled it into working.