CLM4: Unable to communicate with the Rational Reporting Server.
I'm trying to show RRDI report in CCM but getting "Unable to communicate with the Rational Reporting Server.".
I've checked Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21609885
In my case firebug returns:
I've checked Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21609885
In my case firebug returns:
Error 500: no protocol: null/servlet/dispatch
Any ideas?
-thanks in advance
Accepted answer
2 other answers
Hello Timur,
Could you please try flushing the WAS cache, this can be done by deleting the temp files in:
c:\<was Install="" dir="">\profiles\AppSrv01\temp\<machine name="">\server1\<xxx_war> and c:\<was Install="" dir="">\profiles\AppSrv01\temp\wscache\<xxx_war> where xxx is the name of the application such as rtc_war or jazz_war
I had written the technote after implimenting this in the customers' staging environment, however, when the customer did the same steps on Production server, the error was still seen. A simple Reboot of the machine, resolved the issue.
Could you please try flushing the WAS cache, this can be done by deleting the temp files in:
c:\<was Install="" dir="">\profiles\AppSrv01\temp\<machine name="">\server1\<xxx_war> and c:\<was Install="" dir="">\profiles\AppSrv01\temp\wscache\<xxx_war> where xxx is the name of the application such as rtc_war or jazz_war
I had written the technote after implimenting this in the customers' staging environment, however, when the customer did the same steps on Production server, the error was still seen. A simple Reboot of the machine, resolved the issue.
The signer of self signed certificates may not be recognized by the CLM server.
Have you checked my forum entry:
https://jazz.net/forum/questions/83924/what-config-step-is-missing-to-enable-import-custom-report-in-ccm40-to-import-rrdi-reports
Comments
KrishnaKanth Naik
JAZZ DEVELOPER Sep 13 '12, 4:49 a.m.Hello Timur,
Could you please try flushing the WAS cache, this can be done by deleting the temp files in: c:\<was install="" dir="">\profiles\AppSrv01\temp\<machine name="">\server1\<xxx_war> and c:\<was install="" dir="">\profiles\AppSrv01\temp\wscache\<xxx_war> where xxx is the name of the application such as rtc_war or jazz_war
I had written the technote after implimenting this in the customers' staging environment, however, when the customer did the same steps on Production server, the error was still seen. A simple Reboot of the machine, resolved the issue.