Error during RTC setup: SRVE0255E: A WebGroup/Virtual Host to handle /jts/admin has not been defined.
Hello,
I was trying to install RTC 4.0.4 on WAS 8.5.0. I followed the interactive installation guide on http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Froadmap_form.html
When logging on the https://wasrtc02:9043/jts/admin I get the error massage:
I was trying to install RTC 4.0.4 on WAS 8.5.0. I followed the interactive installation guide on http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Froadmap_form.html
When logging on the https://wasrtc02:9043/jts/admin I get the error massage:
SRVE0255E: A WebGroup/Virtual Host to handle /jts/admin has not been defined.
according to Integrated Solutions Console jts is running:
3 answers
Check which virtual host your application (jts) is using.
Go to the virtual host and check it's host alias list, and ensure the port that you are connecting to is in the list.
Make sure the server you are connecting to is listening on that port.
If you're using a plugin, then there is an extra step, but the principle is the same.
You're using the wrong port. It should be 9443 if you took everything by default. So use https://wasrtc02:9443/jts/admin instead of https://wasrtc02:9043/jts/admin
To double check, log on to WAS admin console (or Integrated Solutions Console as you call it) and navigate to Environment > Virtual hosts. You should see two entries there - admin_hosts and default_host. Select either of them and examine "Host Aliases" for the associated ports.
Next navigate to Applications > WebSphere enterprise applications > jts and examine Virtual hosts under Web Module Properties. You want you web application to be mapped to "default_host" only unless you know a specific reason not to.
Finally, in the SystemOut.log file, you should be able to locate such a line as "WSVR0200I: Starting application: jts" (or jts_war depending the name you gave when deploying the web application). A few lines down, and just above "WSVR0221I: Application started: jts", in the same log file, you should see a line like this:
com.ibm.ws.webcontainer.VirtualHostImpl addWebApplication SRVE0250I: Web Module null has been bound to default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443].
In the sample above, 9080 and 9443 are the ports that you can use to access the web application on the WAS profile directly, and 80 and 443 with IHS rerouting.
To double check, log on to WAS admin console (or Integrated Solutions Console as you call it) and navigate to Environment > Virtual hosts. You should see two entries there - admin_hosts and default_host. Select either of them and examine "Host Aliases" for the associated ports.
Next navigate to Applications > WebSphere enterprise applications > jts and examine Virtual hosts under Web Module Properties. You want you web application to be mapped to "default_host" only unless you know a specific reason not to.
Finally, in the SystemOut.log file, you should be able to locate such a line as "WSVR0200I: Starting application: jts" (or jts_war depending the name you gave when deploying the web application). A few lines down, and just above "WSVR0221I: Application started: jts", in the same log file, you should see a line like this:
com.ibm.ws.webcontainer.VirtualHostImpl addWebApplication SRVE0250I: Web Module null has been bound to default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443].
In the sample above, 9080 and 9443 are the ports that you can use to access the web application on the WAS profile directly, and 80 and 443 with IHS rerouting.