Dynamic Runtime Platform Provisioning via Composite Packaging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The provisioning process for runtime components in cloud computing is cumbersome and prone to errors, requiring extensive administrative tasks and resource wastage due to the lack of predictability in successful installation, necessitating offline testing for compatibility between customer applications and the cloud environment.

Innovation Solution

A dynamic updating process that generates and publishes composite product installations, utilizing the Eclipse p2 provisioning platform to package and install runtime platforms as standalone base products, ensuring compatibility through metadata validation without additional testing, thus avoiding resource wastage and simplifying the installation process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If runtime components are provisioned to cloud system environment, then customer application can execute on cloud platform, but provisioning process becomes cumbersome and prone to errors requiring extensive administrative tasks

Engineering Contradiction:
Improveprovisioning processVSAvoidadministrative tasks
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent combines the customer application and required runtime components into a single composite installable unit. This merging eliminates the need for separate provisioning of runtime components, reducing administrative tasks and simplifying the deployment process while ensuring compatibility between the application and its runtime environment.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs preliminary packaging of runtime components with the customer application during the composite unit creation phase. By pre-configuring and validating the runtime environment before deployment, the system avoids complex administrative tasks during actual provisioning and ensures immediate executability upon installation.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If runtime components are selected and provisioned, then application can run efficiently, but resources are wasted when installation fails in later stages

Engineering Contradiction:
Improveapplication execution efficiencyVSAvoidresource wastage
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent performs preliminary validation of compatibility between customer applications and runtime components during the composite unit packaging phase. By validating dependencies and compatibility before deployment, the system prevents installation failures and resource wastage while ensuring efficient application execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a validation mechanism that provides feedback on compatibility between applications and runtime components before actual installation. This feedback loop allows the system to identify and resolve potential conflicts beforehand, preventing resource wastage from failed installations.

Inventive Principle:
Principle #23Feedback

3Reliability

If components are updated offline before installation, then compatibility can be guaranteed, but installation process becomes time-consuming and rigid

Engineering Contradiction:
Improvecompatibility guaranteeVSAvoidinstallation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs compatibility validation and component configuration in advance during the composite unit packaging phase. By completing all necessary compatibility checks and configurations beforehand, the system guarantees reliability while enabling rapid one-step installation without time-consuming updates during deployment.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If extensive testing is performed offline, then operability can be guaranteed, but provisioning process becomes cumbersome and complex

Engineering Contradiction:
Improveoperability guaranteeVSAvoidprovisioning process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the application and runtime components into a single composite installable unit with embedded validation. This integration ensures operability through built-in compatibility checks while simplifying the provisioning process to a single installation step, eliminating complex separate testing procedures.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8850420B2Dynamically updating on-demand runtime platforms executing business applications
Publication Date: 2014.09.30 SAP SE
  • US8850420B2 patent drawing
  • US8850420B2 patent drawing
  • US8850420B2 patent drawing

AI summary

In one aspect, a business application is provided by a customer for execution in a cloud environment. A runtime platform for the business application is identified based on the functionality of the business application. In another aspect, an installable package for a product composing the business application and a first version of the runtime platform is generated. In yet another aspect, the business application and a second version of the runtime platform are synchronously installed in a cloud environment based on the installable package of the product, where the metadata of the business application and the metadata of the business application are dynamically validated prior the installation to guarantee compatibility.