KR20050079278A - System and methode for dealing with data transmitting between a client database and an asp application - Google Patents

Abstract

An object of the present invention is to provide an interworking system and method for interoperating with an ASP service without exposing a path of a client database on a network when interworking a database of an ASP (Application Service Provider) server and a client.

The database interworking method according to the present invention for achieving the above object is in the system consisting of an ASP server and a client, using a client processor downloaded from the ASP server to access the source database in a disconnected state with the ASP server step; A source database search and attribute matching step of searching the source database and matching the attributes by referring to the attributes required by the target database; An attribute value extraction and XML document storage step of extracting a matched attribute value from the source database and storing it as an XML document; Transmitting and storing an attribute value to transmit and store the extracted attribute value to the target database; Characterized in that it comprises a.

According to the present invention, it supports database linkage when the attribute value is the same and the attribute name is different, the system construction is light, the maintenance is easy, and the security information of the client database is prevented from being exposed to the ASP server. It reduces the load, and despite the diversity of ASP's database types, it allows you to perform attribute matching with an easy-to-use client application.

Description

System and Method for dealing with data transmitting between a client database and an ASP application}

The present invention relates to a database interworking system and method of an ASP (Application Service Provider) server and a client, and more particularly, to an interworking system that enables the interworking of a client database on a network without being exposed to an ASP provider. It is about a method.

Recently, more efficient information technology is required for the collection, sharing, and analysis of information held in a company. For example, when introducing information technologies such as Internet-based customer relationship management (e-CRM), enterprise resource planning (ERP) systems, and data warehouse systems, the independent databases and companies that these systems require There is a problem of linkage or integration with the database of the existing system. In particular, in the case of providing an application program having its own database in the form of an application service provider (ASP) application on a web server, an interworking is increasingly required to share data with an ASP client database. have.

A relatively advanced method currently used by ASP operators to solve problems that require interoperability is to extract data from the customer database in the form of an Excel file, etc. It is a form in which the service provider transmits the data using the Internet service and stores it manually in a database on his server side. However, this task requires manual processing by a database operations specialist in both cases of extracting and storing Excel files from the customer's database. The extraction of this data is required for each customer of an application that requires such a database, and the ASP operator needs to store the data for each of these customers in the database. The manual load associated with this storage date will be proportional to the number of customers. . In particular, in the case of an ASP provider with a large number of applications requiring similar tasks, the ASP database storage of the received data becomes heavy, which may cause delays in customer service. Revitalization of ASP business is hampered. In fact, this can be found in the domestic ASP market.

No literature or patent document on ASP database linkage has been found to solve this problem. The following is an introduction to the technology of database linkage in a general case.

Thomas Wiedemann, "Web-based simulation: Simulation application service providing (SIM-ASP)," (Proceedings of the 33nd conference on Winter simulation, pp. 623-628, Dec. 2001.) We mentioned necessity and dealt with data through simulation model, but did not mention how to link database for data interchange.

Amit P. Sheth and James A. Larson, "Federated database systems for managing distributed, heterogeneous, and autonomous databases," (ACM Computing Surveys (CSUR)). , Vol. 22, No. 3, 1990.) analyzed the types of heterogeneity between two databases. However, we have dealt with database interworking when the same attribute name is semantically different, but we have not dealt with interworking when the attribute names are different and need to share the same attribute value.

Erhard Rahm and Philip A. Bernstein wrote in "A survey of approaches to automatic schema matching," (The VLDB Journal-The International Journal on Very Large Data Bases, Vol. 10 No. 4, pp.334-350, 2001.). The schema matching methods of the data model were distinguished and prototype schema matchers applying each matching method were introduced.

Bwang Kwang-jun said, “EasyConnection: Efficient Interworking of Heterogeneous Databases”, (CALS / EC), The Korean Society for Electronic Transactions (CALS / EC), Vol. 4, No. 3, pp.235-246, 1999. CORBA (Common Object Request Broker Architecture) to write the database name, table name, etc., which are the database information each database user needs to share, as metadata and store it in the server, and the client uses the metadata stored in the server. To share attribute matching and attribute values.

Mark Roantree, John Murphy and Wilhelm Hasselbring, in "The OASIS multidatabase prototype," (ACM SIGMOD Record, Vol. 28, No. 1, 1999.) We built and tried to integrate schema with local database.

However, when developing a web application using CORBA, the system is developed in a three-tier way where middleware exists between the server and the client, which makes the implementation complex, difficult to maintain, and suitable for small to medium sized networks. However, there is a problem that ASP operators are burdened with CORBA technology, which is not much for developing linked programs by this technology.

