KR102614060B1 - Automatic analysis method for converting general applications into software-as-a-service applications - Google Patents

Abstract

The present invention relates to an automatic analysis method for converting a general application into a service-type software application.
For this purpose, the present invention performs an automatic analysis method on a computing device to convert a general application into a service-type software application, including the steps of (a) remotely accessing the general application execution environment using Agentless (SSH; Secure Shell) method; (b) executing the general application collection script as a System CLI Shell type collection script; (c) collecting execution environment and service environment information of general applications; (d) storing execution environment and service environment information of general applications; (e) a step where the general application downloads the source code from a source management tool (Git), analyzes and stores it; (f) Tagging the function of the stored source code; (g) searching for service connection information in the source code of a general application; (h) analyzing and combining the environment information of the general application and the connection information discovered from the source code into data; (i) registering a connection function; and (j) visualizing and querying component analysis information as a topology map using connection function matching.
The present invention configured as described above is a cloud conversion analysis technology for source analysis and workload distribution to automatically convert a typical 3-tier (WEB/WAS/DB) application in a legacy environment to a SaaS application in an IaaS/PaaS operating environment. This significantly improves the quality and reliability of the service method, allowing the service to spread further by satisfying the various desires (needs) of users, developers, operators, managers, and people in charge.

Description

Automatic analysis method for converting general applications into software-as-a-service applications}

An embodiment of the present invention relates to an automatic analysis method for converting a general application into a software-as-a-service (SaaS) application, and more specifically, a general 3-tier (WEB/WAS) application in a legacy environment. /DB) application program to a SaaS application in an IaaS/PaaS operating environment, and provides cloud conversion analysis technology for source analysis and workload distribution. This significantly improves the quality and reliability of the service method, so that users can This is to enable the service to spread further by satisfying the various desires (needs) of developers, operators, managers, and people in charge.

Unless otherwise indicated herein, the matters described in this identification are not prior art to the claims of this application, and are not admitted to be prior art by being described in this identification.

As you know, Software-as-a-Service (SaaS) is a cloud-based software delivery method. The SaaS user subscribes to the application instead of purchasing and then installing the application. Users can log in and use SaaS applications on compatible devices over the Internet. The actual application runs on a cloud server that may be remote from the user's location.

The software-as-a-service (SaaS) application includes agentless information collection technology, source code analysis technology, service connection information search technology, analysis data combination technology, connection function matching technology, and analysis information visualization technology. Although required, the conventional technology had a problem in that there was no automatic analysis method for converting SaaS into an application.

In particular, the above prior art requires many people, including source developers, application operators, and application service managers, to reliably service general 3-tier (WEB/WAS/DB) applications as SaaS Applications in the cloud operating environment, IaaS/PaaS. There were technical problems that required knowledge and know-how about cloud conversion and technology from parties involved in the business.

In order to solve the above-mentioned problems, the following prior art documents have been developed, but there is still a big problem that the problems of the above-described prior art cannot be solved at once.

Republic of Korea Patent Publication No. 2134309 (2020. 07. 09) has been registered. Republic of Korea Patent Publication No. 2469977 (November 18, 2022) has been registered. Republic of Korea Patent Publication No. 2471221 (November 22, 2022) has been registered. Republic of Korea Patent Publication No. 2323276 (2021. 11. 02) has been registered. Republic of Korea Patent Publication No. 2439778 (2022. 08. 30) has been registered.

The present invention was developed to solve all the problems of the prior art as described above, and includes information collection technology, source code analysis technology, service connection information search technology, analysis data combination technology, connection function matching technology, and analysis information visualization technology. The first purpose is to provide this, and the second purpose of the present invention based on the above-described technical configuration is to convert a general 3-tier (WEB/WAS/DB) application program in a legacy environment into a SaaS application in an IaaS/PaaS operating environment. In order to automatically convert, it provides cloud conversion analysis technology for source analysis and workload distribution. The third purpose is to analyze the source code without the intervention of the source developer, and application operators can easily convert to the cloud even if they have no knowledge. The fourth purpose is to enable conversion to an IaaS/PaaS environment, and the fourth purpose is to enable application service managers to maintain and manage stable SaaS services in a cloud environment. The fifth purpose is to enable application management through agentless information collection. The purpose is to collect operating environment information without any load or interference, and the sixth purpose is source code analysis, which is a process of analyzing connection information between applications and services, tagging functions in the source code and exploring service connection information. By collecting analysis information, it is possible to easily simplify the complex and difficult process of maintenance developers or engineers analyzing source code. The seventh purpose is to analyze and combine the collected operating environment information and source code data, The goal is to provide convenience to application service managers by matching connection functions to configure and visualize standardized analysis results. The 8th purpose is to significantly improve the quality and reliability of the service method, so users such as developers, operators, and managers It provides an automatic analysis method for converting general applications into service-type software applications to further expand services by satisfying the various desires (needs) of the people in charge.

