It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,678
×10,852
×7,313
×4,663

question asked: Mar 06 '14, 4:53 a.m.
question was seen: 4,055 times
last updated: Mar 13 '14, 11:55 a.m.

Related questions

FAQ - How this Forum works

Unable to add RTC widgets onto RQM MiniDash Board (v3.0.1.1) ---- Error 404 Not Found

0
Rajesh Avanthi (108●15●134●173) | asked Mar 06 '14, 4:53 a.m.
Noticed that while adding RTC widgets on to RQM mini dashboard, they see the widgets gets added but does not display contents... it says  LOADING....

When have the cursor on this added RTC widget, we see the following:
         Disconnected from remote server (https://xyz.kre3052.com/jazz)

There are 2 WAS profiles pointing to the JTS server instance here..

FireBug Console displays the following :
=======================================


Interestingly, we are able to add RQM widgets on RTC dashboard successfully and vice-versa is NOT happening, resulting the above error.
The JTS is being configured with RQM and RTC only here.

Appreciate any quick help.

Thanks in advance

Comments
Paul Slauenwhite commented Mar 06 '14, 6:11 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

Two questions:

1. Can you add the FireBug console output (missing from the post)?

2. Can you create/view/update RTC WIs from RQM?

Sunil Kumar R commented Mar 06 '14, 8:30 a.m.
JAZZ DEVELOPER
Paul, here are the details:
https%253A%252F%252Fxyz.kre1020.com%252Fjazz <<--- RTC
(https://xyz.kre1020.com/jazz)

1. Firebug console:

2. Yes, the create / view / update RTC WI's from RQM works. Also QM widget added into RTC project area works fine.
Gerardo Gomez commented Mar 11 '14, 7:36 p.m. | edited Mar 11 '14, 7:38 p.m.

I see this issue is reported in the Mini Dashboard, Is it present in regular RQM dashboards? (e.g. Project Dashboard)

One answer

Most liked answers|Newest answers|Oldest answers ↑

0
permanent link
Rajesh Avanthi (108●15●134●173) | answered Mar 12 '14, 11:36 p.m.
This issue stands resolved now. Executing the DW jobs and restarting the WAS server did help.

Thanks

Your answer

Register or to post your answer.