KR100521415B1 - XML-based message switching apparatus and method for distributed application data - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to an XML-based message switching device and method for distributed application data interworking.

2. The technical problem to be solved by the invention

The present invention, in the development of distributed applications for the corporate environment, is responsible for the switching of XML-based data exchanged between the interoperable systems to more easily define, update, delete XML data and receive / receive such information An object of the present invention is to provide an XML-based message switching device and a method thereof.

3. Summary of Solution to Invention

The present invention provides a message switching device for distributed application data interworking, comprising: an XML-based message definition and subscription with an information sharing management system and an interworking system via a web service, and a web service interfacing means for calling a message; Message queue monitoring means for monitoring whether an XML message has been received in the message queue from the companion system; Storage means for storing information on definitions and subscriptions of XML messages received from the management system; Message identification means for identifying an XML message received from the companion system via a web service or in the message queue based on the XML message definition information (XPath decision key value); Message tracking processing means for determining whether a header exists and tracking a message flow as header information when the identified XML message has a message definition; Message subscription identifying means for searching for a destination registered to subscribe to the identified XML message based on the XML message subscription information; Message logging processing means for recording a processing history of the XML message; Includes message delivery processing means for delivering an XML message with a distinct destination to that destination.

4. Important uses of the invention

The present invention is used for XML-based message switching device.

Description

XML-based message switching apparatus and method for interworking distributed application data {XML-based message switching apparatus and method for distributed application data}

The present invention relates to a message switching device and method based on XML (XML: eXtensible Markup Language) for distributed application data interworking. In particular, in the development of distributed applications for an enterprise environment, XML-based communication between various systems interworking with each other is provided. The present invention relates to an XML-based message switching device and method for easily defining, updating, and deleting XML data and facilitating reception / reception of such information by in charge of switching data.

Traditional communication middleware implements clients and servers, and since they are closely related to each other, they must be compiled together. In addition, the existing communication middleware must design the interface at the time of design, and implement it in a manner such as Kovar or Distributed Component Object Model (DCOM). Therefore, the communication module implemented as described above has a close relationship with the associated interworking module, and thus there is a problem in that the design of the component / system for transmitting information and the receiving component / system cannot freely create interworking between systems.

Regarding the related art, an "XML document retrieval apparatus and method for supporting XML query words tightly coupled with a database query word" (Republic of Korea Patent Publication No. 10-0054605, published date 2003.7.2) are as follows.

This patent is a syntax analysis module for receiving an integrated query in which a database query word and an XML query word are tightly coupled through an external device, and analyzing the integrated query to generate a syntax tree for the integrated query. A query processing module which executes a query required by an XML query word using the generated syntax tree, a query processing module which performs a query requesting a result of the query processing by the database engine, and a query processing module of the query processing module. A result processing module for converting a query execution result into a form suitable for processing by a database engine, and a search management module for controlling the syntax analysis module, the query processing module, and the result processing module, and performing an interface with a database engine. XML documents can be retrieved by the XML document retrieval device Existing data can be easily interlocked and XML query processing performance can be optimized.

However, this is because the DB is used to query a large amount of XML data. Therefore, it only improves the XML document identification and cannot solve the identification easily using XPath technology for different XML documents. have.

The present invention has been proposed to solve the above problems, and in the development of distributed applications for the corporate environment, it is more convenient to define the XML data by taking care of switching the XML-based data exchanged between the interoperable systems An object of the present invention is to provide an XML-based message switching device and a method for easily updating, deleting, and receiving / receiving such information.

The present invention for achieving the above object, in the message switching device for distributed application data interworking, XM (XML) -based message definition and subscription with the information sharing management system and the interworking system through a web service, message calling Web service interfacing means for; Message queue monitoring means for monitoring whether an XML message has been received in the message queue from the companion system; Storage means for storing information on definitions and subscriptions of XML messages received from the management system; Message identification means for identifying an XML message received from the companion system via a web service or in the message queue based on the XML message definition information (XPath decision key value); Message tracking processing means for determining whether a header exists and tracking a message flow as header information when the identified XML message has a message definition; Message subscription identifying means for searching for a destination registered to subscribe to the identified XML message based on the XML message subscription information; Message logging processing means for recording a processing history of the XML message; Characterized in that it comprises a message delivery processing means for delivering a distinguished XML message to the destination.

