Sun Microsystems Netscape Enterprise Server, Руководство администратора

Страница: 434 / 532

Customizing the Search Interface
434 Netscape Enterprise Server Administrator’s Guide
Customizing the Search Interface
As server administrator, you can customize the search interface to meet specific
user requirements. All of the HTML-based forms that the user sees are defined
through a set of pattern files that set up display formats for the search results
page header and footer as well as each search result record listed in response
to a query. There are a set of pattern variables that you can use to construct the
forms used for search input and output. Many of the variables are defined in
the system and user configuration files (
userdefs.ini
,
webpub.conf
, and
dblist.ini
, which are discussed in “Configuring Manually” on page 400).
Note
The search home page, at
http://
yourServer
/search-ui/examples
, also
provides an introduction to the search interface as well as an online QuickStart
tutorial on customizing the interface. The tutorial discusses the various pattern
files and gives examples of how they can be changed to produce different
results.
Dynamically Generated Headers and
Footers
You can specify dynamically generated headers and footers. To accomplish
this, add the
add-headers
and
add-footers
directives to your
obj.conf
file as Service functions. These directives take either a path or
uri
parameter.
Use the path parameter to specify a static file as the header or footer. For
example:
Service fn="add-headers" path="/export2/docs/header.html"
Service fn="add-footer" path="/export2/docs/footer.html"
Use the
uri
parameter to specify a dynamically generated file, such as a CGI
program, as the header or footer. For example:
uri="/cgi-bin/header.cgi"
These Service functions should precede the actual Service function that will
answer the request, such as
send-file
or
send-cgi
.