Data synchronization

- BEA Systems, Inc.

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.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 10/279,450 entitled “Data Synchronization” filed Oct. 24, 2002; which claims priority to U.S. Provisional Patent Application No. 60/386,487 entitled “Data Synchronization”, filed Oct. 24, 2001.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to technology for deploying and synchronizing data.

2. Description of the Related Art

Web-based software applications have emerged as powerful tools which provide valuable services to vendors and customers alike. E-business web applications can be configured to operate in accordance with business logic to implement a variety of processes which facilitate electronic commerce. Such applications may also provide services which interact with remote Internet clients and/or applications.

The JAVA™2 Platform Enterprise Edition (J2EE), available from Sun Microsystems, Inc. of Santa Clara, Calif., facilitates the development of electronic business web applications that run within the context of multi-tier enterprise applications. The operation of such web applications is governed by the data (“application data”) used to configure the web applications. As a result, the functionality provided by web applications can be modified by updating the application data associated with the applications.

Unfortunately, the deployment and synchronization of new or updated application data to J2EE web applications can be a cumbersome process. Newly-authored application data is often stored in a database in accordance with a particular schema used by the database. If a developer seeks to deploy such application data to a running production server, the data must be extracted from the database before being converted into a form suitable for transmission to the server. Scripts are often necessary to export the application data from a database into a file system. Scripts may also be necessary to import the application data to a running server. For these reasons, maintaining different versions of application data can also be an awkward and unwieldy endeavor.

Moreover, before new application data can be moved to a running production server, it may be necessary to deploy the application data to multiple servers to comply with a multi-stage testing process. This transfer of application data can be a cumbersome manual process which becomes increasingly error-prone as application data is transferred from server to server and more persons are involved. Thus, prior techniques of deploying and synchronizing application data in the context of the J2EE platform can be largely ad-hoc and undesirable.

SUMMARY OF THE INVENTION

The present invention, roughly described, is directed to synchronizing application data used by enterprise applications running on one or more servers. For example, in one embodiment, application data is received and synchronized with a database and data repository. In another embodiment, an application data deployment method is provided allowing application data to be authored, submitted to a source control system, and sent to a remote server where a data repository of the server is synchronized with the data.

In another embodiment, application data is synchronized between enterprise applications through the use of proxy data repositories. In another embodiment, application data is synchronized between data repositories through the polling of one data repository by another.

Systems and computer readable media are also provided for implementing portions of, and variations of, these methods. Many other embodiments are also possible, as set forth in the present disclosure.

BRIEF DESCRIPTIONS OF THE DRAWINGS

FIG. 1 illustrates a conceptual diagram of a system for creating and versioning application data files in accordance with an embodiment of the present invention.

FIG. 2 illustrates a high level block diagram of a system for synchronizing data in accordance with an embodiment of the present invention.

FIG. 3 illustrates a block diagram of a server running an enterprise application having data that can be synchronized in accordance with an embodiment of the present invention.

FIG. 4 is a flowchart illustrating a process for synchronizing data in accordance with an embodiment of the present invention.

FIG. 5 illustrates a block diagram of multiple servers running enterprise applications with data that can be synchronized using a proxy data repository in accordance with an embodiment of the present invention.

FIG. 6 illustrates a block diagram of a cluster of servers running enterprise applications with data that can be synchronized by an administration server in accordance with an embodiment of the present invention.

 DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a conceptual diagram of a system for creating and versioning application data files in accordance with an embodiment of the present invention. Author 110 is a person with the responsibility of creating application data to be used by one or more web applications and/or services. In various embodiments, author 110 can be a line-of-business manager, business engineer, developer, or other person responsible for authoring application data. The application data can be used to configure a web application to operate in accordance with business logic identified by author 110. For example, application data created by author 110 can include business policy documents such as campaign definitions, scenarios, business rule sets, portal definitions, and/or other types of data used by web applications.

In order to produce the application data, author 110 can interface with various software tools, such as control center 120. In one embodiment, control center 120 is an E-Business Control Center tool available from BEA Systems, Inc. of San Jose, Calif. The data created by author 110 using control center 120 can be stored in a local hierarchical file system as a set of application data files. FIG. 1 illustrates an example of application data files 130 stored in a hierarchical file system. The application data files 130 can be organized according to the web application they are created for. In one embodiment, the application data created with control center 120 is stored in XML files in accordance with an XML schema which can be interpreted by the web application for which the data is authored. Since XML can be read and interpreted by various systems across multiple platforms, the use of XML application data provides advantages over database scripting-oriented approaches.

