Gateway Installation Planning
14 Netscape Directory Server Gateway Customization Guide
Migrating 3.x default Gateways to
Release 4.0
Release 4.0 of the Netscape Directory server supports 3.x gateways, so it is not
necessary to modify a 3.x gateway in order for it to access a 4.0 directory.
However, a 3.x gateway can not co-exist with 4.0 gateways unless it is first
migrated to the 4.0 gateway structure.
An upgrade script, dsgwmig, is available which completes the migration of
dsgw.conf and its relevant files. The script does not overwrite the existing 3.x
gateway, but renames it as a new gateway instance (dsgw-30.conf) that runs
from the 4.0 /dsgw installation directory. The 3.x gateway will continue to work
with the 3.x Directory Server installation.
The migration script is installed in <NSHOME>/bin/slapd/admin/bin during
Directory Server installation. The script makes the following changes to the 3.x
gateway.
• Replaces /ds with /dsgw/bin in the gateway’s URLs.
• Changes gateway HTML file syntax to support the GCONTEXT and
PCONTEXT directives.
• Adds parameters to the dsgw .conf file--including htmldir, configdir,
gwnametrans--that support multiple gateway instances.
• Adds localization parameters to dsgw.conf to support the UTF-8 character
set and to support older browsers that are not aware of UTF-8.
• Moves dsgw.conf to /<NSHOME>/dsgw/context and renames it dsgw-
30.conf.
• Changes PATH_INFO to QUERY_STRING
Location of migrated dsgw.conf file
When the migration script finishes, the migrated 3.x dsgw.conf file can be
accessed from:
http://<host>:<port>/dsgw/bin/lang?context=dsgw-30
