Method, apparatus, system, and program product for attaching files and other objects to a partially replicated database

• US 20040162853A1
• Filed: 10/29/2003
• Published: 08/19/2004
• Est. Priority Date: 03/03/1998
• Status: Active Grant

• Current Assignee: Jeffrey I. Cohen, Peter Siam Iii Sy Lim, Prashant Chatterjee, Robert A. Brodersen
• Original Assignee: Jeffrey I. Cohen, Peter Siam Iii Sy Lim, Prashant Chatterjee, Robert A. Brodersen
• Inventors: Brodersen, Robert A., Chatterjee, Prashant, Cohen, Jeffrey I., Sy Lim, Peter Siam III
• Granted Patent: US 7,539,704 B2
• Time in Patent Office: Days
• US Class Current: 707/104.1
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

Attaching files and other objects in a distributed computing environment. This includes adding file attachments and non-database objects, such as, text file data, web file data, image file data, and other file attachment objects to databases. These objects may be retrieved at the convenience of a node to which the objects are sent. Visibility rules can be set to determine which attachments and objects are seen by a node. Distribution rules for an object determine whether a node must request the object or whether the node is forced to receive the object.

Claims

1. A method of managing a database comprising:

a. adding a file attachment to a database, and

a. enabling a user to attach the file attachment to a business object.

2. The method of claim 1 wherein the file attachment comprises one or more of the group consisting of a text data file attachment, an image data file attachment, and a web based data file attachment.

3. The method of claim 1 further comprising automatically replicating the file attachment to all docking clients that have visibility to the business object.

4. The method of claim 3 further comprising enabling users to

a. update the file attachment on any database server or mobile server, and

b. synchronize the file attachment among all databases.

14. The method of claim 1 further comprising allowing a user to attach non-database objects, to any business object chosen by a developer or configurator, wherein the non-database objects comprise one or more of the group consisting of files and file attachments.

15. The method of claim 1 further comprising allowing users to create multiple versions of a file.

16. The method of claim 1 further comprising allowing users to configure file attachments on the business object.

17. The method of claim 16 wherein the business object comprises at least one of the group consisting of a service request, an opportunity, a quote, and an agreement.

23. The method of claim 1 further comprising providing remote support.

24. The method of claim 23 wherein the support comprises distributing at least one of the group consisting of literature templates and correspondence templates.

25. The method of claim 24 further comprising:

a. allowing mobile users to request literature,

b. downloading the requested literature in a next docking session, and

c. distributing at least one of the group consisting of published literature and correspondence templates.

26. The method of claim 3 further comprising replicating file table rows and the associated file attachments or non-database file objects to the docking clients that have visibility to the business object.

27. The method of claim 26 further comprising writing information about the associated file attachments or non-database file objects to a file.

28. The method of claim 26 further comprising sending and retrieving the associated file attachments or non-database file objects for the file table rows.

29. The method of claim 26 further comprising:

a. applying the file table rows to a database or file, and

b. copying the database or file to a local file system.

30. The method of claim 26 further comprising replicating all associated files to regional databases.

31. The method of managing a database of claim 1 wherein:

a. the database contains at least one database table,

b. the database table contains rows and columns,

c. a row corresponds to a database object, and

d. a column corresponds to an attribute of the object.

32. The method of managing a database of claim 31 wherein the attribute refers to a non-database object file or a file attachment.

33. The method of claim 1 further comprising enabling the user to perform at least one of the functions consisting of creating, updating, and deleting the file attachment.

34. The method of claim 3 further comprising automatically replicating the file attachment to docking clients.

35. The method of claim 1 further comprising enabling an administrator to register the file attachment.

41. The method of claim 1 further comprising enabling attachment of a local html file.

42. The method of claim 41 wherein the html file comprises one or more other files.

43. The method of claim 1 further comprising

a. updating files in any location, and

b. replicating the updated files to all docking clients that have visibility to the file.

44. The method of claim 43 further comprising the user updating files while connected to a server database or a mobile client.

