Changing the Hyena configuration

The initial Hyena configuration occurs while installing the Web Administration component of Sybase Search. (See “Installing Sybase Search”.) You can change the configuration of the Hyena servlet container by editing the Hyena configuration file. The Hyena configuration file is server.xml, and it is located in <installLocation>\Hyena\config. Use a text editor to edit the file.

Table 5-1 shows the attributes for the HTTP server tag.

Table 5-1: *HTTP Server tag*
Attribute	Default value	Description
port	None	The TCP/IP port on which Hyena listens for connections.
host	localhost	The name or IP address of the host on which the Hyena servlet container resides.
stdOutput	false	All standard output (for example, printed to java.lang.System.out and java.lang.System err) is always redirected to the Hyena log file. When set to true, the output is sent to the original standard output (usually the console) as well.

Table 5-2 shows the attributes for the Request-Handler tag.

Table 5-2: *Request-Handler tag*
Attribute	Default value	Description
minThreads	10	The minimum number of server threads that Hyena uses to serve connections.
maxThreads	75	The maximum number of server threads that Hyena uses to serve connections.
maxIdleTime	10000	The number of milliseconds an idle server thread is kept alive before being destroyed. This parameter applies only when the current number of server threads exceeds the minimum.
debug	false	If set to true, request handling debug information is written to standard output for every HTTP connection received.

Table 5-3 shows the attributes for the Request-Parser tag.

Table 5-3: *Request-Parser tag*
Attribute	Default value	Description
maxHeaderLength	None	The maximum number of characters accepted in any one HTTP request header (including GET parameters). Requests using headers longer than this are denied. Requests that send large parameter values should use the POST method.
maxNumberOfHeaders	None	The maximum number of request headers accepted as part of any single request. Requests formed using more headers than this are denied.

Table 5-4 shows the attributes for the Request-Keep-Alive tag.

Table 5-4: *Request-Keep-Alive tag*
Attribute	Default value	Description
enabled	false	When set to true, HTTP keep-alive is used with all HTTP clients that support it.
maxRequests	None	The maximum number of requests that are served by any one connection.
timeout	None	The number of milliseconds the server waits for further requests on an open connection before breaking it.

Table 5-5 shows the attributes for the Remote-Admin tag.

Table 5-5: *Remote-admin tag*
Attribute	Default value	Description
enabled	false	When set to true, authorized stop and start commands sent via HTTP are accepted.
authCode	None	The authorization code required by the remote administration listener.

Table 5-6 shows the attributes for the Logging tag.

Table 5-6: *Logging tag*
Attribute	Default value	Description
enabled	false	If set to true, HTTP requests are logged.
directory	None	Designates the directory in which log files are written.
prefix	None	The standard prefix for all log file names (appears before the date).
suffix	None	The standard suffix to use for all log file names (appears after the date).
timestamp	false	If set to true, time of the HTTP request is logged.

Table 5-7 shows the attributes for the container tag.

Table 5-7: *Container tag*
Attribute	Default value	Description
debug	false	When set to true, servlet/JSP debug information is written to standard output for each request received.

Table 5-8 shows the attributes for the JSP-handler tag.

Table 5-8: *JSP-handler tag*
Attribute	Default value	Description
vigilance	None	When set to true, servlet/JSP debug information is written to standard output for each request received.

Table 5-9 shows the attributes for the error-template tag.

Table 5-9: *Error-template tag*
Attribute	Default value	Description
path	<installLocation>\config\error_template.htm	Defines the path to an HTML template with which error messages are formatted to display to clients when an application error is encountered.

Table 5-10 shows the attributes for the context tag.

Table 5-10: *Context tag*
Attribute	Default value	Description
name	None	All context resource URIs implicitly start with this value; it must begin with a forward slash. For example, the context named /omniq might have its home page at /omniq/index.html.
path	None