Application data files 130 produced by the interaction of author 110 with control center 120 can be checked into source control system 140. Source control system 140 allows different versions of the application data files 130 to be easily recalled for testing, deployment, synchronization, and/or other purposes. For example, if faulty application data is deployed to a web application, the source control system 140 allows author 110 to recall a previous version of the application data and re-deploy the data to the web application. The use of source control system 140 can also prevent multiple authors from overwriting each other's files when application data is being authored concurrently. In one embodiment, source control system 140 is any suitable source control system known in the art.

After application data has been created, it will typically be subject to a multi-stage approval process to test the interaction of the newly-authored application data with other data and/or applications created by other authors. For example, before application data is deployed to a production server, it may be subject to separate development and quality assurance stages. These stages help ensure that the web applications running on live production servers will operate reliably.

During this collaborative development of web applications, it can become desirable for software developers to synchronize application data across enterprise application boundaries to remote servers. Various data synchronization processes further described herein leverage the advantages provided by HTTP to facilitate the synchronization of application data on remote servers accessible via the Internet. In accordance with certain embodiments of the present invention, newly-created application data can be synchronized with one or more remote running servers. By identifying the URL associated with a server, application data can be remotely synchronized to any server accessible over the Internet via HTTP.

FIG. 2 illustrates a high level block diagram of a system for synchronizing data in accordance with an embodiment of the present invention. The system of FIG. 2 can be used for collaboratively developing and testing web applications before they are ultimately deployed on a production server. In one embodiment, the system of FIG. 2 is implemented using one or more components of BEA WebLogic Platform™, available from BEA Systems, Inc. of San Jose, Calif. As illustrated in FIG. 2, a plurality of servers are in communication with network 210. In one embodiment, the system of FIG. 2 is implemented as a peer-to-peer network. Each server of FIG. 2 is associated with a database which can store application data used by web applications and/or services running on the server. As indicated by FIG. 2, each server can be used for a different purpose in a multi-stage application data approval process. For example, these purposes can include: development (server 230 and database 235), quality assurance (server 240 and database 245), production (server 250 and database 255), and others (not shown).

Each server of FIG. 2 is capable of receiving application data from author system 220 over network 210. The application data received from author system 220 can be synchronized with application data used by web applications running on the various servers as further described herein. In one embodiment, author system 220 is the system illustrated in FIG. 1.

Server tools 260 and database tools 265 are also illustrated in FIG. 2. These tools allow for the realtime modification of data on production server 250 and production database 255, respectively. In one embodiment, server tools 260 are JSP-based tools which allow changes to be made directly to production server 250.

FIG. 3 illustrates a block diagram of a server running an enterprise application having data that can be synchronized in accordance with an embodiment of the present invention. Server 310 can be any of the servers illustrated in FIG. 2 capable of receiving application data from author system 220. As illustrated in FIG. 3, a plurality of web applications and services reside in enterprise application 320 running on server 310. E-business web applications 350 include services 360 that rely upon application data stored in service data repositories 370, 375, and/or 377. Additional services 365 running within the context of enterprise application 320 can also rely upon application data stored in the service data repositories. In one embodiment, the service data repositories are Java objects that function as in-memory caches of data items of interest to a deployed class of service.

Data sync web application 330 also runs within enterprise application 320 and is responsible for performing data synchronization operations in accordance with the present invention. As indicated by FIG. 3, data sync application 330 can communicate with author system 220 of FIG. 2 over network 210. A master data repository 340 within enterprise application 320 can communicate with data sync application 330, database 380, and data repositories 370 and 375.

Data sync application 330 can intercept incoming synchronization requests sent from author system 220 over network 210. In one embodiment, these synchronization requests are sent as XML over HTTP in accordance with a remote protocol. When data sync application 330 receives a synchronization request from author system 220, it channels application data received from author system 220 to master data repository 340 which is a runtime representation of the application data. The data sync application 330 also channels the application data received to database 380 which is a persistent storage location for the application data. In one embodiment, data repository 340 stores incoming application data as Enterprise Java Beans (EJBs). In another embodiment, database 380 is a relational database management system.

