Service Engine for Java EE and JBI Protocol Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no standard communication mechanism between Java Business Integration (JBI) service providers/consumers and Java Enterprise Edition (EE) technologies, requiring implementers to manage protocol differences on a case-by-case basis, limiting direct communication between JBI and Java EE within the same Java Virtual Machine (JVM).
Innovation Solution
A service engine is introduced to facilitate bidirectional communication between Java EE and JBI using normalized messages, converting messages between different protocols and enabling direct communication within the JVM, thereby bypassing the HTTP layer and utilizing the Normalized Message Router (NMR) and binding components within JBI.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If no standard communication mechanism is implemented between JBI and Java EE, then implementers can manage protocol differences individually on a case-by-case basis, but direct communication between JBI and Java EE within the same JVM is limited
Solution Approach 1:
The service engine acts as an intermediary component between JBI and Java EE, receiving messages from either side, converting them to normalized messages, and routing them appropriately. This mediator enables standardized bidirectional communication while maintaining the ability to handle diverse protocols through the NMR and binding components.
2Adaptability or versatility
If message conversion between different protocols is performed manually on a case-by-case basis, then protocol flexibility is maintained, but communication efficiency and performance are reduced
Solution Approach 1:
The service engine provides universal message conversion capability by supporting multiple protocols through the Normalized Message Router and various binding components. Instead of implementing separate conversion logic for each protocol pair, the system uses a unified architecture that can handle any protocol combination, thereby improving communication efficiency while maintaining protocol flexibility.
Solution Approach 2:
The system changes the parameter of message format by converting messages from different protocols into a standardized normalized message format. This parameter transformation enables efficient routing and processing while maintaining the ability to adapt to different source and destination protocols through configurable bindings.
3Ease of operation
If HTTP layer is used for communication between JBI and Java EE, then communication can occur, but performance is reduced and direct JVM-level communication is not achieved
Solution Approach 1:
The service engine extracts the message conversion and routing functionality from the HTTP layer, implementing it directly within the JVM. By taking out the protocol conversion logic from the external HTTP communication layer and embedding it in the service engine, the system achieves direct JVM-level communication with improved performance while maintaining communication capability.
Data Source
AI summary
A system for bidirectional communication using normalized messages via a service engine includes a Java Enterprise Edition (EE) package, a Java Business Integration (JBI) package including a Normalized Message Router (NMR) and a binding component, and the service engine for enabling direct communication between the Java EE package and the JBI package, where the service engine converts a first message from a first protocol to a second protocol, where the first message is sent from the Java EE package to the JBI package, and the service engine converts a second message from the second protocol to the first protocol, where the second message is sent from the JBI package to the Java EE package.