Adaptation Interface for Virtual Machine Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing JAVA virtual machines lack the ability to access proprietary or specialty enhancements due to the fixed nature of the JAVA Native Interface (JNI), which restricts integration with different versions of virtual machines and limits the use of platform-dependent features.

Innovation Solution

A system and method that utilizes an adaptation interface within an Application Server instance to load both standard and extended features of virtual machines, allowing native platform entities to access standard features through a standardized native interface and extended features through an adaptation interface, enabling the mapping of requests to alternative features if the requested feature is not supported.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a fixed standardized native interface (JNI) is used to ensure interface stability and compatibility, then reliability is improved, but adaptability deteriorates because proprietary or specialty enhancements of a proprietary JVM cannot be accessed

Engineering Contradiction:

Improveinterface stabilityVSAvoidaccess to proprietary enhancements

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The interface is segmented into two distinct layers: a standardized native interface (JNI) for accessing standard JVM features, and a proprietary native interface for accessing extended proprietary features. This segmentation allows each interface to serve its specific purpose without compromising the other, resolving the contradiction between stability and adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A wrapper class acts as an intermediary layer between the standardized native interface and the proprietary native interface. The wrapper class receives requests from the standardized interface and translates or forwards them to the appropriate proprietary interface, enabling access to enhanced features while maintaining compatibility with the standard interface.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If the standardized native interface is kept fixed to maintain compatibility, then ease of operation is improved, but device complexity increases because additional proprietary interfaces and wrapper classes are required

Engineering Contradiction:

Improveinterface compatibilityVSAvoidinterface structure

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The proprietary interface functionality is extracted into a separate wrapper class that sits alongside the standardized interface. This extraction allows the core standardized interface to remain simple and unchanged, while the additional complexity of proprietary features is isolated in the wrapper class, minimizing the impact on overall system complexity.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS7562349B2Version adaptation interface for integration of different virtual machines

Publication Date: 2009.07.14 SAP SE

AI summary

A system and method for integrating different virtual machines (“VMs”). A first VM is loaded into an Application Server (“AS”) instance. The first VM includes standard features accessible through a standard native interface. A second VM is loaded into the AS instance including the standard features and extended features. The standard features provided by the second VM are accessed by native platform entities through a standardized native interface. The extended features provided by the second VM are accessed by the native platform entities through an adaptation interface.