CN117608601A - ERP software application program deployment method, device, equipment and medium - Google Patents

Abstract

The embodiment of the specification discloses a method, a device, equipment and a medium for deploying ERP software application programs, comprising the following steps: generating a dock image file according to the appointed ERP software application program; uploading the dock image file to a harbor image warehouse; logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse; executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

Description

ERP software application program deployment method, device, equipment and medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a medium for deploying an ERP software application.

Background

With the continuous development of cloud computing technology, enterprises increasingly rely on public cloud services in the aspect of informatization construction. Enterprise Resource Planning (ERP) software has become a trend as a critical application system for its deployment on public clouds. However, the conventional ERP software deployment method has the problems of long deployment period, low efficiency, poor maintainability and the like, and is difficult to meet the requirement of quick online of enterprises. In addition, due to the multi-tenant characteristic, when the ERP software is deployed, the enterprise needs to consider the isolation problem of data and configuration so as to ensure the safety among tenants.

In view of the above problems, most of the existing solutions are based on the deployment of ERP software by virtualization technology or containerization technology. The virtualization technology can realize dynamic allocation and isolation of resources, but the creation, deployment and maintenance costs of the virtual machine images are high, and the performance loss is high.

Therefore, there is a need for an ERP software application deployment method, which can meet the requirements of short online period and ensuring the availability of the system.

Disclosure of Invention

One or more embodiments of the present disclosure provide a method, an apparatus, a device, and a medium for deploying an ERP software application, which are used to solve the technical problem set forth in the background art.

One or more embodiments of the present disclosure adopt the following technical solutions:

one or more embodiments of the present disclosure provide a method for deploying an ERP software application, including:

generating a dock image file according to the appointed ERP software application program;

uploading the dock image file to a harbor image warehouse;

logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse;

executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

One or more embodiments of the present specification provide an ERP software application deployment apparatus, the apparatus comprising:

the generation unit generates a dock image file according to the appointed ERP software application program;

an uploading unit for uploading the dock image file to a harbor image warehouse;

the downloading unit logs in the harbor mirror image warehouse in the running environment of the appointed ERP software application program, and downloads the dock mirror image to the running environment in the harbor mirror image warehouse;

and the deployment unit executes the dock mirror image in the running environment and starts the appointed ERP software application program so as to complete the deployment of the appointed ERP software application program.

One or more embodiments of the present disclosure provide an ERP software application deployment apparatus, including:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

generating a dock image file according to the appointed ERP software application program;

uploading the dock image file to a harbor image warehouse;

logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse;

executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

One or more embodiments of the present description provide a non-volatile computer storage medium storing computer-executable instructions that, when executed by a computer, enable:

generating a dock image file according to the appointed ERP software application program;

uploading the dock image file to a harbor image warehouse;

logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse;

executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

The above-mentioned at least one technical scheme that this description embodiment adopted can reach following beneficial effect:

according to the embodiment of the specification, the quick deployment of the ERP software application program can be realized by using the Docker image and the Harbor image warehouse. Compared with the traditional deployment mode, the method has the advantages of short deployment period and high efficiency, and is beneficial to improving the informatization construction efficiency of enterprises.

According to the embodiment of the specification, the version management and updating of the ERP software application program can be conveniently realized by using the Docker image and the Harbor image warehouse, the enterprise can adjust the deployed image version at any time according to the requirements, and the flexibility and maintainability of the system are improved.

The embodiment of the specification can carry out security management and access control on the Docker mirror by using the Harbor mirror warehouse. In the deployment process, the enterprise can isolate data and configuration according to the needs of tenants, so that the safety among the tenants is ensured.

Compared with the traditional deployment mode, the Docker mirror and the Harbor mirror warehouse are used in the embodiment of the invention, so that the cost of the enterprise in terms of hardware, maintenance and management can be reduced. Meanwhile, the Docker mirror image has higher performance, so that the operation efficiency of enterprises can be improved.

According to the embodiment of the specification, the operation of the enterprise when the ERP software application program is deployed is simplified, the efficiency of IT personnel of the enterprise is improved, and the error rate in the deployment process is reduced.

Drawings

In order to more clearly illustrate the embodiments of the present description or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some of the embodiments described in the present description, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:

FIG. 1 is a flow diagram of an ERP software application deployment method provided by one or more embodiments of the present disclosure;

FIG. 2 is a flow diagram of a method for dock container deployment of a multi-tenant ERP software product provided by one or more embodiments of the present disclosure;

FIG. 3 is a schematic structural diagram of an ERP software application deployment device according to one or more embodiments of the present disclosure;

