JP6364262B2 - Server, message processing system, message processing method and program - Google Patents

Description

  The present invention relates to a server, a message processing system, a message processing method, and a program suitable for use in processing a predetermined message.

  There has been proposed a monitoring system indicating that an event requiring alarm notification such as a failure has occurred in a monitoring target device (for example, Patent Document 1). The system mainly consists of a notification function for messages from the monitoring target, a reception function at the central management server, and an alarm transmission function. In order to participate in the monitoring system, the functions already built and introduced are introduced. It was.

  In the present application, a “message” is a data unit handled in an application layer in a TCP / IP (Transmission Control Protocol / Internet Protocol) network (that is, an application layer, a presentation layer, or a session layer in an OSI (Open Systems Interconnection) reference model). Means.

JP 2011-170459 A

  There are cases where there are many monitored devices all over the country, but each function of sending notification messages from the monitoring targets that make up the system, receiving notification messages at the central management server, and issuing alerts based on the received notification messages It has been integrated and it has not been easy to customize at various points during installation. Further, when the system is renewed, even if it is a renewal of only the function of accepting information from the sensor included in the monitoring target device, it is a whole renewal. Furthermore, when there are many types of alarms, even an alarm that is not necessary at a certain point must be dealt with as a whole system, and the function expansion is not easy.

  The present invention has been made in view of the above circumstances, and provides a server, a message processing system, a message processing method, and a program that can easily update or expand functions.

  In one aspect of the present invention, when a notification message including authentication information, first destination information, and notification information is received from a predetermined notification unit, when the validity of the notification message is confirmed based on the authentication information, A transfer message including information corresponding to the notification information is generated, the first destination information is designated as a destination and a communication unit that writes in a predetermined linkage unit, and second destination information is registered in the linkage unit. When the transfer message is received from the cooperation unit, a plurality of processing units each performing predetermined processing using the transfer message, and when the transfer message is written by the communication unit, designated as a destination of the transfer message The transfer message is delivered to one or a plurality of the processing units that have registered the second destination information corresponding to the first destination information. A server, characterized in that it comprises a linkage unit.

  One aspect of the present invention is characterized in that, in the server, the cooperation unit registers a plurality of the second destination information so as to be associated with each other.

  One aspect of the present invention is characterized in that, in the server, a domain different from that set in the communication unit is set in the notification unit.

  In one aspect of the present invention, in the server, the notification message is an HTTP message, and the communication unit restricts acceptance of the notification message based on at least one of a method and a header content included in the notification message. It is characterized by.

  In one aspect of the present invention, when a notification message including authentication information, first destination information, and notification information is received from a predetermined notification unit, when the validity of the notification message is confirmed based on the authentication information, A transfer message including information corresponding to the notification information is generated, the first destination information is designated as a destination and a communication unit that writes in a predetermined linkage unit, and second destination information is registered in the linkage unit. When the transfer message is received from the cooperation unit, a plurality of processing units each performing predetermined processing using the transfer message, and when the transfer message is written by the communication unit, designated as a destination of the transfer message The transfer message is delivered to one or a plurality of the processing units that have registered the second destination information corresponding to the first destination information. A server and a linkage unit, a message processing system characterized by comprising said notification unit.

  In one aspect of the present invention, when the communication unit receives a notification message including authentication information, first destination information, and notification information from a predetermined notification unit, the validity of the notification message is confirmed based on the authentication information. A transfer message including information corresponding to the notification information is generated, the first destination information is designated as a destination and written to a predetermined linkage unit, and a plurality of processing units are provided to the linkage unit. Each of the second destination information is registered, and when the transfer message is received from the cooperation unit, a predetermined process is performed using the transfer message, and the cooperation unit sends the transfer message to the communication unit. If written, the one or more previous registrations of the second destination information corresponding to the first destination information designated as the destination of the transfer message A message processing method characterized by comprising the step of delivering the forwarding message to the processor.

  In one aspect of the present invention, when a notification message including authentication information, first destination information, and notification information is received from a predetermined notification unit, when the validity of the notification message is confirmed based on the authentication information, A transfer message including information corresponding to the notification information is generated, the first destination information is designated as a destination and a communication unit that writes in a predetermined linkage unit, and second destination information is registered in the linkage unit. When the transfer message is received from the cooperation unit, a plurality of processing units each performing predetermined processing using the transfer message, and when the transfer message is written by the communication unit, designated as a destination of the transfer message The transfer message is delivered to one or a plurality of the processing units that have registered the second destination information corresponding to the first destination information. In the server comprising the cooperation unit, the communication unit causes the computer to execute a step of designating the generated transfer message in the cooperation unit by designating the first destination information as the destination. .

  According to the present invention, for example, even when a processing unit that performs alarm transmission or the like is changed or added, the processing unit registers the second destination information in the cooperation unit so as to correspond to the first destination information. The notification message transmitted by the notification unit can be processed by a desired processing unit. Therefore, it is possible to provide a server, a message processing system, a message processing method, and a program that can easily update or expand functions.