In one embodiment, data sync application 330 includes a set of JSPs that are capable of reporting: the contents of master data repository 340, data repositories that are successfully synchronized with master data repository 340, and the contents of each data repository in enterprise application 320.

The service data repositories of FIG. 3 each contain subsets of the application data stored in master data repository 340. Services 360 and 365 use the data in the service data repositories to carry out business tasks. For example, a rules service can use the data to evaluate whether customers fit into a particular customer segment. Since the service data repositories of FIG. 3 maintain only a subset of the data in master data repository 340, each service is able to parse a small, specific set of application data needed by the service without having to maintain copies of all application data maintained in master data repository 340.

Each time the master data repository 340 is synchronized, it notifies data repositories 370 and 375. These data repositories then synchronize their data subsets with the data in the master. In one embodiment, application data is communicated between the components of enterprise application 320 in accordance with a binary protocol. Multiple enterprise applications (not shown) running on server 310 can also be synchronized using a separate data sync application running in each enterprise application. Proxy data repositories can be used to facilitate such synchronizations.

In some cases, the master data repository 340 does not directly synchronize data with a data repository. Rather, a notification chain can be employed using multiple data repositories. Referring to FIG. 3, data repositories 375 and 377 forms a notification chain. When data repository 375 receives updated application data from master data repository 340, it notifies data repository 377. Data repository 377 can then be synchronized with the application data received by data repository 375. As a result, both repositories 375 and 377 can be synchronized without master data repository 340 having to send updated application data to both repositories.

FIG. 4 is a flowchart illustrating a process for synchronizing data in accordance with an embodiment of the present invention. When application data is to be synchronized from author system 220 to any of the servers of FIG. 2, a synchronization process can be initiated (step 410) by sending a synchronization request from author system 220 to the URL of the server to be synchronized where it will be intercepted by data sync application 330. In various embodiments, author 110 can initiate the synchronization process using a graphical interface of control center 120 or a Java command line.

In various embodiments of the present invention, different synchronization modes can be employed. In a refresh-from-client mode, all application data for a given application is synchronized. Using this mode, all data is cleared from the data repositories and then all relevant application data files are sent from the author's local file system to a data sync web application. This mode can be helpful to synchronize in-memory data with persisted data, or to recover from a synchronization error. In a one-way-from-client mode, only those application data files that have been removed, updated, or created on the author's local file are updated. Thus, the amount of data transmitted between an author system and a server to be synchronized can be minimized.

Upon initiation of the synchronization process in step 410, application data to be synchronized will be sent from author system 220 to server 310 over network 210 (step 420). In one embodiment, the application data is sent as XML files over HTTP using a POST command. The application data is received by data sync application 330. Data sync application 330 then synchronizes database 380 and master data repository 340 with the newly-received application data (step 430). As a result of step 430, database 380 contains the updated application data stored in a database format for persistent storage, and master data repository 340 contains the updated application data stored in an EJB runtime format.

As previously described herein, the various applications and services of FIG. 3 may rely upon application data resident in service data repositories. Accordingly, each of the service data repositories can subscribe to receive updated application data. In order to update the application data in data repositories 370 and 375, master data repository 340 notifies each of service data repositories 370 and 375 of any updated application data for which the repositories have subscribed to receive (step 440). Service data repository 377 receives its notification via a notification chain, as previously described. Master data repository 340 also notifies proxy data repositories (not shown) for enterprise applications running on other servers, as further described herein. After the service data repositories have been notified of the updated application data, each repository synchronizes itself with the particular application data in master data repository 340 to which it subscribes (step 450). Proxy data repositories also forward any notifications sent in step 440 to their remote data sync web applications in order to synchronize repositories running in other enterprise applications (not shown) on server 310 or other remote servers (step 460), as further described herein.

Service data repositories 370 and/or 375 can also poll master data repository 340 periodically to check whether application data has been updated. If updated data is detected, then application data maintained in master data repository 340 can be synchronized with service data repositories 370 and/or 375.

Master data repository 340 maintains a log that describes each update and includes a description of which data repositories were successfully updated, and which were not. Data sync application 330 can return a status message to author system 220 via HTTP or a Java command shell to identify which application data files were successfully synchronized. Each data repository of FIG. 3 can also maintain logs that describe its current contents.

