Data synchronization

• US 20050187986A1
• Filed: 04/22/2005
• Published: 08/25/2005
• Est. Priority Date: 10/24/2001
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Bergman, Robert, O'Neil, Edward K., Selman, Daniel
• Granted Patent: US 7,516,167 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/80 of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML content-based retrieval of web data G06F16/95
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions
• CPC Class Codes: G06F 21/1012 to domains
• CPC Class Codes: G06F 21/1015 to users
• CPC Class Codes: G06F 21/1064 Restricting content processing at operating system level
• CPC Class Codes: G06F 21/1073 Conversion
• CPC Class Codes: G06F 21/1076 Revocation
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06F 2221/2117 User registration
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2145 Inheriting rights or properties, e.g., propagation of permissions or restrictions within a hierarchy
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 41/18 : Delegation of network management function, e.g. customer network management [CNM]
• CPC Class Codes: H04L 41/22 : comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 63/0815 : providing single-sign-on or federations
• CPC Class Codes: H04L 63/0884 : by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 : for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/06 : specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/14 : Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 : Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/2871 : Implementation details of single intermediate entities
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/567 : Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/75 : Indicating network or usage conditions on the user display
• CPC Class Codes: H04L 69/22 : Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: Y10S 707/99931 : Database or file accessing
• CPC Class Codes: Y10S 707/99933 : Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99953 : Recoverability
• CPC Class Codes: Y10S 707/99954 : Version management

Abstract

Application data used by enterprise applications running on one or more servers can be synchronized with application data deployed from other locations. Application data can be transmitted as XML files over HTTP to facilitate synchronization with web-enabled servers. Multiple service data repositories can be synchronized with application data residing in a master data repository that runs within an enterprise application. Server-to-server data synchronization functionality is also provided through the use of proxy data repositories. Application data files can be deployed from an author system to remote servers. Newly-authored application data files can be versioned in the author system using a source control system and selectively deployed to various servers by the author in conjunction with a multi-stage testing process in preparation for deployment of the application data to a production server.

Claims

1. A method for deploying application data to a remote web server over a network, comprising:

authoring application data;

submitting said application data to a source control system;

identifying a server to receive application data; and

sending application data to said server, said server capable of synchronizing a data repository of said server with said application data.

2. The method of claim 1, wherein:

said server is identified by a URL associated with said server.

3. The method of claim 1, wherein:

said application data comprises at least one XML file.

4. The method of claim 1, wherein:

said application data comprises application data files adapted for transmission over HTTP.

5. The method of claim 1, wherein:

said method is performed as part of a testing process in preparation for deployment of said application data to a production server.

6. The method of claim 1, wherein the data repository is a master data repository

7. The method of claim 6, wherein when a data sync application receives a synchronization request from an author system, the data sync application channels application data received from the author system to the master data repository.

8. The method of claim 7, wherein the data sync application also channels the application data received to a database which is a persistent storage location for the application data.

9. The method of claim 1 wherein the data repository stores incoming application data as Enterprise Java Beans (EJBs).

10. The method of claim 1, wherein an author system includes a source control system to maintain versioning.

11. A system for deploying application data to a remote web server over a network, comprising:

an authoring system to author application data, the authoring system including a source control system receiving the application data and identifying a server to receive application data; and

a server capable of synchronizing a data repository of said server with the application data.

12. The system of claim 11, wherein:

said server is identified by a URL associated with said server.

13. The system of claim 11, wherein:

said application data comprises at least one XML file.

14. The system of claim 11, wherein:

said application data comprises application data files adapted for transmission over HTTP.

15. The system of claim 11, wherein the system is used in preparation for deployment of said application data to a production server.

16. The system of claim 11, wherein the data repository is a master data repository.

17. The system of claim 16, wherein when a data sync application receives a synchronization request from an author system, the data sync application channels application data received from the author system to the master data repository.

18. The system of claim 17, wherein the data sync application also channels the application data received to a database which is a persistent storage location for the application data.

19. The system of claim 11 wherein the data repository stores incoming application data as Enterprise Java Beans (EJBs).