JPH08129536A - Event processing system - Google Patents

Abstract

PURPOSE: To flexibly handle events from plural applications. CONSTITUTION: A node D is provided with an event manager 100. The event manager 100 is equipped with a registered event management part 101 and a received event management part 102 which manages registered events and informed events from nodes A, B, and C. An event condition decision part 103 when informed of event generation from one of the nodes performs a condition comparison with the registered events of the registered event management part 101 and when the decision result indicates a coincidence, an event process execution indication part 104 calls the node where the event is registered.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an event processing system for performing dynamic event processing in a distributed processing environment.

[0002]

2. Description of the Related Art In order to transmit an event between applications existing in a distributed environment, some kind of communication is required between execution processes. Generally, since the communication is transmitted between nodes, in a UNIX (registered trademark of UNIX System Laboratories) environment, for example, sockets and TLI (Tr
communication is performed using ansport LayerInterface).

In many systems, a remote procedure call (RPC) for performing request / response type communication in the client-server model in the same manner as a normal local procedure call is realized based on this socket. Using this function, when some event occurs, the remote procedure of a specific distributed application can be called to request event processing.

Further, more flexible message communication is also performed by multicast communication for sending a message to a group of nodes grouped for a specific purpose at once, and broadcast communication for sending a message to all nodes at once. In some of these communications, it is possible to specify the number of members that can receive the message and the timeout.

[0005]

However, the above distributed processing system has the following problems. (1) Member management in inter-group communication Normally, in the above-mentioned multicast communication, a group is managed for each application, so management becomes complicated in an application in which members constituting the group dynamically change. (2) Overhead caused by unnecessary network communication
Since the processing is performed after notifying the applications of all the nodes that monitor the event, the event processing is executed only when the event monitoring suspension or the combination of the events of multiple applications satisfies certain conditions. In some cases, the processing overhead is high.

From these points, it has been desired to realize an event processing system capable of flexibly operating events from a plurality of applications.

[0007]

In order to solve the above-mentioned problems, the event processing system of the present invention provides an event manager on any one of a plurality of nodes constituting a distributed environment. This event manager includes a registered event management unit, a reception event management unit, an event condition determination unit, and an event process execution instruction unit. The registration event management unit manages the registration event from each node, and the reception event management unit manages the reception event from each node. Further, when an event occurrence notification is received from any of the nodes, the event condition determination unit compares the condition with the registered event registered in the registered event management unit and outputs the result, and the event processing execution instruction unit , When the determination result of the event condition determination unit matches, the node that registered the event is called. Further, the nodes other than the node having the event manager are provided with an event data processing request unit for registering an event to be monitored in the event manager and an event occurrence notification unit for notifying the occurrence of any event. is there.

[0008]

In the event processing system of the present invention, when an arbitrary node wants to be notified by another node, the event data processing request unit registers the event data. This event data is managed by the registered event management unit of the event manager. On the other hand, when any event occurs, the arbitrary node notifies the event manager of the event occurrence.
This event occurrence is received by the reception event management unit. Then, the event condition determination unit compares the event received by the reception event management unit with the event registered in the registered event management unit, and if the comparison results match, the event processing execution instruction unit determines Call the node that registered.

[0009]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of an event processing system of the present invention. The system shown in the figure shows nodes A, B, C, and D as a plurality of nodes that are connected via a network 1 and perform distributed processing, and the node D is equipped with an event manager 100. Node A,
In each of B and C, an application program (AP: hereinafter simply referred to as an application) 10 for performing processing related to event communication on the network 1,
20 and 30 are provided.

Each of the applications 10 to 30 is written in an object-oriented language, and the event data processing requesting units 11, 21, 31 and the event occurrence notifying units 12, 22, 3 are described.
2, event manager interface units 13, 23,
33 is provided. Since these configurations are common to each of the applications 10 to 30, the application 1
The configuration of 0 will be described as an example.

The event data processing request unit 11 registers the event data that the node A wants to be notified from the event manager 100, and requests the registered event data for processing such as searching, deleting, changing, and temporarily suspending monitoring. It has a function to do. Event occurrence notification unit 1
The node 2 has a function of notifying the event manager 100 of any event that occurs in the node A. Event manager interface section 1
3 has a function as an interface between the event data processing request unit 11, the event occurrence notification unit 12, and the event manager 100.

