Mobile client synchronization and upgrading

• US 20060224622A1
• Filed: 03/31/2005
• Published: 10/05/2006
• Est. Priority Date: 03/31/2005
• Status: Abandoned Application

• Current Assignee: EPiphany Incorporated (Infor Incorporated)
• Original Assignee: EPiphany Incorporated (Infor Incorporated)
• Inventors: Velega, Raghuram
• Application Number:
  US11/096,760
• Publication Number:
  US 20060224622A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Upgrading a mobile client is described, including exporting a deployment unit, the deployment unit including an item, an action, and a target, and logic configured to perform the action on the item at the target, importing the deployment unit from a file system to a master, applying the action on the item at the target on the master, and committing the deployment unit from the master to the mobile client, wherein the deployment unit executes logic configured to apply the action on the item at the target on the mobile client.

Claims

1. A method for upgrading a mobile client, comprising:

exporting a deployment unit, the deployment unit including an item, an action, and a target, and logic configured to perform the action on the item at the target;

importing the deployment unit from a file system to a master;

applying the action on the item at the target on the master; and

committing the deployment unit from the master to the mobile client, wherein the deployment unit executes logic configured to apply the action on the item at the target on the mobile client.

2. The method recited in claim 1, wherein the deployment unit is a file.

3. The method recited in claim 1, wherein the deployment unit is a jar file.

4. The method recited in claim 1, wherein the deployment unit includes a file configuration change.

5. The method recited in claim 1, wherein the logic, when executed, determines how the action is applied on the item at the target.

6. The method recited in claim 1, wherein the deployment unit includes operational data.

7. The method recited in claim 1, wherein the deployment unit includes metadata.

8. The method recited in claim 1, wherein exporting the deployment unit further comprises packaging the deployment unit in a jar file.

9. The method recited in claim 1, wherein committing the deployment unit from the master to the mobile client further comprises sending the deployment unit as an attachment to a message.

10. The method recited in claim 1, wherein committing the deployment unit from the master to the mobile client further comprises sending the deployment unit as an attachment to a data transport message, wherein the attachment is encapsulated using a data transport protocol.

11. A system for upgrading a mobile client, comprising:

a memory for storing data;

a processor configured to create a deployment unit, the deployment unit including an item, an action, and a target, and logic configured to perform the action on the item at the target, the processor being further configured to export the deployment unit to a file system, to import the deployment unit from the file system to a master, to apply the action on the item at the target on the master, and to commit the deployment unit from the master to the mobile client, wherein the deployment unit executes logic configured to apply the action on the item at the target on the mobile client.

12. The system recited in claim 11, wherein the deployment unit is a file.

13. The system recited in claim 11, wherein the deployment unit has a file format of jar.

14. The system recited in claim 11, wherein the logic, when executed, determines how the action is applied on the item at the target on the master or the mobile client.

15. The system recited in claim 11, wherein the deployment unit includes operational data.

16. The system recited in claim 11, wherein the deployment unit includes metadata.

17. The system recited in claim 11, further comprising a packaging module configured to package the deployment unit in a jar file.

18. The system recited in claim 11, wherein the processor being further configured to commit the deployment unit from the master to the mobile client further comprises sending the deployment unit as an attachment to a message.

19. The system recited in claim 11, wherein the processor being further configured to commit the deployment unit from the master to the mobile client further comprises sending the deployment unit as an attachment to a data transport message, wherein the attachment is encapsulated using a data transport protocol.

20. A computer program product for upgrading a mobile client, the computer program product being embodied in a computer readable medium and comprising computer instructions for:

exporting a deployment unit, the deployment unit including an item, an action, and a target, and logic configured to perform the action on the item at the target;

importing the deployment unit from a file system to a master;

applying the action on the item at the target on the master; and

committing the deployment unit from the master to the mobile client, wherein the deployment unit executes logic configured to apply the action on the item at the target on the mobile client.