Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RQM Proxy not getting response from DOORS

Calling this URL (with OSLC headers) in DOORS works:


But calling this URL returns OK status with an empty response message:
https://myRQM/qm/proxy?uri=[URL from above passed through javascript's encodeURIComponent]

Can you tell if there a problem/limitation with the RQM proxy service, or what DOORS can send via proxy? Or am I doing something wrong? I do have Global Config Management enabled, and my URL does not specify the config context... but I would expect an error if DOORS can't identify it and needs it. However, maybe getting OSLC from within a DOORS widget is OK, whereas getting OSLC from RQM requires some other upfront info?

I can see that the RQM application makes plenty of proxy calls that DO work (such as /qm/proxy?uri=https://myJTS/jts/whoami), and a proxy call to DOORS when I open a requirements picker.

Thanks in advance!

0 votes

Comments

I found out that I needed to do encodeUrl on the portion after proxy?url=


However, there still does seem to be some dysfunction in the proxy service, such as this URL I can't get data from:



One answer

Permanent link

 ETM/RQM web ui can directly call DOORS API due to CORS Web server error. So, ETM UI call ETM server which in turn calls the DOORS API. This is done via service called proxy

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 516
× 234
× 27

Question asked: Oct 15 '20, 2:57 p.m.

Question was seen: 1,849 times

Last updated: Dec 01 '20, 3:00 a.m.

Confirmation Cancel Confirm