Occasionally-connected application server

• US 20060117073A1
• Filed: 05/04/2005
• Published: 06/01/2006
• Est. Priority Date: 05/20/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Bosworth, Adam, Eskafi, Farokh H., Bosworth, Alexander, Khesin, Alexander, Lloyd, Alexander, Lucas, Terry, Burdon, Richard, Ong, Ken
• Granted Patent: US 7,650,432 B2
• 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: G06F 16/273 Asynchronous replication or reconciliation

Abstract

Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application'"'"'s anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Claims

1. An occasionally-connected application server comprising:

a synchronization unit configured to synchronize data nodes with a client for an application, the application including an occasionally-connected data model; and

a conduit manager configured to translate between data from external systems and the data nodes defined by the occasionally-connected data model.

2. The occasionally-connected application server of claim 1, wherein the occasionally-connected application server is configured to cache data nodes in the cache as indicated by metadata in the occasionally-connected data model.

3. The occasionally-connected application server of claim 1, wherein the occasionally-connected data model indicates a client'"'"'s anticipated usage of external data.

4. The occasionally-connected application server of claim 1, wherein the conduit manager is configured to use conduits, the conduits defining transforms between data defined by the occasionally-connected data model and requests and responses for a specific web service.

5. The occasionally-connected application server of claim 1, further comprising an adaptive user interface server, wherein at least one client receives HTML pages from the occasionally-connected application server which are constructed by the adaptive user interface server using the data nodes and the occasionally-connected data model.

6. The occasionally-connected application server of claim 1, wherein at least one client is transferred the data nodes and the occasionally-connected data model to produce a display at the client.

7. The occasionally-connected application server of claim 6, wherein the at least one client can run an application using the data nodes and the occasionally-connected data model without being in contact with the occasionally-connected application server.

8. A method comprising:

at a server, synchronizing data nodes with a client for an application including an occasionally-connected data model; and

at the server, translating between data from external systems and the data nodes defined by the occasionally-connected data model.

9. The method of claim 8, wherein the occasionally-connected application server caches data nodes in the cache as indicated by metadata in the occasionally-connected data model.

10. The method of claim 8, wherein the occasionally-connected data model indicates a client'"'"'s anticipated usage of external data.

11. The method of claim 8, wherein the translation uses conduits, the conduits defining transforms between data defined by the occasionally-connected data model and requests and responses for a specific web service.

12. The method of claim 8, wherein clients are transferred both the data nodes and the occasionally-connected data model to produce a display at the client.

13. An occasionally-connected application server comprising:

memory to store an occasionally-connected data model; and

a cache to store data nodes as defined by the occasionally-connected data model, wherein the occasionally-connected application server caches data nodes in the cache as indicated by metadata in the occasionally-connected data model.

14. The occasionally-connected application server of claim 13, wherein the occasionally-connected application server is configured to translate data between external systems and data nodes defined by the occasionally-connected data model.

15. The occasionally-connected application server of claim 13, wherein data nodes include XML.

16. The occasionally-connected application server of claim 13, further comprising a conduit manager, wherein the conduit manager is configured to use conduits, the conduits defining transforms between data defined by occasionally-connected data model and requests and responses for a specific web service.

17. The occasionally-connected application server of claim 13, further comprising an adaptive user interface server, wherein at least one client receives HTML pages from the occasionally-connected application server which are constructed by the adaptive user interface server using the data nodes and the occasionally-connected data model.

18. The occasionally-connected application server of claim 13, wherein at least one client is transferred the data nodes and the occasionally-connected data model to produce a display at the client.

19. The occasionally-connected application server of claim 18, wherein the client can run an application using both the data nodes and the occasionally-connected data model without being in contact with the occasionally-connected application server.

20. The occasionally-connected application server of claim 20, wherein synchronization of the data nodes between the occasionally-connected application server and the client can be done in the background.

21. An occasionally-connected application server comprising:

a first component configured to synchronize data nodes with a client for an application, the application including an occasionally-connected data model; and

a second component configured to translate between data from external systems and the data nodes defined by the occasionally-connected data model.

22. A system including:

an occasionally-connected application server configured to provide an application to a client, the application allowing a client to read and update application data without requiring current access to the occasionally-connected application server, the occasionally-connected application server adapted to obtain application data from an external system to send to the client, wherein the occasionally-connected application server is adapted to translate data from the external system into data nodes.

23. The system of claim 22, wherein the external system is a service bus.

24. The system of claim 22, wherein the external system is a web service.