The Audit Log
The audit log records all events relating to the registration of client licences. The log may be configured within the BAServer Configuration window to be recorded in one of two ways.
1. TEXT - as a simple text file.
2. DATABASE - written to a BASAuditLog table in a suitable ODBC complient database.
The configuration of the log dictates the amount off data recorded and the method by which it may be viewed. For TEXT only the data/time and a message is recorded. In DATABASE mode the following are recorded and thus may form the basis for querying and reporting on the log.
1. LOGID,
2. Code - Client Serial Number.
3. Remote IP Address
4. Remote Machine Name
5. Server IP Address
6. Service Name
7.Comments - the standard message.
Configuring the Log Mode
The mode of operation may be configured from the Servers main diagnostic and configuration window. Click the "Audit Log" button to bring up the audit log configuration window.
Select the type from the drop down selection.
The Log Directory / ODBC Data Source: field is used to specify the directory for text files and the ODBC connectivity string for the DATABASE. Selecting the DATABASE type will for the browse option to look for ODBC data sources.
Filename and Rename Period
The filename of the logfile is generated auotmatically based on the rename option, you may configure the file to be renamed automatically, daily, weekly, monthly or never . If you select never the filename will default to Logfile.txt, if you select daily, weekly or monthly, the filename is automatically relating to the day, week or month, for example weeks are numbered 1 - 52, months 1-12, days are based on the date.
The Database Table BAAuditlog, and its Attributes
The Audit log database option expects to store data into a preset table within the database. The table requires the appropriet name 'BAAuditlog' and contain the following attributes.
|
Fieldname |
Type |
Description |
|
LogID |
Number |
Unique ID for the log entry |
|
Date |
Date/Time |
Date logged |
|
Code |
Text |
Client Serial Number. |
|
RemoteIP |
Text |
Remote IP address initiating the process |
|
RemoteMachineName |
Text |
Remote machine name |
|
ServerIP |
Text |
Server IP address |
|
ServiceName |
Text |
Service name |
|
Comments |
Text |
any attached comments - normally the return string |
The Error Log
The error log records all service events relating to errors and trace information. Although not intended to provide audit information it is intended to provide system managers and engineers with trace and error information in the event of system failures, or errors resulting from configuration errors.
The log may be configured within the BAServer Configuration window to be recorded in one of two ways.
1. TEXT - as a simple text file.
2. DATABASE - written to a BASErrorLog table in a suitable ODBC complient database.
The configuration of the log dictates the amount off data recorded and the method by which it may be viewed. For TEXT only the data/time and a message is recorded. In DATABASE mode the following are recorded and thus may form the basis for querying and reporting on the log.
1. LOGID,
2. Type
3. Message
4. Server IP Address
5. Service Name
Configuring the Log Mode
The mode of operation may be configured from the Servers main diagnostic and configuration window. Click the "Error Log" button to bring up the error log configuration window.
Select the type from the drop down selection.
The Log Directory / ODBC Data Source: field is used to specify the directory for Text files and the ODBC connectivity string for the DATABASE. Selecting the DATABASE type will for the browse option to look for ODBC data sources.
Filename and Rename Period
The filename of the logfile is generated auotmatically based on the rename option, you may configure the file to be renamed automatically, daily, weekly, monthly or never. If you select never the filename will default to Logfile.txt, if you select daily, weekly or monthly, the filename is automatically relating to the day, week or month, for example weeks are numbered 1 - 52, months 1-12, days are based on the date.
Error Log Level
Whether storing the logged information to database or file you may aslo configure the log to operate in one of two levels.
1. Full Trace
2. Errors Only
Errors Only
This level logs only error information.
Full Trace
This level logs trace information as well as errors. Thus if the system appears to be functioning incorrectly we may enable the 'Full Trace' level of loging and gather more information.
The Database Table BAErrorlog, and its Attributes
The Audit log database option expects to store data into a preset table within the database. The table requires the appropriet name 'BAErrorlog' and contain the following attributes.
|
Fieldname |
Type |
Description |
|
LogId |
Number |
Unique Identifier for the logged event |
|
Date |
Date/Time |
Date and time the event was logged |
|
Type |
Number |
Number indicating the type of error |
|
ErrorMessage |
Text |
Description of the error |
|
Server IP |
Text |
Server IP Address |
|
ServiceName |
Text |
Service name |
Checking the NT Event Log
All critical event and error are recorded in the NT Event Log. Each event has a unique number which will help identify the cause of the event. Events include the starting and stopping of the service etc.
