Publish subscribe system

• US 20030115291A1
• Filed: 09/25/2002
• Published: 06/19/2003
• Est. Priority Date: 09/28/2001
• Status: Abandoned Application

• Current Assignee: Christopher Cole, Christopher John Horril, Gary David Kendall
• Original Assignee: Christopher Cole, Christopher John Horril, Gary David Kendall
• Inventors: Cole, Christopher, Kendall, Gary David, Horril, Christopher John
• Application Number:
  US10/254,456
• Publication Number:
  US 20030115291A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/9538 Presentation of query results
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

A system of publishing data from a data repository server to a subscribing client, wherein a subscribing selector server receives data published by the data repository server, filters the published data in accordance with filtering criteria defined on the selector server, and re-publishes the filtered data to the subscribing client, and wherein the filtered data is cached on the selector server and is available for querying by the subscribing client. A number of analytical engines are provided and a broker framework receives requests for an analysis of data and selects one or more engines to use in carrying out the requested analysis. Checkpoints are used to ensure consistency of data.

Claims

1. A system of publishing data from a data repository server to a subscribing client, wherein a subscribing selector server receives data published by the data repository server, filters the published data in accordance with filtering criteria defined on the selector server, and re-publishes the filtered data to the subscribing client, and wherein the filtered data is cached on the selector server and is available for querying by the subscribing client.

2. A system as claimed in claim 1, wherein a plurality of data repository servers are provided, and the selector server receives data published by two or more of the data repository servers.

3. A system as claimed in claim 1, wherein a plurality of selector servers are provided, applying different filtering criteria to the data which is re-published.

4. A system as claimed in claim 1, wherein the selector server receives data which has been published by the data repository server and re-published after preliminary filtering by a preliminary selector server which caches the preliminary filtered data so that it is available for querying by the selector server.

5. A system as claimed in claim 1, wherein the selector server defines a plurality of filtering criteria and re-publishes differently filtered data on a corresponding plurality of channels.

6. A system as claimed in claim 1, wherein a plurality of data repository servers are provided, the selector server receives data published by two or more of the data repository servers, and wherein there is provided a checkpoint server which transmits checkpoints to each of the data repository servers at intervals, each data repository server being configured to publish a checkpoint event on receipt of a checkpoint from the checkpoint server, the receipt of a checkpoint event from one data repository server causing the selector server to queue data change events until a checkpoint event has been received from each of the data repository servers from which the selector server receives data, after which processing of the queued data change events takes place.

7. A system as claimed in claim 1, wherein the selector server is capable of a cold start in which the cached filtered data is re-created from the data repository server, and a warm start in which the cached filtered data is re-created from the existing cached filter data and a history of data change events which have been published by the data repository server.

8. A system as claimed in claim 7, wherein the history of data change events is held on the selector server.

9. A system as claimed in claim 7, wherein the history of data change events is held on the data repository server.

10. A system as claimed in claim 1, including a subscribing application server which receives filtered data re-published by the selector server and also receives notification of data change events from the selector server, the application server hosting an application which provides information derived from the received filtered data for transmission to a client, and wherein on notification of a data change event from the selector server, updated data in accordance with the change event is transmitted from the application server to the client.

11. A system as claimed in claim 10 wherein the updated data is used to change only that portion of information displayed to a user by a client user interface which is affected by the data change event.

12. A system as claimed in claim 1, wherein a number of analytical engines are provided and a broker framework receives requests for an analysis of data and selects one or more engines to use in carrying out the requested analysis.

13. A data repository server for use in a publish—

subscribe system in which data is published from the data repository server to a subscribing client, a subscribing selector server receives data published by the data repository server, filters the published data in accordance with filtering criteria defined on the selector server, and re-publishes the filtered data to the subscribing client, and in which the filtered data is cached on the selector server and is available for querying by the subscribing client;

wherein the data repository server is configured to publish data change events, to maintain a history of data change events and to re-transmit a set of data change events which have occurred after a specified point, in response to a request from the selector server.