The event manager 100 provided in the node D comprises a registered event management unit 101, a reception event management unit 102, an event condition determination unit 103, and an event process execution instruction unit 104. The registration event management unit 101 manages registration events from the nodes A to C, and the reception event management unit 102 manages registration events from the nodes A to C.
It manages a reception event from C. In addition, the event condition determination unit 103 receives the event occurrence notification from any of the nodes, the registered event management unit 101.
The event processing execution instructing unit 104 further compares the registered event registered in the event with the condition and outputs the result. It has a function of activating the event processing function of the application that registered the.

FIG. 2 is an explanatory diagram showing the structure of event data managed by the event manager 100.
Indicates a registration event, and (b) indicates a notification event.
That is, (a) is information registered by the event data processing request unit 11 of each node in the event manager 100, and (b) shows information notified by the event occurrence notification unit 12 of each node to the event manager 100. ing.
The registered event is composed of an event ID (integer) as an identifier of the event, registration source data (reference) that requested monitoring of the event, an event to be monitored (reference), and a pointer (reference) to the next registered event. ing. still,
The data type is shown in parentheses, and the same applies to the following parentheses.

The above-mentioned registration source data is passed to an object ID (reference) registered from the event data processing request unit 11 in a node, a member function (reference) called when an event to be monitored occurs, and the member function. It has argument information as attached information. On the other hand, the monitoring event has a condition operator (integer) with the next monitoring event data linked by a link, an object ID (reference) of the monitoring target, and a type (character string) of the monitoring event. Here, the conditional operator includes a logical product, a logical sum,
Exclusive OR, negation, etc. can be used.

The notification event shown in (b) is composed of the object ID (reference) in which the event occurred, the type of event (character string), and attached information.
It should be noted that the target object of the event occurrence described above can specify all instances of a specific class, or arbitrary instances, in addition to the specific object instance.

Next, the operation of the event processing system configured as described above will be described. FIG. 3 is an explanatory diagram of processing in the event manager 100. In a distributed environment, applications 10 to 30 that have events to be monitored (AP1 and 2 correspond in the figure)
Registers event data in the event manager 100 (step S1). Event manager 1
In 00, the registered event management unit 101 stores this event data.

On the other hand, in the applications 10 to 30 (AP3 in the figure) in which the monitored event has occurred, the event occurrence notifying units 12 to 32 notify the event manager 100 of information regarding the event (step S).
2). In the event manager 100, the reception event management unit 102 temporarily stores the information. Then, in the event manager 100, the event condition determination unit 103
However, the conditions of these events are judged (step S
3) Only when the condition is satisfied, the event processing execution instruction unit 104 calls the function registered in the registered event management unit 101 with an appropriate argument. In addition, the registered event management unit 101 can search, delete, change, temporarily suspend monitoring, and the like for registered events based on a request from the event data processing request unit 11.

FIG. 4 is an explanatory diagram showing a concrete example of such an event processing system. This example shows an event process that starts a backup database server when any of the three database server objects existing on the network 1 goes down. Now, on the network 1, applications 10 to 10
There are nodes A, B, C and X on which 30 operates, and in each of them, objects Server1, Server2, Server3, Mana
ger runs and the event manager 100 is installed on node D.
Is assumed to exist (note that the configuration other than node X is shown in FIG.
Shown).

First, an application object (Manager on node X) that wants to manage the database server.
Registers the type of event to be monitored and the execution member function when the event occurs in the event manager 100 on node D as a registered event. The monitoring event is a server object (Server1 Object) that exists in three nodes.
When any of the on Node A to Server3 Object on Node C) generates the “System Down” event, the event processing function calls the Manager object (Mana
ger Object on Node X) RecoverServer function (Recove
rServer function). This function also returns the server object (Serv) that generated the event (System Down).
er Object of System Down) as an argument.

