JP5035286B2 - Bus-type message exchange system, bus-type message exchange method and program - Google Patents

Description

  The present invention relates to a bus-type message exchange system, a bus-type message exchange method and program, and in particular, a bus-type message exchange system and a bus that are optimally applied to a processing system based on service-oriented architecture (hereinafter referred to as SOA: Service Oriented Architecture). The present invention relates to a type message exchange method and program.

  As the network, various communication networks as shown in Patent Literature 1 to Patent Literature 4 are constructed and processing is performed.

  In recent years, instead of the above-described communication network, a concept or technique for constructing a large-scale computer system called SOA has been taken up. SOA is a methodology for constructing applications and systems as a set of abstracted units of services having a certain granularity (scale).

  As one of means for realizing the SOA, mounting technology such as ESB (Enterprise Service Bus) having connection functions of various communication protocols is considered. The ESB is a bus-type messaging engine, and handles software functions corresponding to one business process as a set of services. Furthermore, the ESB has a role of connecting the services and mediating transmission / reception messages, and can cooperate with each other.

  Since the ESB is a bus-type network format, messages must pass through the bus. The importance of the bus itself is extremely high, and safety and reliability with high accuracy are required. For this reason, there is a need for a system that efficiently performs communication processing without applying an unnecessary load.

  In the bus type message exchange system in the SOA, as shown in FIG. 12, the client 101 and the message bus 102 are connected by a protocol connector 103, and the message bus 102 and the service unit 105 are connected by a protocol connector 104. It is connected. Here, the protocol connector 103 employs a communication protocol and a connection method necessary for exchanging data between the client 101 and the message bus 102. The protocol connector 104 employs a communication protocol or connection method that depends on the application that the service unit 105 executes processing.

In the bus type message exchange system shown in FIG. 12, as shown in FIG. 13, the protocol connector 103 on the client 101 side calls a plurality of protocol connectors 104 corresponding to two or more service units 105 linked on the message bus 102. In other words, a plurality of service units 105 cannot be called in a so-called one-to-many configuration.

Therefore, when calling a plurality of service units 105 that execute an application, as shown in FIG. 14, an intermediary unit 106 that performs proxy processing for a request in which a route and an order are set is arranged on the message bus 102 . Then, a proxy process is constructed in which a request from the client 101 is once received by the mediation unit 106 and the mediation unit 106 calls a plurality of service units 105 in a preset order. More specifically, when the mediation unit 106 receives a request from the client 101, the mediation unit 106 first calls the first service unit 105 in accordance with a preset order, and receives response information from the service unit 105. Then, based on the information, it is realized to call a plurality of service units 105 in a procedure of calling the next service unit according to the order and conditions.

JP 2000-032146 A JP 2005-149515 A JP 2006-277098 A JP 2008-305411 A

  However, in the case of the bus type message exchange system, since all messages (including data) pass through the message bus 102 which is the basis of the system, the call method via the mediation unit 106 depends on the data flow rate and the number of simultaneous connections. The overall data size increases dramatically. For example, in the configuration shown in FIG. 14, communication is performed using the message bus 102 a total of six times for transmission / reception between the client 102 and the protocol connector 103 and transmission / reception between each service unit 105 and the mediation unit 106. Will be.

If the number of service units 105 used by the client 101 increases, the number of communications using the message bus 102 increases astronomically by the increase. In this state, there is a problem in that the bus type message exchange system tends to cause resource depletion such as memory shortage. This is less affected if it is a test environment or a simple system. However, when a large number of messages are exchanged in a large-scale system, there is a possibility that the system itself may malfunction, and this is a problem to be improved.

  An object of the present invention is to provide a bus type message exchange system, a bus type message exchange method, and a program that are optimally applied to a processing system based on a service oriented architecture (SOA). .