It is a block diagram which shows the structure of the message processing system of embodiment of this invention. It is a block diagram which shows the structural example of the cooperation component of this embodiment. It is a block diagram which shows the structural example of the destination information list of this embodiment. It is a block diagram which shows the structural example of the destination information corresponding table | surface of this embodiment. It is a block diagram which shows the structural example of the notification message of this embodiment. It is a block diagram which shows the structural example of the transfer message of this embodiment. It is a sequence diagram which shows the procedure of the process of the message processing system of this embodiment. It is another sequence diagram which shows the procedure of the process of the message processing system of this embodiment. It is explanatory drawing which shows the example of registration of the destination information list of this embodiment. It is explanatory drawing which shows the example of registration of the destination information corresponding table | surface of this embodiment.

  Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a configuration diagram showing a logical configuration of the message processing system according to the present embodiment.
The message processing system 1 shown in the figure includes a Web server 2 and an external server 3. The Web server 2 is a physical server or a virtual server that provides a message processing function. The external server 3 is a physical server or a virtual server that transmits and receives messages to and from the Web server 2. The Web server 2 and the external server 3 are connected via a wired or wireless network (not shown). A plurality of external servers 3 can be provided. Further, the Web server 2 and the external server 3 can be configured using a plurality of computers, for example, by cloud technology. Note that the Web server 2 and the external server 3 may be configured using a personal computer, a portable information terminal, a smartphone, or the like.

  The Web server 2 includes a communication component 21, an alarm processing component 22, a user information processing component 23, and a cooperation component 24. The external server 3 includes an alarm notification component 31 and a user information notification component 32. Here, the component means a partized program. In addition, each component in the present embodiment has a function of transmitting and receiving messages in the application layer in the TCP / IP network. Each component is configured as a program that operates on an OS (Operating System) executed by each server, for example, or is configured as a program that operates under the management of a predetermined framework executed on the OS. be able to. In addition, the cooperation component 24 may be included in the OS or framework kernel. Each component can operate in cooperation with other components not shown.