As illustrated in FIG. 3, application data can be synchronized between an author system and an enterprise application running on a single server. In accordance with various embodiments of the present invention, multiple servers can also synchronized through a single synchronization process initiated in step 410 of FIG. 4. This synchronization of multiple servers can be facilitated through the use of additional elements as set forth in FIG. 5.

FIG. 5 illustrates a block diagram of multiple servers running enterprise applications with data that can be synchronized using a proxy data repository in accordance with an embodiment of the present invention. Enterprise applications 620 and 660 are running on servers 610 and 650, respectively. A master data repository 630 running within enterprise application 620 can be synchronized by a data sync application (not shown) in communication with an author system (not shown) as previously described herein. Master data repository 630 is in communication with proxy data repository 640 also running within enterprise application 620. Proxy data repository 640 can subscribe to receive updated application data stored in master data repository 630.

Data sync web application 680 is an instance of a data sync application that runs on remote server 650. However, rather than receiving updates directly from an author system 220 (similar to data sync application 330 of FIG. 3), data sync application 680 receives updates sent from proxy data repository 640. Remote master data repository 670 is a master data repository for enterprise application 660 which is updated in accordance with application data received by data sync application 680. Remote master data repository 670 can pass updated application data to other proxy and/or service data repositories (not shown) running in enterprise application 660 as previously discussed herein. It will be understood that additional elements (not shown) can be present on the servers of FIG. 5, such as one or more of the elements set forth in the servers of FIG. 3 and/or FIG. 6.

In operation, master data repository 630 receives updated application data from a data sync web application in communication with an author system (not shown) such as author system 220 of FIG. 2. Proxy data repository 640 is subscribed to receive updated application data from master data repository 640. As a result, the updated application data received by master data repository 630 is passed to proxy data repository 640. Proxy data repository 640 then passes the application data from server 610 to the data sync application running on server 650. In one embodiment, application data is received by proxy data repository 640 in accordance with a binary protocol. Accordingly, proxy data repository 640 marshals the application data into an XML format before passing the application data as XML over HTTP to data sync application 680 in remote server 650.

When the updated application data is received by data sync application 680, the data sync application 650 proceeds to update remote master data repository 670 with the updated application data. A persistent storage database (not shown in FIG. 5) as illustrated in FIG. 3 is also synchronized, and the updated application data is then forwarded to all data repositories (not shown) of enterprise application 660 which are subscribed to receive the updated application data.

Thus, by subscribing proxy data repositories to receive updates from a master data repository, application data within enterprise applications running on remote servers can be synchronized with application data received by the master data repository. Proxies can also be used to synchronize data across different enterprise applications running on the same server. Moreover, by linking remote servers to additional remote servers through proxies, chains of multiple servers can be synchronized. These principles can be further applied to the synchronizing application data across clusters of servers as set forth in FIG. 6.

FIG. 6 illustrates a block diagram of a cluster of servers running enterprise applications with data that can be synchronized by an administration server in accordance with an embodiment of the present invention. Data sync web application 730 and master data repository 740 of enterprise application 720 on administration server 710 can communicate with managed servers 760 of cluster 790. As previously discussed, application data residing in data repositories (not shown) of enterprise applications 770 running on remote servers 760 can be synchronized with updated application data stored in master data repository 740. Master data repository 740 can pass updated application data to a proxy data repository (not shown) which then passes the data to data sync web applications (not shown) running on enterprise applications 770. As a result, multiple servers 760 can be synchronized by a single administration server 710 that receives updated application data from an author system (not shown). It will be understood that additional elements (not shown) can be present on the servers of FIG. 6, such as one or more of the elements set forth in the servers of FIG. 3 and/or FIG. 5.

Where applicable, the present invention can be implemented using hardware, software, or combinations of hardware and software. Software in accordance with the present invention, such as program code and/or data, can stored on one or more computer readable mediums. Also where applicable, the various hardware components and/or software components set forth herein can be combined into composite components comprising software, hardware, or both without departing from the spirit of the present invention. Similarly, where applicable, the various hardware components and/or software components set forth herein can be dissected into sub-components comprising software, hardware, or both without departing from the spirit of the present invention. In addition, where applicable, it is contemplated that software components can be implemented as hardware components, and vice-versa. Furthermore, where applicable, the various steps set forth herein can be combined into composite steps and/or dissected into sub-steps. It is also contemplated that software components set forth herein can be implemented using one or more general purpose or specific purpose computers and/or computer systems, networked and/or otherwise.

