KR100629018B1 - The legacy interface system and operating method for enterprise wireless application service - Google Patents

Abstract

The present invention relates to a legacy interface (Legacy I / F) system and operation method of the enterprise wireless application service for the integrated operation of the mobile service of the enterprise having a variety of content. In particular, it relates to technologies that integrate applications to share applications regardless of back-end software such as network protocols, databases, and operating systems.

According to the present invention, in a legacy I / F system of an enterprise wireless application service interworking with an internal and external system of an enterprise and an internet network, the legacy interface system includes a transmission and reception of data with an internal and external system of an enterprise, An interface engine for managing data conversion and process; An adapter developer for providing a tool function for developing an adapter for linking the interface engine with another system; And it provides a legacy interface system of the enterprise wireless application service including an Interface Admin (Interface Admin) that provides a tool function for managing and monitoring the execution status of the interface engine.

Line of Business Platform, Wireless, Applications, Legacy Interfaces (Legacy I / F)

Description

The legacy interface system and operating method for enterprise wireless application service

1 is an overall configuration diagram of a legacy interface (Legacy I / F) system according to the present invention.

FIG. 2 is a conceptual diagram of a built-in component pack package provided in the interface engine IE illustrated in FIG. 1.

3 is a flowchart illustrating a processing process of a request processor of a legacy I / F system according to the present invention.

4 is a flowchart illustrating a process of a response processor of a legacy I / F system according to the present invention.

The present invention relates to a legacy interface (Legacy I / F) system and operation method of the enterprise wireless application service for the integrated operation of the mobile service of the enterprise having a variety of content. More specifically, it's a technology that integrates applications to share applications regardless of back-end software, such as enterprise network protocols, databases, or operating systems.

The enterprise wireless application service is a service that can be delivered through various terminals by implementing a mobile task desired by a customer by interworking with a main system of various client companies.

In particular, the conventional wireless application service has reached the limit of business for the following reasons.

First, the focus was on providing mobile enable solutions for enterprise applications, not the entire application.

Second, there were many demands for the introduction of solutions based on important business partnerships for the formation of an Application Service Provider (ASP).

Third, coexistence of various kinds of package solutions and SI applications was required.

Fourth, for the security of corporate customers, various operating environments were required in which the physical location of the service system could be inside the customer company.

Therefore, in order to overcome the limitations of such a business, 1) it is possible to respond to the customer's service needs at a rapid and low cost, 2) to expand the service offerings of new and existing customers through the integration of services, and 3) to provide flexibility. As a result, the development of new types of business models that could absorb business partners with new models was required.

As a related art, patent application 10-2002-0061037 (corporate application integration solution as a web service integration platform applying web synergy, messaging middleware and web service standard technology), and patent application 10-2000-0083305 (xm system and non -Adapter device for data transmission between XML systems and data transmission method using the same, Patent application 10-2002-0014151 (wireless application service provider system), Patent application 10-2001-0019964 (components based on automata theory Wired and wireless Internet integrated operation management system and its method) and the like are known.

However, such known conventional technologies are an Internet integrated platform service (patent application 10-2002-0061037) for providing an Internet service in an integrated format, and a service for converting non-XML data into XML (patent application 10-2000). -0083305), a service that enables the dynamic user screen composition and relocation by the administrator (Patent Application 10-2002-0014151), and the contents of the wired Internet site can be applied to the construction of the wireless Internet site to manage the integrated operation The service (patent application 10-2001-0019964) can be usefully provided to the customer, but it could not satisfy the requirements of various customers with minimal cost and time while reflecting the characteristics of the wireless application business.

In addition, in the interface processing method of the wireless application service, a problem arises in that the application cannot be stably shared with an external system having back-end software such as a network protocol, a database, and an operating system of an enterprise.

An object of the present invention is to provide a legacy interface system and a method of operating an enterprise wireless application service for integrating and operating a mobile service of an enterprise having various contents.

In particular, the present invention integrates to enable application sharing regardless of back-end software such as enterprise network protocols, databases, or operating systems. Provides services such as message-oriented middleware, data conversion, routing, and business process automation. Its technical characteristics are to enable stable message exchange with multiple external systems without adding / changing internal systems.

As the technical idea for achieving the above object of the present invention

In the legacy I / F system of the enterprise wireless application service interoperating with the internal and external systems of the enterprise and the Internet network,

The legacy interface system

An interface engine for managing data transmission and reception, data conversion, and process with an internal and external system of an enterprise;

