Abstract Layer for CIM Schema Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The rapid evolution of the Common Information Model (CIM) schema requires frequent modifications to CIM provider code and recompilation, along with additional testing, leading to inefficiencies and potential code changes in managing objects within information handling systems.
Innovation Solution
An abstract layer that receives requests from CIM clients, generates commands, and transforms untransformed XML content into CIM data using XML registration and XSL transformation files, allowing modifications to the CIM schema without altering the abstract layer, thus ensuring forward-compatibility and minimizing code changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the CIM schema is modified to accommodate evolving management information definitions, then the adaptability and versatility of the system improves, but the device complexity and difficulty of maintenance increase due to required code modifications and recompilation
Solution Approach 1:
The patent introduces an abstract layer as an intermediary component between the CIM schema definitions and the provider code. This abstract layer handles schema interpretation and data transformation, allowing schema modifications without requiring changes to provider code. The abstract layer mediates between the evolving CIM schema and the stable provider implementation, resolving the contradiction between adaptability and complexity.
Solution Approach 2:
The system is segmented into distinct layers: the CIM schema layer, the abstract layer, and the provider layer. This segmentation allows independent modification of the schema layer without affecting the provider layer. The abstract layer acts as a buffer that absorbs schema changes, enabling schema evolution while maintaining provider stability and reducing overall system complexity.
2Reliability
If provider code is modified and recompiled to accommodate CIM schema changes, then the system remains functional with updated schemas, but the loss of time increases due to recompilation and testing requirements
Solution Approach 1:
The abstract layer performs preliminary actions by pre-defining standard provider implementations and data transformation logic. When schema changes occur, the abstract layer can be configured to handle new schema versions without requiring provider recompilation. This preliminary preparation of transformation logic eliminates the time-consuming recompilation and testing cycle while maintaining system functionality.
Solution Approach 2:
The system uses template-based provider implementations that can be copied and instantiated with different schema configurations. Instead of modifying and recompiling provider code for each schema change, the abstract layer provides template mechanisms that allow rapid deployment of schema-adapted providers through configuration copying, significantly reducing the time loss associated with traditional modification and recompilation processes.
3Ease of operation
If standard CIM schema definitions are updated rapidly to reflect evolving management information needs, then the ease of operation improves for managing diverse systems, but the difficulty of detecting and measuring increases due to the need for validation testing
Solution Approach 1:
The abstract layer serves as a mediator that implements comprehensive validation logic between schema updates and provider operations. This intermediary validation layer automatically detects and measures schema compliance, reducing the difficulty of validation testing. The abstract layer's built-in validation mechanisms make it easier to operate with updated schemas while systematically detecting and measuring schema conformity without requiring extensive manual testing.
Data Source
AI summary
A system and method is disclosed for managing objects in accordance with the Common Information Model. The system and method disclosed herein includes an abstract layer that receives requests from the CIM clients through the CIM Object Manager. After the receipt of a request, the abstract layer retrieves the associated XML registration file for the generation of a command to the managed object that is the target of the request. After the command is executed with respect to the managed object, the requested data is returned to the abstract layer. The data returned to the abstract layer is in the form of untransformed XML content. The abstract layer retrieves an XSL transformation file and transforms the XML content into an instance of CIM data and transfers this data to the CIM Object Manager.