In addition, the present invention, in the message switching method for the distributed application data interworking, determining the structure of the data to be exchanged between the interworking system, extracting the main data structure to register the message information registration information and XML message subscription information XML registration step; A message identification step of identifying an XML message received from the companion system through a web service or a message queue based on the XML message definition information (XPath decision key value); A message tracking step of determining whether a header exists and tracking a message flow as header information when the identified XML message has a message definition; A message subscription identification step for searching for a destination registered to subscribe to the identified XML message based on XML message subscription information; And a message delivery step of delivering the XML message distinguished from the destination to the corresponding destination.

Accordingly, an object of the present invention is to facilitate the development of information definition and update and systems for transmitting and receiving information in message-based mutual information interworking when developing distributed applications. Existing communication middleware has to be closely related to the implementation of the client and server, and compiled together, whereas the present invention implements and operates a system for switching information between interworking components or systems completely independently. Therefore, since the component / system for transmitting information and the component / system for receiving information can be designed and implemented independently, it is possible to create interworking between systems more freely.

As such, the present invention is closely related to communication middleware represented by technologies such as existing COVA or DCOM. Therefore, the present invention can define a message and subscribe to a message regardless of the interworking module. In addition, since XMSS is implemented based on XML web service, all systems interworking through XMSS can use a flexible data standard format called XML and can be implemented relatively lightly using a scalable structure of web. Conventional XML document identification method is based on the XML Schema Definition (XSD), but the present invention uses the "XPath decision key" included in the message definition, if there is an XML element returned by the XPath statement to the message It has a structure to identify it, which is simpler than XSD and has a feature that can be conveniently implemented.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is an exemplary view illustrating an environment in which an XML-based message switching device is interworked with an external system according to the present invention.

The XML-based message switching device (XMSS) 20 determines the structure of the data to be exchanged between the interworking system 12, extracts the main data structure, sets the XML document identification criteria using XPath syntax, and sets the XPath identification criteria for each interworking information. After defining and identifying the interlocking information on the basis of this, if the reception of the corresponding information is registered in the system to receive the information defined as the interlocking information, it transmits the identified interlocking information to the desired interlocking system 12. A more detailed description thereof will be described later with reference to FIGS. 2 and 3.

The management system 11 manages information sharing among various systems, and is generally implemented in the form of a user interface (UI) system, and defines data to be transmitted and received through this system. At this time, the data is defined in the form of an XML document, and when defining a message, validation confirmation using XML XSD may be an option.

The management system 11 implements the registration / change / delete / query of the message definition through the web service interface unit 21.

The web service interface unit 21 is one of several web service interfaces, and has a function of registering / modifying / deleting / looking up a message definition and having a function of registering / modifying / deleting / looking up a message subscription to receive the defined messages. .

The XMSS web service processing unit 23 is an implementation module of the web service interface. In this module, the message definition information storage unit 24 and the message subscription information storage unit interpret the information related to the message definition and subscription delivered from the management system 11. Perform the function of saving / modifying / deleting in the appropriate form in (25). The message definition information storage unit 24 and the message subscription information storage unit 25 may be separately configured, and may be integrally implemented.

The message definition information storage unit 24 is an object containing a message definition and may store a message in the form of a database, a memory, or a general file. At this time, the contents included in the message definition are as follows.

(1) Message sender name: Name of the system that generates the message (optional input)

(2) Message type: The type of message classification (optional input)

(3) Message identifier: An identifier that uniquely identifies the message (mandatory input)

(4) Message description: description of the message (optional input)

(5) XPath decision key for distinguishing messages: XPath syntax for identifying messages. If there is an element extracted by applying this decision key value to XML data, it is recognized as a relevant message. (Required)

<Example of XPath decision key value>

① If you want to identify a message based on two XML elements and values:

  // serviceOrderNo [. = '1' and ../ ContractType [. = '1234']]

② If you want to identify message with only one XML element

  // ClaimRequestForm

