Managing client configuration data
First Claim
Patent Images
1. A method for providing an interface to a function that manages entities, said method comprising:
- receiving a request to implement a change for modifying data associated with the entities in a first client device, said each of the entities includes data stored in a data structure representing a topology data of one of the entities in a memory area of the first client device, wherein a name of the each of the entities is stored in an entity namespace field of the data structure and entity data identifying the each of the entities is stored in an entity field of the data structure, said entity data including at least a transaction identifier data representing an entity change transaction and a date/time data indicating a date and time when a transaction represented by the transaction identifier is deleted, wherein the each of the entities includes properties associated therewith, said properties being stored in a property field of the data structure;
in response to the received request, identifying a subset of each of the entities subject to the change based on a relationship data and a relationship type data, said identified subset of each of the entities stores a version of the data included in each of the entities, said relationship data defining a relationship between the entities, said relationship data being stored in a relationship field of the data structure, said relationship type data describing a type of the relationship between an entity and the another entities, said relationship type data being stored in a relationship type field of the data structure, wherein the received request comprises one of the following changes;
a rollback request for changing the identified subset from a current configuration state identified by a current transaction identifier to a complete configuration state identified by a previous transaction identifier and a roll-forward request to change the identified subset from the current configuration state to a next configuration state identified by a next transaction identifier, said complete configuration state being represented by a last known good configuration data;
if the received request is the rollback request,identifying the transaction identifier of the identified subset associated with the complete configuration state;
setting the date/time data associated with the identified transaction to a current date and time if the transaction identifier data of the identified subset is greater than the previous transaction identifier;
appending the current transaction identifier to a transaction stack for the identified subset; and
setting the previous transaction identifier as the current transaction identifier;
or if the received request is the roll-forward request,setting the date/time data associated with the identified subset to null if the transaction identifier data of the identified subset is greater than the current transaction identifier but less than a last entry in the transaction stack;
setting the current transaction identifier to that of the last entry in the transaction stack; and
removing the last entry from the transaction stack; and
implementing the change to the identified subset in response to the request by modifying the data associated with the identified subset of the one or more entities;
receiving another request, said other request specifying the identified subset of the entities, and wherein said implementing the change in the data comprises implementing the chance in the version of the data associated with the identified subset of the entities, wherein the received other request further specifies a time interval to effect the change in the data stored in the memory area, and wherein said implementing the change in the data comprises effecting the change to the data stored in the memory area in accordance with the specified time interval.
3 Assignments
0 Petitions
Accused Products
Abstract
Method for providing an interface to a function that manages a plurality of entities. Computer-executable instructions receive a request to implement a change in configuration data. The configuration data is stored in a memory area and relates to an operation of one or more entities. In response to the received request, computer-executable instructions identify a plurality of the entities affected by the change and implement the change for the identified plurality of entities in accordance with the function.
-
Citations
21 Claims
-
1. A method for providing an interface to a function that manages entities, said method comprising:
-
receiving a request to implement a change for modifying data associated with the entities in a first client device, said each of the entities includes data stored in a data structure representing a topology data of one of the entities in a memory area of the first client device, wherein a name of the each of the entities is stored in an entity namespace field of the data structure and entity data identifying the each of the entities is stored in an entity field of the data structure, said entity data including at least a transaction identifier data representing an entity change transaction and a date/time data indicating a date and time when a transaction represented by the transaction identifier is deleted, wherein the each of the entities includes properties associated therewith, said properties being stored in a property field of the data structure; in response to the received request, identifying a subset of each of the entities subject to the change based on a relationship data and a relationship type data, said identified subset of each of the entities stores a version of the data included in each of the entities, said relationship data defining a relationship between the entities, said relationship data being stored in a relationship field of the data structure, said relationship type data describing a type of the relationship between an entity and the another entities, said relationship type data being stored in a relationship type field of the data structure, wherein the received request comprises one of the following changes;
a rollback request for changing the identified subset from a current configuration state identified by a current transaction identifier to a complete configuration state identified by a previous transaction identifier and a roll-forward request to change the identified subset from the current configuration state to a next configuration state identified by a next transaction identifier, said complete configuration state being represented by a last known good configuration data;if the received request is the rollback request, identifying the transaction identifier of the identified subset associated with the complete configuration state; setting the date/time data associated with the identified transaction to a current date and time if the transaction identifier data of the identified subset is greater than the previous transaction identifier; appending the current transaction identifier to a transaction stack for the identified subset; and setting the previous transaction identifier as the current transaction identifier;
or if the received request is the roll-forward request,setting the date/time data associated with the identified subset to null if the transaction identifier data of the identified subset is greater than the current transaction identifier but less than a last entry in the transaction stack; setting the current transaction identifier to that of the last entry in the transaction stack; and removing the last entry from the transaction stack; and implementing the change to the identified subset in response to the request by modifying the data associated with the identified subset of the one or more entities; receiving another request, said other request specifying the identified subset of the entities, and wherein said implementing the change in the data comprises implementing the chance in the version of the data associated with the identified subset of the entities, wherein the received other request further specifies a time interval to effect the change in the data stored in the memory area, and wherein said implementing the change in the data comprises effecting the change to the data stored in the memory area in accordance with the specified time interval. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 16, 17, 18, 19, 20, 21)
-
-
10. One or more computer storage media having stored thereon an application programming interface for managing entities, said application programming interface having computer-executable instructions to:
-
receiving a request to implement a change for modifying configuration data associated with the entities in a first client device, said each of the entities includes data stored in a data structure representing a topology data of the one of the entities in a memory area of the first client device, wherein a name of the each of the entities is stored in an entity namespace field of the data structure and entity data identifying the each of the entities is stored in an entity field of the data structure, said entity data including at least a transaction identifier data representing an entity change transaction and a date/time data indicating a date and time when a transaction represented by the transaction identifier is deleted, wherein the each of the entities includes properties associated therewith, said properties being stored in a property field of the data structure; in response to the received request, identifying one or more entities subject to the change based on a relationship data and a relationship type data, said identified entities storing a version of the configuration data, said relationship data defining a relationship between the entities, said relationship data being stored in a relationship field of the data structure, said relationship type data describing a type of the relationship between an entity and the another entities, said relationship type data being stored in a relationship type field of the data structure, wherein the received request comprises one of the following changes;
a rollback request for changing the identified entities from a current configuration state identified by a current transaction identifier to a complete configuration state identified by a previous transaction identifier and a roll-forward request to change the identified entities from the current configuration state to a next configuration state identified by a next transaction identifier, said complete configuration state being represented by a last known good configuration data;if the received request is the rollback request, identifying the transaction identifier of the identified entities associated with the complete configuration state; setting the date/time data associated with the identified transaction to a current date and time if the transaction identifier data of the identified entities is greater than the previous transaction identifier; appending the current transaction identifier to a transaction stack for the identified entities; and setting the previous transaction identifier as the current transaction identifier;
or if the received request is the roll-forward request,setting the date/time data associated with the identified entities to null if the transaction identifier data of the identified entities is greater than the current transaction identifier but less than a last entry in the transaction stack; setting the current transaction identifier to that of the last entry in the transaction stack; and removing the last entry from the transaction stack; and implementing the change to the identified entities in response to the request by modifying the configuration data associated with the identified entities; wherein the application programming interface further comprises computer-executable instructions to receive another request, said other request specifying the identified entities, and implement the change in the version of the configuration data associated with the identified entities, wherein the received other request further specifies a time interval to effect the change in the configuration data stored in the memory area, and wherein the implementing the change in the configuration data comprises effecting the change in the configuration data stored in the memory area in accordance with the specified time interval. - View Dependent Claims (11, 12, 13)
-
-
14. A system for managing a plurality of entities, said system comprising:
-
a memory area for storing configuration data defining an operation for executing a service by one or more of the entities, said memory area further storing topology data describing at least the following information;
a name of each of the entities, entity data identifying the each of the entities, said entity data including at least a transaction identifier data representing an entity change transaction and a date/time data indicating a date and time when a transaction represented by the transaction identifier is deleted, relationship data defining a relationship between the entities, and a relationship type data describing a type of the relationship between an entity and the another entities; anda processor configured to execute computer-executable instructions for; receiving a request to implement a change in the configuration data; identifying a plurality of the entities affected by the change in response to the received request as a function of the topology data, said identified plurality of the entities storing a version of the configuration data, wherein the received request comprises one of the following changes;
a rollback request for changing the identified entities from a current configuration state identified by a current transaction identifier to a complete configuration state identified by a previous transaction identifier and a roll-forward request to change the identified entities from the current configuration state to a next configuration state identified by a next transaction identifier, said complete configuration state being represented by a last known good configuration data;
if the received request is the rollback request,identifying the transaction identifier of the identified entities associated with the complete configuration state; setting the date/time data associated with the identified transaction to a current date and time if the transaction identifier data of the identified entities is greater than the previous transaction identifier; appending the current transaction identifier to a transaction stack for the identified entities; and setting the previous transaction identifier as the current transaction identifier;
or if the received request is the roll-forward request,setting the date/time data associated with the identified entities to null if the transaction identifier data of the identified entities is greater than the current transaction identifier but less than a last entry in the transaction stack; setting the current transaction identifier to that of the last entry in the transaction stack; and removing the last entry from the transaction stack; and implementing the change for the identified plurality of entities by modifying the configuration data associated with the identified plurality of entities; wherein the processor further receives another request. said received other request specifying the identified entities, and the processor implements the change in the version of the configuration data associated with the identified entities, said received other request specifying a time interval to effect the change in the configuration data stored in the memory area, and wherein the processor implements the change in the configuration data stored in the memory area in accordance with the specified time interval. - View Dependent Claims (15)
-
Specification