There is an IHS instance(we want to use only one instance to route the requests) and two different hostname point to the IHS's 80 port
We want to use name based virtual host to route the requests from different hostname onto different WAS application
here is the virtual host configuration fragment
CustomLog "logs/example1-access_log" common
CustomLog "logs/example2-access_log" common
I expected that
when user access www.example1.com/app/index.html,the request can be routed onto WAS server configurated in plugin-cfg-example1.xml
when user access www.example2.com/app/index.html,the request can be routed onto WAS server configurated in plugin-cfg-example2.xml
But the actual result was:
access both www.example1.com/app/index.html and www.example2.com/app/index.html,the requests were routed onto WAS server configurated in plugin-cfg-example2.xml
Seems that the httpd.conf can have only one active WebSpherePluginConfig directive,and the last one will replace the previous
Is there any alternative approach to achieve this(do not start two instances with different httpd.conf)?
Any help will be appreciated
Pinned topic Name based virtual host and WebSpherePluginConfig
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-05T14:11:07Z at 2012-11-05T14:11:07Z by Sunit
Re: Name based virtual host and WebSpherePluginConfig2012-10-15T15:15:44ZThis is the accepted answer. This is the accepted answer.Not possible, it should be rejected in virtualhost context but isn't.
If you want it vhost-aware, you have to deploy to specific host aliases in WAS and re-gen a single plugin-cfg.xml
Sunit 100000DWFV209 Posts
Re: Name based virtual host and WebSpherePluginConfig2012-10-15T17:19:14ZThis is the accepted answer. This is the accepted answer.Try the following:
1. In WAS admin console when you bind the application to virtual_host instead of binding it to *:80 or *:443 bind it to www.example1.com:443 and www.example1.com:443 for the first app and do the same thing for second app with the second hostname and IP address.
Regenerate the plugin-cfg.xml and restart everything
Re: Name based virtual host and WebSpherePluginConfig2012-10-16T09:06:45ZThis is the accepted answer. This is the accepted answer.
- Sunit 100000DWFV
I did what you said,bind www.example1.com in virtual_host in the WAS1 console and did the same thing to WAS2,
regen plugin on both server,replace the plugin configuration file,finally restart WAS1,WAS2 and IHS server,
But I could not access the app on both WAS1 and WAS2 through hostname www.example1.com & www.example2.com
Sunit 100000DWFV209 Posts
Re: Name based virtual host and WebSpherePluginConfig2012-11-05T14:11:07ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK