Websphere 8.5 DefaultApplication not available
Hello!
I installed WebSphere 8.5 on Windows.
I created a new profile,
with the default applications (DefaultApplication, ivtApp, query) included.
No apparent errors. But when I try to get to the DefaultApplication
(or any application), I get 404 (not found) errors. For example:
curl -k https://hostname:9443/
Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri: /
curl -k https://hostname:9443/jts/setup
Error 404: ProxyServlet: /jts/setup
curl -k https://hostname:9443/jts
Error 404: ProxyServlet: /jts
I am new at WebSphere. Any pointers are appreciated! Thanks in advance!
My ultimate goal is to install Rational Quality Manager.
4 answers
It sounds like you have not installed the RTC applications yet.
You will need to use the WAS administration console to install the them. See below for link to instructions.
The administration console uses a different port than the applications.
I believe the default ports are as follows
Administrative console port: 9061
Administrative console secure port: 9044
You can verify by opening the AboutThisProfile.txt found in the logs directory of the WAS profile.
...\WebSphere\AppServer\profiles\Profile1\logs
Link to the information center with the instructions deploying the applications:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/t_deploy_was.html&scope=null
In case you are so inclined here is the link to setting up with Jython
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/c_admin_was_jython.html&scope=null
Have you set the JAZZ_HOME variable in WebSphere as outlined in Setting up WebSphere Application Server? That error usually means WebSphere has not been configured correctly for CLM, most commonly because JAZZ_HOME has not been set. I'd suggest following everything outlined in that InfoCenter topic and you should be ok. Hope it helps,
Comments
Comments
1. Validate which transports the server instance is listening to. It may be a port other then 9443
2. Check the virtualHost configuration to ensure the above transports have been configured as aliases
3. Check to make sure the server instance and applications have been started.
Comments
Karl Weinert
JAZZ DEVELOPER Sep 11 '13, 11:29 a.m.1 vote
Mingzuo Shen
Sep 11 '13, 12:42 p.m.Karl Weinert
JAZZ DEVELOPER Sep 11 '13, 12:51 p.m.1 vote