JP6649527B2 - Message management device and message management method - Google Patents

Description

  The present invention relates to a message management device and a message management method.

  2. Description of the Related Art Conventionally, various types of data are input to an accounting system. For example, Patent Literature 1 discloses a system that outputs data based on a setting table that defines items to be output to an accounting system and the like (for example, see Patent Literature 1).

JP 2011-181024 A

  On the application side that provides data, it is necessary to provide data so as to conform to the data acquisition format on the data acquisition side. In addition, when there are a plurality of other applications for acquiring data, the application providing the data needs to correspond to the data acquisition format of each of the plurality of other applications, so that it takes time to develop the application. There was a problem.

  Therefore, the present invention has been made in view of these points, and an object of the present invention is to provide a message management device capable of reducing a load on an application providing data.

  A message management device according to a first aspect of the present invention includes a first registration unit configured to store configuration information indicating a configuration of a message output from each of a plurality of applications in a storage unit, and an address indicating an output destination of the message. A second registration unit that stores the message in the storage unit, an acquisition unit that acquires a message of the configuration information stored in the storage unit from the application, and when the acquisition unit acquires the message, An output unit that outputs the message to an address stored as an output destination of the message.

  The first registration unit receives the configuration information to be stored in the storage unit from a terminal, and stores similar configuration information when the configuration information is similar to the configuration information already stored in the storage unit. Notification information indicating that the notification has been performed may be output to the terminal.

  The first registration unit may output similar configuration information to the terminal when the configuration information stored in the storage unit is similar to the configuration information already stored in the storage unit.

  The first registration unit associates the configuration information with authority information indicating an acquisition authority of a message corresponding to the configuration information and stores the association information in the storage unit, and the second registration unit allows a user who uses the message to Accepts user information from a corresponding user terminal, selects one or more configuration information from the storage unit based on the user information and the authority information, and responds to a message to be output from the one or more configuration information. Selection of one piece of configuration information to be performed may be received.

The acquisition unit is provided in plurality corresponding to each of a plurality of messages, and the first registration unit receives the function to be executed by the acquisition unit corresponding to the message of the registered configuration information, and acquires the acquisition unit. May implement the function.
The message management device further includes a distribution unit that distributes a message received from the application to one of the acquisition units corresponding to the message, among the acquisition units provided in plurality corresponding to the plurality of messages. May be provided.

  A message management method according to a second aspect of the present invention includes a step of storing, in a storage unit, configuration information indicating a configuration of a message output from each of a plurality of applications executed by a computer, and indicating an output destination of the message. Storing an address in the storage unit; obtaining, from the application, a message of the configuration information stored in the storage unit; when a message is obtained in the obtaining step, Outputting the message to an address stored as an output destination of the message.

  ADVANTAGE OF THE INVENTION According to this invention, there exists an effect that the burden on the application side which provides data can be reduced.

It is a figure showing the outline (the 1) of the message management device concerning a 1st embodiment. It is a figure showing the outline (the 2) of the message management device concerning a 1st embodiment. It is a figure showing the composition of the message management device concerning a 1st embodiment. 6 is a flowchart illustrating a flow of a process in which the message management device according to the first embodiment registers configuration information. FIG. 4 is a diagram illustrating an example of information stored in a configuration information storage unit according to the first embodiment. 5 is a flowchart illustrating a flow of a process in which the message management device according to the first embodiment registers output destination information. FIG. 5 is a diagram illustrating an example of information stored in an output destination information storage unit according to the first embodiment. 6 is a flowchart illustrating a flow of processing from when the output source application according to the first embodiment outputs a message to when the message is output to the output destination application. It is a flowchart which shows the flow of the process which the message management apparatus which concerns on 2nd Embodiment registers configuration information.

