Overview
This subpage provides an overview of all finished jobs in Lobster_data based on a selected Log Pool (more details below), a defined period of time, and additional search fields and filters on search results (more details below).
See also: Sections Logging in Lobster_data and Error Handling.
Standard Dialogue
(1) The logging of a profile job in Lobster_data can be done in separate Log Pools. The default Log Pool is called Standard.
(2) This button opens further search fields (see the following screenshot).
(3) The log messages of a marked job. If available, a trace file (see section System Logging) can be opened via a right-click on the log messages and viewed on subpage Server Logs.
The additional info shows log text that has been created with function log info(a). Note: Marked text can be copied to the clipboard with Ctrl+C. Ctrl+A marks the complete log text.
(4) Here you can set the maximum number (Max Logs) of displayed log entries (minimum 10, maximum 999999).
Advanced Search
(1) If a destination structure field attribute Log field value has the value Yes and there is a value for attribute Name for logging as well, the value of the destination structure field itself will be written in the job log with the specified name. You can select a name in the left field and a value in the right field (1).
(2) Refers to columns Display 1, Display 2 and Display 3. See function set display column(a,b,c) for details.
(3) If this checkbox is set, only jobs that match the search criteria and terminated with an error are displayed.
(4) A click on this symbol executes the search.
(5) See function log info(a).
Error Jobs
Erroneous jobs are indicated by the bug icon of column (1) and the orange coloured job number in column (2).
Note: You can use the context menu of a job to directly open it on subpage Errors.
Context Menu of a Job Line
A right-click on a job opens its context menu.
(1) and (2) Opens the input file in the editor or downloads it to the local computer.
(3) Opens the output file in the editor or downloads it to the local computer. These files must have been created in a Response Route of type File, with set checkbox Is backup of target data.
(4) Open the restart dialogue for this job.
(5) You can search for jobs that have been created as subsequent jobs of this job (so, for example, if a subsequent profile has been triggered in a Response Route of type Message).
(6) Opens an additional metadata editor in which you can view and edit existing variables from the metadata.
(7) Opens an erroneous job directly on subpage Errors.
(8) Opens the process view in the add-on module Data Flow if there is an entry with this profile.
(9) If a profile has a source structure, you can display an analysis of the input data relative to this source structure. The analysis result is an XML file that has a hierarchical structure like the source tree, that is, the input data that has been parsed into the source structure. The following screenshot shows an analysis example of an EDIFACT file and a corresponding EDIFACT source structure. The analysis file is displayed in the editor and can be evaluated there.
(10) In a further dialogue, the job number, profile name and file name can be copied.
(11) If there is a Comm Log entry for this job, you can jump directly to the entry.