KR102639324B1 - Web service construction automation system and method, web service provision method using the same - Google Patents

Abstract

The present invention relates to a web service construction automation system, comprising: a subject call unit that declares a call method of a subject, which is service content; Among the plurality of subjects declared in the subject call unit, one or more subjects are grouped into one bundle and each call path (subject URI) of the one or more subjects is registered. A routine declaration section that declares a routine that is a list of at least one subject; When a user's request for a specific service is entered, a route is declared, which is a calling method of one of the at least one routine declared in the routine declaration part. It is characterized by including a route call unit.

Description

Web service construction automation system and method, web service provision method using the same}

The present invention relates to a web service construction automation system and method and a web service provision method using the same. A web service construction automation system and method that can quickly reflect the needs of non-expert users and prevent server overload by reducing overhead. is to provide.

In general, building and managing a web service requires specialized knowledge for development, so it is difficult for non-experts to create a website.

Content Management System (CMS) provides a user-friendly interface so that even non-experts can easily create and manage websites, but the functions it provides are extremely limited and it is difficult to expand and improve the functions.

According to the needs of non-experts, service providers that provide CMS can provide new functions and provide expansion and improvement of functions, but since this requires professional knowledge, work by experts is required.

Recently, the development of a cloud-native content management system (CMS: Contents Management System) has been required to quickly reflect the needs of non-expert users, and microservice architecture (MSA: Microservice Architecture) is being applied as a development guide for this. In practice, it can be applied in a variety of ways to build and manage web services.

The purpose of a website is to provide content, it can provide at least one content, and functions are implemented to dynamically provide this content. Content can be produced with one or more functions, and the unit that implements these functions. is defined as a subject.

In order to create a website, the functions provided by the website are implemented according to the user's needs. A website is also called a context, and this context can implement at least one or more functions, depending on the development environment. The subject, the unit that implements these functions, can be implemented by a controller, servlet, CGI (Common Gateway Interface), etc.

A client accessing a website receives service content from the website by sending a request. These requests generate overhead, and additional overhead occurs each time such a request is added. This may cause overload on the server.

Ultimately, when a client sends a single request to a website, rather than performing only one task in response and providing one service content to the client, multiple tasks are performed in one request to provide various service content. It is desirable to provide it all at once.

Meanwhile, a general content management system (CMS: Contents Management System) provides templates so that even non-experts can easily create websites, and these templates are provided with multiple service contents. However, these templates are provided with multiple service contents. Since coding work by individual professional developers is required to merge and connect, there is a problem that the service content provided is limited and expansion and improvement of functions are difficult.

Publication Patent Publication No. 10-2023-0111054 relates to a website production service providing server, which allows multiple websites to be created with an optimal design centered on the menu structure, which is the core of the website. Save a template and receive information about the menu structure including the number and depth of menus constituting the website to be created from the user terminal, and select a menu structure among the stored website templates corresponding to the information about the received menu structure. A candidate list of website templates having a menu structure is selected and provided to the user terminal, and when one website template from the candidate list is selected by the user terminal, the user's web is created according to the selected website template. Although sites are designed to be created, coding work by individual professional developers is required to merge and connect multiple service contents to these templates, so there is a problem that the service contents provided are limited and it is difficult to expand and improve functions.

Registered Patent Publication No. 10-2358855 relates to a method and device for generating a web page. In order to create various types of web pages by arranging a plurality of blocks selected from among a plurality of blocks, each of the plurality of blocks is arranged and The configuration included in each of the plurality of blocks is modified, and each of the plurality of blocks is a modular block with individual functions, and the code contents of the plurality of blocks can be modified, but the plurality of service contents are merged into each of the plurality of blocks. Since coding work by individual professional developers is required to connect, the service content provided is limited and expansion and improvement of functions are difficult.

Publication Patent Publication No. 10-2023-0033803 relates to a method of providing a website creation tool, which allows users to create a personal website that suits their tastes by creating a website based on a template page copied to the user's personal folder. When the user clicks on the marker, the information on the cell is displayed to the user through a pop-up window, allowing the user to edit it and the information on the changed cell. is applied to the template page, but individual coding work by professional developers is required to merge and connect multiple service contents to each of the plurality of cells, so the service contents provided are limited and expansion and improvement of functions are limited. There is a problem that it is difficult.