In order to achieve the above object, a bus type message exchange system according to the present invention is a bus type message exchange method for exchanging messages between two or more service units and clients connected on a message bus through the message bus. An exchange system,
A client protocol connector disposed between the client and the message bus; and a service protocol connector disposed between the service unit and the message bus.
The client protocol connector adds route information in the message bus to the communication data transmitted from the client, and transmits the communication data to the message bus. The processing data addressed to the own device is extracted from the communication data transmitted from the message bus, and is transmitted to the service unit of the own device. The processing data is transmitted from the service unit to the service data for the next service following the own device. Destination information to the protocol connector is added and transmitted to the message bus.

  The case where the present invention is constructed as a bus type message exchange system as hardware has been described above, but the present invention is not limited to this. The present invention may be constructed as a bus type message exchange method or a bus type message exchange program as software.

When the present invention is constructed as a bus type message exchanging method, the bus type message exchanging method according to the present invention is a message passing between the two or more service units and clients connected on the message bus through the message bus. A bus-type message exchange method for exchanging
The communication data from the client is received by the client protocol connector, and the communication data is transmitted to the message bus by adding path information in the message bus to the communication data by the client protocol connector.
The communication data from the message bus is received by a service protocol connector, processing data addressed to the own device is extracted from the communication data transmitted from the message bus by the service protocol connector, The information is transmitted to the service unit, and the destination data to the next service protocol connector subsequent to the own device is added to the processing data from the service unit and transmitted to the message bus.

When the present invention is constructed as a bus-type message exchange program, the bus-type message exchange program according to the present invention is executed through the message bus between two or more service units and clients connected on the message bus. A bus-type message exchange program for controlling the exchange of messages,
On the computer,
A function of receiving communication data from the client and adding the communication data to the message bus by adding path information in the message bus to the communication data;
Receives the communication data from the message bus, extracts processing data addressed to its own device from the communication data transmitted from the message bus, transmits it to the service unit of its own device, and processes it from the service unit The data is constructed so as to execute the function of adding destination information to the next service protocol connector following the device itself and transmitting the data to the message bus.

  According to the present invention, it is possible to reduce the number of times of communication without preparing a sequencer that performs an intermediary proxy process by embedding paths, orders, and the like when executing a plurality of service units in communication data itself.

It is a block diagram which shows the bus type message exchange system which concerns on Embodiment 1 of this invention. It is a figure which shows the flow of the communication data which shows operation | movement of the bus type message exchange system which concerns on Embodiment 1 of this invention. It is a figure which shows the internal structure of the protocol connector for clients in the bus type message exchange system which concerns on Embodiment 1 of this invention. It is a figure which shows an example of the communication data transmitted toward a message bus. It is a figure which shows the internal structure of the protocol connector for service in the bus type message exchange system which concerns on Embodiment 1 of this invention. It is a figure which shows the communication data transmitted between service parts. It is a figure which shows the internal structure of the protocol connector for service in the bus type message exchange system which concerns on Embodiment 1 of this invention. It is a sequence diagram which shows the operation | movement of the whole bus type message exchange system which concerns on Embodiment 1 of this invention. It is a block diagram which shows the bus type message exchange system which concerns on Embodiment 2 of this invention. It is a figure which shows the internal structure of the protocol connector for clients in the bus type message exchange system which concerns on Embodiment 2 of this invention. It is a figure which shows an example of the communication data transmitted toward a message bus. It is a block diagram which shows the bus type message exchange system which concerns on a related technique. It is a figure which shows the flow of the communication data which shows operation | movement of the bus type message exchange system which concerns on a related technique. It is a figure which shows the flow of the communication data which shows operation | movement of the bus type message exchange system which concerns on a related technique.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  The basic principle of the embodiment of the present invention will be described. As a method for solving the problem in the configuration shown in FIG. 12, in addition to direct methods such as hardware replacement and improvement of the performance of the bus type message exchange system, the flow rate of messages flowing in the message bus is reduced. Can be considered.

  In order to reduce the flow rate of messages flowing through the message bus, there are methods of reducing the size per message or reducing the number of messages to be communicated. The former depends on the communication protocol and the communication data of the application executed in the service unit, and the latter increases / decreases depending on the transmission / reception model of messages, particularly the transmission / reception model for a plurality of access locations. Although there are differences depending on the message size, the impact of reducing the load is generally greater when the number of messages to be communicated is reduced.

