Computer implemented method for transforming an event notification within a database notification infrastructure

• US 9,390,118 B2
• Filed: 04/19/2006
• Issued: 07/12/2016
• Est. Priority Date: 04/19/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Surlaker, Kapil, Mishra, Shailendra
• Primary Examiner(s): HARPER, ELIYAH STONE
• Application Number:
  US11/408,195
• Publication Number:
  US 20070250545A1
• Time in Patent Office: 3,737 Days
• Field of Search: 707/104.1, 707/100, 707/10, 707/200, 707/951
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

A computer implemented method for automatically transforming an event notification within a database notification infrastructure based on client specified formatting and/or editing procedures. The method includes transforming the event notification having a format compatible with a database using a client specific format conversion procedure into a client-compatible event notification format. Further, the method may include transforming the payload portion of the event notification having a format compatible with a database using a client specific format conversion procedure into a linear event notification format. Moreover, the method may include transforming the event notification using a client specific editing procedure. The client specified procedures may be specified during event registration by the client. The transformed and/or edited event notifications may be forwarded to the client.

Claims

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

receiving information at the database notification infrastructure of the database system that identifies at least one function of a database associated with the database system as a database event to be monitored, said database event being triggered in response to performance of the at least one function by the database associated with the database system;

logging an event registration into an event queue of said database notification infrastructure of the database system based on information received at a time of the event registration indicative of both one or more client-specific format conversion procedures and one or more client-specific editing procedures, wherein the one or more client-specific format conversion procedures and the one or more client-specific editing procedures are stored on the database notification infrastructure;

receiving an event notification generated by the database system in response to monitoring occurrence of said database event within the database system identified by said event registration, said event notification having an event notification format that is compatible with said database system;

editing said event notification in response to triggering at least one of the one or more stored client-specific editing procedures specified at the time of said event registration using the database notification infrastructure of the database system, said edited event notification including information excluded from the unedited event notification, excluding information included in the unedited event notification, or both;

transforming said edited event notification between said event notification format compatible with said database system and an client-compatible event notification format indicative of a format in which a client-compatible event notification is to be delivered to a client subscribed to said event registration in response to triggering at least one of the one or more stored client-specific format conversion procedures specified at the time of said event registration using the database notification infrastructure of the database system, wherein said transformed event notification includes the same information as the edited event notification and has a format different than that compatible with the database system; and

delivering said transformed event notification to said client.

2. The method as recited in claim 1, wherein said event registration also specifies a client-specific event notification delivery mechanism and wherein said delivering uses said delivery mechanism.

3. The method as recited in claim 2, wherein said delivery mechanism is selected from the group comprising:

electronic mail;

http;

delivery over a network to a user specified host and port; and

invocation of a stored PL/SQL procedure.

4. The method as recited in claim 1, wherein said delivering does not require said client to be logged into said database system.

5. The method as recited in claim 1, wherein said client-compatible event notification format is a linear format.

6. The method as recited in claim 5, wherein said linear format is selected from the group comprising:

text;

HTML; and

XML.

7. The method as recited in claim 1, wherein said format compatible with said database system is an ADT event notification format.

8. The method as recited in claim 1, wherein said event registration specifies the one or more client-specific format conversion procedures to be stored on the database notification infrastructure.

28. The method of claim 1, wherein said database event comprises an event notification being published for a subscriber.

29. The method of claim 1, wherein said database event comprises a database starting or stopping.

30. The method of claim 1, wherein said database event comprises a change in a database object.

31. The method of claim 1, wherein said database event comprises a change of data stored in the database.

9. A computer implemented method for processing an event notification within a database notification infrastructure of a database system, said method comprising:

receiving information at the database notification infrastructure of the database system that identifies at least one function of a database associated with the database system as a database event to be monitored, said database event being triggered in response to performance of the at least one function by the database associated with the database system;

logging an event registration into an event queue of said database notification infrastructure of the database system based on information received at a time of the event registration indicative of both a linear event notification format in which event notifications should be delivered to a client and one or more client-specific editing procedures, wherein the linear event notification format and the one or more client-specific editing procedures are stored on the database notification infrastructure;

receiving an event notification generated by the database system at said database notification infrastructure in response to monitoring occurrence of said database event within the database system identified by said event registration, said event notification having an event notification format that is compatible with said database system;

editing said event notification in response to triggering at least one of the one or more client-specific editing procedure stored using the database notification infrastructure of the database system in association with said linear event notification format, said edited payload portion including information excluded from the unedited event notification, excluding information included in the unedited event notification, or both;

transforming said edited payload portion of said event notification between the format compatible with said database system and said linear format in response to triggering at least one of the one or more client-specific format conversion procedure specified at the time of said event registration using the database notification infrastructure of the database system, wherein said transformed payload portion includes the same information as the payload portion of said edited event notification and has a format different than that compatible with the database system; and

delivering an event notification with said transformed payload in said linear format to said client.