The alarm notification component 31 included in the external server 3 generates, for example, a notification message 41 indicating that such an event has occurred when an event that requires an alarm notification such as a failure occurs in the monitoring target device, Transmit to the communication component 21. When the user information notification component 32 needs to notify any information set by the user, the user information notification component 32 generates a notification message 42 indicating the information and transmits it to the communication component 21.
The communication component 21 receives the notification message 41 transmitted by the alarm notification component 31 or receives the notification message 42 transmitted by the user information notification component 32. Further, the communication component 21 generates a transfer message 51 based on the notification message 41 or the notification message 42 and writes it in the cooperation component 24. At that time, the communication component 21 performs a predetermined authentication process when receiving the notification message 41 or 42, generates a transfer message 51 when the validity of the notification message 41 or 42 is confirmed, and generates a link component 24. Write to. In addition, the communication component 21 returns a result of authentication processing, information indicating success or failure of transfer of the transfer message 51 to the transfer destination, or information indicating a response content from the transfer destination to the alarm notification component 31 and the user information notification component 32. have. In this case, the authentication information held on the Web server 2 side used in the authentication process can be shared with the authentication information set for the processing components such as the alarm processing component 22 and the user information processing component 23, for example. Further, the communication component 21 can also restrict access based on the role of the notification component of the transmission source in the authentication process even if authentication is possible. Here, the role-based access restriction is a mechanism in which notification components are grouped by role, and access permission is given to a group unit or a specific member in the group based on a predetermined setting file.

  Further, when the notification message 41 or 42 is configured as an HTTP request message as will be described later, the communication component 21 accepts the notification message 41 or 42 based on at least one of the method or the header content included in the notification message. You may have the function to restrict | limit. This means a restriction by CORS (Cross Origin Resource Sharing). In other words, when the correct CORS is set in advance in the notification message 41 or 42, the notification message 41 or 42 is permitted to be accepted. Thereby, for example, the transmission source of the request, the HTTP method that can be transmitted, and the HTTP header can be restricted.

  The cooperation component 24 transmits the transfer message 51 written by the communication component 21 to the alarm processing component 22 and the user information processing component 23 as a transfer message 52 and a transfer message 53. At that time, the cooperation component 24 selects a transfer destination based on “destination information” registered in the cooperation component 24 by the alarm processing component 22 and the user information processing component 23. For this reason, when the communication component 21 writes the transfer message 51 in the cooperation component 24, the communication component 21 designates the destination information as a destination and performs writing in the cooperation component 24.

  The cooperation component 24 supports a plurality of types of transfer methods. That is, the cooperation component 24 corresponds to a method of transmitting one transfer message 51 to one component and a method of transmitting one transfer message 51 to a plurality of components. In addition, the cooperation component 24 corresponds to a method for requesting a reply to a transmission source such as the transfer messages 52 and 53 and a method for not requesting a transmission destination component such as the transfer messages 52 and 53. Here, the transmission source of the transfer messages 52, 53 and the like is the communication component 21 directly in communication via the cooperation component 24. However, the alarm notification component 31 and the user information notification component 32 are indirectly functioned as a transmission source by transmitting the reply content to the alarm notification component 31 and the user information notification component 32 via the communication component 21. Can do. Further, when the cooperation component 24 requests a reply to the transmission destination component, the cooperation component 24 has a method of waiting the transmission source component until the reply is made (referred to as a synchronous method) and a method of not waiting (referred to as an asynchronous method). It corresponds. These methods can be specified by the communication component 21 when the communication component 21 writes the transfer message 51 to the cooperation component 24, for example.

  When receiving the transfer message 52 from the cooperation component 24, the alarm processing component 22 performs a predetermined process using the transfer message 52. For example, the alarm processing component 22 performs a pop-up display corresponding to the content of the transfer message 52 on a monitor screen monitored by a not-shown supervisor, accumulates notified information, and updates history information. To do.

  When the user information processing component 23 receives the transfer message 53 from the cooperation component 24, the user information processing component 23 performs a predetermined process using the transfer message 53. The user information processing component 23 performs, for example, a pop-up display corresponding to the content of the transfer message 52 on a monitor screen monitored by an unillustrated supervisor, or the notified information, like the alarm processing component 22. Accumulate and update history information.

  In the configuration shown in FIG. 1, the domain set in the communication component 21 can be different from the domains set in the alarm notification component 31 and the user information notification component 32. In this case, the communication component 21 can receive a notification message 41, a notification message 42,... From a plurality of alarm notification components 31, user information notification components 32,.

  Next, a configuration example of the cooperation component 24 will be described with reference to FIGS. FIG. 2 is a configuration diagram showing the functional configuration of the cooperation component 24 divided into blocks. FIG. 3 is a configuration diagram showing a configuration example of the destination information list 245 shown in FIG. FIG. 4 is a configuration diagram showing a configuration example of the destination information correspondence table 246 shown in FIG. As illustrated in FIG. 2, the cooperation component 24 includes a cooperation control unit 241, a message storage unit 242, a message transmission / reception unit 243, and a destination information storage unit 244. The destination information storage unit 244 includes a destination information list 245 and a destination information correspondence table 246.

  The cooperation control unit 241 controls the message storage unit 242, the message transmission / reception unit 243, and the destination information storage unit 244. The message storage unit 242 stores the transfer message 51 written by the communication component 21 in association with the destination information specified by the communication component 21. The message transmission / reception unit 243 receives the transfer message 51 shown in FIG. 1 from the communication component 21, or the transfer message 51 stored in the message storage unit 242 as the transfer message 52 or 53, the alarm processing component 22 or the user information processing component 23. Or send to. When the transfer message 51 is written by the communication component 21, the cooperation controller 241 registers the alarm processing component 22 or the user information processing component 23 in which the destination information corresponding to the destination information specified as the destination of the transfer message 51 is registered, or For both of them, control is performed to deliver the transfer message 51 as the transfer message 52 or 53. At that time, the destination component is determined by the cooperation control unit 241 to refer to the registered contents of the destination information list 245 and the registered contents of the destination information correspondence table 246.

  The destination information list 245 is a table showing a list of correspondence relationships between a plurality of sets of destination information and component identifiers, for example, as shown in FIG. The destination information is information indicating the component of the transmission destination when the cooperation component 24 transmits the transfer message 52 or the transfer message 53, and can be composed of, for example, arbitrary characters or numbers. The component identifier is information for identifying each component being executed in the Web server 2 and can be constituted by a numerical value, for example. The destination information is registered in the destination information list 245 in response to a request from each component such as the alarm processing component 22 and the user information processing component 23. The component identifier is set by, for example, an OS executed on the Web server 2 when each component is started, or set by a framework kernel executed on the OS. In the cooperation component 24, when registration of destination information is requested from each component such as the alarm processing component 22 and the user information processing component 23, the cooperation control unit 241 obtains the component identifier of each request source component from the OS or the framework. The destination information and the component identifier are associated with each other and registered in the destination information list 245.

  In the example illustrated in FIG. 3, for example, if “destination information A” is the destination information requested to be registered by the alarm processing component 22 illustrated in FIG. 1, the component identifier of the alarm processing component 22 is, for example, “component The identifier X ”is registered in association with“ destination information A ”. Similarly, for example, if “destination information B” is the destination information requested to be registered by the user information processing component 23 shown in FIG. 1, the component identifier of the user information processing component 23 is used as shown in FIG. For example, “component identifier Y” is registered in association with “destination information B”.

  In the destination information list 245, the information for identifying each component registered in association with the destination information is not limited to the identifier of each component as described above, and is, for example, a combination of an IP address and a port number. You can also

  Further, as shown in FIG. 4, the destination information correspondence table 246 has each destination information registered in the destination information list 245 (referred to as “destination information 1”) and each destination information 1 as a destination. 10 is a table showing a list of correspondence relationships with additional destination information (this is referred to as “destination information 2”) when a transfer message is added to the destination information 1 and transferred. That is, a plurality of pieces of destination information are registered in the destination information correspondence table 246 so that they can be associated with each other. Each “destination information 2” can be not set, or two or more pieces of destination information can be set. Each “destination information 2” can be registered in response to a request from each component corresponding to “destination information 2”. In the example shown in FIG. 4, “destination information 2” is not registered for “destination information A”. On the other hand, “destination information A” is registered as “destination information 2” in “destination information B”. In this case, the “destination information A” “destination information” is stored in the destination information list 245 as its own destination information (in the example of FIG. 3, the component in which “component identifier X” is set). “Destination information A” is registered as “Destination information 2” in association with “Information B”. When registration is performed as illustrated in FIG. 3, a transfer message having “destination information A” as a transfer destination is transmitted to one component corresponding to “destination information A”. On the other hand, the transfer message having “destination information B” as the transfer destination is transmitted to the component corresponding to “destination information A” in addition to the component corresponding to “destination information B”.

  Next, a configuration example of the notification messages 41 and 42 shown in FIG. 1 will be described with reference to FIG. The notification messages 41 and 42 (hereinafter, the notification message 41 will be described as a representative) shown in FIG. 5 have the same configuration and are configured as HTTP requests that are requests based on HTTP. The notification message 41 includes a request line 411, a message header 412, and a message body 413. The request line 411 includes a method 414 and a URI (Uniform Resource Identifier) 415. The method 414 is a method that is executed by the resource identified by the URI 415. In the notification message 41 of this embodiment, “POST (post)”, which is a method for transmitting data to the server, is set in the method 415. The URI 415 is set with the URI of the communication component 21 shown in FIG. In addition, the request line 411 can include an HTTP version and the like.

  The message header 412 includes additional information delivered to the communication component 21. The notification message 41 of this embodiment includes at least authentication information 416. The authentication information 416 is information used for authentication processing, for example, information obtained by encoding a user name and a password by a predetermined method. The authentication information 416 can be set according to, for example, basic authentication (basic authentication) defined by HTTP. In addition, the message header 412 can include information such as an application type, a character set, an encoding format, an access destination domain, and an access source domain.

  The message body 413 includes a main body of information that the alarm notification component 31 illustrated in FIG. 1 transmits to a predetermined component via the communication component 21 and the cooperation component 24. The notification message 41 of the present embodiment includes destination information 417, control information 418, and notification information 419. The notification information 419 includes the content of information that the alarm notification component 31 wishes to notify the alarm processing component 22, for example. The notification information 419 includes, for example, one or more argument names indicating information to be notified, argument types, and argument values. The destination information 417 includes destination information registered in the cooperation component 24 by the notification destination component of the notification message 41. For example, when the alarm notification component 31 notifies the alarm processing component 22 of the notification information 419, the destination information registered by the alarm processing component 22 with respect to the cooperation component 24 (for example, “destination information A” illustrated in FIG. 9). Is set in the destination information 417. In the control information 418, information specifying a message transfer method by the cooperation component 24 is set. For example, information indicating whether the transfer method is the synchronous method or the asynchronous method is set.

  Next, configuration examples of the transfer messages 51, 52, and 53 shown in FIG. 1 will be described with reference to FIG. Transfer messages 51, 52, and 53 shown in FIG. 6 (hereinafter, transfer message 51 will be described as a representative) have the same configuration, for example, a text message. The transfer message 51 includes notification information 511 that is information corresponding to the notification information 419 included in the notification message 41 illustrated in FIG. The notification information 511 may be the same as the notification information 419, or a part of the information may be omitted. The notification information 511 may be information obtained by converting the format, encoding format, and the like of the notification information 419 into a predetermined one. Further, the notification information 511 may include all or part of the message header 412 included in the notification message 41 illustrated in FIG.

  Next, a processing procedure of the message processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 7 is a sequence diagram showing a processing procedure of the message processing system 1 according to the present embodiment described with reference to FIGS. 1 to 6. Note that “destination information A” is set in the alarm processing component 22 in advance. In the alarm processing component 22, “destination information B” is set as destination information associated with “destination information A”. Further, “destination information B” is set in the user information processing component 23. In the alarm notification component 31, “destination information A” is set as the destination information of the notification destination component of the notification message 41. In the user information notification component 32, “destination information B” is set as the destination information of the notification destination component of the notification message.

  When each component is activated in the Web server 2, the alarm processing component 22 registers “destination information A” in association with its own component (that is, the alarm processing component 22) with respect to the cooperation component 24, and “destination information A "Is registered in association with" destination information B "(step S101). Further, the user information processing component 23 registers “destination information B” in association with the component (that is, the user information processing component 23) in the cooperation component 24 (step S102). Here, “destination information A” and “destination information B” are registered in the destination information list 245 (FIGS. 2 and 3) of the linkage component 24 as shown in FIG. Further, as shown in FIG. 4, “destination information A” is registered in association with “destination information B” in the destination information correspondence table 246 of the linkage component 24. In this case, it is assumed that the component identifier of the alarm processing component 22 is “component identifier X”, and the component identifier of the user information processing component 23 is “component identifier Y”.

  Although not shown, the communication component 21 sends predetermined destination information to the cooperation component so that a reply from another component such as the alarm notification component 31 and the user information notification component 32 can be received via the cooperation component 24. 24 can be registered.

  Next, in the external server 3, if the alarm notification component 31 detects a predetermined alarm event, the alarm notification component 31 generates a notification message 41 in which “destination information A” is set in the destination information 417 (FIG. 5). And transmitted to the communication component 21 (step S201). The communication component 21 determines whether to accept the notification message 41 based on at least one of the method 414 included in the notification message 41 or the content of the message header 412, and performs authentication processing based on the authentication information 416 included in the notification message 41. It performs (step S202). In step S202, for example, the communication component 21 rejects the notification message 41 when the method 414 included in the notification message 41 is not “POST”, or the transmission source domain information included in the message header 412 is other than a predetermined domain. In some cases, the notification message 41 is rejected. Further, the communication component 21 refers to a predetermined database in the Web server 2 and determines whether or not the authentication information 416 is valid.

  Next, the communication component 21 generates the transfer message 51 including information corresponding to the notification information 419 included in the notification message 41 when the validity of the notification message 41 is confirmed in the authentication processing in step S202. The “destination information A” included in the notification message 41 as the destination information 417 is designated as the destination, and the transfer message 51 is written to the cooperation component 24 (S203). In step S203, the communication component 21 refers to the control information 418 included in the notification message 41, and designates whether the message transfer method is “synchronous method” or “asynchronous method” to the cooperation component 24. Do. Here, it is assumed that “asynchronous method” is designated.

  When the transfer message 51 is written by the communication component 21, the cooperation component 24 sends the transfer message 51 to the component in which the destination information corresponding to the “destination information A” designated as the destination of the transfer message is registered. Transmit (in this case, as transfer message 52) and deliver (step S204). In step S204, the linkage component 24 refers to the destination information list 245 (FIG. 3) and confirms that “component identifier X” of the alarm processing component 22 is registered in association with “destination information A”. Detect. Further, in step S204, the linkage component 24 refers to the destination information correspondence table 246 (FIG. 4), and detects that no other destination information is associated with “destination information A”. Therefore, in this case, in step S204, the linking component 24 uses the alarm processing component in which the component that registered the destination information corresponding to the “destination information A” designated as the destination of the transfer message 51 is set to “component identifier X”. 22 is detected, and the transfer message 51 is transferred to the alarm processing component 22 as the transfer message 52.

  Next, when the transfer message 52 is received in step S204, the alarm processing component 22 performs a predetermined process using the transfer message 52 (step S205).

  Next, in the external server 3, if the user information notification component 32 detects a predetermined notification event, the user information notification component 32 sets the notification message 42 in which “destination information B” is set in the destination information 417 (FIG. 5). Is transmitted to the communication component 21 (step S301). The communication component 21 performs authentication processing in the same manner as in step S202 (step S302).

  Next, when the validity of the notification message 42 is confirmed in the authentication process in step S302, the communication component 21 generates a transfer message 51 including information corresponding to the notification information 419 included in the notification message 42, The “destination information B” included in the notification message 42 as the destination information 417 is designated as the destination, and the transfer message 51 is written to the cooperation component 24 (S303). In step S303, the communication component 21 refers to the control information 418 included in the notification message 42, and designates the message transfer method as “asynchronous method”.

  Next, when the transfer message 51 is written by the communication component 21, the cooperation component 24 transfers the transfer to the component in which the destination information corresponding to “destination information B” designated as the destination of the transfer message is registered. The message 51 is transmitted (in this case, as transfer messages 52 and 53) and delivered (step S304). In step S304, the linkage component 24 refers to the destination information list 245 (FIG. 3), and “destination information B” is registered in association with “component identifier Y” of the user information processing component 23. Is detected. Further, in step S304, the cooperation component 24 refers to the destination information correspondence table 246 (FIG. 4), and detects that “destination information A” is associated with “destination information B”. Therefore, in this case, in step S304, the cooperation component 24 determines that the component in which the destination information corresponding to the “destination information B” designated as the destination of the transfer message 51 is registered is the user information processing in which the “component identifier Y” is set. It is detected that the component 23 is an alarm processing component 22 in which “component identifier X” in which “destination information A” is registered is set. Therefore, in step S <b> 304, the cooperation component 24 transfers the transfer message 51 as the transfer message 53 to the user information processing component 23 and transfers it as the transfer message 52 to the alarm processing component 22.

  Next, when the transfer message 52 is received in step S305, the alarm processing component 22 performs a predetermined process using the transfer message 52 (step S305). When the transfer message 53 is received in step S305, the user information processing component 23 performs a predetermined process using the transfer message 53 (step S306).

  Next, with reference to FIG. 8, the process procedure when the alarm processing component 25 shown in FIG. 8 is newly added to the Web server 2 of FIG. 1 will be described. It is assumed that “destination information C” is set in the alarm processing component 25. The alarm processing component 25 is set to register “destination information C” in association with “destination information A”. In FIG. 8, the same steps as those shown in FIG. 7 are denoted by the same reference numerals. Hereinafter, a procedure different from that described mainly with reference to FIG. 7 will be described.

  In the example shown in FIG. 8, when each component is activated in the Web server 2, the alarm processing component 22 registers the destination information with the linkage component 24 (step S <b> 101), and the user information processing component 23 sends the destination information to the linkage component. 24 (step S102), the alarm processing component 25 registers “destination information C” in association with the component (that is, the alarm processing component 25) in the cooperation component 24 (step S103). .

  Here, “destination information A”, “destination information B”, and “destination information C” are registered in the destination information list 245 of the linkage component 24 as shown in FIG. Further, in the destination information correspondence table 246 included in the linkage component 24, “destination information A” is registered in association with “destination information B” as shown in FIG. On the other hand, “destination information C” is registered in association with each other. In this case, it is assumed that the component identifier of the alarm processing component 25 is “component identifier Z”.

  Next, in the external server 3, if the alarm notification component 31 detects a predetermined alarm event, the alarm notification component 31 generates a notification message 41 in which “destination information A” is set in the destination information 417 (FIG. 5). And transmitted to the communication component 21 (step S201). Next, the communication component 21 executes the authentication process in step S202 and the write process in step S203.

  When the transfer message 51 is written by the communication component 21, the cooperation component 24 sends the transfer message 51 to the component in which the destination information corresponding to the “destination information A” designated as the destination of the transfer message is registered. Transmit and deliver (step S204a). In step S204a, the linking component 24 refers to the destination information list 245 (FIG. 9) and confirms that “component identifier X” of the alarm processing component 22 is registered in association with “destination information A”. Detect. Further, in step S204a, the linkage component 24 refers to the destination information correspondence table 246 (FIG. 10) and detects that “destination information C” is associated with “destination information A”. Therefore, in this case, in step S204a, the cooperation component 24 determines that the component that registered the destination information corresponding to the “destination information A” designated as the destination of the transfer message 51 is the alarm processing component in which the “component identifier X” is set. 22 and the alarm processing component 25 in which “component identifier Z” in which “destination information C” is registered is detected. Accordingly, in step S <b> 204 a, the cooperation component 24 transfers the transfer message 51 to the alarm processing component 22 and also to the alarm processing component 25.

  Next, when the transfer message is received in step S204a, the alarm processing component 22 performs a predetermined process using the transfer message (step S205). When the transfer message is received in step S204a, the alarm processing component 25 performs a predetermined process using the transfer message (step S206).

  As described above, according to the present embodiment, for example, in the Web server 2, even when an alarm processing component that performs alarm transmission or the like or a user information processing component is changed or added, a notification message is desired as follows. The processing component can be handed over to perform desired processing. That is, in the external server 3, each component of the Web server 2 cooperates with appropriate destination information so as to correspond to the destination information preset as the notification destination of the notification message for the alarm notification component, the user information notification component, etc. Register for the component. As a result, the external server 3 includes the newly installed processing component in the Web server 2 for the notification message transmitted by each notification component without changing the settings of the notification component such as the alarm notification component and the user information notification component. It can be delivered to a desired processing component, and a desired process can be performed. Therefore, it is possible to easily update or expand functions in the message processing system 1.

  In the present embodiment, a notification component such as an alarm notification component and a user information notification component, a processing component such as an alarm processing component and a user information processing component, and a communication component that receives a notification message transmitted by the notification component, Since the configuration is separated, the range of influence can be reduced when the function is expanded compared to a program in which these are integrally combined, so that the expandability is high. Moreover, since the independence is high, the influence is small even when the system on the opposite server fails. Further, in the present embodiment, log management can be performed relatively easily because communication between the components is performed via the cooperation component.

  The embodiment of the present invention is not limited to the above-described embodiment, and for example, the following configuration can be provided. For example, each step shown in FIGS. 7 and 8 may include sending and receiving a plurality of messages between the components. For example, the destination information registration process in step S101 or the like is configured by dividing the alarm processing component 22 into a step of registering the destination information with the cooperation component 24 and a step of registering the destination information as a message receiving side. Can do. The notification messages 41 and 42 and the transfer messages 51 to 53 may be described according to, for example, JSON (JavaScript (registered trademark) Object Notation), or may be described according to XML (Extensible Markup Language), Or they may be mixed.

  In the above embodiment, the message processing system 1 includes one or more computer systems. Then, a program for realizing the functions of the above-described units is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed, thereby executing the processing of each unit described above. You may go. Here, the “computer system” includes an OS and hardware such as peripheral devices.

Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, “computer-readable recording medium” means a program that dynamically holds a program for a short time when the program is transmitted via a network such as the Internet or a communication line such as a telephone line. It also includes those that hold programs for a certain period of time, such as volatile memory inside computer systems that serve as servers and clients. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

