IBM Support

ClearQuest Web does not function when hosting other applications on the same web application server

Question & Answer


How do I modify the []JSESSIONID[] of IBM Rational ClearQuest Web so that I can deploy ClearQuest Web with other products on the same web application server?


By default, after deploying ClearQuest Web on an IBM WebSphere Application Server, the JSESSIONID cookie path is set to the domain root /. If there are other web applications running on WebSphere Application Server that set the JSESSIONID cookie path to /, this creates a JSESSIONID conflict, which causes ClearQuest Web functions to fail.


To work around this issue, modify the JSESSIONID cookie path for the ClearQuest Web URL.


1. Open the WebSphere Application Server administrative console.

2. If ClearQuest Web is deployed on WebSphere Application Server 6.0, click Servers > Application servers> server_name > Web container settings > Session management > Enable cookies.

If ClearQuest Web is deployed on WebSphere Application Server 7.0 or 8.0, click Servers > Server types > WebSphere application servers > server_name > Session management > Enable cookies.

3. Change the JSESSIONID cookie path from / to /cqweb so that the session cookie is restricted to the ClearQuest Web application on that server.

[{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1;;;7.1.1;;;;;;;;;;7.1.2;;;;;;;8.0;;","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018