Computer database access

The present invention relates generally to the operation of computer systems and networks and more specifically to accessing databases associated with computer systems and networks.

In the operation of computer systems and networks, it is often desirable to access databases that are not accessible via the existing uses of widely used standardized database access methods and systems, e.g., Simple Network Management Protocol (“SNMP”); the Telnet protocol; and various World Wide Web browsers such as Microsoft Corp.'s INTERNET EXPLORER® and Netscape Communication Corp.'s NETSCAPE®. For example, a network device such as a print server may be associated with a database containing data concerning the print server and/or its software, where the database is restricted, e.g., for proprietary or security reasons, from access by normally used standardized database access methods and systems.

One prior method of accessing data makes use of the provision by typical databases of record-based abstraction where there is a correlation of one unique index per record. Such databases may be queried using conditional search criteria. However, it is often desirable to work with devices such as the print server in the example above, for instance, to test such devices, in part by accessing restricted data. If the data sought is restricted by, for example, not being abstracted such that a conditional search will detect it, this prior method will not be able to access the data sought.

Systems and methods are disclosed for accessing databases associated with computer systems and networks.

The present invention provides systems and methods for the access of data in databases that may be otherwise inaccessible.

FIG. 1 is a flowchart showing an embodiment of the invention;

FIG. 2 is a flowchart showing another embodiment of the invention; and

FIG. 3 is a block diagram showing another embodiment of the invention.

Broadly stated, the present invention is directed to systems and methods for use of a unique identifier in a restricted intermediate database, where the restricted intermediate database can be used to store a group of objects pertaining to a database of interest to provide access to any record in the database of interest.

Turning now to FIG. 1 , showing a flowchart of an embodiment of the invention, a management application creates an object for indicating a unique identifier that identifies a data item ( 10 ). The management application may be but is not limited to a management application used in Simple Network Management Protocol (“SNMP”). The data item may be but is not limited to a data item that is stored in, or is to be stored in, a restricted database of interest, i.e., a database to which access is unavailable via existing methods of using standardized access systems, e.g., SNMP; the Telnet protocol; and various World Wide Web browsers such as Microsoft Corp.'s INTERNET EXPLORER® and Netscape Communication Corp.'s NETSCAPE®. The unique identifier may be but is not limited to an index entry or key that is unique to a particular data item and that is available for use in a restricted intermediate database by an embodiment of the invention. An agent stores the unique identifier in the restricted intermediate database ( 12 ). The agent may be but is not limited to an agent used in SNMP. The management application creates an object for indicating the data type of the data item, e.g., numerical value or string ( 14 ). The agent stores the data type of the data item in the restricted intermediate database ( 16 ). The management application creates an object for indicating an action to be performed on the data item with respect to the database of interest, e.g., retrieval of the data item from the database of interest, addition of the data item to the database of interest, or use of the data item to change data in the database of interest ( 18 ). Hereinafter, and in FIGS. 1 and 2 , “storing the data item in the database of interest” and like phrases encompass adding the data item to the database of interest and using the data item to change data in the database of interest. The agent issues a command to perform the action ( 20 ). The agent receives a response to the command ( 22 ). The agent sends the response to the management application ( 24 ).

Turning now to FIG. 2 , showing a flowchart for another embodiment of the invention, steps 10 , 12 , 14 , 16 , 18 , and 20 are as described above in reference to FIG. 1 . After an agent issues a command to perform an action on a data item with respect to the database of interest ( 20 ), the management application determines if the action requires that the data item be stored in the database ( 26 ).

If the action does not require that the data item be stored in the database of interest, the management application creates an object for indicating a GET command to retrieve the data item from the database of interest ( 28 ). The agent issues the GET command ( 30 ).

If the action requires that the data item be stored in the database of interest, the management application creates an object for indicating the actual value of the data item to be stored in the database of interest ( 32 ). The management application creates an object for indicating a SET command to store the data item in the database of interest ( 34 ). The agent issues the appropriate SET command ( 36 ).

The issuing of the GET command ( 30 ) or the issuing of the SET command ( 36 ) may result in an error message signaling the failure of the either of the commands ( 38 ). If the issuing of the GET command ( 30 ) or the issuing of the SET command ( 36 ) produces an error message, the agent receives the error message as a response ( 42 ). If issuing of the GET command ( 30 ) or the issuing of the SET command ( 36 ) is successful, the agent receives the data item that has been stored (if a SET command was issued) or retrieved (if a GET command was issued) as a response ( 40 ). In either case, receiving the data item ( 40 ) or receiving an error massage ( 42 ), the agent sends the response to the management application ( 24 ) as previously described with reference to FIG. 1 .

Turning now to FIG. 3 , showing a block diagram of another embodiment of the invention, a first network device 44 is operatively coupled to a second network device (not shown), and an agent software program 46 is programmed to monitor the second network device. First network device 44 is programmed to create a first object for indicating a unique identifier for a data item, to create a second object for indicating a data type for the data item, to create a third object for indicating an action to be performed on the data item with respect to the database of interest 48 , and to receive a response to an action command to perform an action on the data item with respect to the database of interest 48 . Agent 46 is programmed to store the unique identifier in restricted intermediate database 50 , to store the data type in restricted intermediate database 50 , to issue the action command, to receive the response, and to send the response to the first network device.

While embodiments of the invention are useful in accessing restricted databases, the embodiments are not limited to such restricted databases.

It is apparent to those of ordinary skill in the art that various embodiments of the inventions may be implemented through the use of a variety of tools, including but not limited to SNMP; the Telnet protocol; and various World Wide Web browsers such as Microsoft Corp.'s INTERNET EXPLORER® and Netscape Communication Corp.'s NETSCAPE®. It is further apparent to those of ordinary skill in the art that steps presented herein in embodiments of the invention may be near-simultaneous, or in an order other than that presented herein, depending, among other things, on the tools used and the circumstances of use.

While various embodiments of the present invention have been shown and described, it should be understood that other modifications, substitutions, and alternatives are apparent to one of ordinary skill in the art. Such modifications, substitutions, and alternatives can be made without departing from the spirit and scope of the invention, which should be determined from the appended claims.

Various features of the present invention are set forth in the appended claims.