Robert,

there is some information and links available to your questions here http://jazz.net/library/techtip/407.

You have to distinguish between exported process templates, process templates deployed into a repository (available to create new projects from them) and templates deployed in a project. When upgrading repositories the data in Projects is upgraded and still matches the instantiated process template in the projects. The templates deployed in the repository will also be migrated (There have been differences in how they where stored in 1.0 and 2.0). You can export a migrated template template after migrating the repository and use that for other projects in other repositories.

In general threads in this forum suggest that upgrading the instantiated templates in a project area beside just what repository migration does is not a trivial task. E.g. Newer Templates for Scrum provide things in addition to what was available in 1.0 and you don't get that just migrating the repository. This is known and worked upon which results in the technote above for a first step.

2-4 I can't answer right away. I would consider copy/paste over dangerous however. I think there is data stored in the process XML that belongs to the instance and if picking the XML from another source would overwrite that for one thing.

1) I have upgraded step by step repositories from 1.0 to 2.x and have not seen things breaking. There have been migration tools and in general you should follow the process lined out in the Upgrade section of the download page of the RTC version you are using. This is supported and safe.

Ralph

Hi guys,

A few issues I need clarification on customer deployments.

1) If I have a customer on RTC 1.0 and a custom template built in 1.0, will upgrading to 2.0.0.2 result in any breakage of template functionality or access to my existing data.

2) If I have duplicated a template from 1.0 in 2.0.0.2 with same field names, same forms, same ids, etc... and I copy the xml in this template into a project area based on the 1.0 template, will it result in any breakage or loss of existing data.

3) If I create any private or shared queries on a particular project area and that project area template is upgraded/modified, will I lose those existing private or shared queries.

4) If I perform an upgrade to an existing template (xml copy and paste), will I lose existing items if I have modified forms, fields, team names, categories, queries, reports, etc.... will my data still be available, eg. I have defined some iterations and categories, if I update this template by an xml copy & paste, are my iterations and categories lost.

I know I am asking a variety of questions. Please advise me the best way to update existing project areas to include new template functionality. Pointers to reference material are welcome as well as any best practices used by Rational when deploying new templates to existing projects.

Hello Robert,

1) A custom template from 1.0 will continue to work in 2.0.0.2, as long as the repository migration has been performed, as Ralph describes.

2) Copying process configuration XML from RTC 2.0.0.2 to RTC 1.0 will not work. There were changes to the syntax of the XML between the versions. RTC 1.0 will not be able to understand the XML from RTC 2.0.0.2. You may see errors in the process template or project area editor or, worse yet, you might only see failures when you try to use a certain feature. Don't do it. : >

3) Once a project area is created, changes to the template used to create the project area are not applied to the project area. So, you can change the template without affecting the project area. Also, the queries you create in a project area will not be lost when you migrate a repository, so you are not in danger of losing your queries.

4) If you copy and paste XML, you may lose work item categories and other kinds of data used in work item queries, forms, plans, etc. You will not lose the iterations you created, but you will lose any configurations you have made to those iterations. That is, you will lose any permissions and behavior changes you made specific to the iterations.

The article Ralph mentioned outlines the best way to upgrade project areas that were created with a template that ships "out of the box" in RTC. You should not need to upgrade project areas created with custom templates, unless you have added new new features to the templates and you want them in your projects. If that is the case, you will probably need to do some XML manipulation. This is not a trivial task, because it requires you understand the XML syntax for the data in the project area.

Martha
Jazz Developer

Hi guys,

A few issues I need clarification on customer deployments.

1) If I have a customer on RTC 1.0 and a custom template built in 1.0, will upgrading to 2.0.0.2 result in any breakage of template functionality or access to my existing data.

2) If I have duplicated a template from 1.0 in 2.0.0.2 with same field names, same forms, same ids, etc... and I copy the xml in this template into a project area based on the 1.0 template, will it result in any breakage or loss of existing data.

3) If I create any private or shared queries on a particular project area and that project area template is upgraded/modified, will I lose those existing private or shared queries.

4) If I perform an upgrade to an existing template (xml copy and paste), will I lose existing items if I have modified forms, fields, team names, categories, queries, reports, etc.... will my data still be available, eg. I have defined some iterations and categories, if I update this template by an xml copy & paste, are my iterations and categories lost.

I know I am asking a variety of questions. Please advise me the best way to update existing project areas to include new template functionality. Pointers to reference material are welcome as well as any best practices used by Rational when deploying new templates to existing projects.