Repost; evil, I know. But perhaps people misconstrued my subject line and thought *I* was providing architecture tips...
I have been trying to determine the best way to architect an Internet (external) website and an intranet (internal) website. The requirements are simply that the two web applications may need to share EJB resources and some static content (word, excel, visio docs), but their look and feel (JSPs) will be completely different. It would be nice if they could also share some servlets too - ones that do basic work. I could use some helpful input and suggestions about the best, most secure, way to do this. The main problem we are dealing with is security. If we couple any of these web applications together too tightly someone may be able to sneak into our intranet site via the Internet site. This is what I'm currently looking at: Client - (DMZ) Internet Web Server on Machine A points to Appserver/EJB Container - (firewall) - Intranet Web Server on Machine B - Appserver/EJB Container on Machine B - Data storage Machine A and B would be MS2K Advanced Servers, and there may be another firewall between Machine B and the RDBMS. Has anyone attempted an implementation similar to this before? Thanks in advance for your feedback! ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
