Cross-Deployment Business Object Communication via Message Broker
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business enterprises face challenges in integrating business objects across different deployment units, as local calls are not available between deployment units, requiring low-level access to system utilities that are typically not accessible to partners, making cross-deployment unit integration complex and requiring platform provider involvement.
Innovation Solution
A method for exchanging information between business objects in different deployment units involves selecting a business object, detecting triggering events, evaluating conditions, assembling messages based on mapping information between objects, and using process agents to instantiate and send actions, enabling asynchronous communication and modification of business objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If local calls are used for communication between business objects, then integration within a deployment unit is simple and efficient, but communication between different deployment units is not possible
Solution Approach 1:
The patent introduces a message broker as an intermediary component that enables communication between business objects in different deployment units. The message broker receives messages from publishing business objects, routes them according to subscription criteria, and delivers them to subscribing business objects, thereby enabling cross-deployment unit communication without requiring direct calls between objects.
2Adaptability or versatility
If direct integration methods are used for cross-deployment unit communication, then communication can be established, but low-level access to system utilities is required which is not available to partners
Solution Approach 1:
The patent enables business objects to publish and subscribe to messages using high-level, standardized interfaces that do not require access to low-level system utilities. Business objects can independently configure their publishing and subscribing behavior through declarative subscriptions that specify message types and routing criteria, eliminating the need for complex system utility access.
3Reliability
If platform provider involvement is required for cross-deployment unit integration, then proper integration can be achieved, but partner independence and deployment flexibility are reduced
Solution Approach 1:
The patent creates a universal message broker service that provides standardized publishing and subscribing capabilities available to all business objects across deployment units. This universal interface allows partners to independently implement cross-deployment unit integration without requiring platform provider involvement, while maintaining reliable and correct integration through standardized routing and message delivery mechanisms.
Data Source
AI summary
Disclosed is an architecture that allows business objects to communicate across deployment unit boundaries. A runtime object may be defined to listen for a trigger event in an offering business object. The runtime object then assemble and communicate a message for processing by a consuming business object. User interfaces allow a user to configure a service integration definition to generate the runtime object.