KR20020028951A - Link of web application server for correlation with legacy system in internet - Google Patents

Abstract

PURPOSE: A method for making a web application server link to a legacy system is provided to smoothly convert data of a database, a TP-monitor or a middle ware, constructed in advance under a 3 Tier environment, into web data without additional coding work. CONSTITUTION: The method comprises steps of an EFCL(External Function Call Language) analysis module receiving and storing an EFCL developed by a researcher, analyzing the EFCL, and transmitting the analysis result to a data converter(S102, S103), the data converter receiving the EFCL data from the EFCL analysis module, receiving the input data demanded from a client computer, converting the transmitted data into data in a data type of a legacy system, and then transmitting the converted data to a function call and result receiving module(S105), the function call and result receiving module receiving the data of the legacy system from the data converter, calling the legacy system, receiving the data resulted from a data processing in the legacy, and transmitting the data to an output data converter(S107, S109), and the output data converter receiving the EFCL data from the data converter, receiving the result data of the legacy system from the function call and result receiving module, and converting the transmitted data into the output data(S111).

Description

Link of web application server and its operation method for interworking with legacy system in internet environment {Link of web application server for correlation with legacy system in internet}

The present invention relates to a link of a web application server (Web Application Server) for building a web foundation of a company, and more particularly, a system that is built without additional coding in a three-tier environment (ex. For example, the web seamlessly without changing the information of the legacy system, database, TP-Monitor, SAP / R3, and middleware (Tuxedo, Entera). The present invention relates to a web application server link and its operation method for interworking with a legacy system in an Internet environment.

Recently, with the development of information and communication technology, the explosive spread of global communication infrastructure such as the Internet is emerging as a new mode of economic activity overcoming time and space constraints. These definitions of e-commerce can vary from many perspectives, but include all commercial activities for buying and selling commodity services in cyberspace such as the Internet and supporting activities among economic entities such as individuals, companies, and governments. The acts of

In particular, the subject of electronic commerce traded through an internet web application server is not only physical goods requiring courier services such as books, furniture, and clothing, but also computer software, printed matter, entertainment, information services, professional consulting, financial services, and education. , Digital goods and services that can be transmitted, such as advertising.

1 is a block diagram showing the interworking between a web application server and a legacy system in a general Internet environment.

As shown in FIG. 1, a client computer 10 requesting a service through all kinds of web browsers used according to a client's request, and HTML generated according to a request signal output from the client computer 10 ( Provides a web application server 20 that transmits hypertext markup language to the client computer 10 and middleware information (Tuxedo, Entera, etc.) implemented by the web application server 20. It is composed of a legacy system (Legacy system) (30).

Here, the web application server 20 may include a data store 20-1 storing data and a data object model generator 20- generating a data object model from data output from the data store 20-1. 3), an HTML generator 20-5 for generating HTML from the data object model output from the data object model generator 20-3, and a tuxedo, entera, etc. built in the legacy system 30; It is composed of a coding unit (20-7) for individually coding the program according to the language of the web application server (20).

On the other hand, the tuxedo of the middleware information to be built in the legacy system 30 is a tip-monitor product supplied by BEA Systems in California, USA, a program running on various types of UNIX-based computer, the enter is supplied by Borland It is a tip-monitor product that functions like a tuxedo.

In addition, the middleware refers to a program that acts as a mediator or associates between two separate programs in the computer field, such as "glue".

In particular, the representative function of the middleware is a program written to access a specific database.

The operation of the web application server in the general Internet environment configured as described above with reference to the configuration diagram showing the interworking of the legacy system is described as follows.

First, the client computer 10 requests a service to all kinds of web application servers 20 used according to a client's request.

The web application server 20 is a middleware that is a middle layer providing a management function for a user program. The web application server 20 provides a platform for an application having a management function for a user application, and provides a middleware product for an application in a web environment. Can be defined.

In addition, the web application server 20 mainly supports a function as a development tool that supports application development in a system backend more quickly and easily, system security and stability, and a faster speed function of the web.

