Chapter 2, Setting Up the Gateway 23
Gateway .conf File Configuration
4. Create an HTML directory for the new gateway: For example, to provide an
HTML directory for airius.conf, copy and rename an existing HTML
directory (dsgw/html or dsgw/pbhtml) to /dsgw/airiushtml.
5. Create a template directory containing object class templates and other
configuration files. For example, to provide a template directory for
airius.conf, copy and rename an existing template directory (/dsgw/config
or /dsgw/pbconfig) to /dsgw/airiusconfig.
6. Edit the htmldir and configdir parameters in airius.conf to point to the new
HTML and template directories.
7. To access the new gateway instance--in this example, airius.conf--navigate
the browser to
http://admin:port/dsgw/bin/lang?context=airius
Gateway Cloning
The HTML and template directories for one gateway can serve as the HTML and
template directory for many others. Maintaining the functionality of multiple
gateways in a centralized /config and /html directories is useful when the only
values that are likely to change are parameter setting in the .conf file. (for
example, the host and port specified by the baseurl parameter, the root DN
specified by dirmgr, and the root suffix specified by the location-suffix
parameter).
Gateway .conf File Configuration
Changing the Default Port Setting
The LDAP port is set during Directory server installation. This value can be
changed in the baseurl parameter. Example 2.2 shows the syntax used to
specify a port number that is different than the default port number of 389.
Example 2.2 Changing LDAP port in the baseurl parameter
baseurl “ldaps://dirserver.airius.com:3000/o%3Dairius.com”
