Method and system for installing RPA robot with minimum volume in Linux environment

By compiling RPA robot source code and setting batch scripts in Linux environment, the isolation between RPA robot and framework package directory is achieved, solving the problems of inflexible updates and large size in traditional installation methods, and achieving flexible installation and reducing network transmission effect.

CN118916043APending Publication Date: 2024-11-08YGSOFT INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411023416.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-29
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The traditional RPA robot installation method packages it with the running container, resulting in inflexible updates and maintenance, large size, inconvenient network transmission, and difficulty in adapting to the constraints of server complex networks and hardware resources in the Linux environment.

Method used

By compiling the source code of RPA robot in Linux environment, packaging it into an executable installer, and setting a batch script in the installation package, replacing the default path with the target storage path, realizing the isolation between the RPA robot and the framework package directory, allowing Independent update and installation to reduce network transmission consumption.

Benefits of technology

It realizes flexible RPA robot installation and update, reduces network transmission consumption of installation packages, adapts to the constraints of complex networks and hardware resources, and supports the continuous deployment and maintenance of multiple RPA robots.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916043A_ABST
    Figure CN118916043A_ABST
Patent Text Reader

Abstract

The invention provides a method and system for installing an RPA robot in the Linux environment with the minimum size, and the method comprises the following steps: a Linux end compiles a source code of the RPA robot and packages the source code into an installation program which can be executed by the Linux, and an RPA robot installation package is obtained; the RPA robot installation package comprises a batch processing script, and a default robot path in the batch processing script is replaced with a target robot storage path in the packaging process; the Linux end sends an RPA robot installation package to the outside; the user side obtains an RPA robot installation package and installs a corresponding target RPA robot, the method comprises the steps that a batch processing script is executed to copy the target RPA robot to a target robot storage path, the target robot storage path corresponds to an RPA robot loading catalog, and the RPA robot loading catalog is isolated from a frame package catalog; when the user side starts the RPA service, the storage path of the target robot is appointed as the loading path of the RPA robot. According to the invention, the continuous deployment of a plurality of different RPA robots is realized through the installation of the small-size installation package, and the network transmission consumption of the installation package is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of RPA robots, and in particular to a method and system for minimizing the size of an RPA robot under a Linux environment. Background Art

[0002] RPA (Robotic Process Automation) robots are often used for process automation.

[0003] Traditional continuous integration systems usually package RPA robots and running container applications together for installation. Although this method simplifies the deployment process of RPA robots, it limits the flexibility of updates and maintenance. Every time an RPA robot is updated, the entire application needs to be repackaged, which causes repeated transmission of third-party packages and also brings inconvenience to network transmission due to its large size.

[0004] The Linux installer has an independent installation directory, which makes it difficult to interact with other installed programs. In addition, the RPA robot service in the Linux environment usually requires the construction of an entire construction environment on the Linux system, which is difficult to adapt to the complex network restrictions and hardware resource constraints of the server. Summary of the invention

[0005] The first object of the present invention is to provide a method for minimizing the volume of an RPA robot in a Linux environment, which is flexible to install and has a small installation volume.

[0006] A second object of the present invention is to provide another method for minimizing the volume of an RPA robot installed in a Linux environment, which has flexible installation and small installation volume.

[0007] The third object of the present invention is to provide a system for minimizing the volume of the RPA robot installation in the above-mentioned Linux environment.

[0008] In order to achieve the above-mentioned first purpose, the present invention provides a method for minimizing the volume of an RPA robot in a Linux environment, which includes the following steps: the Linux end compiles the source code of the RPA robot and packages it into a Linux executable installation program to obtain an RPA robot installation package; the RPA robot installation package includes a batch script, and during the packaging process, the default robot path in the batch script is replaced with the target robot storage path; the Linux end sends the RPA robot installation package to the outside; the user end obtains the RPA robot installation package and installs the corresponding target RPA robot, which includes executing the batch script to copy the target RPA robot to the target robot storage path, the target robot storage path corresponds to the RPA robot loading directory, and the RPA robot loading directory is isolated from the framework package directory; when the user end starts the RPA service, it includes specifying the target robot storage path as the RPA robot loading path.

