Technical data

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

13-16 Administration Guide

Sample obj.conf File (Not Using a

WebLogic Cluster)

Below is an example of lines that should be added to the obj.conf file if you are not

using a 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.

You can read the full documentation on Enterprise Server configuration files in the

Netscape Enterprise Server Plug-In documentation.

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

# (no 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 WebLogic Server listening at port 7001 on

# the host myweblogic.server.com.

Service fn=wl_proxy WebLogicHost=myweblogic.server.com\

WebLogicPort=7001 PathTrim="/weblogic"

</Object>

# Here we configure the plug-in so that requests that

# match "/servletimages/" is handled by the

# plug-in/WebLogic.