Software Update Container Routing Across Heterogeneous Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of updating software across disparate systems is complex and burdensome, requiring synchronous activation of software updates and proper version dissemination to avoid issues during execution, especially when dealing with systems of different technologies like ABAP and J2EE.
Innovation Solution
A method involving the creation of a container that includes software objects and attributes to configure transport, allowing for the deployment of software updates across different applications, managed by a transport manager that routes updates through a base system to development, quality assurance, and production systems, using attributes like application type, sub-application type, and vendor information to control deployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software updates are disseminated across disparate systems, then system functionality is improved, but the complexity of the update process increases
Solution Approach 1:
The patent creates a universal container format that can hold software objects for multiple different system types (ABAP, J2EE, and other disparate systems) within a single standardized structure. This container serves multiple functions: packaging, version control, routing, and deployment across heterogeneous systems, thereby improving update capability while managing complexity through standardization.
Solution Approach 2:
The transport manager acts as an intermediary component that receives containers from various source systems, manages the routing logic, and distributes software objects to appropriate target systems. This mediator handles the complexity of cross-system compatibility and synchronous activation requirements, shielding individual systems from the intricacies of the update process while enabling broad software update capability.
2Stability of the object's composition
If synchronous activation of software updates is enforced across systems, then version consistency is improved, but the operational burden increases
Solution Approach 1:
The patent merges multiple software objects and their version information into a single container that is processed and activated together. By combining related software objects into one deployable unit, the system ensures version consistency across disparate systems while reducing the operational burden of managing multiple separate update processes. The container acts as an atomic unit that maintains version integrity.
Solution Approach 2:
The transport manager serves as an intermediary that automatically handles the coordination of synchronous activation across multiple systems. It manages the routing and deployment of containers to ensure that all systems receive and activate the correct versions simultaneously, thereby maintaining version consistency while eliminating the manual coordination burden that would otherwise be required.
3Reliability
If proper software version dissemination is implemented, then execution reliability is improved, but the transport management complexity increases
Solution Approach 1:
The container format incorporates multiple functions within a single standardized structure: it packages software objects, embeds version information, includes routing attributes, and provides deployment metadata. This universal container ensures that all necessary information for reliable execution is contained within one object, improving execution reliability while managing transport complexity through consolidation rather than proliferation of separate management mechanisms.
Data Source
AI summary
The subject matter disclosed herein provides methods and apparatus, including computer program products, for providing software updates. In one aspect there is provided a method. The method may include receiving software objects associated with a software update. Moreover, a container may be provided. The container may include the received software objects and attributes. The attributes may describe the software objects to configure transport to different applications. Related systems, apparatus, methods, and/or articles are also described.