[0009] As can be seen from the above scheme, the present invention sets a batch script in the RPA robot installation package, so that when the user end installs the RPA robot through the RPA robot installation package, the batch script is triggered to copy the installation directory of the corresponding target RPA robot to the target robot storage path, thereby realizing the installation of the target RPA robot. The present invention sets a separate target robot storage path, which corresponds to the RPA robot loading directory, thereby physically separating the RPA robot loading directory from the framework package directory corresponding to the RPA robot running service, and realizing the installation of the RPA robot through a separate RPA robot installation package. There is no need to package the RPA robot and the running container application together for installation. Only the minimized incremental part needs to be updated each time the update is performed, so that multiple different RPA robots can be continuously deployed through a small-volume installation package, and the network transmission consumption of the installation package is reduced.

[0010] A further solution is that the Linux side compiles the source code of the RPA robot and packages it into a Linux executable installation program. When obtaining the RPA robot installation package, it includes: obtaining the compiled first part of the RPA robot source code and the uncompiled second part of the RPA robot source code from the Windows side; wherein, the Windows side compiles the first part of the RPA robot source code in the Jenkins continuous integration tool in the Windows environment and sends it to the Linux side, and sends the second part of the RPA robot source code obtained from the code repository to the Linux side; the Linux server compiles the uncompiled second part of the RPA robot source code according to the script command, and packages it together with the compiled first part of the RPA robot source code to obtain the RPA robot installation package, and then sends the RPA robot installation package to the Windows side.

[0011] It can be seen that it can adapt to the complex network, hardware, and software resource constraints between servers and support the combination of Windows and Linux operating systems.

[0012] A further solution is that the RPA robot installation package is an RPA robot new package or an RPA robot update package.

[0013] It can be seen that a new RPA robot can be installed through the RPA robot new package, and the original RPA robot can be updated through the RPA robot update package.

[0014] A further solution is that when the user end obtains the RPA robot uninstallation instruction, the RPA robot corresponding to the RPA robot uninstallation instruction is removed from the target robot storage path.

[0015] This shows that uninstalling an RPA robot does not affect other RPA robots.

[0016] A further solution is that when the user starts the RPA service, including specifying the target robot storage path as the RPA robot loading path, the target robot storage path is specified as the RPA robot loading path by adding the -Djava.ext.dirs parameter in the Java command.

[0017] A further solution is that, during the packaging process, the Linux side replaces the default robot path in the batch script with the target robot storage path, and also includes replacing the target name in the batch script with the robot name corresponding to the RPA robot installation package; when the user side obtains the RPA robot installation package and installs the corresponding target RPA robot, it also includes copying the target RPA robot to the target robot storage path according to the robot name corresponding to the target RPA robot installation package.

[0018] This shows that you can copy the installation directory of the target RPA robot according to the robot name of the RPA robot to facilitate subsequent maintenance.

[0019] A further solution is that the Linux side replaces the default robot path in the batch script with the target robot storage path by reading the installation configuration file during the packaging process.

[0020] It can be seen that in the process of making the RPA robot installation package, the default storage location of the RPA robot can be determined by reading the installation configuration file when the user installs the RPA robot, and then the storage path of the target robot can be determined.

[0021] In order to achieve the above-mentioned second purpose, the present invention provides a method for minimizing the volume of an RPA robot in a Linux environment, which includes compiling the extensible component plug-in or authorization file required by the RPA robot on the Linux side and packaging it into a Linux executable installation program to obtain an RPA robot extension package; the RPA robot extension package includes a batch script, and during the packaging process, the default framework storage path in the batch script is replaced with the target framework storage path; the Linux side sends the RPA robot extension package to the outside; the user side obtains the RPA robot extension package and installs the RPA robot extension package, which includes executing the batch script to copy the extensible component plug-in or authorization file corresponding to the RPA robot extension package to the target framework storage path, presetting the framework corresponding to the framework package directory, and isolating the RPA robot loading directory from the framework package directory; when the user side starts the RPA service, it includes specifying the target framework storage path as the loading path of the extensible component plug-in or authorization file.

[0022] It can be seen from the above scheme that the present invention can also install or update the extensible component plug-in or authorization file required by the RPA robot by setting a batch script during packaging, so that the user triggers the batch script during installation to install the extensible component plug-in or authorization file into the framework package directory, thereby realizing the minimized incremental update.

