rmt2rqm without SSL?
Has anyone gotten the above mentioned utility to work against a non-SSL RQM site?
We've been testing the rmt2rqm migration utility and it works fine on an RQM site on the SSL-enabled port. When trying to run the utility against a non-SSL port on the same site, the utility GUI returns an "invalid login" error. In the command window behind the scenes, however, I see an error stack which starts with a "javax.net.ssl.SSLHandshakeException" error.
This leads me to believe the migration tool assumes SSL in place, however I can't find any documentation that indicates this as a requirement.
In fact, and I'm thinking it is an oversight on their part, the online documentation for the utility (http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/index.jsp?topic=/com.ibm.rational.test.qm.doc/topics/t_migrate_rmt_intro.html) indicates "HTTP", not HTTPS. Additional documentation specific to RQM installation and setup provides options for setting up the site without SSL so it's clear SSL isn't a requirement.
We've been testing the rmt2rqm migration utility and it works fine on an RQM site on the SSL-enabled port. When trying to run the utility against a non-SSL port on the same site, the utility GUI returns an "invalid login" error. In the command window behind the scenes, however, I see an error stack which starts with a "javax.net.ssl.SSLHandshakeException" error.
This leads me to believe the migration tool assumes SSL in place, however I can't find any documentation that indicates this as a requirement.
In fact, and I'm thinking it is an oversight on their part, the online documentation for the utility (http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/index.jsp?topic=/com.ibm.rational.test.qm.doc/topics/t_migrate_rmt_intro.html) indicates "HTTP", not HTTPS. Additional documentation specific to RQM installation and setup provides options for setting up the site without SSL so it's clear SSL isn't a requirement.
2 answers
I think the migration utilities are (by design) HTTPS only, the same as the execution adapters, as outlined here:
http://www-01.ibm.com/support/docview.wss?uid=swg21393360
Can someone confirm?
If yes, the recommendation would be to continue to use HTTPS for execution adapters and migration utilities, even if you use HTTP to access the WebUI.
Of note... even if you disable security on the RQM server, it will still accept SSL connections. To elaborate (assuming default ports; these can of course be changed):
-by default the server accepts SSL only on port 9443
-if you follow the doc to "disable" security, you gain HTTP access on 9080. However HTTPS is *also* active on 9443. You can use both.
http://www-01.ibm.com/support/docview.wss?uid=swg21393360
Can someone confirm?
If yes, the recommendation would be to continue to use HTTPS for execution adapters and migration utilities, even if you use HTTP to access the WebUI.
Of note... even if you disable security on the RQM server, it will still accept SSL connections. To elaborate (assuming default ports; these can of course be changed):
-by default the server accepts SSL only on port 9443
-if you follow the doc to "disable" security, you gain HTTP access on 9080. However HTTPS is *also* active on 9443. You can use both.