<First embodiment>
[Overview of Message Management Device 1]
FIG. 1 and FIG. 2 are diagrams illustrating an outline of the message management device 1 according to the first embodiment.

  The message management device 1 is a server for providing a message management service for managing exchange of messages output from applications belonging to the content application group 4. The message management device 1 is managed by a company that provides a message management service.

  The content application group 4 includes an output source application 41 that is a message output source, and an output destination application 42 that is a message output destination. Note that the output source application 41 may function as the output destination application 42. Similarly, the output destination application 42 may function as the output source application 41.

  The output source application 41 is, for example, an application that outputs information such as a transaction serving as a starting point of a journal in accounting processing. For example, the output source application 41 is implemented in a system for managing sales or a system for managing financial transactions. The output destination application 42 is, for example, an application that generates journal information in an accounting process. For example, the output destination application 42 is implemented in an accounting system of a company or a tax office.

  As shown in FIG. 1, the message management device 1 performs a preparation process for transmitting a message to the output destination application 42. Specifically, first, the message management device 1 receives, from the first management terminal 2, a registration request for configuration information of a message output by the output source application 41 ((1) in FIG. 1). The first management terminal 2 is a terminal used by a user who manages the output source application 41, for example, a development side of the output source application 41. Upon receiving the configuration information registration request, the message management device 1 stores the configuration information included in the registration request in the storage unit 11 ((2) in FIG. 1).

  Subsequently, the user of the second management terminal 3 refers to the configuration information stored in the storage unit 11 of the message management device 1 in order to specify a message to be input to the output destination application 42 ((3 in FIG. 1). )). The second management terminal 3 is a terminal used by a user who actually uses the output destination application 42. Specifically, first, the message management device 1 receives a request for acquiring the configuration information stored in the storage unit 11 from the second management terminal 3. Then, upon receiving the configuration information acquisition request, the message management device 1 transmits the configuration information to the second management terminal 3. The second management terminal 3 displays the received configuration information, and the user of the second management terminal 3 can check the displayed configuration information.

  Thereafter, the user of the second management terminal 3 inputs the output destination of the message to be input to the output destination application 42. Upon receiving the input of the output destination, the second management terminal 3 transmits a registration request for output destination information for specifying the output destination to the message management device 1. The message management device 1 receives a registration request for output destination information from the second management terminal 3 ((4) in FIG. 1). Upon receiving the output destination information registration request, the message management device 1 stores the output destination information in the storage unit 11 ((5) in FIG. 1).

  As described above, the message management device 1 can transmit and receive a message between a plurality of applications by registering the configuration information and the output destination address in advance.

  Subsequently, as shown in FIG. 2, the message management device 1 performs a process for outputting the message output from the output source application 41 to the output destination application 42. Specifically, first, the output source application 41 transmits a message to the message management device 1 ((6) in FIG. 2). Upon receiving the message, the message management device 1 refers to the output destination information stored in the storage unit 11 and specifies the output destination of the message ((7) in FIG. 2). The message management device 1 transmits the received message to the specified output destination ((8) in FIG. 2).

By doing so, it is not necessary for the output source application 41 to correspond to the data acquisition format of each of the plurality of other applications, so that the application development load can be reduced.
Next, the configuration of the message management device 1 will be described.

[Configuration of Message Management Device 1]
FIG. 3 is a diagram illustrating a configuration of the message management device 1 according to the first embodiment. The message management device 1 includes a storage unit 11 and a control unit 12.
The storage unit 11 is a storage medium such as a ROM (Read Only Memory), a RAM (Random Access Memory), and a hard disk. The storage unit 11 stores various programs executed by the control unit 12. The storage unit 11 stores a message management program that causes the control unit 12 to function as the first registration unit 121, the second registration unit 122, the reception unit 123, the distribution unit 124, the acquisition unit 125, and the output unit 126. The storage unit 11 includes a configuration information storage unit 111 and an output destination information storage unit 112.

The control unit 12 is, for example, a CPU (Central Processing Unit). The control unit 12 controls the functions of the message management device 1 by executing various programs stored in the storage unit 11 or a program obtained from an external device via a communication network. The control unit 12 includes a first registration unit 121, a second registration unit 122, a reception unit 123, a distribution unit 124, an acquisition unit 125, and an output unit 126.
Next, details of the functions of the control unit 12 will be described with reference to flowcharts.

