How do I find out the context root? RTC 6.0.1
5 answers
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.
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.
I am getting the same issue, Any help on this issue ?
I am getting this issue in 6.0.6
Thanks
Deepan
Comments
A few things to check:
- Try to access the application's scr page (https://<server:port>/<app_context>/scr) and see if it returns xml output
- If /scr does not return xml output, review the application's log and see if the application starts up correctly. For example, if the problem is seen when going to /jts/admin or /jts/web, check jts.log and see if any error.
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.