45. The method of claim 44 further comprising:

a. resolving uniqueness,

b. updating conflicts among the files, and

c. consistency checking across databases while docked.

46. The method of claim 43 further comprising routing files to docking clients using visibility rules.

47. The method of claim 1 wherein the database contains files and users further comprising:

a. applying a robust set of visibility rules to the files and users, and

b. determining which files are transferred to which users using the visibility rules.

48. The method of claim 47 wherein the visibility rules specify all files of one or more of the group consisting of a certain type of file, a set of user selected files, and a set of files attached to a visible object.

49. The method of claim 48 wherein the set of files attached to a visible object comprises one or more of the group consisting of attachments to quotes, agreements, and service requests.

50. The method of claim 43 further comprising replicating files with associated database transactions to guarantee transaction integrity on the docking clients.

54. The method of claim 1 further comprising enabling a user to use a consistent user interface to create, update and delete files, wherein the consistent user interface is a file attachment applet.

55. The method of claim 54 further comprising enabling a developer or a configurator to add the file attachment applet to any existing object.

56. The method of claim 54 further comprising enabling a developer or a configurator to enhance or override the behavior of the file attachment.

60. The method of claim 54 further comprising creating a file table for each file attachment applet.

66. The method of claim 54 further comprising:

a. enabling user access of a file attachment,

b. uncompressing and copying the file attachment from a file system to a temporary directory upon user access of the file, and

c. invoking an appropriate program to display and edit the file upon user access of the file.

67. The method of claim 54 further comprising:

a. enabling user modification of a file,

b. updating file information in a file table upon user modification of the file, and

c. copying the modified file from a temporary directory to a file system upon user modification of the file.

72. The method of claim 1 further comprising a headquarters database, wherein the headquarters database comprises one or more of the group consisting of a master database and a collection of databases.

73. The method of claim 72 wherein the master database is a hierarchical collection of databases.

74. The method of claim 73 further comprising enabling a node or client to have full or partial replicas of any of the databases.

75. The method of claim 72 further comprising enabling a user to modify any of the databases.

76. The method of claim 75 further comprising enabling the user to modify objects within any of the databases, attributes of these objects, and values of these attributes.

77. The method of claim 72 further comprising synchronizing databases at least one client, comprising:

propagating effects of a transaction from the headquarters database to the client.

78. The method of claim 77 further comprising merging the transaction, comprising:

applying routed transaction information from the headquarters database to the client.

79. The method of claim 78 further comprising obtaining consistency of one or more of the group consisting of database states, database objects, object attributes, and attribute values.

80. The method of claim 78 further comprising applying conflict resolution rules to the transactions.

81. The method of claim 77 further comprising applying routing rules based upon attributes to be modified to determine if a node should receive the propagation.

82. The method of claim 1 wherein the database has references to objects not in the database.

83. The method of claim 82 comprising upgrading objects using special procedures.

84. The method of claim 1 further comprising using file attachment references as values of attributes of database objects.

85. The method of claim 84 further comprising using the file attachment references to maintain and modify non-database objects.

86. The method of claim 82 comprising creating a new object by upgrading the object.

87. The method of claim 86 further comprising creating a user specific upgrade of an object.

88. The method of claim 1 further comprising copying data or program files during an upgrade.

102. The method of claim 72 further comprising synchronizing databases having at least one client, comprising:

propagating effects of a transaction from the client to the headquarters database.

103. The method of claim 102 further comprising merging the transaction, comprising:

applying routed transaction information from the client to the headquarters database.

5. A method of managing a database having files and a mobile user comprising:

a. enabling the user to defer downloading of a file attachment, and

b. allowing the user to request the deferred file attachment in a future docking session.

6. The method of claim 5 further comprising restricting downloading of the files based on one or more of the group of criteria consisting of file size and file type.

7. The method of claim 5 further comprising:

a. enabling only mobile users to defer file downloads, and

b. sending files automatically to regional databases and server databases.

