KR101219637B1 - Message oriented middleware device for message communication processing using numeralized topic - Google Patents

Abstract

PURPOSE: A message based middleware device for performing message communication by using a numbered topic is provided to perform message communication between client terminals and processors executed in the client terminals, thereby increasing communication speed. CONSTITUTION: An execution means executes a message exchange queue program. The message exchange queue program generates a new second name corresponding to a first name requested by a client terminal(20). Server terminals are connected by a chain structure. A monitoring terminal sets up a message exchange server terminal(10) executing the message exchange queue program and monitors an operation of the server terminal. The message exchange server terminal numbers the first name. The message exchange server terminal generates and transmits the second name. [Reference numerals] (10) Server terminal; (20) Client terminal publication; (21,22) Client terminal subscription

Description

Message-oriented middleware device for message communication processing using numeralized topic}

The present invention relates to a message based middleware device for performing message communication using digitized topics.

Data is sent and received between different processors using Unix's IPC or socket. However, the method provided by the operating system (OS) may not meet the requirements in some cases, and in most cases, a combination of methods appropriate to the situation is used.

A program created by combining these methods may require modification of the program or change of interface in case of changing requirements or adding communication subjects.

In general, message-based middleware (hereinafter referred to as MOM) separates various requirements and changes of communication subjects and methods of interface to provide convenience of maintenance and consistency of communication programs. To implement this functionality, MOM uses a method called publish / subscribe, which means asynchronous communication that operates in a fire and forgot manner. However, this approach generally does not guarantee data delivery.

Since such a general MOM corresponds to one program, there is a problem in that a situation such as 100% system utilization and a lack of resources of a network cannot be overcome. Thus, message queuing using file / memory, guaranteed message delivery, round-robin, and server-to-server to avoid data loss in these situations. It is necessary to provide functions such as fail-over.

An embodiment of the present invention provides a message for performing message communication using a digitized topic that can improve communication speed by using a message exchange program that performs message communication between client terminals and processors executed in the client terminal. It provides a base middleware device.

A message-based middleware device that performs message communication using a digitized topic according to an embodiment of the present invention may generate a new second name corresponding to a first name requested by at least one client terminal. Means for executing a queue program (mxque), each comprising at least two server terminals connected in a chain structure, and performing message communication between the client terminals and at least one or more processors running on the client terminal; And at least two server terminals set any one server terminal for executing the message exchange queue program, and an mx monitoring terminal for monitoring the operation of the set server terminal, between the client terminals, and between the processors. Connection module On, but by performing the message exchange program execution queue the message transmission service request, it characterized in that it comprises a mx server device for generating and transmitting the second name numbered the first name.

The mx monitoring terminal, when the operation of the mx server terminal for executing the message exchange queue program is abnormally terminated, another server terminal for monitoring the mx server terminal is configured to re-run the message exchange queue program do.

The second name may include a function defining a multiple communication method or a 1: 1 communication method of N: M (where N and M are integers).

The mx server terminal is capable of performing N: M multiple communication or 1: 1 communication according to the function defined by the second name.
When there is a processor to communicate with the client terminal, the mx server terminal may perform 1: 1 communication between the processors, and perform N: M multiple communication between the client terminals. It can be characterized by.
The message exchange queue program includes an object library having a second name in which data corresponding to the first name is composed of numbers, and a name corresponding to a name requested to be transmitted by the client terminal is automatically called from the object library. It is characterized by.

delete

delete

The message-based middleware device that performs message communication using a digitized topic according to an embodiment of the present invention performs message communication between client terminals and processors executed in the client terminal by using the same message exchange program. Can improve the communication speed.

1 is a block diagram schematically illustrating a message-based middleware device for performing message communication using a digitized topic according to an embodiment of the present invention.
2 is a block diagram schematically illustrating a structure and an operation of a server terminal of a message-based middleware device that performs message communication using a digitized topic according to an embodiment of the present invention.
3 is a diagram illustrating a possible example of a connection configuration between a client terminal, a server terminal, and a client terminal through a message-based middleware device performing message communication using a digitized topic according to an embodiment of the present invention.
4 is a diagram illustrating an example of a relationship between an event function call and a client terminal of a message-based middleware device that performs message communication using a digitized topic according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention.

1 is a block diagram schematically illustrating a message-based middleware device for performing message communication using a digitized topic according to an embodiment of the present invention, and FIG. 2 is a digitized topic according to an embodiment of the present invention. Is a block diagram briefly illustrating a structure and an operation of a server terminal of a message-based middleware device that performs message communication using FIG. 3, and FIG. 3 illustrates message communication using a digitized topic according to an embodiment of the present invention. A diagram illustrating a possible configuration of a connection configuration between a client terminal, a server terminal, and a client terminal through a message based middleware device.

