Transaction management in a configuration database

A method of managing transactions in a Java system configuration database having a plurality of sub-trees and an initial state, the configuration database having a client schema containing persistent and transient data, and a server schema containing persistent data, the method comprising:

• obtaining a lock on a node in a sub-tree in the server schema of the Java system configuration database, the lock having an access type determined according to whether one of a new node is being added to the Java system configuration database and an existing node is being modified;
• retrieving a first set of persistent data containing a first plurality of data items describing client hardware and a second set of persistent data containing a second plurality of data items describing user configurations from the server schema, wherein the first sot and the second set describe a client computer;
• associating data items in the first set with data items in the second sir thereby creating a plurality of data item correspondences describing a client computer;
• modifying the client schema of the Java system configuration database with the plurality of data item correspondences;
• updating an event repository to reflect modifications to the Java system configuration database;
• notifying an event manager that the lock on the node has been released;
• and
• reverting the Java system configuration database to the initial state by reading data from the event repository.

A computer readable medium containing programmed instructions arranged to update a Java system configuration database having a client schema containing persistent and transient data, and a server schema containing persistent data, the computer readable medium including programmed instructions for:

• creating an event queue, identified by a transaction handle, when the updating transaction is instantiated, for containing state data relating to the updating transaction;
• obtaining a lock having an access type on a node, the access type determined according to whether one of a new node is being added to the Java system configuration database and an existing node is being modified;
• retrieving a first set of persistent data containing a first plurality of data items describing client hardware and a second set of persistent data containing a second plurality of data items describing user configurations from the serve schema, wherein the first set and the second set describe a client computer;
• associating data items in the first set with data items in the second set thereby creating a plurality of data item correspondences describing a client computer;
• modifying the client schema of the Java system configuration database with the plurality of data item correspondences;
• and
• committing the updating transaction by releasing the lock if the modification is successful.

A computer readable medium containing programmed instructions arranged to manage transactions in a Java system configuration database having a plurality of sub-trees and an initial state, the configuration database having a client schema containing persistent and transient data, and a server schema containing persistent data, the computer readable medium including programmed instructions for:

• obtaining a lock on a node in a sub-tree in the server schema of the Java system configuration database, the lock having an access type determined according to whether one of a new node is being added to the Java system configuration database and an existing node is being modified;
• retrieving a first set of persistent data containing a first plurality of data items describing client hardware and a second set of persistent data containing a second plurality of data items describing user configurations from the server schema, wherein the first set and the second set describe a client computer;
• associating data items in the first set with data items in the second set thereby creating a plurality of data item correspondences describing a client computer;
• modifying the client schema of the Java system configuration database with the plurality of data item correspondences;
• updating an event repository to reflect modifications to the Java system configuration database;
• notifying an event manager that the lock on the node has been released;
• and
• reverting the Java system configuration database to the initial state by reading data from the event repository.

A computer data signal embodied in a carrier wave and representing sequences of instructions arranged to update a Java system configuration database having a client schema containing persistent and transient data, and a server schema containing persistent data, the sequencce of instructions comprising:

• creating an event queue, identified by a transaction handle, when the updating transaction is instantiated, for containing state data relating to the updating transaction;
• obtaining a lock having an access type on a node, the access type determined according to whether one of a new node is being added to the Java system configuration database and an existing node is being modified;
• retrieving a first set of persistent data containing a first plurality of data items describing client hardware and a second set of persistent data containing a second plurality of data items describing user configurations from the server schema, wherein the first set and the second set describe a client computer;
• associating data items in the first set with data items in the second set thereby creating a plurality of data item correspondences describing a client computer;
• modifying the client schema of the Java system configuration database with the plurality of data item correspondences;
• and
• committing the updating transaction by releasing the lock if the modification is successful.

A computer data signal embodied in a carrier wave and representing sequences of instructions arranged to manage transactions in a Java system configuration database having a plurality of sub-trees and an initial state, the configuration database having a client schema containing persistent and transient data, and a server schema containing persistent data, the sequence of instructions comprising:

• obtaining a lock on a node in a sub-tree in the server schema of the Java system configuration database, the lock having an access type determined according to whether one of a new node is being added to the Java system configuration database and an existing node is being modified;
• retrieving a first set of persistent data containing a first plurality of data items describing client hardware and a second set of persistent data containing a second plurality of data items describing user configurations from the server schema, wherein the first set and the second set describe a client computer;
• associating data items in the first set with data items in the second set thereby creating a plurality of data item correspondences describing a client computer;
• modifying the client schema of the Java system configuration database with the plurality of data item correspondences;
• updating an event repository to reflect modifications to the Java system configuration database;
• notifying an event manager that the lock on the node has been released;
• and
• reverting the Java system configuration database to the initial state by reading data from the event repository.