Migrate Process template from RTC 2.0.0.2 to RTC 3.0 M6a
What is the proper procedure to move a process template from RTC2.0.0.2 to RTC 3.0 M6a? The following is stated in the 'Help' section "importing/exporting process templates"...
"You can import templates only from the same version of the product. If you attempt to import templates from a different version, you receive an error message with instructions for how to migrate the template to the product version that you are using." I received an error message (see below) but did receive the proper instructions for how to migrate the template to a RTC 3.0m6aversion. Error message received during initialization of project area: Problem An unhandled exception occurred during "Set up Main Project Structures". CRJAZ0215I Item not found: com.ibm.team.workitem.common.internal.model.impl.CategoryHandleImpl@4d344d34 (stateId: , itemId: , origin: <unset>, immutable: <unset>) Reason Initializes a project area with the pieces necessary to start work on a project. Appreciate the support. Judy Yi |
8 answers
RQM ver 3.0.1
When we try to open a specific testcase we receive an error. The problem started after we deleted a RQM auto-generated work item which was linked to the test case. CRJAZ0215I The following record was not found in the database: com.ibm.team.workitem.common.internal.model.impl.WorkItemHandleImpl@236c236c (stateId: , itemId: , origin: , immutable: ) Does anyone have a suggestion how to solve this? Thanks in advance Claus Hjerrild Pedersen |
|
Hi -
I found a submitted defect on this https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=118239 There is also a workaround added. Thanks, Judy Hi Judy, Hi Martha, Hi Judy, Did you use File > Import to import the template, or was it available in the repository after you moved for RTC 2.0.0.2 to RTC 3.0M6a? Is this a template that ships with RTC, or one you created? To upgrade your process templates, import them into a repository that is What is the proper procedure to move a process template from |
Hi Judy,
My teammate pointed out that the failure looks like one that has been reported previously. See https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/68872 . Once a project area initialization has failed, it continues to fail due to the Item Not Found for the CategoryHandleImpl. Can you try re-starting the server and re-running the initialization. If it fails again, set the Team Advisor view to "Show Detail Tree" and drill down to find the primary cause. The Show Detail Tree button is at the top right of the view and has a "tree" of red, green and yellow nodes. Martha Jazz Developer, Process Component Hi Martha, Hi Judy, Did you use File > Import to import the template, or was it available in the repository after you moved for RTC 2.0.0.2 to RTC 3.0M6a? Is this a template that ships with RTC, or one you created? To upgrade your process templates, import them into a repository that is What is the proper procedure to move a process template from |
|
Hi Martha,
I created a new project in RTC 3.0m6a, assigned a process template that was exported from RTC 2.0.0.2 into my new RTC 3.0m6a project, actioned "Initialize" project, and now receiving the error in my orginial request. From the previous response, it sounds like I need to reinstall RTC 2.0.0.2 then upgrade to RTC 3.0m6a - is this the only way to re-use the process template from RTC 2.0.0.2 with RTC 3.0m6a? Thanks, Judy Hi Judy, Did you use File > Import to import the template, or was it available in the repository after you moved for RTC 2.0.0.2 to RTC 3.0M6a? Is this a template that ships with RTC, or one you created? To upgrade your process templates, import them into a repository that is What is the proper procedure to move a process template from |
|
Hi Judy,
From the error, it looks like the action is looking for a category that did not get created. I am not familiar with the Set up Main Project Structures project area initialization follow up action. Is this one you are providing? Thanks, Martha Jazz Developer, Process Component Did you use File > Import to import the template, or was it available in the repository after you moved for RTC 2.0.0.2 to RTC 3.0M6a? Is this a template that ships with RTC, or one you created? To upgrade your process templates, import them into a repository that is What is the proper procedure to move a process template from |
|
I have RTC 3.0 running on a different server. I exported the template from RTC 2.0.0.2 server and used the Web UI import tool to import to RTC 3.0M6a server and then recieved the error in my earlier post.
The template is not a version that ships with RTC - we created this one. Thanks, Judy Did you use File > Import to import the template, or was it available in the repository after you moved for RTC 2.0.0.2 to RTC 3.0M6a? Is this a template that ships with RTC, or one you created? To upgrade your process templates, import them into a repository that is What is the proper procedure to move a process template from |
|
Did you use File > Import to import the template, or was it available in the repository after you moved for RTC 2.0.0.2 to RTC 3.0M6a? Is this a template that ships with RTC, or one you created?
Thanks, Martha To upgrade your process templates, import them into a repository that is What is the proper procedure to move a process template from |
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 07 '10, 5:02 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
To upgrade your process templates, import them into a repository that is
currently at the version from which those templates were exported. Then upgrade that repository (using the normal repository migration tooling). Then export those templates, and they will be at the version level of the upgraded repository. Note: The error message you show below doesn't look like the one you'd get because of a template version mis-match, but maybe the process team could comment on that. Cheers, Geoff On 7/7/2010 10:53 AM, judy7265 wrote: What is the proper procedure to move a process template from |
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.