Segmented Deployment Descriptors for Service Extension Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing deployment descriptors in enterprise application software lack the ability to configure application settings that extend beyond the standard specification, leading to interoperability issues when integrating software with and without service extensions.

Innovation Solution

Incorporating additional deployment descriptors that conform to non-standard document type definitions, allowing configuration information for service extensions, enabling the deployment tool to adapt to environments with or without these extensions by including or excluding specific information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If deployment descriptors conform strictly to standard specification, then interoperability with standard-compliant systems is ensured, but ability to configure service extensions is lost

Engineering Contradiction:

ImproveinteroperabilityVSAvoidservice extension configuration

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The deployment descriptor is segmented into two distinct parts: a standard-compliant portion that ensures interoperability with standard systems, and an extension portion that enables configuration of service extensions. This segmentation allows each part to serve its specific purpose without compromising the other.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Extension-specific configuration information is extracted from the standard deployment descriptor structure and placed into a separate extension deployment descriptor. This extraction allows the standard descriptor to maintain strict compliance while the extension descriptor provides additional functionality.

Inventive Principle:

Principle #2Taking out (Extraction)

2Adaptability or versatility

If deployment descriptors include extension-specific configuration information, then service extension functionality is enabled, but interoperability with standard-compliant systems deteriorates

Engineering Contradiction:

Improveservice extension configurationVSAvoidinteroperability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

Different portions of the deployment descriptor have different qualities: the standard portion maintains strict conformity for interoperability, while the extension portion incorporates non-standard elements for enhanced functionality. Each portion is optimized for its specific purpose.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The extension deployment descriptor acts as an intermediary that bridges standard-compliant systems and service extensions. It contains configuration information that mediates between the standard environment and extension-specific requirements.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Device complexity

If a single standard-compliant deployment descriptor is used, then simplicity is maintained, but configuration capability for extended services is insufficient

Engineering Contradiction:

Improvedescriptor structureVSAvoidconfiguration capability

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The standard deployment descriptor and extension deployment descriptor are merged into a unified deployment package. The deploy tool combines both descriptors, allowing the application to benefit from both standard compliance and extension functionality without manual intervention.

Inventive Principle:

Principle #5Merging (Combining)

4Adaptability or versatility

If deployment tool handles both standard and extension descriptors, then full functionality is achieved, but processing complexity increases

Engineering Contradiction:

Improvefull functionalityVSAvoidprocessing complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The deploy tool performs preliminary actions by automatically detecting the presence of extension deployment descriptors and preparing the appropriate processing logic before deployment. This preliminary detection and preparation simplifies the actual deployment process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The deploy tool dynamically adjusts its processing based on the content of the deployment descriptors. If extension descriptors are present, the tool activates extension-handling logic; otherwise, it processes only standard descriptors. This dynamic adaptation optimizes processing efficiency.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS9626173B1Non specification supported application deployment descriptors and web application deployment descriptors

Publication Date: 2017.04.18 SAP SE

AI summary

A method is described that inserts first and second deployment descriptors into an application archive file. The first deployment descriptor conforms to a first document type definition that is defined by a standard specification. The second deployment descriptor conforms to a second document type definition that is not defined by the standard specification. The second deployment descriptor has an element that is directed to a service that is an extension to the services offered by an environment described by the standard specification. The first and second deployment descriptors provide configuration information selected from the group consisting of: a) configuration information that pertains to the application as a whole; and, b) configuration information that pertains to a web application portion of the application.