WebSpeed
Installation and
Configuration Guide


Configuring the Netscape Web Server For the NSAPI Messenger

You must perform the following tasks to configure a Web server to work with the WebSpeed NSAPI Messenger:

Editing the Netscape Web Server Configuration File

A Web server uses information in its configuration file to recognize the WebSpeed NSAPI Messenger. The configuration file for the Netscape Enterprise Server is named install-dir/https-host-name/config/obj.conf. (If you are using the Fast Track Server, refer to your Web server documentation for the name of the server’s configuration file.)

Make a copy of the file before you modify it so that you can restore the original configuration. Table 8–2 describes the changes you must make to obj.conf.

Table 8–2: Netscape Web Server Configuration
New Line
Description
Init fn=load-modules
shlib="
pathname"
funcs=WSNSAinit,WSNSAdefault,
WSNSAshutdown,WSNSAwebspeedCheck
This pathname is the absolute path to the Messenger shared object, wsnsa.dll. The Init line must appear after any existing Init commands. This line informs the Web server that it must load the Messenger shared object at the end of the initialization process, and that the named functions are external entry points within the shared object.
Init fn=WSNSAinit 
This Init line must appear as the last Init command. It informs the Web server that the named function is an external entry point within the shared object.
NameTrans fn=WSNSAwebspeedCheck 
This NameTrans line must appear before any existing NameTrans commands. You must add it within the block of commands delimited by <Object name=default> and </Object>. This line informs the Web server to handle WebSpeed requests properly.
Service method=(GET|POST|HEAD) 
fn=WSNSAdefault 
This Service line must appear before any existing Service commands. You must add it within the block of commands delimited by <Object name=default> and </Object>. This line informs the Web server to handle WebSpeed requests properly.

Each line you add to obj.conf must be on a single line. Do not add line breaks within a command line. Use forward slashes (/) in pathnames. Here is an excerpt from a sample obj.conf file (the additions that you must make for the WebSpeed Messenger are bold):

Init ...
Init ...
# The following directive is a single line; it contains no line breaks
Init fn=load-modules shlib="/usr/dlc/bin/wsnsa.dll"
     funcs=WSNSAinit,WSNSAdefault,WSNSAshutdown,WSNSAwebspeedCheck
Init fn=WSNSAinit 
<Object name=default>
AuthTrans ...
AuthTrans ...
NameTrans fn=WSNSAwebspeedCheck
NameTrans ...
NameTrans ...
PathCheck ...
PathCheck ...
ObjectType ...
ObjectType ...
Service method=(GET|POST|HEAD) fn=WSNSAdefault
Service ...
Service ...
AddLog ...
AddLog ...
Error ...
</Object>...
...
...
... 

Editing the Netscape Web Server Start File

The Netscape Web server must be able to locate the WebSpeed Messenger and the resources that the Messenger requires for configuration information and messages. Edit the Netscape Web server’s start file (for Netscape Web servers, this file is install-dir/https-hostname/start) to set the environment variables described in Table 8–3.

Table 8–3: NSAPI Messenger Settings 
Environment Variable
Setting
DLC
The WebSpeed Messenger installation path
PROMSGS
The pathname of the PROMSGS file: /install-path/promsgs
PROCFG
The pathname of the Progress configuration file: /install-path/progress.cfg
WRKDIR
The pathname of your working directory
LD_LIBRARY_PATH
Shared library search path (on Solaris, Compaq Tru64 UNIX and Linux only)
SHLIB_PATH
Shared library search path (on HP-UX only)
LIBPATH1
Shared library search path (on AIX only)
  1. On AIX only, you need to add /usr/lib to the shared library search path environment variable.

Here is a sample start file for AIX that includes the necessary WebSpeed information:

#! /bin/sh 
... 
LIBPATH=/usr/lib:$LIBPATH export LIBPATH 
...
DLC=/usr/dlc; export DLC
PROMSGS=/$DLC/promsgs; export PROMSGS
PROCFG=$DLC/progress.cfg: export PROCFG 
WRKDIR=/usr/workdir export WRKDIR 

Applying the Configuration Changes

Access the Netscape Server’s browser-based Admin panel and apply the configuration changes before restarting the Web server.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095