RQM 3.0 command line utility 302 Redirect Exception
java -jar C:\SVN\Common\trunk\Common\etc\java\RQMUrlUtility.jar -command PUT -user user -password pass -filepath c:\\temp\\testcase\\8_1308328463116_27526.xml -url https://site:port/qm/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Desktop+PM+%28Quality+Management%29/testcase/tscript13083284602578
When I call this command I get back this response in my command line ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <<<<<RQMUrlUtility>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ RQMUrlUtility: Connected to https://10.48.135.203:9443 using project "Desktop+PM +%28Quality+Management%29" java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available Unable to create SSL_TLS context, trying SSLv3 RQMUrlUtility: Login error (response code) - 404 Response Body: <html><head><title>Apache Tomcat/5.5.30 - Error report</title><st><H1></style> </head><body><h1>HTTP Status 404 - /jazz/j_security_check</h1><HR><p><b>type</b> Status report</p><p><b>message</b> <u>/jazz/j_security_check</u></p><p><b>description</b> <u>The requested resource (/jazz/j_security_check) is not available.</u></p><HR><h3>Apache Tomcat/5.5.30</h3></body></html> RQMUrlUtility: Calling method to upload XML from a specified file t o URL Jun 17, 2011 12:44:13 PM org.apache.commons.httpclient.HttpMethodDirector isRedi rectNeeded INFO: Redirect requested but followRedirects is disabled RQMUrlUtility: Server Response code: 302 RQMUrlUtility: >>>>>>>>!!!put returned 302, location = https://10.48.135.203:944 3/qm/secure/authenticated/identity?redirectPath=%2Fqm%2Fsecure%2Fservice%2Fcom.i bm.rqm.integration.service.IIntegrationService%2Fresources%2FDesktop%2BPM%2B%252 8Quality%2BManagement%2529%2Ftestcase%2Ftscript13083284602578 RQMUrlUtility: Got an IOException: org.apache.commons.httpclient.RedirectExcepti on org.apache.commons.httpclient.RedirectException at com.ibm.rqm.url.client.RQMUrlPUT.<init>(Unknown Source) at com.ibm.rqm.url.UrlUtility.main(Unknown Source) Prior to 3.0 RQM was being hosted on another box and our URL was slightly different and we used url/jazz instead but I noticed that the URL had changed to url/qm, not sure if this is right/wrong. Any advice on this would be great, appreciate it. EDIT: I'm guessing my URL is correct because a GET command will work instead and I am returned some XML. Brandon |
3 answers
The older urls had /jazz as the context root, where as a new RQM 3.0.1 install will have /qm as the context root. But this is configurable and depends on what public URL was specified during the server setup. So the easiest place to make note of the correct context root, is to see the URL shown in the browser when you are logged into RQM.
In either case, I get the impression that you are running the an older 2.x copy of the RQMUrlUtility. I say that because in your command you specified /qm as the context root but in the 404 the utility is looking for /jazz/j_security_check, which is the old context root. Be certain you download the RQMUrlUtility from the all downloads page of RQM 3.0.1: https://jazz.net/downloads/rational-quality-manager/releases/3.0.1?p=allDownloads |
The older urls had /jazz as the context root, where as a new RQM 3.0.1 install will have /qm as the context root. But this is configurable and depends on what public URL was specified during the server setup. So the easiest place to make note of the correct context root, is to see the URL shown in the browser when you are logged into RQM. Please see the Reportable REST API WIKI for more information on the API (e.g. context roots - https://jazz.net/wiki/bin/view/Main/RqmApi#contextRoot). |
The older urls had /jazz as the context root, where as a new RQM 3.0.1 install will have /qm as the context root. But this is configurable and depends on what public URL was specified during the server setup. So the easiest place to make note of the correct context root, is to see the URL shown in the browser when you are logged into RQM. Oh I didn't think about that. I will be sure to download the new RQMUrlUtility and give it another try. |
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.