The foregoing disclosure is not intended to limit the present invention to the precise forms or particular fields of use disclosed. It is contemplated that various alternate embodiments and/or modifications to the present invention are possible in light of the disclosure.

Claims

1. A method for synchronizing application data in a cluster of servers, comprising:

receiving an update to the application data in a first server in the cluster of servers, wherein the update to the application data is provided from a device external to the cluster of servers;
synchronizing the application data with the update to form updated application data;
forwarding the updated application data to a proxy data repository in the first server; and
forwarding said updated application data from said proxy data repository to a second server in the cluster of servers, wherein said updated application data is configured to synchronize with the proxy data repository on said second server, said synchronizing in said second server being performed on data in the second server by the second server separate from the synchronizing performed in the first server;
forwarding said updated application data from said proxy data repository to a third server in the cluster of servers wherein said updated application data is configured to synchronize with the proxy data repository on said third server, said synchronizing in said third server being performed on data in the third server by the third server separate from the synchronizing performed in the first and second server,
wherein said proxy data repository receives the updated application data in a binary protocol and marshals the updated application data into an XML format before forwarding the updated application data to the second server and the third server.

2. The method of claim 1, wherein:

the proxy data repository transmits the XML formatted data over HTTP to the second server and the third server.

3. The method of claim 1, wherein:

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

4. The method of claim 1 wherein the second server and the third server are running on a same enterprise application as the first server.

5. The method of claim 1, further comprising:

synchronizing data in a master data repository in the first server with the updated application data;
notifying a first service data repository in the first server each time the master data repository is synchronized; and
synchronizing data subsets in the first service data repository with the data in the master data repository, said synchronizing being performed on the data subsets by the first service data repository separate from synchronizing performed on the new application data in the master data repository after being notified by the master data repository.

6. The method of claim 5, further comprising:

notifying said master data repository the first service data repository has been synchronized with the updated application data; and
maintaining a log in the master data repository indicating when the first service data repository has been synchronized.

7. The method of claim 1, further comprising:

maintaining a log in the first server indicating when the proxy data repository in the second server has been synchronized with the updated application data and when the proxy data repository in the third server has been synchronized with the updated application data.

8. The method of claim 1, further comprising: storing the updated application data in a master data repository in the first server separate from the proxy data repository.