③ When trying to identify based on XML elements and upset values of complex structure

  // root [../sub and ../sub2 and ../cost[@value and @date]]

(6) Message schema: XSD of the message. Input for validation of message. (Optional input)

The message subscription information storage unit 25 is an object containing message subscription information and may store a message in the form of a database, a memory, or a general file. At this time, the message subscription information is as follows.

(1) Message subscription system name: System name to subscribe (receive) the message (required)

(2) Message subscription list: list of message identifiers to subscribe (receive) (mandatory input)

(3) How to receive messages: Whether to use queue or web service. In the case of using a web service, the reference path of the web service must be entered (mandatory).

The interworking system 12 may generate a message to interrelated systems, or may receive a desired message. At this time, when receiving through the message queue 13 includes a structure for monitoring the message queue 13 (message queue 13 monitoring module), when receiving through the web service for receiving the corresponding web service A web service receiving unit 16 is provided. However, the basic is to use the message queue. This is to take advantage of the message-based communication.

The web service interface unit 22 is for receiving data among web services provided by the XMSS 20. The interworking system 12 calls the XML data to be delivered to the web service interface unit 22 of the XMSS.

The message queue 14 is used when the interworking system 12 uses the message queue instead of the web service for XML data transmission. In order to transmit through this message queue 14, the following information should be input.

(1) Message providing system name: System name to which the message is to be sent. The message queue corresponding to this name is automatically created and monitored by XMSS (mandatory input).

The queue monitoring unit 231 of the XMSS web service processing unit 23 monitors whether a message has been received in the corresponding message queue 14, and, if there is a message, the XML data received through the web service interface unit 22. Process in the same flow.

The database 15 is a place where a log is processed before transmitting a message classified through the XMSS web service processing unit 23 and the destination of XML data is distinguished.

The message queue 13 is a place for storing XML data of which destinations are distinguished through the XMSS web service processor 23. Accordingly, through this message queue 13, the interworking system 12 that has registered a message subscription monitors its own message queue 13 and, if there is a message, receives and processes it. In addition, the interworking system 12 may receive a web service message through the web service receiving unit 16.

2 is a block diagram of an embodiment of an XML-based message switching device according to the present invention.

As shown in FIG. 2, the XML-based message switching device (XMSS) 20 according to the present invention defines an XML-based message with the management system 11 and the interworking system 12 through the web service. And an XMSS web service interface unit 21 and 22 for subscription and message invocation, a queue monitoring unit 231 for monitoring whether an XML message is received from the interworking system 12 to the message queue 14, and a management system. On the basis of the message definition information storage unit 24 and the message subscription information storage unit 25, which store information on the definition and subscription of the XML message received from (11), and the XML message definition information (XPath decision key value). For example, the message identification unit 232 for identifying the XML message received through the web service or the message queue 14 from the interworking system 12 and, if the message definition is defined in the identified XML message, presence or absence of a header Is determined as header information. A message tracking processor 233 for tracking the flow of the message, a message subscription identifier 234 for searching for a destination registered to subscribe to the identified XML message based on the XML message subscription information, and a processing history of the XML message. A message logging processing unit 235 for recording the data into a database 15, and a message delivery processing unit 236 for delivering an XML message distinguished from a destination to a corresponding destination (the message queue 13 or the web service receiving unit 16). It includes.

An operation of the XML-based message switching device (XMSS) according to the present invention having the above configuration will be described in more detail with reference to FIG. 3.

First, the management system 11, through the web service interface unit 21, message definition information (message sender name, message type, message identifier, message description, XPath decision key, etc.) and information about subscription (i.e., message subscription system). The name, message subscription list, and message receiving method (web service call or message queue) are registered in the message definition information storage unit 24 and the message subscription information storage unit 25 (301). Of course, the management system 11 is capable of changing, deleting, and inquiring information stored in the message definition information storage unit 24 and the message subscription information storage unit 25.

Subsequently, when the message is called through the web service interface unit 22, the message identification unit 232 analyzes (identifies) the message based on the XPath decision key value among the message definition information stored in the message definition information storage unit 24. (302).

