Netscape

There are two stages to configuring Netscape to work with WebLogic servers or server clusters. First, you must install the plug-in. This is simplein essence, you just copy over the library file from your WebLogic distribution and tell Netscape where to find it. Second, you must define the circumstances in which Netscape uses the installed plug-in to pass requests along. Both of these tasks are accomplished by editing the Netscape configuration file, obj.conf .

Plug-ins exist for Netscape servers installed on both Unix and Windows platforms. The Unix plug-in is a shared object file, with a ".so" extension. The Windows plug-in is a dynamic linked library file, with a ".dll" extension. The exact name of the file varies with the release, so you should check your documentation or the BEA Web site to be sure. However, at the time of this writing the appropriate libraries were:

 \BEA\weblogic6.1\bin\proxy6.1 

for Windows and

 /BEA/weblogic6.1/lib/<Unix OS Vendor>/libproxy.so 

for Unix, where < Unix OS Vendor > was one of Solaris, RedHat Linux, AIX, or HP-UX. Copy the library file that is appropriate for your operating system to the plugins directory of your Netscape Enterprise Server installation. For example, this might be something like:

 cp libproxy.so /usr/local/netscape/plugins 

Next, you need to modify the obj.conf file. As mentioned earlier, there are two sets of modifications to be made. First, you tell Netscape to load the library file that we just copied over:

 Init fn="load-modules" funcs="wl_proxy,wl_init"\ shlib=/usr/local/netscape/plugins/libproxy.so Init fn="wl_init" 

Second, you tell Netscape what sort of requests it will be relaying and where to find the WebLogic servers to which it will be relaying them. A common configuration option is to distinguish static page requests from dynamic requests by their location in the URL space. This is accomplished with the < Object > container directive. In the example below, all URLs containing the string "/dynamic/" are being associated with the WebLogic service.

 <Object name="dyn" ppath="*/dynamic/*"> </Object> 

Finally, you complete the configuration by placing the directives that tell Netscape how to locate the WebLogic server (notethat's "server," not "cluster") to which it will be relaying requests between the object directives.

 <Object name="dyn" ppath="*/dynamic/*">       Service fn=wl_proxy \       WebLogicHost=myserver.com \       WebLogicPort=7001 </Object> 

If you are proxying to a cluster, the configuration might look like this.

 <Object name="dyn" ppath="*/dynamic/*">  Service fn=wl_proxy \  WebLogicCluster="cluster1.com:7001,cluster2.com:7001" </Object> Service fn=wl_proxy WebLogicHost=cluster1.com WebLogicPort=7001 

You need to tell Netscape under what circumstances it is to relay client requests to the WebLogic server.