On the other hand, the coding unit 20-7 of the web application server 20 individually codes the middleware information (tuxedo, entera, etc.) pre-built in the legacy system 30 according to the web application server 20.

The web application server 20 directly accesses the data storage 20-1, collects data, generates an object model on the server, and transmits the processed HTML to the client computer 10.

The operation of the web application server will be described in more detail as follows.

The object model generator 20-3 of the web application server 20 generates an object model from data transmitted from the data storage 20-1, and then converts the generated object model into an HTML generator 20-5. To send).

The HTML generator 20-5 processes the object model received from the data object model generator 20-3 and transmits the processed HTML to the client computer 10.

However, when the existing legacy system is to be converted into the web, the coding unit of the web application server has to individually code information (tuxedo, entera) of the middleware of the legacy system.

Therefore, there has been a problem that many companies have difficulty in switching from the existing legacy system to the web due to the coding.

Accordingly, the present invention has been proposed to solve the above-described problems according to the prior art, and an object of the present invention is to provide a database, a tip-monitor of a system that is configured without additional coding in a 3-tier environment. It provides a link and operation method of a web application server for interworking with a legacy system in an internet environment that enables a smooth transition to the web without changing the information of the SAP, R3 and middleware.

Features of the link of the web application server for interworking with the legacy system in the Internet environment according to the present invention for achieving the above object,

In the link of the web application server that converts the legacy system to the web,

The link,

An EFCL analyzer for storing the EFCL written by the developer and analyzing the stored EFCL;

A data converter which receives EFCL information transmitted from the EFCL analyzer and input data required by a client computer, and converts the received information into a variable type and size of a legacy system;

A function call and a result receiving unit for calling the legacy system using the variable type and size of the legacy system converted and transmitted from the data converting unit and receiving the result data from the legacy system;

And an output data conversion unit for receiving the EFCL information transmitted from the data conversion unit and the result data of the legacy system transmitted from the function call and result reception unit, converting the received information into output data, and transmitting the result data to the data store.

In addition, a feature of the link operation method of the web application server for interworking with the legacy system in the Internet environment according to the present invention for achieving the above object,

Receiving and storing the EFCL prepared by the developer in the EFCL analyzer, analyzing the stored EFCL, and transmitting the analyzed EFCL to a data converter;

Receiving, by the data converter, EFCL information transmitted from the EFCL analyzer and input data required from a client computer, converting the received information into a data format of a legacy system, and transmitting the data to a function call and a result receiver;

The function call and result receiving unit receives data information of the legacy system transmitted from the data conversion unit, calls the legacy system, receives the result from the legacy system, and transmits the result of the received legacy system to the output data conversion unit. Steps;

Receiving the EFCL information transmitted from the data conversion unit and the result data of the legacy system transmitted from the function call and result receiving unit, converting the received information into output data, and transmitting the EFCL information transmitted from the data conversion unit to the data storage; It is made to include.

1 is a block diagram showing the interworking between a web application server and a legacy system in a general Internet environment,

2 is a block diagram showing a link and its surroundings of a web application server according to the present invention;

3 is a flowchart illustrating the operation of a link of a web application server according to the present invention;

4 is a flowchart illustrating an operation of an EFCL analyzer in the method of operating a link of FIG. 3;

5 is a flowchart illustrating an operation of a data conversion unit in an operation method of a link of FIG. 3;

FIG. 6 is a flowchart illustrating an operation of an output data converter of an operation method of a link of FIG. 3.

<Explanation of symbols for the main parts of the drawings>

100: client computer

200: web application server

210: data storage

220: data object model generation unit

300: Legacy System

Hereinafter, a preferred embodiment of a link of a web application server for interworking with a legacy system in an internet environment and an operation method thereof according to the present invention will be described with reference to the accompanying drawings.

2 is a block diagram showing a link and its surroundings of a web application server according to the present invention.

