KR20050001796A - Method for exchanging SOAP message using JMS - Google Patents

Abstract

PURPOSE: A system and a method for exchanging a message capsulating a document or data by an SOAP(Simple Object Access Protocol) using a JMS(Java Message Service) are provided to exchange information asynchronously and stably by interchanging the XML(eXtensible Markup Language) document or data capsulated by the SOAP through a JMS transfer mode. CONSTITUTION: A web application subsystem(200) receives requests for applying for membership and generating/removing a queue/topic from client subsystems(100a,100b). A message relay subsystem(300) transfers a JMS message received form one client, and adding a header and an attribute of a JMS protocol to an SOAP message to other client. A message management subsystem(400) processes a queue/topic generating/removing request of the clients received from the web application subsystem, and records/manages information for the JMS message transmitted from the message relay subsystem. A database(500) stores related information for the JMS message needed from each component.

Description

Simple object access protocol message exchange system using Java message service and its method {Method for exchanging SOAP message using JMS}

The present invention relates to a simple object access protocol message exchange system using a Java message service, and a method and a computer readable recording medium recording a program for realizing the method. System and method for simple object access protocol message exchange using Java message service, which are encapsulated in Simple Object Access Protocol (SOAP) and exchanged with Java Message Service (JMS) transport method. A computer readable recording medium having recorded thereon a program for realization.

In recent years, e-business has brought about major changes in all business activities and the relationship between business and business (B2B). For example, a company shares information with each other via the web to conduct a joint research to trade an item or create a new product with other companies.

On the other hand, as business processes are diversified according to the systems established for each business in a company, and business flows are linked to both inside and outside the company, individual applications of a department or a company can no longer be operated independently within a company. It is gone. The proliferation of electronic commerce has made it necessary to have an information exchange system that can improve the speed and interworking of business by improving the interface between business applications for information exchange between companies.

Currently, each company's information exchange system shares documents or data created by using platform-based applications using different protocols, either inside or outside the enterprise. There is a problem that can not be read directly from other companies.

Conventional technology for solving such a problem is a message exchange system based on the Simple Object Access Protocol (SOAP). The SOAP is a message service standard protocol of E-Business Extensible Markup Language (ebXML), and encapsulates an Extensible Markup Language (XML) document into a SOAP message. Hyper Text Transfer Protocol (HTTP) is defined as a protocol that can be interchanged with each other.

However, in order for a SOAP message produced by one company to be transmitted to another company through an HTTP transmission method, there is a problem in that each company's system is synchronized when the company and the company exchange information.

That is, the client calling the other party for transmitting the SOAP message and the server receiving the call must be closely coupled to each other, and the client cannot proceed with other tasks until the server responds to the call sent by the client. There is this. In addition, when a failure occurs in one system, there is a problem in that the SOAP message transmitted to the failed system by another system is lost in a chain reaction.

The present invention has been proposed to solve the above problems, and in order to asynchronously and securely exchange messages, a document or data is encapsulated in a Simple Object Access Protocol (SOAP) to enable Java Message Service (JMS). Java Message Service) A simple object access protocol message exchange system using a Java message service and a computer readable recording medium having recorded thereon a program for realizing the method. have.

1 is a configuration diagram of an embodiment of a simple object access protocol message exchange system using a Java message service according to the present invention.

2 is an embodiment configuration diagram of a client subsystem in accordance with the present invention.

3 is a diagram illustrating an embodiment of a web application subsystem in accordance with the present invention.

4 is a block diagram of an embodiment of a message relay subsystem according to the present invention;

5 is a diagram illustrating an embodiment of a message management subsystem in accordance with the present invention.

6 is a flowchart illustrating a simple object access protocol message exchange method using a Java message service according to the present invention.

7 is a diagram illustrating an embodiment of a message generation process in a client subsystem according to the present invention.

8 is an exemplary diagram of a message structure generated by a client subsystem according to the present invention.

* Explanation of symbols on the main parts of the drawing

100a, 100b: client subsystem 200: web application subsystem

