Adding Dashboard Widget Issue (RTC 3.0)- No 'Select Catalog'

Ran into something similar a week or so ago. We had a few things including the lack of the widgets types to select that were not behaving correctly (see below).

I ended up checking through the teamserver.properties files for both the JTS and CCM. If you are using derby then the paths to the various indices should be absolute, if DB2 then they can be relative. I had been advised by support to list all the paths as absolutes (even though we're using DB2), then when we noticed the widgets and issues below, they had us change them back to relative paths and all these issues were resolved.

My advice is to check through the teamserver.properties file/s and ensure that everything is defined correctly and that you utilize relative or absolute paths as per the isntallation guide for the db your using. If there is an end of line missing then the server might run but you may see license errors or other odd behavior after logging in.


Is the "Home Menu" (upper left) not working as well? If it list a discovery service error when you click to see a list of project areas it sounds very close to an issue we had.

Another item to look for is logging into the JTS admin and then look at the main landing page, see if any of the registered applications like the CCM is showing the link from the main page of not under Application Administration and if not goto the Server tab and Click Registered APplications, see if the App Type is listed correctly or if it says, unkown or similar.

Hello,

same problems here.
we tried to change the relative paths to absolute paths. But it didn't change anything. There seems to be some problems with the registration of the application. After the migration in registered application /ccm is type "unknown".
Under Consumer Keys there are only "/ccm" and "ajax" and "repository".

If we delete all keys and the application delete the tomacat cash and reregister ccm. There is dashboard and "/ccm", but no "repository" and "ajax". The dashboards are not working any more at all (see below)

We are using Oracle and the ActiveDirectory Ldap interface.

Error

An error occured while retrieving the dashboard:

Internal Server Error
HTTP Status 500 - Unexpected response code 403 while updating indexTime resource

type Status report

message Unexpected response code 403 while updating indexTime resource

description The server encountered an internal error (Unexpected response code 403 while updating indexTime resource) that prevented it from fulfilling this request.
Apache Tomcat/5.5.30

It sounds like something is failing at a lower level but it's hard to say what without more information. If you could scan your logs (<install_dir>/server/logs/) for errors that look relevant, that would be helpful. If you don't find anything interesting, it would be helpful if you could install the Firebug plugin (or any browser tool that can see all the requests the browser is making), and look for failing requests.

As for the 403 errors after deleting the keys, this is happening because storage areas on the JTS are associated with those consumer keys as a way to sandbox components to their own storage areas. Unfortunately, after you delete a key, the next time dashboard wakes up and sees it has no key, it thinks it's a first launch and goes and gets a new one. But this new one doesn't match the old one, and it's no longer allowed to access its own storage area.

The ideal fix to this specific one is to bring back the same keys. Did you happen to copy them down somewhere?

Hi,

no sorry we haven't saved the old keys. We deleted the keys on behalf of the rational support and it hasn't requested to to copy them.

We suppose this is not a feature.

Can anybody else reproduce the same issue? We are using Oracle 10g with Active Directory. We phase the same issue on 2 different servers.

Regards,
Alexander

The problem is still not resoved.

To recover lost keys, have a look at:
https://jazz.net/wiki/bin/view/Main/JFSRepoToolsScenarios

As for the problem where the drop down doesn't appear in the widget catalog, this field gets its list from the friends of the current server. So if you go to <context_root>/admin and look at the Friends (Outbound) page, it should match this list. If you're on your CCM server and the list is empty, it may indicate that you've somehow lost your friends during the migration. If it's there, then there would be some sort of failure while retrieving the widget catalog.

Note that the friends list on the JTS may be different than that of the CCM server. If you want to be able to add remote viewlets from other servers to your personal dashboards, which reside on the JTS, you'll need to add friend entries on your JTS for those servers.

Please check the friends and let me know if this still doesn't resolve the issue.

The problem is still not resoved.

Is the issue fixed? I ran into the same problem:
0000001e webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: -: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: Unexpected response code 403 while updating indexTime resource
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:637)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1187)
at com.ibm.team.dashboard.service.internal.DashboardServiceBase.service(DashboardServiceBase.java:259)
at com.ibm.team.dashboard.service.internal.DashboardServiceBase.perform_POST(DashboardServiceBase.java:204)
at com.ibm.team.repository.service.TeamRawService.service(TeamRawService.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy744.service(Unknown Source)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestService(AbstractTeamServerServlet.java:813)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1829)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1688)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1598)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3933)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:445)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:504)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:301)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:275)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1016)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:639)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

shihuib, please see earlier comments - it looks like you may have deleted the oauth consumer key for com.ibm.team.dashboard in the admin Web UI. See the link above to recover lost keys.