To achieve this purpose, the present invention performs an automatic analysis method on a computing device to convert a general application into a service-type software application. (a) Remotely accesses the general application execution environment using Agentless (SSH; Secure Shell) method. steps; (b) executing the general application collection script as a System CLI Shell type collection script; (c) collecting execution environment and service environment information of general applications; (d) storing execution environment and service environment information of general applications; (e) a step where the general application downloads the source code from a source management tool (Git), analyzes and stores it; (f) Tagging the function of the stored source code; (g) searching for service connection information in the source code of a general application; (h) analyzing and combining the environment information of the general application and the connection information discovered from the source code into data; (i) registering a connection function; and (j) visualizing and querying the component analysis information as a topology map using connection function matching.

As discussed in detail above, the present invention is a cloud conversion for source analysis and workload distribution in order to automatically convert a typical 3-tier (WEB/WAS/DB) application program in a legacy environment to a SaaS application in an IaaS/PaaS operating environment. Provides analysis technology.

In addition, the present invention analyzes source code without the intervention of a source developer, and allows application operators to easily switch to a cloud IaaS/PaaS environment even if they have no knowledge or knowledge about the cloud.

And the present invention allows application service managers to maintain and manage stable SaaS services in a cloud environment.

In particular, the present invention allows information on the operating environment to be collected without any load or interference on the running application through agentless information collection.

In addition, the present invention is that source code analysis is a process of analyzing connection information between applications and services. Analysis information can be collected by tagging functions of the source code and exploring service connection information, allowing maintenance developers or engineers to analyze the source code. This is to simplify a complex and difficult process.

In addition, the present invention analyzes and combines collected operating environment information and source code data, matches connection functions, and configures and visualizes standardized analysis results to provide convenience to application service managers.

The present invention is a very useful invention that significantly improves the quality and reliability of the service method due to the above-described effects, thereby enabling the service to further spread by satisfying the various desires (needs) of users (developers, operators, managers, and people in charge).

Hereinafter, a preferred embodiment of the present invention for achieving these effects will be described in detail according to the attached drawings.

Figure 1 is a configuration diagram of a general web application.
Figure 2 shows the results of collecting and analyzing general application information.
A flowchart expressing a series of processes.
Figure 3 shows Postgre in the source code of the general application backend (API).
Source code containing connection information calling the SQL (Database) service
Example of function of de.
Figure 4 is a diagram comparing the legacy environment and SaaS conversion prediction map.

The automatic analysis method for converting a general application applied to the present invention into a service-type software application is configured as shown in FIGS. 1 to 4.

In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description will be omitted.

In addition, the terms described below are terms established in consideration of the functions in the present invention, and may vary depending on the intention or custom of the producer, so their definitions should be made based on the content throughout the specification.

In addition, since the size and thickness of each component shown in the drawings are arbitrarily shown for convenience of explanation, the present invention is not necessarily limited to what is shown in the drawings.

First, the present invention is equipped with a method of information collection technology, source code analysis technology, service connection information search technology, analysis data combination technology, connection function matching technology, and analysis information visualization technology.

Meanwhile, the present invention can be variously modified and take various forms when applying the above-mentioned components.

And it should be understood that the present invention is not limited to the particular form mentioned in the above detailed description, but rather includes all modifications, equivalents and substitutes within the spirit and scope of the present invention as defined by the appended claims. It should be understood as

The effect of the automatic analysis method for converting the general application of the present invention configured as above into a service-type software application is explained as follows.

First, the present invention provides a cloud conversion analysis technology for source analysis and workload distribution to automatically convert a typical 3-tier (WEB/WAS/DB) application in a legacy environment to a SaaS application in an IaaS/PaaS operating environment. It is done.

For this purpose, Figure 1 applied to the present invention is a configuration diagram of a general Web Application. A general application in a legacy environment for automatic conversion to SaaS Application includes a front-end (UI), back-end (API) and service programs (database, message) developed by the user. It can be separated into standardized roles in a 3-tier (WEB/WAS/DB) structure (Queue, Redis, ETC).

In addition, Figure 2 shows a flowchart expressing a series of processes from collecting general application information to querying the analysis results.

And Figure 3 is an example function diagram of the source code that includes connection information for calling the Postgre SQL (Database) service from the source code of the general application backend (API), showing service connection information search.

Additionally, Figure 4 shows a diagram comparing the legacy environment and the SaaS conversion prediction map.

Below, the automatic analysis method for converting the general application of the present invention into a service-type software application will be described in more detail as follows.

First, the present invention involves performing an automatic analysis method on a computing device to convert a general application into a service-type software application, and goes through the following steps.

That is, the present invention goes through the steps of (a) remotely accessing a general application execution environment using Agentless (SSH; Secure Shell) method.