Publication Patent No. 10-2023-0080049 relates to an AI-based website production support system. In order to create web pages easily and quickly, pages are created based on categories and tags representing the basic classification of the website being produced. Alternatively, information about a template is recommended, and a website is created using the layout of the page or template selected by the user and the corresponding content, but in order to merge and connect multiple service contents corresponding to the page or template. Since coding work by individual professional developers is required, there is a problem that the service content provided is limited and it is difficult to expand and improve functions.

Public Patent Publication No. 10-2023-0111054 Registered Patent Publication No. 10-2358855 Public Patent Publication No. 10-2023-0033803 Public Patent Publication No. 10-2023-0080049

The purpose of the present invention is to build a web service by quickly reflecting the needs of non-expert users.

Another purpose of the present invention is to build a web service that prevents server overload by reducing the overhead of content service requests.

Another purpose of the present invention is to allow a user to make a single command call and call various service functions accordingly.

The problem to be solved by the present invention is not limited to the above object, and other technical problems not explicitly indicated above can be easily understood by those skilled in the art through the structure and operation of the present invention. You will be able to.

The present invention includes the following configuration to solve the above problems.

The present invention relates to a web service construction automation system, comprising: a subject call unit that declares a call method of a subject, which is service content; Among the plurality of subjects declared in the subject call unit, one or more subjects are grouped into one bundle and each call path (subject URI) of the one or more subjects is registered. A routine declaration section that declares a routine that is a list of at least one subject; When a user's request for a specific service is entered, a route is declared, which is a calling method of one of the at least one routine declared in the routine declaration part. It is characterized by including a route call unit.

The subject calling unit of the present invention is characterized in that the subject identification name is defined so that it is not duplicated even outside the class.

In the routine declaration part of the present invention, the method used when calling the two or more subjects grouped into one bundle within one routine, which is a subject list, is included in the routine declaration part of the present invention. It is characterized by having equal attribute values.

The route call unit of the present invention further provides an expression structure for the results of sequentially performing the two or more subjects grouped into one bundle within one routine, which is a subject list. It is characterized by a declaration.

In the route call unit of the present invention, the attribute value of the method used when calling the routine, which is the subject list, is grouped into one bundle in the routine declaration unit. It is characterized in that it is identical to the attribute value of the method used when calling the two or more subjects.

The present invention also relates to a method for automating web service construction, which includes the steps of declaring a call method of a subject, which is service content, in a subject call unit (S100); In the routine declaration section, at least two or more subjects among the plurality of subjects whose calling method is declared in the subject call section are grouped into one bundle to create the two or more subjects. A step (S200) of declaring a routine, which is a list of at least one subject for which each call path (subject URI) is registered; When a user's request for a specific service is entered, a route is declared, which is a calling method of one of the at least one routine declared in the routine declaration part. It is characterized in that it includes a step (S300).

Additionally, the present invention may be a computer program stored in a recording medium to execute a method for automating web service construction.

The effect of the present invention is to make it possible to build a web service by quickly reflecting the needs of non-expert users.

Another effect of the present invention is to make it possible to build a web service that prevents server overload by reducing the overhead of content service requests.

Another effect of the present invention is to make it possible for a user to make a single command call and call several service functions in response.

The effects of the present invention are not limited to the above effects, and other effects not explicitly shown above will be easily understood by those skilled in the art through the structure and operation of the present invention.

Figure 1 shows a context that is a typical website.
Figure 2(a) shows the data and overhead included in a single content service request by a user for the context of a conventional general website, and Figure 2(b) shows the data and overhead of the user for the context of a conventional general website. It shows the data and overhead included in multiple content service requests.
Figure 3 shows the data and overhead included in a user's one-time content service request for the context of the website of the present invention.
Figure 4 shows the web service construction automation system of the present invention.
Figure 5 shows the present inventor's method of automating web service construction.