In recent years, data transmission and exchange on the web using the HTTP communication protocol is generally more efficient than XML using CORBA. As a study of database interworking using XML, Kwon Eun-jung and Yong-hwan Seung, “Database: Designing and Implementing a Relational Database Metadata Repository Based on XML,” Journal of Information Processing Society, Vol.9, No.1, pp.1-10 , 2002.) generated metadata such as host name of relational database, version of specific DBMS as XML document, stored in XML-only object-oriented database, and searched for detailed information by using metadata.

Lee In-ki, Lee Min-soo and Yong Hwan-seung have not set the standard in "Design and Implementation of Web-Based OLAP Metadata Exchange System", (Journal of Information Processing Society D, Vol.9, No.6, pp.971-980, 2002.) A study on using XML as a metadata exchange model commonly used among OLAP (On Line Analytical Processing) products was conducted using an XML-only database.

As a study on XML document storage, Sang-Hyuk Jung, Kyung-Soo Joo and Lee Jung-Soo “Multimedia Database: Development of B2B Integration System based on XML Database System”, Journal of Multimedia Society, Vol. 6, No.1, pp.1-14, 2003 In the.

On the other hand, the above studies using XML use an XML-only database, but in the case of ASP business, it is not only necessary to use a commercial relational database but also to manage the metadata of many ASP clients in an ASP database that receives data. An additional problem arises. In addition, customers will be able to avoid the use of ASP applications if there is information in the metadata that they do not want to expose for security.

1 is a conventional A system configuration diagram when attribute matching and transmission are performed on the ASP server side. As shown, the conventional system is located in the target database 220 and the target database 220, which is a database of the ASP application 210 and the ASP server 200, which is an application provided by the ASP operator, and the target database 220. An ASP server including an interworking processor 220 that is responsible for all matching, extraction, and transmission functions between the source database 310 located on the client side; And a client 300 including a source database 310 and a terminal 320.

The conventional configuration as described above Referring to the data interworking procedure of the system, first, the customer 330 who wants to use the ASP application 210 provided by the ASP server 200 is connected to the ASP server 200 having the target database 220, Log in to the source database 310 located on the client 300 side. Next, a searchable attribute name is searched and registered from the source database 310 of the client by referring to the attribute name requested by the target database 220, and the attribute value extracted from the matched attribute name is transmitted to the ASP server. In addition, the transmitted data and matching-related data (for example, a database name, a table name, an attribute name, etc.) are stored in the target database 220 and the connection to the source database 310 is terminated. The customer then logs out of the connection to the ASP server after using the ASP application.

However, the conventional According to the system, when the customer logs in to his database through the ASP application 210, the user must enter the database server IP address, database login information, database name, table name, etc. online so that the information can be secured on the network. The ASP server side is always exposed, and this situation causes a problem that can only inhibit the activation of the ASP service.

In order to solve the above problems, the present invention overcomes the inefficiency of manual data transfer, avoids the problem of exposing the path information on the network of the customer database, and also has no knowledge of SQL (structured query language). An object of the present invention is to provide a database interworking system and method for easily handling data transmission.

Another object of the present invention is to provide a database interworking system and method capable of supporting interworking even when data transmitted during interworking of a database has the same attribute value but different attribute names.

In addition, an object of the present invention is to provide a database interworking system and method that can reduce the customer management load of the ASP server by managing the data interlocking-related metadata management on the customer side.

In accordance with an aspect of the present invention, an ASP server and client database interworking system includes: an ASP application provided by an ASP server to a client in a system consisting of an ASP server and a client; A target database located at an ASP server side and storing data to be used in the ASP application; And a transmission processor for transmitting matched data between the target database and a source database located at a client side, wherein the client comprises: a source database storing data of a customer; A client processor that can download data from an ASP server by matching data of the source database with reference to attributes required by the target database while being disconnected from the ASP server; And a customer terminal capable of confirming the extracted data result of the attribute matched customer obtained by executing the client processor.

In addition, the ASP server of the ASP server and the client database interworking system according to the present invention further comprises an XML DB converter for converting the XML document to fit the target database, the client to store the matched result in an XML file It is preferred to further comprise means.

In addition, it is preferable that the client of the ASP server and the client database interworking system according to the present invention further comprises means for storing, as metadata, attribute names of the source database that match one-to-one with the attribute names requested by the target database.