Each server object sends a notification event to the event manager 100 on the node D when trouble occurs for some reason. The notification event consists of the object where the event occurred, the type of event, and the data passed to the event processing function.
In this example, the Server2 object (Serv
er2 Object on Node B) raises the “SystemDown” event and sets the Server object itself as argument data (Server
2) Notification event is created and transferred to Object on Node B).

Event manager 100 on node D
Each time the notification event is transferred, the event condition determination unit 103 performs matching with the registered event managed by the registered event management unit 101. When the event condition determination unit 103 finds a notification event that matches the event condition of the registered event, it calls a member function for the object of the registration source data with the transferred argument data. Therefore, finally, on the node X, the member function RecoverServer is called from the event manager 100 on the node D with the Server2 object as an argument.

As described above, in the above embodiment, the event manager 100 is provided at any node on the network 1.
An application having an event to be monitored registers event data in the event manager 100, while an application in which some event has occurred notifies the event manager 100 of this event occurrence, and the event manager 100 reports these events. Since the registered member functions are called when they are collated and matched, the following effects can be obtained.

(1) Dynamic event monitoring By setting a monitoring event at an arbitrary time point, or by specifying a class name or an arbitrary object instead of a specific object instance, another application existing in the distributed environment Event notification is possible without knowing the details of the event. (2) Reducing the overhead of event processing Since the event manager manages event conditions in a unified manner, interaction with the object requested for event monitoring occurs only when absolutely necessary.

In this embodiment, in addition to the example shown in FIG.
In the electronic conference, the user input from each participant is distributed to all the conference attendees, or the field called groupware that requires collaborative processing such as electronic circulation boards, common editors, etc. Is effectively used for hypertext and piper media that realize various operations.

[0025]

As described above, according to the event processing system of the present invention, an event manager is provided in any one of a plurality of nodes forming a distributed environment, and this event manager is provided from each node. It manages the registered event and the notification event of, and when the event occurrence notification is received from any node, the condition is compared with the registered event, and if they match, the node that registered the event is called. Even applications that change dynamically can be easily managed, and the overhead of event processing can be reduced.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of an event processing system of the present invention.

FIG. 2 is an explanatory diagram showing the structure of event data in the event processing system of the present invention.

FIG. 3 is an explanatory diagram of processing of an event manager in the event processing system of the present invention.

FIG. 4 is an explanatory diagram of a specific example in the event processing system of the present invention.

[Explanation of symbols]

 1 Network 10, 20, 30 Application 11, 21, 31 Event Data Processing Request Section 12, 22, 32 Event Occurrence Notification Section 100 Event Manager 101 Registered Event Management Section 102 Received Event Management Section 103 Event Condition Judgment Section 104 Event Processing Execution Instruction Department

Claims (2)

[Claims] 1. An event processing system in a distributed environment in which distributed processing is executed by a plurality of nodes, wherein an event manager is provided in any one of the plurality of nodes, and the event manager is provided from each node. A registered event management unit that manages registered events, a reception event management unit that manages generated events notified from each node, and an event occurrence notification from any node,
The event condition determination unit that performs a condition comparison with the registered event registered in the registered event management unit and outputs a comparison result as to whether the conditions match, and the determination result in the event condition determination unit match. In this case, an event processing execution instructing unit that calls the node that registered the event is provided, and nodes other than the node having the event manager include an event data processing request unit that registers the event to be monitored in the event manager, and some event When an event occurs, the event processing system is provided with an event occurrence notification unit that notifies the event occurrence. 2. The event processing system according to claim 1, wherein the nodes other than the node having the event manager include a node name, an object name, a member processing function, and an argument for calling the event processing function. Register the registered event data consisting of data, the condition for monitoring the event, the object to be monitored, and the monitoring event data indicating the type of the event to be monitored, with the event manager, and for the registered event data, Event data processing request part that makes event data processing requests including search, deletion, change, and temporary suspension of monitoring, the object where the event occurred, the type of event, and the data passed to the event processing function And an event occurrence notification unit that notifies The event processing execution instruction unit of the event manager is configured to call the event processing function with the data to be passed to the event processing function as an argument at the node that registered the event when the determination result of the event condition determination unit matches. An event processing system characterized by being provided.