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.
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 executable is WebObjects-NSAPI.so.
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>
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