1 and 3, a message-based middleware device for performing message communication using a digitized topic according to an embodiment of the present invention may include a client terminal through a message exchange queue program and a server terminal 10. 20 is a device for performing message communication between processors executed in the client terminal 20.

More specifically, a message-based middleware device for performing message communication using a digitized topic according to an embodiment of the present invention executes one execution program 1 which is a message exchange queue program. Means and at least two server terminals 10. Here, the message exchange queue program (hereinafter referred to as mxque) generates a new second name corresponding to the first name requested to be transmitted by the client terminal 20. The first name means a topic used for communication between the client terminals 20, 21, and 22. These topics are addresses of messages that the programmer specifies and can be created arbitrarily as needed. The topic is composed of characters, which serve as a port of a socket and an IP address or a key of a message queue. For example, the first topic may be “/ abc / 123”. The distribution of messages by the topic is handled by a message engine such as the mx server terminal 120 described later. The second name is formed by digitizing the first name and serves as a topic. For example, the second name may be in the form of “1234567890” that is digitized to correspond to the first name “/ abc / 123”. The message-based middleware device according to the present invention can use up to 256 blocks, 8 blocks separated by "/", as a topic. At this time, "*" and "?" In the name of the topic means a wild character. This second name may include a function defining a multiple communication scheme of N: M (where N and M are integers) or a 1: 1 communication scheme. Accordingly, the mx server terminal 120 can perform N: M multiple communication or 1: 1 communication according to the function defined by the second name. For example, if the message is TOPIC_HUB, the message using the topic is distributed in a hub manner, and if it is TOPIC_P2P, it is distributed in a peer-to-peer manner. Therefore, in the present invention, unlike the general method of inspecting a topic registered for message communication and delivering a message to the topic, by switching the topic to a number to skip the search of the topic to deliver the message, the communication speed of the message It will be possible to improve.

When the server terminal 10 is connected in a chain structure and one server terminal is abnormally terminated, the mx monitoring terminal 110 for monitoring the corresponding server terminal is re-executed. The server terminal 10 includes at least two server terminals 110, 120, 130, and 140. Specifically, the server terminal 10 sets any one server terminal for executing the message exchange queue program 1, the mx monitoring terminal 110 and the client terminal to monitor the operation of the set server terminal A connection module between (20, 21, 22) and the processor (not shown), executing the message exchange queue program 1 to execute a message transfer request service, wherein the first name is digitized 2 includes an mx server terminal 120 for generating and transmitting a name. In addition, the server terminal 10 includes the mx first monitoring terminal 130 in charge of monitoring the server resources, and the mx second monitoring terminal 140 for automatically executing or monitoring the hourly client terminal by the client table. It may further include. Preferably, the server terminal 10 used in the present invention is composed of mx monitoring terminal 110, mx server terminal 12 0, mx first monitoring terminal 130 and mx second monitoring terminal 140. It can consist of four daemons.

In addition, the message-based middleware device according to the present invention can implement both a hub (HUB) method and a peer to peer method through mxque (1). Here, the hub method A function of distributing a message to a corresponding topic in a publish / subscribe process, and the peer-to-peer method does not go through a message engine, that is, an mx server terminal 120, and the client terminal 20 and the client. This means sending and receiving messages through a direct connection between the terminals 21 and 22. According to the present invention, a form of a topic is defined through a message-based middleware device, and both methods may be used. In particular, the message-based middleware device according to the present invention can support high-speed multi-communication (N: M) by allowing the server terminal 10 that performs the message hub to be integrated management. For example, as described above, the message using the topic is distributed in the hub manner if TOPIC_HUB, and in the peer-to-peer manner if TOPIC_P2P.

A message-based middleware device for performing message communication using a digitized topic according to an embodiment of the present invention configured as described above may have a communication scheme and a connection structure as shown in FIG. 3. Hereinafter, a communication method that can be implemented by the message-based middleware device according to the present invention between the mx server terminal, the client terminal and The description will be made between the mx server terminals and the client terminals.

between mx server terminals

In the server where the message-based middleware device is installed, the mx server terminal 121 serves as a message engine, and sockets are connected between the mx server terminals 121 and 122.

Between client terminal and mx server terminal