[Process for registering configuration information]
First, details of the function of the control unit 12 relating to registration of configuration information will be described. FIG. 4 is a flowchart illustrating a flow of a process in which the message management device 1 according to the first embodiment registers configuration information.

  First, the first registration unit 121 receives a registration request for requesting registration of the configuration information from the first management terminal 2 (S10). The registration request includes configuration information corresponding to the message output by the output source application 41. When receiving the registration request from the first management terminal 2, the first registration unit 121 registers the configuration information by causing the configuration information storage unit 111 to store the configuration information included in the registration request (S20). Here, the first registration unit 121 generates a message ID for identifying the configuration information, and stores the message ID in the configuration information storage unit 111 in association with the configuration information.

  FIG. 5 is a diagram illustrating an example of information stored in the configuration information storage unit 111 according to the first embodiment. As shown in FIG. 5, it can be confirmed that the configuration information storage unit 111 stores the message ID and the message configuration information in association with each other.

  As described above, the first registration unit 121 receives the configuration information registration request of the plurality of output source applications 41, and stores the configuration information indicating the configuration of the message output from each of the plurality of output source applications in the configuration information storage unit 111.

  Returning to FIG. 4, the first registration unit 121 generates the acquisition unit 125 corresponding to the configuration information (S30). Specifically, a plurality of acquisition units 125 are provided corresponding to each of the plurality of messages. For example, when the configuration information is stored in the configuration information storage unit 111, the first registration unit 121 generates a new acquisition unit 125 corresponding to the configuration information. The first registration unit 121 may associate the acquisition unit 125 with the configuration information by associating the generated acquisition unit 125 with the message ID.

  Further, the first registration unit 121 may receive a function to be executed by the acquisition unit 125 corresponding to the message of the registered configuration information. For example, the function executed by the acquisition unit 125 is a log output function. When the first registration unit 121 receives a function to be executed by the acquisition unit 125 corresponding to the message of the registered configuration information, the first registration unit 121 causes the newly generated acquisition unit 125 to implement the function. In this way, the first registration unit 121 can determine whether or not to generate a log individually in each of the plurality of output source applications 41.

  Subsequently, the first registration unit 121 generates acquisition unit information for the distribution unit 124 to be described later to distribute the message to the acquisition unit 125 corresponding to the output message among the plurality of acquisition units 125. Then, the first registration unit 121 causes the storage unit 11 to store the generated acquisition unit information (S40). In this way, the distribution unit 124 can distribute the message received by the reception unit 123 to the acquisition unit 125 corresponding to the message.

[Process for registering output destination information]
Next, details of the function of the control unit 12 relating to registration of the output destination information will be described. FIG. 6 is a flowchart illustrating a flow of a process in which the message management device 1 according to the first embodiment registers output destination information.

  First, the second registration unit 122 receives a reference request for configuration information from the second management terminal 3 (S50). Upon receiving the configuration information reference request, the second registration unit 122 acquires the configuration information from the configuration information storage unit 111 and transmits the configuration information to the second management terminal 3 (S60). The user of the second management terminal 3, that is, the user on the output destination application 42 side can refer to the acquired configuration information and confirm the configuration information to be notified.

  Subsequently, the second registration unit 122 receives a registration request for output destination information from the second management terminal 3 (S70). Here, the output destination information includes a message ID of a message to be output to the output destination application 42 (a message of the output source application 41) and an output destination address indicating an output destination of the message. Here, the output destination address is an address set for the output destination application 42 to acquire a message. The output destination address is, for example, an address corresponding to a computer on which the output destination application 42 is executed.

  Subsequently, the second registration unit 122 stores the received output destination information in the output destination information storage unit 112 (S80). FIG. 7 is a diagram illustrating an example of information stored in the output destination information storage unit 112 according to the first embodiment. As shown in FIG. 7, it can be confirmed that the output destination information storage unit 112 stores the message ID as the output destination information and the output destination address in association with each other. Further, in FIG. 7, it can be confirmed that a plurality of output destination addresses are associated with the message ID “M001”. By doing so, the message management device 1 can output one message output by the output source application 41 to a plurality of output destination applications 42.

[Process until message output from output source application 41 is output to output destination application 42]
Next, details of functions of the control unit 12 relating to processing until a message is output to the output destination application 42 are described. FIG. 8 is a flowchart illustrating a process flow from when the output source application 41 according to the first embodiment outputs a message to when the message is output to the output destination application 42.

  First, the output source application 41 outputs a message to the message management device 1. Specifically, the output source application 41 transmits a message to the message management device 1. Here, the message includes a message ID for identifying the message.

  The receiving unit 123 acquires the message by receiving the message transmitted from the output source application 41 (S90). Subsequently, the distribution unit 124 refers to the acquisition unit information stored in the storage unit 11, and specifies the acquisition unit 125 corresponding to the message ID included in the acquired message. Then, the distribution unit 124 distributes the acquired message to the specified acquisition unit 125 (S100). Thereby, the specified obtaining unit 125 obtains a message corresponding to the configuration information stored in the configuration information storage unit 111 from the output source application 41.

  Here, the acquisition unit 125 executes a function implemented therein when the configuration information is registered. For example, when the function implemented in the acquisition unit 125 is the log output function, the acquisition unit 125 causes the storage unit 11 to store the output log information in association with the identification information for identifying itself.

  Subsequently, when the obtaining unit 125 obtains the message, the output unit 126 outputs the message to the output destination address stored in the output destination information storage unit 112 as the output destination of the message. Specifically, the output unit 126 specifies, from the output destination information storage unit 112, an output destination address associated with the message ID corresponding to the acquisition unit 125 (S110).

  Subsequently, the output unit 126 outputs a message to the output destination application 42 based on the specified output destination address (S120). Specifically, the output unit 126 outputs a message as follows. First, the output unit 126 transmits an HTTP request to the computer that executes the specified output destination address, that is, the output destination application 42. When the computer executing the output destination application 42 receives the HTTP request, the output destination application 42 detects that there is a message output from the output source application 41. When detecting that there is a message, the output destination application 42 accesses the message management device 1 and acquires the message. By doing so, the output unit 126 can push out the message to the output destination application 42.