An adapter developer for providing a tool function for developing an adapter for linking the interface engine with another system; And

It provides a legacy interface system of the enterprise wireless application service including an interface admin (Interface Admin) that provides a tool function for managing and monitoring the execution status of the interface engine.

In addition, the present invention is a method for processing the request and response process of the legacy interface (Legacy I / F) for the enterprise wireless application service,                         

A first step of requesting a management screen for authentication information from a Biz Common Platform Manager to a legacy interface (Legacy I / F);

A second step of receiving authentication information from an interface admin and requesting authentication to an interface engine;

A third step of generating a management screen of a legacy interface after processing an authentication in an interface engine;

And a fourth step of transmitting a management screen of the legacy I / F to a BCP manager.

Hereinafter, with reference to the accompanying drawings, the configuration and operation of the embodiment of the present invention will be described in detail.

1 is an overall configuration diagram of a legacy interface (Legacy I / F) system according to the present invention.

The legacy interface system according to the present invention is interworked with the internal system of the enterprise and the internet network 300, and its configuration is largely composed of the interface administration (IA) 100 and the adapter developer (Adapter Developer). : AD) 200 and an Interface Engine (IE) 300.

The interface admin (IA) 100 is interworked with a Biz Logic Builder (BLB) 110 of a system input.

The interface engine (IE) 300 is interworked with a Biz Logic Processor (BLP) 210 of a system input, and a database / file 310 of a system output. ), The middleware 320 and the application 330 are linked. In addition, there is a built-in Component Pack that provides a set of reusable basic components for the adapter configuration.

Looking at the operation of each component, the Interface Admin (100) (100) is responsible for managing the legacy interface server (Legacy I / F Server). It uses a web browser to log and error legacy interfaces (I / F), check system status, authenticate users, and manage legacy system connections.

Adapter Developer 200 is a tool for developing adapters and components using a graphical user interface (GUI). It uses the HTTP / SOAP protocol to access legacy I / F and develop service components to link with legacy systems.

The interface engine 300 includes various built-in components and a cooperative adapter for interworking with a legacy system. This is handled by the message broker upon request of the Biz Logic Processor 210 by calling built-in components and associated adapters through the process flow.

The Biz Logic Builder 110 retrieves the service component information to refer to the service component provided by the legacy I / F. That is, the service component information provided by the legacy interface (Legacy I / F) is retrieved using the HTTP protocol through a web browser embedded in the Biz Logic Builder 110.

The Biz Logic Processor 210 calls a service component provided by the legacy I / F using the HTTP / SOAP protocol. That is, the service component application interface (API) is called by using the client library provided by the legacy interface (Legacy I / F).
BLP (Biz Logic Processor) is a well-known term for a functional module that interprets various business requests of many users into pre-implemented (programmed) Biz Logic and processes them sequentially.
In the present invention, the BLP (BizLogic Processor) is a function of interpreting a legacy interface as a pre-implemented (programmed) BizLogic among various business requests of many users as described in FIGS. 1, 3, and 4 and sequentially processing them. It means a module.

At this time, the legacy interface (Legacy I / F) supports more than about 200 built-in components and association patterns for linking with a number of legacy systems (Legacy System). Each built-in component is well-divided into various communication protocols and categories by JDBC, middleware, etc. according to the legacy system type, and it is easily and quickly linked with any legacy system by providing flow components by linking pattern. Do it.

FIG. 2 is a conceptual diagram of a built-in component pack package provided in the interface engine IE illustrated in FIG. 1.

As shown in FIG. 2, the interface engine IE basically provides a built-in component package for linking with a legacy system.

The built-in component package is a collection of various types of components that can be used to implement various functions such as components, adapters, processes, etc. in order to extend and change the system and to connect with other systems later. By eliminating the wasteful elements used to develop new methods, it has the effect of increasing the stability and efficiency in the development of integrated systems. It also supports connectivity to various standard technologies.

3 is a flowchart illustrating a processing process of a request processor of a legacy I / F system according to the present invention.

1) Request management screen from legacy Biz Common Platform Manager to Legacy I / F. At this time, information such as authentication information and language mode is transmitted.

Then, the Interface Admin 100 receives the authentication information and requests authentication to the Interface Engine 300. (A-②)

The interface engine 300 then handles authentication. (C-③)

2) BizLogic Builder 110 requests the service component information from the legacy interface (Legacy I / F). At this time, the authentication information is transmitted. (B-①)

Then, the interface admin 100 receives the authentication information and requests authentication to the interface engine 300. (A-②)

