Computer implemented method for removing an event registration within an event notification infrastructure

• US 8,458,725 B2
• Filed: 04/10/2006
• Issued: 06/04/2013
• Est. Priority Date: 04/10/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Surlaker, Kapil, Bhatt, Neerja
• Primary Examiner(s): Ho, Andy
• Assistant Examiner(s): Mudrick, Timothy A
• Application Number:
  US11/401,560
• Publication Number:
  US 20070240169A1
• Time in Patent Office: 2,612 Days
• Field of Search: 719/318
• US Class Current: 719/318
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A computer implemented method and system for automatically removing an event registration within an event notification infrastructure of a database system is disclosed. The method includes removing an event registration from an event queue automatically if a specified active period of time has elapsed. Further, the method includes removing an event registration from an event queue automatically if the event occurred N times where N can be specified at event registration. Also, the method includes removing an event registration from an event queue automatically if either the event occurred N times where N can be specified at event registration or a specified active period of time has elapsed. Moreover, the method includes removing an event registration from an event queue if a client explicitly requests removal of said event registration.

Claims

1. A computer implemented method for removing an event registration within an event notification infrastructure of a database system, said method comprising:

receiving a first event registration at the event notification infrastructure of the database system from a client of the database system, the first event registration comprising a plurality of parameters, the plurality of parameters include at least one parameter from the client defining a database event to be monitored by the event notification infrastructure of the database system and at least two parameters from the client defining an active period for the first event registration, the at least two parameters defining the active period including at least one parameter specifying an active period of time during which said first event registration is valid and at the end of which said first event registration automatically expires and at least one parameter defining a beginning time for the active period;

logging said event registration into an event queue of said event notification infrastructure of the database system, wherein the event queue comprises a plurality of event registration records, wherein each event registration record comprises a plurality of fields, wherein the plurality of fields comprises a field identifying a subscriber, a field identifying a name of the event registration, a field identifying a beginning time for the event registration, and at least one field identifying an active period for the event registration, and wherein logging said first event registration into the event queue comprises creating and storing a record of the plurality of records based on the parameters of the first event registration;

determining with the event notification infrastructure of the database system if said active period of time for the first event registration has elapsed; and

removing said first event registration from said event queue automatically with the event notification infrastructure of the database system if said active period of time has elapsed.

2. The method as recited in claim 1 further comprising:

receiving a second event registration at the event notification infrastructure of the database system;

logging said second event registration into said event queue of said event notification infrastructure of the database system, wherein said second event registration includes a parameter defining an active period for the second event registration, wherein the active period for the second event registration specifies that said second event registration remains valid for N occurrences of said event identified by said second event registration;

determining with the event notification infrastructure of the database system if an Nth occurrence of said event has occurred; and

removing said second event registration from said event queue automatically with the event notification infrastructure of the database system if said Nth occurrence of said event has occurred.

3. The method of claim 2, further comprising:

receiving a third event registration at the event notification infrastructure of the database system;

logging said third event registration into said event queue of said event notification infrastructure of the database system, wherein said third event registration includes a parameter defining an active period for the third event registration, wherein the active period for the third event registration specifies that said third event registration remains valid for an active period of time or N occurrences of said event identified by said third event registration;

determining with the event notification infrastructure of the database system if the active period of time has elapsed or an Nth occurrence of said event has occurred; and

removing said third event registration from said event queue automatically with the event notification infrastructure of the database system if the active period of time has elapsed or said Nth occurrence of said event has occurred.

4. The method as recited in claim 1 further comprising:

notifying the client with the event notification infrastructure of the database system when the event identified by said first event registration occurred during said active period.

5. The method as recited in claim 4 further comprising:

removing said first event registration from said event queue with the event notification infrastructure of the database system in response to a failure during said event notification.

6. The method as recited in claim 1, wherein said determining is performed by an event monitor of the database system.

7. The method as recited in claim 1 further comprising:

removing said event registration from said event queue with the event notification infrastructure of the database system if a client explicitly requests removal of said event registration.

8. The method as recited in claim 1, wherein said event registration identifies an event and wherein said event is a message being enqueued.