At this time, step (a) is a case of a general web application as shown in Figure 1. The general application in the legacy environment for automatic conversion to SaaS Application includes the front-end (UI), back-end (API) and service program developed by the user. It can be separated into standardized roles in a 3-tier (WEB/WAS/DB) structure (e.g. database, message queue, Redis, ETC).

For example, the front end of a general application is WEB UI using the VueJS framework, and the back end is an API developed using Spring Boot. Session information is stored in Redis to maintain continuity and consistency of session management, and user data is stored in Redis. There is a general application that is stored in a database called PostgreSQL.

In addition, the present invention goes through the step of (b) executing the general application collection script as a System CLI Shell type collection script.

At this time, step (b) above is information collection by Remote Agent (Agentless method), and as shown in Table 1 below, an agentless SSH connection is used to collect various information on various execution environments in the legacy environment where general applications are running. Uses Remote Agent, which executes CLI shell-based script and collects the results. The following asset information and performance information are collected through Remote Agent.

Server classification OS CPU Memory Disk CPU Usage Memory Usage User WEB server Ubuntu 14.04 8core 8GB 100G utilization utilization User API server Ubuntu 14.04 4core 8GB 40G utilization utilization Databaseserver Ubuntu 14.04 4core 8GB 40G utilization utilization Message queue server Ubuntu 14.04 4core 4GB 20G utilization utilization

The present invention collects basic information about OS information and CPU, memory, and disk infrastructure based on the collected information.

Then, the present invention goes through the step (c) of collecting execution environment and service environment information of general applications.

At this time, step (c) above requires more than the runtime-environment of the general application and the type and version information of the service in order to convert a general application in the legacy operating environment to a SaaS application in a cloud environment, as shown in Tables 2 and 3 below. Detailed information must be collected.

Application runtime environment information

Process name Development language Execution environment Version role UserWEB UI VueJS JVM 17 Frontend User API Java/SpringBoot JVM 17 Backend

Service environment information

Process name Version Service category Redis 5.0.6 message queue PostgreSQL 8.0 Database

The runtime environment information and service environment information of the general application are collected and analyzed by remotely accessing the agentless method using a remote agent and executing a System CLI Shell-based script. Remote Agent analyzes runtime environment information and service environment information of general applications by referring to executable files and configuration files collected at the process level. According to the results of analyzing the collected information, the user WEB UI was developed using a NodeJS-based framework called VueJS, the user API used Java-based SpringBoot, and the service used is a message queue service called Redis for session management. The user data is stored in the environmental information DB by analyzing the application of a DBMS called PostgreSQL.

Additionally, the present invention goes through the step of (d) storing the execution environment and service environment information of the general application.

In addition, the present invention goes through the steps of (e) the general application downloading the source code from the source management tool (Git), analyzing and storing it. This is the source code analysis of the general application, and the purpose of the source code analysis is the backend of the general application. This is to substantially verify the connection information between the (API) and the service.

At this time, the most recent (Master branch) source code is downloaded from a tool (e.g. Git, etc.) that manages the backend (API) source code of the general application and saved for analysis. To analyze the source code, tag all functions defined in the saved source code, analyze the source code of the general application, and call a specific function of the practical service (Service) used by the backend (API) of the general application. The exact connection information of the service is verified by exploring the part where the call is made.

In addition, the present invention goes through the step of (f) tagging the function of the stored source code, which creates a tag on the function defined in the source code and indexes the location of the function so that the function can be easily recognized.

At this time, the source code analyzer creates tagging as shown in Table 4 below for all functions declared in the stored source code.

Tag name file name number of lines Defined format in file Class.forName LoadDriver.java 23 Class.forName("org.postgresql.Driver"); Class.forPassword LoadDriver.java 78 Class.forPassword("org.postgresql.Driver"); Class.forProject LoadDriver.java 97 Class.forProject("org.postgresql.Driver"); Class.forCluster LoadDriver.java 123 Class.forCluster("org.postgresql.Driver"); Class.forNameSpace LoadDriver.java 157 Class.forNameSpace("org.postgresql.Driver"); Class.forAccount LoadDriver.java 256 Class.forAccount("org.postgresql.Driver");

And, the present invention goes through the step of (g) searching for service connection information in the source code of a general application, which means that after tagging all functions of the backend (API) source code of a general application where the source code analyzer is stored, the general application Search for connection information that calls a specific function of the service in the source code of the backend (API).

At this time, the general application is a function of the source code that includes connection information calling the PostgreSQL (Database) service from the source code of the backend (API), as shown in Figure 3.

In addition, the present invention goes through the step of (h) analyzing and combining the environment information of the general application and the connection information discovered from the source code into data, which builds more accurate information by combining (merging) various collected and analyzed information. As a step, first, the runtime environment information and service environment information of the general application stored in the environment information DB are retrieved, and the source code analyzer specifies the service from the source code of the general application backend (API). Accurate connection function information is generated by combining the connection information search results that call the function.