A method of interworking a database between an ASP server and a client according to the present invention includes: accessing a source database in a state in which a connection with an ASP server is blocked by using a client processor downloaded from an ASP server; A source database search and attribute name matching step of searching the source database and matching attributes by referring to attributes required by a target database; An attribute value extraction and XML document storage step of extracting a matched attribute value from the source database and storing it as an XML document; And transmitting and storing the attribute value to be transmitted and stored to the target database.

In addition, the step of accessing the source database of the database server interworking method of the ASP server and the client according to the present invention includes the steps of downloading a client processor from the ASP server; Blocking a connection between the client processor and the ASP server; Logging in to the source database; characterized in that consisting of.

In addition, the step of logging into the source database of the ASP server and the client database interworking method according to the present invention is preferably by a user interface screen providing a database instance name, ID (ID) and password input window.

In addition, the source database search and attribute matching step of the database server interworking method of the ASP server and the client according to the present invention is a step of confirming the attributes required by the target database output on the user interface of the client processor has been downloaded and successfully logged in ; Searching for an attribute to match the required attribute in the target database by using a tree structure menu consisting of the database, tables and attributes of the connected customer displayed on the user interface screen upon successful login. ; Inputting a matchable attribute to an input unit of a user interface screen; Performing matching; characterized in that consisting of.

In addition, the step of inputting to the input unit of the user interface screen of the ASP server and the client database interworking method according to the present invention is preferably by a direct input unit or a drag and drop (drag & drop) method.

In addition, the step of searching the source database and the attribute matching method of the database server interworking method of the ASP server and the client according to the present invention comprises the steps of checking the presence of pre-stored metadata; Loading metadata when there is already stored metadata; Performing matching; characterized in that consisting of.

In addition, the step of extracting the attribute value and storing the XML document in the method of interworking the database between the ASP server and the client according to the present invention may include: extracting, by the client processor, attribute values of related attribute names from the source database in a batch when matching is completed; Storing the extracted data as an XML file; Displaying a matching result on a user interface screen to confirm whether the extracted data is suitable; Characterized in that consisting of.

In addition, the step of extracting the attribute value and storing the XML document in the method of interworking the database between the ASP server and the client according to the present invention preferably further includes storing metadata.

In addition, the step of transmitting and storing the attribute value of the ASP server and the client database interworking method according to the invention comprises the steps of connecting the client processor and the ASP server; Transmitting, by the transport processor, the matching data to the XML DB converter; Converting the transmitted matching data into a format suitable for a target database by an XML DB converter; Inputting and storing the converted data in a target database; Characterized in that consisting of.

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

2 is a configuration diagram of a database interworking system according to the present invention. As shown, the system according to the present invention is located in the ASP application 410 and the ASP server 400, which are applications provided by the ASP server, and a target database 420 for storing data to be used in the ASP application 410. XML to convert the transport processor 430 and the XML document to be suitable for the target database 420 between the target database 420 and the source database 510 located on the client side while being located at the ASP server side. An ASP server including a DB converter 440; And a database on the user interface screen of the client processor which the customer 540 describes his or her related database and table by referring to the attribute names requested by the source database 510 and the target database 420 storing the client data. A client processor that searches a tree-type menu consisting of a table and an attribute, matches an attribute name necessary for matching with an attribute name of the target database 510 on the same screen, and extracts and uses the matched data as an XML file. And a client 300 including a 520 and a terminal 530.

The database interworking system according to the present invention configured as described above is used in a client's own database off-line with the ASP server using a client processor (or application program) provided by an ASP server (or a web site). Connect. After that, the property name required by the target database of the ASP server is matched and the property value is extracted into the XML file. It accesses the ASP site online and sends the XML file to the database.

Hereinafter, the data interworking method of the system according to the present invention will be described in more detail.

The first step for data interworking is a step in which a customer accesses the source database 510 (S100). In order to match the attribute, the customer must first access his or her source database 510. The connection to the source database 510 is disconnected from the ASP server by using a client processor downloaded from the ASP server 400 (S110). That is, in the offline state (S120). The reason for accessing the source database 510 in the offline state as described above is to eliminate the problem that the login information is exposed to the ASP operator during the access process.

Here, the client processor 520 is a program for matching and extracting data of the source database 510 according to the attributes required by the target database 420. The client may access the ASP server 400 and download the data when necessary. It may be.

3 shows an embodiment of a login using a user interface screen. The above screen is a database instance name, an IP address, and an ID 620 and a password 630 for accessing the database 610 so that the customer 540 can connect to the source database 510. And so on.