[1] In the above embodiment, the Web server 2 sends a notification message 41 including authentication information 416, destination information 417 (first destination information), and notification information 419 to a predetermined notification component such as the alarm notification component 31. When received from the (notification unit), when the validity of the notification message 41 is confirmed based on the authentication information 416, the transfer message 51 including information corresponding to the notification information 419 is generated and the destination information 417 (first destination information) ) Is designated as a destination, and the communication component 21 (communication unit) is written to the predetermined cooperation component 24 (cooperation unit). Further, the Web server 2 registers the destination information (second destination information) with respect to the cooperation component 24 (cooperation unit), and sends a transfer message 51 (= transfer message 52 or 53) from the cooperation component 24 (cooperation unit). A plurality of processing components (processing units) such as an alarm processing component 22 and a user information processing component 23 that respectively perform predetermined processing using the transfer message when received. Further, when the transfer message 51 is written by the communication component 21 (communication unit), the Web server 2 receives the destination information (second destination information) corresponding to the destination information 417 (first destination information) specified as the destination of the transfer message. Cooperation component 24 (cooperation) that delivers the transfer message 51 (= transfer message 52 or 53) to one or a plurality of alarm processing components 22 and user information processing components 23 that have registered the destination information) Part).
Thereby, for example, even when a processing component (processing unit) such as the alarm processing component 22 that performs alarm transmission or the like is changed or added, the processing component (first destination information) is processed so as to correspond to the destination information 417 (first destination information). The processing unit) registers the destination information (second destination information) in the cooperation component 24 (cooperation unit), so that the notification messages 41, 42 and the like transmitted by a predetermined notification component (notification unit) such as the alarm notification component 31 are transmitted. Processing can be performed by a desired processing component (processing unit). Therefore, it is possible to facilitate renewal and expansion of functions in a plurality of processing components (processing units) and the message processing system 1.

