Used to view and change logger parameters.
Entry Form
Fields
Log Access
|
Whether to log requests.
Yes is the default for iServer.
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 for iServer.
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 for iServer.
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 Java Class in the form package.class of the Logger to use.
The CLASSPATH will be searched for the specified logger.
|
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 Java Exception classes can be specified.
java.net.SocketException 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.
|
Configuration
iServer includes console, file 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 and the
database logger to any JDBC accessible database.
Select the method to use:
Console
Flat File
Microsoft Access
Oracle
Other
Use the following steps to configure the console logger.
- Set Class File to stec.iws.ConsoleLogger.
- Define the following Parameters:
access_log_template=template
interval=interval
interval
|
The number of milliseconds that 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 results in logger entries being that have not been flush being lost if
the server crashes or if it is aborted.
|
template
|
The template to use for access log entries.
default is the default for iServer.
If None is the value then a template will not be used. Using
None may improve performance.
Templates are defined using the iServer Administrator or directly by editing
the templates.ini file located at /iws/config directory,
assuming iServer was installed in /iws.
|
Use the following steps to configure the file logger.
- Set Class File to stec.iws.FileLogger.
- Define the following Parameters:
basedir=path
access_log_template=template
log_rollover_interval=rollover_interval
interval=interval
interval
|
The number of milliseconds that 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 results in logger entries being that have not been flush being lost if
the server crashes or if it is aborted.
|
path
|
The directory that will contain the log files.
./logs is the default directory.
|
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 for iServer.
If None is the value then a template will not be used. Using
None may improve performance.
Templates are defined using the iServer Administrator or directly by editing
the templates.ini file located at /iws/config directory,
assuming iServer was installed in /iws.
|
Use the following steps to configure the database logger for Microsoft Access.
- Set Class File to stec.iws.DatabaseLogger.
- Define the following Parameters:
driver=sun.jdbc.odbc.JdbcOdbcDriver
url=jdbc:odbc:iserver.msaccess
username=admin
password=admin
interval=interval
interval
|
The number of milliseconds that 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 results in logger entries being that have not been flush being lost if
the server crashes or if it is aborted.
|
- If you have not already created a System DSN for iServer then from the
Control Panel run ODBC Data Sources (32bit) and add a new System DSN named
iserver.msaccess that uses a Microsoft Access driver and that
references c:\iws\databases\iserver.mdb, assuming that iServer was
installed in c:\iws
The example provided above makes use of the JDBC-ODBC bridge to access the
iserver.mdb database. It will only work under Microsoft Windows 9x/NT and may
not work with JView.
Use the following steps to configure the database logger for Oracle.
- Set Class File to stec.iws.DatabaseLogger.
- Define the following Parameters:
driver=sun.jdbc.odbc.JdbcOdbcDriver
url=jdbc:odbc:iserver.oracle
username=admin
password=admin
interval=interval
interval
|
The number of milliseconds that 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 results in logger entries being that have not been flush being lost if
the server crashes or if it is aborted.
|
- If Oracle database server is not running then start then it.
- If you have not already created an Oracle database for iServer 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 iServer was installed in /iws, create the
database.
@/iws/databases/iserver.sql
exit
If iServer was installed in a directory other than /iws then
edit installdir/databases/iserver.sql and change the directory
path of the iserver.ora database to the proper path.
- Using the sample TNSNAMES.ORA file in
installdir/databases, define a new SQL Net entry named
iserver.oracle for iServer.
- Start SQL Net Listener.
lsnrctl start
The example provided above makes use of the JDBC-ODBC bridge to access the
Oracle database. It will only work under Microsoft Windows 9x/NT and may
not work with JView.
Use the following steps to configure the database logger for any JDBC
accessible database.
- Set Class File to stec.iws.DatabaseLogger.
- Define the following Parameters:
driver=driver
url=url
username=username
password=password
interval=interval
driver
|
The JDBC driver used to access the database.
|
interval
|
The number of milliseconds that 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 results in logger entries being that have not been flush being lost if
the server crashes or if it is aborted.
|
password
|
The password.
|
url
|
The JDBC URL that references the database.
|
username
|
The username.
|
- If you have not already created a database for iServer then using the
instruction for configuring database based realm for Oracle as a guideline
and /iws/databases/iserver.sql as a template create the appropriate
user login, database, tables, stored procedures and views.
Notes
Changes made will not be used until the iServer is restarted.
|