Steps to configure SunOne WebServer with Weblogic Server Proxy Plug-In

Before proceeding with Configuring SunOne WebServer with Weblogic server Proxy Plug-In we shall learn "What is a Weblogic Web Server Plug-In" and "How Web Server Plug-Ins Work with WebLogic Server"

What is a Weblogic Web Server Plug-In?

Weblogic Web Server plug-ins are modules that you add to your third-party Web server installation and configure to enable interactions between WebLogic Server and applications running on Apache HTTP Server, Sun One Web Server, and Microsoft Internet Information Server. 

Plug-ins usually use one of the two following architectures to enable applications running on third-party Web servers to use the capabilities of WebLogic Server.

-- As a load balancer for the Web server (proxying the requests to the backend servers)

-- To proxy requests for dynamic content to backend servers (the Web server can supply only static content and relies on WebLogic Server for dynamic content)

How Web Server Plug-Ins Work with WebLogic Server?

A user application running on a third-party Web server generates an HTTP request, which the Web server routes to the WebLogic Server plug-in. The plug-in sends the HTTP request based on configuration information that specifies a WebLogic Server cluster or instance. The targeted WebLogic Server instance processes the request and returns a response to the user application through the plug-in.

 

Steps to configure SunOne WebServer with Weblogic server Proxy Plug-In

Considering the SunOne WebServer https-Weblogic10.3 is already running on port 1080 we shall continue to configure SunOne WebServer with Weblogic Server Proxy Plug-In.

I am making use of SunOne WebServer 7.0 and Weblogic 10.3 for this Post and demonstrating to access the Weblogic Console via WebServer.

1. Copy the appropriate Weblogic Proxy plug-ins from Weblogic Installation to WebServer installation.

Windows: %WEBLOGIC_HOME%\server\plugin\win\32\proxy61.dll to %WEBSERVER_HOME%\plugins\lib\10.3\proxy61.dll

Solaris:  $WEBLOGIC_HOME/server/plugin/solaris/sparc/libproxy_61.so to %WEBSERVER_HOME%/plugins/lib/10.3/libproxy_61.so

Note: To differentiate the version of Weblogic proxy plug-ins, create a directory named with Weblogic version under %WEBSERVER_HOME%/plugins/lib

2. Load the Weblogic proxy plug-ins to WebServer https-Weblogic10.3 by adding the below lines immediately after Init fn="load-modules" shlib="j2eeplugin.dll" in  magnus.conf file located under %WEBSERVER_HOME%\https-Weblogic10.3\config.

Windows: Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="%WEBSERVER_HOME%/plugins/lib/10.3/proxy61.dll" 

Solaris: Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="$WEBSERVER_HOME/plugins/lib/10.3/libproxy_61.so"

Note: Replace WEBSERVER_HOME value as per your WebServer installation path. In my case it is C:\oracle\Sun\WebServer7. Make sure you use "/" instead in all path locations.

3. Edit the obj.conf located under %WEBSERVER_HOME%\https-Weblogic10.3\config to forward the HTTP requests received at WebServer from a user application to a Weblogic Server. See below.

Add the below configuration at the end of obj.conf file

<Object name="console" ppath="*/console">
Service fn="wl_proxy" WebLogicCluster="localhost:7001" DynamicServerList="OFF" KeepAliveEnabled="false" Debug="ALL" DebugConfigInfo="ON" WLLogFile="%WEBSERVER_HOME%/https-Weblogic10.3/logs/https-Weblogic10.3.log"
</Object>

OR

First add NameTrans fn="assign-name" from="*/console" name="console" immediately after AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true" 

and add the below configuration at the end of the obj.conf file

<Object name="console">
Service fn="wl_proxy" WebLogicCluster="localhost:7001" DynamicServerList="OFF" KeepAliveEnabled="false" Debug="ALL" DebugConfigInfo="ON" WLLogFile="%WEBSERVER_HOME%/https-Weblogic10.3/logs/https-Weblogic10.3.log"
</Object>

Note: Replace WEBSERVER_HOME & WebServer value as per your WebServer installation path. In my case it is C:\oracle\Sun\WebServer7 & https-Weblogic10.3. Make sure you use "/" instead in all path locations.

Also replace appropriate application redirects in place of console as in my example above.

4. Restart the https-Weblogic10.3 WebServer via WebServer admin console or via the scripts located under %WEBSERVER_HOME%\https-Weblogic10.3\bin.

[06/Jul/2011:17:27:17] info ( 9008): CORE1116: Sun Java System Web Server 7.0U5 B03/10/2009 22:30
[06/Jul/2011:17:27:17] info ( 9008): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_15] from [Sun Microsystems Inc.]
[06/Jul/2011:17:27:22] info ( 9008): HTTP3072: http-listener-1: http://localhost:1080 ready to accept requests
[06/Jul/2011:17:27:22] info ( 9008): CORE3274: successful server startup

5. Access the application using http://localhost:1080/console and you should be set.

Please do valuable comments/queries on this post.