Database network connectivity product

• US 5,873,084 A
• Filed: 01/18/1996
• Issued: 02/16/1999
• Est. Priority Date: 01/18/1996
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Bracho, Rafael, Sporkert, Tilman
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US08/588,142
• Time in Patent Office: 1,125 Days
• Field of Search: 395/610, 395/800, 395/500, 395/650, 395/200, 395/200.31, 395/200.61, 364/200, 364/401, 707/10
• US Class Current: 1/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A method and apparatus for publishing and receiving events to a network. A plurality of "publisher" entities publish information and a plurality of "subscriber" entities request and use the information. Publishers and subscribers are connected to each other through a network. The network is a "store and forward" network whose routing is "content-based." The basic quanta of information is called an "event." Publishers publish events and subscribers subscribe to events that match criteria defined by the subscriber. Publication and subscription are performed asynchronously. Publishers and subscribers do not have direct knowledge of each other. The system receives a published event from a publisher and routes the event to all appropriate subscribers. Each subscriber is guaranteed to receive all events published on the system if, and only if, they match the subscription criteria specified by the subscriber. A legacy data base can be added to the network by way of a data base connector, which can be a publisher, a subscriber, or both.

Claims

1. A method of connecting a data base to a publisher/subscriber network, so that the data base can publish events to the network, the method comprising the steps, performed by a data processing system, of:

providing a link so that the data base can communicate with a data base connector computer program by way of a transaction monitor computer program;

setting up the data base connector as a publisher in the network, wherein the publisher publishes events of a first event type;

receiving input, from the transaction monitor that a user has altered data in the data base;

receiving input from the transaction monitor indicating that the user has committed the data alteration; and

publishing, by the data base connector, in accordance with the input from the transaction monitor that the data is committed, an event, having the first event type, to the network in accordance with the altered data.

2. The method of claim 1, further including the steps of:

receiving input from the transaction monitor indicating that the user wants to roll back the altered data; and

refraining, by the data base connector, from sending the altered data to the network in accordance with the rollback.

4. The method of claim 1, further comprising the step of:

sending the event, by the data base connector, to one of its neighbor hubs, where a data structure in the data base connector indicates that the neighbor hub is on the least-cost path to a subscriber for the event.

5. The method of claim 1, further comprising the steps of:

receiving an event by the data base connector from a neighbor hub of the data base connector;

determining, by the data base connector, in accordance with a data structure of the data base connector, that the data base connector has subscribed to events having the event type; and

sending, by the data base connector, the event to the data base.

6. The method of claim 1, further comprising the steps of:

receiving an event, by the data base connector from a neighbor hub of the data base connector;

determining, by the data base connector, in accordance with a data structure of the data base connector, that a neighbor hub is connected either directly or indirectly on the least-cost path to a subscriber for the event; and

sending, by the data base connector, the event to its neighbor hub, so that the event can be forwarded to the subscriber.

7. The method of claim 1, further including the step of:

sending the event, by the data base connector, to one of its neighbor hubs when a data structure in the data base connector indicates that a client of the neighbor subscribes to events having the type of the event.

8. The method of claim 1, further includes the step of:

sending an event, by the data base connector, to one of its neighbor hubs when a content filter in a data structure of the data base connector indicates that the data base subscribes to events having values found in the event.

9. The method of claim 1, further including the steps of:

defining an event that will be published by the data base connector; and

installing advertisements for the event in the data base connector.

10. The method of claim 1, further including the steps of:

adding an envelope to the event; and

adding a routing block to the event.

11. The method of claim 1, further including the step of:

incrementing a time-spent field of the event.

12. The method of claim 1, further including the step of:

determining if the time-to-live for the event has expired.

13. The method of claim 1, further including the step of:

determining if the content filter of the event is OK for a subscriber to the event.

19. The method of claim 4 wherein the least cost path is measured in units of time.

20. The method of claim 4, wherein the least cost path is measured in units of financial cost.

3. A method of connecting a data base to a publisher/subscriber network, so that the data base can subscribe to types of events advertised on the network, the method comprising the steps, performed by a data processing system, of:

providing a link so that a data base connector computer program can communicate with the data base;

setting up the data base connector as a subscriber in the network, wherein the subscriber subscribes to a first events of a first event type;

receiving, by the data base connector, an event from the network, having the first event type;

sending, by the data base connector, data in accordance with the received event to the data base; and

committing, by the data base connector, the data in the data base.

14. The method of claim 3, wherein the step of setting up the data base connector as a subscriber hub in the network includes the step of:

registering the data base connector with a hub included within the data base connector.

15. The method of claim 14 wherein the registering step further includes the step of:

setting a content filter for the data base connector.

16. The method of claim 3, wherein the step of setting up the data base connector as a subscriber hub in the network includes the step of:

establishing a callback procedure for the subscription.

17. The method of claim 3, further including the steps of:

distributing the subscription among hubs neighboring the data base connector.

18. The method of claim 3, further including the steps of:

receiving a subscription from a neighboring hub, where a client of the neighboring hub has registered the subscription with the neighboring hub;

determining a least-cost path from the data base connector to the publisher; and

sending the subscription registration to a neighbor hub that is on the least-cost path to the publisher.

21. A computer program product, including:

a computer usable medium having computer readable code embodied therein for causing a data base to connect to a publisher/subscriber network, so that the data base can publish events to the network, the computer program product comprising;

computer readable program code devices configured to cause a computer to effect providing a link so that the data base can communicate with a data base connector computer program by way of a transaction monitor computer program;

computer readable program code devices configured to cause a computer to effect setting up the data base connector as a publisher in the network;

computer readable program code devices configured to cause a computer to effect receiving input, from the transaction monitor that a user has altered data in the data base;

computer readable program code devices configured to cause a computer to effect receiving input from the transaction monitor indicating that the user has committed the data alteration; and

computer readable program code devices configured to cause a computer to effect publishing, by the data base connector, in accordance with the input from the transaction monitor that the data is committed, an event to the network in accordance with the altered data.

22. The computer program product of claim 21, further comprising:

computer readable program code devices configured to cause a computer to effect receiving input from the transaction monitor indicating that the user wants to roll back the altered data; and

computer readable program code devices configured to cause a computer to effect refraining, by the data base connector, from sending the altered data to the network in accordance with the rollback.

23. A computer program product, including:

a computer usable medium having computer readable code embodied therein for causing a data base to connect to a publisher/subscriber network, so that the data base can publish events to the network, the computer program product comprising;

computer readable program code devices configured to cause a computer to effect providing a link so that a data base connector computer program can communicate with the data base;

computer readable program code devices configured to cause a computer to effect setting up the data base connector as a subscriber in the network;

computer readable program code devices configured to cause a computer to effect receiving, by the data base connector, an event from the network;

computer readable program code devices configured to cause a computer to effect sending, by the data base connector, data in accordance with the received event to the data base; and

computer readable program code devices configured to cause a computer to effect committing, by the data base connector, the data in the data base.