The input of information on the input window begins with the selection of a database, which is a specific button (for example, a graphic user interface (GUI)) screen as shown in FIG. By clicking on button 640. That is, for example, when the customer clicks the above button, a GUI screen (not shown) shows a list of all database instances recognizable on the local network of the customer's platform, and the customer can select a desired database from among them.

Of course, if the customer knows the instance name or IP address of the source database 510, the database instance name may be directly input to the input unit 610 on the screen of FIG. 3 (S130).

The second step is the source database search and attribute name matching step (S200). 4 is a screen provided by the client side processor 520 to facilitate a customer database source search and attribute name matching. In FIG. 4, the right side of the screen (hereinafter also referred to as a 'target screen unit') is an attribute name required for the target database 420 and a description of each attribute, and the left side of the screen (hereinafter also referred to as a 'small screen unit') is a connected source. This is a result of showing the database 510 in the form of a tree structure in the order of the database name 710, the table name 720, and the attribute name 730.

For attribute name matching, the customer checks the types of attributes required by the target database of the ASP server from the right screen (S210), and searches the tree structure of the left screen for the attribute names matching the requested property names on the right (S220). ). The attribute names found as a result of the search are matched by dragging and dropping them to the matching attribute input unit 740 on the right screen or directly inputting the attribute names (S230). At this time, in order to avoid problems such as data type mismatch, all data types of the attributes of the target database 420 are varchar types, so that any type of data can be accommodated without coercion.

The result input to the attribute matching input unit 740 of FIG. 4 is to search for and match the attribute name required by the target database 420 in the source database 510 (S240). For example, Customer_ID is ACCOUNT_ID and Name is NAME. Matches.

On the other hand, when the customer has performed attribute matching in the past, the present invention checks whether there is already stored metadata when executing the client processor 520, and if there is already stored metadata, the metadata stored in the platform of the customer By reading the data and displaying the attribute matching result on the screen, the attribute value may be extracted without performing attribute matching repeatedly (S210 '). The generation of the metadata file to store the matched result will be described later.

The third step is an attribute value extraction and XML document storage step (S300). When the one-to-one matching process of all the attribute names is completed through the above steps, the client processor 520 extracts the attribute values for the associated attribute names (S310) and stores them as an XML file 550 (S320). The stored XML file 550 preferably has a valid format for the XML document structure. In the present invention, an attribute value is extracted into an XML file because a domain-specific attribute tag used by an ASP application is used. Easy to define, XML is the industry's standard for data exchange, cross-platform data transfer, compact documents, small XML parser programs, and cross-platform use. It is more effective than using Excel file because it has various advantages.

In addition, the client processor 520 simultaneously stores the attribute name of the source database 510 that is one-to-one matched to the attribute name requested by the target database 420 as metadata 560 on the customer platform. If matching is required, repetitive work may be avoided (S330).

5 illustrates a screen provided to check attribute value data of the XML document 550 generated as a result of performing the attribute matching step. When the customer checks the data of the XML document through the screen as described above and wants to transmit the data to the target database 420, the customer may execute a completion 810. Otherwise, the customer may cancel the generation result (820) (S340). ). On the other hand, attribute value extraction and XML document storage are performed in a back-end interface.

The fourth step is to transmit and store the extracted attribute value to the ASP server (S400). The attribute value data extracted into the XML file should be transmitted to the ASP server. In order to transmit the attribute value data to the ASP server, the client processor needs to be connected to the ASP server online (S410). Once the server is online with the ASP server, data transfer is performed by the transfer processor 430 located on the ASP server side at the same time as the uploading command of the client's xml file. The transfer processor 430 is extracted from the client's source database. The extracted attribute value data is read and transmitted to the XML DB converter 440 (S420).

Meanwhile, the XML DB converter 440 converts the data so as to be suitable for the target database (S430), and then inputs and stores the data in the target database 420 (S450). It is used by. In this case, before storing, it is preferable to output the read XML document to the terminal 530 of the customer to confirm whether it is finally stored or used once more (S440).

As described above, the present invention performs a preprocessing process in which a client processes a property matching and extraction offline after accessing a database on his local network using a client processor downloaded from an ASP server. The extracted data is then transmitted to the ASP server side via the web in the online state, stored in a database through a post processor on the server side, and used by the ASP application.

As described above, the data interlocking system and method according to the present invention support database interlocking when the attribute values are the same and the attribute names are different, the system construction is light, the maintenance is easy, and the security information of the client database. Prevents exposure to ASP servers, lowers the load on ASP servers, and provides attribute matching with an easy-to-use client application despite the variety of ASP customer database types.