Referenced Cited
U.S. Patent Documents
5237614 August 17, 1993 Weiss
5347653 September 13, 1994 Flynn et al.
5355474 October 11, 1994 Thuraisingham et al.
5369702 November 29, 1994 Shanton
5426747 June 20, 1995 Weinreb et al.
5544322 August 6, 1996 Cheng et al.
5557747 September 17, 1996 Rogers et al.
5627886 May 6, 1997 Bowman
5649195 July 15, 1997 Scott et al.
5757669 May 26, 1998 Christie et al.
5758355 May 26, 1998 Buchanan
5797128 August 18, 1998 Birnbaum
5825883 October 20, 1998 Archibald et al.
5826000 October 20, 1998 Hamilton
5838909 November 17, 1998 Roy et al.
5848396 December 8, 1998 Gerace
5867667 February 2, 1999 Butman et al.
5884325 March 16, 1999 Bauer
5889953 March 30, 1999 Thebaut et al.
5918210 June 29, 1999 Rosenthal et al.
5926816 July 20, 1999 Bauer
5950195 September 7, 1999 Stockwell et al.
5954798 September 21, 1999 Shelton et al.
5956400 September 21, 1999 Chaum et al.
5956719 September 21, 1999 Kudo et al.
5966707 October 12, 1999 Van Huben et al.
5987469 November 16, 1999 Lewis et al.
5987611 November 16, 1999 Freund
5991735 November 23, 1999 Gerace
6006194 December 21, 1999 Merel
6006265 December 21, 1999 Rangan et al.
6009410 December 28, 1999 LeMole et al.
6026433 February 15, 2000 D'Arlach et al.
6029144 February 22, 2000 Barrett et al.
6029182 February 22, 2000 Nehab et al.
6054910 April 25, 2000 Tada et al.
6055515 April 25, 2000 Consentino et al.
6055637 April 25, 2000 Hudson et al.
6058392 May 2, 2000 Sampson et al.
6081829 June 27, 2000 Sidana
6083276 July 4, 2000 Davidson et al.
6092083 July 18, 2000 Brodersen et al.
6098173 August 1, 2000 Elgressy et al.
6105027 August 15, 2000 Schneider et al.
6108687 August 22, 2000 Craig
6112192 August 29, 2000 Capek
6122647 September 19, 2000 Horowitz et al.
6128663 October 3, 2000 Thomas
6133915 October 17, 2000 Arcuri et al.
6141010 October 31, 2000 Hoyle
6141686 October 31, 2000 Jackowski et al.
6148333 November 14, 2000 Guedalia et al.
6154844 November 28, 2000 Touboul et al.
6157924 December 5, 2000 Austin
6158010 December 5, 2000 Moriconi et al.
6161139 December 12, 2000 Win et al.
6167407 December 26, 2000 Nachenberg et al.
6167445 December 26, 2000 Gai et al.
6167448 December 26, 2000 Hemphill et al.
6169794 January 2, 2001 Oshimi et al.
6170009 January 2, 2001 Mandal et al.
6178172 January 23, 2001 Rochberger
6182142 January 30, 2001 Win et al.
6182226 January 30, 2001 Reid et al.
6182277 January 30, 2001 DeGroot et al.
6185587 February 6, 2001 Bernardo et al.
6188399 February 13, 2001 Voas et al.
6195696 February 27, 2001 Baber et al.
6202066 March 13, 2001 Barkley et al.
6202157 March 13, 2001 Brownlie et al.
6202207 March 13, 2001 Donohue
6205466 March 20, 2001 Karp et al.
6209101 March 27, 2001 Mitchem et al.
6216231 April 10, 2001 Stubblebine
6226745 May 1, 2001 Wiederhold
6233576 May 15, 2001 Lewis
6236991 May 22, 2001 Frauenhofer et al.
6237628 May 29, 2001 Miller et al.
6241608 June 5, 2001 Torango
6249795 June 19, 2001 Douglis
6253321 June 26, 2001 Nikander et al.
6260050 July 10, 2001 Yost et al.
6269393 July 31, 2001 Yost et al.
6269456 July 31, 2001 Hodges et al.
6275941 August 14, 2001 Saito et al.
6285366 September 4, 2001 Ng et al.
6285983 September 4, 2001 Jenkins
6285985 September 4, 2001 Horstmann
6292900 September 18, 2001 Ngo et al.
6295607 September 25, 2001 Johnson
6301613 October 9, 2001 Ahlstrom et al.
6304881 October 16, 2001 Halim et al.
6308163 October 23, 2001 Du et al.
6317868 November 13, 2001 Grimm et al.
6327594 December 4, 2001 Van Huben et al.
6327618 December 4, 2001 Ahlstrom et al.
6336073 January 1, 2002 Ihara et al.
6339423 January 15, 2002 Sampson et al.
6339826 January 15, 2002 Hayes, Jr. et al.
6341352 January 22, 2002 Child et al.
6353886 March 5, 2002 Howard et al.
6360363 March 19, 2002 Moser et al.
6377973 April 23, 2002 Gideon
6381579 April 30, 2002 Gervais et al.
6385627 May 7, 2002 Cragun
6393474 May 21, 2002 Eichert et al.
6397222 May 28, 2002 Zellweger
6397231 May 28, 2002 Salisbury et al.
6412070 June 25, 2002 Van Dyke et al.
6412077 June 25, 2002 Roden et al.
6418448 July 9, 2002 Sarkar
6418452 July 9, 2002 Kraft
6430556 August 6, 2002 Goldberg et al.
6438563 August 20, 2002 Kawagoe
6449638 September 10, 2002 Wecker et al.
6457007 September 24, 2002 Kikuchi et al.
6460084 October 1, 2002 Van Horne et al.
6460141 October 1, 2002 Olden
6463440 October 8, 2002 Hind et al.
6466239 October 15, 2002 Ishikawa
6466949 October 15, 2002 Yang et al.
6473791 October 29, 2002 Al-Ghosein et al.
6477543 November 5, 2002 Huang et al.
6477575 November 5, 2002 Koeppel et al.
6484177 November 19, 2002 Van Huben et al.
6484261 November 19, 2002 Wiegel
6487594 November 26, 2002 Bahlmann
6510513 January 21, 2003 Danieli
6519647 February 11, 2003 Howard et al.
6530024 March 4, 2003 Proctor
6539375 March 25, 2003 Kawasaki
6571247 May 27, 2003 Danno et al.
6581071 June 17, 2003 Gustman et al.
6584454 June 24, 2003 Hummel et al.
6587849 July 1, 2003 Mason et al.
6587876 July 1, 2003 Mahon et al.
6598077 July 22, 2003 Primak et al.
6615218 September 2, 2003 Mandal et al.
6618806 September 9, 2003 Brown et al.
6633538 October 14, 2003 Tanaka et al.
6654747 November 25, 2003 Van Huben et al.
6665677 December 16, 2003 Wotring et al.
6668354 December 23, 2003 Chen et al.
6684369 January 27, 2004 Bernardo et al.
6697805 February 24, 2004 Choquier et al.
6721888 April 13, 2004 Liu et al.
6725446 April 20, 2004 Hahn et al.
6732144 May 4, 2004 Kizu et al.
6735586 May 11, 2004 Timmons
6735701 May 11, 2004 Jacobson
6738789 May 18, 2004 Multer et al.
6751659 June 15, 2004 Fenger et al.
6754672 June 22, 2004 McLauchlin
6757698 June 29, 2004 McBride et al.
6769095 July 27, 2004 Brassard et al.
6769118 July 27, 2004 Garrison et al.
6779002 August 17, 2004 Mwaura
6785721 August 31, 2004 Immerman
6789202 September 7, 2004 Ko et al.
6801949 October 5, 2004 Bruck et al.
6834284 December 21, 2004 Acker et al.
6856999 February 15, 2005 Flanagin et al.
6857012 February 15, 2005 Sim et al.
6865549 March 8, 2005 Connor
6880005 April 12, 2005 Bell et al.
6889222 May 3, 2005 Zhao
6901403 May 31, 2005 Bata et al.
6904454 June 7, 2005 Stickler
6915482 July 5, 2005 Jellum
6920457 July 19, 2005 Pressmar
6922695 July 26, 2005 Skufca et al.
6934934 August 23, 2005 Osborne et al.
6957261 October 18, 2005 Lortz
6961897 November 1, 2005 Peel et al.
6965999 November 15, 2005 Fox et al.
6970876 November 29, 2005 Hotti et al.
6978379 December 20, 2005 Goh et al.
6985915 January 10, 2006 Somalwar et al.
6988138 January 17, 2006 Alcorn et al.
7003578 February 21, 2006 Kanada et al.
7035879 April 25, 2006 Shi et al.
7035944 April 25, 2006 Fletcher et al.
7047522 May 16, 2006 Dixon, III et al.
7054910 May 30, 2006 Nordin et al.
7062490 June 13, 2006 Adya et al.
7062511 June 13, 2006 Poulsen
7080000 July 18, 2006 Cambridge
7085755 August 1, 2006 Bluhm et al.
7089584 August 8, 2006 Sharma
7093200 August 15, 2006 Schreiber et al.
7096224 August 22, 2006 Murthy et al.
7174563 February 6, 2007 Brownlie et al.
7181731 February 20, 2007 Pace
7290015 October 30, 2007 Singhal et al.
20010009016 July 19, 2001 Hofmann et al.
20010032128 October 18, 2001 Kepecs
20010034771 October 25, 2001 Hutsch et al.
20010039586 November 8, 2001 Primak
20010044810 November 22, 2001 Timmons
20020005867 January 17, 2002 Gvily
20020019827 February 14, 2002 Shiman et al.
20020029296 March 7, 2002 Anuff et al.
20020046286 April 18, 2002 Caldwell
20020059394 May 16, 2002 Sanders
20020062451 May 23, 2002 Scheidt et al.
20020067370 June 6, 2002 Forney et al.
20020069261 June 6, 2002 Bellare et al.
20020087571 July 4, 2002 Stapel et al.
20020103818 August 1, 2002 Amberden
20020104071 August 1, 2002 Charisius et al.
20020107913 August 8, 2002 Rivera et al.
20020107920 August 8, 2002 Hotti
20020111998 August 15, 2002 Kim
20020112171 August 15, 2002 Ginter et al.
20020120685 August 29, 2002 Srivastava et al.
20020124053 September 5, 2002 Adams et al.
20020135617 September 26, 2002 Samid
20020143819 October 3, 2002 Han et al.
20020147645 October 10, 2002 Alao et al.
20020147696 October 10, 2002 Acker et al.
20020152267 October 17, 2002 Lennon
20020152279 October 17, 2002 Sollenberger et al.
20020161903 October 31, 2002 Besaw
20020169893 November 14, 2002 Chen et al.
20020173971 November 21, 2002 Stirpe et al.
20020178119 November 28, 2002 Griffin et al.
20020194267 December 19, 2002 Flesner et al.
20030014442 January 16, 2003 Shiigi et al.
20030032409 February 13, 2003 Hutcheson et al.
20030065721 April 3, 2003 Roskind
20030069874 April 10, 2003 Hertzog
20030078959 April 24, 2003 Yeung et al.
20030078972 April 24, 2003 Tapissier et al.
20030088617 May 8, 2003 Clark et al.
20030105974 June 5, 2003 Griffin et al.
20030110448 June 12, 2003 Haute et al.
20030115292 June 19, 2003 Griffin et al.
20030117437 June 26, 2003 Cook et al.
20030120686 June 26, 2003 Kim et al.
20030126464 July 3, 2003 McDaniel et al.
20030126558 July 3, 2003 Griffin
20030131113 July 10, 2003 Reeves et al.
20030135490 July 17, 2003 Barrett et al.
20030145275 July 31, 2003 Qian et al.
20030146937 August 7, 2003 Lee
20030149722 August 7, 2003 Jolley et al.
20030167315 September 4, 2003 Chowdhry et al.
20030167455 September 4, 2003 Iborra et al.
20030187956 October 2, 2003 Belt et al.
20030204481 October 30, 2003 Lau
20030212766 November 13, 2003 Giles et al.
20030216938 November 20, 2003 Shour
20030220913 November 27, 2003 Doganata et al.
20030220963 November 27, 2003 Golovinsky et al.
20030229623 December 11, 2003 Chang et al.
20040019650 January 29, 2004 Auvenshire
20040024812 February 5, 2004 Park et al.
20040030744 February 12, 2004 Rubin et al.
20040030795 February 12, 2004 Hesmer et al.
20040078371 April 22, 2004 Worrall et al.
20040098467 May 20, 2004 Dewey et al.
20040167880 August 26, 2004 Smith
20040167899 August 26, 2004 Patadia et al.
20040205473 October 14, 2004 Fisher et al.
20040205557 October 14, 2004 Bahrs et al.
20040230546 November 18, 2004 Rogers
20040243824 December 2, 2004 Jones
20050021502 January 27, 2005 Chen et al.
20050050184 March 3, 2005 Boden et al.
20050060324 March 17, 2005 Johnson et al.
20050086206 April 21, 2005 Balasubramanian et al.
20050097008 May 5, 2005 Ehring et al.
20050198617 September 8, 2005 Kim et al.
20060059107 March 16, 2006 Elmore et al.
20060085412 April 20, 2006 Johnson et al.
20060122882 June 8, 2006 Brown et al.
20070083484 April 12, 2007 McVeigh et al.
Other references
  • Method and System for Visually Constructing Document Type Definitions and Related Artifacts Using a Reusable Object Model, IBM Technical Disclosure Bulletin, May 23, 2001.
Patent History
Patent number: 7516167
Type: Grant
Filed: Apr 22, 2005
Date of Patent: Apr 7, 2009
Patent Publication Number: 20050187986
Assignee: BEA Systems, Inc. (Redwood Shores, CA)
Inventors: Daniel Selman (Stodmarsh), Robert Bergman (Denver, CO), Edward K. O'Neil (Boulder, CO)
Primary Examiner: Don Wong
Assistant Examiner: Thanh-Ha Dang
Attorney: Fliesler Meyer LLP
Application Number: 11/112,440
Classifications
Current U.S. Class: 707/203; 707/1; 707/3; 707/10; 707/200; Distributed Data Processing (709/201); Client/server (709/203)
International Classification: G06F 17/30 (20060101); G06F 15/16 (20060101); G06F 7/00 (20060101);