Trigger Subsystem Embedding JMS for Feature-Rich Messaging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current application integration solutions face challenges in fully utilizing the capabilities of integration server trigger subsystems with standards-based messaging protocols like JMS, requiring custom implementation and non-standardized configurations, leading to a tradeoff between feature-rich proprietary protocols and interoperable messaging.
Innovation Solution
Embedding JMS as a peer to the proprietary messaging protocol in the integration server trigger subsystem, enabling access to all capabilities through a common trigger subsystem without the need for special adapters or custom programming, and providing parallel subsystems for proprietary and standards-based messaging.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a proprietary messaging protocol is used in the trigger subsystem, then feature-rich capabilities are available, but interoperability and standards-based integration are limited
Solution Approach 1:
The trigger subsystem is designed to support multiple messaging protocols (proprietary and JMS) through a common architecture. The subsystem can function with different protocol types without requiring separate implementations, achieving multi-functionality that resolves the contradiction between feature richness and integration complexity
Solution Approach 2:
A protocol adapter or intermediary layer is introduced between the trigger subsystem and messaging protocols. This intermediary enables the subsystem to work with both proprietary and standards-based protocols like JMS, reducing direct integration complexity while maintaining access to feature-rich capabilities
2Adaptability or versatility
If JMS messaging is integrated with proprietary protocol, then interoperability is improved, but full access to feature-rich capabilities may be limited
Solution Approach 1:
The intermediary layer translates JMS messages into the proprietary protocol format that the trigger subsystem expects. This translation mechanism ensures that interoperability with standards-based messaging is achieved while maintaining full access to the subsystem's feature-rich capabilities through the protocol conversion
Solution Approach 2:
The system changes the parameter of message format from JMS protocol to proprietary protocol through the intermediary. This parameter transformation allows the trigger subsystem to process JMS messages while maintaining its full functionality, resolving the contradiction between interoperability and capability completeness
3Ease of manufacture
If custom implementation is used for JMS integration, then specific requirements are met, but configuration complexity and lack of standardization increase
Solution Approach 1:
The trigger subsystem provides a universal interface that works with both proprietary and JMS protocols through a common architecture. This eliminates the need for custom implementation for each protocol type, reducing configuration complexity while maintaining ease of integration through standardized access patterns
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The example embodiments disclosed herein relate to application integration techniques and, more particularly, to application integration techniques built around the publish-and-subscribe model (or one of its variants). In certain example embodiments, triggers are provided for establishing subscriptions to publishable document types and for specifying the services that will process documents received by the subscription. A standards-based messaging protocol (e.g., JMS messaging) may be fully embedded as a peer to a proprietary messaging protocol provided to an integration server's trigger subsystem so that all or substantially all of the feature-rich capabilities available via the proprietary protocol may also become available via the standards-based messaging protocol. The triggers may be JMS triggers in certain example embodiments.