In addition, the data interworking system and method according to the present invention has the effect of reducing the error and time of input because the customer's data delivered to the ASP provider is automatically processed at the system level without being input to the ASP server side in the manual form.

In addition, the data interlocking system and method according to the present invention not only exposes the security information related to the database of the customer according to the data transmission to the ASP side, but also manages the data interlocking related metadata on the customer side, thereby managing the customer management load of the ASP server. It has the effect of lowering.

In addition, the present invention has an effect that the database interworking system of ASP does not use middleware such as CORBA, so that the interlocking system can be lightly constructed.

1 is a system configuration diagram when a conventional attribute matching and transmission is performed on the ASP server side.

2 is a configuration diagram of a database interworking system according to the present invention.

3 shows an example of login using a user interface screen.

4 illustrates an example of attribute value matching using a user interface screen.

5 is a screen showing an attribute value matching result.

6 is a flowchart illustrating a database interworking method according to the present invention.

Claims (13)

In a system consisting of an ASP server and a client, The ASP server includes an ASP application provided to the client by the ASP server; A target database located at an ASP server side and storing data to be used in the ASP application; And a transmission processor for transmitting matched data between the target database and a source database located at a client side. Including, The client includes a source database that stores data of the client; A client processor that matches data of the source database by referring to the attributes required by the target database while being disconnected from the ASP server; And a customer terminal for checking an execution result of the client processor. The method of claim 1, wherein the ASP server further comprises an XML DB converter for converting the XML document to fit the target database, And said client further comprises means for storing the matched result in an XML file. 3. The database of claim 1 or 2, wherein the client further comprises means for storing, as metadata, attribute names of the source database that match one-to-one with the attribute names requested by the target database. Interlock system. The client processor of claim 1, wherein the client processor comprises a user interface screen unit, wherein the user interface screen unit is configured to display and input an attribute name requested by a target database, and a connected source. A database interworking system of an ASP server and a client, characterized in that the source screen unit displays the structure of the database. In a system consisting of an ASP server and a client, Accessing a source database in a state in which connection with the ASP server is blocked by using a client processor downloaded from the ASP server; A source database search and attribute name matching step of searching the source database and matching attributes by referring to attributes required by a target database; An attribute value extraction and XML document storage step of extracting a matched attribute value from the source database and storing it as an XML document; Transmitting and storing an attribute value to transmit and store the extracted attribute value to the target database; Database interworking method of the ASP server and the client comprising a. The method of claim 5, wherein the step of accessing the source database is Downloading a client processor from an ASP server; Blocking a connection between the client processor and the ASP server; Logging in to the source database; Database interworking method of the ASP server and the client, characterized in that consisting of. 7. The method of claim 6, wherein logging in to the source database A database interface method of an ASP server and a client, characterized in that the user interface screen providing a database instance name, ID (ID) and password input window. The method of claim 5, wherein the searching and attribute matching of the source database is performed. Identifying attributes required by the target database; Retrieving a required attribute from a source database; Inputting a matchable attribute; Performing a match; Database interworking method of the ASP server and the client, characterized in that consisting of. The method of claim 8, wherein the searching of the attribute in the source database comprises: searching for a required attribute through a source screen unit of a user interface screen unit, and inputting a matchable attribute to a target screen unit of the user interface screen unit. A method of interlocking a database between an ASP server and a client, which comprises directly inputting an attribute input unit or inputting an attribute of a source screen unit by a drag and drop method. The method of claim 5, wherein the searching and attribute matching of the source database is performed. Confirming the existence of pre-stored metadata; Loading metadata when there is already stored metadata; Performing a match; Database interworking method of the ASP server and the client, characterized in that consisting of. The method of claim 5, wherein the attribute value extraction and XML document storing step Once the matching is complete, the client processor collectively extracting attribute values of related attribute names from a source database; Storing the extracted data as an XML file; Displaying a matching result on a user interface screen to confirm whether the extracted data is suitable; Database interworking method of the ASP server and the client, characterized in that consisting of. The method of claim 5 or 11, wherein the attribute value extraction and the XML document storing step are performed. The database interworking method of the ASP server and the client further comprising the step of storing the metadata. 6. The method of claim 5, wherein transmitting and storing the attribute value Connecting the client processor and the ASP server; Transmitting, by the transport processor, the matching data to the XML DB converter; Converting the transmitted matching data into a format suitable for a target database by an XML DB converter; Inputting and storing the converted data in a target database; Database interworking method of the ASP server and the client, characterized in that consisting of.