FIG. 4 is a schematic structural diagram of an ERP software application deployment device according to one or more embodiments of the present disclosure.

Detailed Description

The embodiment of the specification provides a method, a device, equipment and a medium for deploying ERP software application programs.

In order to make the technical solutions in the present specification better understood by those skilled in the art, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present disclosure.

FIG. 1 is a flow diagram of an ERP software application deployment method provided by one or more embodiments of the present disclosure, which may be performed by an ERP software application deployment system. Some input parameters or intermediate results in the flow allow for manual intervention adjustments to help improve accuracy.

The method flow steps of the embodiment of the present specification are as follows:

s102, generating a dock image file according to the appointed ERP software application program.

In the embodiment of the present specification, the step of generating the dock image file may be implemented as follows:

determining ERP software application program: there is a need to specify the name, version, and required dependencies of the ERP software application to be deployed.

Acquiring an ERP software application program: the installation package or source code for the ERP software application is downloaded from an official website or other reliable source.

When the docker image file is generated, the running catalog and related environment variables can be determined; copying the service directory in the file deployment mode into a container; mapping the corresponding starting port of the appointed ERP software application program; and generating the docker image file through the specific starting script of the appointed ERP software application program.

Determining the running catalog and related environment variables: the required operating catalog and environment variables may be determined based on official documents or actual operating requirements of the ERP software application.

Copying the service directory in the file deployment mode into a container: service directories (e.g., HTML, CSS, javaScript files of a Web application, etc.) in a file deployment mode required by an ERP software application may be copied to specified directories in a container.

Mapping the corresponding starting port of the appointed ERP software application program: the required boot ports may be determined based on official documents or actual operating requirements of the ERP software application and mapped to the outside of the container.

Generating a dock image file by specifying a specific start script of the ERP software application program: a specific startup script may be written for launching the ERP software application and associating it with the docker container. The startup script may include the following:

preparing a running environment: to ensure that the ERP software application operates properly in the container, a proper operating environment needs to be configured, i.e. a proper operating environment is configured in the docker image file, including an operating system, JJDK, maven, nodejs, redis, a database, and the like.

Installing and configuring ERP software applications: in the ready operating environment, ERP software applications are installed and configured, which may be installed and configured with reference to official documents or related courses.

Determining data and configuration isolation: and according to the multi-tenant requirements, data and configuration isolation is carried out on the ERP software application program. Methods such as database splitting, table splitting, profile isolation and the like can be adopted.

Writing dockerfile: a dockerfile is written to describe how to construct the docker mirror. dock rf lie should include the following:

a. base mirror image: operating system images, such as Ubuntu, centOS, etc., are designated for use.

b. Installation dependence: install JDK, maven, nodejs, redis, etc.

c. Copying a file: the installation catalog and configuration files of the ERP software application are copied to a specified path in the container.

d. Setting environment variables: setting environment variables applicable to ERP software applications.

e. Exposing ports: and mapping an external service port of the ERP software application program.

f. Running ERP software application program: the ERP software application is automatically run at the start-up of the container.

Constructing a dock mirror image: the docker build command may be used to build a docker mirror from dockerfile.

Testing dock mirror: and a dock run command can be used to run the built dock mirror image, so that the normal running of the ERP software application program is ensured.

Optimizing and adjusting: and optimizing and adjusting the dock mirror image according to the test result to improve the performance and stability.

Through the implementation steps, a docker image file suitable for a specified ERP software application can be generated. The image file can be deployed on public cloud, and quick, efficient and reliable ERP software application deployment is realized.

S104, uploading the docker image file to a harbor image warehouse.

In the embodiment of the present specification, the implementation steps of uploading the dock image file to the Harbor image repository are as follows:

installing and configuring Harbor: and installing the Harbor on the server and completing corresponding configuration such as users, rights, storage and the like. The installation and configuration process of the Harbor may refer to official documents or other courses.

Logging in Harbor: a user with corresponding rights is used to log in to a Harbor, such as an administrator or a user with uploading mirror rights.

Creating a warehouse: a warehouse for storing the dock images is created in the Harbor, and the access authority, the storage space and the like of the warehouse can be set according to the requirements.

Preparing a docker image file: and placing the constructed dock image file in a local server or a storage service on a public cloud so as to upload the file to the Harbor.

Logging in Harbor: a user with the right to upload the image is used to log in to the Harbor.

Uploading a docker mirror image: the prepared dock image file is uploaded to a designated repository using the upload function provided by the Harbor. Related metadata information such as mirror names, labels, descriptions and the like need to be filled in the uploading process.

