KR20210025779A - Automatic configuration method for openapi linkage - Google Patents

Abstract

The present invention relates to an automatic configuration method for OpenAPI linkage implemented so that a new link API can be registered only by configuration without adding a new component, comprising: entering a key value in the URL, requesting sample data, listing the items of the returned data by level, and expressing each attribute and value separately if there is an OpenAPI request address and an acquired key; generating metadata by selecting, by a user (or an administrator), an attribute ID of a corresponding item and selecting a value or attribute of the corresponding data; reading data through the generated metadata and storing it in a DB or as an object; building the interface that the meta data to be set stores the type so that data can be loaded by specifying the shape of global properties, objects, and lists (or page lists), and when the data is loaded, the developer uses it immediately in the form of an object, and every time each record is patched, if necessary, it automatically requests the API through paging so that the developer doesn′t care about the association.

Description

Automatic setting method for OpenAPI linkage{AUTOMATIC CONFIGURATION METHOD FOR OPENAPI LINKAGE}

The present invention relates to an automatic setting method for OpenAPI connection, and more particularly, to an automatic setting method for OpenAPI connection implemented so that a new connection API can be registered only by setting without adding a new component.

With the advent of the ubiquitous environment, subnetworks to provide the ubiquitous environment are diversifying. Several sub-networks such as Jini, UPnP, DPWS, and Bluetooth are provided for service discovery in a ubiquitous environment.

In such a ubiquitous environment, it is difficult for one of the existing protocols to solve all the problems that arise, such as the flexibility of the location, information, and status of various devices and services. To this end, despite the existence of various heterogeneous service discovery middlewares, new service discovery middlewares specialized for personal electronic devices and home appliances are emerging.

In other words, as the ubiquitous environment develops, people can use services regardless of time and space. Accordingly, many types of ubiquitous devices and services have been developed. Each of these services has developed its own network protocol to communicate.

On the other hand, the above-described background technology is technical information that the inventor possessed for derivation of the present invention or acquired during the derivation process of the present invention, and is not necessarily known to be known to the general public prior to filing the present invention. .

Korean Patent Registration No. 10-1348927 Korean Patent Registration No. 10-0811407

One aspect of the present invention is to develop each linked component for the use of OpenAPI in these days when the demand for OPENAPI and data linkage increases.There are many parts that developers need to care about. There is a problem that needs to be corrected, and it provides an automatic setting method for OpenAPI linkage that automates this so that a new linkage API can be registered only by setting without adding a new component.

The technical problem of the present invention is not limited to the technical problem mentioned above, and other technical problems that are not mentioned will be clearly understood by those skilled in the art from the following description.

If there is an OpenAPI request address and an acquired key according to an embodiment of the present invention, the key value is entered into the URL, and sample data is requested, listing the returned data item by level, and displaying each attribute and value separately The step of doing; Generating metadata by selecting an attribute ID of a corresponding item and selecting a value or attribute of the corresponding data, by a user (or an administrator); Reading data through the generated metadata and storing it in a DB or as an object; And the metadata to be set stores the type so that data can be loaded by designating the type of global properties, objects, and lists (or page lists). When the data is loaded, the developer is directly used in the form of an object and patching each record. It includes a step of constructing an interface so that the developer does not care about connection by automatically requesting an API through paging whenever necessary.

According to one aspect of the present invention described above, it is possible to provide an effect of improving the speed of development by constructing an interface through which a developer can directly utilize various object styles according to data types.

The effects of the present invention are not limited to the above-mentioned effects, and various effects may be included within a range apparent to those of ordinary skill in the art from the contents to be described below.

1 is a flowchart illustrating an automatic setting method for linking OpenAPI according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The detailed description of the present invention described below refers to the accompanying drawings, which illustrate specific embodiments in which the present invention may be practiced. These embodiments are described in detail sufficient to enable a person skilled in the art to practice the present invention. It should be understood that the various embodiments of the present invention are different from each other, but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the present invention in connection with one embodiment. In addition, it should be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the present invention. Accordingly, the detailed description to be described below is not intended to be taken in a limiting sense, and the scope of the present invention, if appropriately described, is limited only by the appended claims, along with all ranges equivalent to those claimed by the claims. Like reference numerals in the drawings refer to the same or similar functions over several aspects.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the drawings.

