SOA Monitoring with Fuzzy Logic Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Monitoring a Service-Oriented Architecture (SOA) is challenging due to the limitations of traditional log file-based monitoring systems, which lack flexibility and are unable to detect complex errors in advance, and existing solutions fail to provide comprehensive supervision of the entire SOA landscape.

Innovation Solution

A method and system using fuzzy logic to analyze input data from SOA components, providing statistical information and response curves to classify and derive conclusions, enabling flexible and accurate monitoring of individual and overall SOA performance, with a modular and hierarchical approach to handle complex interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional log file-based monitoring systems are used, then the monitoring system is simple to implement, but the system lacks flexibility and cannot detect complex errors in advance

Engineering Contradiction:
ImproveflexibilityVSAvoidmonitoring system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The monitoring system is divided into multiple independent monitoring units, each responsible for specific SOA components. This segmentation allows the system to scale flexibly by adding or removing units as needed, while maintaining manageable complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically adapts to changing SOA landscapes by automatically discovering new components and adjusting monitoring configurations. The modular monitoring units can be dynamically added, removed, or reconfigured based on runtime conditions, providing flexibility without requiring complete system redesign.

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If centralized registry/repository is used to document SOA landscape, then the management of complex SOA is facilitated, but the system cannot automatically analyze complex situations

Engineering Contradiction:
ImproveSOA management easeVSAvoidautomatic analysis capability
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The monitoring units continuously collect and store runtime information about SOA components in the centralized registry before problems occur. This preliminary data gathering enables automated analysis by having all necessary information readily available when anomalies need to be detected, eliminating the need for manual situation assessment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements automated feedback loops where monitoring units continuously report component status to the centralized registry, which then triggers automated analysis. When threshold violations or anomalies are detected, the system automatically generates alerts and recommendations, reducing manual intervention while improving operational management.

Inventive Principle:
Principle #23Feedback

3Reliability

If monitoring units continuously monitor SOA components, then complex error situations can be detected in advance, but the amount of data to be processed increases

Engineering Contradiction:
Improveerror detection capabilityVSAvoiddata volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Each monitoring unit focuses on monitoring only its assigned SOA components rather than all components globally. This partial monitoring approach reduces the data volume each unit must process while maintaining comprehensive coverage through the distributed architecture. The system processes exactly the amount of data needed for reliable error detection without excessive overhead.

Inventive Principle:
Principle #16Partial or excessive action

4Measurement precision

If the monitoring system uses fuzzy logic to analyze input data, then the classification accuracy is improved, but the computational complexity increases

Engineering Contradiction:
Improveclassification accuracyVSAvoidcomputational complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The fuzzy logic system acts as an intermediary layer between raw monitoring data and final error classification. Instead of directly analyzing complex multi-dimensional data, the fuzzy logic intermediary transforms inputs into standardized membership values, simplifying the classification process while maintaining high accuracy. This intermediary approach manages computational complexity by breaking down complex analysis into manageable fuzzy inference steps.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2073123B1Method and system for monitoring a service oriented architecture
Publication Date: 2014.03.12 SOFTWARE AG
  • EP2073123B1 patent drawingFigure 1
  • EP2073123B1 patent drawingFigure 2~3
  • EP2073123B1 patent drawingFigure 4~5

AI summary

The invention relates to a method for monitoring a service oriented architecture (SOA), comprising a plurality of components (20, 30, 31, 40), the method comprising the steps of: a. providing at least one monitoring unit (53, M1b, M2a, M2b, M2c, ..., Mia, Mib, M1, M2, M3) for at least one of the plurality of components (20, 30, 31, 40); b. providing data concerning an operation of the at least one component (20, 30, 31, 40) as input data (60) to the at least one monitoring unit (53, M1b, M2a, M2b, M2c, ..., Mia, Mib, M1, M2, M3); and c. applying fuzzy logic in the monitoring unit (53, M1b, M2a, M2b, M2c, ..., Mia, Mib, M1, M2, M3) to analyse the input data (60) for generating at least one output value (62).