KR20130091052A - Method for supporting service oriented architecture based web services in legacy system - Google Patents

Abstract

The present invention relates to a method of applying an SOA-based web service to a legacy system. The present invention provides a method of opening legacy programs and functions of existing closed legacy systems and sharing them in a standardized form. By providing a way to interoperate the services of legacy systems with other legacy systems, as well as with SOA-based applications that provide a standardized interface, the existing legacy systems can be reusable. It is.

Description

How to apply service-oriented architecture based web services to legacy systems {Method for supporting Service Oriented Architecture based web services in legacy system}

The present invention relates to a method of applying a web service to an existing legacy system using an SOA-based web service, and more specifically, a legacy service (software developed in dependence on a programming language, platform, and technology developed from the past). By describing how to apply SOA-based web services, a standard interface to legacy systems, to other legacy systems, using mutual services through standard interfaces that are open to other legacy systems as well as SOA-based applications. It relates to how to interlock.

In general, legacy systems could only run on the platform on which they were developed. However, companies with legacy systems are now trying to increase the value of reuse by converting business value from legacy systems into standardized services as well as from legacy environments. However, modifying an existing legacy environment introduces many problems, including development costs, administrative costs, and replacement costs. Therefore, many companies are now adopting a service-oriented architecture (SOA) to minimize the modification of existing legacy systems and to solve the problems caused by the transformation of existing legacy environments.

 Web services technology allows companies to freely use remote service objects or APIs by sending and receiving messages in a simple object access protocol (SOAP) in mutually understandable formats for interoperability between different applications built on heterogeneous platforms. Started at the request of. SOAP is transmitted over HTTP as a protocol that can access distributed objects without depending on the specific distributed technology or platform.

All data in a web service is represented in XML, and when the data and the operations that can handle it are defined in Web Service Description Language (WSDL), they are registered in a global service repository called Universal Description Discovery Integration (UDDI) and anyone can It is open to the public to find. When a published web service is used, the service is invoked using SOAP between the service requester and the service provider and the result is returned.

Not applicable

Not applicable

The technical problem of the present invention is to open legacy programs and functions of legacy systems and share them in a standardized form so that the services of legacy systems can interoperate with other SOA-based applications as well as other legacy systems. To provide a way.

The technical objects of the present invention are not limited to the technical matters mentioned above, and other technical subjects not mentioned can be clearly understood by those skilled in the art from the following description.

In order to achieve the above object, the components included in the technical content of the present invention is a web service provider for providing a standardized interface SOA-based web service, and converts the web service request information received from the web service to the legacy system The legacy system connection unit for delivering, the legacy system management unit for generating the legacy system connection unit.

As described above, the method of the present invention has the following effects.

Legacy systems operating on heterogeneous platforms can be easily converted to standard service-oriented architecture services, and the services can be used to maximize the reusability of services by sharing the services of legacy systems regardless of platform. .

.

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

1 is an exemplary diagram for understanding a web service system in a service-oriented architecture environment to which the present invention is applied.

In general, to use a web service, a series of processes are as follows.

1. The web service provider 101 creates a service, defines it as a WSDL, and publishes it to a web service directory called UDDI 102.

2. The web service requester 103 queries the web service with UDDI 102 to receive a response including the WSDL descriptor of the requested service.

3. The web service requester 103 uses the information of the WSDL descriptor to construct a SOAP message to invoke the desired web service.

2 is an exemplary configuration diagram of legacy systems 203 to which web services 204 are applied in a service-oriented architecture environment to which the present invention is applied.

The SOA Infrastructure 201 refers to an SOA infrastructure that provides a web service based on a service-oriented architecture.

The web service provisioning implementation 202, which provides the web service 204 in the legacy system 203, exposes the functions of the legacy system 203 as the web service 204, so that the SOA-based applications 205 or other legacy system. It provides a public interface function that can interoperate between the (203). Here, the legacy API 206 is a legacy system 203 dependent interface supporting the functions published by the legacy system 203 as a web service 204, and is an API of heterogeneous communication middleware or a heterogeneous programming language (C / C ++ / C #). It refers to a programming level interface supported by the legacy legacy system 203, such as dynamic and static libraries and applications implemented in / Java.

The term '~' used in this embodiment refers to a software component, and '~' plays a role. The functionality provided within the components 'parts' may be further separated into smaller number of components ('parts').

3 is a functional block diagram of the web service providing implementation unit 202 of the legacy system 203 to which the present invention is applied.

As shown, the web service providing implementation unit 202 may transmit the service request information received from the web service providing unit 301 and the web service 204 to provide the web service 204 which is a standardized interface. To the legacy API 206 by calling the legacy API 206 and receiving the asynchronous information generated from the legacy system 203 through the legacy API 206 to receive the asynchronous information. Legacy system connection unit 303 to search and deliver to the recipient identified in (304), the legacy system connection unit 303, the legacy system management unit for generating and storing unique identifier information for the web service requester (103) ( 302).

The web service provider 301 processes the request of the web service requester 103 for the web service 204 of the legacy system 203. Here, the request processing of the web service requester 103 is transmitted to the legacy system manager 302 or the legacy system connector 303 by interpreting the web service 204 name and parameter information.

Here, the web service provider 301 stores and manages communication information that can communicate with the legacy system manager 302 and the legacy system connector 303 in the communication information store 305. The communication information of the legacy system management unit 302 is stored and managed at the time of initialization, and the communication information of the legacy system connection unit 303 is set by the legacy system management unit 302 when the initialization registration request service of the web service requester 103 is called. The communication information of the given legacy system connection unit 303 is received as a result and stored and managed in the communication information store 305.

First, the case in which the request information is transmitted to the legacy system manager 302 is when the web service requester 103 calls a registration request service for interworking using the web service 204. The parameter transmitted at this time is the domain information of the web service provider 101 that provides the web service 204 for the web service requester 103 to receive asynchronous information from the legacy system 203 in the future. This domain information is stored and managed together with the identifier information store 304 together with newly assigned identifier information to identify the web service requester 103. That is, when the registration request service is called, the legacy system manager 302 generates new identifier information based on the received domain information, and stores the new identifier information in the identifier information storage 304 together with the domain information.

When the legacy system connection unit 303 is generated by the legacy system management unit 302, the identifier information is transmitted together. To maintain for use as an identification value for retrieving and determining from information repository 304.

Next, when the request information is transmitted to the legacy system connection unit 303, when all other request services except for the registration request service are called, the communication information is retrieved from the communication information store 305 using the received identifier parameter information. Will be delivered.

The legacy system connection unit 303 is generated by the legacy system management unit 302, and the legacy API 206 of the legacy system 203 to receive and communicate with the request of the web service requester 103 from the web service provider 301. It is responsible for calling).