As shown in FIG. 2, the client computer 100 requesting a service through all kinds of web browsers used according to the client's request, and the HTML generated according to the request signal output from the client computer 100 ( Provides a web application server 200 for transmitting hypertext markup language to the client computer 100 and middleware information (Tuxedo, Entera, etc.) implemented by the web application server 200. It is composed of a mechanism axis (Legacy system) (300).

The web application server 200 may include a data storage 210 for storing data, a data object model generator 220 for generating a data object model from data output from the data storage 210, and the data. EFCL stored by the developer when calling a program such as a tuxedo, entera, etc. built in the legacy system 300 and the HTML generation unit 230 for generating HTML from the data object model output from the object model generation unit 220 A link for transmitting data to the data storage 210 by calling middleware of the legacy system according to a variable of (External Function Call Language: variable information on middleware (tuxedo, entera, etc.) information of the legacy system). TOInB Linker) 240.

In particular, the EFCL is composed of function information, input data information, and output data information.

The function information refers to information for calling a function of a legacy system, and information required for calling one function is different for each legacy system. For example, a tuxedo requires a service name to call, information about the buffer type used by the service, and a connect mode.

The input / output data information refers to mapping information for data input or output data by a function. In addition, the structure of the input / output data information is different for each legacy system, and describes information on the variable type, size, etc. of the legacy system.

Looking at the configuration of the link in detail as follows.

The link 240 stores an EFCL written by a developer and analyzes the stored EFCL, and the EFCL information and the client computer 100 transmitted from the EFCL analysis unit 240-1. A data conversion unit 240-3 for receiving input data required from the data source and converting the received information into a variable type and size of the legacy system 300, and converted and transmitted from the data conversion unit 240-3. Function call and result receiver 240-5 for calling the legacy system 300 using the variable type and size of the legacy system 300 and receiving the result data from the legacy system 300, and the data conversion. The EFCL information transmitted from the unit 240-3 and the result data of the legacy system 300 transmitted from the function call and result receiver 240-5 are received, and the received information is converted into output data to store the data store ( Exodus sent to 210) It consists of a data conversion unit (240-7).

Referring to the link operation of the web application server configured as described above are as follows.

3 is a flowchart illustrating the operation of a link of a web application server according to the present invention.

As shown in FIG. 3, first, the EFCL analyzer 240-1 receives and stores an EFCL created by a developer, analyzes the stored EFCL, and then converts the analyzed EFCL to a data converter 240-3. Are transmitted (S101) (S103).

The data conversion unit 240-3 receives the EFCL information transmitted from the EFCL analyzer 240-1 and input data required from the client computer 100, and transmits the received information to the legacy system 300. The data is converted into the data form and transmitted to the function call and result receiver 240-5 (S105).

The function call and result receiver 240-5 receives data information of the legacy system 300 transmitted from the data converter 240-3 and calls the legacy system 300 and the legacy system 300. Receives the result from the transmission of the result of the legacy system 300 is transmitted to the output data conversion unit 240-7 (S107) (S109).

Then, the output data converter 240-7 transmits the EFCL information transmitted from the data converter 240-3 and the result data of the legacy system transmitted from the function call and result receiver 240-5. The received information is converted into output data and transmitted to the data storage 210 (S111).

4 is a flowchart illustrating an operation of an EFCL analyzer of the link operating method of FIG. 3.

As shown in FIG. 4, first, an EFCL created by a developer is received and stored, and the stored EFCL is analyzed (S201) (S203).

In operation S205, it is determined whether the information on the function, the information on the input variable, and the EFCL on the output variable are checked in the stored EFCL.

If the item of the EFCL is not checked as a result of the determination in S205, the request data is input again from the developer.

If the item of the EFCL is checked as a result of the determination in S205, the EFCL information is converted into EFCL structure information and transmitted to the data conversion unit 240-3 (S207).

5 is a flowchart illustrating an operation of a data conversion unit in a method of operating a link of FIG. 3.

As shown in FIG. 5, first, input data is received from the client computer 100 and EFCL structure information is received from the EFCL analyzer 240-1 (S301).

