Table of Contents Previous Section
If you have a Netscape server, the NSAPI adaptor to use, and the procedure for configuring it, depends on the type of server. Adaptors are located in NextLibrary/WOAdaptors/NSAPI.
|If you have server...||use adaptor...|
Note: There is no requirement for installing an adaptor anywhere other than its original location. If you wish, you can copy the adaptor to the server's executable or configuration directories, but ensure that the configuration specifications refer to its proper location. The following procedures assume the original installed locations. NSAPI configuration is applicable only to the WebObjects Enterprise product.
To configure the NSAPI adaptor for Netscape 1.1 servers on Windows NT, you must make a series of key-value entries in the NT registry. These instructions assume some familiarity with the registry editor. If you aren't sure how to use this program, refer to the appropriate documentation.
The interior folder name represented by "Http[d|s]" is Https if the server performs authentication and Httpd if it doesn't; port is either a port number or the server host name, depending on the server.
|from||/cgi-bin/WebObjects (assuming "cgi-bin" is the name given to the CGI executable directory)|
To configure Netscape 1.1 NSAPI adaptors for the Solaris and HPUX platforms, and to configure Netscape 2.0 or 2.0.1 NSAPI adaptors for all platforms, complete the following procedure:
|Server||Platform||Configuration Files to Modify|
2.0 and 2.0.1 Servers:In the obj.conf file insert the following:
Init fn=load-modules shlib=c:/NeXT/NextLibrary/WOAdaptors/NSAPI/2.0/WebObjects-NSAPI.dll funcs="WONetscapeInterface,WONSInterfaceFindWebObjects"
This example is specific to Windows NT and NSAPI 2.0; for Solaris and HPUX the name of the adaptor binary is WebObjects-NSAPI.so.
1.1 Servers (HPUX/Solaris): In the magnus.conf file insert the following:
Init fn=load-modules shlib=c:/NeXT/NextLibrary/WOAdaptors/NSAPI/1.1/WebObjects-NSAPI.so funcs="WONetscapeInterface,WONSInterfaceFindWebObjects"
NameTrans from="/cgi-bin" fn="pfx2dir" dir="cgi_bin_dir" name="cgi"
Just before this line, insert the following line:
NameTrans from="/cgi-bin/WebObjects" fn="WONSInterfaceFindWebObjects" name="webobjects"
<Object name="webobjects"> Service fn="WONetscapeInterface" </Object>
On Windows NT, you can restart your server from the Services control panel by stopping and then starting it (clicking the Stop button, then clicking the Start button). However, it is better to use the browser interface provided for administration to restart the server. If there are errors, you can check the error activity log to find out what they are.
When you test an API-based adaptor to verify that it's properly configured, you should eliminate the CGI adaptor as a factor. To do this, rename WebObjects (or WebObjects.exe) to something like "WebObjects_test" (or "WebObjects_test.exe") and test the API-based adaptor. If you wish later to restore the CGI adaptor, simply undo the changes you made previously.
Table of Contents Next Section