It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×10,958
×7,479
×6,033

question asked: Apr 25 '14, 10:54 a.m.
question was seen: 5,299 times
last updated: Apr 28 '14, 7:41 p.m.

Related questions

Failure to copy the project in RQM from one server to another.

0
Pradeep Basnet (60●1●13●20) | asked Apr 25 '14, 10:54 a.m.

Hello,

I am trying to copy the RQM project artifacts from the one server to another server by using RQM copy Utility by using following command:

---------------------------------------------------------------

-s=https://myRQMServerA:9443/qm/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/RQMProjectA -us=Admin -pws=Admin-

d=https://myRQMServerB:9443/qm/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/RQMPorjectB -ud=Admin -pwd=Admin -

l=importlog.txt -f -a=testscript

------------------------------------------------------------------------------------

It is throwing below error. Any thought and suggetion why I am encoutering error. Is there any other option to copy RQM project artifacts from one server to other server.

Apr 25, 2014 10:38:32 AM com.ibm.rqm.ct.util.Logger logInfo
INFO: Attempting to create SSL_TLS context
Apr 25, 2014 10:38:32 AM com.ibm.rqm.ct.util.Logger logError
SEVERE: SSL_TLS SSLContext not available
Apr 25, 2014 10:38:32 AM com.ibm.rqm.ct.util.Logger logInfo
INFO: Unable to create SSL_TLS context, trying SSLv3
Apr 25, 2014 10:38:41 AM com.ibm.rqm.ct.util.Logger logInfo
INFO: Starting processing of artifact type: testscript
Apr 25, 2014 10:38:41 AM com.ibm.rqm.ct.util.Logger logInfo
INFO: Reading feed for artifact type: testscript
Apr 25, 2014 10:38:41 AM com.ibm.rqm.ct.util.Logger logInfo
INFO: Error received: 400, retry #: 0
Apr 25, 2014 10:38:44 AM com.ibm.rqm.ct.util.Logger logInfo
INFO: Error received: 400, retry #: 1
Apr 25, 2014 10:38:47 AM com.ibm.rqm.ct.util.Logger logError
SEVERE: General REST Exception: RestException executing: GET Artifact Feed, RC: 400, message: Error 400: SRVE0295E: Error reported: 400

Accepted answer

1
permanent link
Don Yang (7.7k●21●114●139) | answered Apr 26 '14, 3:57 a.m.
The CopyUtility uses project area alias instead of UI project area name for source and destination Project Area.
error 400 means bad request, so the first is to check if you have the right project area alias for both source and destination.
Running
https://server:port/qm/service/com.ibm.rqm.integration.service.IIntegrationService/projects

to find out your RQMProjectA and RQMProjectB project alias.

Some other check points are:
1) make sure permission/license  for the user are correct(GET/PUT): https://jazz.net/wiki/bin/view/Main/RqmApi#Permissions
for both source and destination projects
2) The CopyUtility should be the same version as your RQM.
3) Source and destination projects should be from the same version of RQM
Pradeep Basnet selected this answer as the correct answer
Comments
Pradeep Basnet commented Apr 28 '14, 12:52 p.m. | edited Apr 28 '14, 7:38 p.m.

Thanks Don,

Now it works. As you mentioned it was the alias issues.

Thanks,

Pradeep

Don Yang commented Apr 28 '14, 7:41 p.m.

Thanks for the update and glad to know it works for you.
I converted the latest answer as comments as it does not provide anything new.
As a best practice, if your question has been answered and it works for you, please accept the answer so that it won't appear in any feeds for the posts without an accepted answer.

One other answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Brett Bohnn (941●1●11●57) | answered Apr 25 '14, 11:39 a.m.
Hi Pradeep,

Are you sure there is not typo in the destination? Should that be RQMProject not RQM Porject?

d=https://myRQMServerB:9443/qm/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/RQMPorject

Thanks,
Brett
Comments
Pradeep Basnet commented Apr 25 '14, 12:56 p.m.

Hi Brett,

There is no typo.

Your answer

Register or to post 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.