Applying hot fixes for metadata customizing user interactions based on a software program deployed in multiple versions

• US 9,052,978 B2
• Filed: 07/24/2013
• Issued: 06/09/2015
• Est. Priority Date: 07/24/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Appadurai, Easwaran
• Primary Examiner(s): Rampuria, Satish
• Application Number:
  US13/949,256
• Publication Number:
  US 20150033216A1
• Time in Patent Office: 685 Days
• Field of Search: 717138-178
• US Class Current: 1/1
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

An aspect of the present disclosure provides for applying hot fixes to metadata customizing user interactions based on a software program. In an embodiment, a hot fix containing new files is received. Each new file contains a corresponding modified metadata. The user is presented for selection, differences between each new file and a corresponding existing file. Only the selected differences are then used to form patched files, which thereafter control the user interactions, for example, by replacing the corresponding existing file with the patched file. Accordingly the user is provided enhanced control over which of the differences is applied to the metadata.

Claims

1. A method of providing user interactions based on a software program, said method being performed at least in part in a digital processing system, comprising:

executing said software program to provide said user interactions, wherein said user interactions are in the form of process flows, wherein said process flows specify receiving inputs from a program user and providing corresponding outputs, wherein said user interactions constituting said process flows are operative according to an original metadata stored in the form of a plurality of existing files;

receiving a hot fix containing a plurality of new files, each new file containing a corresponding modified metadata;

identifying a set of existing files of said plurality of existing files, wherein each of said set of existing files corresponds to a new file of said plurality of new files;

retrieving each of said set of existing files from a secondary storage;

presenting to an administrator on a display unit, differences between each of said set of existing files and said corresponding new files, wherein said differences correspond to differences between original metadata in said existing files and modified metadata in the corresponding new files;

getting inputs from said administrator indicating a selected set of differences of the presented differences, wherein said inputs are provided by said administrator by selecting said selected set of differences from said differences displayed on said display unit;

forming a set of patched files, each patched file being formed by incorporating the selected differences in a corresponding existing file of said set of existing files,

wherein said identifying, said retrieving, said presenting, said getting and said forming are performed for each of said plurality of new files in response to said receiving; and

controlling, after said forming, said user interactions based on said set of patched files instead of said set of existing files.

2. The method of claim 1, wherein said presenting displays a first difference and a second difference between a first new file of said plurality of new files and a first existing file of said set of existing files,

wherein said inputs from said administrator indicate only said first difference, but not said second difference, in said selected set of differences,

wherein said forming forms a first patched file of said set of patched files by incorporating said first difference, but not said second difference, in said first existing file,

wherein said controlling controls said user interactions based on said first patch file containing said first difference, but not said second difference.

3. The method of claim 2, wherein said controlling comprises replacing each of said identified existing files with a corresponding patched file of said plurality of patched files in said secondary storage,

wherein said replacing replaces said first existing file with said first patched file.

4. The method of claim 3, further comprising:

maintaining identification data indicating the identifiers of each of said plurality of existing files, wherein each of said plurality of new files is also identified by a corresponding identifier,

wherein said identifying identifies said set of existing files as having identifiers matching the identifiers of said plurality of new files in said identification data.

5. The method of claim 4, wherein said software program is executing on a first system external to said digital processing system, wherein said first system contains said secondary storage,

wherein said retrieving retrieves said set of existing files from said first system,

wherein said replacing replaces said set of existing files with said set of patched files in said first system.

6. The method of claim 1, wherein said software program is available in a set of versions, wherein multiple instances of said software program are executing on a plurality of systems external to said digital processing system,

wherein a first system executing a first version is operable based on a first file storing corresponding portion of metadata, said first file being identified by a first identifier,

wherein a second system executing a second version does not contain any files with said first identifier in the corresponding plurality of existing files,

wherein, in response to said hot fix containing a new file having said first identifier, all of said identifying, said retrieving, said presenting, said getting and said forming are performed when said hot fix is applied to said first system based on matching of said first identifier, and not performed when said hot fix is applied to said second system.

7. The method of claim 6, each of said first system and said second system corresponds to a POS (point of sale) terminal of a plurality of POS terminals in a retail store, wherein said software program corresponds to a client application executing in said plurality of POS terminals, wherein said first file stores said corresponding portions of metadata according to XML (extensible markup language).

8. A non-transitory machine readable medium storing one or more sequences of instructions for enabling a system to apply hot fixes to software programs, wherein execution of said one or more instructions by one or more processors contained in said system enables said system to perform the actions of:

receiving a hot fix containing a plurality of new files, each new file containing a modified metadata corresponding to an original metadata, said original metadata being stored in the form of a plurality of existing files,

wherein upon execution, a software program provides user interactions customized based on said original metadata;

identifying a set of existing files of said plurality of existing files, wherein each of said set of existing files corresponds to a new file of said plurality of new files;

retrieving each of said set of existing files from a secondary storage;

presenting to an administrator on a display unit, differences between each of said set of existing files and said corresponding new files, wherein said differences correspond to differences between original metadata of said existing files and modified metadata of the corresponding new files, wherein said presenting displays a first difference and a second difference between a first new file of said plurality of new files and a first existing file of said set of existing files;

getting inputs from said administrator indicating a selected set of differences of the presented differences, wherein said inputs are provided by said administrator by selecting said selected set of differences from said differences displayed on said display unit, wherein said inputs from said administrator indicate only said first difference, but not said second difference, in said selected set of differences; and

forming a set of patched files, each patched file being formed by incorporating the selected differences in a corresponding existing file of said set of existing files, wherein said forming forms a first patched file of said set of patched files by incorporating said first difference, but not said second difference, in said first existing file,

