• Netscape Enterprise Server
• Microsoft Internet Information Server

• Check whether or not the Web Connector plug-in has been previously installed. If it has, the web server instance is already configured for your Netscape Application Server. The start and stop scripts and the obj.conf file of the Web Connector plug-in may be affected, causing the installation of the plug-in to fail. To uninstall the earlier copy of the Web Connector plug-in, before installing the new copy, run the following command:
webremove
• Stop running your web server instance.
• Log on as the root user, or as a user from the same group as the root user, who installed Netscape Application Server before installing the Web Connector plug-in

1. After you finish installing Netscape Application Server as a webless installation, take the installation CD-ROM to the machine or machines that host the web server.
2. Mount the CD-ROM on, for example, /cdrom/cdrom0.

1. Create a directory (for example, nas21).
2. Change to that directory.
3. At the shell prompt, type the following command:

setup_WebConnector.sh 



The Web Connector installation program starts. 

1. Follow the Web Connector installation program instructions to complete the installation.

When the installation program prompts you for the web server directory, be sure to specify the directory of the appropriate web server instance.

1. Enable CGI, if it is not already enabled:

1. Go to the Netscape program group and click Administer Netscape Servers.
2. Enter the administrator ID and password, and click OK.
3. On the Netscape Server Selector screen, click on the web server instance you want to configure.
4. On the main menu bar across the top of the page, click Programs.
5. On the CGI directory screen under URL prefix, type cgi-bin.
6. Under CGI directory, enter the cgi-bin path.
<server home dir>/docs/cgi-bin

Now, you are ready to configure the Web Connector plug-in.

2. Edit the obj.conf file in the web server configuration directory.

For example:

Netscape Enterprise Server 2.x:

<server home dir>/httpd-<machinename>/config

Netscape Enterprise Server 3.x:

<Netscape home dir>/https-<machinename>/config

Make a copy of the file before modifying it. At the end of the Init section of the obj.conf file, add the following as two lines:

Init fn="load-modules" funcs=gxrequest,gxlog,gxinit,gxredirect,gxhtmlrequest shlib="gxnsapi30.so"
Init fn="gxinit"

3. In the Object name=default section, just after type=text/plain section, add the following two lines:
Service fn="gxhtmlrequest" method="(GET|HEAD)" type="text/html"
Service fn="gxredirect" fnname="imagemap" method="(GET|HEAD)"
4. In the Objectname=cgi section(s), insert the following line immediately before the line Service fn="send-cgi":
Service fn="gxrequest"

And then insert the following line immediately after the line Service fn="send-cgi":

AddLog fn="gxlog"
5. Make a copy of the current version of the file obj.conf and copy it to the back up version (so that the backup is consistent with the current version) in the following directory:
<Netscape home dir>/https-<machinename>/conf_bk
6. Modify the web server's start and stop scripts as follows:

• Set GX_ROOTDIR to the directory in which Netscape Application Server is installed. For example:
GX_ROOTDIR=<NAS installation directory>; export GX_ROOTDIR

• Set LD_LIBRARY_PATH to gxlib under the Netscape Application Server installation directory. For example:
LD_LIBRARY_PATH=<NAS installation directory>/gxlib:$LD_LIBRARY_PATH;
export LD_LIBRARY_PATH

• Set SHLIB_PATH to javalib under the Netscape Application Server installation directory. For example:
SHLIB_PATH=<NAS installation directory>/javalib:$SHLIB_PATH;
export SHLIB_PATH

Solaris and HPUX

• In the stop script of the Netscape web server, add -9 after "kill" and - before the process file. For example:
kill -9 -\Qcat $PID_FILE\Q

where PID_FILE is set to <web server instance>/logs/pid

7. Restart the web server.