 |
Gateway
Customization Guide Netscape Directory Server |
| Previous |
Contents |
Index |
DocHome | Next |
This chapter provides examples of customized gateways. The chapter contains the following sections:
To the gateway user, the gateway is a set of HTML forms that can be accessed from a web browser to communicate directly with the Directory Server over HTTP.
To the gateway administrator, the gateway is controlled by a set of files installed during Directory Server installation. These files can be edited to:
Files that control gateway functionality are described in Table 3-1.
|
Define basic configuration parameters for the gateway and specify the HTML and template directory. (See Gateway .conf Files.) |
||
|
Define how the gateway performs searches in the Directory. (See Gateway Search Configuration Files.) |
||
|
Define object classes and attributes for entry types. (See Object Class Templates.) |
||
|
Contain scripts used to communicate instructions to the Directory Server over HTTP. (See Gateway Script Files.) |
||
|
Define the filters used to display search results to the user. (See Gateway Search Result Templates.) |
||
|
Define appearance of colors, background, graphics on gateway forms. (See Banner Files.) |
A gateway's configuration file (.conf file) describes an instance of the gateway. The file controls the host, port, root suffix, and Directory Manager when communicating with the Directory Server. The file also controls:
pb.conf is the configuration file for Directory Express, a gateway customized as a directory lookup tool. pb.conf is invoked at:
Gateway configuration parameters are defined in Appendix A, "Parameters Defined in the .conf File."
Gateway search configuration files determine how the gateway queries information in the directory and returns search results to the users. Gateway search configuration files are stored in the serverRoot/clients/dsgw/config directory. All gateway instances for a Directory Server use these common search configuration files.
The
dsgwsearchprefs.conf and
dsgwfilter.conf files are discussed in chapter 5, "Search Attributes,
Filters, and
Results."
The gateway contains a template file for each object class defined in the gateway. To modify how the gateway displays an entry type, edit the corresponding template file. To add gateway support for a new object class, create a new template file, or modify an existing one.
Modifying template files is discussed in chapter 4, "Editing Entry Types."
Default gateway object class templates stored in the serverRoot/clients/dsgw/config directory are listed in Table 3-2.
Script files are used to generate HTML forms dynamically for the user, based on information supplied by the user and information retrieved from the Directory Server. Script files contain directives the gateway uses to construct the HTML for a page.
Script files can be modified to change the appearance of text that appears in fields, buttons, and prompts on gateway forms.
Script files used to modify the information provided on gateway forms are stored in the serverRoot/clients/dsgw/config directory and are identified in Table 3-3.
Search result templates control how the results of a standard or advanced search are displayed when more than one entry is found. A separate search result file exists for each search object defined in dsgwsearchprefs.conf.
The default search result files installed in the serverRoot/clients/dsgw/config directory during Directory Server installation are shown in Table 3-4.
Chapter
5, "Search
Attributes, Filters, and Results," describes how search result
templates can be edited to modify the display of search results.
Banner files identified in Table 3-5 are used to specify the banner and button images that appear in gateway forms.
Chapter
6, "Banner
Image," describes how to alter the color schemes and images
appearing
on gateway forms.
| Previous |
Contents |
Index |
DocHome | Next |