The Apache Tomcat project implemented the ajp* protocol with an NSAPI plugin for Netscape Enterprise Server. This NSAPI should also work with iPlanet Web Server, Sun ONE Web Server, Sun Java System Web Server, and the newly open sourced Open Web Server. The Tomcat ajp* NSAPI allows (Sun|Open) Web Server to act as the HTTP front-end and load balancer for Tomcat (similar to mod_jk).
It's very much worth noting that Tomcat has a HTTP Connector that allows Tomcat to expose an HTTP interface rather than a ajp* interface. By using this connector with (Sun|Open) Web Server's built-in HTTP Reverse Proxy. This option nicely lets Web Server use nothing but native Web Server code, Tomcat use nothing but native Tomcat code, and the deployment still derive the traditional benefits of a high performance HTTP engine serve static content and a high-performance Java engine serve the dynamic Java content.
I would be remise if I neglected to point out that the same Reverse Proxy capabilities of (Sun|Open) Web Server allow a similar deployment with ANY HTTP compliant origin server including Sun's GlassFish Server, Microsoft's IIS with .Net apps, SAP, Oracle, Web Logic, etc. In some cases those origin servers also provide connectors that may offer more health check options, more load balancing, etc. In most cases, however, the built-in Reverse Proxy provides high quality connectivity between (Sun|Open) Web Server and your App Server of choice regardless of whether it's Java, .Net, or something else).
Post new comment