Content
Introduction
Release Notes
Features
FAQs
Requirements
Installation
Change Log
Future Plans
Knowledge Base
Documentation
Conventions
Users
iServer
Administration
Login
Control Panel
Manage
Server
Session
Servlets
Filters
Aliases
Mime Types
Messages
Pools
Realms
Resources
Users
Groups
Access Rights
ACLs
Logger
Templates
Deployment
Reference
Samples
Sales
Legal
Feedback
|
Used to view and change logger parameters.
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
errrors. Setting this value to Yes may have a negative impact on
performance.
|
|
Class File
|
The package.class name 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.
|
Configuration
iServer includes both file and database loggers. 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:
Flat File
Microsoft Access
Oracle
Other
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=interval
|
path
|
The directory that will contain the log files.
./logs is the default directory.
|
|
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.
|
|
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.
|
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
- If you have not already created a System DNS for iServer then from the
Control Panel run ODBC Data Sources (32bit) and add a new System DNS named
iserver.msaccess that uses a Microsoft Access driver and assuming that
iServer was installed in c:\iws that references
c:\iws\databases\iserver.mdb.
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
- 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 first
edit /iws/databases/iserver.sql and change the directory path of the
iserver.ora database to the proper path.
- Using the sample TNSNAMES.ORA file in /iws/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
accessiable database.
- Set Class File to stec.iws.DatabaseLogger.
- Define the following Parameters:
driver=driver
url=url
username=username
password=password
|
driver
|
The JDBC driver used to access the database.
|
|
url
|
The JDBC URL that references the database.
|
|
username
|
The username.
|
|
password
|
The password.
|
- 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.
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.
|
Notes
Changes made will not be used until the iServer is restarted.
|
|