10. The method as recited in claim 9 wherein said delivering uses a client specific event notification delivery mechanism and wherein said event registration also specifies said client-specific event notification delivery mechanism.

11. The method as recited in claim 10, wherein said delivery mechanism is selected from the group comprising:

electronic mail;

http;

delivery over a network to a user specified host and port; and

invocation of a stored PL/SQL procedure.

12. The method as recited in claim 10, wherein said delivering does not require said client to be logged into said database system.

13. The method as recited in claim 9, wherein said linear format is selected from the group comprising:

text;

HTML; and

XML.

14. The method as recited in claim 9, wherein said event notification having a format compatible with said database system is an ADT event notification.

15. The method as recited in claim 9, wherein said event registration also specifies said client-specific format conversion procedure to be stored on the database notification infrastructure.

16. A system comprising:

a processor; and

a memory configured to store a set of instructions that when executed by the processor configure the processor to;

receive information that identifies at least on function of a database as a database event to be monitored within a database system;

register the database event based on information received at a time of an event registration indicative of both one or more client-specific format conversion procedures and one or more client-specific editing procedures, wherein the one or more client-specific format conversion procedures and the one or more client-specific editing procedures are stored on the database notification infrastructure

store the one or more client-specific editing procedures and the one or more client-specific format conversion procedures as stored database procedures;

receive an event notification in response to monitoring occurrence of said database event, said event notification having a format compatible with said database system;

edit said event notification in response to triggering at least one of the one or more client-specific editing procedures specified at the time of said event registration, said edited event notification including information excluded from the unedited event notification, excluding information included in the unedited event notification, or both; and

transform said edited event notification into a client compatible event notification using at least one of the one or more client-specific format conversion procedure specified at the time of said event registration, said client compatible event notification including the same information as the edited event notification and having a format different than that compatible with the database system; and

deliver said client compatible event notification to said client.

17. The system as recited in claim 16, wherein said event registration also specifies a client-specific event notification delivery mechanism, and wherein said delivering uses said client specific event notification delivery mechanism.

18. The system as recited in claim 17, wherein said client specific event notification delivery mechanism is selected from the group comprising:

electronic mail;

http;

delivery over a network to a user specified host and port; and

invocation of a stored PL/SQL procedure.

19. The system as recited in claim 16, wherein said delivering does not require said client to be logged into said database system.

20. A non-transitory computer readable medium having stored therein instructions that when executed by a processor implement a method of processing an event notification within an event notification infrastructure of a database system, non-transitory computer-readable medium comprising:

instructions configured for receiving information at the database notification infrastructure of the database system that identifies at least one function of a database associated with the database system as a database event to be monitored, said database event being triggered in response to performance of the at least one function by the database associated with the database system;

instructions configured for logging event registration into an event queue of said database notification infrastructure of the database system based on information received at a time of the event registration indicative of both one or more client-specific format conversion procedures and one or more client-specific editing procedures, wherein the one or more client-specific format conversion procedures and the one or more client-specific editing procedures are stored on the database notification infrastructure;

instructions configured for receiving an event notification generated by the database system in response to monitoring occurrence of said database event within the database system identified by said event registration, said event notification having an event notification format that is compatible with said database system;

instructions configured for editing said event notification in response to triggering at least one of the one or more stored client-specific editing procedures specified at the time of said event registration using the database notification infrastructure of the database system, said edited event notification including information excluded from the unedited event notification, excluding information included in the unedited event notification, or both;

instructions configured for transforming said edited event notification between said event notification format compatible with said database system and a client-compatible event notification format indicative of a format in which a client-compatible event notification is to be delivered to a client subscribed to said event registration in response to triggering at least one of the one or more stored client-specific format conversion procedures specified at the time of said event registration using the database notification infrastructure of the database system, wherein said transformed event notification includes the same information as the edited event notification and has a format different than that compatible with the database system; and

instructions configured for delivering said transformed event notification to said client.

21. The non-transitory computer readable medium as recited in claim 20, wherein said event registration also specifies a client-specific event notification delivery mechanism and wherein said delivery uses said delivery mechanism.

22. The non-transitory computer readable medium as recited in claim 21, wherein said delivery mechanism is selected from the group comprising:

electronic mail;

http;

delivery over a network to a user specified host and port; and

invocation of a stored PL/SQL procedure.

23. The non-transitory computer readable medium as recited in claim 20, wherein said delivering does not require said client to be logged into said database notification infrastructure.

24. The non-transitory computer readable medium as recited in claim 20, wherein said client-compatible event notification format is a linear format.

25. The non-transitory computer readable medium as recited in claim 24, wherein said linear format is selected from the group comprising:

text;

HTML; and

XML.

26. The non-transitory computer readable medium as recited in claim 20, wherein said format compatible with said database system is an ADT format.

27. The non-transitory computer readable medium as recited in claim 20, wherein said event registration also specifies said format conversion procedure.