It's all about the answers!

Ask a question

Must to do things at client side before executing migration from RTC 3.0.1.x to 4.0.6

Natsumi Yokoyama (209387101) | asked Apr 15 '14, 6:06 a.m.
edited Apr 15 '14, 6:11 a.m.


Is there any thing which must be (not "better to be" )done by end users, i.e RTC clients,  before executing migration from RTC 3.0.1.x to 4.0.6?

For example, follwing things.

  • Unlock all locked files
  • Check in / Deliver all change sets
  • copy(back up) ".metadata" of their eclipse local workspaces

I could not find above information in following InfoCenter/Wiki. My clients use Scource Management, Workitem Management, and Build Management feature of RTC.

My understanding that It is enough for them to back up files in their local workspaces.

In case of ClearCase, there are some thins must be done by end users. But RTC does not have such a things?

Thank you in advance.


Accepted answer

permanent link
Krzysztof Ka┼║mierczyk (7.5k479103) | answered Apr 15 '14, 6:24 a.m.
Hi Natsumi, RTC does not have any constraints regarding eclipse workspace. You can back up it if you want. The only thing recommended to do is to clear browser cache.

Let us know if that helps.
Natsumi Yokoyama selected this answer as the correct answer

Natsumi Yokoyama commented Apr 15 '14, 8:34 p.m.

Thank you for your answer. Could you tell me why you recommend to clear browser cache?

Krzysztof Ka┼║mierczyk commented Apr 23 '14, 2:39 a.m.

If you use web client, html and js code is changing through versions. It is important to use the latest code, not one cached by web browser. We had couple of issues with that especially when using proxy server.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.