How do I find out the context root? RTC 6.0.1
I used the CLM Web Installer for Windows to install RTC 6.0.1 on a Windows 2008 R2 machine. I run server.startup to launch the server, and then open my browser to go to https://servername:9443/jts/setup and I get a page that says "Context Root Not Found".
Any ideas?
|
5 answers
I suggest you to look at your log files, maybe something went wrong on startup. Also, verify your listening ports on your tomcat...
|
Hi John,
The context root being accessed is /jts... and jts is a default context root for JTS (refer to https://www-01.ibm.com/support/knowledgecenter/SSYMRC_6.0.1/com.ibm.jazz.install.doc/topics/t_s_server_installation_im.html). Unless a different context root was entered during the installation, I would expect /jts to be the context root for JTS application. %CLM601_DIR%\server\liberty\servers\clm\conf\application.xml has information about the application being deployed. It should also show application context roots as well. Can you access /jts/scr or any other applications such as /ccm/scr, /qm/scr, etc? If not, that could be that the applications are not deployed OR they did not start up successfully. You can check logs such as console.log, jts.log, etc in %CLM601_DIR%\server\liberty\servers\clm\logs and see if any errors. |
On Windows, try not to use a directory that's virtualized, such as "C:\Program Files", for the installation. You will have troubles with starting up the application with a non-administrative Windows account if you do so.
|
I just ran into the same problem. Accessing https://localhost:9443/jts/setup gave me "Context root not found" on a clean CLM 6.0.6.1 unpacked from plain Zip-file. The server.startup.bat script calls liberty.server.bat which in turn copies some files on the first run. This seems to have failed on my machine (for reasons I don't know).
In the end manually copying the content of server\liberty\clmServerTemplate to server\liberty\servers\clm solved the issue for me.
Comments
Ralph Schoon
commented Feb 23 '20, 7:40 a.m.
| edited Feb 23 '20, 8:05 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I have seen the server start not being successfull in cases where users keep installing in Program Files. The reason is that Windows limits what a user can do in the file system, unless they explicitely run the startup using run as Administrator.
|
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.