The embodiment of the present invention is intended to reduce the number of message communications, and instead of a method of calling a plurality of services by mediation of a mediation unit, between two or more service units linked on a message bus The system is constructed so that communication using the message bus is performed by adopting a method in which the immediately preceding service unit calls the next service unit. Embodiments of the present invention will be described in detail using specific examples.
(Embodiment 1)

As shown in FIG. 1, the bus type message exchange system according to the first exemplary embodiment of the present invention is between two or more service units 2 ₁ , 2 ₂ ... 2 _{n connected} to a message bus 1 and a client 3. The present invention is intended for a bus type message exchange system for exchanging messages through the message bus 1. _{2 1, 2 2} ··· _{2 n} the service unit is adapted to execute respectively on a unit corresponding to one processing application software business, the service unit _{2 1, 2 2} ··· _{2 n} messages By linking to the bus 1, an entire system that consistently executes business processes is constructed.

In the first embodiment of the present invention, as shown in FIG. 1, a client protocol connector 4 disposed between the client 3 and the message bus 1 and the service units 2 ₁ , 2 ₂ ... 2 _n And service protocol connectors 5 ₁ , 5 ₂ ,..., 5 _n respectively disposed between the message bus 1 and the message bus 1. In the following description, two service units 2 ₁ , 2 ₂ are used as the service units 2 ₁ , 2 ₂ ... 2 _n , and two service protocol connectors 5 ₁ , 5 ₂ are combined correspondingly. The number of installed service units 2 ₁ , 2 ₂ ... 2 _n and the service protocol connectors 5 ₁ , 5 ₂ ,... 5 _n is limited to that shown in FIG. There are no, and these are increased or decreased depending on the processing capacity of the business. The number in this case, as the service protocol connector _{5 1,} 5 2, · · · _{5 n} and the service unit _{2 1,} 2 2 pairs of · · · _{2 n} to be called, the number of processes, for example, the process of the operation execution There are as many pairs as there are.

The protocol connector _{4,5 1, 5 2, ··· 5} n is for connecting the client 3 and the message bus 1 or the service unit _{2 1, 2 2} ··· _{2 n} and message bus 1, service unit _{2 1,} 2 2 ... ₂ protocol connector ₅ 1 connected to _n, 5 2, ... _{5 n} is to call the service unit _{2 1,} 2 2, ... _{2 n} associated in If information is communicated by, for example, the HTTP protocol, it has URL information, a structure of message data required for a request, a structure of return data, and the like.

The client protocol connector 4 adds the path information D2 in the message bus 2 to the communication data D1 transmitted from the client 2, and converts it into a data format for communication in the message bus 1. Then, it is transmitted to the message bus 2 as communication data D3. Wherein the service protocol connector 5 ₁ example of the service protocol connector 5 _1, or 5 ₂ takes out the processed data D4 destined for the own device from the communication data D3 transmitted from the message bus 2, it self transmitted to the service unit 2 ₁ of the apparatus, the processed data D5 from the service unit 2 ₁ adds the destination information D6 to the service protocol connector 5 ₂ corresponding to the next service unit 2 ₂ following the own device, This is converted into a data format for communication within the message bus 1 and transmitted to the message bus 2 as communication data D7.

