Error connecting LQE to a doors data source
I have added the local key to doors and altered the festival.xml file and added the datasource as described in the following two links. I have ensured all the processes are up, but no dice. Any ideas why, places to look for a solution? I am a bit worried by the dwa address being http and the following setting in the festival.xml file
<f:property name="ForceHttpsForAuthenticationForOAuth" value="true"/>
I have tried setting that to both false and true but it doesn't work. Also, the trusted connection tick box within DOORS in the Registered OAuth Consumer dialog is greyed out and not selectable, not sure If that is an issue?
I have raised a case with IBM, but the correct answer has not arrived yet.
Thanks for any help
Richard
Accepted answer
Hi Richard,
You should definitely set <f:property name="ForceHttpsForAuthenticationForOAuth" value="false "/> if DWA isn't running in secure mode, and make sure to restart DWA after saving that change. If you haven't already seen this video on IBM DeveloperWorks, it might be useful to step through it to see if it matches what you're doing.
https://www.ibm.com/developerworks/community/blogs/iotsupport/entry/How_to_index_DOORS_9_6_artifacts_in_Lifecycle_Query_Engine?lang=en
One more thing to check is the Derby database port. Sometimes the default port number (1527) is grabbed by something else - so it might be worth stopping Derby, seeing the port is still in use with a 'netstat' and if it is, reset the Derby port to something free. You'd need to update that port in all these files:
<DWA_HOME>\server\festival\config\festival.xml:
<DWA_HOME>\derby.start.bat:
<DWA_HOME>\derby\derby.properties:
<DWA_HOME>\derby\scripts\init_setting.bat:
and restart DWA. That's all I can think of - if that doesn't help then the Support guys should be able to figure it out.
John
You should definitely set <f:property name="ForceHttpsForAuthenticationForOAuth" value="false "/> if DWA isn't running in secure mode, and make sure to restart DWA after saving that change. If you haven't already seen this video on IBM DeveloperWorks, it might be useful to step through it to see if it matches what you're doing.
https://www.ibm.com/developerworks/community/blogs/iotsupport/entry/How_to_index_DOORS_9_6_artifacts_in_Lifecycle_Query_Engine?lang=en
One more thing to check is the Derby database port. Sometimes the default port number (1527) is grabbed by something else - so it might be worth stopping Derby, seeing the port is still in use with a 'netstat' and if it is, reset the Derby port to something free. You'd need to update that port in all these files:
<DWA_HOME>\server\festival\config\festival.xml:
<DWA_HOME>\derby.start.bat:
<DWA_HOME>\derby\derby.properties:
<DWA_HOME>\derby\scripts\init_setting.bat:
and restart DWA. That's all I can think of - if that doesn't help then the Support guys should be able to figure it out.
John
Comments