[Effects in First Embodiment]
As described above, when the message management device 1 according to the first embodiment receives the message corresponding to the configuration information registered in advance, the output destination stored in the output destination information storage unit 112 as the output destination of the message is output. Output a message to the address.

  By doing so, the output source application 41 does not need to support the data acquisition format in each of the plurality of output destination applications 42. Therefore, since the influence on the development of the output source application 41 is reduced, the load on the development of the output source application 41 can be reduced.

<Second embodiment>
[If the configuration information to be registered is similar to the existing configuration information, notify the terminal to that effect]
Subsequently, a second embodiment will be described. The message management device 1 according to the first embodiment registers configuration information based on a registration request from the first management terminal 2. On the other hand, when the configuration information to be registered is similar to the existing configuration information, the message management device 1 according to the second embodiment notifies the first management terminal 2 of that fact. And different. Hereinafter, portions different from the first embodiment will be described. The description of the same parts as those in the first embodiment will be omitted as appropriate.

  FIG. 9 is a flowchart illustrating a flow of a process in which the message management device 1 according to the second embodiment registers configuration information. The processing from S20 to S40 shown in FIG. 9 is the same as the processing from S20 to S40 in FIG.

  The first registration unit 121 receives configuration information to be stored in the configuration information storage unit 111 from the first management terminal 2 and, when the configuration information is similar to the configuration information already stored in the configuration information storage unit 111, Then, notification information indicating that similar configuration information is stored is output to the first management terminal 2.

  Specifically, upon receiving the configuration information from the first management terminal 2 (S10), the first registration unit 121 checks whether configuration information similar to the configuration information included in the registration request is stored in the configuration information storage unit 111. It is determined whether or not it is (S11). Here, the similarity determination may be a perfect match or a partial match. If the first registration unit 121 determines that there is configuration information similar to the configuration information included in the registration request, the similar configuration information is already stored in the configuration information storage unit 111 in the first management terminal 2. Is notified (S12). On the other hand, when the first registration unit 121 determines that there is no configuration information similar to the configuration information included in the registration request, the first registration unit 121 performs the processing after S20.

  When the configuration information stored in the configuration information storage unit 111 is similar to the configuration information already stored in the configuration information storage unit 111, the first registration unit 121 stores the similar configuration information in the first management terminal. 2 may be output. In this case, the first registration unit 121 acquires similar configuration information from the configuration information storage unit 111, and transmits the acquired configuration information to the first management terminal 2.

[Effect in Second Embodiment]
As described above, when the configuration information to be registered by the application is similar to the existing configuration information, the message management device 1 according to the second embodiment does not register the configuration information related to the registration request, and the existing similarity. The first management terminal 2 is notified that there is configuration information.

  By doing so, the message management device 1 allows the user of the first management terminal 2, that is, the developer of the output source application 41, to register the already registered configuration information similar to the configuration information to be registered. By setting the configuration information of the message transmitted by the output source application 41 based on this, the message used by each application can be shared. This makes it easier for the user of the second management terminal 3, that is, the developer of the output destination application 42, to select the configuration information of the message to be received.

<Third embodiment>
Subsequently, a third embodiment will be described. The message management device 1 according to the first embodiment registers output destination information with reference to all configuration information in which the second management terminal 3 is registered. On the other hand, when registering the configuration information, the message management device 1 according to the third embodiment registers the configuration information in association with the authority information, and the second management terminal 3 registers the output destination information. The first embodiment differs from the first embodiment in that, when trying to refer to the configuration information, one or more configuration information is selected from the storage unit 11 based on the authority information.

  First, the first registration unit 121 causes the configuration information storage unit 111 to store the configuration information in association with authority information indicating the authority to acquire a message corresponding to the configuration information. The first registration unit 121 stores the configuration information and the authority information in the configuration information storage unit 111 in association with each other. Here, the authority information is, for example, attribute information indicating an attribute of a user who can use the configuration information or an attribute of a user who cannot use the configuration information. The attribute information is, for example, information indicating the position of the user or the company to which the user belongs.

  Subsequently, the second registration unit 122 receives user information including user attribute information from the second management terminal 3 corresponding to the user using the message. The second registration unit 122 selects one or more configuration information from the configuration information storage unit 111 based on the user information and the authority information, and selects one of the one or more configuration information corresponding to the message to be output. Accepts selection of configuration information.

  Specifically, the second registration unit 122 receives the user information from the second management terminal 3, and specifies the attribute information of the user included in the received user information. The second registration unit 122 selects one or more configuration information from the configuration information storage unit 111 based on the specified attribute information of the user. For example, it is assumed that the user information received by the second registration unit 122 includes attribute information “Company A”. The second registration unit 122 refers to the configuration information storage unit 111 and selects one or more configuration information stored in association with the attribute information “Company A”. The second registration unit 122 transmits the selected one or more pieces of configuration information to the second management terminal 3 and causes the second management terminal 3 to display the configuration information. Thus, only the configuration information associated with the attribute information “Company A” is displayed on the second management terminal 3.

  Next, the second management terminal 3 causes the display unit to display one or more configuration information selected by the second registration unit 122. The second registration unit 122 receives a request for registration of output destination information from the second management terminal 3 by receiving a selection of one piece of configuration information corresponding to a message to be output.

