JP2004348680A - Complex event notification system and complex event notification program - Google Patents

Abstract

An object of the present invention is to provide a system and a method for collecting and notifying publishing information using pre-stored logic for subscribing information obtained by combining a plurality of events, with respect to an event notification system.
A composite event notification system according to the present invention includes a module storage unit that stores aggregation logic of publishing information in advance, a composite subscription information acquisition unit that acquires composite subscribe information requested by a subscriber application, A subscribe information registering unit that decomposes and registers the composite subscribe information, a publish information acquisition unit that acquires the publish information based on the subscribe information registered and the aggregation logic when the publish information is received, and notifies the acquired information. Publish information notification means.
[Selection diagram] Fig. 1

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an event notification system for notifying publishing information transmitted from a publisher application based on a request from a subscriber application, and in particular, a subscriber application publishes with a logic specified for a request that combines a plurality of events. The present invention relates to an event notification system that acquires, aggregates, and notifies information.
[0002]
[Prior art]
Various services are provided on the Internet, and many users are able to receive these services. However, each service is provided in a unique manner by each service provider, and the use of one service is limited.
[0003]
On the other hand, user requests are complicated, and in order to fulfill the requests, it is sometimes necessary to use a plurality of services in order and efficiently, and to use the execution results of each other. However, if the user has to worry about which services should be used in which order, it is burdensome for the user and error-prone. Further, if the processing of the service takes a long time, the next processing cannot be started immediately unless the user is aware of when the processing is completed, which may waste time.
[0004]
For this reason, it is desired that services cooperate autonomously to some extent and operate cooperatively. However, services are created as needed by service providers and managed independently, so design a system that knows in advance the services that can be linked, executes each service according to it, and aggregates the results It is difficult to keep. Another problem is that as the number of service combinations that can be linked increases, the system must be designed and developed accordingly.
[0005]
Therefore, when a certain event occurs, an event notification service that notifies a specific service that the event has occurred is used. FIG. 3 shows the mechanism of the event notification service. The service X and the service Y register (subscribe) information of an event to be notified in advance ((1) in FIG. 3). Further, the services A to C autonomously transmit (publish) information to the event notification service in the form of an event ((2) in FIG. 3). The event notification service is for notifying (notifying) the information to the service X or the service Y when an event registered by the service X and the service Y occurs in the service A to C ((3) in FIG. 3). Here, the expression "event notification service" is a term viewed from the service, and the event notification service is described in other words as an event notification system, services X and Y are subscriber applications X and Y, and services A to C are publisher applications A to Although expressed as C, the entities may be the same.
[0006]
As standards of such an event notification service, a notification service of CORBA (for example, Non-Patent Documents 1 and 2), a pub / sub (Pub / sub) messaging model of Java Message Service (for example, Non-Patent Document 3), Alternatively, Microsoft. NET Alerts (for example, Non-Patent Document 4).
[0007]
[Non-patent document 1]
Notification Service Specification, [online], An Adapted Specification of the Object Management Group, Inc., [Search on April 7, 1993], Internet </ www. omg. org / docs / formal / 02-08-04. pdf>
[0008]
[Non-patent document 2]
CORBA Notification Service, [online], Dave Bartlett, [searched April 7, 2003], Internet <http: // www-6. ibm. com / jp / developerworks / components / 010720 / j_co-cjct7-index. html>
[0009]
[Non-Patent Document 3]
Java Message Service Specification-version 1.1, [online], Sun Microsystems, Inc. [Retrieved April 7, 2003], Internet <http: // java. sun. com / products / jms / docs. html>
[0010]
[Non-patent document 4]
Microsoft. NET Alerts, [online], Microsoft Corporation, [Retrieved April 7, 2003], Internet <http: // www. Microsoft. com / japan / net / services / alerts / default. asp>
[0011]
[Problems to be solved by the invention]
As mentioned above, it is desired that services cooperate autonomously to some extent and operate cooperatively. However, the cooperation of services that are actually required is not only a sequential activation but also a specific time. It may be started automatically, triggered by the number of executions of multiple services, started after waiting for the termination of multiple services, or may be limited to a specific procedure. Needs a function of notifying such intensive events.
[0012]
For example, in a development project, a message urging project members to submit a progress report is sent every fixed day of the week (eventual occurrence), and when all members have completed their progress, Notification to the project leader at a time (waiting for an event). In addition, when there is a member who has not submitted by the due date, it is also conceivable that a reminder is performed several times, and when a certain number of times is reached, the progress information that is available is collectively notified (event counter). In addition, an event service can be used when a majority decision is made to form a consensus among members.
[0013]
However, many conventional event notification services did not handle complex events. Therefore, in order for a service to be activated in response to the occurrence of multiple events, the service itself, which is the recipient of the event notification, receives all the individual events, and when all the necessary events have been collected, It is necessary to design a service so as to start processing, or to separately construct a service that only notifies the target service of the event when the event is completed.
[0014]
However, in the former case, if a service that can be linked is newly added or if the way of event aggregation is changed, the service itself must be changed each time, and it is difficult to respond flexibly. is there. In some cases, it may be necessary to restart the service. In the latter case, it is necessary to construct a service only for coordination according to the aggregation of events, and it is difficult to easily realize coordination because the cost of development and subsequent management increases.
[0015]
Therefore, it is difficult to make the cooperation between services correspond to an intensive event, which has been an obstacle to realizing complicated service cooperation. According to the present invention, operation logic for acquiring and aggregating publish information generated by a plurality of events is modularized and internally provided, and a corresponding module is selected based on composite subscribe information, and a request for each primitive event is internally generated. And publishes the information by operation logic and notifies the subscriber application. Moreover, it is an object of the present invention to increase the versatility by enabling the addition of a module, and to facilitate the realization of complex service cooperation.
[0016]
[Means for Solving the Problems]
In order to solve the above problems, a composite event notification system according to the present invention is configured as follows.
(1) First invention
The first invention decomposes composite subscribing information composed of a combination of a plurality of events into individual primitive subscribing information, acquires publishing information by aggregation logic of publishing information stored in advance, and specifies the designated publishing information. The notification destination is notified. The principle will be described with reference to FIG. As shown in FIG. 1, the present invention comprises a module storage unit 1, a composite subscribe information acquisition unit 2, a subscribe information registration unit 3, a publish information acquisition unit 4, and a publish information notification unit 5.
[0017]
The module storage unit 1 stores (stores) an event processing module describing logic for aggregating publishing information in an appropriate storage unit in advance. If the event processing module is, for example, a waiting logic, the event processing module waits for the occurrence of three events A to C, acquires publishing information of them, and notifies (collects) the information when all the information is completed. , And so on. The description of the logic is not fixedly determined for the event name or the number of events to be processed, but is described so as to be able to be processed in a general-purpose manner.
[0018]
The composite subscribe information obtaining means 2 obtains composite subscribe information in response to a request from a subscriber application. The composite subscribe information includes information in which a plurality of event names to be notified are combined, a notification destination of the acquired information, and the like.
The subscribe information registering means 3 decomposes the acquired composite subscribe information into subscribe information of individual events based on the event processing module, and registers the subscribe information in an appropriate storage unit. For example, composite subscribe information composed of a combination of five primitive events is decomposed into five subscribe information.
[0019]
The publishing information acquisition means 4 acquires and publishes information (publishing information) published by the occurrence of an event in the publisher application using the registered subscribing information and the event processing module. . That is, the published information is the information required by the subscribe information, and when the information matches the logic in the event processing module, the published information is acquired and aggregated. For example, when it is composite subscribe information that the user wants to acquire information of event X and event Y and then acquire information of event Z, the subscribe information registering means 2 registers primitive events of event X and event Y. , Event Z is registered, but even if the event Z occurs before the event X or the event Y, the information of the event Z is not acquired at that time.
[0020]
The publishing information notification means 5 notifies the obtained publishing information to a notification destination designated by the composite subscribe information.
According to the first aspect, a complex event notification system that can easily notify complex information can be provided by describing a logic for aggregating publish information by giving a complicated relationship to the event processing logic. Further, only the aggregated notification message is transmitted between the subscriber application and the composite event notification system, and individual events are not notified, so that the communication amount can be reduced. Further, when it is desired to collectively notify events by different logics, only the event processing module needs to be changed.
(2) Second invention
According to a second aspect of the present invention, a plurality of event processing modules each describing an aggregation logic of publishing information are provided, and an event processing module can be selected based on composite subscribe information.
[0021]
The parts different from the first invention will be described.
First, the module storage means 1 is that the aggregation logic of the publishing information includes a plurality of event processing modules. For example, an event processing module such as "waiting", "majority decision", or "counter" is provided like a cartridge.
[0022]
Further, the composite subscribe information acquired by the composite subscribe information acquisition means 2 includes information on the type of event processing in addition to the information on the combination of a plurality of events of the first invention. The type of event processing designates an event processing method such as "waiting" or "majority decision" described in the module storage means 1, and is information used to identify selection of an event processing module.
[0023]
The subscribe information registering means 3 selects an event processing module based on the information on the type of event processing, decomposes the composite subscribe information into individual event subscribe information using the selected event processing module, and registers the subscribe information. . The publishing information collecting unit 4 acquires publishing information using the selected event processing module.
[0024]
According to the second aspect, by storing a plurality of event processing modules, it becomes possible to provide a composite event notification system that can support various acquisition logics of publishing information. There is also a merit that this event processing module can be added as needed without stopping the entire system.
(3) Third invention
According to a third aspect of the present invention, only by designating a composite event name, composite subscribe information is created based on a composite event definition stored in advance corresponding to the composite event name, and publish information for the composite event is obtained. Is what you do.
[0025]
FIG. 2 shows the principle of the third invention. The module storage means 1, the composite event definition body storage means 6, the composite subscribe information creation means 7, the subscribe information registration means 3, the publish information aggregation means 4, and the publishing It comprises information notification means 5. Among these, the composite event definition body storing means 6 and the composite subscribe information creating means 7 are different from those of the second invention, and the other components are the same as those of the second invention, so these components will be described.
[0026]
The composite event definition storage unit 6 stores a definition for creating composite subscribe information in advance corresponding to the composite event name.
Upon obtaining the composite event name and its parameters from the subscriber application, the composite subscribe information creating means 7 calls the composite event definition stored from the composite event name, and creates the composite subscribe information by incorporating the parameters. .
[0027]
After the composite subscribe information is created, it is the same as the second invention.
According to the third aspect, the subscriber application need only specify the composite event name and the parameter without creating the composite subscribe information. The definition of the composite event can be easily changed by, for example, allowing the administrator or the user of the event service to perform the definition. This has an effect that the composite event notification system becomes easier to use.
(4) Fourth invention
According to a fourth aspect, in the subscribe information registering means according to the first to third aspects, the acquired composite subscribe information is forwarded to another composite event notification system to request processing.
[0028]
According to the fourth aspect, by being able to request another complex event notification system, the load can be leveled out when the load of the own complex event notification system is high, and the event processing module can be provided to the own system. There is an effect that processing can be performed even when is not implemented.
(5) Fifth invention
A fifth invention is a composite event notification program according to the first invention.
[0029]
According to the fifth aspect, by providing a plurality of event processing modules, it becomes possible to provide a composite event notification program that can easily acquire various publish information from the composite subscribe information in cooperation with each other.
[0030]
BEST MODE FOR CARRYING OUT THE INVENTION
Next, an embodiment of the present invention will be described with reference to FIGS.
(Embodiment 1)
Embodiment 1 is an example that embodies the first invention, and FIG. 4 shows the overall configuration. The composite event notification system 100 according to the present invention includes a subscribe information receiving unit 101, a subscribe dispatcher 102, an event processing module 103, a subscribe information managing unit 104, an event receiving unit 105, a clock 106, a notification dispatcher 107, and an event notice. It comprises a fire 108, a composite subscribe information management table 120, a sub event processing work table 130, and a subscribe information table 140. Here, the hardware of the composite event notification system 100 is a computer, and the composite subscribe information management table 120, the subevent processing work table 130, and the subscribe information table 140 are stored in an external storage or a storage unit on a memory. It is a data table. The clock 106 is a clock function built in the computer, and the other than the above-described clock is a program developed on the memory.
[0031]
The subscribe information receiving unit 101 has a function of receiving subscribe information requested by a subscriber application. Here, the format of the received subscribe information is checked, and if appropriate, an ID is assigned and passed to the subscribe dispatcher 102. If the format does not match, an error is notified to the subscriber application that made the request. FIG. 5 shows a data example of the subscribe information. FIG. 5A shows an example of conventional subscribe information of a primitive event, and FIG. 5B shows an example of subscribe information of a composite event, which is described using XML. Each tag will be described. First, the “subscribe” tag in FIG. 5A indicates that it is subscribe information. The “event” tag indicates the content of the event that the user wants to be notified, and “type” indicated in the tag is an attribute indicating the type of event processing. In this case, “primitive” indicating that the event processing is a single event processing "And" name "indicate the event name. Subsequently, a “destination” tag indicates a notification destination of the acquired publish information, a “contents” tag indicates contents to be notified, and an “expire” tag indicates an expiration date of the publish information acquisition. In the example of the subscribe information of the composite event in FIG. 5B, the attribute of “event” is “wait”, which indicates that the event indicated in the next line is to be waited for and the process of notifying that the event is completed is performed. Things. [Subevent] below the “event” tag indicates a combination of a plurality of events. Here, three primitive sub-events of Event-A, Event-B and Event-C are combined.
[0032]
The subscribing dispatcher 102 checks the contents of the subscribing information received by the subscribing information receiving unit 101, and sets the subscribing information management unit 104 for a primitive event and the event processing module 103 for a complex event. Call and pass subscribe information. That is, a single (primitive) event or a composite event is sorted here.
[0033]
The event processing module 103 describes the aggregation logic of the publishing information and basically has two functions. One is a function at the time of subscribing. The subscribing information (subscribing information of the composite event) passed from the subscribing dispatcher 102 is registered in the composite subscribing information table 120. Break down into events. Then, an ID obtained by adding an additional number to the ID previously given to the information of the plurality of decomposed sub-events is entered (registered) in the sub-event work table 130. Further, the information of the sub-event decomposed together with the newly assigned ID is passed to the subscribe information management unit 104, and a request is made to register the information in the subscribe information table 140. Another function of the event processing module 103 is to acquire and aggregate publish information, and determine whether to acquire publish information passed from the subscribe information management unit 104, which will be described later, based on aggregation logic, and acquire it. If so, the function is to write the publish information in the sub-event processing table 130. Furthermore, it is checked whether or not the publish information has been acquired for all the subscribe information of the related IDs in the sub-event processing table 130. If the publish information has been acquired, a notification message is created and notified to the notification dispatcher 107. Make a request.
[0034]
Here, an example of the data structure of the composite subscribe information management table 120 and the sub-event work table 130 will be described. FIG. 6 shows an example of the composite subscribing information management table 120, which includes fields of "ID", "notification destination", "notification content", and "expiration date". “ID” is assigned by the subscribe information receiving unit 101, “notification destination” is a notification destination for notifying the aggregated publish information, and “notification content” is notified when an event specified by the subscribe information occurs. The content and “expiration date” are the expiration date of the subscribe information, and after this, the notification is not notified even if the target event occurs. The ID "subid # 123" in FIG. 6 is the data of the subscribe information of the composite event shown in FIG. 5B.
[0035]
FIG. 7 shows an example of the sub-event work table 130, which includes fields of "ID", "content type", and "content". “ID” is an ID assigned to the sub-event, which is obtained by adding an additional number to the ID assigned by the subscribe information receiving unit 101. In the data of the ID shown in FIG. 7, the subscribe information received by the subscribe information receiving unit 101 is first given an ID of “subvid # 123” to the subscribe information of the composite event, An ID is assigned with an additional number. The “content type” and “content” are written when the publishing information is acquired, and nothing is written at the time of entry at the time of subscribing. The example in FIG. 7 indicates that the publishing information has been acquired for the sub-events “subid # 123-1” and “subid # 123-2”.
[0036]
The subscribing information management unit 104 subscribes to the subscribing information received by the subscribing information receiving unit 101 for the complex event and the subscribing information received by the subscribing information receiving unit 101 for the single event. Register in the table 140. Further, it checks whether the publishing information passed from the event receiving unit 105 is the information requested by the subscribe information, and if the publishing information is a primitive event, requests the notification dispatcher 107 to notify the acquired publishing information. If the event is a composite event, the event processing module 103 is notified.
[0037]
Here, a data example of the subscribe information table 140 will be described. FIG. 8 shows an example of data in the subscribe information table 140, which is composed of fields of "ID", "event name", and "sub-event notification destination". The “ID” is an ID assigned to the subscribe information of the single event by the subscribe information receiving unit 101, and the subscribe information of the subevent decomposed by the composite event is an ID assigned by the event processing module 103. It is. The “event name” is the name specified in the subscribe information, and the “sub-event notification destination” is a notification destination when an event occurs. For example, in the case of a single event, the URL is used, and in the case of a sub-event decomposed by a composite event, the name specifies the event processing module 103 (the event name of the event that is implemented by adding “#” at the beginning of the Java class name). Processing module). More specifically, the event processing module 103 subscribes the individual sub-events to the subscribe information managing unit 104, and the subscribe information managing unit 104 notifies the event processing module 103 of the occurrence of the sub-event. This is the notification destination of the event processing module 103.
[0038]
The event receiving unit 105 receives publishing information when an event occurs in the publisher application. Here, the format of the published information is checked and passed to the subscribe information management unit 104. FIG. 9 shows a data example of the publishing information. This is an example of publishing Event-A information.
[0039]
The clock 106 is used to determine whether or not it is within the validity period of the subscribe information. For example, if the required event does not occur for a long time, it will continue to wait, so if the time specified by the clock 106 has passed, only the acquired information is notified even if the acquired information is missing. Used in such cases. The determination is made by comparing with the value of the “expiration date” field of the composite subscribe information management table 120 of FIG.
[0040]
The notification dispatcher 107 receives a notification request from the event processing module 103 and the subscribe information management unit 104, and issues a notification instruction to the event processing module 103 or the event notifier 108 according to a notification destination. is there. If the notification destination is a normal URL, the notification request is sent to the event notifier 108, and if the notification destination is the event processing module name, the notification is requested to the event processing module 103.
[0041]
The event notifier 108 notifies the notification destination of the publish information acquired in response to the instruction from the notification dispatcher 107. FIG. 10 shows an example of the notification data. FIG. 10 is an example of notification information that the event processing module 103 acquires and aggregates publishing information based on the request for composite subscribing information in FIG. 5B.
[0042]
Next, a processing flow of the complex event notification system 100 shown in FIG. 4 will be described. In this description, two processes, a process of registering an event name at the time of subscribing and a process of acquiring and notifying publish information when an event occurs, will be described.
First, the former subscribe process will be described with reference to FIGS. In FIG. 11, the composite event notification system 100 receives the subscribe information from the subscriber application and checks the format of the subscribe information. If there is a problem with the format, the subscriber application is notified as an error. If there is no problem, a unique ID is assigned to the subscribe information. (S101 to S105).
[0043]
Next, the type of the event is checked by checking the contents of the subscribe information. That is, it checks whether the subscribe information is a single event or a composite event. If it is a composite event, the event processing module 103 is called. At this time, the ID and the subscribe information (ie, the composite subscribe information) are passed to the event processing module 103. The processing inside the event processing module 103 will be described below. The composite event is decomposed from the processed event processing module 103 to receive information of sub-events each assigned an ID, and registered in the subscribe information table 140. I do. On the other hand, if the subscribe information is a single event, the subscribe information is registered in the subscribe information table 140 together with the ID given without passing through the event processing module 103. (S106 to S109).
[0044]
Next, a processing flow of the event processing module 103 called in step S108 will be described with reference to FIG. The event processing module 103 will be described as an example of a waiting logic module, and the data of the subscribe information will be described as the information of FIG. 5B. First, the notification destination, the notification content, and the expiration date are written from the subscribe information to the composite subscribe information management table 120 together with the assigned ID. Subsequently, the information is decomposed into primitive sub-events by a “subvent” tag in a lower hierarchy of the “event” tag of the subscribe information. Since the subscribe information in FIG. 5B can be decomposed into three subevents, “ID + sequential number” is assigned to each of them as the ID of the subevent. This ID is written (ie, entered) in the sub-event processing work table. (S201 to S204).
[0045]
The processing from receiving the subscription information of the single event and the subscribing information of the composite event to registering the same has been described. Next, a processing flow for acquiring publishing information from the publisher application based on the registration information will be described with reference to FIGS.
In FIG. 13, publishing information is received based on the occurrence of an event of the publisher application. The format of this information is checked, and if there is no problem, the subscribed information table 140 is checked to see if the published event name is registered (that is, the subscribed information requires the published information). To see if they are). If there is subscribe information equal to the event name in the subscribe information table 140, then the subscribe information table 140 is checked to determine whether the notification destination is the name of the waiting event processing module. Call 103. (S301 to S308).
[0046]
Although details will be described later in the event processing module 103, the publishing information is selected by the aggregation logic. When it is determined that the publishing information requested by the subscribing information has been completed, a notification request is made. In response to the notification request, the publishing information collected by the event processing module 103 is notified to the designated notification destination. On the other hand, when the subscribe information requested in step S307 is a single event, a notification destination is acquired from the subscribe information table 140 to notify the publish information. (S309 to S311).
[0047]
Next, the process of acquiring the publishing information in the event processing module 103, which has been briefly described, will be described using an example of a waiting event with reference to FIG. When this module is called, the publishing information and the ID are passed. First, the publishing information is checked with reference to the composite subscribing information management table 120 to determine whether the obtained publishing information is within the expiration date. If the expiration date has passed, the subscribe information is deleted and the processing ends. If the publish information is within the expiration date, the publish information is written in the “content type” and “content” fields of the sub-event processing work table 130 based on the publish information. Subsequently, the sub-event processing work table 130 is checked to determine whether all the subscribe information of the same composite event has acquired publish information (by checking whether the “content type” or “content” field has NULL). to decide). If all of them have been acquired, the information of the “content type” and “content” fields of the sub-event processing work table 130 are aggregated to create a notification message, and refer to the composite subscribe information management table 120. Then, the notification destination is acquired, and a notification request is made to the notification dispatcher 107. Subsequently, the contents of the sub-event processing work table 130 are cleared, and the process ends. If there is any sub-event information for which acquisition has not been completed, the process ends without making a notification request. (S401 to S409).
[0048]
The processing of the composite event notification system has been described above. In addition to the description of the processing flow, the composite subscribing information management table 120 may be checked at regular time intervals, and the expired subscribing information may be collected and notified for the expired subscribing information.
(Embodiment 2)
Embodiment 2 is an example that embodies the second invention, and FIG. 15 shows the overall configuration. FIG. 4 showing the overall configuration of the first embodiment is different from the configuration shown in FIG. 4 in that a plurality of event processing modules 103 are provided and a module management table 150 for managing them is added. The different parts will be described.
[0049]
The event processing module 103 is configured by a module for each aggregation logic such as “Wait” and “Sequential acquisition”. These modules can be easily added or deleted.
The module management table 150 is, for example, the one shown in FIG. 16 and is a correspondence table between event types and module names. When selecting the event processing module 103 in the subscribe dispatcher 102, the event processing module 103 is selected using the module management table 150.
[0050]
The composite subscribe information management table 120 and the sub-event processing work table 130 are provided for each event processing module 103. This facilitates mounting and dismounting of the module.
Other functions and flows are the same as those described in the first embodiment.
(Embodiment 3)
Embodiment 3 is a composite event notification system that creates composite subscribe information and enables processing of composite events simply by specifying the composite event name, and its configuration is shown in FIG.
[0051]
FIG. 17 is obtained by adding a complex event definition body receiving unit 109 and a complex event definition body table 160 to the configuration of FIG. The composite event definition receiving unit 109 stores the composite event definition created by the user or the like in the composite event definition table 160, or receives the composite event name and the parameter received by the The subscribe information of the event is created and returned to the subscriber information receiving unit 101. Subsequent creation of the subscribe information is as described in the first embodiment, and a description thereof will not be repeated.
[0052]
The composite event definition is, for example, the description shown in FIG. In this example, the composite event name is “MonthlyReport”, and the notification destination (destination), the content to be acquired (contents), and the expiration date (expire) are specified by respective tags.
The composite event name and parameters specified by the subscriber application are, for example, those shown in FIG. Here, the composite event name is “MonthlyReport”, the event type is “Wait (waiting event)” as a parameter, and the events to be notified are “MemberA to C”. The composite subscribe information created for this is shown in FIG. 20, and is created by combining the information shown in FIG. 18 and FIG. FIGS. 18 to 20 are application examples in which monthly reports created by project members A to C are set with due dates and collected. However, even if the members are changed, the monthly reports are changed only by changing the parameters of the composite event name. Can collect books. This is particularly effective when there is a slight change in routine work.
[0053]
Further, it is also possible to combine processes of a plurality of types of composite events using this definition field. For example, the process of "waiting" for acquiring the information of the event C after waiting for the event A and the event B is combined with the process of "sequential acquisition".
(Embodiment 4)
The fourth embodiment enables a plurality of complex event notification systems to perform event notification using each other's extension modules, and FIG. 21 shows the configuration.
[0054]
The composite event notification system A200 in FIG. 21 has, in the module management table 203, information on event processing modules that can be used by the composite event notification system B300 (including information on connection destinations) in addition to the event processing modules that can be processed by itself. It is assumed that
When the composite event notification system A 200 receives the composite subscribe information from the subscriber application in the subscribe information reception unit 201, the subscribe dispatcher 202 refers to the module management table 203 and subscribes to the subscribe information reception unit 301 of the composite event notification system B 300. Subscribe to. The composite event notification system B300 that has received the request performs normal subscribe processing using the internal event processing module, and publishes the publishing information from the publisher application received by the event receiving unit 302 by the logic of the event processing module. It acquires them and notifies them to the event notifier 204 of the composite event notification system A200 via the event notifier 303. The composite event notification system A200 notifies the subscriber application that received the request of the publishing information. Alternatively, the subscriber application may be notified directly from the event notifier 303 of the composite event notification system B300.
[0055]
Further, the complex event processing module notification system A200 may have a module management table 203 so that the module management table 203 can be forwarded to a plurality of other complex event notification systems.
Further, a plurality of complex event notification systems may have an event processing module in common. In this case, the composite event notification systems need to keep the module management table updated at all times.
[0056]
With such a configuration, it is possible to prevent the load of the composite event notification system from being concentrated on one system.
Although the four embodiments have been described above, the present invention can be incorporated in a database. A setting that captures operations and changes to specific data stored in the database as failures that occur during processing as composite subscribing information as events, and notifies you when a composite event that aggregates these events occurs Can be considered. Further, not only an event from the database but also an event from an external service may be combined to detect and notify a composite event.
[0057]
【The invention's effect】
ADVANTAGE OF THE INVENTION According to this invention, publish information can be acquired, aiming at complicated cooperation between events. Further, it is possible to construct a system that can easily add or change the publishing information acquisition logic.
[Brief description of the drawings]
FIG. 1 is a principle diagram of the first invention.
FIG. 2 is a principle diagram of the third invention.
FIG. 3 is an explanatory diagram of an event notification service.
FIG. 4 is an overall configuration diagram of Embodiment 1;
FIG. 5 is a data example of subscribe information.
FIG. 6 is a data example of a composite subscribe information management table 120;
FIG. 7 is a data example of a sub-event processing work table 130;
FIG. 8 is a data example of a subscribe information table 140;
FIG. 9 is a data example of publishing information.
FIG. 10 is a data example of notification information.
FIG. 11 is a flow example of a subscribe information registration process;
FIG. 12 is an example of a flow of a composite subscribed information decomposing process by a waiting event processing module.
FIG. 13 is a flow example of a publishing information acquisition process.
FIG. 14 is a flowchart illustrating an example of a flow of a publishing information acquisition process of a waiting module;
FIG. 15 is an overall configuration diagram of a second embodiment.
FIG. 16 is a data example of a module management table 150;
FIG. 17 is an overall configuration diagram of Embodiment 3;
FIG. 18 is a data example of a complex event definition body.
FIG. 19 is a data example of a composite event name and parameters.
FIG. 20 is a data example of subscribe information created from a composite event name.
FIG. 21 is an overall configuration diagram of a fourth embodiment.
[Explanation of symbols]
1: Module storage means
2: Composite subscribe information acquisition means
3: Subscription information registration means
4: Publish information acquisition means
5: Publish information notification means
6: Composite event definition storage means
7: Composite subscribe information creation means
100: Complex event notification system
101: subscribe information reception unit
102: subscribe dispatcher
103: Event processing module
104: subscribe information management unit
105: Event reception unit
106: Clock
107: Notification dispatcher
108: Event Notifier
109: Complex event definition body reception unit
120: Composite subscribe information management table
130: work table for sub-event processing
140: subscribe information table
150: Module management table
160: Composite event definition table
200: Complex event notification system A
201: subscribe information reception unit
202: subscribe dispatcher
203: Module management table
204: Event Notifier
300: Complex event notification system B
301: subscribe information reception unit
302: Event reception unit
303: Event Notifier

