Problem with RTC just after installation
Hello!
I`ve got problem with RTC. After installation and starting server, I`m trying to get the localhost:9443/jazz/setup page to end installation. And it is written thera that Apche Tomcat/5.5.30 Error report HTTP Status 404 - /jazz/setup ...
description The requested resource (/jazz/setup) is not available.
I don`t know what to do and I`m not keen on this topics. The OS is Windows Server 2003, I have already installed "Java SE 6 Runtime Environment (JRE) Update 24".
Please, help me. What am I doing wrong? (I have already installed RTC for 4 times, always the same result)
I`ve got problem with RTC. After installation and starting server, I`m trying to get the localhost:9443/jazz/setup page to end installation. And it is written thera that Apche Tomcat/5.5.30 Error report HTTP Status 404 - /jazz/setup ...
description The requested resource (/jazz/setup) is not available.
I don`t know what to do and I`m not keen on this topics. The OS is Windows Server 2003, I have already installed "Java SE 6 Runtime Environment (JRE) Update 24".
Please, help me. What am I doing wrong? (I have already installed RTC for 4 times, always the same result)
5 answers
Jazz Foundation has changed the context root to /jts in the new version.
Can you try: https://localhost:9443/jts/setup instead?
Hope this helps,
Chemi.
On 2/23/2011 11:08 AM, mchol wrote:
Can you try: https://localhost:9443/jts/setup instead?
Hope this helps,
Chemi.
On 2/23/2011 11:08 AM, mchol wrote:
Hello!
I`ve got problem with RTC. After installation and starting server, I`m
trying to get the localhost:9443/jazz/setup page to end installation.
And it is written thera that Apche Tomcat/5.5.30 Error report HTTP
Status 404 - /jazz/setup ...
description The requested resource (/jazz/setup) is not available.
I don`t know what to do and I`m not keen on this topics. The OS is
Windows Server 2003, I have already installed "Java SE 6 Runtime
Environment (JRE) Update 24".
Please, help me. What am I doing wrong? (I have already installed RTC
for 4 times, always the same result)
Hi Chemi,
I have the same problem. Using https://localhost:9443/jts/setup endup with the same problem.
What could be wrong?
Thanks,
Dixie
HI
Are you using Tomcat as your app server? If so - you should see a window with the output from Tomcat. If this says something like:
INFO: Server startup in 81950ms
then you know your server is up and running.
If not, try opening a command window and run server.startup.bat and see if it reports any problems.
anthony
I was also having problem running Quality Manager. I did the following:
First, "Start the CML App Server" as an Administrator (Windows 7 user)
Then, if you want to access Quality Manager Setup, then use https://localhost:9443/qm/setup instead of https://localhost:9443/jazz/setup
HI
Are you using Tomcat as your app server? If so - you should see a window with the output from Tomcat. If this says something like:
INFO: Server startup in 81950ms
then you know your server is up and running.
If not, try opening a command window and run server.startup.bat and see if it reports any problems.
anthony
First, "Start the CML App Server" as an Administrator (Windows 7 user)
Then, if you want to access Quality Manager Setup, then use https://localhost:9443/qm/setup instead of https://localhost:9443/jazz/setup
Hi Chemi,
I have the same problem. Using https://localhost:9443/jts/setup endup with the same problem.
What could be wrong?
Thanks,
Dixie
HI
Are you using Tomcat as your app server? If so - you should see a window with the output from Tomcat. If this says something like:
INFO: Server startup in 81950ms
then you know your server is up and running.
If not, try opening a command window and run server.startup.bat and see if it reports any problems.
anthony
I ran into this exact same issue. I installed the evaluation topology onto a 64x Windows 7 machine and got a 404 when going to the URL provided in the setup guide. There were a lot of errors being thrown by Tomcat, however, such as "invalid scratch disk" and so on.
I shut down the server and then restarted, but I used "run as administrator" on my second attempt and it did not encounter these errors.
In short, the server needs to be started with administrator level permissions in Windows 7.