The information on the link input variable is read from the input EFCL structure information (S303).

Then, the actual value of the link input variable is read from the link data table, and the variable information of the legacy system 300 is read from the EFCL structure information, and the actual value of the variable type and size of the legacy system 300 is stored ( S305) (S307) (S309).

Here, the link data table refers to an area where data is stored. In addition, the link data table is a data structure having a column and a row. The structure includes a header structure, a column information structure, a column index information structure, a real data storage area, and a constant data storage area.

In particular, the structure of the link data table is as follows.

DataTable Header Column Information Data Index Data Const Information

DataTable Header Data table header structure (80 bytes) Column Information Column Information Structure (variable length) Data Index Column Index Information Structure (variable length) Data Real data storage (variable length) Const Information Const data storage (variable length)

In addition, the data table header structure is as follows.

DataTable Name Data table name (40 bytes) type Data table type (4 bytes) Cur row Current row pointer (4 bytes) update Correction (4 bytes) unpack Whether to pack (4 bytes) val alloc size Total allocated memory space (4 bytes) val use size Memory space in use (4 bytes) Row capacity row free space (4 bytes) Row count Currently stored row count (4 bytes) Col count The current number of columns (4 bytes) Const Size Const information number (4 bytes)

The column information structure is as follows.

Column name Column name (40 bytes) val pointer Data pointer (ignored during communication) (4 bytes) val Size The length of the column (4 bytes) type Column type (4 bytes) property Column attribute (4 bytes) Max Size The maximum size of the column (4 bytes) Decimal Size Decimal size (4 bytes) for Decimal type

Meanwhile, the data index structure is as follows.

Row offset Start position of row (4 bytes) Row size Row size (4 bytes)

The data structure is as follows.

Sort data Attribute value of a row (4 bytes) Column size Column length (4 bytes)

.

.

.

Val data Column data (variable bytes)

.

.

In addition, the Const information structure is as follows.

Const data Column data (variable bytes)

.

.

Therefore, the link data table is set by the developer at link creation.

Then, it is determined whether the information on the link input variable has been read (S311). When the result of the determination is that the link input variable has been read, the function call and the result receiving unit 240 determine the actual value of the variable type and size of the legacy system 300. -5).

FIG. 6 is a flowchart illustrating an operation of an output data converter of an operation method of a link of FIG. 3.

As shown in FIG. 6, first, EFCL information transmitted from the data converter 240-3 and result data of the legacy system 300 transmitted from the function call and result receiver 240-5 are received (S401). ).

Then, information about the link output variable is read from the input EFCL structure information (S403).

The data table list and output data table column information are constructed from the input EFCL structure information and stored in the memory (S405).

Thereafter, it is determined whether the information on the link output variable has been read from the EFCL structure information (S407).

When the link output variable has been read, the stored output data table list and the output data table column information are read (S409).

Then, the variable information of the legacy system 300 for the data table column of the link output variable is read, and the actual value of the legacy system 300 corresponding to the column is read (S411) (S413).

Thereafter, the actual value of the column type and size of the link data table is stored (S415).

In operation S417, it is determined whether the last output column is read from the variable information of the legacy system.

If the last output column of the link data table is read as a result of the determination in S417, the column is stored in a row of the link data table (S419).

Then, it is determined whether the output data of the legacy system 300 is the last row (S421).

If the output data of the legacy system 300 is the last row, it is determined whether the output data table is the last output data table (S423). If the output data table is the last output data table, the output data is converted to the data storage 210. send.

As described above, the present invention has the effect of improving development productivity by defining functions of the legacy legacy system by defining only the EFCL interface without additional coding.

In particular, the present invention has the effect that the modification of the business logic developed in the existing legacy system can be reused on the web.

Claims (5)