Claims (5)

Module storage means for storing an event processing module describing aggregation logic of publishing information,
By a request from a subscriber application, a composite subscribe information obtaining means for obtaining composite subscribe information including a combination of a plurality of events,
A subscribe information registering unit that decomposes the composite subscribe information into subscribe information of individual events and registers the composite subscribe information based on the event processing module;
Publish information acquisition means for acquiring the publish information based on the registered subscribe information and the event processing module when receiving publish information due to an event occurrence of a publisher application,
A publishing information notification unit that notifies the obtained publishing information based on the composite subscribing information. Module storage means for storing a plurality of event processing modules describing aggregation logic of publishing information,
A composite subscribe information acquisition unit that acquires composite subscribe information including a type of event processing and a combination of a plurality of events by a request from the subscriber application,
A subscribe information registering unit that decomposes the composite subscribe information into subscribe information of individual events and registers based on the event processing module selected by the type of the event process;
Publisher information obtaining means for obtaining the publish information based on the registered subscribe information and the selected event processing module when receiving the publish information due to the event occurrence of the publisher application,
A publishing information notification unit that notifies the obtained publishing information based on the composite subscribing information. Module storage means for storing a plurality of event processing modules describing aggregation logic of publishing information,
A composite event definition storage means for storing a plurality of composite event definition bodies describing a definition body for creating composite subscribe information corresponding to the composite event name;
Based on a composite event name and a parameter specified by the subscriber application, a composite subscribe information creating unit that selects the composite event definition to create composite subscribe information,
Based on the event processing module selected by the composite subscribe information, subscribe information registration means for decomposing the composite subscribe information into subscribe information of individual events and registering the subscribe information,
Publisher information obtaining means for obtaining the publish information based on the registered subscribe information and the selected event processing module when receiving the publish information due to the event occurrence of the publisher application,
A publishing information notification unit that notifies the obtained publishing information based on the composite subscribing information. The composite event notification system according to any one of claims 1 to 3, wherein the subscribe information acquired by the subscribe information registration means is requested to another composite event notification system for event notification processing. Complex event notification system. A module storage procedure for storing an event processing module describing the aggregation logic of the publishing information,
A composite subscribe information acquisition procedure for acquiring composite subscribe information including a combination of a plurality of events in response to a request from the subscriber application,
A subscribe information registration step of decomposing the composite subscribe information into subscribe information of individual events and registering the composite subscribe information based on the event processing module;
A publishing information acquisition procedure for acquiring the publishing information based on the registered subscribe information and the event processing module when receiving the publishing information due to the event occurrence of the publisher application,
A publishing information notification procedure for notifying the acquired publishing information based on the composite subscribing information.

Images