[0023] In order to achieve the above-mentioned third purpose, the present invention provides a computer device, a system for minimizing the volume of an RPA robot under a Linux environment, which includes: a Linux end and a user end, the Linux end is used to compile the source code of the RPA robot and package it into a Linux executable installation program to obtain an RPA robot installation package; the RPA robot installation package includes a batch script, and during the packaging process, the default robot path in the batch script is replaced with the target robot storage path; the Linux end sends the RPA robot installation package to the outside; the user end is used to obtain the RPA robot installation package and install the corresponding target RPA robot, including executing the batch script to copy the target RPA robot to the target robot storage path, the target robot storage path corresponds to the RPA robot loading directory, and the RPA robot loading directory is isolated from the framework package directory; when the user end starts the RPA service, it includes specifying the target robot storage path as the RPA robot loading path. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 This is a system block diagram of a system embodiment of the present invention for minimizing the size of an RPA robot for installation in a Linux environment.

[0025] Figure 2 This is a flowchart of the first embodiment of the method for minimizing the volume of an RPA robot under a Linux environment of the present invention.

[0026] Figure 3 This is a schematic diagram of the robot and third-party dependency packages in the operation center of the RPA service on the user side in the first embodiment of the method for minimizing the volume of the RPA robot in the Linux environment of the present invention.

[0027] Figure 4 This is a schematic diagram of installing an RPA robot installation package on a user side in the first embodiment of the method for minimizing the volume of an RPA robot under a Linux environment of the present invention.

[0028] Figure 5 This is another schematic diagram of installing the RPA robot installation package on the user side in an embodiment of the method for installing the RPA robot with minimized volume under the Linux environment of the present invention.

[0029] The present invention is further described below in conjunction with the accompanying drawings and embodiments. DETAILED DESCRIPTION

[0030] The method for minimizing the volume of an RPA robot under a Linux environment of the present invention separates the running service from the RPA robot, thereby realizing flexible and continuous updating of the RPA robot service under a Linux environment.

[0031] System implementation example of minimizing the size of the RPA robot installation in Linux environment:

[0032] See also Figure 1 The installation system of the RPA robot of this embodiment includes a Linux terminal 11, a Windows terminal 12 and a user terminal 13. Data transmission is achieved between the Linux terminal 11 and the Windows terminal 12, and between the Linux terminal 11 and the user terminal 13 through a network connection.

[0033] In this embodiment, the Linux terminal 11 and the Windows terminal 21 cooperate to realize the production of the RPA robot installation package, so that the user terminal 13 can download the produced RPA robot installation package from the Linux terminal 11 and install it.

[0034] First embodiment of the method for minimizing the size of an RPA robot under Linux environment:

[0035] The present invention is implemented based on the installation system of the RPA robot in the above embodiment, see Figure 2 , specifically including the following steps:

[0036] S1: On the Linux side, compile the RPA robot source code and package it into a Linux executable installation program to obtain the RPA robot installation package.

[0037] The constructed RPA robot installation package consists of multiple different parts, corresponding to different source codes, wherein the source code of the first part of the RPA robot installation package needs to be compiled on the Windows side, and the source code of the second part of the RPA robot installation package needs to be compiled on the Linux side. In this embodiment, the Jenkins continuous integration tool is deployed on the Windows side. The developer builds a part of the application on the Windows side to obtain the compiled source code of the first part of the RPA robot, and obtains the source code of another part of the application from the git code repository, that is, the uncompiled source code of the second part of the RPA robot. The compiled source code of the first part of the RPA robot and the uncompiled source code of the second part of the RPA robot are sent to the Linux side through ssh, and then the script command is transmitted through ssh to control the Linux side for compilation and packaging.

[0038] The Linux side compiles the uncompiled source code of the second part of the RPA robot according to the script command, and packages the compiled source code of the first part of the RPA robot together to obtain the RPA robot installation package.

[0039] A batch script is set in the RPA robot installation package. The batch script is used to copy the RPA robot to the target robot storage path when the RPA robot installation package is executed. In the process of packaging the RPA robot installation package, the Linux end replaces the target name in the batch script with the robot name corresponding to the RPA robot installation package by reading the data in the installation configuration file in a data-driven manner, and determines the target robot storage path to which the RPA robot needs to be copied based on the installation default path where the RPA service on the user side is running, and replaces the default robot path in the batch script with the target robot storage path.

