High availability event topic

• US 20040078440A1
• Filed: 11/13/2002
• Published: 04/22/2004
• Est. Priority Date: 05/01/2002
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Upton, Mitch, Golding, Christa, Potter, Tim
• Application Number:
  US10/293,674
• Publication Number:
  US 20040078440A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Events are delivered to multiple topic subscribers using a single distributed event topic. An event generator can receive data for the event from an EIS and can generate an event object. An event queue stores the event object until the event is retrieved by an event processor, which publishes the event to each destination. One of these destinations, the distributed event topic, receives the published event from the event processor and handles the delivery of the event to any user subscribing to the event topic. Each subscriber can utilize a remote application view to invoke system functions in the EIS and receive messages from the information system on behalf of the subscriber. A user event queue can be used for each topic subscriber to store an event until the subscriber is capable of receiving the event.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system for distributing messages to topic subscribers, comprising:

a distributed event topic adapted to handle the delivery of an event to any user subscribing to the event topic; and

an event processor, the event processor adapted to receive an event from an information system and publish the event to the distributed event topic.

2. A system according to claim 1, wherein:

said distributed event topic is a JMS topic.

3. A system according to claim 1, further comprising:

at least one remote application view, each remote application view adapted to invoke system functions in the information system and receive messages from the information system on behalf of a topic subscriber.

4. A system according to claim 3, further comprising:

a remote listener for each remote application view, the remote listener adapted to listen for events on the distributed event topic.

5. A system according to claim 3, further comprising:

an event context class for each application view, the event context class establishing a connection with the distributed event topic.

6. A system according to claim 5, wherein:

said event context class further filters the events for an application view.

7. A system according to claim 1, wherein:

said distributed event topic further supports durable subscriptions.

8. A system according to claim 1, further comprising:

a client application capable of subscribing to the distributed event topic.

9. A system according to claim 1, further comprising:

an information system adapted to generate data for an event.

10. A system according to claim 1, further comprising:

an event queue adapted to store the event until the event is retrieved by the event processor.

11. A system according to claim 1, further comprising:

a user event queue for storing an event delivered by the distributed event topic for a user until that user is able to receive the event.

12. A system according to claim 1, wherein:

said event processor is implemented as a message-driven Enterprise JavaBean.

13. A system according to claim 1, wherein:

said distributed event topic delivers the event transactionally to allow the event to be rolled back.

14. A system according to claim 1, wherein:

said distributed event topic delivers the event to every topic subscriber in a single transaction.

15. A system according to claim 10, wherein:

said event queue is distributed across a cluster.

16. A system according to claim 1, further comprising:

an event generator adapted to receive data for the event from the information system and generate an event object to be received by the event processor.

17. A system for distributing an event to event topic subscribers, comprising:

an event generator adapted to receive data for the event from an information system and generate an event object;

an event queue for storing the event object until the event is retrieved;

an event processor adapted to receive the event object from the event queue and publish the event contained in the event object; and

a distributed event topic adapted to receive the published event and handle the delivery of the event to any user subscribing to the event topic.

18. A method for distributing an event to event topic subscribers, comprising:

receiving data for the event from an information system and generating an event object;

storing the event object in an event object queue;

retrieving the event object from the event queue and publishing the event contained in the event object; and

receiving the published event to a single distributed event topic and delivering the event to any user subscribing to the event topic.

19. A method according to claim 18, further comprising:

invoking system functions in the information system and receiving messages from the information system on behalf of a topic subscriber using an application view.

20. A method according to claim 18, further comprising:

listening for events on the distributed event topic using a remote listener for every topic subscriber.

21. A method according to claim 18, further comprising:

establishing a connection with the distributed event topic using an event context class for each topic subscriber.

22. A method according to claim 18, further comprising:

filtering events using an event context class for each topic subscriber.

23. A method according to claim 18, further comprising:

storing an event delivered by the distributed event topic in a user event queue for a topic subscriber until that subscriber is able to receive the event.

24. A computer-readable medium, comprising:

means for receiving data for the event from an information system and generating an event object;

means for storing the event object in an event object queue;

means for retrieving the event object from the event queue and publishing the event contained in the event object; and

means for receiving the published event to a single distributed event topic and delivering the event to any user subscribing to the event topic.

25. A computer program product for execution by a server computer for distributing an event to event topic subscribers, comprising:

computer code for receiving data for the event from an information system and generating an event object;

computer code for storing the event object in an event object queue;

computer code for retrieving the event object from the event queue and publishing the event contained in the event object; and

computer code for receiving the published event to a single distributed event topic and delivering the event to any user subscribing to the event topic.

26. A system for distributing an event to event topic subscribers, comprising:

means for receiving data for the event from an information system and generating an event object;

means for storing the event object in an event object queue;

means for retrieving the event object from the event queue and publishing the event contained in the event object; and

means for receiving the published event to a single distributed event topic and delivering the event to any user subscribing to the event topic.

27. A computer system comprising:

a processor;

object code executed by said processor, said object code configured to;

receive data for the event from an information system and generate an event object;

store the event object in an event object queue;

retrieve the event object from the event queue and publish the event contained in the event object; and

receive the published event to a single distributed event topic and deliver the event to any user subscribing to the event topic.

28. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to receive data for the event from an information system and generate an event object;

a code segment including instructions to store the event object in an event object queue;

a code segment including instructions to retrieve the event object from the event queue and publish the event contained in the event object; and

a code segment including instructions to receive the published event to a single distributed event topic and deliver the event to any user subscribing to the event topic.