It's all about the answers!

Ask a question

Problems finalizing 5.0.2 upgrade with /admin association

Michael Johnson (44718) | asked May 20 '15, 3:00 p.m.

After the upgrade of RTC 4.0.6 to 5.0.2, I get the following error in Diagnostics:

Application:  The discovery resource at https://my.rtc.server.url for "/admin" cannot be accessed:  the returned HTTP status was 404.
The response body was error 404:  No target servlet for uri: /admin/rootservices......

I get the same error for uri:  /admin/scr

I understand that there are several steps that remove the association of RM and JTS to the /admin.  I did all of the steps, however, one did not take. 

My questions are:

1.  does anyone know which repotools step needs to be run again?

2.  my system is running fine for the most part (however, I cannot search LDAP for users - seemingly because of this error.  Can I just run all of the repotools commands again without causing more damage?

Thanks in advance.


Accepted answer

permanent link
Martha (Ruby) Andrews (3.0k44351) | answered May 21 '15, 3:16 p.m.
I agree with Donald's answer -- check to see if something happened with the mergeLPAJTS commmand. In addition, a word of caution:

In general, avoid running migration commands more than once unless/until you understand whether there was an error in running it the first time.

In particular, there was a bug in the logic for finalizing RM migration that can cause data loss if the script is run more than once.  See
for details. This is fixed in 5.0.2 iFix003 and later.

If you are considering running migration commands more than once, install the iFix before doing so.

Martha (Ruby) Andrews
Jazz Foundation L3 Development Team LEad.
Michael Johnson selected this answer as the correct answer

3 other answers

permanent link
Kegham Anbarjian (231711) | answered Oct 14 '16, 11:56 a.m.
edited Oct 14 '16, 12:20 p.m.
Hello all,

I am experiencing the same condition. I upgraded from RTC 4.0.3 to RTC 5.0.2 with iFix 017 applied. All upgrade scripts executed without errors.  When I click on Manage Projects (Administration -> Manage Lifecycle Projects), I get the following error:

Error 404: No target servlet configured for uri: /admin/web/projects/new

and the URL shows https://sever:port/admin, which seems wrong.

When I manually type the URL https://ttps://sever:port/jts/lpa, it brings up the LPA page, which make me believe that the LPA module is up and running. I am not sure if it's safe to run the subcommand -mergeLPAJTS again.

In the repotools-jts_mergeLPAJTS.log, the subcommand for -mergeLPAJTS looks as follows:
repotools-jts -mergeLPAJTS jtsContextRoot=jts lpaContextRoot=admin oldJTSHome=C:\IBM\JazzTeamServer\server\conf

Is the value lpaContextRoot=admin correct? Any suggestions on how to fix this?

Thanks in advance,

permanent link
Donald Nong (14.5k614) | answered May 20 '15, 8:06 p.m.
The jts_upgrade script is supposed to migrate the LPA for you. Check the log file and see if any errors reported there. Or you can try to run the sub command directly.
Runs the -mergeLPAJTS command that migrates the Lifecycle Project Administration (LPA) storage areas, indexes, and registrations to Jazz Team Server. Starting in CLM version 5.0.2, the LPA application is moved to Jazz Team Server.

For the LDAP search issue, I am not quite convinced that it's related to the LPA issue as LDAP search is handled by JTS alone. I suggest you open a new topic and explain the details about it.

permanent link
Alexandre Stegani (8664) | answered May 20 '15, 6:17 p.m.
Hi Michael,

As far as I know, the "/admin" application no longer exists in 5.0.2, which can explain that error. The "Lifecycle Project Administration" application is now acessble by using "https://server:port/jts/lpa/".

Could you please just check if the LPA application is up and running by using the URL above?

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.