300: message relay subsystem 400: message management subsystem

500: database

The present invention for achieving the above object, in a Simple Object Access Protocol (SOAP) message exchange system using a Java Message Service (JMS), membership registration and queue from a plurality of clients Web application means for receiving (Queue) / Topic creation and deletion requests; Message relay means for transmitting a JMS message received from one client to the other client, the header and attribute of the JMS protocol added to the SOAP message; Message management means for receiving and processing queue / topic creation and deletion requests of the plurality of clients from the web application means, and recording and managing information of JMS messages transmitted from the message relay means; And storage means for storing relevant information of the JMS message required by each of the above components.

Meanwhile, the present invention provides a method of exchanging a Simple Object Access Protocol (SOAP) message using a Java Message Service (JMS), and generates a queue / topic from one client. Receiving a first step; A second step of creating a queue / topic requested from the client of one side; A third step of receiving and storing a JMS message including a header and an attribute according to a JMS protocol in a SOAP message from the client of one side; A fourth step of confirming whether the client of the other side has the appropriate access right to the JMS message; And a fifth step of transmitting the JMS message to the client of the other side.

On the other hand, the present invention, a message exchange system having a processor, a first function that is requested to create a queue (Queue) / topic (Topic) from one client; A second function of generating a queue / topic requested from the client of one side; A third function of receiving and storing a JMS message added with a header and an attribute according to a JMS protocol to a SOAP message from the client of one side; A fourth function of confirming that the client of the other side has the appropriate access right to the JMS message; And a computer-readable recording medium having recorded thereon a program for realizing a fifth function of transmitting the JMS message to the client of the other side.

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 a block diagram of an embodiment of a simple object access protocol message exchange system using a Java message service according to the present invention.

As shown in FIG. 1, the simple object access protocol message exchange system using the Java message service according to the present invention includes a subscription request and queue / topic from the client subsystems 100a and 100b. JMS (Java Message Service, Sun Microsystems, Inc.) that adds headers and attributes according to the JMS protocol to SOAP messages received from the web application subsystem 200 and the client subsystem 100a on one side for receiving creation and deletion requests. Java-based enterprise messaging application program interface (hereinafter referred to as JMS) proposed by the message relay subsystem 300 for transmitting to the client subsystem (100b) and from the web application subsystem (200) Receives a queue / topic creation or deletion request from the client subsystems 100a and 100b to process the request and In the message management subsystem 400 for recording and managing the information of the JMS message transmitted from the message relay subsystem 300, and in each of the above components such as data conversion data according to the membership application, JMS message transmission and management, etc. It includes a database 500 for storing the JMS message related information required. Hereinafter, a simple object access protocol message exchange system using a Java message service according to the present invention will be described in detail with reference to FIGS. 2 to 5.

2 is an embodiment configuration diagram of a client subsystem according to the present invention.

As shown in FIG. 2, the client subsystem according to the present invention includes a message generating module 110, a message transmitting and receiving module 120, an interpreting module 130, a data conversion module 140, and a data database ( 150). The client subsystem 100a provides a connection interface to a user and generates a SOAP message by encapsulating the document or data converted into an XML document into SOAP, and then adding headers and attributes according to the JMS protocol to the SOAP message. A JMS message is generated and sent to the message exchange system.

In addition, the client subsystem 100a requests a queue / topic creation to the web application subsystem 200 in advance in order to transmit a JMS message to the client subsystem 100b on the other side, and thus creates a queue / topic for the client subsystem 100a. Is assigned. Here, the queue serves as a passage used for one-to-one message transmission, and the topic serves as a passage used for one-to-many message transmission. This queue / topic allows a client subsystem to send a message when it wants to send it and to receive a message when it wants to receive it.

In addition, the client subsystems 100a and 100b may be gateways that collectively manage a user's personal computer or multiple users' personal computers. In addition, the client subsystem is provided with an XML document conversion program, a SOAP message generator, a JMS message generator, and an application program integrating the same.

