IMPLEMENTING LOCALE MANAGEMENT ON PAAS: LOCALE REPLACEMENT RISK ANALYSIS

• US 20180053000A1
• Filed: 08/22/2016
• Published: 02/22/2018
• 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
• Granted Patent: US 10,102,376 B2
• Time in Patent Office: Days
• 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.

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

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

4. The apparatus as recited in claim 1 includes a Locale-Object Management Daemon (LOMD), and 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.

5. The apparatus as recited in claim 1 includes moving not ready applications to another node, and deploying the living locale object update in a targeted node.

6. The apparatus as recited in claim 1 includes 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.

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

8. 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.

9. The apparatus as recited in claim 8 wherein the predetermined parameters include at least one of application type, business mode, language, and locale names.

10. 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.

11. The apparatus as recited in claim 10 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.

12. 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; and

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

13. The method as recited in claim 12 includes a General Globalization API List (GGAPIL), and API usages being rated in different risk levels based upon predetermined parameters;

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

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

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

16. The method as recited in claim 15 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.

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

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

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

20. The method as recited in claim 12 includes moving not ready applications to another node, and deploying the living locale object update in a targeted node.