Web Service Integration via WSDL Messaging Destinations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in seamlessly integrating web services with existing messaging configurations, often requiring gateway programs or proxies, which hide service details and complicate the selection of services and ports.
Innovation Solution
A method and system that map WSDL document elements to messaging destinations within the messaging infrastructure, allowing direct addressability and invocation of web services using messaging infrastructure facilities, eliminating the need for gateways or proxies by generating messaging destinations for service and port elements and providing associated invocation mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a gateway program or proxy is used to integrate web services with messaging infrastructure, then integration capability is improved, but device complexity increases and service details are hidden
Solution Approach 1:
The patent extracts the integration logic from a separate gateway program and embeds it directly into the messaging infrastructure. The messaging system natively generates messaging destinations from WSDL port elements and provides invocation mechanisms, eliminating the need for an external gateway component while maintaining integration capability.
Solution Approach 2:
The patent introduces a mapping mechanism as an intermediary that automatically maps WSDL service and port elements to messaging destinations. This mapping mechanism bridges the web service interface definition and the messaging infrastructure without requiring a full gateway, reducing complexity while enabling seamless integration.
2Adaptability or versatility
If a gateway program is used for web service access, then integration is achieved, but ease of operation deteriorates due to infrastructure-specific configuration requirements
Solution Approach 1:
The patent makes the messaging infrastructure universally compatible with web services by natively supporting WSDL-based service invocation. The system can handle multiple web service protocols and messaging configurations through a unified interface, eliminating infrastructure-specific configuration requirements and simplifying service selection.
Solution Approach 2:
The messaging system automatically generates messaging destinations and invocation mechanisms from WSDL definitions without requiring manual gateway configuration. The system self-configures the integration by parsing WSDL port elements and creating appropriate messaging destinations, reducing operational complexity.
3Reliability
If gateway programs are used to hide web service details, then security is improved, but information availability deteriorates
Solution Approach 1:
The mapping mechanism serves as a transparent intermediary that preserves service detail visibility. It maps WSDL port elements to messaging destinations while maintaining the ability to trace and understand the relationship between web service interfaces and messaging infrastructure, unlike opaque gateways that hide these details.
Data Source
AI summary
A method, system and computer program for addressing a web service defined by a service definition document, such as a Web Services Definition Language (WSDL) document. The method includes, for example, generating a messaging destination for a service element, and each associated port element, of the WSDL document, and providing an invocation mechanism associated with each port destination for invoking the web service. A destination is an addressable location in the messaging configuration, such as a message queue.