Web Service Conversation Managed Object for Distributed Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current frameworks lack a standard method for managing Web services, which are challenging due to their distributed nature, extensibility, and the need for unified yet customized management across control and management domains, along with security and service agreement enforcement.
Innovation Solution
A system and method for managing conversations in Web services, including a conversation managed object with interfaces that provide management information, monitoring capabilities, and event notification, allowing managers to track message processing and resource interactions within a unified framework.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Web services are designed to be highly extensible and loosely coupled, then adaptability and versatility are improved, but device complexity and difficulty of detecting and measuring increase
Solution Approach 1:
The patent introduces a conversation managed object as an intermediary layer between Web service participants. This mediator tracks message exchanges, maintains conversation state, and provides management interfaces without requiring changes to the extensible Web service architecture itself. The intermediary handles the complexity of monitoring and managing loosely coupled services while preserving their adaptability.
Solution Approach 2:
The system implements feedback mechanisms where the conversation managed object continuously monitors message exchanges and provides information about conversation state, participant status, and service interactions. This feedback enables managers to track and control distributed Web service conversations despite their extensible and loosely coupled nature.
2Adaptability or versatility
If Web services form distributed applications across multiple domains, then adaptability is improved, but ease of operation and ease of repair worsen
Solution Approach 1:
The conversation managed object provides universal management capabilities that work across different domains and control boundaries. It implements a standardized interface for monitoring and controlling Web service conversations regardless of where services are deployed or what domains they belong to, making distributed application management easier through a unified approach.
Solution Approach 2:
The managed object acts as a domain-neutral intermediary that sits between various control and management domains. It abstracts away domain-specific complexities and provides consistent operation and repair capabilities across distributed Web service architectures.
3Adaptability or versatility
If no standard framework is used for managing Web services, then adaptability is maintained, but device complexity and loss of information increase
Solution Approach 1:
The system performs preliminary actions by establishing a standardized framework structure in advance, including predefined interfaces and management capabilities. This framework is prepared beforehand to handle Web service conversations, ensuring that management information is captured and organized from the start without losing critical data.
Solution Approach 2:
The conversation managed object creates a standardized representation or copy of the Web service conversation state, including message exchanges, participant information, and service interactions. This standardized copy preserves management information in a structured format that can be monitored and controlled without losing details.
Data Source
AI summary
A system for managing a conversation includes one or more interfaces configured to provide management information about the conversation to a manager. The interface can be configured to provide information regarding a resource such as a Web service that contains the conversation. Information regarding the conversation that may be made available to the manager includes the number of failed messages processed by the conversation; the number of successful messages processed by the conversation; the total number of messages processed by the conversation; the number of other resources participating in the conversation; the identity of other resources participating in the conversation; an identifier of the conversation; the last message received; the last fault message received; and an identifier of the resource that contains the conversation.