Incidentally, the service protocol connector _{5 1,} 5 2, ... _{5 n} is the corresponding said service unit _{2 1,} 2 2 ... ₂ communication protocol and message bus 2 _n is dependent on the application software running respectively The communication data D3 and D7 are exchanged with the message bus 2 using the communication protocol used, and the bus is connected via the service protocol connectors 5 ₁ , 5 ₂ ... 5 _n. A plurality of types of service protocol connectors 5 ₁ , 5 ₂ ... 5 _n are prepared so that various communication protocols can be received as a characteristic of the type message exchange system.

  Further, each protocol connector will be described in detail with reference to FIG. 3, FIG. 5, and FIG.

  As shown in FIG. 3, the client protocol 4 includes a request reception function unit 4a, an in-bus communication data creation function unit 4b, and an in-bus transmission function unit 4c. Further, as shown in FIG. 3, the client protocol connector 3 according to the first embodiment records the route information D2 in the route file 4d and manages it, and adds the route information D2 to the communication data D1. is there.

  The request receiving function unit 4a receives a request message from the client 1 and receives communication data D1 from the client 1.

When the communication data creation function unit 4b in the bus receives the communication data D1 from the request reception function unit 4a, the communication data creation function unit 4b acquires the route information D2 in the message bus 1 from the route file 4d, and uses this route information D2 as the communication data. Communication data D3 (D1 + D2) is created by adding to data D1. The intra-bus communication data creation function unit 4b includes data necessary for actual communication (for example, data described in the </ message> column in FIG. 4) and route information D2 (for example, the </ route> column in FIG. 4). Communication data D3 is created in the same language, for example, XML format as shown in FIG. More specifically, when creating communication data D3 in the XML format, for example, as shown in FIG. 4, the in-bus communication data creation function unit 4b originally communicates with the message bus 1 in the </ message> column. The contents of the message to be transmitted (the data necessary for the actual communication) are described, and in the </ route> column, the communication data D3 is _first transmitted through the message bus 1 to the service unit 21 and then the service unit 2 ₂ is added to the communication data D1 to create the communication data D3. The format (language etc.) for creating the communication data D3 is not limited to the XML format.

  The in-bus transmission function unit 4c transmits the communication data D3 created by the in-bus communication data creation function unit 4b into the message bus 1.

The message bus 1 is a core configuration of the bus type message exchange system, receives communication data D3 transmitted via the client protocol connector 4, and based on the information described in the communication data D3, the message bus 1 It has a function to call the service protocol connector 5 ₁ or 5 ₂ to which the service unit 2 ₁ or 2 ₂ is connected. Specifically, the message bus 1 3, as shown in FIGS. 5 and 7, and the bus within the receiving unit 1a for receiving communication data D3 from the client protocol connector 3, the service unit 2 ₁ bath exchanges communication data D7, D11 transmission function section 1d and between the receiving unit 1c in the transmission function part 1b and bath bus for exchanging communication data D3, D7, and the service unit 2 ₂ between And an in-bus reception function unit 1e.

The in-bus reception function unit 1a and the in-bus transmission function unit 1b exchange communication data D3 via the message bus 1. The in-bus reception function unit 1c and the in-bus transmission function unit 1d exchange communication data D7 via the message bus 1. The in-bus reception function unit 1e and the client protocol bus 4 exchange communication data D11 via the message bus 1. The client protocol bus 4 receives the communication data D11 from the in-bus reception function unit 1e, extracts data processed by the service units 2 ₁ and 2 ₂ from the received communication data D11, and the data Is transmitted to the client 3 in the same manner as in the configuration shown in FIG. 12 and the like, and is not shown in the figure because there is no feature in the configuration.

Next, the service protocol connectors 5 ₁ and 5 ₂ will be described. These service protocol connectors 5 ₁ , 5 ₂ have the same internal configuration, and differ in part of their functions due to differences in the service units 2 ₁ , 2 ₂ to be connected. Therefore, the internal configuration will be described with the same reference numerals.

As shown in FIG. 5 and FIG. 7, the service protocol connectors 5 ₁ and 5 ₂ include an in-bus reception function unit 5a, a data extraction function unit 5b, a request transmission / reception function unit 5c, and an in-bus communication data creation function unit. 5d and an in-bus transmission function unit 5e.

  The in-bus reception function unit 5a receives the communication data D3 or D7 transmitted from the in-bus transmission function unit 1b or 1d in the message bus 1.

