Problems migrating Beta 1 to Beta 2 (Linux/DB2)
I recently upgraded my Jazz Team Server from Beta 1 to Beta 2 and no longer see my user lists or projects.
I used the Installation Manager on my Linux server. I choose the option to upgrade my existing package to Beta2. It appeared to run successfully. When I tried to log into the server afterwards, my userid id no longer worked. I had to use the ADMIN account. Once logged in as ADMIN, I could see that the server was up and connected to my DB2 database on the same server. I noticed that the tomcat users file had been reset and none of my previous projects are visible. Is there some other steps I need to perform to complete the migration? |
6 answers
I believe this may help:
https://jazz.net/downloads/rational-team-concert/releases/1.0.1.1?p=upgrading Look under the section "Copying the required configuration files from a previous server installation" You will also find this in the help under: Installing and upgrading -> Installing Rational Team Concert -> Upgrading to Rational Team Concert 2.0. |
|
Hi Adrian,
I had already been through that information. In my case, I am upgrading from 2.0 Beta 1 to 2.0 beta 2. Because I used the Installation Manager, I would have expected the configuration files to be backed up (just like the document says it backs up files from 1.0 to 1.0.1). I don't think it did. It should though. In the end, it is not that big a deal right now. I only had 10 users in the tomcat-users.xml file, so I was able to recreate it manually. The bigger issue is that I can not see any of the projects I created in Beta 1, nor can I create new projects with Beta 2. The server page on the web UI confirms that I am connected to my DB2 database, and does not report any errors. Is there some sort of migration that I need to perform in order for the data in DB2 to be used by Beta 2? This is the issue that I am most concerned with. Jeff |
|
Jeff
I believe that information applies if you are updating any existing server installation. The problem with doing it as part of the IM install is detecting and having access to all the various directorys and files. We froze the repository schema for 2.0 in M3. Since Beta 1 was based on M2 and Beta 2 was based on RC1 you will need to migration your repository. Did you do that? |
No, not yet. Where do I find that information? |
|
It should be under the "Migrating" topic in the online help. Here's a link to the in-development help that should pretty much match what's in the Beta 2 build you have:
https://jazz.net/help-dev/rational-team-concert/index.jsp |
|
I realized that the RTC Beta 2 installation was try to access the Derby server. I though I has alrady fixed that. In any case, I went back and reconfigured the Jazz server to look for the DB2 database.
With the teamserver.properties file change, I tried to connect via the Web UI. After logging in, I see the following error message on the Server page: Status Summary: Error fetching server status information. Database Status: Connected Server License: Error fetching server status information Database Status: The database is configured correctly. Here are the details of the error message: java.lang.Exception com.ibm.team.repository.common.transport.ServerHttpUtil.serializeError(ServerHttpUtil.java:1053) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleException(AbstractTeamServerServlet.java:1149) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1541) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1465) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) 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:803) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) 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:210) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) 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:685) java.lang.Thread.run(Thread.java:810) |
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.