3) The BizLogic Processor 210 requests an application interface (API) linked with a legacy system through a legacy interface (C-①).

The interface engine 300 then executes an internal service component. At this time, a built-in component and an association pattern built in the interface engine 300 are called and processed. (C-②)

Then, the data request message is sent to the legacy system (C-③).

4) The adapter developer 200 makes an export request for a package through a legacy I / F. At this time, the authentication information is transmitted to the adapter developer 200. (D-1).

Then, the Interface Engine 300 executes the export for the requested package. (C-②)

4 is a flowchart illustrating a process of a response processor of a legacy I / F system according to the present invention.

1) The Biz Common Platform Manager generates a legacy I / F management screen after processing the authentication in the Interface Engine 300. (C-⑥)

The legacy I / F management screen is then sent to the BCP Manager. (A-③)

 2) The BizLogic Builder 110 processes the authentication in the Interface Engine 300 and generates information about the component. (C-⑤)

Then, the service component list of the legacy interface (Legacy I / F) is transmitted to the BizLogic Builder 110 (B-②).

3) The BizLogic Processor 210 receives data requested from a Legacy System in the Interface Engine (C-④).

Then, the interface engine 300 performs a process such as data format change through the built-in built-in component. (C-⑤)

Then, the requested result is transmitted to the BizLogic Processor 210 (C-7).

4) In the adapter developer 200, the interface engine 300 transmits the exported result of the requested package to the adapter developer 200. (D-②)

Then, the adapter developer 200 executes the source manager and transmits the exported result to the source management server. (D-③)

As described above, according to the legacy interface system and operation method of the enterprise wireless application service according to the present invention, it integrates so that applications can be shared regardless of back-end software such as a network protocol, a database, and an operating system of an enterprise. Providing services such as message-oriented middleware, data conversion, routing, and business process automation, it is possible to provide stable service by performing stable message exchange with multiple external systems without adding / changing internal systems.                     

Therefore, it is possible to maximize user convenience in the interface processing method of the wireless application service.

Claims (8)

In the legacy I / F system of the enterprise wireless application service interoperating with the internal and external systems of the enterprise and the Internet network, The legacy interface system An interface engine for managing data transmission and reception, data conversion, and process with an internal and external system of an enterprise; An adapter developer for providing a tool function for developing an adapter for linking the interface engine with another system; And Legacy interface system of the enterprise wireless application service including an interface admin (Interface Admin) that provides a tool function for managing and monitoring the execution status of the interface engine. The legacy system of claim 1, wherein the interface administrator IA is connected to a Biz Logic Builder of a system input and is connected to a legacy interface using an HTTP protocol through a web browser embedded in the BizLogic Builder. Legacy interface system of enterprise wireless application services, characterized in that the service component information provided by the F) can be retrieved The service component of claim 1, wherein the interface engine IE is interworked with a Biz Logic Processor of a system input and is provided by a legacy I / F using an HTTP / SOAP protocol. Legacy interface system of the enterprise wireless application service, characterized in that the call. The legacy interface of claim 3, wherein the legacy interface supports a built-in component and an association pattern for interfacing with a plurality of legacy systems, and the built-in component supports communication protocols, JDBC, and middleware according to types of legacy systems. Legacy interface system of the enterprise wireless application service, characterized in that it is well supported by each category, and provide a flow component according to the association pattern. In the method of processing the request and response process of the legacy interface (Legacy I / F) for the enterprise wireless application service, A first step of requesting a management screen for authentication information from a Biz Common Platform Manager to a legacy interface (Legacy I / F); A second step of receiving authentication information from an interface admin and requesting authentication to an interface engine; A third step of generating a management screen of a legacy interface after processing an authentication in an interface engine; And transmitting a management screen of the legacy interface (Legacy I / F) to a BCP manager. The method of claim 5, wherein the service component information is provided when requesting authentication information from the BizLogic Builder to the legacy interface (Legacy I / F) instead of the platform manager for the main business of the first step. How to operate legacy interface of enterprise wireless application service. The application interface of claim 5, wherein the authentication information is requested from the BizLogic Processor instead of the business platform manager of the first step by using the legacy I / F from the BizLogic Processor. A method of operating a legacy interface of an enterprise wireless application service, characterized by providing information (API). The method according to claim 5 or 6, wherein if the provided authentication information is service component information, an authentication is performed by executing a built-in component built in an interface engine and processing data format change. How to operate legacy interface of wireless application service.

Images