Cluster event service method and system

• US 7,500,249 B2
• Filed: 05/02/2001
• Issued: 03/03/2009
• Est. Priority Date: 05/02/2000
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Herrmann, Frederic, Kampe, Mark A., Fernandez, Ludovic Christophe
• Primary Examiner(s): Ho; Andy
• Application Number:
  US09/846,254
• Publication Number:
  US 20020016867A1
• Time in Patent Office: 2,862 Days
• Field of Search: 719/318
• US Class Current: 719/318
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 41/0618 based on the physical or logical position
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks

Abstract

A network having a plurality of nodes is disclosed. The network includes an event channel adapted to transmit an event between a publisher node and a subscriber node within the network. The network also includes a filter to identify the event on the subscriber node. The network also includes an application on the subscriber node to receive the event according to the filter.

Claims

1. A network having a plurality of nodes connected by a digital data communication link, comprising:

an event channel adapted to transfer an event between a publisher node and a subscriber node within said network over the communication link;

a filter on said subscriber node to process a plurality of events published on said event channel to identify said event as a matching event, wherein said matching event includes at least one pattern field that matches a filter field within said filter; and

an application on said subscriber node to receive said matching event, wherein said application defines said filter and said filter field and opens said event channel at said subscriber node.

2. The network of claim 1, further comprising an event server on said subscriber node, said event server adapted to receive said event and to pass said received event to said filter from said event channel.

3. The network of claim 2, wherein said event server exchanges information with another event server on another one of the nodes of the network.

4. The network of claim 2, wherein said application opens said event channel through said event server.

5. The network of claim 2, wherein said publisher node has a configuration, said configuration being known to said event server on said subscriber node.

6. The network of claim 1, wherein said event further includes a data field.

7. The network of claim 1, wherein said event channel has a unique name.

8. The network of claim 7, wherein said unique name is registered in a naming service within said network.

9. The network of claim 1, further comprising an event server on said publisher node, wherein said event server publishes said event on said event channel.

10. The network of claim 9, wherein said subscriber node has a configuration, said configuration being known to said event server on said publisher node.

11. The network of claim 1, further comprising a plurality of additional publishers nodes linked to the event channel transferring publishing events on the event channel and a plurality of additional subscriber nodes linked to the event channel, each of the additional subscriber nodes comprising a filter defined by an application on the additional subscriber node with filter fields for use in processing said published events to identify matching events based on the filter fields.

12. A node within a network to exchange information, comprising:

an application running on the node;

an event server adapted to receive events from an event channel on a communication link, wherein said event server includes an event control block to subscribe to said event channel for said application; and

a filter to identify matching ones of said events for use by said application, wherein said filter is assigned by said application, said event includes at least one pattern field, said at least one pattern field matches at least one filter field within said filter, and said event is placed in a queue on said node by said event server prior to the use by said application.

13. The node of claim 12, wherein said event server further includes an event control manager to control said event control block.

14. The node of claim 13, wherein said event control manager updates said event control block.

15. The node of claim 13, wherein said event control manager detects an overload condition within said event control block.

16. The node of claim 13, wherein said event control manager controls a configuration of said event control block.

17. The node of claim 12, wherein said event server further includes an event protocol module to manage network connections to said event control block.

18. The node of claim 12, wherein said event control block includes a remote event control block that correlates to an event control block.

19. The node of claim 12, wherein said event server includes an event channel descriptor to access said event control block for said client application.

20. The node of claim 12, further comprising an event application program interface to publish and subscribe to said event channel.

21. The node of claim 12, wherein said event is processed by said application.

22. A method for receiving information at a node, comprising:

opening an event channel at said node, said event channel providing a shared communication path on a digital data communication link with other nodes;

subscribing to receive events at the node over the event channel;

with an application running on the node, assigning a filter to said event channel by said application;

receiving an event on said event channel;

processing said event at said node by said filter to determine whether the received event is a match according to said filter; and

when determined a match, passing the received event to the application on the node.

23. The method of claim 22, further comprising registering a function indicating said opened event channel.

24. The method of claim 22, further comprising publishing said event on said event channel.

25. The method of claim 22, further comprising dispatching a callback responding to said event.

26. The method of claim 22, further comprising creating said event channel by operation of an event server running on the node.

27. The method of claim 22, further comprising filtering said event by said filter.

28. The method of claim 27, wherein said filtering includes matching a pattern within said event with a filter pattern within said filter.

29. The method of claim 22, further comprising storing said event at an event control block.

30. The method of claim 22, wherein said subscribing includes invoking an event control block.

31. A method for receiving information at a node, comprising:

opening an event channel with a client application running on said node, the client application opening said event channel in a write mode or a read mode, wherein the client application can publish events over the event channel in said write mode and can receive events published on the event channel in said read mode;

receiving an event from said event channel at said node;

assigning a filter to said event channel by said client application running on said node;

filtering said event from said event channel with said filter at said node by determine whether the received event is a match according to said filter; and

when determined a match, passing the received event to the client application on the node.

32. The method of claim 31, further comprising queuing said event in an event control block at said node corresponding to said application.

33. The method of claim 31, further comprising dropping said event during an overload condition at said node.