Runtime Message Scenario Enrichment for Cross-Component Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current message exchange systems like SAP's XI lack a notion of cross-component message scenarios, making it difficult to monitor and control message exchanges effectively, especially under high message loads, as they only allow explicit selection criteria without the ability to define subsets of messages based on execution attributes.
Innovation Solution
A system and method for defining messaging scenarios by enriching message formats with scenario attributes at runtime, allowing for aggregated views and selective monitoring based on priority, business area, or technical components, using direct, agreement, and hash representations to integrate scenario attributes into an aggregation infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If explicit selection criteria are used in monitors for different messaging components, then message monitoring is possible, but it becomes difficult to monitor and control message exchanges effectively under high message loads without a notion of cross-component message scenarios
Solution Approach 1:
The patent introduces scenario definitions as an intermediary layer between messages and monitors. Scenario attributes are enriched into message headers at runtime, acting as a mediator that enables centralized control and monitoring of cross-component message scenarios without requiring complex configurations in each individual monitor.
Solution Approach 2:
The scenario definition mechanism provides a universal approach for monitoring different types of messages across multiple messaging components (integration server, adapter engine, etc.) through a single centralized configuration, rather than requiring separate explicit selection criteria in each component's monitors.
2Measurement precision
If all messages are monitored individually with explicit selection criteria, then comprehensive monitoring coverage is achieved, but error detection and system health assessment become difficult in complex message exchange systems
Solution Approach 1:
The patent merges monitoring capabilities by introducing scenario definitions that can encompass multiple messages and components. Monitors can be configured to watch entire message scenarios rather than individual messages, combining monitoring precision with simplified error detection through aggregated scenario-level views.
3Ease of operation
If scenario attributes are enriched into message format at runtime, then selective monitoring based on message subsets is enabled, but additional processing overhead is introduced
Solution Approach 1:
Scenario attributes are enriched into message headers at runtime, which is a preliminary action that prepares messages for efficient filtering and monitoring. This preliminary enrichment enables subsequent selective monitoring operations to be performed quickly without requiring complex analysis of message content during monitoring.
Data Source
AI summary
A computer-implemented method, computer program product, and system for monitoring messages being exchanged at runtime between two or more applications via a message exchange infrastructure are presented. A scenario definition for one or more messages is provided, the scenario definition including a number of scenario conditions that are associated with a set of scenario attributes related to the message header and/or message payload. A message format of the one or more messages is enriched at runtime with an associated set of scenario attributes.