Implementing locale management on PaaS: locale replacement risk analysis

• US 10,303,882 B2
• Filed: 07/10/2018
• Issued: 05/28/2019
• Est. Priority Date: 08/22/2016
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Anglin, Debbie A., Aslot, Vishal C., Gu, Yu, Liu, Su
• Primary Examiner(s): Song, Hosuk
• Application Number:
  US16/031,946
• Publication Number:
  US 20180322290A1
• Time in Patent Office: 322 Days
• Field of Search: 726 22- 25
• CPC Class Codes: G06F 16/337 Profile generation, learning or modification
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/454 Multi-language systems; Localisation; Internationalisation
• CPC Class Codes: H04L 63/1433 Vulnerability analysis

Abstract

A method and apparatus are provided for implementing system locale management including locale replacement risk analysis in a computer system. A Locale Update Risk Analysis Agent (RAA) scans globalization API usages on each pair of locale and running application. The scanned API list of each running application is compared with predefined API locale sensitive weights, and a locale replacement risk index is calculated on each application under a certain locale. A living locale-object update decision is made based on the calculated locale replacement risk indexes.

Claims

1. An apparatus for implementing system locale management including locale replacement risk analysis in a computer system comprising:

a processor,

a Locale Update Risk Analysis Agent (RAA) tangibly embodied in a non-transitory machine readable medium used to implement locale replacement risk analysis;

said processor using said Locale Update Risk Analysis Agent (RAA), scanning globalization API usages on each pair of locale and running applications;

comparing the scanned API list with predefined API locale sensitive weights, and calculating a locale replacement risk index on each application under a certain locale and making a living locale-object update decision based on the calculated locale replacement risk indexes;

identifying running applications not ready for the living locale-object update decision, moving the identified not ready running applications to another node;

deploying a living local object update session in a targeted node, and applying an original locale object file set.

2. The apparatus as recited in claim 1 includes a Locale Replacement Risk Examiner (LRRE), and evaluating locale-object replacement risks on a certain pair of application and locale.

3. The apparatus as recited in claim 2 includes a Locale-Object Management Daemon (LOMD) receiving an output of the Locale Replacement Risk Examiner (LRRE) used to make the living locale-object update decision.

4. The apparatus as recited in claim 1 includes a Living Locale-Object Update Profile (LLOU), said processor using said Living Locale-Object Update Profile (LLOU), saving and updating the calculated locale replacement risk index into one or more living locale-object update profiles.

5. The apparatus as recited in claim 1 includes a Running Application Status File (RASF), said processor using said Running Application Status File (RASF), saving and updating the calculated locale replacement risk index into the running application status file.

6. The apparatus as recited in claim 1 includes a Locale-Object Management Daemon (LOMD), said processor using said Locale-Object Management Daemon (LOMD) invoking the locale object management daemon to make the living locale-object update decision based on the locale replacement risk indexes stored in a living locale-object update profile.

7. The apparatus as recited in claim 1 includes said processor using said updating and saving application status into one or more living locale-object update profiles, and sharing living locale-object update profiles with other nodes as crowdsourcing contribution to other users.

8. The apparatus as recited in claim 1 includes a Table of Running Applications and Correlated Loaded Locale-Objects (TRACLLO), said processor using said Table of Running Applications and Correlated Loaded Locale-Objects (TRACLLO) storing running application status information under certain locales into the Table of Running Applications and Correlated Loaded Locale-Objects (TRACLLO).

9. The apparatus as recited in claim 1 includes a General Globalization API List (GGAPIL), and each API being rated in different risk levels based upon predetermined parameters, said predetermined parameters include at least one of application type, business mode, language, and locale names.

10. A computer-implemented method for implementing system locale management including locale replacement risk analysis in a computer system including a processor, and a Locale Update Risk Analysis Agent (RAA) tangibly embodied in a non-transitory machine readable medium used to implement locale replacement risk analysis, said computer-implemented method comprising:

scanning globalization API usages on each pair of locale and running applications; and

,

comparing the scanned API list with predefined API locale sensitive weights, and calculating a locale replacement risk index on each application under a certain locale;

making a living locale-object update decision based on the calculated locale replacement risk indexes;

identifying running applications not ready for the living locale-object update decision, moving the identified not ready running applications to another node;

deploying a living local object update session in a targeted node, and applying an original locale object file set.

11. The method as recited in claim 10 includes rating API usages being rated in different risk levels based upon predetermined parameters using a General Globalization API List (GGAPIL);

said predetermined parameters including at least one of application type, business mode, language, and locale names.

12. The method as recited in claim 10 includes evaluating locale-object replacement risks on a certain pair of application and locale using a Locale Replacement Risk Examiner (LRRE).

13. The method as recited in claim 12 includes making the living locale-object update decision based on the locale replacement risk indexes stored in a living locale-object update profile using a Locale-Object Management Daemon (LOMD).

14. The method as recited in claim 13 wherein the Locale-Object Management Daemon (LOMD) receives an output of the Locale Replacement Risk Examiner (LRRE) used to make the living locale-object update decision.

15. The method as recited in claim 10 includes saving and updating the calculated locale replacement risk index into one or more living locale-object update profiles using a Living Locale-Object Update Profile (LLOU).

16. The method as recited in claim 10 includes saving and updating the calculated locale replacement risk index into the running application status file using a Running Application Status File (RASF).

17. The method as recited in claim 10 includes storing running application status information under certain locales using a Table of Running Applications and Correlated Loaded Locale-Objects (TRACLLO).