Automatic Redeployment Agent for IDE Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing approaches for redeploying web applications in an Integrated Development Environment (IDE) are time-consuming, requiring frequent server restarts or redeployments, which hinder productivity and efficiency, especially when only file content changes are made, leading to unnecessary redeployment of unchanged files based on timestamp changes.

Innovation Solution

An automatic redeployment agent is introduced that compares directory paths between a development code repository and a server file repository, updating only the changed files or directories in the server repository, thereby eliminating the need for full redeployment or restart, and ensuring real-time reflection of changes without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the developer manually initiates server redeployment after each code change, then the application changes are reflected on the server, but the development productivity decreases due to time-consuming redeployment activities

Engineering Contradiction:
Improveapplication change reflectionVSAvoiddevelopment productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by automatically detecting file changes and initiating selective redeployment processes without waiting for manual developer intervention. The redeployment agent continuously monitors the development environment and pre-processes change detection, comparing timestamps and initiating transfers before the developer would manually trigger redeployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The redeployment system serves itself by automatically detecting changes, determining what needs to be redeployed, and executing the redeployment process without human intervention. The agent autonomously monitors file systems, compares timestamps between development and server environments, and initiates selective file transfers based on actual changes detected.

Inventive Principle:
Principle #25Self-service

2Extent of automation

If the system uses timestamp comparison to determine file changes, then change detection is automated, but unnecessary redeployment occurs when timestamps change but file content remains unchanged

Engineering Contradiction:
Improvechange detection automationVSAvoidcomputational resource waste
Core Design Contradiction:
Extent of automationVSLoss of energy

Solution Approach 1:

The system performs partial action by using timestamp comparison as a filtering mechanism rather than an absolute trigger. Timestamp changes initiate a more thorough verification process, where the system selectively redeploys only the specific files that actually changed, rather than redeploying entire applications or all files. This partial approach avoids the excessive action of full redeployment while maintaining automation.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If the developer waits for server compilation and redeployment to complete, then changes are implemented, but the overall development process gets delayed

Engineering Contradiction:
Improvechange implementationVSAvoiddevelopment process time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary change detection and preparation actions continuously in the background. When a file change is detected, the redeployment agent has already prepared the transfer information and can immediately initiate selective redeployment without waiting for manual confirmation or full application context, significantly reducing the time from code change to server implementation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The redeployment process is segmented into independent file-level operations rather than requiring full application redeployment. The system identifies and transfers only the specific modified files individually, allowing parallel processing and reducing overall redeployment time. Each file can be processed independently, eliminating the need to wait for entire application compilation and deployment cycles.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10540163B2System and method for automatic deployment of applications in an integrated development environment
Publication Date: 2020.01.21 WIPRO LTD
  • US10540163B2 patent drawing
  • US10540163B2 patent drawing
  • US10540163B2 patent drawing

AI summary

Disclosed herein is a method and an automatic redeployment agent for automatic redeployment of applications in an integrated Development Environment (IDE). The automatic redeployment agent loads all changes in codebase of the applications onto an application Enterprise Archive (EAR) on the server, by sequentially validating directory paths in the application codebase and the application EAR. The changes in the application codebase are instantly reflected on the server application without restarting or redeploying the server. The automatic redeployment agent helps in reducing the deployment and server restart turnaround time for the IDE by instantly loading the changes to the server. Also, the overall productivity of the IDE is enhanced due to significant reduction in the efforts required for deployment and/or redeployment of the application.