The data extraction function unit 5b extracts processing data D4 or D8 addressed to the own apparatus from the communication data D3 or D7 transmitted from the in-bus transmission function unit 1b or 1d in the message bus 1. The request receiving function unit 5c is for transmitting the processed data D4 or D8 received from the data extraction function unit 5b in the service unit 2 ₁ or 2 ₂ of its own device. Specifically, the request receiving function unit 5c of the service protocol connector 5 ₁ transmits the processed data D4 into the service unit 2 ₁ is its own device, wherein the request transmission and reception of the service protocols connector 5 ₂ functional unit 5c, and transmits the processed data D8 to the service unit 2 ₂ which is the self-device.

Further, the request receiving function unit 5c is configured to receive the service unit 2 ₁ or 2 ₂ processed the processed data D5 or D9. Specifically, the request receiving function unit 5c of the service protocol connector 5 ₁ receives the processed data D5 that has been processed by the service unit 2 _1, the request reception function portion of the service protocol connector 5 ₁ 5c is configured to receive the processed data D9 that is processed by the service unit 2 _2.

Wherein the bus in the communication data creating function unit 5d of the service protocol connector 5 ₁ As shown in FIG. 5, when receiving the processed data D5 by the service unit 2 ₁ from the request receiving function unit 5c, next to the processing data D5 it is to create a communication data D7 for calling the service protocol connector 5 ₂ corresponding to the service unit 2 _2. Specifically, the bus in the communication data creating function unit 5c of the service protocol connector _{5 1,} when creating a communication data D7 in XML format as shown in FIG. 6, for example, in the column of </ message>, describing the contents of the message to be communicated in the original message bus 1, </ route> in the column, the communication data D7 by adding routing information D6 to process data D5 showing sending the next service unit 2 ₂ create. The format for creating the communication data D7 is not limited to the XML format.

The bus in the communication data creating function unit 5d of the service protocol connector 5 ₂ As shown in FIG. 7, when receiving the processed data D9 by the service unit 2 ₂ from the request receiving function unit 5c, the client in the processing data D9 The communication data D11 for calling the protocol connector 4 is created.

  The in-bus transmission function unit 5c transmits the communication data D7 or D11 created by the in-bus communication data creation function unit 5b into the message bus 1.

  Next, the case of executing the bus type message exchange method using the bus type message exchange system according to the first embodiment of the present invention will be described with reference to FIG. 1, FIG. 2, FIG. 3, FIG. explain.

2, 3, and 8, the client protocol 4 communicates with the client 3, and uses the plurality of service units 2 ₁ , 2 ₂ from the client 3 to request, for example, business processing. When the request is received, the request reception function unit 4a of the client protocol 4 receives the request message from the client 1 and receives the communication data D1 from the client 1.

  Next, as shown in FIG. 3, when the communication data creation function unit 4b in the bus receives the communication data D1 from the request reception function unit 4a, it acquires the route information D2 in the message bus 1 from the route file 4d. (Step S1 in FIG. 8), the route information D2 is added to the communication data D1 to create communication data D3 (D1 + D2) (Step S2 in FIG. 8). Then, the in-bus transmission function unit 4c transmits the communication data D3 created by the in-bus communication data creation function unit 4b into the message bus 1 (step S3 in FIG. 8).

The message bus 1 receives the communication data D3 transmitted via the client protocol connector 4, the service protocol of the service unit 2 ₁ as a destination based on the information described in the communication data D3 is connected call the connector _{5 1.} Specifically, as shown in FIG. 3, the in-bus reception function unit 1a of the message bus 1 receives the communication data D3 transmitted through the client protocol connector 4, and receives the path information D2 of the communication data D3. Referring to FIG. 8, the communication data D3 is transmitted to the in-bus transmission function unit 1b of the message bus ₁ to call the first service unit 21 (step S4 in FIG. 8).

