Gateway Installation Planning
16 Netscape Directory Server Gateway Customization Guide
• the number of users accessing the gateway at a given time
• the complexity of the directory searches performed and the search results
required
• whether the gateway is additionally to be used for authentication and login
• the load from other processes managed by the host machine
• the speed and performance of the computer hardware selected for the host
computer
• the speed and capacity of the network (network hardware and software)
In general, gateway performance on the Netscape Administration Server begins
to slow down when the number of users accessing the gateway throughout the
enterprise reaches 6,000 people. (Note that this is a very general
recommendation that does not take into account factors listed above, especially
the speed of the host machine.)
Note It is not advisable to run the gateway from a Netscape Administration server
that is also running a Netscape server process as root. This may expose
sensitive information about the configuration of Netscape servers.
Running the Gateway in High-Usage Networks
Network administrators expecting high gateway usage may want to move the
gateway to a high-performance HTTP server that is dedicated to running the
gateway.
Note If you do decide to migrate the gateway’s configuration files to a high-
performance HTTP server, Netscape recommends Netscape Enterprise Server or
FastTrack Server.
See Also
“Name Translation Mapping” on page 17