14. Computer software in the form of machine readable code on a data carrier which when run on data processing apparatus will configure the data processing apparatus as a data repository server for use in a publish—

subscribe system in which data is published from the data repository server to a subscribing client, a subscribing selector server receives data published by the data repository server, filters the published data in accordance with filtering criteria defined on the selector server, and re-publishes the filtered data to the subscribing client, and in which the filtered data is cached on the selector server and is available for querying by the subscribing client;

wherein the computer software further configures the data repository server to publish data change events, to maintain a history of data change events and to re-transmit a set of data change events which have occurred after a specified point, in response to a request from the selector server.

15. A selector server for use in a system in which data is published from a data repository server to a subscribing client, wherein the selector server is configured as a subscribing selector server to receive data published by the data repository server, to filter the data in accordance with filtering criteria defined on the selector server, to re-publish the filtered data to a subscribing client, and to cache the filtered data so that it is available for querying by the subscribing client.

16. A selector server as claimed in claim 15, being further configured to receive data published by two or more data repository servers.

17. A selector server as claimed in claim 15, being further configured to receive data re-published by at least one preliminary selector server.

18. Computer software in the form of machine readable code on a data carrier which when run on data processing apparatus will configure the data processing apparatus as a selector server for use in a system in which data is published from a data repository server to a subscribing client, wherein the computer software configures the selector server as a subscribing selector server to receive data published by the data repository server, to filter the data in accordance with filtering criteria defined on the selector server, to re-publish the filtered data to a subscribing client, and to cache the filtered data so that it is available for querying by the subscribing client.

19. An application server for use in a publish—

subscribe system in which data is published from a data repository server to a subscribing client, a subscribing selector server receives data published by the data repository server, filters the published data in accordance with filtering criteria defined on the selector server, and re-publishes the filtered data to the subscribing client, in which the filtered data is cached on the selector server and is available for querying by the subscribing client; and

in which the data repository server is configured to publish data change events, to maintain a history of data change events and to re-transmit a set of data change events which have occurred after a specified point, in response to a request from the selector server;

wherein the application server is configured to receive filtered data re-published by the selector server and also to receive data change events re-published by the selector server, the application server hosting an application which provides information derived from the received filtered data for display to a client, and being further configured so that on notification of a data change event from the selector server, updated data in accordance with the change event is transmitted from the application server to the client.

20. Computer software in the form of machine readable code on a data carrier which when run on data processing apparatus will configure the data processing apparatus as an application server for use in a publish—

subscribe system in which data is published from a data repository server to a subscribing client, a subscribing selector server receives data published by the data repository server, filters the published data in accordance with filtering criteria defined on the selector server, and re-publishes the filtered data to the subscribing client, in which the filtered data is cached on the selector server and is available for querying by the subscribing client; and

in which the data repository server is configured to publish data change events, to maintain a history of data change events and to re-transmit a set of data change events which have occurred after a specified point, in response to a request from the selector server;

wherein the computer software configures the data processing apparatus to receive filtered data re-published by the selector server and also to receive data change events re-published by the selector server;

to host an application which provides information derived from the received filtered data for display to a client; and

, on notification of a data change event from the selector server, to transmit updated data in accordance with the change event from the application server to the client.

21. A system of publishing data change events from a plurality of data repository servers to a subscribing client, wherein a subscribing selector server receives data published by the data repository servers and re-publishes the data change events to the subscribing client, and wherein there is provided a checkpoint server which transmits checkpoints to each of the data repository servers at intervals, each data repository server being configured to publish a checkpoint event on receipt of a checkpoint from the checkpoint server, the receipt of a checkpoint event from one data repository server causing the selector server to queue data change events until a corresponding checkpoint event has been received from each of the data repository servers from which the selector server receives data, after which processing of the queued data change events takes place and the data change events are re-published to the subscribing client.

22. A system for analysing data published from a data repository server to a subscribing client, wherein an analytics server provides a plurality of analytics engines which provide calculation based services to the client, there being a broker framework which receives requests for calculations on data and determines which of the analytics engines should be used for a particular request.