9. The method of claim 1, further comprising:

receiving a second event registration at the event notification infrastructure of the database system;

logging said second event registration into said event queue of said event notification infrastructure of the database system, wherein said second event registration includes a parameter defining an active period for the second event registration, wherein the active period for the second event registration specifies that said second event registration remains valid for an active period of time or N occurrences of said event identified by said second event registration;

determining with the event notification infrastructure of the database system if the active period of time has elapsed or an Nth occurrence of said event has occurred; and

removing said second event registration from said event queue automatically with the event notification infrastructure of the database system if the active period of time has elapsed or said Nth occurrence of said event has occurred.

10. A system comprising:

a processor; and

a memory coupled with and readable by the processor and storing a set of instructions which, when executed by the processor, cause the processor to remove event an registration within an event registration infrastructure if a database system by;

receiving a first event registration at the event notification infrastructure of the database system from a client of the database system, the first event registration comprising a plurality of parameters, the plurality of parameters include at least one parameter from the client defining a database event to be monitored by the event notification infrastructure of the database system and at least two parameters from the client defining an active period for the first event registration, the at least two parameters defining the active period including at least one parameter specifying an active period of time during which said first event registration is valid and at the end of which said first event registration automatically expires and at least one parameter defining a beginning time for the active period;

logging said event registration into an event queue of said event notification infrastructure of the database system, wherein the event queue comprises a plurality of event registration records, wherein each event registration record comprises a plurality of fields, wherein the plurality of fields comprises a field identifying a subscriber, a field identifying a name of the event registration, a field identifying a beginning time for the event registration, and at least one field identifying an active period for the event registration, and wherein logging said first event registration into the event queue comprises creating and storing a record of the plurality of records based on the parameters of the first event registration;

determining with the event notification infrastructure of the database system if said active period of time for the first event registration has elapsed; and

removing said first event registration from said event queue automatically with the event notification infrastructure of the database system if said active period of time has elapsed.

11. The system as recited in claim 10 further comprising:

receiving a second event registration at the event notification infrastructure of the database system;

logging said second event registration into said event queue of said event notification infrastructure of the database system, wherein said second event registration includes a parameter defining an active period for the second event registration, wherein the active period for the second event registration specifies that said second event registration remains valid for N occurrences of said event identified by said second event registration;

determining with the event notification infrastructure of the database system if an Nth occurrence of said event has occurred; and

removing said second event registration from said event queue automatically with the event notification infrastructure of the database system if said Nth occurrence of said event has occurred.

12. The system of claim 11, further comprising:

receiving a third event registration at the event notification infrastructure of the database system;

logging said third event registration into said event queue of said event notification infrastructure of the database system, wherein said third event registration includes a parameter defining an active period for the third event registration, wherein the active period for the third event registration specifies that said third event registration remains valid for an active period of time or N occurrences of said event identified by said third event registration;

determining with the event notification infrastructure of the database system if the active period of time has elapsed or an Nth occurrence of said event has occurred; and

removing said third event registration from said event queue automatically with the event notification infrastructure of the database system if the active period of time has elapsed or said Nth occurrence of said event has occurred.

13. The system as recited in claim 10 further comprising:

notifying the client with the event notification infrastructure of the database system when the event identified by said first event registration occurred during said active period.

14. The system as recited in claim 13 further comprising:

removing said first event registration from said event queue with the event notification infrastructure of the database system in response to a failure during said event notification.

15. The system as recited in claim 10, wherein said determining is performed by an event monitor of the database system.

16. The system as recited in claim 10 further comprising:

removing said event registration from said event queue with the event notification infrastructure of the database system if a client explicitly requests removal of said event registration.

17. The system as recited in claim 10, wherein said event registration identifies an event and wherein said event is a message being enqueued.

18. The system of claim 10, further comprising:

receiving a second event registration at the event notification infrastructure of the database system;

logging said second event registration into said event queue of said event notification infrastructure of the database system, wherein said second event registration includes a parameter defining an active period for the second event registration, wherein the active period for the second event registration specifies that said second event registration remains valid for an active period of time or N occurrences of said event identified by said second event registration;

