Conditional Deployment of SOA Artifacts via Installation Module

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing SOA deployment mechanisms, including the deployment plan mechanism of AIA, cannot adequately allow for the conditional deployment of artifacts, as they are constrained to deploying or undeploying artifacts based on default logic specified in the deployment plan, without the ability to dynamically modify deployment activities based on user-defined conditions or availability of other artifacts at the time of deployment.

Innovation Solution

The system generates a deployment plan that specifies a list of artifacts and default deployment logic, with an installation module that determines if each artifact is associated with a user-defined condition, evaluating and executing conditional deployment logic if present, allowing for dynamic modification of deployment activities at the time of deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If default deployment logic is used for all artifacts, then deployment process is simple and automated, but flexibility to adapt to different customer site requirements is lost

Engineering Contradiction:

Improveflexibility to adapt to different customer site requirementsVSAvoiddeployment process complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The deployment plan is segmented into artifacts with conditional deployment logic attached to specific artifacts. Each artifact can independently have conditional deployment requirements, allowing flexible adaptation without complicating the entire deployment process. The installation module processes each artifact separately to determine whether conditional logic applies.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The deployment system transitions from static default logic to dynamic conditional logic. The installation module evaluates user-defined conditions at runtime and dynamically determines deployment actions. This allows the deployment process to adapt to different customer site requirements while maintaining automation through the installation module.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If conditional deployment logic is added for each artifact, then deployment flexibility is improved, but deployment processing time and complexity increase

Engineering Contradiction:

Improvedeployment flexibilityVSAvoiddeployment processing time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

Conditional deployment logic is defined and attached to artifacts during the development phase, before deployment occurs. The installation module retrieves the deployment plan and pre-defined conditional logic at deployment time, eliminating the need for real-time decision-making complexity. This preliminary preparation reduces processing time during actual deployment.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The installation module automatically evaluates conditions and executes appropriate deployment logic without manual intervention. The system self-determines which artifacts to deploy based on evaluated conditions, reducing processing time compared to manual conditional deployment decisions while maintaining flexibility.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If deployment activities are dynamically modified at deployment time, then adaptability to customer requirements is improved, but reliability of deployment process decreases

Engineering Contradiction:

Improveadaptability to customer requirementsVSAvoiddeployment process reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The installation module evaluates user-defined conditions and uses the results to determine deployment actions. This feedback mechanism ensures that deployment decisions are based on actual customer site requirements while maintaining a structured, reliable process. The conditional logic provides feedback on whether deployment should proceed, modify, or skip specific artifacts.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS8806475B2Techniques for conditional deployment of application artifacts

Publication Date: 2014.08.12 ORACLE INT CORP

AI summary

Techniques for conditionally deploying artifacts of a software application (e.g., a SOA application). In one set of embodiments, a deployment plan can be generated that specifies a list of artifacts to be deployed for the application. At a time of deployment, the deployment plan can be retrieved and processed by an installation module to carry out the deployment process. As part of this processing, the installation module can determine, for each artifact in the deployment plan, whether the artifact is associated with a user-defined condition. If such an association is found, the installation module can evaluate the user-defined condition and execute conditional deployment logic for the artifact based on the outcome of the evaluation. In this manner, the deployment activities to be carried out for the application can be dynamically modified at the time of deployment.