wherein said identifying, said retrieving, said presenting, said getting and said forming are performed for each of said plurality of new files in response to said receiving,

wherein after said forming, said user interactions of said software program are controlled based on said first patch file containing said first difference, but not said second difference, instead of said set of existing files.

9. The machine readable medium of claim 8, further comprising one or more instructions for:

replacing each of said identified existing files with a corresponding patched file of said plurality of patched files in said secondary storage,

wherein said replacing replaces said first existing file with said first patched file.

10. The machine readable medium of claim 9, further comprising one or more instructions for:

maintaining identification data indicating the identifiers of each of said plurality of existing files, wherein each of said plurality of new files is also identified by a corresponding identifier,

wherein said identifying identifies said set of existing files as having identifiers matching the identifiers of said plurality of new files in said identification data.

11. The machine readable medium of claim 10, wherein said software program is executing on a first system external to said digital processing system, wherein said first system contains said secondary storage,

wherein said retrieving retrieves said set of existing files from said first system,

wherein said replacing replaces said set of existing files with said set of patched files in said first system.

12. The machine readable medium of claim 8, wherein said software program is available in a set of versions, wherein multiple instances of said software program are executing on a plurality of systems external to said digital processing system,

wherein a first system executing a first version is operable based on a first file storing corresponding portion of metadata, said first file being identified by a first identifier,

wherein a second system executing a second version does not contain any files with said first identifier in the corresponding plurality of existing files,

wherein, in response to said hot fix containing a new file having said first identifier, all of said identifying, said retrieving, said presenting, said getting and said forming are performed when said hot fix is applied to said first system based on matching of said first identifier, and not performed when said hot fix is applied to said second system.

13. The machine readable medium of claim 12, each of said first system and said second system corresponds to a POS (point of sale) terminal of a plurality of POS terminals in a retail store, wherein said software program corresponds to a client application executing in said plurality of POS terminals, wherein said first file stores said corresponding portions of metadata according to XML (extensible markup language).

14. The machine readable medium of claim 8, wherein said user interactions are in the form of process flows, wherein said process flows specify receiving inputs from a program user and providing corresponding outputs, wherein said user interactions constituting said process flows are operative according to said original metadata stored in the form of said plurality of existing files.

15. A computing system comprising:

a plurality of systems to execute multiple instances of a software program, wherein each of said plurality of systems contains (a) a corresponding memory to store instructions, and (b) a corresponding processor to retrieve said instructions from said memory and execute the retrieved instructions, wherein execution of said retrieved instructions causes said system to provide an instance of said multiple instances of said software program, and wherein said software program upon execution provides user interactions, wherein said user interactions are in the form of process flows, wherein said process flows specify receiving inputs from a program user and providing corresponding outputs, wherein said user interactions constituting said process flows are operative according to an original metadata stored in the form of a plurality of existing files; and

a patch tool operable to;

receive a hot fix containing a plurality of new files, each new file containing a corresponding modified metadata;

identify a set of existing files of said plurality of existing files, wherein each of said set of existing files corresponds to a new file of said plurality of new files;

retrieve each of said set of existing files from a first system of said plurality of systems;

present to an administrator on a display unit, differences between each of said set of existing files and said corresponding new files wherein said differences correspond to differences between original metadata in said existing files and modified metadata in the corresponding new files;

get inputs from said administrator indicating a selected set of differences of the presented differences, wherein said inputs are provided by said administrator by selecting said selected set of differences from said differences displayed on said display unit;

form a set of patched files, each patched file being formed by incorporating the selected differences in a corresponding existing file of said set of existing files,

wherein said patch tool performs said identify, said retrieve, said present, said get and said form for each of said plurality of new files in response to receiving said hot fix,

after said forming, wherein said user interactions of said software program executing on said first system are controlled based on said set of patched files instead of said set of existing files.

16. The computing system of claim 15, wherein to said present, said patch tool displays a first difference and a second difference between a first new file of said plurality of new files and a first existing file of said set of existing files,

wherein said inputs from said administrator indicate only said first difference, but not said second difference, in said selected set of differences,

wherein said patch tool forms a first patched file of said set of patched files by incorporating said first difference, but not said second difference, in said first existing file,

wherein said user interactions of said software program executing on said first system are based on said first patch file containing said first difference, but not said second difference.

17. The computing system of claim 16, wherein said patch tool is further operable to:

replace each of said identified existing files with a corresponding patched file of said plurality of patched files in said first system,

wherein said patch tool replaces said first existing file with said first patched file.

18. The computing system of claim 17, wherein said patch tool is further operable to:

maintain identification data indicating the identifiers of each of said plurality of existing files, wherein each of said plurality of new files is also identified by a corresponding identifier,

wherein said patch tool identifies said set of existing files as having identifiers matching the identifiers of said plurality of new files in said identification data.

19. The computing system of claim 15, wherein said software program is available in a set of versions,

wherein said first system executing a first version is operable based on a first file storing corresponding portion of metadata, said first file being identified by a first identifier,

wherein a second system of said plurality of systems executing a second version does not contain any files with said first identifier in the corresponding plurality of existing files,

wherein, in response to said hot fix containing a new file having said first identifier, said patch tool performs said identify, said retrieve, said present, said get and said form when said hot fix is applied to said first system based on matching of said first identifier, and not performed when said hot fix is applied to said second system.

20. The computing system of claim 19, wherein said patch tool is further operable to:

receive a request to distribute said hot fix to a set of systems of said plurality of systems; and

in response to said request, replace said set of existing files in each of said plurality of systems with said set of patched files,

wherein said user interactions of said software program executing on said set of systems are controlled based on said set of patched files instead of said set of existing files after said replacement.