Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

JTS reports "Discovery resource for '/admin' cannot be accessed" after upgrade from CLM 4.0.3 to 5.0.2

Questions
Tags
Users
Badges
Ken Murphy
(103●34●36) Oct 27 '15, 12:22 p.m.
After upgrading from CLM 4.0.3 to 5.0.2, we are seeing the following diagnostic message for the JTS.  Everything seems to be functioning fine, but would like to know how to resolve this diagnostic.  Any ideas:

Application: the discovery resource at https://<jts_server>:9444/admin/rootservices for "/admin" cannot be accessed:
The returned HTTP status was 404
The response body was

SRVE0255E: A WebGroup/Virtual Host to handle /admin/rootservices has not been defined.

SRVE0255E: A WebGroup/Virtual Host to handle rubylake:9444 has not been defined.

IBM WebSphere Application Server

Application: the discovery resource at https://<jts_server>:9444/admin/scr for "/admin" cannot be accessed:
The returned HTTP status was 404
The response body was

SRVE0255E: A WebGroup/Virtual Host to handle /admin/scr has not been defined.

SRVE0255E: A WebGroup/Virtual Host to handle rubylake:9444 has not been defined.


0 votes

Comments
Lily Wang
Oct 27 '15, 8:23 p.m.
Starting in CLM 5.0.2, the LPA application is moved to Jazz Team Server so the "/admin" application should not exist. The command "repotools-jts -mergeLPAJTS" should be run by the upgrading script. Please check the log if there's any error reported with the mergeLPAJTS commmand.

Taki Nakajo
Oct 28 '15, 2:14 a.m.
I had a similar experience in the past. The best practice is applying the latest 5.0.2 iFix before upgrading since there are some defects. But it is too late to roll back your system, I'd like to check 2 things. Can you check if you see 'The LPA is merged before.'  instead of 'The LPA is migrated successfully' in .\IBM\JazzTeamServer502\server\repotools-jts_mergeLPAJTS.log?  or paste the last 10 lines in the log?  , and also check if you see the following 2 lines in .\IBM\JazzTeamServer502\server /conf/jts/teamserver.properties file:     com.ibm.team.lpa.storage.area.name=com.ibm.team.lpa.xxxxxxxxxxxxxxxx     com.ibm.team.lpa.storage.area.label=Jazz Lifecycle Project Administration

Ken Murphy
Oct 28 '15, 4:57 p.m.
Here is the contents of the repotools-jts_mergeLPAJTS.log, after some initial housekeeping messages:  2015-10-23 14:20:07,483 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties". 2015-10-23 14:20:07,784 CRJAZ1779I This server is configured as a JTS. 2015-10-23 14:20:09,014 CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false. 2015-10-23 14:20:10,736 CRJAZ1365I The server is attempting to connect to the following database: "//SQLRationalProd:1433;databaseName=jazz_ts;user=xxxxxxxx;password=xxxxxxxx" 2015-10-23 14:20:11,008 CRJAZ1364I The connection to the following database was successful: Db Product Name: Microsoft SQL Server   Db Product Version: 12.00.2269   Db URL: jdbc:sqlserver://SQLRationalProd:1433;databaseName=jazz_ts;user=xxxxxxxx;password=xxxxxxxx   Jdbc Driver Name: Microsoft SQL Server JDBC Driver 2.0   Jdbc Driver Version: 2.0.1803.100 2015-10-23 14:20:11,087 CRJAZ1971I The server is configured with:   Public URI: "https://<jts_server>:9444/jts" 2015-10-23 14:20:11,988 CRJAZ2523I Setting the global server rename state to false and the validation state to false. 2015-10-23 14:20:18,532 2015-10-23 14:20:18,533 The LPA is merged before. Is it safe to re-run the repotools-jts  -mergeLPAJTS command?  Is that what we should do?

2 answers
7,077 views
0 votes

2 answers

Permanent link
Taki Nakajo
(1.1k●29●46) Oct 28 '15, 8:45 p.m.
Hi Ken,

The message "The LPA is merged before." is the exactly same as I had before. I hope you can use this solution. 

1. Shutdown the Jazz Team Server 5.0.2.
2. backup \IBM\JazzTeamServer502\server\conf\jts\teamserver.properties file.
3. Remove following 2 lines and save it:
    com.ibm.team.lpa.storage.area.name=com.ibm.team.lpa.xxxxxxxxx
    com.ibm.team.lpa.storage.area.label=Jazz Lifecycle Project Administration
4. I assume the old 40X environment is under /IBM/JazzTeamServer40.
    a) go to the 502 folder: cd  /IBM/JazzTeamServer502/server
    b) run command: repotools-jts.sh -mergeLPAJTS jtsContextRoot=jts lpaContextRoot=admin oldJTSHome= /IBM/JazzTeamServer40/server/conf
5. If it finishes with "The LPA is migrated successfully" in repotools-jts_mergeLPAJTS.log, then you are good.
6. Start the Jazz Team Server 5.0.2, then verify JTS diagnostic to see if errors are gone. 

0 votes

Comments
Ken Murphy
Nov 06 '15, 10:18 a.m.
Taki, this solution did not work for us.  I've submitted a PMR.

Permanent link
Omar Jimenez
(11●2) Mar 03 '17, 5:58 p.m.

Ken Murphy, by a chance what was the final status on your PMR, we are dealing with the same thing here.
Thanks.

0 votes

Comments
Lily Wang
Mar 05 '17, 6:07 p.m.
Hi, before providing a solution, there's a few things you need to check, such as: - could you see "/admin" in "jts/admin > Server > Registered Applications"? - is there any error in the log of "repotools-jts -mergeLPAJTS " command? - could you see "com.ibm.team.lpa.storage.area.*" entries from teamserver.properties? I suggest you contact support or submit a new question with the above information.

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,623
× 2,382

Question asked: Oct 27 '15, 12:22 p.m.

Question was seen: 7,077 times

Last updated: Mar 05 '17, 6:07 p.m.

Confirmation Cancel Confirm