Process Configuration Source Migration
We are testing v3.0 RC1 on a new server and using v2.0.0.2 on another server. Is there a way to export the Process Configuration Source XML from the v2.0.0.2 server and import it to the v3.0 RC1 server? When I copy the one from the v2.0.0.2 server to the v3.0 RC1 server we get an error when we click on the project name on the Active Project Areas page in the Web GUI. The error is 'Error fetching project area data' and clicking show details displays this: java.lang.NullPointerException
com.ibm.team.process.internal.service.web.ProcessRestService.contribToDTO(ProcessRestService.java:796) com.ibm.team.process.internal.service.web.ProcessRestService.projectAreaToDTO(ProcessRestService.java:634) com.ibm.team.process.internal.service.web.ProcessRestService.getProjectAreaByUUID(ProcessRestService.java:524) sun.reflect.GeneratedMethodAccessor1310.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) $Proxy791.getProjectAreaByUUID(Unknown Source) sun.reflect.GeneratedMethodAccessor1309.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:500) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1817) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1673) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1584) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:62) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:420) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) java.lang.Thread.run(Thread.java:811) Thanks George Jutras |
5 answers
You can't just simply copy the process source xml from 2.0.0.2 server to
3.0RC1 server. Let's suppose the process source xml you want to migration is in a project. So, what you need to do is: 1. Extract a process template from this project. (On eclipse client, in Team Artifact view right click this project and choose Extract Process Tempalte menu item.) 2. Export this process template to a zip file. (You can do it from web client or eclipse client.) 3. Import this process template from the exported zip file. (You can do it from web client or eclipse client.) 4. Create a new project with this imported process template. (You can do it from web client or eclipse client.) |
You can't just simply copy the process source xml from 2.0.0.2 server to Thanks, but I don't see 'Extract Process Template' when I right click on the project in the Team Artifact view. Any ideas why? |
You can't just simply copy the process source xml from 2.0.0.2 server to Thanks, but I don't see 'Extract Process Template' when I right click on the project in the Team Artifact view. Any ideas why? Could you please double check it? 'Extract Process Template' should be in Team Artifact view and Team Organization View. |
Geoffrey Clemm (30.1k●3●30●35)
| answered Nov 01 '10, 10:38 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Another place to find it is:
File -> Export -> Team_Process:Process_Template Cheers, Geoff On 11/1/2010 9:08 PM, ThomasYu wrote: gejjfmrwrote:You can't just simply copy the process |
|
Yes, that works for me.
Thanks George Another place to find it is: gejjfmrwrote:You can't just simply copy the process |
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.