RQMCopy not copying test plan template
Enviroment:
RQM 4.0.1, RQMCopy 4.0.1, JRE 7.0, Windows 2008 server R2
From a batch file I'm running:
REM Runn the RQM Copy utility
"C:\Program Files\Java\jre7\bin\java" -jar \\pna401f7070\c632566\RQM-Extras-RQMCopyUtil-4.0.1\RQMCopyUtility.jar -s="https://jts2.ent.corp.bcbsm.com:9443/jazz/service/com.ibm.rqm.integration.service.IIntegrationService/resources/CCS_Trial+%28Quality+Management%29" -us=C632566 -pws=58875887aQ! -a=template -id=com.ibm.rqm.planning.templates.testplan.template_1420050166657 -l=\\pna401f7070\c632566\RQM-Extras-RQMCopyUtil-4.0.1\importlog.txt
And the response I get is:
Jan 05, 2015 9:01:53 AM com.ibm.rqm.ct.util.Logger logError SEVERE: SSL_TLS SSLContext not available Jan 05, 2015 9:01:53 AM com.ibm.rqm.ct.util.Logger logInfo INFO: Unable to create SSL_TLS context, trying SSLv3 Jan 05, 2015 9:01:57 AM com.ibm.rqm.ct.util.Logger logError SEVERE: After login, attempt to access init data returned: 404 Jan 05, 2015 9:01:57 AM com.ibm.rqm.ct.util.Logger logInfo INFO: Starting: template com.ibm.rqm.planning.templates.testplan.template_1420050166657 Jan 05, 2015 9:01:57 AM com.ibm.rqm.ct.util.Logger logInfo INFO: SUCCESS!
I can copy a plan -- even with the 404 error -- but not a template.
Anybody have any insight into this?
2 answers
For the id argument, add the testplan/ prefix to the test plan template ID (see Copying a template in https://jazz.net/wiki/bin/view/Main/RQMCopyUtility#Usage_Examples).
Comments
showing 5 of 9
show 4 more comments
I was finally able to get it to work.
My notes are:
-Must run from the command line.
-User must be a member and admin of both source and destination project areas. (I haven't tested member only or admin only)
-No '/' before testplan in the id
-Project area name must be the project alias from the API feed.
-Template ID must be the REST ID found in the html source from the /template API feed.
Once the feed is returned, view the source and find the <id></id> tags for the template of interest.
For a utility that was supposed to make things easier, it sure was hard.
My notes are:
-Must run from the command line.
-User must be a member and admin of both source and destination project areas. (I haven't tested member only or admin only)
-No '/' before testplan in the id
-Project area name must be the project alias from the API feed.
-Template ID must be the REST ID found in the html source from the /template API feed.
Once the feed is returned, view the source and find the <id></id> tags for the template of interest.
For a utility that was supposed to make things easier, it sure was hard.