Claims
- 1. A method for updating an asset in a source environment on a source node connected to a network, comprising the steps of:
receiving a synchronization call having a data argument and an asset type, the data argument defining changes to the asset, the asset being of the asset type; selecting an adapter, associated with the asset type, based on the asset type; passing the data argument to the adapter; determining if the asset type is at least one of an entity data type and entity bean type; determining a table, associated with the asset, based on the data argument; retrieving at least one synchronization information object from a target environment on the target node; creating a synchronization asset having a logic/data portion and an extended environment portion copied from the asset, the asset being updated with the synchronization information object; establishing a connection between the target node and the source node, the source node being the origin of the asset; and sending the synchronization asset over the network to the source node.
- 2. The process according to claim 1, wherein the synchronization call is generated external to the target node.
- 3. The process according to claim 1, wherein the synchronization call is generated internal to the target node.
- 4. The process according to claim 1, wherein the asset type is an entity data type and the argument data indicates that a synchronization should occur every time a database record in the table is changed.
- 5. The process according to claim 1, wherein the asset type is an entity data type and the argument data indicates that a synchronization should occur every time a specific set of database tables is changed.
- 6. The process according to claim 1, wherein the asset type is an entity data type and the argument data indicates that a synchronization should occur every time a database record in the table is changed and a certain user interface navigation has occurred.
- 7. The process according to claim 1, wherein the asset type is an entity data type and the argument data indicates that a synchronization should occur every time a database record in the table is changed and a certain connectivity event has occurred.
- 8. The process according to claim 1, wherein the asset type is an entity data type and the argument data indicates that a synchronization should occur every time a database record in the table is changed and a certain number of database record changes has occurred.
- 9. The process according to claim 1, wherein the asset type is an entity data type and the argument data indicates that a synchronization should occur every time a database record in the table is changed and a certain set of database changes have occurred resulting in a number of bytes being changed.
- 10. The process according to claim 1, wherein the asset type is an entity data type and the argument data indicates that a synchronization should occur every time a database record in the table is changed and at least one of a database record in the table is changed, a specific set of database tables is changed, a database record in the table is changed and a certain user interface navigation has occurred, a database record in the table is changed and a certain user interface navigation has occurred, a database record in the table is changed and a certain connectivity event has occurred, a database record in the table is changed and a certain number of database record changes has occurred, and a database record in the table is changed and a certain set of database changes have occurred that result in a number of bytes being changed.
- 11. The process according to claim 1, wherein the synchronization information object includes at least one of an insertion, a deletion, and updating of database records.
- 12. The process according to claim 1, wherein the connection is established through a component distribution server/asset distribution server.
- 13. The process according to claim 1, wherein the connection is established directly to the source node.
- 14. The process according to claim 1, wherein the connection is established indirectly to the source node through a chain of component distribution servers.
- 15. The process according to claim 15, wherein the source node includes at least one of a target node, an enterprise information system, a component distribution server/asset distribution server, and an edge server.
- 16. The process according to claim 15, wherein the connection is made using the machine address of the source node.
- 17. The process according to claim 1, wherein the source node includes an enterprise information system having at least one of an on-line retail/wholesale sales, marketing, and inventory system, an enterprise supply chain management systems, a product and/or content distribution systems, an on-line financial systems, a service providing system, an on-line human resource system, an on-line pay roll service, an on-line banking system, an airline reservation system, and a general business transaction system.
- 18. The process according to claim 1, wherein “said asset being updated” includes at least one of updating the extended environment portion, and updating the logic/data portion.
- 19. The process according to claim 1, wherein the connection is made through an enterprise information system deployment agent on the source node.
- 20. The process according to claim 1, wherein the synchronization information object includes at least one SQL query applicable to a source database table on the source.
- 21. The process according to claim 1, further including creating a “coalesced synchronization asset” from a first synchronization asset and a second synchronization asset.
- 22. The process according to claim 22, further including:
determining whether the first synchronization asset and the second synchronization conflict; and rectifying the conflict using a compensating transaction.
- 23. A method for synchronizing an asset on a multi-tiered network, comprising:
receiving an asset synchronization request; selecting a synchronization asset adapter associated with the asset; retrieving synchronization information associated with the asset; creating a synchronization asset; and transferring the synchronization asset to a component distribution server.
- 24. The method of claim 23, wherein the asset is an entity bean type.
- 25. The method of claim 23, wherein the asset is an entity data type.
- 26. The method of claim 25, wherein the synchronization request is received every time at least one record in a database associated with the asset is changed.
- 27. The method of claim 26, wherein the synchronization information includes insertions, deletions, or modifications to the database associated with the asset.
- 28. The method of claim 27, wherein the synchronization information further comprises recorded SQL queries adaptively configured to be applied to a source database.
- 29. The method of claim 23, wherein the asset includes a logic/data part and an extended environment part, and the synchronization asset is created by updating the logic/data part and extended environment part of the asset.
- 30. A method for synchronizing an asset on a multi-tiered network, comprising:
receiving an asset synchronization request in a target environment; determining a first asset type associated with the asset; selecting a first synchronization asset adapter associated with the asset; determining a table associated with the asset; retrieving synchronization information associated with the asset; creating a synchronization asset having the synchronization information; transferring the synchronization asset to a component distribution server; determining a source environment associated with the asset; sending the synchronization asset to the source environment; selecting a second synchronization asset adapter associated with the synchronization asset; determining a second asset type associated with the synchronization asset; and applying the synchronization information from the synchronization asset to the asset in the source environment.
- 31. The method of claim 30, wherein the asset is an entity bean type.
- 32. The method of claim 30, wherein the asset is an entity data type.
- 33. The method of claim 32, wherein the synchronization request is received every time at least one record in a database associated with the asset is changed.
- 34. The method of claim 33, wherein the synchronization information includes insertions, deletions, or modifications to the database associated with the asset.
- 35. The method of claim 34, wherein the synchronization information further comprises recorded SQL queries adaptively configured to be applied to a source environment database.
- 36. The method of claim 30, wherein the asset includes a logic/data part and an extended environment part, and the synchronization asset is created by updating the logic/data part and extended environment part of the asset.
- 37. The method of claim 30, further comprising:
transferring a plurality of synchronization assets to the component distribution server; creating a coalesce synchronization asset from the plurality of synchronization assets; and sending the coalesce synchronization asset to the source environment.
- 38. The method of claim 30, wherein the synchronization asset is sent to an enterprise information system deployment agent in the source environment.
- 39. The method of claim 30, wherein the synchronization request is sent to a client distribution agent in the target environment.
- 40. A system for synchronizing an asset on a multi-tiered network, comprising:
an asset synchronization request; a target computer, including a new version of the asset, a first synchronization asset adapter, and a synchronization asset associated with the new version of the asset; a component distribution computer, including a database associating assets with source computers; and a source computer, including an old version of the asset and a second synchronization asset adapter.
- 41. The system of claim 40, wherein the target computer further includes a client distribution agent.
- 42. The system of claim 40, wherein the source computer further includes an enterprise information system deployment agent.
- 43. The system of claim 40, wherein the component distribution computer further includes a coalesce synchronization asset.
PRIORITY DOCUMENTS & RELATED REFERENCES
[0001] This application claims priority to provisional U.S. Patent Application Serial No. 60/229,685, entitled “Distributed Internet Services Provisional Filing”, filed on Sep. 1, 2000 to Chen et al. which is incorporated herein by reference in its entirety.
[0002] Priority is also claimed for the following documents for any matter not disclosed in provisional U.S. patent application Ser. No. 60/229,685 incorporated by reference above. The following references are related to this patent application and are herein incorporated by reference in their entirety:
[0003] provisional U.S. Patent Application Serial No. 60/236,864, entitled “Distributed Internet Server” to Pace et al., filed Sep. 29, 2000;
[0004] provisional U.S. Patent Application Serial No. 60/237,179, entitled “Business Plan and Business Plan Executive Summary” to Chen et al., filed Oct. 2, 2000;
[0005] provisional U.S. Patent Application Serial No. 60/254,377, entitled “Distributed Internet Services provisional filing II” to Pace et al., filed Dec. 8, 2000;
[0006] provisional U.S. Patent Application Serial No. 60/262,288, entitled “Data Structure, Architecture, Apparatus, and Program Product Capable of Being Distributed to and Executed on Different Network Tiers and on Various Computer Platforms and Environment” to Pace et al., filed Jan. 17, 2001;
[0007] U.S. patent application Ser. No. ______, entitled “Extended Environment Data Structure for Distributed Digital Assets Over Multi-tiered Computer Networks”, to Pace et al., filed Sep. 4, 2001;
[0008] U.S. patent application Ser. No. ______, entitled “Server System and Method for Discovering Digital Assets in Enterprise Information Systems”, to Bobick et al., filed Sep. 4, 2001;
[0009] U.S. patent application Ser. No. ______, entitled “Server System and Method for Exporting Digital Assets in Enterprise Information Systems”, to Pace et al., filed Sep. 4, 2001;
[0010] U.S. patent application Ser. No. ______, entitled “System and Method for Transactional Deployment J2EE Web Components, Enterprise Java Bean Components, and Application Data over Multi-tiered Computer Networks”, to Pace et al., filed on Sep. 4, 2001;
[0011] U.S. patent application Ser. No. ______, entitled “Server System and Method for Distributing and Scheduling Modules to be Executed on Different Tiers of a Network”, to Pace et al., filed Sep. 4, 2001;
[0012] U.S. patent application Ser. No. ______, entitled “Data Structure, Architecture Apparatus, and Program Product Capable of Being Distributed to and Executed on Different Network Devices and on Various Computer Platforms and Environments”, to Pace et al., filed Sep. 4, 2001;
[0013] U.S. patent application Ser. No. ______, entitled “System and Method for Distributing Assets to Multi-Tiered Network Nodes, to Pizzomi et al. filed on Sep. 4, 2001;
[0014] U.S. patent application Ser. No. ______, entitled “Method and System for Deploying An Asset Over a Multi-Tiered Network”, to Pace et al. filed on Sep. 4, 2001;
[0015] U.S. patent application Ser. No. ______, entitled “System and Method for Translating an Asset for Distribution Over Multi-Tiered Networks (Processing)” to Pace et al. filed on Sep. 4, 2001;
[0016] U.S. patent application Ser. No. ______, entitled “System and Method for Synchronizing Assets on Multi-Tiered Networks, to Pace et al. filed on Sep. 4, 2001;
[0017] U.S. patent application Ser. No. ______, entitled “Method and System for Deploying an Asset Over a Multi -Tiered Network” to Pace et al. filed on Sep. 4, 2001;
[0018] U.S. patent application Ser. No. ______, entitled “System and Method for Adjusting the Distribution of an Asset Over a Multi-Tiered Network”, to Pace et al. filed on Sep. 4, 2001;
[0019] U.S. patent application Ser. No. ______, entitled “System and Method for Bridging Assets to Network Nodes on Multi-Tiered Networks”, to Pace et al. filed on ______;
[0020] U.S. patent application Ser. No. ______, entitled “Method and System for Deploying an Asset Over a Multi-Tiered Network”, to Pace et al. filed on Sep. 4, 2001, describing asset streaming;
[0021] U.S. patent application Ser. No. ______, entitled “System, Method, and Data Structure for Packaging Assets for Processing and Distribution on Multi-Tiered Networks”, to Bobick et al. filed on Sep. 4, 2001;
[0022] U.S. patent application Ser. No. ______, entitled System and Method for Transactional and Fault-Tolerant Distribution of Digital Assets Over Multi-Tiered Computer Networks, to Bobick et al. filed on Sep. 4, 2001;
[0023] U.S. patent application Ser. No. ______, entitled “System and Method for Collaboration Using Web Browsers”, to Chen et al. filed on Sep. 4, 2001;
[0024] PCT Patent Application No. ______, entitled “System and Method for Collaboration Using Web Browsers”, to Chen et al. filed on Aug. 31, 2001;
[0025] PCT Patent Application No. ______, entitled “System, Method, Uses, Products, Program Products, and Business Methods for Distributed Internet and Distributed Network Services”, to Chen et al. filed on Aug. 31, 2001; and
[0026] U.S. patent application Ser. No. ______, entitled “System, Method, Uses, Products, Program Products, and Business Methods for Distributed Internet and Distributed Network Services”, to Chen et al. filed on Sep. 4, 2001.
Provisional Applications (5)
|
Number |
Date |
Country |
|
60229685 |
Sep 2000 |
US |
|
60236864 |
Sep 2000 |
US |
|
60237179 |
Oct 2000 |
US |
|
60254377 |
Dec 2000 |
US |
|
60262288 |
Jan 2001 |
US |