[2] The cooperation component 24 (cooperation unit) can register a plurality of pieces of destination information (second destination information) registered by a plurality of processing components (processing units) so that they can be associated with each other.
As a result, even when a processing component (processing unit) is newly added, a notification message transmitted by the existing notification component (notification unit) can be changed to a new processing component without changing the existing notification component (notification unit). It can be received by the (processing unit).

[3] A domain different from the domain set in the communication component 21 (communication unit) may be set in a predetermined notification component (notification unit) such as the alarm notification component 31.
As a result, for example, notification components (notification units) can be distributed over a wide range.

[4] Then, when the notification message 41 or the like is an HTTP message, the communication component 21 (communication unit) performs the processing based on at least one of the contents of the method 414 or the message header 412 (header) included in the notification message 41 or the like. Acceptance of the notification message 41 or the like can be restricted.
Thereby, it is possible to realize access restriction by CORS.

  Although the embodiment of the present invention has been described above, the message processing system 1 of the present invention is not limited to the above illustrated example, and various modifications are made without departing from the gist of the present invention. Of course you get.

1 message processing system,
2 Web server,
21 Communication component, 22 Alarm processing component, 23 User information processing component, 24 Cooperation component, 25 Alarm processing component,
242 message storage unit, 243 message transmission / reception unit, 244 destination information storage unit,
245 Destination information list 246 Destination information correspondence table 3 External server
31 Alarm notification component, 32 User information notification component,
41-42 notification messages,
412 Message header, 414 method, 416 authentication information, 417 destination information, 419 notification information,
51-53 Transfer message,
511 Notification information

