Web Services Runtime Framework WS-Policy Protocol Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Web services message processing runtime frameworks lack efficiency in handling business models requiring confidentiality, ordered message processing, and support for multiple transport protocols, while also being scalable and adaptable to varying business relationships.
Innovation Solution
The improved runtime framework eliminates the mapping registry and context intermediary, redesigns protocols to be state-less, and incorporates WS-Policy for enhanced message processing, enabling efficient handling of diverse business relationships and transport protocols, and supporting hibernation for reliable messaging.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the existing Web services message processing runtime framework is used, then basic message processing is supported, but efficiency is insufficient for handling business models requiring confidentiality, ordered message processing, and support for multiple transport protocols
Solution Approach 1:
The patent segments the message processing framework into distinct protocol handlers (e.g., WS-Security, WS-ReliableMessaging, WS-Addressing) that can be independently configured and applied based on specific business requirements. This allows efficient processing by only applying necessary protocols rather than a monolithic framework.
Solution Approach 2:
The framework dynamically selects and applies protocol stacks based on WS-Policy assertions in the service description. The protocol configuration is not fixed but adapts runtime based on the specific business relationship and message requirements, enabling both efficiency and versatility.
2Productivity
If the mapping registry and context intermediary are retained in the runtime framework, then existing message processing functionality is maintained, but scalability and performance are limited
Solution Approach 1:
The patent removes the mapping registry and context intermediary from the framework architecture. These components are extracted and replaced with direct protocol stack application based on WS-Policy, reducing structural complexity and eliminating bottlenecks that limited concurrent message processing scalability.
Solution Approach 2:
The service endpoint directly applies the appropriate protocol stack based on WS-Policy assertions without requiring intermediary components for mapping or context management. This self-service approach enables parallel processing of multiple messages concurrently, improving productivity.
3Productivity
If protocols are designed to be state-less, then concurrent message processing and scalability are improved, but handling of business models requiring ordered message processing and confidentiality becomes more challenging
Solution Approach 1:
The patent applies protocol stacks in a predetermined sequence defined by WS-Policy (e.g., WS-Security first, then WS-ReliableMessaging, then WS-Addressing). This preliminary ordering of protocol application ensures that confidentiality and ordering requirements are met while maintaining state-less protocol handlers that support concurrent processing.
Solution Approach 2:
The WS-Policy framework acts as an intermediary that coordinates between state-less protocol handlers, ensuring proper ordering and reliability requirements are met without requiring the protocol handlers themselves to maintain state. The policy assertions mediate the interaction between concurrent processing and reliability constraints.
Data Source
AI summary
A method and system for implementing WS-Policy is described. In one embodiment, the system includes an API that may be used to call one or more methods for processing a WS policy file. These methods are associated with one or more classes.