Business Process Management System for Message-Based Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current enterprise systems face challenges in accurately representing business processes and flexibility in dynamic scenarios due to hardwired integration capabilities and limited connectivity among applications, making comprehensive system upgrades costly and unfeasible.
Innovation Solution
A business process management (BPM) system and method that uses a business process engine to manage and execute message-based communication according to actual business processes, enabling correlation, serialization, transformation, and multicast capabilities across heterogeneous systems using open standards like XML and HTTP.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If comprehensive system upgrades or large-scale replacement strategies are implemented to achieve connectivity among all applications, then system integration capability is improved, but cost and implementation time increase significantly
Solution Approach 1:
The patent introduces a message broker as an intermediary component that enables communication between applications without requiring direct integration or system upgrades. The message broker receives, routes, and manages messages between heterogeneous systems, allowing legacy applications to communicate effectively while avoiding costly comprehensive system replacements.
Solution Approach 2:
The message broker is designed as a universal platform that can handle multiple communication protocols and message types simultaneously. It provides multi-functional capabilities including message routing, transformation, persistence, and event-driven architecture support, enabling a single system to serve diverse integration needs across the enterprise landscape.
2Reliability
If direct one-to-one connections are established between application components to achieve integration, then communication reliability is improved, but system complexity and difficulty of management increase
Solution Approach 1:
The message broker serves as a central intermediary that manages all communication between applications. Instead of establishing direct one-to-one connections between application pairs, the broker receives messages from senders and routes them to appropriate receivers, maintaining reliable communication while significantly reducing system complexity and making integration management more straightforward.
Solution Approach 2:
The patent segments the integration architecture into distinct functional components: message producers, message broker, and message consumers. This segmentation allows each component to be developed, deployed, and managed independently, reducing overall system complexity while maintaining reliable communication through the structured message flow managed by the broker.
3Speed
If integration capabilities are hardwired into application components to achieve direct communication, then communication speed is improved, but adaptability to dynamic business scenarios decreases
Solution Approach 1:
The message broker implements dynamic routing capabilities that allow message flow paths to be changed at runtime based on business requirements. Instead of hardwired static connections, the system can dynamically route messages between different applications and services, enabling rapid adaptation to changing business scenarios while maintaining efficient communication through the broker's optimized message handling.
Solution Approach 2:
The system allows configuration parameters such as routing rules, message formats, and protocol specifications to be changed without modifying the underlying application code. The message broker interprets these parameter changes and adjusts its behavior accordingly, enabling the system to adapt to dynamic business scenarios while maintaining fast communication through pre-established message channels.
4Ease of operation
If batch processing is used to manage business processes to simplify system operation, then ease of operation is improved, but real-time processing capability deteriorates
Solution Approach 1:
The message broker supports both periodic batch processing and event-driven real-time processing modes. For routine operations, it can process messages in batches at scheduled intervals, providing ease of operation. When real-time response is required, the broker's event-driven architecture enables immediate message routing and processing, allowing the system to switch between processing modes based on specific business needs without sacrificing either ease of operation or real-time capability.
Data Source
AI summary
Methods and systems for managing integration of a heterogeneous application landscape are disclosed. The landscape is defined by one or more business process. A business process management system includes an integration server connected between two or more applications in the landscape. The integration server includes a business process engine configured to execute one or more business processes that define message-based interactions between the two or more applications. The business process management system further includes a runtime engine, under direction of the business process engine, for executing one or more messaging services on the message-based interactions between the two or more applications.