Hereinafter, the overall configuration and operation according to a preferred embodiment of the present invention will be described. These examples are illustrative and do not limit the configuration and operation of the present invention, and other configurations and operations that are not explicitly shown in the examples are also provided by common knowledge in the technical field to which the present invention pertains through the examples below. If it can be easily understood by those who have it, it can be seen as the technical idea of the present invention.

The purpose of a website is to provide content, it can provide at least one content, and functions are implemented to dynamically provide this content. Content can be produced with one or more functions, and the unit that implements these functions. is defined as a subject.

In order to create a website, the functions provided by the website are implemented according to the user's needs. A website is also called a context, and this context can implement at least one or more functions, depending on the development environment. The subject, the unit that implements these functions, can be implemented by a controller, servlet, CGI (Common Gateway Interface), etc.

Figure 1 shows a context that is a typical website.

Referring to FIG. 1, the website 10 is generally also called a context, and this context can implement at least one function, and a search window (subject) is a unit that implements these functions. Functions such as 11), menu (12), login (13), news stand (14), weather (15), and shopping (16) are included.

A client accessing the website 10 receives service content from the website 10 by sending a request. In reality, even if the user is not aware of it, the client searches for it in the web browser or web application used by the user. Requests for each function, such as window (11), menu (12), login (13), news stand (14), weather (15), and shopping (16), are transmitted to the server.

These requests generate overhead and require requests for each of the following functions: search box (11), menu (12), login (13), news stand (14), weather (15), shopping (16), etc. Each time a request is added, additional overhead is generated, which can cause overload on the server.

Conventionally, in order to prevent additional overhead, several functions are displayed on the website in response to a single request sent from the client. However, for this purpose, a professional developer must manually display each function on the website. Because encoding work must be done, it becomes difficult to quickly reflect the needs of non-expert users.

Figure 2(a) shows the data and overhead included in a single content service request by a user for the context of a conventional general website, and Figure 2(b) shows the data and overhead of the user for the context of a conventional general website. It shows the data and overhead included in multiple content service requests.

Referring to Figures 2(a) and 2(b), a request from a client generates the data originally intended to be transmitted (DATA) and the overhead required to transmit this data (DATA). .

The data (DATA) and overhead (OVERHEAD) included in a single request may be small, but if such requests are transmitted multiple or repeatedly, not only the data (DATA) but also the overhead (OVERHEAD) increases rapidly. Servers that have to receive and process information may be overloaded.

Figure 3 shows the data and overhead included in a user's one-time content service request for the context of the website of the present invention.

Referring to FIG. 3, in reality, the website 10 implements various functions, and a user accesses the website 10 and makes a single request rather than sending a request for each function. By transmitting only ), the overhead included therein can be prevented from increasing.

Of course, in the past, in order to prevent additional overhead, several functions are displayed on the website in response to a single request sent from the client. However, for this to happen, a professional developer must display each function on the website. Because manual coding work must be done for this, it becomes difficult to quickly reflect the needs of non-expert users.

Figure 4 shows the web service construction automation system of the present invention.

Referring to FIG. 4, the web service construction automation system of the present invention includes a subject call unit 100, a routine declaration unit 200, and a route call unit 300.

A subject is a service function provided by a website and is developed and provided by a professional developer. In order to provide such a subject on a website, the present invention is designed to minimize the coding work that must be applied to layouts, templates, etc. includes the following specific composition.

The subject call unit 100 uses an ID, name, title, method, and URI (Uniform Resource) to declare the call method of the subject, which is service content. Identifier) Specifies properties such as path.

The ID is given as a subject identifier and cannot be changed, and the name is given as a subject identifier and can be changed outside the class as long as it is not duplicated, The title is given as a name to identify the subject, duplication is allowed, and changes are possible.

The method follows the specification definition of the method of the Hypertext Transfer Protocol (HTTP) in order to call the subject function.

The Uniform Resource Identifier (URI) path is entered to use the subject function, and can be defined using a complete Uniform Resource Identifier (URI) or Expression Language (EL).

