SOA Registry Consistency Enforcement for XML Processing Tasks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex distributed computing environments, such as those used in manufacturing, require a flexible yet controlled adaptation of processing sequences to ensure production continuity and prevent potential damages, which existing SOA-registries fail to provide by lacking consistency enforcement mechanisms.
Innovation Solution
A consistency enforcement system for XML objects in an SOA-registry that includes an interface for updating XML objects with additional processing tasks and a validation unit to match these tasks against predefined identifiers, ensuring only approved changes are stored and executed, using a whitelist or blacklist approach to control adaptability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the processing sequence is made flexible to allow adaptation by individual parties, then adaptability is improved, but the risk of unallowed changes that could stop production or cause damages increases
Solution Approach 1:
The patent introduces an SOA-registry as an intermediary between the processing parties and the processing sequence definitions. The registry stores and manages processing task XML elements, acting as a centralized coordination point that enables flexible adaptation while maintaining overall control and consistency across the distributed computing environment.
Solution Approach 2:
The system implements feedback mechanisms where processing task definitions are stored in the SOA-registry and can be queried and validated. This allows individual parties to adapt processing tasks while the system can verify that adaptations remain within allowed boundaries, providing continuous monitoring and control.
2Reliability
If strict control is imposed on processing sequence adaptations, then production continuity is maintained, but the ability of individual parties to adapt to their individual needs is reduced
Solution Approach 1:
The patent segments the processing sequence into individual processing task XML elements that can be independently defined, stored in the SOA-registry, and adapted by individual parties. This segmentation allows fine-grained control where specific tasks can be modified without affecting the entire processing sequence, balancing flexibility with stability.
Solution Approach 2:
The system implements dynamic adaptability where processing task definitions can be modified by individual parties based on their specific needs, while the SOA-registry maintains the overall structure and coordination. This dynamic approach allows the system to adapt to changing requirements while preserving production continuity through centralized management.
3Adaptability or versatility
If distributed computing systems are allowed to operate independently, then system flexibility is improved, but coordination and consistency across the network becomes more difficult
Solution Approach 1:
The SOA-registry serves as a universal coordination mechanism that works across all distributed computing systems in the network. It provides a common interface and standardized XML-based task definitions that enable independent systems to coordinate efficiently, reducing the complexity of inter-system communication while maintaining independence.
Solution Approach 2:
The system uses XML parameters and task definitions to standardize communication between distributed systems. By changing the representation of processing tasks into a universal XML format stored in the SOA-registry, the system enables independent computing systems to interact through standardized parameters, simplifying coordination while preserving system independence.
Data Source
AI summary
A consistency enforcement system includes an XML object of an SOA-registry. The XML object includes a plurality of processing task XML elements that define a processing task to be performed the SOA. An updated XML object is received through an interface. The updated object includes at least one additional processing task XML element that defines at least one further processing task to be performed by the SOA. A validation unit is use to query the SOA-registry in order to obtain one or more predefined processing task identifiers. The validation unit matches a processing task identifier of the at least one additional processing task XML element of the updated XML object against the one or more predefined processing task identifiers obtained from the SOA-registry and approves or rejects the updated XML object (20′) depending on the result of the match.