1 is a flowchart illustrating an automatic setting method for linking OpenAPI according to an embodiment of the present invention.

Referring to FIG. 1, in the automatic setting method for OpenAPI linkage, first, if there is an OpenAPI request address and an acquired key, enter the key value into the URL, request sample data, and list the items of the returned data by level, respectively. The attribute and value of are separated and displayed (S110).

The user (or administrator) selects an attribute ID of a corresponding item and selects a value or attribute of the corresponding data to generate metadata (S120).

Data is read through the generated metadata and stored in a DB or as an object (S130).

The metadata to be set stores the type so that data can be loaded by designating the global property, object, and list (or page list) type, and when the data is loaded, the developer is directly used in the form of an object and is used when patching each record. Whenever necessary, an interface is built so that the developer does not care about connection by automatically requesting an API through paging (S140).

The automatic setting method for OpenAPI linkage having the above-described steps can improve the speed of development by constructing various object styles according to the type of data and constructing an interface that allows developers to directly utilize them.

Referring to Table 1 to describe API metadata settings, when metadata is input when entering a link address, the program automatically displays the input window of the corresponding item so that the corresponding value can be specified, and when metadata is inherited. This allows you to automatically add similar types of data.

Inheritance of metadata is easy to set connection API by inheriting preset metadata defined in advance when there is a data protocol of a certain format such as WMS and WFS. Therefore, metadata in this format can be provided as a basic preset. Make it easy to build a connection API.

Refer to Table 2 to show WMS metadata settings.

Table 3 describes the setting of the connection API of the WMS method, and it is possible to select whether to redefine the upper meta data and expand it, or to set the connection API only with the default input value.

The format of the response data is to separate the data type by setting the data type such as TXT, CSV, XML (GML, KML, etc.), and the data is in the form of a tree. Select the schema of the data to be returned from among the types of list, etc., and set whether to list the data or convert it into an object only by setting.

In response data format designation, the response data format is set as metadata to automatically parse the data format for a general response by creating a common preset for the response data format as well as the request metadata.

The meta data setting (example) of GML data reception is shown in Table 4 below.

In other words, in the case of a location, if you select and designate a location from the tree and designate the value name of the corresponding value, the read response data value according to the data type is saved in a map or list.

Response data management is designated so that if an error occurs in the read part with the specified value, the administrator is notified so that the response is abnormal, and the details can be taken. This is through the accumulated value of the error. By providing a notification function so that the user (or administrator) can take action by identifying the cause when the service can be maintained due to a certain number of errors in the response, a management program is provided so that the response data can always operate normally. Respond to changes in related OpenAPI without modification of development.

The above-described embodiments are for illustrative purposes only, and those of ordinary skill in the art to which the above-described embodiments belong can easily transform into other specific forms without changing the technical spirit or essential features of the above-described embodiments. You can understand. Therefore, it should be understood that the above-described embodiments are illustrative and non-limiting in all respects. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as being distributed may also be implemented in a combined form.

The scope to be protected through the present specification is indicated by the claims to be described later rather than the detailed description, and should be interpreted as including all changes or modified forms derived from the meaning and scope of the claims and the concept of equivalents thereof. .

Claims (1)

If there is a request address of OpenAPI and an acquired key, inputting a key value into the URL, requesting sample data, listing the returned data items by level, and separating and expressing each attribute and value;
Generating metadata by selecting an attribute ID of a corresponding item and selecting a value or attribute of the corresponding data by a user (or administrator);
Reading data through the generated metadata and storing it in a DB or as an object; And
Meta data to be set stores the type so that data can be loaded by designating the type of global properties, objects, and lists (or page lists), and when the data is loaded, the developer is directly used in the form of an object and is used when patching each record. Building an interface so that the developer does not care about the connection by automatically requesting the API through paging whenever necessary; including, automatic setting method for OpenAPI connection.

Images