When the mx server terminal 121 and the client terminals 21 and 22 exist in the same node (node # 1), the mx server terminal 121 and the client terminal (21) 22 is connected by IPC (Inter-Process Communication), if necessary, is connected to the socket. In addition, when the mx server terminal 121 and the client terminal (that is, the remote client terminal) 25, 26 are present in other nodes (node # 1, node # 4), it is connected to the socket. In addition, when the connection between the mx server terminal 121 and the client terminals 21 and 22 is abnormally terminated, the adapter thread of the client automatically reconnects to the mx server terminal.

Between client terminals

In the connection between the client terminals 23, 24 and 26, the communication means is changed according to the type and position of the TOPIC. That is, the communication method in the case of connecting TOPIC_IPC between two client terminals 23 and 24 in the same server (node # 2) is IPC, and in the case of TOPIC_P2P, a socket is used. However, if two client terminals 25 and 26 exist in different servers (node # 2 and node # 3), IPC cannot be used and sockets are used.

On the other hand, according to the message-based middleware device for performing a message communication using a digitized topic according to an embodiment of the present invention, it is possible to support low latency data communication between processors, between servers, Specifically, multiple communication through the message engine and 1: 1 (limited N: M communication) communication between processors can be implemented using one application programming interface (API). You can decide. Furthermore, since the message-based middleware device according to the present invention uses an API having the same structure as a method of opening / closing / reading / writing a file system, a communication program is produced. Not only can provide shorter periods of time, ease of maintenance and variety of communication methods, but also allows users to round-robin, guaranteed delivery, message queuing, as described below. Make g) easy to use. Hereinafter, the features and functions of the message-based middleware device according to the present invention for providing such an effect will be described in detail.

Features of Message-Based Middleware Device According to the Present Invention

The message-based middleware device according to the present invention may implement publish / subscribe of various characteristics according to a topic type. For example, TOPIC_HUB is a general publish / subscribe feature, TOPIC_P2P is a topic for peer-to-peer, TOPIC_MQ is message queuing, TOPIC_IPC is high-speed peer-to-peer communication on the same server, TOPIC_GD also defines the topic for Guaranteed Delive-ry.

In addition, the message-based middleware device according to the present invention may implement a publish / subscribe (publsh / subscribe) according to the message delivery (message delivery) method. For example, Request / Reply, cumulative data transfer by message queuing, publish to receive an ack from a subscriber, multiple subscribers / nodes It is possible to round-robin for multiple topics, subscribe to multiple topics at the same time, and publish / publish by multiple characters (publis -h / subscribe).

In addition, the message-based middleware device according to the present invention can implement CPU affinity (linux version). For example, four daemons (ie server terminals) that are used as message engines, CPU allocation for each client, and the execution type suitable for the operating server environment can be provided to provide an optimized usage environment of the CPU cache. Can be.

In addition, the message-based middleware device according to the present invention may provide a fail-over function. For example, system failover between clients running on each of the two servers, automatic server switching in the event of a client's connection server failure, node master / slave switching, and slab A client hold function of a slave node and a message drop prevention function by guaranteed delivery can be provided.

Function of message-based middleware device according to the present invention

The message-based middleware device according to the present invention performs publish / subscribe through a message engine such as an mx server terminal. Specifically, publish / subscribe and round-robin ), Publish, receive ack, message queuing, Request / Reply, and Guaranteed delivery. In addition, publication / subscribe is performed through direct communication between clients. More specifically, publication / subscribe, round-robin, and approval to receive an ack. You can implement the (p -ublish) function.

In addition, as a failover function, abnormal termination of a publish / subscribe-be, a master node, and a publish client is performed.

4 is a diagram illustrating an example of a relationship between an event function call and a client terminal of a message-based middleware device that performs message communication using a digitized topic according to an embodiment of the present invention.

Referring to FIG. 4, a message-based middleware device performing message communication using a digitized topic according to an embodiment of the present invention may include a message arriving at a subscribe side, a response to a request, and the like. If a wait condition occurs as well, a message arrives at the waiting topic and the program can be programmed to execute the registered function. At this time, the developer can define and use the topic and the function to be called. In this case, the called function is structured to be executed by a separate thread. As such, in addition to user-defined topics and function calls, events such as master / slave switching, automatic reconnection, connection, close, and so on, may occur when each event occurs. If you define, the function is called automatically. That is, after the client terminal is connected (con -nection) to the mx server terminal 120, an adapter thread is automatically generated and communicates with the mx server terminal.

In addition, when the message-based middleware device according to the present invention uses an independent thread in one program, the message-based middleware device can be connected to the message-based middleware device running on several computers. Through this, the load balancing effect of the work can be obtained and the execution of the main work can be guaranteed.

Meanwhile, to describe the configuration of an API and a program used in a message-based middleware device for performing message communication using a digitized topic according to an embodiment of the present invention, an API used in a client terminal of a message-based middleware device The library is provided in two forms, a shared object and a static object, and includes a header file required for this.

Table 1 below is a directory created after the installation of the message-based middleware device.

