Logging
Database-based logs
The logs in "Control Center/Logs" are stored in the database. The following comments only apply if a relational database is used for logging (standard case).
See also section Retention periods of backup files, logs, crashed jobs.
Overview
All log messages that have been generated during profile runs (jobs) (including erroneous jobs). The corresponding tables are "dw_log_sum" and "dw_log" .
Errors
Only the errors from the overview are listed here. The corresponding table is "xml_datawizard_error".
General messages
Log messages that cannot be assigned to a particular job and therefore do not appear on pages "Overview" or "Errors" . This is the case, for example, if an error occurred in phase 1 of a profile run, but no job has been created yet. The corresponding table is "dw_log" (job number "dw_job" = "0"). Here you will also find log messages for the add-on modules Content Inspection and ENGDAT.
ASM messages
Log messages for the add-on module Asynchronous Sending Module (ASM) are listed here. The corresponding tables are "dw_asm_log" and "dw_asm_log_detail" .
Comm Log
You need an additional license for the CommLog. Additional log messages can be generated for communications with partner systems that are conducted via channels. The corresponding tables are "comm_log*".
Server Logs
These logs are not database-based but file-based. See the following section.
File-based logs
For logging, the LogService is used, which in turn uses a number of LogManagers (there are several types of LogManagers, but by default the FileLogManager (file-based) is used).
All file-based logs are stored in folder ./logs. You can access them directly in the file system or in the Control Center (→ Logs/Server Logs) or in the Admin Console (→ Log Monitor).
The following FileLogManagers are available by default. You will find daily files "message.log" (messages that are not error-related) and error.log (error messages). In addition, some subfolders may also contain trace files (also called client logs) that contain connection details.
|
Subfolder in ./logs |
Name in Control Center resp. Admin Console |
Description |
|
Directly in folder ./logs |
"Http server" resp. "Request Log" |
The following files can be found here: adminrequest.log (HTTP requests to the Admin Console.) request.log (HTTP requests to the Integration Server.) server.log (Windows) resp. hub.log (Linux) (logs of the Integration Server.) Additionally, the folder ./logs contains a few log files that are not displayed in the Control Center or the Admin Console. statistic.log (Contains some statistical data that is, for example, displayed on the Dashboard.) threads.log (Contains information to threads that is, for example, displayed on the Dashboard.) wrapper.log (If the Integration Server is started as a service on Windows systems, then all messages that are otherwise output on the console will be written in here. For Linux systems see ./logs/console.txt) boot.log (Contains information about when Lobster Integration was started and ended. In addition, the total number of all profiles and the number of active profiles are recorded.) To activate this log, the following entry has to be added in configuration file ./etc/startup.xml (after the application for Lobster Integration itself): <Call name="addApplication"> |
|
_data |
_data |
Logs of the Lobster Integration GUI. |
|
as2 |
as2log |
Messages of the AS2Service. Additionally, there might be trace files in here (see pages "System logging" and "Profile logging"). |
|
capitraces |
CapiTraces |
Capi traces for OFTP are stored here if this is configured accordingly in the OFTPService (base directory and "verbose" mode are set). |
|
CEXLog |
cexlog |
Messages of the CertificateExchangeService. |
|
CronLogManager |
cronlogmanager |
Messages for cron jobs are stored here (e.g. profiles with time-driven Input Agents). |
|
DataWizard |
defaultdatawizardlog |
Messages of profile jobs are stored here. |
|
dump |
- |
If the system property -Dhub.mail.preserveOriginal=true is set, this folder will be used to store all received emails as files. |
|
|
|
This subfolder is created if the option "Mail Log" has been set in the System logging or Profile logging. It contains trace files that also include the received emails. |
|
engdat |
engdat |
Messages of the add-on module "ENGDAT". |
|
fax |
Fax |
There might be trace files in here (see System Logging and Profile logging). |
|
FtpLog |
ftplog |
Messages of the FTPService. Additionally, there might be trace files in here (see System Logging and Profile logging). |
|
services |
internal |
All services write messages in here (including the messages of the "verbose" mode). |
|
OftpLog |
oftplog |
Messages of the OFTPService. Additionally, there might be trace files in here (see System Logging and Profile logging). |
|
SCM |
scm |
Not relevant for Lobster Integration alone (only if Lobster_scm is used as well). |
|
SSHLog |
sshlog |
Messages of the SshService. Additionally, there might be trace files in here (see System Logging and Profile logging). |
|
WebMonClientLog |
webmonclientlog |
Messages of the add-on module "DataCockpit". |
|
x400 |
X.400 |
There might be trace files in here (see System Logging and Profile logging). |
|
TransportManager |
transportmanagerlog |
Logs for the "Transport Manager". |
Automatic log monitoring/evaluation
See sections Activating the Log Listener and CommLog (Input Agent).