[Effects in Third Embodiment]
As described above, the message management device 1 according to the third embodiment registers the configuration information and the authority information in association with each other, so that only the authorized output destination application 42 refers to the configuration information and outputs the output destination information. Can be registered.

  In this way, for example, the developer of the output source application 41 can restrict the message from being output to the output destination application 42 developed by the competing developer.

  As described above, the present invention has been described using the embodiment. However, the technical scope of the present invention is not limited to the scope described in the above embodiment, and various modifications and changes can be made within the scope of the gist. is there. For example, the specific embodiment of the dispersion / integration of the apparatus is not limited to the above embodiment, and all or a part of the apparatus may be functionally or physically dispersed / integrated in an arbitrary unit. Can be. Further, new embodiments that are generated by arbitrary combinations of the plurality of embodiments are also included in the embodiments of the present invention. The effect of the new embodiment caused by the combination has the effect of the original embodiment.

DESCRIPTION OF SYMBOLS 1 ... Message management apparatus, 11 ... Storage part, 111 ... Configuration information storage part, 112 ... Output destination information storage part, 12 ... Control part, 121 ... First registration part, 122 ... second registration unit, 123 ... reception unit, 124 ... distribution unit, 125 ... acquisition unit, 126 ... output unit, 2 ... first management terminal, 3 ...・ Second management terminal, 4 ・ ・ ・ Application group, 41 ・ ・ ・ Output source application, 42 ・ ・ ・ Output destination application

Claims (7)

A first registration unit configured to store configuration information indicating a configuration of a message output from each of the plurality of applications in a storage unit;
A second registration unit that stores an address indicating an output destination of the message in the storage unit in association with the configuration information ;
From the application, an acquisition unit that acquires a message corresponding to the configuration information stored in the storage unit,
When the acquisition unit acquires a message, an output unit for outputting the message to the address in association with the configuration information corresponding to the message stored in the storage unit,
A message management device comprising: The first registration unit receives the configuration information to be stored in the storage unit from a terminal, and stores similar configuration information when the configuration information is similar to the configuration information already stored in the storage unit. Outputting to the terminal notification information indicating that the
The message management device according to claim 1. The first registration unit outputs the similar configuration information to the terminal when the configuration information stored in the storage unit and the configuration information already stored in the storage unit are similar,
The message management device according to claim 2. The first registration unit associates the configuration information with authority information indicating an authority to acquire a message corresponding to the configuration information and stores the association information in the storage unit;
The second registration unit receives user information from a user terminal corresponding to a user who uses a message, and selects one or more configuration information stored in the storage unit in association with the authority information included in the user information. Receiving, from among the one or more pieces of configuration information, a selection of one piece of configuration information corresponding to the message to be output;
The message management device according to claim 1. The acquisition unit is provided in plurality corresponding to each of a plurality of messages,
The first registration unit, when receiving a function to be executed by the acquisition unit corresponding to the message of the registered configuration information, causes the acquisition unit to implement the function.
The message management device according to claim 1. Among the plurality of acquisition units provided corresponding to each of a plurality of messages, further includes a distribution unit that distributes a message received from the application to one of the acquisition units corresponding to the message.
The message management device according to claim 1. Computer runs,
Storing in a storage unit configuration information indicating a configuration of a message output from each of the plurality of applications;
Storing an address indicating an output destination of the message in the storage unit in association with the configuration information ;
From the application, obtaining a message corresponding to the configuration information stored in the storage unit,
When a message is acquired in a step of obtaining and outputting the message to the address in association with the configuration information corresponding to the message stored in the storage unit,
Message management method comprising:

Images