Directory Contents ~ / bin Executor and four server terminals ~ / clilog Client log file of a user with a message-based middleware device according to the present invention ~ / env Execution environment file of message-based middleware device according to the present invention ~ / inc Header file for client program development ~ / lib Shared object library ~ / libs Static object library ~ / license License file ~ / log Log file on the server terminal ~ / queue File for message queue ~ / table Errcode table, CPU table, client table ~ / tutorial Example Program in the Tutorial Manual ~ / GD Archive for Guaranteed Delivery

In addition, Table 2 below is an example of a client program, which is a program that publishes arbitrary data.

6 #include "mxqapi.h"
7
8 int main ()
9 {
10 int rtn, id, deliverytype = 0;
11 int i, sndsize, size = 256;
12 int waitsec = 0, waitmsec = 0;
13 char topicname [256];
14 unsigned char data [1024];
15
16 rtn = MXconnect ( NULL , 0, NULL , NULL , 5, NULL );
17 if (rtn <0)
18 {
19 printf ("ERROR:% s \ n", MXgetErrMsg ());
20 exit (0);
21}
22 strcpy (topicname, "/ sample / topic");
23 id = MXopenTopic ( TOPIC _ HUB , topicname , 0);
24 if (id <0)
25 {
26 printf ("ERROR:% s \ n", MXgetErrMsg ());
27 exit (0);
28}
29 memset (data, 'a', 1024);
30 size = 1024;
31 for (i = 0; i <10; i ++)
32 {
33 sndsize = MXpubMsg ( id , deliverytype , data , size , waitsec , waitmsec );
34 if (sndsize <0)
35 {
36 printf ("ERROR:% s \ n", MXgetErrMsg ());
37 exit (0);
38}
39 printf ("PUB:% d:%. 50s .. \ n", sndsize, data);
40 sleep (1);
41}
42 MXcloseTopic ( id );
43 MXdisconnect (0);
44 exit (0);
45}

Briefly based on the API used for [Table 2], MXconnect () indicates connection between client (i.e. client terminal) and mxserver (i.e. mxserver terminal), and MXopenTopic () indicates the topic to use. This is to request a topic open by using mxserver to get a topic id for future use. In addition, MXpubMsg () sends arbitrary data to the topic id obtained from MXopenTopic (), MXcloseTopic () closes the used topic, and MXdisconnect () terminates the connection with the mx server terminal. . In this way, the use of a topic may have the same structure as that of a Unix stream.

What has been described above is only one embodiment for implementing a message-based middleware device for performing message communication using the digitized topics according to the present invention, the present invention is not limited to the above embodiment, the following patents As claimed in the claims, any person of ordinary skill in the art without departing from the gist of the present invention will have the technical spirit of the present invention to the extent that various modifications can be made.

1: mxque 10: server terminal
20: client terminal 110: mx monitoring terminal
120: mx server terminal 130: mx first monitoring terminal
140: mx 2nd monitoring terminal

Claims (6)

Means for executing a message exchange queue program (mxque) for generating a new second name corresponding to the first name requested to be transmitted by at least one or more client terminals; And
At least two server terminals each connected in a chain structure;
A message communication between the client terminals and at least one or more processors running on the client terminal;
The at least two server terminals,
An mx monitoring terminal configured to set any one server terminal for executing the message exchange queue program and to monitor an operation of the set server terminal; And
An mx server, which is a connection module between the client terminals and between the processors, executes the message exchange queue program to execute a message transfer request service, and generates and transmits the second name by digitizing the first name. Message-based middleware device for performing a message communication using a digitized topic, characterized in that it comprises a terminal.
The method of claim 1,
The mx monitoring terminal, when the operation of the mx server terminal for executing the message exchange queue program is abnormally terminated, another server terminal for monitoring the mx server terminal is configured to re-run the message exchange queue program Message-based middleware device for performing a message communication using a digitized topic.
The method of claim 1,
The second name may be a message communication using a digitized topic, characterized in that it may include a function for defining a multiple communication scheme of N: M (where N, M is an integer) or 1: 1 communication scheme Message-based middleware device that performs.
The method of claim 3,
The mx server terminal is a message-based middleware device for performing a message communication using the digitized topic, characterized in that the N: M multiple communication or 1: 1 communication according to the function defined by the second name. .
5. The method of claim 4,
The mx server terminal,
When there is a processor to be communicated with the client terminal, the processors may perform a 1: 1 communication, and the client terminals may perform N: M multiple communication. Message-based middleware device for performing a message communication using a digitized topic.
The method of claim 1,
The message exchange queue program includes an object library having a second name consisting of numbers of data corresponding to the first name.
And a message corresponding to a name requested to be transmitted by the client terminal is automatically called from the object library.

Images