Local Alert Engine for BPM-PI Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business Process Management (BPM) systems lack a centralized configuration conception, making it difficult to integrate BPM alerts with Process Integration (PI) alerting solutions, as BPM configuration details are not exposed to central repositories and require local configuration for error handling.
Innovation Solution
A computer-implemented method that identifies business process runtime errors, evaluates them using rules and configuration information in a JavaScript Object Notation (JSON) format, and stores alerts, enhancing PI alerting with BPM-specific rules stored in a PI directory for central configuration and local alert engines to process errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If BPM configuration is decentralized and stored locally with BPM runtime, then BPM can operate independently without central repository dependency, but integration with PI alerting solutions becomes difficult and configuration management complexity increases
Solution Approach 1:
The patent introduces a local alert engine as an intermediary component within the BPM runtime that bridges the gap between decentralized BPM configuration and centralized PI alerting solutions. This local alert engine evaluates BPM runtime events using locally stored configuration and rules, then communicates with the PI alerting infrastructure, thereby enabling integration without requiring BPM to expose its configuration details to external repositories.
2Reliability
If BPM configuration details are not exposed to central repositories, then BPM maintains security and encapsulation, but alert integration with PI solutions requires complex local configuration
Solution Approach 1:
The patent segments the alerting functionality into two distinct parts: a local alert engine that operates with BPM runtime using locally stored configuration and rules, and a communication interface that bridges to the PI alerting solution. This segmentation allows BPM configuration to remain encapsulated and secure while still enabling alert integration through the localized evaluation and selective communication of alert events.
3Productivity
If centralized configuration repository is implemented for PI components, then configuration distribution and caching efficiency improve, but BPM alerts cannot leverage this central repository due to lack of configuration exposure
Solution Approach 1:
The patent applies local quality by storing alert rules and configuration information locally within the BPM runtime environment rather than attempting to access the PI central configuration repository. This local storage approach allows the local alert engine to efficiently evaluate BPM runtime events using locally available configuration and rules, maintaining the performance benefits of local access while enabling BPM-PI integration without requiring configuration exposure to external repositories.
Data Source
AI summary
A computer implemented method may include identifying one or more business process runtime events received at an events queue of a process integration runtime component. One or more errors associated with the business process runtime events may be identified. The one or more errors may be evaluated based, at least in part, on one or more rules associated with the business process runtime event and configuration information associated with the process integration runtime component. The one or more rules may be associated with the business process runtime event and configuration information associated with the process integration runtime component having the same format. An alert for the one or more errors associated with the business process runtime event can be stored.