As a result of the analysis, when the identified XML message has a message definition, the message tracking processing unit 233 determines the existence of the XMSS header of the message input to the XMSS 20, and performs a processing function for message tracking (303). ).

That is, the header does not exist in the case of the first input message, and if the header is input again to the XMSS 20 to be sent to another interworking system for subsequent processing after being inputted to the interlocking system 12, the header is attached. Will be entered (interlocking system optional). Accordingly, the XMSS 20 basically generates the following information on the headerless XML message, and the generated header information is stored in the database 15 to provide a function of tracking the flow of the message.

(1) Message Identifier: Identifier of the message. Messages whose identifiers are not identified are discarded, leaving only the record in the database. If there is no identifier, it is indicated separately as "Not Matched" (mandatory).

(2) Transmission system name: name of the interlocking system that delivered the message (input based on the message definition)

(3) Date and time of transmission: The point of time when a message is entered in the XMSS system (required)

(4) Message Unique Number: A serial number that is sequentially incremented by one per message initially entered (ie, without an XMSS header), regardless of the message identifier, to track the processing of the message.

(5) Additional Information: Defined when necessary (optional).

As a result of the analysis, when the message definition is not defined in the identified XML message, the message analysis result is transmitted to the message logging processing unit 235, and only the record is left in the database 15 (305).

Meanwhile, the message subscription identification unit 234 finds the linked system 12 registered to subscribe to the identified XML message based on the message subscription information storage unit 25 (304). At this time, if there is the corresponding subscription information, as the message subscription is identified, the message is sent to the actual message queue 13 (in this case, the message queue 13 is already generated at the message subscription registration step) or a web service call method ( When the message subscription is registered as a web service, the message is processed through the message delivery processing unit 236 to the web service receiving unit 16 of the interworking system 12 (306). At this time, all of the XML message processing records of the XMSS 20 may be transferred to the message logging processing unit 235 and recorded in the database 15 (307).

The database 15 stores all the processing records of the XMSS 20, and can track the flow of the message by the message unique number and time.

As described above, the present invention is composed of an XML web service for inputting / modifying message definition and message subscription information, a database for recording all operations of the XMSS, and a message queue infrastructure used by the XMSS. XML web service is a method of sending and receiving data through the web using internationally standardized XML and SOAP (Simple Object Access Protocol) protocol. For example, Microsoft's MSMQ (MicroSoft Message Queuing) is the message queue infrastructure. Message delivery and reception through the message infrastructure has the advantage of preserving data and loosely interworking messages even in the abnormal operation of each interworking system.

The method of the present invention as described above may be implemented as a program and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.). Since this process can be easily implemented by those skilled in the art will not be described in more detail.

The present invention described above is not limited to the above-described embodiments and the accompanying drawings, and various substitutions, modifications, and changes are possible in the art without departing from the technical spirit of the present invention. It will be clear to those of ordinary knowledge.

The present invention as described above, in the message-based mutual information interworking in the development of distributed applications, to facilitate the update and update of information and the development between systems that transmit and receive it, the following effects can be obtained .

First, you can freely define a message in XML format whenever necessary and register it in XMSS, and you can identify the message without defining an XSD.

Second, the message identification method through XPath can specify a variety of message identification criteria ranging from XML element, XML attribute, and corresponding value (XML element / attribute value). You can identify the message at a comparable level, or you can define it very simply.

Third, interworking systems can be conveniently implemented because of the advantages of Message Queuing and Web services.

In addition, the present invention, since the component / system for transmitting information and the component / system for receiving can be designed and implemented independently, there is an effect that can create a linkage between systems more freely.

1 is an exemplary view illustrating an environment in which an XML-based message switching device according to the present invention is linked to an external system.

2 is a block diagram of an embodiment of an XML-based message switching device according to the present invention;

3 is a flowchart of an embodiment of an XML-based message switching method according to the present invention;

* Explanation of symbols for the main parts of the drawings

21,22: XMSS web service interface unit 23: XMSS web service processing unit

24: message definition information storage unit 25: message subscription information storage unit

231: queue monitoring unit 232: message identification unit

233: message tracking processor 234: message subscription identification unit

