Shadow System Pre-Import Versioning for Transport Request Downtime
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing software architecture update procedures often require substantial downtime due to the need to recreate changes in a new system, especially when migrating customer-specific customizations, which can be time-consuming and disruptive to business operations.
Innovation Solution
The method involves performing pre-import versioning of customer-specific transport requests during the uptime of a shadow system, allowing for parallel importation of dictionary and non-dictionary objects, and completing the import of remaining requests during downtime, thereby reducing overall business downtime and enabling continuous system availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If customer-specific transport requests are imported sequentially during system downtime, then system reliability is maintained, but business downtime increases
Solution Approach 1:
The patent performs pre-import versioning of customer-specific transport request objects during system uptime before the actual import. This preliminary action prepares the objects in advance, allowing the subsequent import process to complete faster during downtime, thus reducing the loss of time while maintaining system reliability
Solution Approach 2:
The patent divides the import process into separate phases: pre-import versioning during uptime and actual import during downtime. This segmentation allows different parts of the process to occur at different times, optimizing both reliability and downtime reduction
2Stability of the object's composition
If all customer-specific transport requests are imported during system downtime, then data consistency is ensured, but productivity decreases
Solution Approach 1:
The patent performs pre-import versioning during system uptime as a preliminary action. This prepares the transport request objects in advance without compromising data consistency, as the versioning is just preparatory work. The actual import during downtime ensures data consistency while minimizing the impact on productivity
3Stability of the object's composition
If sequential import of transport request objects is performed, then system stability is maintained, but the duration of the update procedure increases
Solution Approach 1:
The patent performs versioning as a preliminary action during uptime, which is a less resource-intensive operation. This separates the versioning step from the main import process, allowing the import to complete faster during downtime while maintaining system stability
Data Source
AI summary
When customer transport requests are included in an update procedure performed on a customer-customizable business software architecture, versioning of the objects and other features imported via such transport requests can require an extended period of business downtime using conventional methods. Additional downtime can result if the objects of the customer transports are not automatically generated. Consistent with features described herein, versioning can be done for many object types in a second shadow system or instance during uptime. The generation of objects in the customer transports can also done in the second shadow system or instance during uptime.