Live Locale Object Update via Daemon Monitoring

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current locale management systems in enterprise computing environments lack efficient methods for live locale object updates, leading to risks of application behavior changes and uncertainty about the impact of locale data changes on running applications, without adequate risk assessment or update status analysis.

Innovation Solution

The implementation of a Locale-Object Management Daemon (LOMD) that checks a predefined update profile, monitors running applications, and decides on locale object updates, allowing for live locale object replacement without system shutdown, by moving not-ready applications to another node if necessary, and enabling real-time locale reloading.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional locale object update method is used, then locale objects can be updated, but system shutdown is required causing application downtime

Engineering Contradiction:

Improveapplication availabilityVSAvoidsystem downtime

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system dynamically manages locale objects by implementing a daemon process that monitors and updates locale objects in real-time without requiring system shutdown. The locale object management daemon (LOMD) dynamically replaces locale objects while applications are running, allowing the system to adapt locale configurations on-the-fly based on application needs and update availability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system performs preliminary actions by pre-loading and caching locale objects before they are needed by applications. The daemon process prepares updated locale objects in advance and maintains a repository of locale data, so when an update is required, the switch can occur without interruption to application execution.

Inventive Principle:

Principle #10Preliminary action

2Loss of time

If living locale-object replacement is implemented, then system uptime is maintained, but risks of application behavior changes increase

Engineering Contradiction:

Improvesystem downtimeVSAvoidapplication behavior consistency

Core Design Contradiction:

Loss of timeVSReliability

Solution Approach 1:

The locale object management daemon implements feedback mechanisms by monitoring application locale object usage and tracking which applications are using which locale objects. This feedback allows the system to make informed decisions about when and how to update locale objects, ensuring that updates only occur when safe and that applications are properly notified of changes.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system provides beforehand cushioning by maintaining a repository of both current and updated locale objects simultaneously. Before performing a living replacement, the system ensures that backup locale objects are available and that applications can be gracefully migrated to new locale objects without abrupt behavior changes or data loss.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

3Adaptability or versatility

If manual locale object update is performed, then update control is maintained, but update efficiency and automation level are low

Engineering Contradiction:

Improveupdate control flexibilityVSAvoidlocale update efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system implements self-service by deploying a locale object management daemon that automatically monitors, manages, and updates locale objects without requiring manual administrator intervention. The daemon autonomously tracks which locale objects are in use, determines when updates are safe to perform, and executes replacements while maintaining proper application notifications and error handling.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The locale object management daemon provides universal functionality by handling multiple locale objects across multiple applications simultaneously. It maintains a comprehensive repository of locale data, supports multiple locale formats and standards, and can manage updates system-wide or for individual applications based on configured policies.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Productivity

If locale objects are updated without monitoring application status, then update speed increases, but risk of inconsistent data output formats increases

Engineering Contradiction:

Improveupdate speedVSAvoiddata output format consistency

Core Design Contradiction:

ProductivityVSManufacturing precision

Solution Approach 1:

The daemon implements real-time feedback monitoring of application locale object usage status. It tracks which applications have loaded which locale objects and maintains this information in a usage table. This feedback mechanism allows the system to verify that locale object updates will not cause inconsistencies before executing the update, ensuring data output format consistency across all applications.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9910666B1Implementing locale management on PaaS: live locale object update

Publication Date: 2018.03.06 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A method and apparatus are provided for implementing system locale management including live locale object update in a computer system. A living locale-object replacement is provided on an operating system without shutdown of the operating system. A Locale-Object Management Daemon (LOMD) checks a predefined living locale object update profile, monitors status of a table of running application and correlated loaded locale-objects and decides if a locale object can be updated in certain nodes for certain applications.