Checking an uploading result: after the uploading is completed, checking whether the uploaded dock mirror image is successful or not. The uploaded mirror list can be checked through the interface of the Harbor or the API interface to confirm whether the metadata information of the mirror is correct.

Issuing a mirror image: if the uploaded dock mirror image needs to be published for other users to use, corresponding publishing rules can be set in the Harbor, and the mirror image is pushed to other mirror image warehouses or container registries.

Through the implementation steps, the dock image file can be uploaded to the Harbor image warehouse, so that the management and the use are convenient. Meanwhile, the Harbor also provides functions of version management, security audit and the like of the mirror image, and ensures the security and reliability of the docker mirror image.

Before the dock image file is uploaded to the harbor image warehouse, different ERP software programs can be classified and stored through hierarchical authorization and user management of the harbor image warehouse.

Further, the harbor image warehouse may be used to implement version management of the dock image file, and perform integrity test on the dock image file.

For the above, the embodiment of the present specification may include the following specific steps:

preparation:

a Harbor mirror warehouse is installed and configured.

The Docker engine is installed and configured.

Creating Harbor users and roles:

log into the Harbor management interface.

Different users are created, and different roles and authorities are allocated according to actual demands.

For example, different roles of administrators, general users, etc. may be created.

Configuring hierarchical authorization:

and distributing corresponding rights for different roles in the Harbor management interface.

For example, an administrator may have all the rights, and an average user may only view or download images of his own rights.

Classification save ERP software program:

different ERP software programs are packaged into a Docker mirror image.

A classification (Tag) is assigned to each Docker image.

The Docker images are uploaded to a Harbor image repository and stored under the corresponding classifications.

Version management:

the Harbor image warehouse supports version management of the Docker image by default.

When there is a new version of the requirements, a new Tag (Tag) may be created in the Harbor image repository and the new version of the Docker image uploaded to the Tag.

Integrity test:

the integrity test is performed on the Docker image file using commands or APIs provided by the Harbor image repository.

For example, the Harbor's Harbor aspect command may be used to check the details of the image.

And processing the detected abnormal mirror image in time to ensure the integrity and reliability of the mirror image file in the mirror image warehouse.

Uploading the Docker image file to a Harbor image warehouse:

the local Docker image is uploaded to the Harbor image repository using the Docker CLI or API.

At the time of uploading, classification (Repository), tag (Tag) and authority (Harbor user and role) can be specified for the mirror image as required.

Continuously monitoring and maintaining:

and performing operations such as version updating, integrity testing and the like on the Docker images in the Harbor image warehouse at regular intervals.

And adjusting the user and role rights of the Harbor mirror image warehouse according to actual requirements.

Through the implementation steps, the classified storage, version management and integrity test of the ERP software program can be realized, and the safety and reliability of the Docker image file in the Harbor image warehouse are ensured.

S106, logging in the harbor mirror image warehouse in the running environment of the appointed ERP software application program, and downloading the dock mirror image to the running environment in the harbor mirror image warehouse.

In the embodiment of the present specification, the implementation steps for downloading the dock image to the running environment are as follows:

downloading the Docker image to the running environment: the selected Docker image is downloaded from the Harbor image repository to the runtime environment using the Docker CLI or API.

Download command example: dock pull < restore >: tag >, where < restore > is mirror silo name and < tag > is mirror version tag.

Waiting for the downloading of the Docker image to be completed.

Running a Docker mirror: in the running environment, the Docker container is started using the Docker CLI or API, using the downloaded image.

Launch container command example: dock run-d < image_id >, where < image_id > is the ID of the dock image.

And confirming that the Docker container is started normally, and starting to run the ERP software application program.

And after the dock image is downloaded to the running environment in the harbor image warehouse, the integrity of the dock image can be detected in a preset mode. The predetermined pattern may be MD5.

Integrity detection may be performed by the following steps:

obtaining an MD5 value of a Docker mirror image: in the running environment, the MD5 value of the Docker image is obtained using the Docker CLI or API.

Example get MD5 value command: dock aspect-format= '{ {. Id }' < image_id >, where < image_id > is the Id of the dock mirror.

Presetting an MD5 value: one or more MD5 values are preset according to actual requirements and serve as reference values for detecting the integrity of the Docker mirror image. The pre-set MD5 values may be stored in a configuration file, environmental variable, or other reliable data store.

