2 Replies Latest reply on Dec 7, 2001 2:50 PM by test

    Port 80 only ... Please

    Jon Newbie

      I would like to have one Web Server serving all my development needs. Those needs require Microsoft technologies (i.e. ASP) and Java technologies. Currently I have IIS redirecting my Jsp / Servlet requests to Tomcat. All ASP and simple html requests are not redirected, but handled by IIS directly.

      I don't see why JBoss, being an Applications Server working in a tier behind the Web Server tier, couldn't have it's workload provided to it by IIS, as tomcat does.

      To be honest, a perfect combination would be IIS redirecting Java related work to the JMX infrastructure, and JMX dolling out JSP / Servlets to Tomcat, JMS messaging to JBoss (JBossMQ), JTA/JTS transactions to JBoss (JBossTX), etc...

      Is this a good idea, just hasn't been done yet?
      It is a good idea and has been done. Here is how ...
      Am I missing something, like 'How is IIS going to know an EJB message?'

      Admittedly, I have plenty of Java experience (Java applications, JSP, and Servlets), but am only now delving into EJB's (and other).

      I welcome ANY constructive comments. Thank you.

        • 1. Re: Port 80 only ... Please
          J. Wolfgang Kaltz Novice

          > OR
          > Am I missing something, like 'How is IIS going to
          > know an EJB message?'

          This one is the right answer :)
          The point is, IIS is a web-server, meaning it speaks only HTTP. That's why you need servlets (Tomcat) to be able to execute Java code in your web-server.

          Bottom line, if you want to access ejbs from your browser, you need to either write a servlet which is your gateway to your ejbs (normally, your servlet handles your GUI so it is the one making ejb business calls)
          Or, you have an HTTP protocol which can encapsulate remote server calls, this is the goal of SOAP (but I don't know the details of SOAP)

          • 2. Re: Port 80 only ... Please
            test Newbie

            SOAP is rpc over http (or smtp theoritically). It allows you to make RPC calls using http as transport thus avoiding firewall issues.

            Apache/IIS can redirect http calls to Tomcat(servlet) which in turn can access EJBs running on JBoss or any other app server.

            Or you can define RPC interface on top of EJB interface (using WSDL/SOAP) and let soap rpc router handle client requests and reroute them to EJBs.