Administrator
Login
Monitor
Control Panel
Manage
Server
Socket
Virtual Hosts
Workgroup
Session
Servlets
Contexts
Aliases
Mime Types
Locales
Messages
Pools
Realms
Resources
Users
Groups
Computers
Access Rights
ACLs
Logger
Templates
File System
Archives
About
|
Used to view and change logger parameters.
Entry Form
Fields
Log Access
|
Whether to log requests.
Yes is the default value.
Setting this value to No will result in no access log being
maintained. Setting this value to Yes may have a negative impact on
performance.
|
Log Events
|
Whether to log events.
Yes is the default value.
Setting this value to No will result in no log being maintained for
events. Setting this value to Yes may have a negative impact on
performance.
|
Log Errors
|
Whether to log errors.
Yes is the default value.
Setting this value to No will result in no log being maintained for
errors. Setting this value to Yes may have a negative impact on
performance.
|
Class File
|
The Class in the form package.class of the Logger to use.
|
Parameters
|
Any parameters used during initialization of the Logger.
Zero or more parameters can be specified by entering line delimited
key=value pairs.
|
Ignore Exceptions
|
Any exceptions to ignore.
Zero or more Exception classes can be specified.
java.io.IOException is the default.
|
Actions
SAVE
|
Used to save changes made and to return the Control Panel form.
|
CANCEL
|
Used to discard changes made and to return the Control Panel form.
|
HELP
|
Used to display online help for this form.
|
Notes
Changes made will not be used until the server is restarted.
Configuration
Servertec Internet Server includes console, file, POS and database loggers.
The console logger outputs events and requests to stdout and errors to
stderr. The file logger is used to log client requests, errors and events to
flat files. The POS logger uses Servertec Object Store and the database
logger to any JDBC accessible database.
Select the method to use:
Console
Flat File
Microsoft Access
Oracle
Servertec Persistent Object Store
Use the following steps to configure the console logger.
- Set Class File to stec.iws.ConsoleLogger.
- Define the following Parameters:
access_log_template=template
access_log_header_template=header_template
interval=interval
header_template
|
The header template to use.
Header templates are defined using the Servertec Internet Server
Administrator or directly by editing the templates.ini file located at
c:\iws.net\config directory, assuming that the server was installed in
c:\iws.net.
|
interval
|
The number of milliseconds that Logger waits between flushing queued
logger entries.
0 milliseconds is the default for the Logger.
0 can be used to flush logger entries immediately.
The number must be at least 50 milliseconds.
Setting this value too small may have a negative impact on performance.
Setting this value too large may have a negative impact on performance and
may result in logger entries being lost if the server crashes or if it is
aborted.
|
template
|
The template to use for access log entries.
default is the default value.
If None is the value then a template will not be used. Using
None may improve performance.
Templates are defined using the Servertec Internet Server Administrator or
directly by editing the templates.ini file located at
c:\iws.net\config directory, assuming that the server was installed in
c:\iws.net.
|
Use the following steps to configure the file logger.
- Set Class File to stec.iws.FileLogger.
- Define the following Parameters:
basedir=basedir
access_log_template=template
access_log_header_template=header_template
log_rollover_interval=rollover_interval
interval=interval
basedir
|
The directory that will contain the log files.
./logs is the default directory.
|
header_template
|
The header template to use.
Header templates are defined using the Servertec Internet Server
Administrator or directly by editing the templates.ini file located at
c:\iws.net\config directory, assuming that the server was installed in
c:\iws.net.
|
interval
|
The number of milliseconds that Logger waits between flushing queued
logger entries.
0 milliseconds is the default for the Logger.
0 can be used to flush logger entries immediately.
The number must be at least 50 milliseconds.
Setting this value too small may have a negative impact on performance.
Setting this value too large may have a negative impact on performance and
may result in logger entries being lost if the server crashes or if it is
aborted.
|
rollover_interval
|
How often to rollover the log files.
None do not rollover the log files.
Daily rollover the log files every day.
Weekly rollover the log files every week.
Monthly rollover the log files every month.
Weekly is the default value.
On a very active site log files should be rollover every day.
The Logger uses yyyymmdd_logfile.log when
Daily, Weekly and Daily is selected and
logfile.log when None is selected.
|
template
|
The template to use for access log entries.
default is the default value.
If None is the value then a template will not be used. Using
None may improve performance.
Templates are defined using the Servertec Internet Server Administrator or
directly by editing the templates.ini file located at
c:\iws.net\config directory, assuming that the server was installed in
c:\iws.net.
|
Use the following steps to configure the database logger for Microsoft Access.
- Defined a System DSN for the database using the ODBC Data Source
Administrator from the Control Panel.
Driver: Microsoft Access Driver (*mdb)
Data Source Name: iserver.msaccess
Database: iws_dir\databases\iserver.mdb
iws_dir is the directory where the server was installed,
normally c:\iws.net.
- Set Class File to stec.iws.DatabaseLogger.
- Define the following Parameters:
driver=com.ms.jdbc.odbc.JdbcOdbcDriver
url=jdbc:odbc:iserver.msaccess
interval=interval
interval
|
The number of milliseconds that Logger waits between flushing queued
logger entries.
0 milliseconds is the default for the Logger.
0 can be used to flush logger entries immediately.
The number must be at least 50 milliseconds.
Setting this value too small may have a negative impact on performance.
Setting this value too large may have a negative impact on performance and
may result in logger entries being lost if the server crashes or if it is
aborted.
|
Notes
The database logger makes use of the JDBC-ODBC bridge to access the
iserver.mdb database.
Use the following steps to configure the database logger for Oracle.
- If Oracle database server is not running then start it.
- If you have not already created an Oracle database for Servertec
Internet Server then follow the instructions below to create it.
- Start SQLPLUS and login as an administrator.
sqlplus system/manager
The user name and password shown above may not be correct on all systems.
Please consult the appropriate Oracle documentation or a system database
administrator for the correct user name and password.
- Create admin user.
grant connect to admin identified by admin;
grant dba to admin;
commit;
exit
- Start SQLPLUS again and this time login using the new admin
user.
sqlplus admin/admin
- Assuming that Servertec Internet Server was installed in c:\iws.net,
create the database.
@/iws.net/databases/iserver.sql
exit
If Servertec Internet Server was installed in a directory other than
c:\iws.net then edit installdir/databases/iserver.sql and
change the directory path of the iserver.dbf database to the proper
path.
- Using the sample TNSNAMES.ORA file in
installdir/databases, define a new SQL Net entry named
iserver.oracle for Servertec Internet Server.
- Start SQL Net Listener.
lsnrctl start
- Set Class File to stec.iws.DatabaseLogger.
- Define the following Parameters:
driver=com.ms.jdbc.odbc.JdbcOdbcDriver
url=jdbc:odbc:iserver.oracle
user=admin
password=admin
interval=interval
interval
|
The number of milliseconds that Logger waits between flushing queued
logger entries.
0 milliseconds is the default for the Logger.
0 can be used to flush logger entries immediately.
The number must be at least 50 milliseconds.
Setting this value too small may have a negative impact on performance.
Setting this value too large may have a negative impact on performance and
may result in logger entries being lost if the server crashes or if it is
aborted.
|
Use the following steps to configure the Servertec Persistent Object Store logger.
- Install and configure Servertec Persistent Object Store.
- Set Class File to stec.iws.PosLogger.
- Define the following Parameters:
access_store=access_store
access_capacity=access_capacity
errors_store=errors_store
errors_capacity=errors_capacity
events_store=events_store
events_capacity=events_capacity
server_store=server_store
interval=interval
access_store
|
the base file name of the Access store. If not specified defaults to iws_dir/databases/access.store.
|
access_capacity
|
the average number of entries in the Access store.
The number must be at least 1.
If not specified defaults to 65536.
Setting this value too small may have a negative impact on performance.
Setting this value too large will waste disk space.
|
errors_store
|
the base file name of the Errors store. If not specified defaults to iws_dir/databases/errors.store.
|
errors_capacity
|
the average number of entries in the Errors store.
The number must be at least 1.
If not specified defaults to 65536.
Setting this value too small may have a negative impact on performance.
Setting this value too large will waste disk space.
|
events_store
|
the base file name of the Events store. If not specified defaults to iws_dir/databases/events.store.
|
events_capacity
|
the average number of entries in the Events store.
The number must be at least 1.
If not specified defaults to 65536.
Setting this value too small may have a negative impact on performance.
Setting this value too large will waste disk space.
|
server_store
|
the base file name of the Server store. If not specified defaults to iws_dir/databases/iws.store.
|
interval
|
The number of milliseconds that Logger waits between flushing queued
logger entries.
0 milliseconds is the default for the Logger.
0 can be used to flush logger entries immediately.
The number must be at least 50 milliseconds.
Setting this value too small may have a negative impact on performance.
Setting this value too large may have a negative impact on performance and
may result in logger entries being lost if the server crashes or if it is
aborted.
|
Each entry in the Access store is a stec.pos.Blob containing:
Field
|
Type
|
Length (Bytes)
|
Timestamp
|
long
|
8
|
RemoteAddress
|
UTF8 String
|
4 + utf8 string length
|
RemoteHost
|
UTF8 String
|
4 + utf8 string length
|
RemoteUser
|
UTF8 String
|
4 + utf8 string length
|
Host
|
UTF8 String
|
4 + utf8 string length
|
Port
|
int
|
4
|
LocalAddress
|
UTF8 String
|
4 + utf8 string length
|
ContentLength
|
long
|
8
|
RequestLength
|
long
|
8
|
ResponseTime
|
long
|
8
|
StatusCode
|
int
|
4
|
ErrorCode
|
int
|
4
|
RequestMethod
|
UTF8 String
|
4 + utf8 string length
|
RequestURI
|
UTF8 String
|
4 + utf8 string length
|
QueryString
|
UTF8 String
|
4 + utf8 string length
|
UserAgent
|
UTF8 String
|
4 + utf8 string length
|
Referer
|
UTF8 String
|
4 + utf8 string length
|
Protocol
|
UTF8 String
|
4 + utf8 string length
|
ServerService
|
UTF8 String
|
4 + utf8 string length
|
Each entry in the Errors store is a stec.pos.Blob containing:
Field
|
Type
|
Length (Bytes)
|
Timestamp
|
long
|
8
|
Message
|
UTF8 String
|
4 + utf8 string length
|
Exception
|
UTF8 String
|
4 + utf8 string length
|
Each entry in the Events store is a stec.pos.Blob containing:
Field
|
Type
|
Length (Bytes)
|
Timestamp
|
long
|
8
|
Message
|
UTF8 String
|
4 + utf8 string length
|
|
|