I'm working on ways to consolidate all front end Web Servers through IHS and have multiple end points to Application Servers other than WAS.... dot NET, JBOSS, Tomcat.  Has anyone accomplished this on a large scale before?

I actually didn't understand the question completely

 

but from what i can understand, is something like profiles/multiple instances of IHS is the requirement ?

Can you explain it bit more ..

similar to the multiple profile approach.  If I want to have one binary set of IHS to various AppServers on the back end. (Tomcat, Jboss, other than WAS only). 
Would you have to configure multiple named httpd.conf. type files or is there a way anyone has done that with one or two?

Maybe you can use virtual server + reverse proxy (its like websphere plugin) but  works  with other webapps, for  virtual server if you use SSL you must add one virtual server for  each SSL domain, if you dont have SSL maybe you can use  virtual server with names

It's posible

publib.boulder.ibm.com/infocenter/wasinf...

hope this help ,if you need more help tell us.

regards

Rene,

Apart from some extra modules and (mandatory re-branding per the Apache License), IHS (IBM HTTP Server) is nothing but an Apache HTTP Server. Thus you have a number of options you can pursue here:

- create virtual hosts (each virtual host, usually a distinct DNS name, would point to one of your servers). Someone mentioned a reverse proxy, which isone option to do that, but you can also use the specific connector (JK 1.2 or something like that for Tomcat)
- use the same DNS name for all websites, but use either reverse proxy or the specific connectors to send different URIs to different back-end servers. Here you got to be extra careful not to use the same URI for two different app servers.
- anything you find in that regard about Apache Web Server is likely to work seamlessly in IHS
- a good test would be to point the WebSphere plugin to a different application server... I have never seen or heard anything about that before,  but I can't think of a reason why it shouldn't work - I think the plugin is quite "agnostic" about the application server, as long as it talks HTTP and gets back to it. Me thinks :-)

Let us know how it goes!

Cheers,
Alexei 

Thanks, I just got my sandbox going so I'll give it a try.