Serviceability and configuration management

• US 8,418,140 B2
• Filed: 05/20/2009
• Issued: 04/09/2013
• Est. Priority Date: 05/20/2009
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Iyer, Jayaram R., Parupudi, Gopal, Qadir, Mahmood G., Karri, Naveen R., Manohar, Anubhuti, Chan, Chi-Kit, Sherwani, Adil A., Tran, Christine H., Fischer, Kevin Joseph, Minick, Jason
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): Bourzik, Brahim
• Application Number:
  US12/468,925
• Publication Number:
  US 20100299653A1
• Time in Patent Office: 1,420 Days
• Field of Search: 717/121
• US Class Current: 717/121
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

Many current computer software platforms support user customization and version upgradability. Unfortunately, upgrading a computer software platform may result in significant loss of user customization data. Additionally, it may be advantageous for users to export and import their customization data to share as customized business solutions with other instances of the computer software platforms. Accordingly, a technique for creating and importing a configuration package and a technique for creating and utilizing an update package is disclosed herein. The configuration package allows configuration data of elements within a computer software platform to be exported and imported. The update package allows elements to be exported within the update package. The update package may be utilized in upgrading, overwriting, and/or creating a new instance of elements. When an existing element is upgraded with an update element within the update package, the existing element'"'"'s original configuration may be retained.

Claims

1. A method for updating an application utilizing an update package while retaining an original target element configuration, comprising:

receiving an update package comprising first update data corresponding to a first element of an application and second update data corresponding to a second element of the application;

receiving a descriptor file associated with the update package, the descriptor file indicating that a first provider is configured to import the first update data and a second provider, different than the first provider, is configured to import the second update data;

invoking the first provider to import the first update data into the application before invoking the second provider to import the second update data based upon a derivative relationship between the first update data and the second update data to maintain element integrity, the invoking the first provider comprising updating an original instance of the first element while retaining an original target element configuration of the first element; and

invoking the second provider to import the second update data into the application, the invoking the second provider comprising;

creating a new instance of the second element while retaining an original instance of the second element; and

executing the application to provide a side-by-side comparison of the original instance of the second element and the new instance of the second element.

2. The method of claim 1, the update package corresponding to a script file.

3. The method of claim 1, the application is related to a hospital.

4. The method of claim 2, comprising:

providing the script file to a provider.

5. The method of claim 1, the executing the application comprising:

responsive to receiving input indicating that the new instance of the second element is to be used, replacing the original instance of the second element with the new instance of the second element.

6. The method of claim 1, the first provider comprising functionality not comprised within the update package.

7. A computer memory which does not include signal or carrier wave, comprising instructions that when executed perform a method for updating an application utilizing an update package while retaining an original target element configuration, comprising:

receiving an update package comprising first update data corresponding to a first element of an application and second update data corresponding to a second element of the application;

receiving a descriptor file associated with the update package, the descriptor file indicating that a first provider is configured to import the first update data and a second provider, different than the first provider, is configured to import the second update data;

invoking the first provider to import the first update data into the application before invoking the second provider to import the second update data based upon a derivative relationship between the first update data and the second update data to maintain element integrity, the invoking the first provider comprising updating an original instance of the first element while retaining an original target element configuration of the first element; and

invoking the second provider to import the second update data into the application, the invoking the second provider comprising;

creating a new instance of the second element while retaining an original instance of the second element; and

executing the application to provide a side-by-side comparison of the original instance of the second element and the new instance of the second element.

8. The computer memory of claim 7, the application is related to a hospital.

9. The computer memory of claim 7, the executing the application comprising:

responsive to receiving input indicating that the new instance of the second element is to be used, replacing the original instance of the second element with the new instance of the second element.

10. The computer memory of claim 9, the replacing comprising:

retaining an original target element configuration of the second element.

11. The computer memory of claim 7, the update package corresponding to a script file.

12. The computer memory of claim 7, the first provider comprising functionality not comprised within the update package.

13. The computer memory of claim 7, the executing the application comprising:

responsive to receiving a first input associated with the original instance of the second element, invoking first computational logic associated with the original instance of the second element; and

responsive to receiving a second input associated with the new instance of the second element, invoking second computational logic associated with the new instance of the second element.

14. The computer memory of claim 7, the method comprising:

retaining an original target element configuration of the second element.

15. The computer memory of claim 11, the method comprising providing the script file to a provider.

16. A system for updating an application utilizing an update package while retaining an original target element configuration, comprising:

one or more processing units; and

memory comprising instructions that when executed by at least some of the one or more processing units, provide for;

an update package utilization component configured to;

receive an update package comprising first update data corresponding to a first element of an application and second update data corresponding to a second element of the application;

receive a descriptor file associated with the update package, the descriptor file indicating that a first provider is configured to import the first update data and a second provider, different than the first provider, is configured to import the second update data;

invoke the first provider to import the first update data into the application before invoking the second provider to import the second update data based upon a derivative relationship between the first update data and the second update data to maintain element integrity;

update an original instance of the first element while retaining an original target element configuration of the first element; and

invoke the second provider to import the second update data into the application, the invoking the second provider comprising;

creating a new instance of the second element while retaining an original instance of the second element; and

executing the application to provide a side-by-side comparison of the original instance of the second element and the new instance of the second element.

17. The system of claim 16, the update package utilization component configured to:

responsive to receiving input indicating that the new instance of the second element is to be used, replace the original instance of the second element with the new instance of the second element.

18. The system of claim 16, the application is related to a hospital.

19. The system of claim 16, the update package corresponding to a script file.

20. The system of claim 19, the update package utilization component configured to:

provide the script file to a provider.