Dynamic Language Resource Import via Inter-Process Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Self-contained applications with multilingual support require redeployment and significant service interruptions to add language extension resources, as they typically do not use outside resources for execution, leading to lengthy service interruptions during the process of uncompressing, modifying, and recompressing large files like WAR files.

Innovation Solution

A system utilizing inter-process communication (IPC) between an application server and a resource server to import language extension resources dynamically, allowing self-contained applications to execute without redeployment by caching these resources in memory, thus avoiding service interruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If language extension resources are added to self-contained applications by uncompressing and modifying WAR files, then multilingual support capability is improved, but service interruption time increases significantly

Engineering Contradiction:
Improvemultilingual support capabilityVSAvoidservice interruption time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent divides the application resources into two separate segments: the core application package (WAR file) and the language extension resources. The language resources are stored externally in a database rather than being embedded within the WAR file. This segmentation allows the application to continue running with the original WAR file while language resources are loaded separately, eliminating the need to uncompress and modify the WAR file during language updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts language extension resources from the self-contained WAR file structure and places them in an external database. This extraction allows the language resources to be updated independently without affecting the core application package. The application server can dynamically load these extracted language resources without requiring service interruption for WAR file modification.

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of manufacture

If language extension resources are embedded inside WAR files during deployment, then self-contained execution is improved, but redeployment complexity increases

Engineering Contradiction:
Improveself-contained execution capabilityVSAvoidredeployment complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent introduces a resource manager and database as an intermediary layer between the WAR file and language resources. Instead of directly embedding language resources in the WAR file, the system uses a resource manager that communicates with an external database to provide language resources to the application. This intermediary approach maintains the self-contained nature of the WAR file while simplifying the deployment process, as language resources can be added or updated in the database without requiring WAR file redeployment.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If WAR files are uncompressed and recompressing for language updates, then language extension integration is improved, but processing time increases

Engineering Contradiction:
Improvelanguage extension integrationVSAvoiddeployment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent performs preliminary organization of language resources into a separate database structure during the initial deployment phase. The resource manager is pre-configured to access this external database. When language updates are needed, only the database records need to be modified, not the entire WAR file. This preliminary setup eliminates the need for time-consuming uncompression and recompression operations during subsequent language updates, significantly improving deployment efficiency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8375379B2Importing language extension resources to support application execution
Publication Date: 2013.02.12 SAP FRANCE
  • US8375379B2 patent drawing
  • US8375379B2 patent drawing
  • US8375379B2 patent drawing

AI summary

A computer readable storage medium includes executable instructions to provide a registration service that is configured to accept a registration, where the registration includes a first address and a description of available language extension resources of a resource provider. The computer readable storage medium further includes executable instructions to import, based on the registration, the available language extension resources from the resource provider to support execution based on the available language extension resources. The executable instructions to import use inter-process communication.