The routine declaration unit 200 groups at least two or more subjects from among the plurality of subjects declared in the subject call unit 100 into one bundle and calls the two or more subjects. Declare a routine, which is a list of at least one subject that registers the call path (subject URI) of each subject, and for this purpose, ID, title, subject list, etc. Specify properties.

The ID is given as a routine identifier and cannot be changed, and the title is given as a name to identify the routine, duplication is allowed and change is possible.

The subject list is registered in the routine to ensure the order of the subjects, and to enable change management of the order of the subjects.

Additionally, to avoid the problem of duplication of variable names to refer to the value returned from the subject, a return object access indicator is managed for each subject.

Subjects grouped in one bundle ensure that the attribute values of the methods are the same.

The route call unit 300 is one of at least one routine declared in the routine declaration unit when a user's request for a specific service is input. To declare a route, which is a calling method, ID, routine, title, method, URI (Uniform Resource Identifier) path, layout, and viewname are used. Specify properties such as:

The ID cannot be changed after being assigned as a route identifier, the routine specifies a list of subjects as an execution process, and the title identifies the route. A name is given for this purpose, duplication is allowed, and changes are possible.

The method follows the specification definition of a method of Hypertext Transfer Protocol (HTTP) to call a route, and its attribute value is one declared as a routine. Ensure that it is identical to the attribute value of the method of the subjects grouped in a bundle.

The Uniform Resource Identifier (URI) path is for calling a route and can be defined using a complete Uniform Resource Identifier (URI) or Expression Language (EL).

The layout defines the identification code of the layout used in the template defined in the viewname attribute, and the path or alternative name of the layout can be used. .

The viewname is a template for displaying object information returned from multiple subjects after the process of subjects grouped into a bundle declared as a routine is performed. You can define an identification code and use a template path or alternative name.

The route call unit 300 calls the two or more subjects grouped into one bundle within one routine that is a subject list according to the layout and view name ( You can declare the expression structure of the results of sequentially performing subjects).

When a context such as a website or web application is established by the present inventor's web service construction automation system, general users access and send requests for specific services.

First, the route call unit 300 searches for a route that matches the request, and returns an error message if there is no route that matches the request.

Additionally, a route without a routine declaration may be searched. In this case, there is no function to perform, so the layout and viewname properties defined in the route call section are used immediately. This renders the template and responds to the user with the results.

When a route that matches the above request and has a routine declaration is searched, each call path of one or more subjects declared in the calling method of the corresponding routine (subject) URI) is traversed and a template is rendered using the searched/collected information and layout and viewname properties to respond to the user with the results.

Figure 5 shows the present inventor's method of automating web service construction.

Referring to Figure 5, the present inventor's method of automating web service construction includes the steps of declaring a call method of a subject, which is service content, in a subject call unit (S100); In the routine declaration section, at least two or more subjects among the plurality of subjects whose calling method is declared in the subject call section are grouped into one bundle to create the two or more subjects. A step (S200) of declaring a routine, which is a list of at least one subject for which each call path (subject URI) is registered; When a user's request for a specific service is entered, a route is declared, which is a calling method of one of the at least one routine declared in the routine declaration part. Step S300 is performed.

The step of declaring the calling method of the subject (S100) is to declare the calling method of the subject, which is service content, using ID, name, title, method, and URI. (Uniform Resource Identifier) Specifies properties such as path.

The ID is given as a subject identifier and cannot be changed, and the name is given as a subject identifier and can be changed outside the class to the extent that it does not overlap. The title is given as a name to identify the subject, duplication is allowed, and changes are possible.

The method follows the specification definition of the method of the Hypertext Transfer Protocol (HTTP) in order to call the subject function.

The Uniform Resource Identifier (URI) path is entered to use the subject function, and can be defined using a complete Uniform Resource Identifier (URI) or Expression Language (EL).

The step of declaring a routine (S200) bundles at least two or more subjects among the plurality of subjects declared in the step of declaring the calling method of the subject (S100). Declare a routine, which is a list of at least one subject that groups and registers the call path (subject URI) of each of the two or more subjects, and for this purpose, ID, title, and subject (subject) Specifies properties such as a list.