The bus in the transmission function part 1b of the message bus 1 as shown in FIG. 5, toward the service protocol connector 5 ₁ corresponding to the service unit 2 ₁ to call first transmits the communication data D3 (FIG. 8 Step S4).

As shown in FIG. 5, the bus in the receiving unit 5a of the service protocol connector 5 ₁ receives the communication data D3 transmitted from the bus the transmission function portion 1b of the message bus 1. Then, the data retrieval function unit 5b retrieves the processing data D4 addressed to itself from the communication data D3 transmitted from the intra-bus transmission function unit 1b in the message bus 1. Request receiving function unit 5c transmits the processed data D4 received from the data extraction function unit 5b in the service unit 2 ₁ of its own device (step S5 in FIG. 8). The first service unit 2 ₁ receives the processed data D4, the processed data D4 is treated by the application software (step S6 in FIG. 8), and transmits the processed data D5 to the request receiving function unit 5c ( Step S7 in FIG.

Further, the request receiving function unit 5c, when receiving the processed data D5 that has been processed by the service unit 2 _1, and transmits the processed data D5 to the bus in the communication data creating function unit 5d. The bus in the communication data creating function unit 5d, as shown in FIG. 5, when receiving the processed data D5 by the service unit 2 ₁ from the request receiving function unit 5c, corresponding to the processed data D5 to the next service unit 2 ₂ create a communication data D7 for calling the service protocol connector 5 _2, and transmits the message bus 1 through the communication data D7 to the bus in transmission function unit 5c (step S8 in FIG. 8).

The bus in the receive function section 1c of the message bus 1 as shown in FIG. 5, receives communication data D7 sent from the first service protocol connector 5 _1, by referring to the route information D6 of the communication data D7, to invoke the next service unit 2 _2, and transmits the communication data D7 to the bus in the transmission function portion 1d of the message bus 1 (step S9 in FIG. 8).

The bus in the transmission function portion 1d of the message bus 1 as shown in FIG. 7, then the corresponding to the service unit 2 ₂ toward the service protocol connector 5 ₂ transmits the communication data D7 to call (in FIG. 8 Step S9).

As shown in FIG. 7, the service protocol connector 5 ₂ bus in receiving unit 5a receives the communication data D7 transmitted from the bus the transmission function portion 1d of the message bus 1. Then, the data retrieval function unit 5b retrieves the processing data D8 addressed to itself from the communication data D7 transmitted from the intra-bus transmission function unit 1d in the message bus 1. Request receiving function unit 5c transmits the processed data D8 received from the data extraction function unit 5b in the service unit 2 ₂ of its own device (step S10 in FIG. 8). Service unit 2 ₂ receives the process data D8, the processing data D8 is treated by the application software (step S11 of FIG. 8), and transmits the processed data D9 to the request receiving function unit 5c (FIG. 8 Step S12).

Further, the request receiving function unit 5c, when receiving the processed data D9 that is processed by the service unit 2 _2, and transmits the processed data D9 to a bus in the communication data creating function unit 5d. The bus in the communication data creating function unit 5d, as shown in FIG. 7, when receiving the processed data D9 by the service unit 2 ₂ from the request receiving function unit 5c, for calling a client protocol connector 4 to the processing data D9 The communication data D11 is created by adding the route information D10, and the communication data D11 is transmitted to the message bus 1 through the in-bus transmission function unit 5c (step S13 in FIG. 8).

The message bus 1 receives the communication data D11 transmitted from the service protocol for connector 5 _2, by referring to the path information D10 of the communication data D11, and transmits the communication data D11 to the client protocol connector 4 (FIG. 8 step S14).

When the client protocol connector 4 receives the communication data d11, the client protocol connector 4 notifies the client 3 of the processing results of the service units 2 ₁ and 2 ₂ .

  As described above, according to the first embodiment of the present invention, the existing bus type message exchange system has the following effects as compared with a method of calling a plurality of services using a sequencer by an intermediary unit.

  That is, in the first embodiment of the present invention, in order to realize communication between protocol connectors by incorporating route information into communication data communicated between protocol connectors through a message bus, in the existing bus type message exchange system It is possible to reduce the number of communication data communications within the system. In addition, since a mechanism for mediating communication is not required in the message bus, communication with the mediation mechanism is not required, so that the number of times of communication itself can be reduced. This effect becomes more prominent as the number of service units performing processing increases.

  Next, it is possible to reduce the communication with the service department by reducing the number of message communications, and the internal data amount associated therewith, thereby suppressing the occurrence of resource depletion such as a lack of memory consumed in the bus type message exchange system. Can do. This means that when the function of the bus type message exchange system is executed by constructing as a bus type message exchange program, it is possible to reduce the use of the CPU that executes the program.

(Embodiment 2)
A modification of the client protocol connector 4 according to the first embodiment of the present invention will be described as a second embodiment with reference to FIGS. In the second embodiment of the present invention, only differences from the first embodiment will be described. Other configurations are the same as those of the first embodiment.

  In the embodiment of the present invention, as shown in FIGS. 9 and 10, the client protocol connector 4 includes a route acquisition function unit 4e instead of the route file 4d. Then, the route information in the message bus 1 recorded in the route file 4d is stored in the storage unit 10 as a database. The route acquisition function unit 4e may acquire route information by accessing the storage unit 10 via a network or the like.

  When the client protocol connector 4 receives a request from the client 3, the route acquisition function unit 4e of the client protocol connector 4 accesses the database of the storage unit 10 as shown in FIGS. Route information D2 in the message bus 1 is acquired. The in-bus communication data creation function unit 4b of the client protocol connector 4 receives the route information D2 from the route acquisition function unit 4e and adds it to the communication data D1 from the client 3, thereby Communication data D3 used by the transmission function is created.

In this case, the intra-bus communication data creation function unit 4b creates communication data D3 having two parameters, that is, data D31 actually communicated and data D32 describing the path information D2, as shown in FIG. To do. In this case, the bus in the communication data creating function section 4b, in the column of route information D2, first transmits through the communication data D3 to the message bus 1 to the service unit 2 _1, and then be sent to the service unit 2 ₂ Describe the information indicating.

  According to the second embodiment of the present invention, the data D31 used for communication within the message and the data of the route information D2 included in the communication data D3 are described in different languages. It is not necessary to use any other language, and information that is not text, such as binary data, can be handled as the data D31.

  According to the present invention, the present invention can be applied to network equipment in which a bus type message exchange system is implemented by hardware / software and application server software that integrates applications / systems. It can also be used for a service provider that provides mediation between a plurality of service units.

1 Message Bus 2 ₁ , 2 ₂ Service Unit 3 Client 4 Client Protocol Connector 5 ₁ , 5 ₂ Server Protocol Connector 10 Storage Unit

Claims (10)

A bus type message exchange system for exchanging messages through the message bus between two or more service units and clients linked on a message bus;
A protocol connector for a client disposed between the client and the message bus;
Two or more service protocol connectors respectively disposed between the service unit and the message bus;
The two or more service units process processing data transmitted from the corresponding service protocol connector, and transmit the processing data to the corresponding service protocol connector.
The client protocol connector is:
In-bus communication data creation function for creating communication data D3 by adding route information D2 in the message bus to the communication data D1 transmitted from the client, and converting this to communication data format in the message bus And
An in-bus transmission function unit that transmits the communication data D3 created by the in-bus communication data creation function unit to the message bus;
The two or more service protocol connectors are:
In-bus reception / transmission function unit for exchanging communication data with the message bus using a communication protocol depending on application software executed by the corresponding service unit and a communication protocol used in the message bus;
The communication data D3 transmitted from the client protocol connector through the message bus and taken into the corresponding service protocol connector by the in-bus reception transmission function unit, or processed by the one service unit and transmitted through the message bus A data extraction function unit that extracts processing data D4 or D8 addressed to the own device from the communication data D7 captured by the corresponding service protocol connector by the in-bus reception / transmission function unit;
On-bus communication data creation function for creating communication data D7 or D11 for calling a service protocol connector corresponding to the next service section in the processing data D5 or D9 when the processing data D5 or D9 processed by the service is received And a bus-type message exchange system.   The communication data creation function unit in the bus of the client protocol connector creates the communication data by describing the route information in the same language or different language as the communication data from the client. Bus-type message exchange system.   2. The bus type message exchange system according to claim 1, wherein the client protocol connector self-manages the route information and adds the route information to the communication data. A storage unit for managing the route information as a database;
2. The bus type message exchange system according to claim 1, wherein the client protocol connector reads out route information managed by the storage unit and adds it to the communication data. A bus-type message exchange method for exchanging messages through the message bus between two or more service units linked to a message bus and a client,
The client and the message bus are connected by a client protocol connector, and the service unit and the message bus are respectively connected by a service protocol connector,
Route information D2 in the message bus is added to the communication data D1 transmitted from the client, and this is created as communication data D3 converted into a data format of communication in the message bus, and the communication data D3 is created. Send from the client connector to the message bus,
Using the communication protocol depending on the application software executed by the corresponding service unit and the communication protocol used in the message bus, the communication protocol connector for the service performs communication data exchange with the message bus,
The communication data D3 transmitted from the client protocol connector through the message bus and taken into the corresponding service protocol connector, or processed by the one service unit and transmitted through the message bus to the corresponding service protocol connector The processing data D4 or D8 addressed to its own device is extracted from the communication data D7 captured in
When the service unit receives the processing data D5 or D9 obtained by processing the processing data D4 or D8, communication data D7 or D11 for calling a service protocol connector corresponding to the next service unit is sent to the processing data D5 or D9. A bus-type message exchanging method characterized by creating and transmitting the created communication data D7 or D11 into the message bus.   6. The bus type message exchange method according to claim 5, wherein the communication data is created by describing the route information in the same language as the communication data from the client.   6. The bus type message exchange method according to claim 5, wherein the communication data is created by describing the route information in a language different from the communication data from the client. A bus-type message exchange program for controlling exchange of messages performed through the message bus between two or more service units linked to a message bus and a client;
The client and the message bus are connected by a client protocol connector, and the service unit and the message bus are respectively connected by a service protocol connector,
On one computer,
Route information D2 in the message bus is added to the communication data D1 transmitted from the client, and this is created as communication data D3 converted into a data format of communication in the message bus, and the communication data D3 is created. The function of transmitting from the client connector to the message bus is executed,
To other computers
A function for exchanging communication data with the message protocol bus by the service protocol connector using a communication protocol depending on application software executed by the corresponding service unit and a communication protocol used in the message bus; ,
The communication data D3 transmitted from the client protocol connector through the message bus and taken into the corresponding service protocol connector, or processed by the one service unit and transmitted through the message bus to the corresponding service protocol connector A function to extract the processing data D4 or D8 addressed to the own device from the communication data D7 captured in
When the service unit receives the processing data D5 or D9 obtained by processing the processing data D4 or D8, communication data D7 or D11 for calling a service protocol connector corresponding to the next service unit is sent to the processing data D5 or D9. A bus-type message program that executes a function of creating and transmitting the created communication data D7 or D11 into the message bus. In the one computer,
9. The bus-type message exchange program according to claim 8 , wherein a function for creating the communication data by describing the route information in the same language as the communication data from the client is executed. In the one computer,
9. The bus-type message exchange program according to claim 8 , wherein a function for creating the communication data by describing the route information in a language different from the communication data from the client is executed.

Images