In addition, the present invention goes through the step of (i) registering a connection function, which is connection function matching, and connection function matching is determined using information on the connection function created through analysis data combination. A connection function matching task is performed to search for a connection function that contains accurate connection information for the service, and if it is not detected, a query is made to LLM (ChatGPT) for language-specific codes.

For example, if you create a java source to connect to Postgre SQL and request a Restful API, the source code is returned among the query response results.

Among the results, the prediction function related to postgresql is Class.forName("org.postgresql.Driver"); in Table 5 below. Match in source code.

tag name Expression component Class.forName postgresql PosgreSQL Class.forPassword postgresql PosgreSQL Class.forProject postgresql PosgreSQL Class.forCluster postgresql PosgreSQL Class.forNameSpace postgresql PosgreSQL Class.forAccount postgresql PosgreSQL

If the connection function is not detected as a result of the above matching process, the predicted connection function and expression obtained by querying LLM (ChatGPT) for the code for each language are stored in the environment information DB and then again in the analysis data combination stage. Through this, the repeated task of performing connection function matching is performed, and the accurate final analysis results are viewed.

Lastly, the present invention goes through the step of visualizing and querying the component analysis information as a Topology Map through (j) connection function matching. This is analysis information visualization, which is a standardized analysis detected by successfully performing the matching task of the connection function. Information is visualized as a topology map to compare and query the legacy environment and SaaS conversion prediction map (Figure 4).

As described above, the present invention uses cloud conversion analysis technology for source analysis and workload distribution to automatically convert a typical 3-tier (WEB/WAS/DB) application in a legacy environment to a SaaS application in an IaaS/PaaS operating environment. It provides and analyzes source code without the intervention of source developers, and allows application operators to easily switch to a cloud IaaS/PaaS environment even if they have no knowledge or knowledge about the cloud. Application service managers provide stable SaaS in a cloud environment. It is designed to maintain and manage the service, and through agentless information collection, it is possible to collect operating environment information without any load or interference on the running application, and source code analysis provides connection information between the application and the service. In the process of analyzing the source code, analysis information can be collected by tagging the function of the source code and exploring service connection information, allowing maintenance developers or engineers to easily simplify the complex and difficult process of analyzing the source code. It provides convenience to application service managers by analyzing and combining operating environment information and source code data, and matching connection functions to construct and visualize standardized analysis results.

The technical idea of the automatic analysis method for converting a general application into a service-type software application of the present invention is that the same result can be repeatedly performed in practice, and in particular, by implementing the present invention, it can promote technological development and contribute to industrial development, thereby providing protection. It's well worth doing.

Claims (5)

Performing an automatic analysis method on a computing device to convert a general application into a software-as-a-service application,
(a) remotely accessing a general application execution environment using Agentless (SSH; Secure Shell) method;
(b) executing the general application collection script as a System CLI Shell type collection script;
(c) collecting execution environment and service environment information of general applications;
(d) storing execution environment and service environment information of general applications;
(e) a step where the general application downloads the source code from a source management tool (Git), analyzes and stores it;
(f) Tagging the function of the stored source code;
(g) searching for service connection information in the source code of a general application;
(h) analyzing and combining the environment information of the general application and the connection information discovered from the source code into data;
(i) registering a connection function; and
(j) An automatic analysis method for converting a general application into a service-type software application, including the step of visualizing and querying the component analysis information as a topology map by matching the connection function.
In claim 1,
The step (e) where the general application downloads the source code from the source management tool (Git), analyzes and stores it,
Source code analysis of a general application. The purpose of the source code analysis is to substantially verify the connection information between the backend (API) of the general application and the service. An automatic analysis method for converting a general application into a service-type software application. .
In claim 1,
The step (f) of tagging the function of the stored source code is,
An automatic analysis method for converting a general application into a service-type software application, which is characterized by creating a tag for the function defined in the source code and indexing the location of the function so that it can be easily recognized.
In claim 1,
The step (g) of searching for service connection information in the source code of a general application is,
After tagging all functions in the backend (API) source code of the general application where the source code analyzer is stored, search for connection information that called a specific function of the service in the source code of the general application backend (API). An automatic analysis method for converting a general application into a service-type software application.
In claim 1,
The step (h) of analyzing and combining the environment information of the general application and the connection information discovered from the source code into data,
This is a step to build more accurate information by merging various collected and analyzed information. First, the runtime environment information and service environment information of general applications stored in the environment information DB are retrieved, and the source code is retrieved. A service-type general application characterized in that the analyzer generates accurate connection function information by combining the results of searching for connection information that calls a specific function of the service from the source code of the general application backend (API). Automated analysis methods for translation into software applications.