Claims (7)

When a notification message including authentication information, first destination information, and notification information is received from a predetermined notification unit, when the validity of the notification message is confirmed based on the authentication information, information corresponding to the notification information is displayed. A communication unit that generates a transfer message including the first destination information as a destination and writes the first destination information in a predetermined cooperation unit;
A plurality of processing units that respectively register the second destination information with respect to the cooperation unit, and that perform predetermined processing using the transfer message when the transfer message is received from the cooperation unit;
When the transfer message is written by the communication unit, the transfer message is transferred to one or a plurality of processing units that have registered the second destination information corresponding to the first destination information specified as a destination of the transfer message. A server comprising a linkage unit that delivers a message. The server according to claim 1, wherein the cooperation unit registers a plurality of the second destination information so as to be associated with each other. The server according to claim 1 or 2, wherein a domain different from that set in the communication unit is set in the notification unit. The notification message is an HTTP message;
The server according to any one of claims 1 to 3, wherein the communication unit restricts acceptance of the notification message based on at least one of a method and a header content included in the notification message. When a notification message including authentication information, first destination information, and notification information is received from a predetermined notification unit, when the validity of the notification message is confirmed based on the authentication information, information corresponding to the notification information is displayed. A communication unit that generates a transfer message including the first destination information as a destination and writes the first destination information in a predetermined cooperation unit;
A plurality of processing units that respectively register the second destination information with respect to the cooperation unit, and that perform predetermined processing using the transfer message when the transfer message is received from the cooperation unit;
When the transfer message is written by the communication unit, the transfer message is transferred to one or a plurality of processing units that have registered the second destination information corresponding to the first destination information specified as a destination of the transfer message. A server comprising a linkage unit that delivers a message;
A message processing system comprising: the notification unit. When the communication unit receives a notification message including authentication information, first destination information, and notification information from a predetermined notification unit, when the validity of the notification message is confirmed based on the authentication information, the notification information Generating a transfer message including information corresponding to the first destination information and designating the first destination information as a destination and writing it in a predetermined linkage unit;
A plurality of processing units respectively registering the second destination information to the cooperation unit, and performing a predetermined process using the transfer message when the transfer message is received from the cooperation unit;
One or a plurality of the processes in which the cooperation unit registers the second destination information corresponding to the first destination information designated as a destination of the transfer message when the transfer message is written by the communication unit Delivering the transfer message to a section. When a notification message including authentication information, first destination information, and notification information is received from a predetermined notification unit, when the validity of the notification message is confirmed based on the authentication information, information corresponding to the notification information is displayed. A communication unit that generates a transfer message including the first destination information as a destination and writes the first destination information in a predetermined cooperation unit;
A plurality of processing units that respectively register the second destination information with respect to the cooperation unit, and that perform predetermined processing using the transfer message when the transfer message is received from the cooperation unit;
When the transfer message is written by the communication unit, the transfer message is transferred to one or a plurality of processing units that have registered the second destination information corresponding to the first destination information specified as a destination of the transfer message. In a server comprising a linkage unit that delivers a message,
A program that causes the computer to execute a step in which the communication unit designates the first destination information as a transmission destination and writes the generated transfer message in the cooperation unit.

Images