Installation guide
Installing and configuring an iPlanet Web server plug-in
44
EAServer
• Context paths that inform the Web server which client requests to forward
to the redirector. See “Defining context paths” on page 45.
•An
EASProxy object that specifies which HTTP methods are forwarded to
the redirector. See “Adding the EASProxy object” on page 45.
Adding location information
The redirector plug-in is a Netscape Application Programming Interface
(NSAPI) extension.
Table 4-2: Web server plug-in library names
To load and initialize the plug-in, edit either the obj.conf file, and add the
locations of both the plug-in file, and the redirector configuration file, which is
used by the redirector to map incoming client requests to EAServer HTTP
listeners.
Warning! Make a backup of obj.conf, and when editing the file, do not include
any extra spaces, tabs, or return characters.
Add these lines at the top of the configuration file, obj.conf, located in the
config subdirectory of your Web server installation:
Init fn="load-modules" shlib="PLUGIN_PATH" funcs="conn_init,conn_service"
Init fn="conn_init" configfile="CONFIG_FILE_PATH"
Replace PLUGIN_PATH with the complete path and name of the NSAPI plug-
in you are creating and CONFIG_FILE_PATH with the complete path and
name of the redirector configuration file. The redirector configuration file can
be any name and location you choose, but must be defined by the
configfile
attribute.
The following samples illustrate the correct syntax for each Web server type;
each example uses “neptune” as the name of the Web server, and
“conn_config” as the name of the configuration file.
iPlanet:
Init fn="load-modules"shlib="WEB_SERVER_HOME/bin/https/libjeas_httpd40.so"
funcs="conn_init,conn_service"
Init fn="conn_init" configfile="/webserver/https-neptune/config/conn_config"
Platform File name
iPlanet libjeas_httpd40.so