US 2004/0025079 A1Published application

System and method for using a data replication service to manage a configuration repository

AssigneeBEA Systems, Inc.

InventorsAnanthan Srinivasan, Reto Kramer, Dean B. Jacobs

Life of this patent

Estimating the term…

Loading patent…

Abstract

A mechanism for making changes consistently across an application server domain or a cluster. Server configuration consistency is absolutely necessary for cluster deployments. The invention allows changes to the configuration repository and to the application deployment process to be managed via a Data Replication Service (DRS). The former requires that the configuration repository be version aware, while the latter breaks down the application deployment process into two phases—one for data distribution and processing as far as possible, and the second to expose the changes through the Java Naming and Directory Interface (JNDI).

Claims12

Dependent claims

A system for using a data replication service to consistently manage server configuration within a domain or cluster, comprising:

a master server that contains server configuration information;
a master data replication service layer adapted to send, from said master server, data replication packets defining changes in the server configuration information, said data replication packets including a version number associated with each change in the server configuration;
a slave data replication service layer adapted to receive, at a slave server, data replication packets from the master data replication service layer;
and,
a slave server that determines whether the configuration data currently contained thereon has been updated to correspond to the version number associated with the latest data replication packet received, and if the data on the slave server does not correspond to that version number requesting a delta of server configuration information be sent from said master server to said slave server.

2 more elements

Dependencies are inferred from the claim text.

Facts

Application: 10/371,247Filed 20 Feb 2003
Priority: 22 Feb 2002
Published: 5 Feb 2004
Term ends: Not estimatedThe source records don’t support an estimate.

Classification7 codes

H04L 67/1095
In which an application is distributed across nodes in the network: replication or mirroring of data, e.g. scheduling or transport for data…
G06F 2201/82
Indexing scheme relating to error detection, to error correction, and to monitoring: solving problems relating to consistency
Y10S 707/99953
Coherency, e.g. same view to multiple users: recoverability
Y10S 707/99954
Coherency, e.g. same view to multiple users: version management

Family

Application60/359,063Us provisional application · filed 22 Feb 2002
US 7,617,289 B2Related patent
US 2004/0025079 A1This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key