The ID is given as a routine identifier and cannot be changed, and the title is given as a name to identify the routine, duplication is allowed and change is possible.

The subject list is registered in the routine to ensure the order of the subjects, and to enable change management of the order of the subjects.

Additionally, to avoid the problem of duplication of variable names to refer to the value returned from the subject, a return object access indicator is managed for each subject.

Subjects grouped in one bundle ensure that the attribute values of the methods are the same.

In the step of declaring a route (S300), when a user's request for a specific service is input, any one of at least one routine declared in the step of declaring the routine (S200) To declare a route, which is a method of calling a routine, an ID, routine, title, method, URI (Uniform Resource Identifier) path, and layout are used. , specify properties such as viewname.

The ID cannot be changed after being assigned as a route identifier, the routine specifies a list of subjects as an execution process, and the title identifies the route. A name is given for this purpose, duplication is allowed, and changes are possible.

The method follows the specification definition of a method of Hypertext Transfer Protocol (HTTP) to call a route, and its attribute value is one declared as a routine. Ensure that it is identical to the attribute value of the method of the subjects grouped in a bundle.

The Uniform Resource Identifier (URI) path is for calling a route and can be defined using a complete Uniform Resource Identifier (URI) or Expression Language (EL).

The layout defines the identification code of the layout used in the template defined in the viewname attribute, and the path or alternative name of the layout can be used. .

The viewname is a template for displaying object information returned from multiple subjects after the process of subjects grouped into a bundle declared as a routine is performed. You can define an identification code and use a template path or alternative name.

In addition, the flowchart of this method of automating web service construction can be implemented as a computer program, and since each component of the present invention can be implemented as hardware or software, it may also be implemented as software running on a single piece of hardware or individual hardware. there is. Additionally, the web service construction automation method of the present invention may be implemented by being stored in a recording medium as a computer program.

10: Website (context)
11: Search box subject
12: Menu Subject
13: Login subject
14: Newsstand Subject
15: Weather Subject
16: Shopping Subject
100: Subject call unit
200: Routine declaration part
300: Route call unit
400: User

Claims (7)

In the web service construction automation system,
A subject call unit that declares a call method for a subject that is service content;
Among the plurality of subjects declared in the subject call unit, at least two or more subjects are grouped into one bundle and each call path (subject URI) of the two or more subjects is registered. A routine declaration section that declares a routine that is a list of at least one subject;
When a user's request for a specific service is entered, a route is declared, which is a calling method of one of the at least one routine declared in the routine declaration part. A web service construction automation system comprising a route call unit.
According to claim 1,
An automated system for building a web service, characterized in that the subject call unit defines the subject identifier name so that it is not duplicated even outside the class.
According to claim 1,
In the routine declaration part, the attribute value of the method used when calling the two or more subjects grouped as a bundle within one routine, which is a subject list, is A web service construction automation system characterized by equivalence.
According to claim 1,
The route call unit further declares the expression structure of the result of sequentially executing the two or more subjects grouped into one bundle within a routine that is a subject list. A web service construction automation system characterized by:
According to claim 1,
In the route call unit, the attribute value of the method used when calling the routine, which is the subject list, is the two or more groups grouped into one bundle in the routine declaration unit. A web service construction automation system characterized by being identical to the attribute value of the method used when calling subjects.
In the method of automating web service construction,
A step (S100) of declaring a call method of a subject, which is service content, in a subject calling unit;
In the routine declaration section, at least two or more subjects among a plurality of subjects whose calling method is declared in the subject call section are grouped into one bundle to create the two or more subjects. A step (S200) of declaring a routine, which is a list of at least one subject for which each call path (subject URI) is registered;
In the route call section, when a user's request for a specific service is input, a calling method of one of the at least one routine declared in the routine declaration section. A method of automating the construction of a web service, comprising the step of declaring an in route (S300).
A computer program stored in a recording medium to execute the web service construction automation method of paragraph 6.