| System Administrator
|
The System Administrator username is used to access these sysadmin folder
and administrator methods. By default, the administrator username is 'admin'.
|
| System Administrator IP
|
If left blank, the Sambar Server System Administrator may login from
any host. A space-separated list of IP addresses may be provided
(the wild-card character '*' may be used, i.e. 140.172.165.* ) to ensure
that only hosts which you plan to use for administration have access to
your System Administration tools.
|
| Server Port
|
The TCP/IP protocol has a number of ports which are used to differentiate
requests to different processes. The standard HTTP port number is 80. You can
choose any port number from 1 to 65000, however, many port numbers on your
system are reserved for other applications. Should you choose any port other
than port 80, you will have to access you homepage with the port number
appended to the URL (i.e. http://www.sambar.com:1080/ ).
|
| Automatic Server Restart
|
The server can automatically restart itself daily. This feature is
recommended for users of the DBMS system to free cached connections
periodically and for very active sites to periodically cleanup the
network connections, memory and thread pools. Note: Server restart
cannot be scheduled for midnight as it could conflict with daily or
weekly scheduled tasks. No other tasks should be scheduled for the
restart hour. Note: This feature is still being debugged.
|
| Server Security Realm
|
The security realm of the server. This applies to all Basic
security.
|
| Maximum Connections
|
Configure the maximum simultaneous connections supported by the system.
Connections differ from users in that a connection is only maintained
by the HTTP server for the duration of the transaction (HTTP request).
Therefore, while you might wish to support 200 simultaneous users, the
number of simultaneous connections needed to support that number of users
would likely be no more than 20.
|
| Network Read Timeout
|
Configure the maximum time, in seconds, to wait for a client connection
before terminating the connection. This period must be at least as
large as the Keep-Alive duration defined for the HTTP protocol. This
duration affects HTTP, proxy and FTP clients.
|
| Resolve Host Names
CHECKED>
Yes
CHECKED>
No
|
Configure the server to perform a DNS lookup on every host connection
to resolve the hostname. WARNING: This requires communicating with
a DNS server which can be quite slow if not properly configured. You
should absolutely NOT turn this feature on if your DNS server is on the
other side of a WAN, modem dial-up, or if you expect user heavy traffic.
|
| Automatic Directory Lists
CHECKED>
Yes
CHECKED>
No
|
If no default index page is present, this boolean indicates whether
the server should display the contents of the directory.
|
| Test CGI Exit Status
CHECKED>
Yes
CHECKED>
No
|
If turned on, the server tests the exit status of all CGI programs
and displays to the client the data written to stderr if the
exit status is not zero (0).
|
| ISAPI Debug Level
|
The debug level for ISAPI applications.
- None: No logging of any kind.
- Basic: Log only ISAPI function failures.
- Call: Trace all ISAPI function calls.
- Full: Detailed trace of each ISAPI call (for developers only).
|
| CGI/WinCGI tmp Removal
|
The execution of CGI/WinCGI files results in temporary files that
are often useful in debugging script execution.
|
| Automatic Log Rotation
CHECKED>
Yes
CHECKED>
No
|
If turned on, the server log files will be automatically rotated
daily shortly after midnight and a log report will be
automatically run. The log reports are available through the system
administration Report interface.
|
| Home Page
|
The HTTP document served when users request the home page (/) from the server.
|
| Default Page
|
The HTTP page served when users request a page from a directory without
specifying a path to a URL. This can be a space separated list of file
names (i.e. index.htm index.html index.shtml).
|
| Documents Directory
|
The directory in which documents are served out of. If not preceded by
a drive letter (i.e. d:\wwwdir), this directory is assumed to be relative to
the installation directory of the Sambar Server.
|
| CGI Directory
|
The directory in which cgi-bin scripts are served out of. The
CGI directory must be found in the installation directory of the
Sambar Server. The Sambar Server CGI plug-in module can be used to
execute CGI applications outside the CGI directory.
|
| WinCGI Directory
|
The directory in which Windows CGI scripts are served out of. The
WinCGI directory must be found in the installation directory of the
Sambar Server. The Sambar Server WinCGI plug-in module can be used to
execute WinCGI applications outside the WinCGI directory.
|
| ISAPI Extensions
|
This should be a space separated list of ISAPI extensions that, if found
in the Documents Directory should be recognized as a DLL with
ISAPI extensions executed (i.e. *.dll).
If left blank, ISAPI extension cannot be run in the Doucments
Directory (with the exception of any direct execute ISAPI DLLs found
in the [isapi] section).
|
| CGI Extensions
|
This should be a space separated list of CGI extensions that, if found
in the Documents Directory should be recognized as CGI scripts and
executed (i.e. *.cgi *.exe *.pl).
If left blank, only scripts found in the CGI Directory are
treated as CGI scripts.
|
| WinCGI Extensions
|
This should be a space separated list of WinCGI extensions that, if found
in the Documents Directory should be recognized as CGI scripts and
executed (i.e. *.cgi *.exe).
If left blank, only scripts found in the WinCGI Directory are
treated as WinCGI scripts.
|
| HTTP PUT Users
|
A space separated list of server users that have permission to use
the HTTP PUT method. Directory access can be further restricted with the
security interfaces.
|
| Server Side Includes
|
A space separated list of HTML file extensions that correspond with
files containing server side includes (i.e. shtml sht). As parsing
server-side include files is expensive, it is recommended that the
extensions be limited to shtml.
|
| Log Format
|
The log format options are:
- performance - Sambar Server performance format
- combined - NCSA combined log format
- common - NCSA Common Log Format
|
| Don't Log IPs
|
A space separated list of IP addresses not to log requests from.
This list may use wild-cards to match against (i.e. 127.0.0.1 140.172* ).
|
| Don't Log Requests
|
A space separated list of requests not to log.
This list may use wild-cards to match against (i.e. *.jpg *.gif /foo* ).
|
| Log Buffer Size
|
Configure the maximum number of lines permitted in the server log
file (server.log). Once this number is reached for a server session,
the log is reset to the first line (it operates much like a circular buffer).
For an infinite log size, set the log size value to 0.
|
| Enable DBMS Usage
CHECKED>
Yes
CHECKED>
No
|
Enable the DBMS interface of the Sambar Server. The DBMS interface
must be initialized to use the DBMS scripting. Once configured, the
DBMS management interfaces become available in the System Administration
console. (Note: You must have ODBC installed to enable this option.)
|
| Act as FTP Server
CHECKED>
Yes
CHECKED>
No
|
Start the FTP Server when the Sambar Server is started (in addition
to the HTTP server). WARNING: If your machine is already running an
FTP Server, the Sambar Server will fail to start if the ports of the two
servers conflict.
|
| Run Watcher
CHECKED>
Yes
CHECKED>
No
|
Start a Watcher Daemon when the server is started to monitor the
WWW server and restart it in the event of a failure. This feature should
NOT be used when the Sambar Server is run as an NT Service.
|
| Watcher Timeout
|
Configure the delay in seconds between each wwwping of the server
by the watcher daemon. This time should exceed 60 seconds (300 is the default).
After two consecutive failures, the server will automatically be terminated
and restarted.
|