In the link of the web application server that converts the legacy system to the web, The link, An EFCL analyzer for storing the EFCL written by the developer and analyzing the stored EFCL; A data converter which receives EFCL information transmitted from the EFCL analyzer and input data required by a client computer, and converts the received information into a variable type and size of a legacy system; A function call and a result receiving unit for calling the legacy system using the variable type and size of the legacy system converted and transmitted from the data converting unit and receiving the result data from the legacy system; And an output data conversion unit for receiving the EFCL information transmitted from the data conversion unit and the result data of the legacy system transmitted from the function call and result reception unit, converting the received information into output data, and transmitting the result data to a data store. Link of web application server for interworking with legacy system in internet environment. A first step of receiving and storing an EFCL prepared by a developer in the EFCL analyzer, analyzing the stored EFCL, and then transmitting the analyzed EFCL to a data converter; A second step in which the data conversion unit receives the EFCL information transmitted from the EFCL analysis unit and the input data required from the client computer, converts the received information into a data format of a legacy system, and transmits it to a function call and a result receiver; ; The function call and result receiving unit receives data information of the legacy system transmitted from the data conversion unit, calls the legacy system, receives the result from the legacy system, and transmits the result of the received legacy system to the output data conversion unit. A third step; A fourth for receiving the EFCL information transmitted from the data conversion unit and the result data of the legacy system transmitted from the function call and the result receiving unit, converting the received information into output data, and transmitting the result data to the data store; Link operation method of the web application server for interworking with the legacy system in the Internet environment, characterized in that it comprises a step. The method of claim 2, The EFCL analysis of the first step of receiving and storing the EFCL created by the developer in the EFCL analyzer and analyzing the stored EFCL, then transmitting the analyzed EFCL to the data converter, Receiving and storing the EFCL created by the developer and analyzing the stored EFCL; Determining whether the information on the function, the information on the input variable, and the EFCL on the output variable are checked in the stored EFCL; If the item of the EFCL is not checked as a result of the determination, re-input of request data from a developer; And if the item of the EFCL is checked, converting the EFCL information into EFCL structure information and transmitting the converted information to a data conversion unit. The link of the web application server for interworking with the legacy system in the Internet environment, characterized in that the EFCL information is checked. How to operate. The method of claim 2, The data conversion unit receives the EFCL information transmitted from the EFCL analysis unit and the input data required from the client computer, converts the received information into the data format of the legacy system, and transmits it to the function call and the result receiver. Data conversion, Receiving input data from a client computer and receiving EFCL structure information from the EFCL analyzer; Reading information on a link input variable from the input EFCL structure information; Reading the actual value of the link input variable from a link data table and reading variable information of the legacy system from the EFCL structure information to store the actual value of the variable type and size of the legacy system; Determining whether the information on the link input variable has been read, and when the link input variable has been read, transmitting the actual value of the variable type and size of the legacy system to the function call and the result receiver. Link management method of web application server for interworking with legacy system in internet environment. The method of claim 2, A fourth for receiving the EFCL information transmitted from the data conversion unit and the result data of the legacy system transmitted from the function call and the result receiving unit, converting the received information into output data, and transmitting the result data to the data store; The output data conversion of the step, Receiving the EFCL information transmitted from the data converter and the result data of the legacy system transmitted from the function call and the result receiver; Reading information on a link output variable from the input EFCL structure information; Constructing a data table list and output data table column information from the input EFCL structure information and storing them in a memory; Determining whether the information on the link output variable has been read from the EFCL structure information; Reading the stored output data table list and output data table column information when the link output variable has been read as a result of the determination; Reading variable information of the legacy system for the data table column of the link output variable, and reading actual values of the legacy system corresponding to the column among them; Storing an actual value of a column type and a size of the link data table; Determining whether the last output column has been read from the variable information of the legacy system; Storing the column in a row of the link data table if the last output column of the link data table is read as a result of the determination; Determining whether the output data of the legacy system is the last low; And if the output data of the legacy system is the last row, determining whether the output data table is the last row, and if the output data table is the last output data table, converting the output data and transmitting the output data to the data storage. Link management method of web application server for interworking with legacy system in environment.