MANAGING DATABASE AGENTS

• US 20090259692A1
• Filed: 04/11/2008
• Published: 10/15/2009
• Est. Priority Date: 04/11/2008
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bangel, Matthew J., Murray, Douglas G., Martin, James A. JR.
• Application Number:
  US12/101,518
• Publication Number:
  US 20090259692A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24553 of query operations
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries

Abstract

Aspects of the present invention provide a solution for managing database agents. Specifically, an embodiment of the present invention produces a predetermined number of replica databases for running the agents. Agent scheduling documents are produced and parsed to determine on which database the agent should be run and on which database the agent should run if the first choice of databases is not functioning. The agent scheduling documents also specify whether running of a specific agent has certain prerequisites, such as a time constraint and/or whether its running is dependent upon successful completion of another agent.

Claims

1. A system for managing database agents, comprising:

a database replicator for producing a number of replica databases based on an original database;

an agent scheduling document that includes;

an identifier for an agent to be scheduled;

a primary database upon which the agent is to be run, the primary database being at least one of the original database or one of the replica databases; and

a prerequisite that must be satisfied before the agent is run; and

a scheduling server, including a parser for parsing the agent scheduling document, the parser, for the agent scheduling document;

determining, based on the prerequisite, whether the agent specified by the identifier is ready to be run, and;

in case that a determination is made that the agent is ready to be run, forwarding the agent for running on the primary database.

2. The system of claim 1, the agent scheduling document further including:

a secondary database upon which the agent is to be run that is different from the primary database,

wherein the parser, for the scheduling document;

determines whether the primary database of the agent scheduling document is operational, and;

in case that a determination is made that the primary database is non-operational, forwarding the agent for running on one of the secondary database.

3. The system of claim 1, wherein the scheduling document further includes a time after which the agent is to run and wherein the parser further makes a determination whether the time has past and runs the agent based on a positive determination.

4. The system of claim 1, wherein the scheduling document further includes a prerequisite agent that must be run prior to running of the agent and wherein the parser further makes a determination whether the prerequisite agent has run and runs the agent based on a positive determination.

5. The system of claim 1, further comprising a notification component for notifying an appropriate party in case that a determination is made that the primary database is non-operational.

6. The system of claim 1, further comprising a backup scheduling server being an identical replica of the scheduling server.

7. The system of claim 1, wherein the scheduling server controls execution of all agents on the system.

8. A method for providing for management of database agents, comprising:

producing a number of replica databases based on an original database;

providing an agent scheduling document that includes;

an identifier for an agent to be scheduled;

a primary database upon which the agent is to be run, the primary database being at least one of the original database or one of the replica databases; and

a prerequisite that must be satisfied before the agent is run;

parsing an agent scheduling document via a scheduling server, by, for the agent scheduling document determining, based on the prerequisite, whether the agent specified by the identifier is ready to be run, and;

in case that a determination is made that the agent is ready to be run, forwarding the agent for running on the primary database.

9. The method of claim 8, the agent scheduling document further including:

a secondary database upon which the agent is to be run that is different from the primary database,

wherein the parsing, for the agent scheduling document, further includes;

determining whether the primary database of the agent scheduling document is operational, and;

in case that a determination is made that the primary database is non-operational, forwarding the agent for running on one of the secondary database.

10. The method of claim 8, wherein the prerequisite includes a time after which the agent is to run and wherein the parsing further determines whether the time has past and runs the agent based on a positive determination.

11. The method of claim 8, wherein prerequisite includes a prerequisite agent that must be run prior to running of the agent and wherein the parsing further includes making a determination whether the prerequisite agent has run and running the agent based on a positive determination.

12. The method of claim 8, further comprising notifying an appropriate party in case that a determination is made that the primary database is non-operational.

13. The method of claim 8, further comprising providing a backup scheduling server being an identical replica of the scheduling server, wherein the scheduling server and backup scheduling server control execution of all agents on the system.

14. A program product stored on a computer readable for providing for maintaining database agents, comprising:

program code for producing a predetermined number of replica databases based on an original database;

program code for providing an agent scheduling document that includes;

an identifier for an agent to be scheduled;

a primary database upon which the agent is to be run, the primary database being at least one of the original database or one of the replica databases; and

a prerequisite that must be satisfied before the agent is run;

program code for parsing an agent scheduling documents in a scheduling server, by, for the agent scheduling document, determining, based on the prerequisite, whether the agent specified by the identifier is ready to be run, and;

in case that a determination is made that the agent is ready to be run, program code for forwarding the agent for running on the primary database.

15. The program product of claim 14, the agent scheduling document further including:

a secondary database upon which the agent is to be run that is different from the primary database,

wherein the program code for parsing, for the agent scheduling document, further includes;

program code for determining whether the primary database of the agent scheduling document is operational, and;

in case that a determination is made that the primary database is non-operational, program code for forwarding the agent for running on one of the secondary database.

16. The program product of claim 14, wherein the prerequisite includes a time after which the agent is to run and wherein the program code for parsing further makes a determination whether the time has past and runs the agent based on a positive determination.

17. The program product of claim 14, wherein the prerequisite includes a prerequisite agent that must be run prior to running of the agent and wherein the program code for parsing further makes a determination whether the prerequisite agent has run and runs the agent based on a positive determination.

18. The program product of claim 14, further comprising program code for notifying an appropriate party in case that a determination is made that the primary database is non-operational.

19. The program product of claim 14, wherein the scheduling server comprises a plurality of duplicate the scheduling servers, and wherein the scheduling server controls execution of all agents on the system.

20. A method for deploying an application for managing database agents, comprising:

providing a computer infrastructure being operable to;

produce a predetermined number of replica databases based on an original database;

provide an agent scheduling document that includes;

an identifier for an agent to be scheduled;

a primary database upon which the agent is to be run, the primary database being at least one of the original database or one of the replica databases; and

a prerequisite that must be satisfied before the agent is run;

provide a scheduling server to parse a plurality of agent scheduling documents, by, for every agent scheduling document determining, based on the prerequisite, whether the agent specified by the identifier is ready to be run, and;

in case that a determination is made that the agent is ready to be run, forward the agent for running on the primary database.

21. The method of claim 20, the agent scheduling document further including:

a secondary database upon which the agent is to be run that is different from the primary database,

wherein the parsing, for the agent scheduling document, further includes;

determining whether the primary database of the agent scheduling document is operational, and;

in case that a determination is made that the primary database is non-operational, forwarding the agent for running on one of the secondary database.

22. The method of claim 20, wherein the prerequisite includes a time after which the agent is to run and wherein the parser further makes a determination whether the time has past and runs the agent based on a positive determination, and wherein the prerequisite further includes a prerequisite agent that must be run prior to running of the agent and wherein the parser further makes a determination whether the prerequisite agent has run and runs the agent based on a positive determination.