It's all about the answers!

Ask a question

How to upgrade DM from 5.0 to 5.0.2 ?


Bruno Di Giandomenico (501124) | asked Apr 15 '15, 5:36 a.m.
 We have had some problems in finding out the correct instructions for the subject upgrade, also because there is problem on Rhapsody 8.1.2

2 answers



permanent link
Bruno Di Giandomenico (501124) | answered Apr 15 '15, 6:00 a.m.
 Sorry, my question was truncated. 
We came from a DM 5.0 and Rhapsody 8.1 with DM extension 5.0 working installation.
I was meaning to say that if you try to follow Rhapsody 8.1.2 help instructions you will be referred to an empty page.
So I used 8.1.1 instructions.
Our installation uses Websphere, so we upgraded the WAR images of DM, VVC, VVCHELP, and then we run the upgrade scripts. Apparently on the server all is fine, the previously saved project are visible, with some small problems (more later).
We did not run the scripts such as this one

repotools-vvc -vvc_online_migrationCommand credentialsFile=credentials.txt fromVersion=5.0 logLevel=DEBUG logPort=52000

because it is not clear whether they are to be run, it depends which source you use.

Anyway, if we tried to run these scripts, what comes out is the following, with problems on the credentials.txt file:
(sorry, but it is partially in Italian)

2015-04-10 16:50:03,578 Repo Tools
2015-04-10 16:50:03,578 java.version=1.6.0
2015-04-10 16:50:03,578 java.runtime.version=pwa6460sr16fp1-20140706_01 (SR16 FP1)
2015-04-10 16:50:03,594 Predisposizione tramite "C:\Program Files\IBM\JazzTeamServer\server\conf\vvc\provision_profiles".
2015-04-10 16:50:03,625 repotools-vvc -vvc_online_migrationCommand credentialsFile=credentials.txt fromVersion=5.0 logLevel=DEBUG logPort=52000
2015-04-10 16:50:03,625   Configuration Management - Web Libraries, Version 5.0.2 (VVCvvc-502-I20141021_2130)
  Jazz Foundation - Core Libraries, Version 5.0.2 (RJF-I20141028-1603)
  Configuration Management, Version 5.0.2 (VVCvvc-502-I20141028_1747)

2015-04-10 16:50:03,656 The com.ibm.team.vvc.server.core bundle's plugin.xml file contains a <component> element with the id attribute value com.ibm.team.vvc that is not unique.
2015-04-10 16:50:03,688 VVCOnlineMigrationCommand ha inaspettatamente trovato il parametro richiesto "adminUserId" come null. Controllare la dichiarazione di estensione com.ibm.team.repotools.rcp.commands nel file plugin.xml.
2015-04-10 16:50:03,688 VVCOnlineMigrationCommand ha inaspettatamente trovato il parametro richiesto "adminPassword" come null. Controllare la dichiarazione di estensione com.ibm.team.repotools.rcp.commands nel file plugin.xml.
2015-04-10 16:50:03,688 VVCOnlineMigrationCommand ha inaspettatamente trovato il parametro richiesto "certificateFile" come null. Controllare la dichiarazione di estensione com.ibm.team.repotools.rcp.commands nel file plugin.xml.
2015-04-10 16:50:03,688 VVCOnlineMigrationCommand ha inaspettatamente trovato il parametro richiesto "repositoryURL" come null. Controllare la dichiarazione di estensione com.ibm.team.repotools.rcp.commands nel file plugin.xml.
2015-04-10 16:50:03,688 VVCOnlineMigrationCommand ha inaspettatamente trovato il parametro richiesto "smartCard" come null. Controllare la dichiarazione di estensione com.ibm.team.repotools.rcp.commands nel file plugin.xml.
2015-04-10 16:50:03,703 CRJAZ1398I Caricamento delle credenziali da 'credentials.txt'.
2015-04-10 16:50:04,982 CRJAZ1357E Il comando repotools non è riuscito ad accedere al seguente server: https://jtsserver.aeronautica.alenia.it:9443/dm. Verificare le credenziali di accesso.
2015-04-10 16:50:04,982 Failed on team server JFS failure, ensure server is up.
2015-04-10 16:50:04,982 
java.lang.RuntimeException
at com.ibm.team.vvc.repotools.commands.migrate.VVCOnlineMigrationCommand.init(VVCOnlineMigrationCommand.java:53)
at com.ibm.team.vvc.repotools.commands.migrate.VVCOnlineMigrationCommand.execute(VVCOnlineMigrationCommand.java:135)
at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:68)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:816)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:891)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
2015-04-10 16:50:04,982 CRJAZ1728E Si è verificato un errore di Repository Tools. Per ulteriori informazioni, consultare questo file di log: C:\Program Files\IBM\JazzTeamServer\server\repotools-vvc_vvc_online_migrationCommand.log

We have also installed the DM extension on one of our PCs, where Rhapsody 8.1.2 is installed.
There is no way we have been able to connect Rhapsody to DM, we keep having the message "400 Bad Request" whenever we try to insert our credentials.

There is something fishy there, as we get the same "Bad Request" message whatever user id we enter, whether they are DM user ID or false / invented ID. That means that Rhapsody DM extension do not even bother to look up to the DM server.

The questions are the following:
1) is there something wrong with the upgrade procedure we followed ? Were we right in not executing the repotools-vvc etc. script ? I hope I inserted all the needed details
2) any advice on the Rhapsody issue ?

Can somebody help or is a PMR needed ?

Thanks in advance

permanent link
Francois-xavier Panaget (58914) | answered Apr 15 '15, 8:15 a.m.
Hi Bruno,

I do see the 5.0.2 upgrade steps in the following pages:
http://www-03preprod.ibm.com/support/knowledgecenter/SSB2MU_8.1.2/com.ibm.rcam.install.doc/topics/t_upgrade_dm_single.html?lang=en
or
 help  http://www-03preprod.ibm.com/support/knowledgecenter/SSB2MU_8.1.2/com.ibm.rcam.install.doc/topics/t_upgrade_dm_distributed.html?lang=en

The command repotools-vvc.bat -vvc_online_migrationCommand credentialsFile=credentials.txt fromVersion=<previous_version> logPort=52000 logLevel=DEBUG is definitely needed for the upgrade to be complete.
It needs to be run before the DM upgrade otherwise the DM upgrade is likely going to fail.

Looking at your error it seems to be related to the authorization. In the helps there is the following tip:
If this repotools-vvc command stops immediately with an authorization error, verify that the server is running and that the user Id and password in the credentials file are correct.
If this does not help, I would recommend you to open a PMR.

Regards,
François


Comments
Bruno Di Giandomenico commented Apr 15 '15, 12:00 p.m.

 Thanks for the answer. We have tried a number of times to run the batch file, but the results are always the same as above.

We wonder if there is a particular way to write the credentials.txt file, i.e. the use of some character such as " or ' or <.
The example given is pretty clear and seems clean but the nagging feeling that something is wrong remains.
As of now all servers (Oracle, WebSphere and JTS) are running, so unless you can advice on a different server which I cannot imagine right now, probably it is best to follow your advice about opening a PMR.

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.