Apparatus, methods, and computer program products for transactional support of network management operations
First Claim
Patent Images
1. A computer implemented method of managing network management transactions requested by a particular application and directed toward at least a single predetermined target object, in a computer system including an application transaction server and a network management platform, comprising:
- receiving a plurality of network management requests for affecting at least a single object having particular initial object values, wherein the plurality of network management requests are received from a plurality of sources;
building a network management transaction combining the plurality of network management requests which have been received, wherein the network management transaction comprises an atomic unit such that the plurality of network management requests commits or fails in unison; and
storing current object values of each targeted object to enable resetting of object values to initial settings if network management transaction processing fails.
2 Assignments
0 Petitions
Accused Products
Abstract
An application transaction (AT) server collects multiple user specified application operations for processing as a single application transaction and records essential information about each transaction being performed in a database. Such recordation enables the values of objects targeted by the particular application transaction prior to completion of a transaction to be restored in case of failed operation of the application transaction.
41 Citations
64 Claims
-
1. A computer implemented method of managing network management transactions requested by a particular application and directed toward at least a single predetermined target object, in a computer system including an application transaction server and a network management platform, comprising:
-
receiving a plurality of network management requests for affecting at least a single object having particular initial object values, wherein the plurality of network management requests are received from a plurality of sources;
building a network management transaction combining the plurality of network management requests which have been received, wherein the network management transaction comprises an atomic unit such that the plurality of network management requests commits or fails in unison; and
storing current object values of each targeted object to enable resetting of object values to initial settings if network management transaction processing fails. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A computer program product embodied in a computer usable medium having a computer readable code means embodied therein for managing network management transactions, the computer program product comprising:
-
a first computer readable code construct (CRCC) configured to receive a plurality of network management request messages from a plurality of sources, wherein the network management request messages specify desired network management operations with respect to at least a single target object;
a second CRCC configured for combining the plurality of network management requests into a single network management transaction, wherein the network management transaction comprises an atomic unit such that the plurality of network management requests commits or fails in unison; and
a third CRCC configured to determining whether to perform the network management transaction locally or whether to select a particular application transaction server to perform the constructed network management transaction.
-
-
7. A computer system comprising:
-
an application transaction server (ATS) configured to operate an application transaction manager in response to receipt of network management transactions from a plurality of sources, wherein the network management transactions comprise atomic units of network management requests that commit or fail in unison; and
a database coupled to the ATS for storing an undo log to enable reversal of network management transactions performed by said application transaction server. - View Dependent Claims (8)
a data processing system configured with a routing mechanism to selectively distribute particular network management requests for processing at selected servers.
-
-
9. A computer implemented method of network management, comprising:
-
combining a plurality of network management request messages from a plurality of sources for performance of corresponding network management operations into a combined network management transaction, wherein the transaction comprises an atomic unit such that the network management operations are either performed or not performed in unison; and
executing the combined network management transaction, wherein said executing comprises attempting to perform each of the network management operations. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27)
invoking separate M-GET request(s) to get the original values of the object(s) and attribute(s) that would be overwritten by the actual M-SET;
storing the result of said requests in an M-SET record in the undo log, and committing this record if the actual M-SET operation is successful; and
invoking the undo record to roll back the effect of the actual operation in case of abort.
-
-
22. The method of claim 20, further comprising the below steps to prepare the undo record for a management operation equivalent to an M-CREATE operation and to roll back the effect of said operation in the event the transaction enclosing said operation is aborted:
-
creating a new M-DELETE record for the target object in the undo log, and committing the record, if the actual M_CREATE operation is successful; and
invoking the said undo record to roll back the effect of the actual operation in case of abort.
-
-
23. The method of claim 20 further comprising preparing an undo record for a management operation equivalent to an M-DELETE operation and rolling back the effect of the management operation in the event the transaction enclosing said operation is aborted:
-
invoking separate M-GET requests to get the original values of the object(s) and attribute(s) that are removable by the actual M-DELETE;
storing the result of said requests in an M-CREATE record in an undo log, and committing this record if the particular M-SET operation is successful; and
invoking the undo record to roll back the effect of the actual operation in case of abort.
-
-
24. The computer implemented method according to claim 20 including building an undo record for management operations equivalent to SNMP-SET PDU, SNMP-SET operation for simple object instance operation for creating a row object, SNMP-SET operation for deleting a row object for objects exhibiting and conforming to the behaviours as specified in SNMP (RFC 1157 and related RFC'"'"'s) and SNMP V2 (RFC 1905 and related RFC'"'"'s) for said SNMP protocols.
-
25. The method of claim 24, further comprising preparing the undo record for a management operation equivalent to SNMP-SET operation for simple object instance and rolling back the effect of said operation in the event the transaction enclosing said operation is aborted;
-
invoking separately SNMP-GET request(s) to get the original values of the object(s) and attribute(s) that would be overwritten by the actual SNMP-SET;
storing the result of the said requests in an SNMP-SET record in the undo log, and committing this record if the actual SNMP-SET operation is successful; and
invoking the undo record to roll back the effect of actual operation in case of abort.
-
-
26. The method of claim 24, further comprising preparing the undo record for a management operation equivalent to a SNMP-SET operation for creating a row object and to roll back the effect of said operation in the event the transaction enclosing said operation is aborting, including:
-
creating a new SnmpDelReq record for the target row object in the undo log, and committing this record if the actual SNMP-SET operation to create a row object is successful; and
invoking the said undo record to roll back the effect of the actual operation in case of abort.
-
-
27. The method of claim 24, further comprising preparing an undo record for a management operation equivalent to SNMP-SET operation for deleting a row object and to roll back the effect of the operation in the event the transaction enclosing said operation is aborting, including:
-
invoking separate SNMP-GET requests to get the original values of columns of the row object that would be removed by the actual SNMP-SET operation;
storing the result of said requests in an SnmpCreReq record for the target row object in the undo log, and committing this record if the actual SNMP-SET operation to delete a new object is successful; and
invoking said undo record to roll back the effect of the actual operation in case of abort.
-
-
28. A computer system comprising:
-
an application transaction server (ATS) configured to process a network management transaction, wherein the network management transaction comprises an atomic unit of network management requests from a plurality of sources, wherein the atomic unit commits or fails in unison; and
a database coupled to the application transaction server for storing an undo log to enable reversal of a network management transaction performed by said application transaction server in the event of failure of any subordinate part of the network management transaction.
-
-
29. A method for performing network management, the method comprising:
-
receiving a plurality of network management request messages from a plurality of sources, wherein each network management request message comprises a request to perform a network management operation affecting one or more target objects;
performing the plurality of requested network management operations as a single network management transaction, wherein said performing the plurality of requested network management operations as a single network management transaction comprises ensuring that either
1) all of the network management operations are committed successfully;
or
2) each network management operation is aborted if one or more of the network management operations fail, wherein, for a given network management operation, aborting the given network management operation comprises ensuring that the given network management operation does not affect a target object.- View Dependent Claims (30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42)
storing information regarding the original states of target objects to be affected by the requested network management operations, wherein the stored information is usable to undo the effects of the requested network management operations if one or more of the network management operations fail.
-
-
31. The method of claim 30, further comprising:
undoing the effects of one or more of the requested network management operations using the stored information, in the event that one or more of the network management operations fail.
-
32. The method of claim 31,
wherein a first network management request message includes a request to perform a network management operation affecting original values associated with a first target object; -
wherein said storing information regarding the original states of target objects to be affected by the requested network management operations comprises storing the original values associated with the first target object;
wherein said undoing the effects of one or more of the requested network management operations using the stored information comprises resetting the first target object to use the stored original values.
-
-
33. The method of claim 31,
wherein said storing information regarding the original states of target objects to be affected by the requested network management operations comprises: -
for at least one of the requested network management operations, creating an undo record, wherein the undo record specifies a command which, when executed, is operable to undo the effects of the requested network management operation;
wherein said undoing the effects of one or more of the requested network management operations using the stored information comprises executing the command specified by the undo record.
-
-
34. The method of claim 33,
wherein the plurality of network management request messages comprises a plurality of Common Management Information Protocol (CMIP) messages; -
wherein the command comprises one or more of;
a CMIP M-GET message;
a CMIP M-SET message;
a CMIP M-CREATE message; and
a CMIP M-DELETE message.
-
-
35. The method of claim 29, further comprising:
-
receiving a “
begin transaction”
message prior to said receiving the plurality of network management request messages, wherein the “
begin transaction”
message signifies that subsequently received network management request messages are to be performed as a single network management transaction;
receiving a “
commit transaction”
message subsequently to said receiving the plurality of network management request messages, wherein the “
commit transaction”
message signifies that previously received network management request messages are to be performed as a single network management transaction.
-
-
36. The method of claim 35, further comprising:
associating the plurality of network management request messages together as a single network management transaction, in response to said receiving the “
begin transaction”
message.
-
37. The method of claim 29,
wherein the plurality of network management request messages are received from a network management application. -
38. The method of claim 29,
wherein each network management request message is a message creating according to a particular network management protocol. -
39. The method of claim 38,
wherein the network management protocol comprises one of: -
the Common Management Information Protocol (CMIP);
orthe Simple Network Management Protocol (SNMP).
-
-
40. The method of claim 29, wherein the plurality of network management request messages comprises one or more of:
-
a CMIP M-GET message;
a CMIP M-SET message;
a CMIP M-CREATE message; and
a CMIP M-DELETE message.
-
-
41. The method of claim 29,
wherein each of said target objects comprises an object that conforms to behavior specified by a particular network management protocol. -
42. The method of claim 29,
wherein at least one of the target objects represents a particular device connected to a network.
-
43. A computer system for performing network management, the computer system comprising:
-
a processor coupled to a memory medium, wherein the memory medium stores program instructions;
wherein the processor is operable to execute the program instructions in order to;
receive a plurality of network management request messages from a plurality of sources, wherein each network management request message includes a request to perform a network management operation affecting one or more target objects;
perform the plurality of requested network management operations as a single network management transaction, wherein said performing the plurality of requested network management operations as a single network management transaction comprises ensuring that either
1) all of the network management operations are committed successfully;
or
2) each network management operation is aborted if one or more of the network management operations fail, wherein, for a given network management operation, aborting the given network management operation comprises ensuring that the given network management operation does not affect a target object.- View Dependent Claims (44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56)
store information regarding the original states of target objects to be affected by the requested network management operations, wherein the stored information is usable to undo the effects of the requested network management operations if one or more of the network management operations fail.
-
-
45. The computer system of claim 44, wherein the processor is further operable to execute the program instructions in order to:
undo the effects of one or more of the requested network management operations using the stored information, in the event that one or more of the network management operations fail.
-
46. The computer system of claim 45,
wherein a first network management request message includes a request to perform a network management operation affecting original values associated with a first target object; -
wherein said storing information regarding the original states of target objects to be affected by the requested network management operations comprises storing the original values associated with the first target object;
wherein said undoing the effects of one or more of the requested network management operations using the stored information comprises resetting the first target object to use the stored original values.
-
-
47. The computer system of claim 45, wherein, in performing said storing information regarding the original states of target objects to be affected by the requested network management operations, the processor is operable to:
-
for at least one of the requested network management operations, create an undo record, wherein the undo record specifies a command which, when executed, is operable to undo the effects of the requested network management operation;
wherein said undoing the effects of one or more of the requested network management operations using the stored information comprises executing the command specified by the undo record.
-
-
48. The computer system of claim 47,
wherein the plurality of network management request messages comprises a plurality of Common Management Information Protocol (CMIP) messages; -
wherein the command comprises one or more of;
a CMIP M-GET message;
a CMLP M-SET message;
a CMIP M-CREATE message; and
a CMIP M-DELETE message.
-
-
49. The computer system of claim 43, wherein the processor is further operable to execute the program instructions in order to:
-
receive a “
begin transaction”
message prior to said receiving the plurality of network management request messages, wherein the “
begin transaction”
message signifies that subsequently received network management request messages are to be performed as a single network management transaction; and
receive a “
commit transaction”
message subsequently to said receiving the plurality of network management request messages, wherein the “
commit transaction”
message signifies that previously received network management request messages are to be performed as a single network management transaction.
-
-
50. The computer system of claim 49, wherein the processor is further operable to execute the program instructions in order to:
associate the plurality of network management request messages together as a single network management transaction, in response to said receiving the “
begin transaction”
message.
-
51. The computer system of claim 43,
wherein the plurality of network management request messages are received from a network management application. -
52. The computer system of claim 43,
wherein each network management request message is a message creating according to a particular network management protocol. -
53. The computer system of claim 52,
wherein the network management protocol comprises one of: -
the Common Management Information Protocol (CMIP);
orthe Simple Network Management Protocol (SNMP).
-
-
54. The computer system of claim 43, wherein the plurality of network management request messages comprises one or more of:
-
a CMIP M-GET message;
a CMIP M-SET message;
a CMIP M-CREATE message; and
a CMIP M-DELETE message.
-
-
55. The computer system of claim 43,
wherein each of said target objects comprises an object that conforms to behavior specified by a particular network management protocol. -
56. The computer system of claim 43,
wherein at least one of the target objects represents a particular device connected to a network.
-
57. A memory medium for performing network management, the memory medium comprising program instructions executable to:
-
receive a plurality of network management request messages from a plurality of sources, wherein each network management request message includes a request to perform a network management operation affecting one or more target objects;
perform the plurality of requested network management operations as a single network management transaction, wherein said performing the plurality of requested network management operations as a single network management transaction comprises ensuring that either
1) all of the network management operations are committed successfully;
or
2) each network management operation is aborted if one or more of the network management operations fail, wherein, for a given network management operation, aborting the given network management operation comprises ensuring that the given network management operation does not affect a target object.- View Dependent Claims (58, 59, 60, 61, 62, 63, 64)
store information regarding the original states of target objects to be affected by the requested network management operations, wherein the stored information is usable to undo the effects of the requested network management operations if one or more of the network management operations fail.
-
-
59. The memory medium of claim 58, further comprising program instructions executable to:
undo the effects of one or more of the requested network management operations using the stored information, in the event that one or more of the network management operations fail.
-
60. The memory medium of claim 57,
wherein each network management request message is a message creating according to a particular network management protocol. -
61. The memory medium of claim 60,
wherein the network management protocol comprises one of: -
the Common Management Information Protocol (CMIP);
orthe Simple Network Management Protocol (SNMP).
-
-
62. The memory medium of claim 57, wherein the plurality of network management request messages comprises one or more of:
-
a CMIP M-GET message;
a CMIP M-SET message;
a CMIP M-CREATE message; and
a CMIP M-DELETE message.
-
-
63. The memory medium of claim 57,
wherein each of said target objects comprises an object that conforms to behavior specified by a particular network management protocol. -
64. The memory medium of claim 57,
wherein at least one of the target objects represents a particular device connected to a network.
Specification
-
- Resources
Litigation Campaign Assessment
Thank you for your request. You will receive a custom alert email when the Litigation Campaign Assessment is available.
×
-
Current AssigneeOracle America, Inc. (Oracle Corporation)
-
Original AssigneeSun Microsystems Incorporated (Oracle Corporation)
-
InventorsVuong, Tony T., Horan, Gerard, Bapat, Subodh
-
Primary Examiner(s)KANG, PAUL H
-
Application NumberUS09/045,491Publication NumberTime in Patent Office2,356 DaysField of Search709/201, 709/102, 709/103, 709/303, 709/304, 709/223, 709/224, 709/226, 709/228, 709/202US Class Current709/223CPC Class CodesH04L 41/0213 Standardised network manage...H04L 41/046 comprising network manageme...
