It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,461
×5,929
×2,351
×267

question asked: Aug 14 '14, 9:44 a.m.
question was seen: 5,688 times
last updated: Aug 15 '14, 10:52 a.m.

Related questions

RM (DNG) Upgrade to 5.0.1 not working

0
Dieter Paul (103●1●16●20) | asked Aug 14 '14, 9:44 a.m.
Following the interactive upgrade guide from 4.0.6 to 5.0.0 there is the following sequence (shorted)

  • Install Appilcations
  • Undeploy Applications from Websphere
  • Copy DB etc.
  • Run upgrade script (upgrade\rm\rm_upgrade.bat)
  • Deploy Applictions to WebSphere

The last step of these RM upgrade script request that the system is running. But this is impossible, because the deployment will be done later.

Please ensure servers hosting linked projects are online. Press [Enter] to continue to determine if RM server is online.
..

When we continue, the script asked for an admin user and we got the following Exception

Enter admin userId [ADMIN]
rtcadmin
Internal error: Cannot prompt for a password
java.lang.UnsupportedOperationException: Internal error: Cannot prompt for a password
        at com.ibm.team.repotools.command.AbstractCommand.promptSensitiveValue(AbstractCommand.java:323)

Is there anything we are missing?

Comments
Ralph Schoon commented Aug 15 '14, 10:33 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Consider to open a ticket with support. As far as I recall, the scripts don't require the server to be up. They actually do a lot of stuff that requires the server to be down.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Gail Burati (61●1) | answered Aug 15 '14, 10:52 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
 Hi Dieter Paul -

As you and Ralph noted, the upgrade process does require the servers to be down for almost all of the upgrade process. However, there is one last repotools command that should be run after the servers have been deployed and are up. You do not need the upgrade script to run the command but it is also fine to leave the script waiting until you have deployed and verified that your servers are up. The final repotools command is:

repotools-rm  -rmUpdateProjectBackLinksOnline adminUserID=<> adminPassword=<> repositoryURL=<public URI><RM context root>

I'm suspecting the error you are hitting is due to the server not being up when the script attempts to run the above command. Let me know if this helps or if you need more information!


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.