Event Notification Component for LOB Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Information workers face challenges in accessing and synchronizing business object data stored in line of business (LOB) systems, particularly when entities do not support read operations or return partial data, making it difficult for composite applications to manage shared data across multiple applications.
Innovation Solution
Implementing an event notification system with a middle-tier LOB server that includes an event notification component comprising an event agent, notification service, and user event queue, which converts change events into standard LOB entity events and stores them in a user event queue for clients to receive notifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If read operations are not supported by LOB entities, then data security and system integrity are maintained, but applications cannot programmatically access or synchronize business object data
Solution Approach 1:
The patent introduces an event notification component as an intermediary between the LOB system and external applications. This component includes an event agent that monitors LOB data changes, converts them to standardized events, and delivers them to applications without requiring direct read access to the LOB entities, thus maintaining data integrity while enabling application access
Solution Approach 2:
The event notification system creates copies of change event data rather than requiring applications to read the original LOB entities. The event agent captures change events and converts them to LOB event messages that contain the necessary data information, allowing applications to work with event data copies while the original LOB entities remain protected
2Reliability
If applications continuously read LOB entities to detect changes, then data synchronization is achieved, but system performance and efficiency deteriorate
Solution Approach 1:
The event notification system performs preliminary action by proactively monitoring and detecting LOB data changes before applications need to read them. The event agent continuously watches for changes and immediately generates notification events when changes occur, eliminating the need for applications to continuously poll or read LOB entities to detect changes
Solution Approach 2:
The system implements feedback by establishing an event subscription mechanism where applications register for specific LOB entity types and receive targeted change notifications. The event agent monitors LOB changes and provides feedback to subscribed applications only when relevant changes occur, creating an efficient pull-based notification system rather than continuous pushing
3Ease of operation
If data is served by external store for read-less entities, then application data access is enabled, but system complexity increases
Solution Approach 1:
The event notification component serves multiple functions within a single integrated system: it monitors LOB data changes, converts various LOB change events to standardized events, manages event queuing and delivery, and supports multiple application subscriptions. This multi-functional approach enables data access without requiring separate external stores for each LOB entity type
Data Source
AI summary
Techniques to manage event notifications are described. An apparatus may comprise a server having an event notification component. The event notification component may have an event agent component to receive a message indicating a change event for line of business (LOB) data, and convert the change event to a defined LOB entity event. The event notification component may have a notification service component to generate a LOB event message for the entity event. The event notification component may have an event database to store the event message in a user event queue. Other embodiments are described and claimed.