Centralized Application Message Logging System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for logging processing operations in multi-operation applications are limited by per-job logging, making end-to-end event reporting difficult, requiring users to search multiple logs, and complicating analysis due to non-standardized content and runtime decision-making on event storage, which hampers performance and efficiency in high-volume processing environments.

Innovation Solution

A central logging system that collects and stores application messages generated by multiple jobs in a standardized format, allowing for uniform logging and storage in a database, enabling object-oriented reporting and reducing computational loads by filtering and sorting messages during runtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If per-job logging is used to maintain individual job logs, then each job can document its specific messages and events, but users must search multiple logs to find relevant information and end-to-end event reporting becomes extremely difficult

Engineering Contradiction:
Improvelogging information completenessVSAvoidlog search complexity
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent merges multiple per-job logs into a single centralized log. The job control log receives and stores messages from all individual job logs in one unified location, allowing users to access all logging information through a single search operation rather than searching across multiple separate logs.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The job control log serves multiple functions: it maintains individual job logs, aggregates messages from all jobs, provides centralized access point, and enables end-to-end event reporting across the entire application. This single logging mechanism handles both individual job tracking and global application monitoring.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If multiple separate job logs are maintained for different jobs, then each job can be tracked individually, but the complexity of analyzing different logs increases due to non-standardized content

Engineering Contradiction:
Improvejob-specific tracking accuracyVSAvoidlog analysis complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by maintaining the specific characteristics of individual job logs while adding a layer of standardization at the job control level. Each job log retains its job-specific format and content, but the job control log imposes a standardized structure on all aggregated messages, enabling consistent analysis across different jobs.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The job control log acts as an intermediary between individual job logs and the final analysis process. It receives messages from various jobs, standardizes their format, and stores them in a unified structure that facilitates consistent analysis without losing the specific details of each job.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If logging decisions are made at each job's runtime, then only necessary events can be stored to optimize performance, but the decision-making process becomes complex and performance-critical in high-volume processing

Engineering Contradiction:
Improveprocessing throughputVSAvoidlogging decision complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the logging decision-making logic from individual jobs and centralizes it in the job control log. Individual jobs simply send their messages to the job control log without making logging decisions, while the job control log centrally determines which messages to store, simplifying the decision process and reducing per-job complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

4Loss of information

If each job maintains its own log, then job-specific information is preserved, but end-to-end event reporting for a specific object across multiple jobs becomes extremely difficult

Engineering Contradiction:
Improvejob-specific detail retentionVSAvoidevent reporting accuracy
Core Design Contradiction:
Loss of informationVSManufacturing precision

Solution Approach 1:

The patent adds a new dimension to logging by creating a hierarchical structure with both individual job logs and a centralized job control log. This two-level approach allows simultaneous preservation of job-specific details in individual logs and enables end-to-end event reporting through the centralized log that aggregates information across all jobs.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS9098613B2Logging of application messages
Publication Date: 2015.08.04 SAP SE
  • US9098613B2 patent drawing
  • US9098613B2 patent drawing
  • US9098613B2 patent drawing

AI summary

The processing application includes numerous jobs for performing processing operations on computing objects. Whereas previous systems log job information on a per job basis, the apparatus and method includes generating application messages. These application messages are generated based on events in the operation of the application and the messages include predefined event information. The application messages are processing and filtered by a central logging device, which may be in response to customization properties. From this central logging device the filtered messages are centrally stored in an application log database, thereby providing a central depository and formatting of previously incongruent job-specific logging data.