These settings determine which log messages are to be saved for all profiles for which no specific settings have been made in the Profile Logging. This is the database-based logging, which is displayed in the Overview of the Control Center, for example. Further more, additional text files are sometimes created. These files are called trace files or client logs and contain connection details. They can be found in several subfolders 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). See also section Logging in Lobster_data.

images/download/attachments/91133510/Konfiguration_System-Logging_1_2_3_EN-version-2-modificationdate-1644223228820-api-v2.png

images/download/attachments/91133510/system_logging_2_EN-version-1-modificationdate-1644223207075-api-v2.png

(1) A template previously stored in (3) can be loaded. After deleting a template, it no longer appears in the selection. However, if that template was used for the settings before, the settings remain unaffected by the deletion of the template.

(2) The logging settings for phases 1-6.

(3) The settings can be saved as a template and then selected in (1). A saved template can be used in the System Logging and Profile Logging.

Logging Settings for Phases 1-6

Trace Messages

If this checkbox is set, additional detailed messages are output for the respective phase (not to be confused with 'trace files', which are actual additional files, see below). Important note: This option should only be used sparingly as it may produce large amounts of data and slow down processing. Ideally, use only during development and for a specific troubleshooting!

Phase 1

If this checkbox is set, information for phase 1 of the profile will be logged.

FTP Log

If this checkbox is set, information for incoming FTP communication is logged.

Additional client logs (= trace files) are created. The client log is stored under ./logs/FtpLog/client_<System.currentTimeMillis()>.log. As a result, the logging of the trace messages for phase 1 may be omitted.

OFTP Log

If this checkbox is set, information for incoming OFTP communication is logged.

Additional client logs (= trace files) are created. The client log is stored under ./logs/OftpLog/<System.currentTimeMillis()>_oftp.log. As a result, the logging of the trace messages for phase 1 may be omitted.

Mail Log

If emails are received via event-driven Input Agent SMTP or a time-driven Input Agent Mail/X.400, trace files are created in directory ./logs/mail. These trace files also contain the received emails.

Phase 2

If this checkbox is set, the information for phase 2 of the profile will be logged.

Records

If this checkbox is set, the creation of new records will be logged.

Unknown Segments

If this checkbox is set, segments (of an input file) that are not included in the source tree (due to the source structure) are logged. See also section Unknown Segment Log Listener for further processing.

Phase 3

If this checkbox is set, the information for phase 3 of the profile will be logged.

Records

If this checkbox is set, the creation of new records will be logged.

Function Calls

If this checkbox is set, the function calls within the mapping are logged.

Dump

This option can be used by functions (internally) to write additional log messages.

Phase 4

If this checkbox is set, the information for phase 4 of the profile will be logged.

Generated SQL Commands

If this checkbox is set, the generated SQL commands are logged.

SQL Execution

If this checkbox is set, the execution of SQL commands is logged.

Phase 5

If this checkbox is set, the information for phase 5 of the profile will be logged (Integration Units).

Phase 6

If this checkbox is set, the information for phase 6 of the profile will be logged.

Created File Names

If this checkbox is set, the name of the file into which the output data was written is logged for Response Routes of all types.

AS2

Additional log messages are generated for Response Routes of type AS2.

Additional client logs (= trace files) are created. The client log is stored under ./logs/as2/<job number>_<System.currentTimeMillis()>.log. Important note: Checkbox Trace messages has to be set. Otherwise the file will not be created. Note: For a complete trace, the AS2Service must be switched to verbose mode.

AS400, Custom Class

Additional log messages are generated for Response Routes of type AS400 and Custom Class.

File

If this checkbox is set, the name of the file into which the output data was written is logged for Response Routes of type File. Like option Created File Names, but more details.

FTP

Additional log messages are generated for Response Routes of type FTP.

Additional client logs (= trace files) are created. The client log is stored under ./logs/FtpLog/<job number>_client.log. Important note: Checkbox Trace messages has to be set. Otherwise the file will not be created.

Fax

Additional log messages are generated for Response Routes of type Fax.

Additional client logs (= trace files) are created. The client log is stored under ./logs/fax/fax_<job number>.log. Important note: Checkbox Trace messages has to be set. Otherwise the file will not be created.

HTTP, SMTP, Message, SAP, SMS, WebDAV

Additional log messages are generated for Response Routes of type HTTP, SMTP, Message, SAP, SAP ALE, SMS and WebDAV.

SCP

Additional log messages are generated for Response Routes of type SCP.

Additional client logs (= trace files) are created. The client log is stored under ./logs/SSHLog/SSH_<System.currentTimeMillis()>.log. Important note: Checkbox Trace messages has to be set. Otherwise the file will not be created.

X.400

Additional log messages are generated for Response Routes of type X.400.

Additional client logs (= trace files) are created. The client log is stored under ./logs/x400/Job_<job number>.log.

OFTP

Additional client logs (= trace files) are stored under path ./logs/OftpLog/<job number>_oftp.log. Note: For a complete trace, the OftpService must be switched to verbose mode.