Introduction

As we have discussed, WebLogic is designed to service requests for the various types of J2EE resources. It is not, in and of itself, an HTTP server. This chapter discusses the options available for handling HTTP requests in the context of a WebLogic server installation.

The WebLogic server distribution includes a servlet that will enable WebLogic to recognize and service requests for static HTTP. In the absence of a legacy system, this is probably the best choice for administrative purposes. Because the HttpClusterServlet is a native WebLogic application, it can be controlled entirely from within the WebLogic console. The same is not true of the other three options.

If, for reasons of legacy application support, you need to get WebLogic to work cooperatively with a third-party HTTP server, the odds are good that you can. The WebLogic distribution includes software modules that extend the functionality of the three most popular HTTP servers, namely Apache, IIS, and Netscape.

The plug-ins serve two purposes:

  • They serve requests for static HTML pages. It is also possible to configure the HTTP servers in such a way that they will also handle requests for CGI. However, for performance reasons this is not recommended.

  • They route requests for dynamic content to individual WebLogic servers or to WebLogic clusters.



BEA WebLogic Server Administration Kit
BEA WebLogic Server Administration Kit (Prentice Hall PTR Advanced Web Development)
ISBN: 0130463868
EAN: 2147483647
Year: 2002
Pages: 134
Authors: Scott Hawkins

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net