In addition, the personal computer must go through an authentication process (for example, requesting a user's employee number or checking an Internet address) for each user or a computer thereof, and one gateway goes through one authentication process for this gateway. It can provide services to multiple lower users or their computers.

The message generating module 110 generates a SOAP message by converting a document or data (such as a document or data stored in the data database 150) to be transmitted to the client subsystem 100b of the counterpart into an XML document and encapsulating it in SOAP. After that, the header and attributes according to the JMS protocol are added to the SOAP message to generate a JMS message. At this time, the data conversion module 120 provides data conversion data necessary for message generation to the message generation module 110.

The message transmission / reception module 120 transmits the JMS message generated by the message generation module 110 to the message relay subsystem 300 or receives the JMS message transmitted from the message relay subsystem 300. Here, the message transmission / reception module 120 transmits / receives a transmission / reception message with the message relay subsystem 300 by using a JMS transmission method.

The interpretation module 130 decrypts the message received by the message transmission / reception module 120 and causes the client subsystem 100a to perform the corresponding operation. For example, the interpretation module 130 identifies the attribute of the message and confirms that the attribute is text so that the client subsystem 100b outputs the contents of the text through a notepad or the like. In addition, if the attribute of the message is an executable file, the corresponding file may be executed immediately.

3 is a configuration diagram of an embodiment of a web application subsystem according to the present invention.

As shown in FIG. 3, the web application subsystem 200 according to the present invention includes a web user module 210, a web administrator module 220, and a member authentication unit 230, and an interface for accessing users and administrators. Provides access and work processing function through web. That is, the web application subsystem 200 receives a request for creating or deleting a queue / topic from the client subsystems 100a and 100b, and performs an appropriate authentication process (for example, a member) on the client subsystems 100a and 100b. Subscription, ID and password input request, etc.) and then transmits the corresponding queue / topic creation or deletion request to the message management subsystem 400.

In addition, the web application subsystem 200 automatically performs a function such as a subscription request from a user, a request for creating a queue / topic, and the like, but the user may access the web manager module 220 through an administrator. Application subsystems can be managed and supervised to prevent cracking or malfunctioning of the system by multiple users or illegal users.

The web user module 210 includes a queue / topic application unit 212, a queue / topic details unit 214, and a membership application unit 216, and the web manager module 220 requests a queue / topic application. The processor 222 includes a queue / topic history manager 224 and a member manager 226. In addition, the web application subsystem 200 includes a member authentication unit 230 for performing authentication on the client subsystems 100a and 100b.

The queue / topic application unit 212 receives a queue / topic creation or deletion request from the client subsystems 100a and 100b and requests the queue / topic creation or deletion request from the web manager module 220. And transmits to 222. Then, the queue / topic application processing unit 222 transmits the queue / topic creation or deletion request to the message management subsystem 400, and the processing result (for example, queue / transmission for the message transmission of the client subsystem). Since the topic is created, a notification to send a message, etc.) is returned to the client subsystem 100a or 100b.

The queue / topic description unit 214 stores the queue / topic related information (eg, time resulting from the creation and deletion of a queue / topic, etc.) requested from the client subsystems 100a and 100b. The information is transmitted to the queue / topic description management unit 224 of the device or outputs the information to the client subsystems 100a and 100b according to a request of the client subsystems 100a and 100b.