Integrity test is performed: integrity checking is performed on the Docker image in the operating environment using Docker CLI or API. Detection command example: dock aspect-format= '{ {. Id }' < image_id >, where < image_id > is the Id of the dock mirror. Comparing the actually calculated MD5 value with a preset MD5 value, and judging whether the Docker mirror image is complete or not.

Handling abnormal conditions: if the Docker mirror image is found to be incomplete, timely processing abnormal conditions. Such as re-downloading the image, cleaning the damaged image, etc.

S108, executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

In the embodiment of the present disclosure, the implementation steps for launching a specified ERP software application are as follows:

executing a Docker mirror image: in the running environment, the Docker container is started using the Docker CLI, and the downloaded image is used.

Launch container command example: dock run-d < image_id >, where < image_id > is the ID of the dock image.

Starting a specified ERP software application: in the Docker container, ERP software applications are launched using corresponding commands or scripts. For example, the application may be started using a command such as./ start. Sh or npm start.

Confirming that the ERP software application program runs normally: and checking the running state of the application program to ensure the normal running of the application program. For example, the confirmation may be performed by viewing a log, monitoring system indicators, or the like.

Work after deployment is completed: and carrying out necessary tests to ensure that the ERP software application program functions normally. Relevant configuration files are deployed, such as security policies, network configuration, etc. The running state of the ERP software application program is monitored regularly, and stable running is ensured.

Through the implementation steps, the Docker mirror image can be executed in the running environment, and the appointed ERP software application program is started to finish deployment. Based on the method, the Docker mirror image can be updated, monitored and managed according to actual requirements.

Technical problems that this embodiment of the present specification can solve: in the deployment of the multi-tenant application program in a dock container environment in a public cloud mode, the deployment of a new environment can be rapidly and accurately completed, and rapid delivery is realized.

The greatest advantage of the embodiments of the present specification is:

firstly, the rapid deployment of products in a dock environment can be perfectly ensured, so that the situation of misoperation is avoided;

secondly, the program version is stored based on the internal class of the program file, and the method does not depend on the attributes such as the modification date of the file, so that the method has high reliability;

the embodiment of the specification is a scheme for solving the problem of docker containerization deployment in a multi-tenant public cloud environment, and fig. 2 is a flow diagram of a method for docker containerization deployment of a multi-tenant ERP software product, which can be divided into four parts, docker base mirror image production, mirror image warehouse uploading, application program mirror image downloading and application program mirror image deployment operation.

Docker base mirror image production is based on the ERP software application program of our department, writes Docker file and comprises the following related components as a running base:

1. JDK, based on openjdk image, requires JDK environment to be greater than or equal to version of JDK8, where JDK8 version requires greater than 8u221.

2. Maven package, required version is Maven 3.6.3+

3. Nodejs, required version is Node 8.0+

4. Redis, requiring server v= 3.2.12+

5. Databases, versions postgresql10+, SQL Server12+, oracle11.2+, dream 7.6+, highgo5.4.6, my SQL8.0.19+, oscar7.0.8+, kingbaseV8R6, DB210.5

The image warehouse uploading is a container warehouse which is used for storing the dock images, the image warehouse is used as a harbor image warehouse in the embodiment of the specification, and the manufactured dock images are uploaded to the harbor image warehouse. In the link, through hierarchical authorization of the harbor mirror image warehouse, user management stores different software programs in a classified mode, version management of the dock mirror image is achieved through the harbor mirror image warehouse, and integrity test is conducted on the uploaded dock mirror image. And monitoring the dock mirror image in an MD5 comparison peer-to-peer mode.

The application program image downloading is to log in a harbor image warehouse in the environment where the software application program needs to be deployed, download the needed dock image from the image warehouse, and detect through MD5 to ensure the program integrity.

And (3) carrying out mirror image deployment operation on the application program, and writing operation script deployment operation according to the starting characteristics of the ERP product.

The key point of the embodiment of the specification is that the Docker base mirror image is manufactured, wherein the writing of the Dockerfile file is particularly important, and the following specific writing requirements of the Dockerfile file are as follows:

1. JAVA environment, requiring JDK environment to be greater than or equal to JDK8 version based on openjdk image, wherein JDK8 version requires greater than 8u221.

2. Specifying the current running directory of the docker container, for example: home/app

3. ERP software application program adopts the latest version GSCloud6.0 of ERP product of I department as the basis to install package.

4. And installing fonts and related environment variables, selecting default fonts for installing the system according to the running operating system, and configuring the environment variables.

5. Copying the service directory in the file deployment mode into a container.

6. Port mapping, which maps the application software to the corresponding boot port 5200.

7. And starting the script, namely using the special starting script of the ERP software of the me, and designating the script which needs to be executed after starting from a dock entry.

