Project Dashboards restored to default after upgrading RTC

Hi Milan,

All dashboards are stored on the JTS's storage service, so this indicates a problem finding the dashboards using the query service. A few questions..

1. Are you still using the same JTS (which version?), and have you made any changes to the JTS that might affect the storage service, e.g. switch to a new DB or forget to migrate from the old one?
2. Did you change the public URL of either the JTS or RTC?
3. Is the JTS still able to find your personal dashboards, e.g. in the home menu?

Hi Milan,

All dashboards are stored on the JTS's storage service, so this indicates a problem finding the dashboards using the query service. A few questions..

1. Are you still using the same JTS (which version?), and have you made any changes to the JTS that might affect the storage service, e.g. switch to a new DB or forget to migrate from the old one?
2. Did you change the public URL of either the JTS or RTC?
3. Is the JTS still able to find your personal dashboards, e.g. in the home menu?

Hi curtispd,

We actually migrated all environment from 32-bit windows server 2003 to 64-bit win server 2008.
We have changed all necessary software (DB2 64-bit, WAS 7 64-bit).
After configuring necessary 64-bit environment, we established Jazz Team Server 3.0 ifix1 first (restoring the backup from 32-bit DB2 ESE to 64-bit DB2 ESE using option comprlib, then we have done some migration steps:

We upgraded CCM part from 3.0ifix1 to 3.0.1 following instructions from CLM help site.

Also the public URL of JTS and RTC has been changed.

Is there any way to retrieve the dashboards?

Hi Milan,

Unfortunately, changing the public URL is not currently supported in the latest releases, see: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/127009.

Dashboard is one of the components most affected by changes in the public URL, but you may encounter any number of issues from other components as well, since this scenario is not tested. I don't have a list of known defects handy though.

Before continuing, I'd recommend reconsidering the URL change. If it's possible to hold on to the original URLs until it is supported, the fix should simply be to change it back to the original URLs, then do a repotools-jts -reindex.

Let me know if this is possible or not.

Hi Milan,

Unfortunately, changing the public URL is not currently supported in the latest releases, see: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/127009.

Dashboard is one of the components most affected by changes in the public URL, but you may encounter any number of issues from other components as well, since this scenario is not tested. I don't have a list of known defects handy though.

Before continuing, I'd recommend reconsidering the URL change. If it's possible to hold on to the original URLs until it is supported, the fix should simply be to change it back to the original URLs, then do a repotools-jts -reindex.

Let me know if this is possible or not.

Hi curtispd,

Just to be sure. Will this issue work if I replace original Public URI to another machine?

Thanks,

Yes, it shouldn't matter which physical machine it is on, as long as it's the same database content and original public URL it was created with.

Yes, giving a new machine that URL is fine ... what RTC cares about is
that the original URL gets you to the right repository ... it doesn't
care what physical machine currently hosts that repository.

Cheers,
Geoff

On 2/10/2012 4:38 AM, milan.krivic wrote:

curtispdwrote:
Hi Milan,

Unfortunately, changing the public URL is not currently supported in
the latest releases, see:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/127009.

Dashboard is one of the components most affected by changes in the
public URL, but you may encounter any number of issues from other
components as well, since this scenario is not tested. I don't have a
list of known defects handy though.

Before continuing, I'd recommend reconsidering the URL change. If
it's possible to hold on to the original URLs until it is supported,
the fix should simply be to change it back to the original URLs, then
do a repotools-jts -reindex.

Let me know if this is possible or not.

Hi curtispd,

Just to be sure. Will this issue work if I replace original Public URI
to another machine?

Thanks,