Dynamic Software Component Replacement via Vestibule Bank
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-host transaction processing environments, software installation is complex, error-prone, and results in significant downtime due to conflicts with shared storage and multiple hosts, preventing non-stop service availability.
Innovation Solution
A non-stop multi-host transaction processing environment is achieved through the use of an installation manager and a vestibule bank that stages replacement software components, drains user calls from the old component, queues new calls, and routes them to the replacement component, ensuring seamless service continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software components are replaced in a multi-host environment, then software updates can be deployed, but system downtime occurs and service continuity is interrupted
Solution Approach 1:
The patent stages the replacement component in advance before the old component is taken offline. The installation manager prepares the replacement component in a ready state, so that when the old component is drained of user calls, the replacement can immediately take over without interruption to service.
Solution Approach 2:
The patent introduces a vestibule bank as an intermediary layer between user calls and the component being replaced. The vestibule bank intercepts and queues incoming user calls during the replacement process, preventing them from reaching the old component and ensuring they are properly routed to the replacement component afterward.
2Adaptability or versatility
If software installation is performed in a multi-host environment with shared storage, then new software versions can be deployed, but installation complexity and error rates increase
Solution Approach 1:
The patent extracts the installation management functionality from the complex multi-host environment and consolidates it into a dedicated installation manager component. This separate installation manager handles all aspects of component replacement, including staging, draining, and routing, thereby simplifying the overall installation process and reducing errors.
Solution Approach 2:
The installation manager autonomously manages the entire replacement process without requiring manual intervention for each step. It automatically stages replacement components, drains user calls from old components, queues incoming calls during replacement, and routes calls to replacement components, making the system self-managing and reducing installation complexity.
3Stability of the object's composition
If locks are placed on shared control files during component updates, then file consistency is maintained, but other database manager copies cannot access the file and processing stops
Solution Approach 1:
The patent segments the component replacement process into distinct phases: staging the replacement component, draining user calls from the old component, performing the replacement, and routing calls to the new component. This segmentation allows file locks to be applied only during the actual replacement phase rather than during the entire update process, maintaining file consistency while minimizing impact on other database manager copies.
Data Source
AI summary
A non-stop multi-host transaction processing environment may be created by receiving incoming user calls to components through a vestibule bank, and by utilizing an installation manager during the replacement of software. The installation manager may be used in connection with a vestibule bank to handle user calls during the installation of a replacement software component such that user calls for a component can be processed while that component is being replaced, without an error being passed back to the end user. During the replacement of a software component, user calls from the old component may be drained and diverted to a replacement component. User calls received during the installation may be queued and then routed to the replacement component once the component has been replaced.


