Managed Server Independence for Software Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud computing and application server environments, managed servers may not always be available to respond to administration servers, leading to failed deployment operations, especially in large enterprise applications deployed across thousands of servers, and existing systems lack robustness in handling errors during deployment, particularly in environments like Oracle Fusion Applications or Lifecycle Management.
Innovation Solution
A system and method for managed server independence (MSI-D) that allows software applications and libraries to be deployed in a multi-version format, enabling managed servers to independently poll for configuration updates and perform changes, thereby reducing dependency on administration servers and ensuring eventual consistency of application and library versions across multiple servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If managed servers rely on administration server for deployment operations, then centralized control is maintained, but deployment reliability decreases when servers are unavailable
Solution Approach 1:
Managed servers are empowered to independently poll for deployment configuration changes and self-update without requiring continuous availability of the administration server. Each managed server autonomously checks for configuration updates, determines version differences, and performs self-upgrade when changes are detected, eliminating the single-point dependency on the administration server and enabling deployment to continue even when the administration server is unavailable.
2Productivity
If deployment operations require administration server availability, then centralized deployment control is maintained, but deployment speed decreases due to server unavailability
Solution Approach 1:
Deployment configurations are prepared in advance and stored in a shared file system accessible to all managed servers. The deployment configuration file contains pre-defined version information and update instructions that managed servers can retrieve without real-time administration server intervention, enabling rapid self-upgrade operations.
Solution Approach 2:
Managed servers implement a polling mechanism that periodically checks for configuration changes in the shared file system. When changes are detected, the server automatically initiates the upgrade process by comparing version information and executing the necessary updates, creating a closed-loop feedback system that ensures deployment continuity without requiring constant administration server availability.
3Extent of automation
If error messages are handled by administrative scripts, then automated error handling is achieved, but adaptability to unexpected situations decreases
Solution Approach 1:
The deployment system incorporates built-in self-diagnosis and self-recovery capabilities that allow managed servers to autonomously handle deployment errors without requiring pre-programmed administrative scripts. The system can detect deployment failures, log errors, and attempt automatic recovery actions, providing adaptability to unexpected situations while maintaining high levels of automation.
Data Source
AI summary
In accordance with an embodiment, described herein is a system and method for managed server independence for deployment (MSI-D) of software applications and libraries, for use in a cloud computing, application server, or other environment. Software applications or libraries can be prepared for deployment as multi-version format application(s) or library(s). A deployment configuration tool enables use of an input file which specifies one or more deployment configuration overrides data that provide additional pieces of information for each MSI-D/multi-version format application and library. A managed server can independently poll for changes to the deployment configuration overrides, for example to update one or more of its deployed applications or libraries, from a first version to a second version. The system can be used to provide eventual consistency of the deployed application and library versions within a plurality of managed servers.