8. The method of claim 5 further comprising enabling mobile users to request files that were deferred.

9. The method of claim 8 further comprising downloading the requested files in a next docking session.

10. The method of claim 5 further comprising retrieving a deferred file in a next docking session when the mobile user requests the file.

11. The method of claim 8 enabling a mobile user to delete the requested files from a mobile client'"'"'s local disk to minimize disk usage.

68. The method of claim 5 further comprising enabling a mobile user to defer downloading of selected files and associated files, file attachments, and non-database file objects.

69. The method of claim 68 further comprising enabling the mobile user to specify files to defer by setting docking session preferences in a control file.

70. The method of claim 69 further comprising displaying a file status of the files in a local file system to the mobile user.

71. The method of claim 5 further comprising:

a. enabling the mobile user to request a file that is previously deferred or is out-of-date, and

b. retrieving an up-to-date copy of the file in a next docking session.

12. A method of managing a database having a software platform, wherein the platform has a specialized business component that creates, updates, and deletes one or more of the objects from the group consisting of file attachments and non-database object files.

13. The method of claim 12 comprising:

a. enabling file attachments on a business object,

b. creating an applet that uses the specialized business component, and

c. adding the applet.

18. A method of managing a database comprising:

a. creating a business object tool, and

b. allowing users to register any file using the tool.

19. The method of claim 18 wherein the business object tool supports object file teams.

20. The method of claim 19 further comprising:

a. allowing a one user to register at least one of the group consisting of a non-database object file and a file attachment, and

b. allowing the user to add other users to a file team.

21. The method of claim 20 wherein the file team views at least one of the group consisting of the non-database object file and the file attachment.

22. The method of claim 20 wherein at least one of the group consisting of the non-database object file and the file attachment is automatically distributed to all users on the file team.

36. A method of managing a database comprising:

a. using at least one of the group consisting of pre-built specialized business components, frames, and applets to enable a file attachment, and

b. adding the file attachment to a database.

37. The method of claim 36 further comprising using at least one of the group of standard features consisting of drag and drop, file updating, and conflict resolution without writing new code.

38. A method of managing a database having at least one user comprising

a. allowing the user to copy an external file attachment wherein the external file attachment is stored in at least one of the group consisting of a file system and a web page, and

b. using this external file to create an additional file.

39. The method of claim 38 further comprising automatically updating the copy of the external file from the original external file.

40. A method of managing a database having at least two business objects comprising allowing different business objects to share a same copy of a file.

51. A method of managing a database having files, file attachments, and at least one docking client comprising:

a. extracting and initializing the docking client,

b. initializing both the file attachments and the files when extracting and initializing the docking client.

52. A method of managing a database having one or more files and file attachments, one or more regional databases, and one or more mobile clients comprising distributing one or more of the files and file attachments to one or more regional databases and one or more mobile clients.

53. The method of claim 52 further comprising:

a. routing files and file attachments from one or more docking clients to one or more server databases, and

b. routing files and file attachments from one or more server databases to one or more docking clients.

57. The method of claim 53 further comprising:

a. enabling a user to create a new data entry or file attachment, and

b. inserting a row in a file table, wherein the file table stores information about file attachments.

58. The method of claim 57 wherein the file table stores file attachment information comprising one or more of the group consisting of a file name, a file size, an original file source, and one or more file docking statuses.

59. The method of claim 58 wherein the original file source comprises one or more of the group consisting of a source file type and a source file full path name.

61. The method of claim 58 further comprising storing a copy of the file attachment and an internal file name in a file system.

62. The method of claim 58 further comprising storing each file attachment in a compressed format to reduce disk usage.

63. The method of claim 58 further comprising:

a. using a file system for connected users, wherein the file system comprises a collection of directories on a file server, and

b. specifying a value in the file.

64. The method of claim 58 further comprising using a file system for a mobile client, wherein the file system resides on a location on the mobile client'"'"'s local disk.

65. The method of claim 64 wherein the location on the mobile client'"'"'s local disk is a client installation directory.

89. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps managing a database, said method steps comprising:

a. adding a file attachment to a database; and

b. enabling a user to attach the file attachment to a business object.

90. An article of manufacture comprising a computer usable medium having computer readable program code embodied therein for causing managing a database, the computer readable program means in said article of manufacture comprising:

a. computer readable program code means for causing a computer to effect adding a file attachment to a database; and

b. computer readable program code means for causing a computer to effect enabling a user to attach the file attachment to a business object.

91. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps managing a database, said method steps comprising:

a. adding a file attachment to a database; and

b. enabling a user to attach the file attachment to a business object; and

c. automatically replicating the file attachment to all docking clients that have visibility to the business object.

92. An article of manufacture comprising a computer usable medium having computer readable program code embodied therein for causing managing a database, the computer readable program in said article of manufacture comprising:

a. computer readable program code for causing a computer to effect adding a file attachment to a database; and

b. computer readable program code for causing a computer to effect a user attaching a file attachment to a business object; and

c. computer readable program code for causing a computer to effect automatically replicating the file attachment to all docking clients that have visibility to the business object.

93. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps managing a database having files, file attachments, and a mobile user, said method steps comprising:

a enabling the user to defer downloading of the files or file attachments; and

b. allowing the user to request the deferred file attachments in a future docking session.

94. An article of manufacture comprising a computer usable medium having computer readable program code embodied therein for causing managing a database having files, file attachments, and a mobile user, the computer readable program in said article of manufacture comprising:

a. computer readable program code for causing a computer to effect enabling the user to defer downloading of the files or file attachments; and

b. computer readable program code for causing a computer to effect allowing the user to request the deferred file attachments in a future docking session.

95. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps managing a database, said method steps comprising:

a. adding a file attachment to a database; and

b. enabling a user to attach one or more file attachments to a business object; and

c. automatically replicating the file attachments to all docking clients that have visibility to the business object; and

d. replicating file table rows and the associated file attachments or non-database file objects to the docking clients that have visibility to the business object.

96. An article of manufacture comprising a computer usable medium having computer readable program code embodied therein for causing managing a database, the computer readable program in said article of manufacture comprising:

a. computer readable program code for causing a computer to effect adding a file attachment to a database; and

b. computer readable program code for causing a computer to effect enabling a user to attach the file attachment to a business object; and

c. computer readable program code for causing a computer to effect automatically replicating the file attachment to all docking clients that have visibility to the business object; and

d. computer readable program code for causing a computer to effect replicating file table rows and the associated file attachments or non-database file objects to the docking clients that have visibility to the business object.

97. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps managing a database, said method steps comprising:

a. adding a file attachment to a database; and

b. enabling a user to attach the file attachment to a business object; and

c. enabling the user to perform at least one of the functions consisting of creating, updating, and deleting files.

98. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps managing a database having at least one user, said method steps comprising:

a. allowing the user to copy an external file wherein the external file is stored in at least one of the group consisting of a file system and a web page.

b. using the external file to create an additional file.

99. A program storage device readable by a machine managing a database having files and at least one server, tangibly embodying a program of instructions executable by a machine to perform method steps managing a database having files and at least one server, wherein some of the files are available and some of the files are not available, said method steps comprising:

a. supporting file access from different data sources; and

b. enabling a server to differentiate between which files are available and which files are not available.

100. A method of managing a database having at least one file attachment and at least one database table, wherein the database table has rows and columns, comprising:

a. associating a file attachment with a row in the database, and

b. updating both the file attachment and the row in a transaction.

101. A method of managing a database having at least one client, at least one file attachment, and at least one database table, wherein the database table has rows and columns, comprising:

a. associating a file attachment with a row in the database, and

b. replicating the file attachment only to the clients that have visibility to the associated database row.

104. A method of managing a database comprising:

a. deferring file attachment transmission during high communications load periods, and

b. transmitting file attachments during low communications load periods.

105. The method of claim 104 further comprising users retrieving deferred files.