HTTP Server Configuration
18 Netscape Directory Server Gateway Customization Guide
In release 3.x, to access a different suffix, another HTTP server and another
gateway must be configured on the host where the Directory Server is installed.
Note When the root suffix, directory manager, or port change, the gateway settings
in dsgw.conf must be updated to reflect the changes (if they haven’t been
updated through the Netscape Console).
Configuring the Gateway for Enterprise
or FastTrack Servers
The configuration procedures provided in this section assume that a Netscape
FastTrack (or Enterprise) HTTP server is installed and configured to
communicate with the Netscape LDAP Directory server.
In release 4.0, Directory Express and the default gateway are installed with the
Directory Server and configured to run under the Netscape Administration
Server, which is the default HTTP server for the gateway clients. No additional
configuration is necessary. However, customers in high-usage networks may
wish to move their gateways (or set up new gateways) on a high-performance
HTTP server, following the procedures provided in this section.
In release 3.x, the gateway must be configured to communicate with the LDAP
Directory Server, following the procedures provided in this section. The 3.x
gateway allows one instance of the gateway per HTTP server.
Figure 2.1 shows the Netscape FastTrack Server configuration screen used to
configure an additional document directory. Figure 2.2 shows the Netscape
Enterprise Manager configuration screen used to configure an additional CGI
directory.
