Messaging Layer Embeds JMS in Trigger Subsystem
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current application integration solutions face challenges in using the 'trigger subsystem' capabilities with standards-based messaging protocols like JMS, requiring custom implementation and leading to non-standardized solutions, and lack a configuration-driven approach for processing SOAP messages over JMS transport.
Innovation Solution
A messaging layer that fully embeds JMS as a peer to proprietary messaging protocols in the integration server trigger subsystem, enabling JMS messaging without adapters and reducing custom programming, and provides a configuration-driven approach for standards-based messaging protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a proprietary messaging protocol is used with the trigger subsystem, then rich feature sets and advanced capabilities are available, but standards-based interoperability and ease of integration are reduced
Solution Approach 1:
The patent introduces a messaging layer as an intermediary component that sits between the trigger subsystem and external messaging systems. This messaging layer provides standardized interfaces (JMS, SOAP) that translate external messages into the proprietary trigger subsystem's internal format, enabling standards-based interoperability without requiring custom programming throughout the entire system. The messaging layer acts as a mediator that handles protocol conversion and integration complexity isolation.
Solution Approach 2:
The system is segmented into distinct layers: the trigger subsystem layer that provides rich capabilities, and the messaging layer that handles standards-based communication. This segmentation allows each layer to be optimized independently - the trigger subsystem maintains its advanced features while the messaging layer provides standardized interfaces, reducing overall system complexity for integration.
2Adaptability or versatility
If a JMS adapter is used for standards-based messaging, then interoperability is improved, but the trigger subsystem capabilities cannot be fully utilized and non-standardized implementations are required
Solution Approach 1:
The patent merges the messaging layer functionality directly into the integration server alongside the trigger subsystem, rather than using a separate adapter. This unified architecture allows both the trigger subsystem capabilities and standards-based messaging (JMS, SOAP) to be fully utilized simultaneously. The messaging layer and trigger subsystem share common infrastructure and can work together seamlessly, eliminating the limitations of separate adapter-based approaches.
3Adaptability or versatility
If custom programming is implemented for each new application to access trigger subsystem capabilities, then application-specific functionality is achieved, but configuration time and deployment complexity increase
Solution Approach 1:
The messaging layer provides self-service capabilities through configuration files and standardized interfaces. Applications can access trigger subsystem capabilities through predefined messaging patterns and configurations rather than requiring custom programming for each application. The system enables developers to configure messaging behavior through standard mechanisms, reducing configuration time while maintaining application-specific functionality.
4Productivity
If proprietary messaging infrastructure is used, then advanced integration capabilities are available, but portability and interoperability with external systems are reduced
Solution Approach 1:
The messaging layer is designed with universal interfaces that support multiple messaging standards (JMS, SOAP, proprietary protocols). This multi-functionality allows the same underlying trigger subsystem to work with different messaging protocols and external systems, providing both advanced integration capabilities and portability. The messaging layer can adapt to different protocol requirements while leveraging the unified trigger subsystem infrastructure.
Data Source
AI summary
The example embodiments disclosed herein relate to application integration techniques built around the publish-and-subscribe model (or one of its variants). In certain example embodiments, a first standards-based messaging protocol (e.g., the JMS messaging protocol) may be used to create a trigger so that a message envelope according to a second standards-based messaging protocol (e.g., SOAP) may be communicated over the first standards-based messaging transport layer. In other words, in certain example embodiments, a trigger according to a first protocol (e.g., JMS) may have a message according to a second protocol (e.g., SOAP) associated therewith so as to enable the message to be communicated over the first protocol's transport layer. The trigger may be configured to receive a message from a web service consumer via the JMS messaging protocol and pass it to the web service stack for dispatch to the web service provider. Similarly, for a request-reply web service exchange pattern, the trigger may be configured to send the reply message from the web service provider, as returned by the web service layer, to the web service consumer via the JMS messaging protocol.