[0040] The target robot storage path is the loading path of the RPA robot inferred and confirmed according to the installation default path corresponding to the RPA service running on the user side. When the user side starts the RPA service, the RPA robot is loaded from the target robot storage path, thereby distinguishing the running service of the RPA robot. Figure 3 In the operation center 20 of the RPA service on the user side, multiple RPA robots including the newly installed target RPA robot 205 are separated from the third-party dependency package 211. According to the dependency minimization strategy, this can physically separate the operating environment of the RPA service (corresponding to the third-party dependency package 211) from the storage directory of the RPA robot (corresponding to multiple RPA robots), reuse the third-party dependency package 211, and increase the security and stability of the system.

[0041] S2: The Linux end sends the RPA robot installation package to the outside.

[0042] The Linux server sends the RPA robot installation package back to the Windows or user side through FTP (File Transfer Protocol).

[0043] S3: The user obtains the RPA robot installation package and installs the corresponding target RPA robot.

[0044] After the RPA robot installation package is available, users can download the independent RPA robot installation packages. In the visualized Linux operating system, such as the Tongxin uos system, the RPA robot installation package can be installed by double-clicking. At this time, the batch script in the RPA robot installation package will be triggered, and the corresponding target RPA robot will be automatically copied to the target robot storage path indicated in the batch script according to the corresponding robot name, and the configuration will be completed, so that the target RPA robot can be correctly loaded when the RPA service is started.

[0045] See also Figure 4 and Figure 5When installing through the RPA robot installation package, the Linux operating system 30 on the user side copies the robot installation directory 302 corresponding to the RPA robot installation package 901 to the robot loading directory 312 in the installation directory 301 of the operation center of the RPA service through a batch script. The robot loading directory 312 corresponds to the storage path of the target robot. The robot loading directory 312 is isolated from the framework package directory 311. The framework package directory 311 is used to implement the operation service of the RPA robot, corresponding to the third-party dependency package.

[0046] S4: When the user starts the RPA service, the target robot storage path is specified as the loading path of the RPA robot.

[0047] When the user starts the RPA service, add the -Djava.ext.dirs parameter in the Java command to specify the loading path of the RPA robot as the target robot storage path.

[0048] When the user receives an RPA robot uninstallation instruction, the RPA robot corresponding to the RPA robot uninstallation instruction is removed from the target robot storage path to achieve uninstallation. Other RPA robots in the target robot storage path will not be affected, and the framework package directory will not be affected.

[0049] The RPA robot installation package of this embodiment is an RPA robot new creation package, which realizes the creation of a new RPA robot on a Linux server. In different embodiments, the RPA robot installation package can also be an installation package RPA robot update package.

[0050] In different embodiments, a Jenkins continuous integration tool may also be deployed on the Linux side, so as to obtain the uncompiled source code of the second part of the RPA robot directly from the git code repository on the Linux side.

[0051] In summary, the present invention realizes the installation of the RPA robot through a separate RPA robot installation package. There is no need to package the RPA robot and the running container application together for installation. Only the minimized incremental part needs to be updated each time. The continuous deployment of multiple different RPA robots can be achieved through a small-volume installation package, and the network transmission consumption of the installation package is reduced.

[0052] Second embodiment of the method for minimizing the size of an RPA robot under Linux environment:

[0053] In this embodiment, the extensible component plug-ins or authorization files required by the RPA robot in the framework package directory are installed. The specific method can be achieved by the same installation method as described above to achieve minimal volume installation. At this time, the extensible component plug-ins or authorization files required by the RPA robot can be copied to the target framework storage path through a batch script. The target framework storage path corresponds to the framework package directory, and only the minimized incremental part can be updated.

Claims

1. A method for minimizing the size of an RPA robot in a Linux environment, characterized in that: The following steps are involved: The Linux end compiles the source code of the RPA robot and packages it into a Linux executable installation program to obtain an RPA robot installation package; the RPA robot installation package includes a batch processing script, and during the packaging process, the default robot path in the batch processing script is replaced with the target robot storage path; The Linux end sends the RPA robot installation package to the outside; The user end obtains the RPA robot installation package and installs the corresponding target RPA robot, including executing the batch script to copy the target RPA robot to the target robot storage path, the target robot storage path corresponds to the RPA robot loading directory, and the RPA robot loading directory is isolated from the framework package directory; When the user terminal starts the RPA service, it includes specifying the target robot storage path as the RPA robot loading path.