The subscription request unit 216 receives a subscription request from the client subsystems 100a and 100b and transmits the subscription request to the member manager 226 of the web manager module 220. Then, the member management unit 226 through the member authentication unit 230 connected to the database 500 through the appropriate authentication process (request to enter the user's resident registration number or employee number or confirmation of the corresponding Internet address, etc.) the client subsystem ( Process membership for 100a).

The web manager module 220 manages queue / topic related information and member information of the client subsystems 100a and 100b. In addition, the web manager module 220 provides an administrator with an interface to perform the queue / topic application processing, member management, member authentication, monitoring and statistics functions.

4 is a configuration diagram of an embodiment of a message relay subsystem according to the present invention.

As shown in FIG. 4, the message relay subsystem 300 according to the present invention includes a message transmission module 310 and an access management module 320, and includes message relay, message management, queue / topic management, and access authority. Carry out management, etc.

The message transmission module 310 is a module implemented according to the JMS protocol, and functions to relay message transmission / reception between the client subsystem 100a and the client subsystem 100b of the counterpart. Here, the message transmission module 310 is an unprocessed message when the message exchange system is inoperable (for example, when the server is powered off and a message transmitted by the client subsystem cannot be transmitted to the client subsystem of the counterpart). It stores the delivery message of the queue / topic and its delivery event in the database 500 so that it can be processed later when the message exchange system is recovered.

The access management module 320 confirms whether the client subsystem 100a or 100b has a client subsystem having proper authority when accessing for message transmission / reception. At this time, the access management module 320 requests the message management subsystem 400 for the access authority of the client subsystems 100a and 100b and according to the returned information thereof, the client subsystems 100a and 100b. To control access.

5 is a configuration diagram of an embodiment of a message management subsystem according to the present invention.

As shown in FIG. 5, the message management subsystem 400 according to the present invention includes a client management module 410 and a queue / topic management module 420.

The client management module 410 manages the creation or deletion request queues / topics of the client subsystems 100a and 100b transmitted from the web application subsystem 200 and the corresponding queues to the message relay subsystem 300. Provide information about whether a suitable client subsystem is available for the topic. Here, the message management subsystem 400 manages information on queues / topics that serve as a path through which messages are relayed.

The queue / topic management module 420 processes a queue / topic creation or deletion request of the client subsystems 100a and 100b transmitted from the web application subsystem 100, and stores the queue / topic related information in a database ( 500).

6 is a flowchart illustrating a simple object access protocol message exchange method using a Java message service according to the present invention. Here, the client subsystems 100a and 100b exchanging JMS messages may be subscribed through an appropriate authentication process to request creation and deletion of queues / topics, and to transmit and receive messages.

First, the client subsystem 100a requests the queue / topic creation to the web application subsystem 200 (600).

Then, the web application subsystem 200 forwards the queue / topic creation request of the client subsystem 100a to the message management subsystem 400 (601).

Accordingly, the message management subsystem 400 creates a queue / topic of the client subsystem 100a (602).

Thereafter, the client subsystem 100a generates a JMS message by adding headers and attributes according to the JMS protocol to the SOAP message (603).

The client subsystem 100a then transmits the generated JMS message to the message relay subsystem 300 (604).

Then, the message relay subsystem 300 receives and stores the JMS message (605).

The message relay subsystem 300 then verifies 606 that the receiving client subsystem 100b has appropriate access rights to the JMS message.

The message relay subsystem 300 then sends (607) the JMS message to the receiving client subsystem 100b.

Accordingly, the receiving client subsystem 100b performs the operation after receiving and decrypting the JMS message (608).

7 is a diagram illustrating an embodiment of a message generation process in a client subsystem according to the present invention. Hereinafter, the JMS message generating process in step 603 will be described in detail with reference to FIG. 7.

First, the client subsystem 100a encodes a document or data to be transmitted to the counterpart client subsystem 100b into an XML format based on Base64 (Base64, hereinafter referred to as Base64) (700). . Here, the base64-based encoding process can convert binary data, rather than a document, into text. In addition, the document or data may be encrypted for security.

Thereafter, a SOAP header is added to the XML document to generate a SOAP message (701).

The JMS message is then added to the SOAP message to generate a JMS message (702).

8 is an exemplary diagram of a message structure generated by a client subsystem according to the present invention.

As shown in FIG. 8, the JMS message generated by the client subsystem according to the present invention is structured into three parts: a header, an attribute, and a body.

The property provides information on the type of message so that an application can perform the task. For example, the client sub-system 100b of the counterpart receiving the message through a property called processType determines the type of the message (text, executable program, image, sound, etc.) and performs the corresponding task.

This text provides a SOAP message encapsulated in the form of a TextMessage according to the JMS protocol. The SOAP message includes a SOAP header and a SOAP body, which contains substantial data, that is, a document or data in XML format.

As described above, the method of the present invention may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a computer-readable form. 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, by exchanging the XML document or data encapsulated in SOAP by the JMS transmission method, there is an effect that can be asynchronous stable exchange of information.

Claims (9)

In a simple object access protocol (SOAP) message exchange system using a Java message service (JMS), Web application means for receiving a subscription request and a queue / topic creation and deletion request from a plurality of clients; Message relay means for transmitting a JMS message received from one client, the header and attributes according to the JMS protocol in the SOAP message to the other client; Message management means for receiving and processing queue / topic creation and deletion requests of the plurality of clients from the web application means, and recording and managing information of JMS messages transmitted from the message relay means; And Storage means for storing the relevant information of the JMS message required by each component Simple object access protocol message exchange system using a Java message service including. The method of claim 1, The message relay means, Message transmitting means for transmitting a JMS message, which has received a header and an attribute according to a JMS protocol to a SOAP message received from the client of one side, to the client of the other side, and storing a delivery event thereof; Access management means for controlling access by checking from the message management means whether the client on one side and the client on the other side have appropriate access rights; Simple object access protocol message exchange system using a Java message service including. The method according to claim 1 or 2, The client, After generating an Extensible Markup Language (XML) document for a document or data and encapsulating it in SOAP to generate a SOAP message, adding a header and an attribute according to the JMS protocol to the SOAP message to generate a JMS message. Message generating means for; Data conversion means for providing data conversion data for generating a JMS message in said message generating means; Message transmitting and receiving means for transmitting the JMS message generated by the message generating means to the message relaying means or receiving a JMS message of the other client from the message relaying means; And Interpreting means for decrypting the JMS message received by the message transmitting and receiving means to perform a corresponding operation Simple object access protocol message exchange system using a Java message service including. The method according to claim 1 or 2, The web application means, Web user means for receiving a request for membership registration and creation and deletion of queues / topics of the plurality of clients, and storing corresponding queue / topic details; A web manager for subscribing the plurality of clients to store the information of the corresponding members, forwarding the queue / topic creation and deletion requests of the plurality of clients to the message management means, and storing the queue / topic details thereof. Way; And Member authentication means for authenticating the member applying for membership Simple object access protocol message exchange system using a Java message service including. The method according to claim 1 or 2, The message management means, Client management means for providing information on access rights of the client of one side and the client of the other side according to a request of the message relay means; Queue / topic management means for processing the queue / topic creation and deletion requests of the plurality of clients to notify the web application means of the result thereof and to store the queue / topic related information. Simple object access protocol message exchange system using a Java message service including. In the Simple Object Access Protocol (SOAP) message exchange method using Java Message Service (JMS), A first step of requesting creation of a queue / topic from a client of one side; A second step of creating a queue / topic requested from the client of one side; A third step of receiving and storing a JMS message including a header and an attribute according to a JMS protocol in a SOAP message from the client of one side; A fourth step of confirming whether the client of the other side has the appropriate access right to the JMS message; And A fifth step of transmitting the JMS message to the client of the other side Simple object access protocol message exchange method using a Java message service comprising a. The method of claim 6, The client on the one side, After converting a document or data, etc. into an Extensible Markup Language (XML) format and converting it into an XML document, a SOAP message is generated by adding a SOAP header to the XML document, and then a JMS header to the SOAP message. Simple object access protocol message exchange method using a Java message service, characterized in that for generating a JMS message by adding an attribute. The method of claim 7, wherein The other client, Simple object access protocol message exchange method using a Java message service, characterized in that to check the properties of the transmitted JMS message to perform a corresponding operation. In a message exchange system having a processor, A first function of requesting creation of a queue / topic from a client of one side; A second function of generating a queue / topic requested from the client of one side; A third function of receiving and storing a JMS message added with a header and an attribute according to a JMS protocol to a SOAP message from the client of one side; A fourth function of confirming that the client of the other side has the appropriate access right to the JMS message; And A fifth function of sending the JMS message to the client of the other side A computer-readable recording medium having recorded thereon a program for realizing this.