BEA WebLogic 6.1

Installing BEA WebLogic

Follow the installation instructions given at:

    http://e-docs.bea.com/wls/docs61/install/instcon.html 

Once this is done, you should have WebLogic running on port 7001 (the default).

Then, add an application to your "example" server using the Quick-Start instructions in the samples/examples/examples.html file in your WebLogic installation. For this example, we installed the jsp examples in samples/examples/jsp.

Verify that you can access the application you have installed, for example, by going to:

http://myserver:7001/examplesWebApp/HelloWorld.jsp.

Integration with Zeus Web Server

Ensure that your WebLogic server is correctly installed and functioning before proceeding.

WebLogic supplied an NSAPI 'bridge' with their product. The aim of this bridge was to proxy/gateway connections received by the web server through to WebLogic. In versions of Zeus Web Server prior to 4.0, it was recommended to use this bridge.

With Zeus Web Server version 4.0 and later, the Gateway feature provides a simpler and faster means of integration. The Gateway feature allows mapping of a portion of the URL tree to a remote server, in this case, WebLogic.

First, create a Virtual Server within the Zeus Admin Server to receive requests. Go to the Gateway configuration page for this Virtual Server, listed in the lefthand configuration menu under URL mapping. Enable support by checking the radio button, and enter the following settings:

    * Requests to redirect: /examplesWebApp
    * Web Server: localhost
    * Port: 7001 

If you have changed your WebLogic defaults, you will need to change the port number from 7001. Zeus Web Server and WebLogic need not be on the same machine; if they are not, enter the hostname where WebLogic is running in the 'Web Server' box.

Enable the "Rewrite HTTP redirects" to ensure that any HTTP redirects issued by the weblogic server are correctly handled.

In version 4.0 of Zeus Web Server, you will need to add an extra configuration key. Edit the file:

    %ZEUSHOME%/webadmin/conf/virtual_servers/sites/vserver

Where %ZEUSHOME% is the installation path for Zeus (typically /usr/local/zeus)and vserver is the name of the virtual server you are configuring. Add the following line to the file:

    modules!gateway!rewritelocation yes

Apply your changes and commit them. All requests for /examplesWebApp will now be gatewayed to WebLogic.

Testing your WebLogic installation

    * http://server:port/ will give access to your Zeus hosted website.
    * http://server:port/examplesWebApp/ will be forwarded on to the backend WebLogic server. 

For example, you can access the HelloWorld.jsp page as http://server:port/examplesWebApp/HelloWorld.jsp.

Where to go next? Proceed to http://www.weblogic.com/docs/techstart/.

Benefits

The embedded web server in the WebLogic product is not suitable for high traffic loads, and lacks the configuration flexibility that a dedicated webserver product provides. By placing the Zeus Web Server in front of a WebLogic cluster, much of the HTTP load can be taken off the WebLogic cluster and a demonstrably more responsive, more reliable service will result.
Clustered WebLogic Installation

If you wish to use a WebLogic 'cluster' then you will need to use the NSAPI bridge instead of the Gateway feature. You should make use of the instructions here: http://support.zeus.com/products/v3/weblogic.html.

Content Manager [Administrator] 10 November 2005