determining with the event notification infrastructure of the database system if the active period of time has elapsed or an Nth occurrence of said event has occurred; and

removing said second event registration from said event queue automatically with the event notification infrastructure of the database system if the active period of time has elapsed or said Nth occurrence of said event has occurred.

19. A computer-readable memory storing a set of instructions which, when executed by a processor, cause the processor to remove event an registration within an event registration infrastructure if a database system by:

receiving a first event registration at the event notification infrastructure of the database system from a client of the database system, the first event registration comprising a plurality of parameters, the plurality of parameters include at least one parameter from the client defining a database event to be monitored by the event notification infrastructure of the database system and at least two parameters from the client defining an active period for the first event registration, the at least two parameters defining the active period including at least one parameter specifying an active period of time during which said first event registration is valid and at the end of which said first event registration automatically expires and at least one parameter defining a beginning time for the active period;

logging said event registration into an event queue of said event notification infrastructure of the database system, wherein the event queue comprises a plurality of event registration records, wherein each event registration record comprises a plurality of fields, wherein the plurality of fields comprises a field identifying a subscriber, a field identifying a name of the event registration, a field identifying a beginning time for the event registration, and at least one field identifying an active period for the event registration, and wherein logging said first event registration into the event queue comprises creating and storing a record of the plurality of records based on the parameters of the first event registration;

determining with the event notification infrastructure of the database system if said active period of time for the first event registration has elapsed; and

removing said first event registration from said event queue automatically with the event notification infrastructure of the database system if said active period of time has elapsed.

20. The computer-readable memory as recited in claim 19 further comprising:

receiving a second event registration at the event notification infrastructure of the database system;

logging said second event registration into said event queue of said event notification infrastructure of the database system, wherein said second event registration includes a parameter defining an active period for the second event registration, wherein the active period for the second event registration specifies that said second event registration remains valid for N occurrences of said event identified by said second event registration;

determining with the event notification infrastructure of the database system if an Nth occurrence of said event has occurred; and

removing said second event registration from said event queue automatically with the event notification infrastructure of the database system if said Nth occurrence of said event has occurred.

21. The computer-readable memory of claim 20, further comprising:

receiving a third event registration at the event notification infrastructure of the database system;

logging said third event registration into said event queue of said event notification infrastructure of the database system, wherein said third event registration includes a parameter defining an active period for the third event registration, wherein the active period for the third event registration specifies that said third event registration remains valid for an active period of time or N occurrences of said event identified by said third event registration;

determining with the event notification infrastructure of the database system if the active period of time has elapsed or an Nth occurrence of said event has occurred; and

removing said third event registration from said event queue automatically with the event notification infrastructure of the database system if the active period of time has elapsed or said Nth occurrence of said event has occurred.

22. The computer-readable memory as recited in claim 19 further comprising:

notifying the client with the event notification infrastructure of the database system when the event identified by said first event registration occurred during said active period.

23. The computer-readable memory as recited in claim 22 further comprising:

removing said first event registration from said event queue with the event notification infrastructure of the database system in response to a failure during said event notification.

24. The computer-readable memory as recited in claim 19, wherein said determining is performed by an event monitor of the database system.

25. The computer-readable memory as recited in claim 19 further comprising:

removing said event registration from said event queue with the event notification infrastructure of the database system if a client explicitly requests removal of said event registration.

26. The computer-readable memory as recited in claim 19, wherein said event registration identifies an event and wherein said event is a message being enqueued.

27. The computer-readable memory of claim 19, further comprising:

receiving a second event registration at the event notification infrastructure of the database system;

logging said second event registration into said event queue of said event notification infrastructure of the database system, wherein said second event registration includes a parameter defining an active period for the second event registration, wherein the active period for the second event registration specifies that said second event registration remains valid for an active period of time or N occurrences of said event identified by said second event registration;

determining with the event notification infrastructure of the database system if the active period of time has elapsed or an Nth occurrence of said event has occurred; and

removing said second event registration from said event queue automatically with the event notification infrastructure of the database system if the active period of time has elapsed or said Nth occurrence of said event has occurred.