Creating a New Gateway Instance (4.0 only)
22 Netscape Directory Server Gateway Customization Guide
The process listed identifies the name under which the HTTP process is
running.
2. Log into the machine as root.
3. Go to the <NSHOME>/dsgw and enter:
# chown <uid> authck
where <uid> is the user name determined in step 1.
4. Verify that the directory is accessible by opening the URL:
http://<webserver-host>:<port>/ds/search
where <webserver-host> is the HTTP server’s host name, and <port> is the
port number used by the server.
Note When the HTTP server is using the standard HTTP port number (80), the port
number does not need to be included in the URL.
Creating a New Gateway Instance (4.0 only)
These instructions assume that the new gateway instance is running under the
Netscape Administration server or a similarly capable HTTP server.
Example 2.1 Setting up .conf file and directories for new gateway instance
1. Rename dsgw.conf or pb.conf to a new gateway context. For example,
dsgw/context/dsgw.conf might become dsgw/context/airius.conf.
2. Set the gwnametrans parameter in the new gateway’s .conf file to point to
the HTML directory. For example, the gwnametrans parameter setting for
airius.conf should point to /dsgw/airiushtml.
3. To support non-anonymous searching (one individual user DN and
password per directory instance) using the new gateway, set the binddnfile
parameter in airius.conf to point to the location of the file containing the
bind DN and bind password be used to access information in the user
directory (the binddnfile contains sensitive information; for security
purposes, do not store the binddnfile within the /dsgw directory or within
any directory served up over HTTP).