2. The method for minimizing the size of an RPA robot in a Linux environment according to claim 1, wherein: The following steps are involved: The Linux end compiles the source code of the RPA robot and packages it into the Linux executable installation program to obtain the RPA robot installation package, including: Obtaining the compiled source code of the first part of the RPA robot and the uncompiled source code of the second part of the RPA robot from the Windows end; wherein the Windows end compiles the source code of the first part of the RPA robot in the Jenkins continuous integration tool under the Windows environment and sends it to the Linux end, and sends the source code of the second part of the RPA robot obtained from the code repository to the Linux end; The Linux server compiles the uncompiled second part of the source code of the RPA robot according to the script command, and packages it together with the compiled first part of the source code of the RPA robot to obtain the RPA robot installation package, and then sends the RPA robot installation package to the Windows end.

3. The method for minimizing the size of an RPA robot in a Linux environment according to claim 2, wherein: The following steps are involved: The RPA robot installation package is an RPA robot new installation package or an RPA robot update package.

4. The method for minimizing the size of an RPA robot in a Linux environment according to claim 3, characterized in that: The following steps are involved: When the user terminal obtains the RPA robot uninstallation instruction, the RPA robot corresponding to the RPA robot uninstallation instruction is removed from the target robot storage path.

5. The method for minimizing the size of an RPA robot in a Linux environment according to claim 4, characterized in that: The following steps are involved: When the user terminal starts the RPA service, including specifying the target robot storage path as the RPA robot loading path, the target robot storage path is specified as the RPA robot loading path by adding the -Djava.ext.dirs parameter in the Java command.

6. The method for minimizing the size of an RPA robot in a Linux environment according to any one of claims 1 to 5, characterized in that: The following steps are involved: The Linux end replaces the default robot path in the batch script with the target robot storage path during the packaging process, and also replaces the target name in the batch script with the robot name corresponding to the RPA robot installation package; When the user end obtains the RPA robot installation package and installs the corresponding target RPA robot, it also includes copying the target RPA robot to the target robot storage path according to the robot name corresponding to the target RPA robot installation package.

7. The method for minimizing the size of an RPA robot in a Linux environment according to any one of claim 6, wherein: The following steps are involved: During the packaging process, the Linux end replaces the default robot path in the batch script with the target robot storage path by reading the installation configuration file.

8. A method for minimizing the size of an RPA robot in a Linux environment, characterized in that: The following steps are involved: The Linux end compiles the extensibility component plug-in or authorization file required by the RPA robot and packages it into a Linux executable installation program to obtain an RPA robot extension package; the RPA robot extension package includes a batch script, and during the packaging process, the default framework storage path in the batch script is replaced with the target framework storage path; The Linux end sends the RPA robot expansion package to the outside; The user end obtains the RPA robot extension package and installs the RPA robot extension package, which includes executing the batch script to copy the extensibility component plug-in or authorization file corresponding to the RPA robot extension package to the target framework storage path, the preset framework corresponds to the framework package directory, and the RPA robot loading directory is isolated from the framework package directory; When the user terminal starts the RPA service, it includes specifying the target framework storage path as the loading path of the extensibility component plug-in or the authorization file.

9. A system for installing RPA robots in a Linux environment with minimal volume, characterized in that ,include: A Linux end and a user end, wherein the Linux end is used to compile the source code of the RPA robot and package it into a Linux executable installation program to obtain an RPA robot installation package; the RPA robot installation package includes a batch script, and during the packaging process, the default robot path in the batch script is replaced with the target robot storage path; The Linux end sends the RPA robot installation package to the outside; The user end is used to obtain the RPA robot installation package and install the corresponding target RPA robot, including executing the batch script to copy the target RPA robot to the target robot storage path, the target robot storage path corresponds to the RPA robot loading directory, and the RPA robot loading directory is isolated from the framework package directory; When the user terminal starts the RPA service, it includes specifying the target robot storage path as the RPA robot loading path.