Web Services Manager SOAP Logging for Custom Metrics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for managing web-based services lack a holistic view of interactions and require extensive coding efforts to create custom metrics, leading to performance issues and inefficiencies in monitoring and optimizing business processes.
Innovation Solution
A system and method for monitoring web-based services that involves receiving transactions, logging performance data, and generating reports based on pre-defined metrics, allowing business users to define and compute custom metrics without coding through a web services manager that utilizes pre-built functions and data models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If code-mapping execution data into business metrics is implemented, then business-oriented management capability is improved, but development and maintenance effort increases severely
Solution Approach 1:
The patent introduces SOAP message logging as an intermediary mechanism that automatically captures service execution data without requiring custom coding for each metric. The logging system acts as a mediator between the web service execution and business metrics generation, eliminating the need for direct code-mapping while preserving full measurement capability.
Solution Approach 2:
The patent creates a copy of the execution data through SOAP message logging, storing complete transaction information in a standardized format. This copied data can then be queried and analyzed to generate any business metric without requiring additional coding, as the complete execution picture is already captured in the logged SOAP messages.
2Loss of information
If SOAP message logging is used to collect performance data, then holistic view of service interactions is improved, but performance problems occur when large number of real-time reports are needed
Solution Approach 1:
The patent performs preliminary action by logging complete SOAP messages at the point of service execution, capturing all interaction data in advance. This pre-captured data is stored in a structured format that enables efficient querying later, eliminating the need for real-time data collection during report generation and thus avoiding performance bottlenecks.
Solution Approach 2:
The patent segments the performance monitoring system into distinct components: SOAP message logging, data storage, and metric generation. This segmentation allows the logging to occur independently at service execution time, while report generation can query and process only the specific data needed, improving real-time performance by avoiding processing of unrelated data.
3Measurement precision
If custom metrics are created through intensive coding, then specific business requirements are met, but rapid creation of new metrics becomes difficult
Solution Approach 1:
The patent creates a reusable copy of the data collection mechanism through standardized SOAP message logging. Once the logging infrastructure is in place, any custom metric can be generated by querying the logged data with different parameters, eliminating the need to rewrite collection code for each new metric while maintaining precise measurement capability.
Solution Approach 2:
The patent implements a universal SOAP message logging system that serves multiple functions: capturing execution timing, tracking service interactions, storing request/response data, and enabling various business metrics. This single universal logging mechanism replaces multiple specialized coding efforts, allowing rapid creation of different metrics from the same data source.
Data Source
AI summary
A method and system are disclosed for monitoring the performance of web-based services. The method comprises receiving a transaction from a client and routing the transaction to an appropriate web service for execution of the transaction. During execution of the transaction, performance data relating to the execution of the transaction is monitored and logged. The collected performance data is then queried based on pre-defined performance metrics and web service performance reports are generated. A system for the foregoing method is also disclosed.