fail to integrate DOORS 9.4 and RQM 4.0

Luc
What are the steps when you hit this issue. Could you provide little background on what you could complete successfully so far?

I integrated RQM 4.0 and Doors 9.4 last week for a customer and IBM Help documentation wasn't really helpfull, especially documentation about making "Doors works in https mode". There was little documentation about  it. Same thing happen during the handshake of the two server. I recommend you to review Doors Help site about the RQM integration and RQM site for Doors integration. There could be some minor differences between them and you can catch it up :)

All the servers and clients are in the same vm environment (win 7 pro 64bits)
 I have configured Web Access to support HTTP and HTTPS: login, browsing and https url solving is OK
 I am using the DOORS help about integrating DOORS & RQM
Configuration of RQM:
- consumers in: DOORS,     f492a8be0ad2433f8c998736316104c, trusted
- friends out: DOORS, https://rmsrv:8443/dwa/public/rootservices, 22532956-341e-4322-a931-c56e5664baff
- white list  https://rmsrv:8443/

After this setting, the RQM application and friends disgnostic displays an error:

Friend: there is no OAuth domain in the discovery resource at https://rmsrv:8443/dwa/public/rootservices for "DOORS" that is a prefix of the discovery resource URI.
This could be caused by changing the public URI setting in the application or friend.
OAuth domains from the discovery resource: [http://rmsrv:8080/dwa]

And the configuration of an association from a RQM project to DOORS fails

Failed to read matching artifact container catalog resource:
Unable to load URL: /qm/proxy?uri=https://rmsrv:8443/dwa/rm/discovery/catalog, Status: 401


I assume that there is some error in the DWA configuration, but I have no idea ....

OAuth domains from the discovery resource: [http://rmsrv:8080/dwa]

this line might give us a clue. I dont have my wm image with me that's why I can't really help you with this but just trying :)

the problem was in festival.xml from DWA, with the OAuth url ...

Hi Luc,

I have similar issues. Could you please tell me, how you solved it?