This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
WebLogic does not provide all of the proxying services of a full blown Web Server (without writing it yourself). Furthermore, even you could easily do this, why would you want to? If you want to separate the Web Container from the EJB Container then the request for pages should go directly to the Web Container or a Web Server like Apache or iPlanet. Therefore should be: Web Server (proxy) -> Tomcat (Servlet/JSP) -> WebLogic (EJB) Not: WebLogic (proxy) - > Tomcat (Servlet/JSP) -> WebLogic (EJB) I think you need to explain your reasoning for doing this before we can effectively help you.
Joined: Feb 19, 2002
Thanks Chris. I was asked to find out that if it is feasible to do so. Now we are going to use apache/tomcat as the webserver and jsp/servlet container and weblogic 7.0 as the EJB container . So appreciate if you could tell me how to configure the tomcat server in order to do it. Thanks.
Just have all the EJB lookups from Tomcat use WebLogic server's jndi - use WLInitialContextFactory and the provider url to point to the WLS server. I've never experimented with a config like this, so I'm not sure if you would get proper security credentials forwarded from Tomcat to WLS. I guess you'd at least have to set up some consistent security store and implement security Authentication/Authorization providers for both servers so they'd have the same user base, role mappings, etc. Why not just let WebLogic do both jobs. [ October 24, 2002: Message edited by: Dave Landers ]