Technical data

13 Installing and Configuring the Netscape Enterprise Server Plug-In (NSAPI)

13-18 Administration Guide

Sample obj.conf File (Using a WebLogic

Cluster)

Below is an example of lines that should be added to obj.conf if you are using a

WebLogic Server cluster. You can use this example as a template that you can modify

to suit your environment and server. Lines beginning with

# are comments.

Note: Make sure that you do not include any extraneous white space in the

obj.conf

file. Copying and pasting from the samples below sometimes adds extra white

space, which can create problems when reading the file.

Note: If you are proxying to more than one WebLogic Server cluster from a single

Web server, each cluster must have a unique

CookieName parameter, and each

value should start with a unique string.

For more information, see the full documentation on Enterprise Server configuration

files from Netscape.

## ------------- BEGIN SAMPLE OBJ.CONF CONFIGURATION ---------

# (using a WebLogic Cluster)

# The following line locates the NSAPI library for loading at

# startup, and identifies which functions within the library are

# NSAPI functions. Verify the path to the library (the value

# of the shlib=<...> parameter) and that the file is

# readable, or the server fails to start.

Init fn="load-modules" funcs="wl_proxy,wl_init"\

shlib=/usr/local/netscape/plugins/libproxy.so

Init fn="wl_init"

# Configure which types of HTTP requests should be handled by the

# NSAPI module (and, in turn, by WebLogic). This is done

# with one or more "<Object>" tags as shown below.

# Here we configure the NSAPI module to pass requests for

# "/weblogic" to a cluster of WebLogic Servers.

Service fn=wl_proxy \

WebLogicCluster="myweblogic.com:7001,yourweblogic.com:7001,\