235: message logging processing unit 236: message delivery processing unit

Claims (8)

In the message switching device for distributed application data interworking, A web service interfacing means for defining and subscribing an XML-based message to an interworking system through an information sharing management system and a web service, and invoking a message; Message queue monitoring means for monitoring whether an XML message has been received in the message queue from the companion system; Storage means for storing information on definitions and subscriptions of XML messages received from the management system; Message identification means for identifying an XML message received from the companion system via a web service or in the message queue based on the XML message definition information (XPath decision key value); Message tracking processing means for determining whether a header exists and tracking a message flow as header information when the identified XML message has a message definition; Message subscription identifying means for searching for a destination registered to subscribe to the identified XML message based on the XML message subscription information; Message logging processing means for recording a processing history of the XML message; Message delivery processing means for delivering an XML message with a distinct destination to that destination. XM-based message switching device for distributed application data interworking comprising a. The method of claim 1, The XML message definition information is An object that contains a message definition, where the message is stored in the form of a database, memory, or general file, the name of the message sender (system name that generates the message (optional input)), the message type (type of message classification (optional input)). ), The message identifier (the identifier that uniquely identifies the message (mandatory input)), the message description (the description of the message (optional input)), the XPath decision key for identifying the message (the XPath syntax for identifying the message. X-ML-based message switching device for distributed application data interworking, characterized in that it includes a (required input) to recognize the message when there is an element extracted by applying to the XML data. The method of claim 1, The XML message subscription information is As an object that contains subscription information, messages are stored in the form of database, memory, general file, message subscription system name (system name (required) to subscribe to (message)), message subscription list (subscription (receive) List of message identifiers (mandatory input)), message reception method (whether to use queue or web service. In case of using web service, the reference path of the corresponding web service must be entered (mandatory input). XM-based message switching device for distributed application data interworking, comprising a). The method according to any one of claims 1 to 3, The message identifying means, With XPath, there is no need to define and distribute XSD every time data is changed, and when important elements to identify data are changed, a separate message or an XPath decision key value should be modified, but less important non-determinants change. The X-ML based message switching device for interworking distributed application data, characterized in that it can be used without modifying the definition of the message. The method of claim 4, wherein The message tracking processing means, Inserting a header for tracking messages, and storing the processing information in the database, XM-based message switching device for distributed application data interworking, characterized in that to track the flow of messages between the interworking system. In the message switching method for distributed application data interworking, A message information registration step of determining a structure of data to be exchanged between the interworking systems, extracting a main data structure, and registering XML message definition information and XML message subscription information; A message identification step of identifying an XML message received from the companion system through a web service or a message queue based on the XML message definition information (XPath decision key value); A message tracking step of determining whether a header exists and tracking a message flow as header information when the identified XML message has a message definition; A message subscription identification step for searching for a destination registered to subscribe to the identified XML message based on XML message subscription information; And Message delivery step of delivering the XML message with the destination to the destination XM-based message switching method for distributed application data interworking comprising a. The method of claim 6, The XML message definition information includes a message sender name (system name for generating a message (optional input)), a message type (type for classifying a message (optional input)), a message identifier (identifier for uniquely distinguishing a message (mandatory input). )), The message description (message description (optional input)), the XPath decision key for identifying the message (the XPath syntax for identifying the message, and if the element extracted by applying this decision key value to the XML data, Recognized (required)) The XML message subscription information includes a message subscription system name (system name (mandatory input) to subscribe to (receive) a message), a message subscription list (list of message identifiers (required input) to subscribe to (receive)), and message reception. Method for interworking distributed application data, including a method (whether to use a queue or a web service. A reference path of the web service must be entered (mandatory input) in the case of using a web service.) MP-based message switching method. The method according to claim 6 or 7, The message identification step, With XPath, there is no need to define and distribute XSD every time data is changed, and when important elements to identify data are changed, a separate message or an XPath decision key value should be modified, but less important non-determinants change. Can be used without modifying the definition of the message. The message tracking step, Inserting a header for message tracking, and storing the processing information in the database, XM-based message switching method for interworking distributed application data, characterized in that to track the flow of messages between the interworking system.