Referring to the legacy system connection unit 303 in more detail, it is responsible for calling the individual legacy API 206 by interpreting the request information of the web service requester 103 received from the web service provider 301, the legacy API (206) It is responsible for delivering the result to the web service provider 301 to deliver the call result back to the web service requester (103). In this case, the result information delivered to the web service requester 103 may be in the form of a return value of the requested web service 204, and the return value may be a primitive type such as boolean, integer, or the like. Can be of the same data container type. In addition, the legacy system connection unit 303 is responsible for receiving asynchronous information generated from the legacy system 203 and using the domain information corresponding to the identifier information to deliver it to the web service provider 101 which is the receiver.

4 is a flowchart illustrating a process of calling a web service requester 103 to request a web service 204 for using a web service to interoperate with the legacy system 203 according to an embodiment of the present invention.

First, when the registration request web service 204 by the web service requester 103 is called, the web service provider 301 sends the domain information of the web service requester 103 received as a parameter when the service is called. Forward to 302 (401).

Next, the web service manager 302 searches whether the received domain information exists in the identifier information repository 304 currently managed. If present, the identifier information corresponding to the domain information is retrieved (404) and delivered to the web service provider 301 for delivery to the web service requester 103, and the web service provider 301 requests for registration. The identifier information is transmitted to the web service requester 103 as a result of the web service.

If the domain information does not exist, the identifier information corresponding to the domain information of the web service requester 103 is generated and the identifier information is stored in the identifier information store 304.

The domain information is stored and managed together (403).

Next, a legacy system connection unit 303 is generated (405) in charge of processing all web services 204 from the web service requester 103 including valid ring identifier information. In this case, when the legacy system manager 302 generates the legacy system connector 303, the legacy system manager 302 transfers newly generated identifier information together.

The legacy system manager 302 then transfers the generated communication information of the legacy system connector 303 to the web service provider 301. This is for future use by the web service provider 301 as information for communicating with the legacy system connection unit 303 for processing of the web service of the web service requester 103. The web service provider 301 receiving the communication information is stored and managed in the communication information store 305 together with the identifier information (406). The communication information may be a general communication protocol address or port number such as TCP / IP or UDP / IP.

Next, the web service provider 301 delivers the processing result (eg, identifier information and success / failure status, etc.) of the registration request web service to the web service requester 103.

5 is a flowchart illustrating a process in which the web service requester 103 calls the provision web service 204 of the legacy system 203 to interoperate with the legacy system 203 according to an embodiment of the present invention.

First, when the web service provider 301 calls the web service 204 of the legacy system 203 by the web service requester 103 (501), the web service requester 103 among the parameters received at the time of the service call. Retrieve the identifier information of the communication information storage 305 currently managed. If there is no communication information for the identifier information as a result of the search, the result is transmitted to the web service requester 103 including the identifier information error (504 and 506).

In the case of the existing communication information, the parameter information of the received web service 204 is transferred to the corresponding legacy system connection unit 303 using the communication information so that the parameter information of the received web service 204 may be transferred to the legacy system 203 (503).

Then, the legacy system connection unit 303 calls the legacy API 206 of the legacy system 203 corresponding to the web service 204 request, and receives the processing result of the request from the legacy system 203 again to receive the web. The web service provider 301 delivers the result of the request web service 204 to the web service requester 103 so that it can be delivered to the service requester 103.

6 is a flowchart illustrating a process for receiving asynchronous information from the legacy system 203 according to an embodiment of the present invention.

First, when the legacy system connection unit 303 receives 601 asynchronous information from the legacy system 203, the legacy system connection unit 303 extracts 602 asynchronous information, which is parameter information to be delivered together with the web service. Then, the web service provider 101 that receives the asynchronous information of the legacy system 203 is searched and determined in the identifier information store as the identifier information (603), and the web service 204 that receives the asynchronous information of the corresponding receiver is determined. Call and pass (604).

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not intended to limit the invention to the particular forms disclosed. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

.

Claims (2)

Identifier information store and legacy that provide SOA-based web service corresponding to legacy service of legacy system, store domain information for web service provider for generating identifier when requesting web service and delivering asynchronous information from legacy system. A web service providing unit including communication information with a system manager and a connection unit;
A legacy system manager configured to generate a legacy system connection unit under control of the web service provider;
The legacy system comprising a legacy system connection unit for transmitting the request to the web service provider to the legacy system using the legacy API, and receives asynchronous data from the legacy system through the legacy API to deliver to the web service provider. How to apply SOA-based web services. The method of claim 1,
The web service provider uses an SOA-based web service to uniquely manage a web service requester who wants to interoperate with a legacy system, and provides domain information of a web service provider corresponding to the identifier to transfer asynchronous data of the legacy system. How to manage storage together.

Images