The method based on the embodiments of the present specification has the following points:

1. the deployment architecture is flexible, and can support the deployment of multiple cloud mode architecture schemes such as public cloud, private cloud, hybrid cloud and the like;

2. the program has simple structure and strong expandability, has stronger compatibility for operating systems of different versions, and can be rapidly deployed.

3. The embodiment of the specification provides a deployment method of a multi-tenant ERP software product, which is simple and realizable in deployment mode, has complete independent autonomy and has good support for code primordia;

effects of the embodiments of the present specification: for realizing the multi-tenant ERP software product, the newly added tenant only needs to download the dock application software container in a new operating system or public cloud, private cloud and other environments, and then operates the container through an operation script. The method is simple and convenient to operate, low in fault tolerance rate and capable of greatly guaranteeing the availability of the system and facilitating software delivery, and the deployment time is about 5 hours.

FIG. 3 is a schematic structural diagram of an ERP software application deployment device according to one or more embodiments of the present disclosure, where the device includes:

the generating unit 302 generates a dock image file according to the appointed ERP software application program;

an uploading unit 304, configured to upload the dock image file to a harbor image repository;

a downloading unit 306, configured to log in the harbor image repository in the running environment of the specified ERP software application, and download the dock image to the running environment in the harbor image repository;

and a deployment unit 308, executing the dock mirror image in the running environment, and starting the specified ERP software application program to complete the deployment of the specified ERP software application program.

FIG. 4 is a schematic structural diagram of an ERP software application deployment device according to one or more embodiments of the present disclosure, including:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

generating a dock image file according to the appointed ERP software application program;

uploading the dock image file to a harbor image warehouse;

logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse;

executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

One or more embodiments of the present description provide a non-volatile computer storage medium storing computer-executable instructions that, when executed by a computer, enable:

generating a dock image file according to the appointed ERP software application program;

uploading the dock image file to a harbor image warehouse;

logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse;

executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for apparatus, devices, non-volatile computer storage medium embodiments, the description is relatively simple, as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The foregoing is merely one or more embodiments of the present description and is not intended to limit the present description. Various modifications and alterations to one or more embodiments of this description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of one or more embodiments of the present description, is intended to be included within the scope of the claims of the present description.

Claims (10)

1. A method for deploying an ERP software application, the method comprising:

generating a dock image file according to the appointed ERP software application program;

uploading the dock image file to a harbor image warehouse;

logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse;

executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

2. The method of claim 1, wherein the generating a dock image file comprises:

determining a running catalog and related environment variables

Copying the service directory in the file deployment mode into a container;

mapping the corresponding starting port of the appointed ERP software application program;

and generating the docker image file through the specific starting script of the appointed ERP software application program.

3. The method of claim 1, wherein the dock image file comprises JDK, maven, nodejs, redis and a database.

4. The method of claim 1, wherein before uploading the dock image file to a harbor image repository, the method further comprises:

and classifying and storing different ERP software programs through hierarchical authorization and user management of the harbor mirror image warehouse.

5. The method of claim 1, wherein the harbor image repository is configured to implement version management of the dock image file and perform integrity testing on the dock image file.

6. The method of claim 1, wherein after the downloading the dock image to the operating environment in the harbor image repository, the method further comprises:

and carrying out integrity detection on the docker mirror image in a preset mode.

7. The method of claim 6, wherein the predetermined pattern is MD5.

8. An ERP software application deployment apparatus, the apparatus comprising:

the generation unit generates a dock image file according to the appointed ERP software application program;

an uploading unit for uploading the dock image file to a harbor image warehouse;

the downloading unit logs in the harbor mirror image warehouse in the running environment of the appointed ERP software application program, and downloads the dock mirror image to the running environment in the harbor mirror image warehouse;

and the deployment unit executes the dock mirror image in the running environment and starts the appointed ERP software application program so as to complete the deployment of the appointed ERP software application program.

9. An ERP software application deployment apparatus, comprising:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

generating a dock image file according to the appointed ERP software application program;

uploading the dock image file to a harbor image warehouse;

logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse;

executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.

10. A non-transitory computer storage medium storing computer executable instructions that when executed by a computer enable:

generating a dock image file according to the appointed ERP software application program;

uploading the dock image file to a harbor image warehouse;

logging in the harbor image warehouse in the running environment of the appointed ERP software application program, and downloading the dock image to the running environment in the harbor image warehouse;

executing the dock mirror image in the running environment, and starting the appointed ERP software application program to finish the deployment of the appointed ERP software application program.