WO2020000811A1 - 应用组件部署方法、装置及计算机存储介质 - Google Patents
应用组件部署方法、装置及计算机存储介质 Download PDFInfo
- Publication number
- WO2020000811A1 WO2020000811A1 PCT/CN2018/111669 CN2018111669W WO2020000811A1 WO 2020000811 A1 WO2020000811 A1 WO 2020000811A1 CN 2018111669 W CN2018111669 W CN 2018111669W WO 2020000811 A1 WO2020000811 A1 WO 2020000811A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- deployment
- action
- application
- deployed
- application component
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Definitions
- the present application relates to the field of application development technology, and in particular, to a method, device, and computer storage medium for deploying application components.
- application components are usually manually deployed by technicians.
- application component deployment requires a lot of configuration information.
- different teams may collaborate to develop different application components.
- Each application component has a different development language and development environment, and application component deployment methods are also different. It will be different, and with the rise of the microservices framework, an application computer-readable instruction to the bottom layer may need to deploy dozens or even hundreds of application components.
- Manually deploying application components will make it impossible to control the pace of application component architecture deployment, resulting in Application component deployment is slow, and it is easy to increase the errors and risks of application component deployment, which leads to lower efficiency and accuracy of application component deployment.
- This application provides an application component deployment method, device, and computer storage medium, which are mainly capable of automatically completing application component deployment and standardizing the application component deployment process, accelerating the deployment speed, controlling the deployment rhythm, and reducing the complexity of deployment. , Reduce manual operation errors and risks, which can improve the efficiency and accuracy of application component deployment.
- a method for deploying an application component including:
- an application component deployment device including:
- a receiving unit configured to receive an application component deployment instruction, where the deployment instruction includes an application component identifier of an application component to be deployed;
- An obtaining unit configured to obtain a to-be-deployed file and a deployment configuration file of the application component according to the application component identifier
- a parsing unit configured to parse the deployment configuration file to obtain a standard deployment execution action of the application component and a deployment path corresponding to the file to be deployed;
- a deployment unit configured to perform an application stop action, a pre-deployment action, a post-deployment action, an application start action, and an application verification action in the standard deployment execution action, and deploy the to-be-deployed file to the deployment path according to the deployment path
- the server to be deployed to complete the application component deployment.
- a computer non-volatile readable storage medium on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor, the following steps are implemented:
- the deployment instruction includes an application component identification of an application component to be deployed; obtaining a to-be-deployed file and a deployment configuration file of the application component according to the application component identification; and parsing the deployment configuration file to obtain The standard deployment execution action of the application component and the deployment path corresponding to the file to be deployed; executing an application stop action, a pre-deployment action, a post-deployment action, an application start action, and an application verification action in the standard deployment execution action, and Deploying the to-be-deployed file to the to-be-deployed server according to the deployment path to complete the application component deployment.
- an application component deployment apparatus including a memory, a processor, and computer-readable instructions stored on the memory and executable on the processor, where the processor executes the computer-readable Implement the following steps when instructing:
- the deployment instruction includes an application component identification of an application component to be deployed; obtaining a to-be-deployed file and a deployment configuration file of the application component according to the application component identification; and parsing the deployment configuration file to obtain The standard deployment execution action of the application component and the deployment path corresponding to the file to be deployed; executing an application stop action, a pre-deployment action, a post-deployment action, an application start action, and an application verification action in the standard deployment execution action, and Deploying the to-be-deployed file to the to-be-deployed server according to the deployment path to complete the application component deployment.
- the deployment instructions include the application component identification of the application component to be deployed. ; Can obtain the application component's to-be-deployed file and deployment configuration file according to the application component identifier, and at the same time, can parse the deployment configuration file to obtain the standard deployment execution action of the application component and the standby The deployment path corresponding to the deployment file; execute the application stop action, pre-deployment action, post-deployment action, application start action, and application verification action in the standard deployment execution action, and deploy the to-be-deployed file to the deployment path to In the to-be-deployed server, the application component deployment is completed, so that application component deployment can be completed automatically and the application component deployment process can be standardized, speeding up deployment, controlling deployment rhythm, reducing deployment complexity, and reducing manual Operational errors and risks, And can improve the efficiency and accuracy of application components deployed.
- FIG. 1 shows a flowchart of an application component deployment method provided by an embodiment of the present application
- FIG. 2 shows a flowchart of another method for deploying application components according to an embodiment of the present application
- FIG. 3 is a schematic structural diagram of an application component deployment device according to an embodiment of the present application.
- FIG. 4 is a schematic structural diagram of another application component deployment apparatus according to an embodiment of the present application.
- FIG. 5 is a schematic structural diagram of a computer device according to an embodiment of the present application.
- an embodiment of the present application provides an application component deployment method.
- the method includes: 101. Receive an application component deployment instruction.
- the deployment instruction includes an application component identifier of an application component to be deployed.
- the application component identifier may be a name of the application component or a unique encoding of the application component, which is not limited in the embodiment of the present application.
- the deployment instruction may be received by the execution subject application component deployment device when a technician clicks or triggers a deployment button or key.
- the deployment configuration file may be prepared in advance by a technician for the application component, and the deployment configuration file may define content describing two parts: a standard deployment execution action of the application component and the to-be-deployed file. The corresponding deployment path. Different application components correspond to different deployment configuration files, but different deployment configuration files describe the contents of the previous two parts.
- the standard deployment execution actions of different application components are the same. Each execution action in the standard deployment execution action can be performed by several Each command may be represented by a command line execution statement.
- the command line execution statement may be a shell execution statement or other execution statements. Each command under each execution action may be determined according to the actual situation of the application component.
- the standard deployment execution actions can be defined with five execution actions: application stop action, pre-deployment action, post-deployment action, application start action, and application verification action, that is, for different application components, the deployment configuration file can all describe the above five Perform the action.
- the deployment path may be a path where the file to be deployed is deployed and installed on a server to be deployed.
- the deployment configuration file may be written in a json text format, or may be written in a yaml or xml text format, and the embodiment of the present application is not limited thereto.
- the application stop action can be: “app_stop action”
- the pre-deployment action can be: “before_install action”
- the post-deployment action can be: “After_install action”
- the application startup action may be: “app_startaction”
- the application verification action may be: "health_check action”.
- the deployment path may be: “/ app”, “/ etc”, “/ var / log”, and so on.
- the application stopping action may specify stopping an application component or deleting an application component currently installed during the deployment preparation process
- the pre-deployment action may specify a pre-installation action to be performed, such as creating a current application component version. Backup, check dependent resource packages, etc .
- the post-deployment actions can specify actions after the installation files are deployed, such as configuring application components, changing certain related file permissions, etc .
- the application launch actions can specify launching application components to perform actions; and all The application verification action can specify whether the application component deployment is successful.
- the application component deployment is completed. If one of the above five execution actions does not exist in the standard deployment execution action, or if there is an execution action that fails to execute in the standard deployment execution action, the application component deployment process ends.
- An application component deployment method provided by the embodiment of the present application compared with the current manual deployment of application components, the embodiment of the present application can receive an application component deployment instruction, where the deployment instruction includes an application component identification of an application component to be deployed; Obtain the application component's to-be-deployed file and deployment configuration file according to the application component identifier, and at the same time, can parse the deployment configuration file to obtain the standard deployment execution action of the application component and the to-be-deployed file A corresponding deployment path; performing an application stop action, a pre-deployment action, a post-deployment action, an application start action, and an application verification action in the standard deployment execution action, and deploying the to-be-deployed file to the deployment path according to the deployment path
- the application component deployment is completed, so that the application component deployment can be completed automatically and the application component deployment process can be standardized, speeding up the deployment, controlling the deployment rhythm, reducing the complexity of deployment, and reducing manual operations. Mistakes and risks that can
- this embodiment of the present application provides another application component deployment method, as shown in FIG. 2, the method includes :
- the deployment instruction includes an application component identifier of an application component to be deployed.
- the step 202 may specifically include: downloading a deployment installation package of the application component from a preset package storage server according to the application component identifier, where the preset package storage server stores different application components A corresponding deployment installation package; the to-be-deployed file and the deployment configuration file of the application component are parsed from the deployment installation package.
- the deployment installation package may be obtained by packaging and processing the to-be-deployed file and the deployment configuration file after a technician has written the deployment configuration file.
- a deployment installation package of the application component may be downloaded to the server to be deployed.
- the deployment installation package may generally be a compressed file package, and the compressible file package is a zip compressed file package or a tar compressed file package.
- the deployment and installation package exists in the form of a compressed file package, which can be conveniently stored, transmitted, and distributed.
- the method further includes: storing a to-be-deployed file and a deployment configuration file of the application component in a local temporary storage file; when receiving the application component After the return value after the deployment is completed, the to-be-deployed file and the deployment configuration file of the application component are deleted from the temporary storage file.
- the return value of the deployment of the application component may be 0. When the return value of the deployment of the application component is 0, it indicates that the deployment of the application component is completed, and the to-be-deployed file of the application component is deleted from the temporary storage file. And deployment profiles.
- the standard deployment execution action may define five execution actions: an application stop action, a pre-deployment action, a post-deployment action, an application start action, and an application verification action.
- the application stop action may include an application stop command print command and an application stop command; specifically, the resource-dependent package download command print command may be: "echo application stop ..”, and the application stop command may be: ". /bin/stop.sh ".
- the pre-deployment action may include a pre-deployment action print command and an application component pre-installation command.
- the application component pre-installation command may be a current version application component backup creation command, a resource package detection command, etc.
- the pre-deployment action print command The command may be: "echo before_install action ..”, and the application component pre-installation command may be: “./bin/backup.sh”.
- the post-deployment action may include a post-deployment action print command and an application component related permission configuration or change command.
- the post-deployment action print command may be: "echo after_install action ..”
- the command can be: "chmod ba + x bin-R”.
- the application start action may include an application start action print command and an application component start command.
- the application start action print command may be: “echo application start action "
- the application component start command may be: "./Bin/start.sh”.
- the application verification action may include the application verification action print command and the application component deployment verification command.
- the application verification action print command may be: "echo application health check action "
- the application The component deployment verification command can be: "test-f var / app.pid”.
- step 204 Perform an application stop action in the standard deployment execution action, and detect whether the execution is completed. If the execution is completed, step 205 is performed; if the execution fails, step 210 is performed.
- the step 204 may specifically include: executing the application stopping action to execute the installed application component stop command, stopping the application component, or Remove application components that are currently installed during deployment preparation.
- the application stop action may include an application stop command print command and an application stop command
- the step 204 may specifically include: executing the application stop action to first execute the application stop command print command and print out a message application stop.action ...; and then execute the installed application component stop command to stop the application component or delete the currently installed application component during the deployment preparation process.
- the execution of the application stopping action may sequentially execute each command defined by the application. Specifically, each command line execution statement is executed. After the execution of any command line execution statement is completed, the corresponding return value may be 0. After each command in the application stop action, the return value of each command can be received, that is, it can be determined whether the execution of the application stop action is completed by detecting whether the return value corresponding to the application stop action is 0. If the return value of each command of the application stop action is 0, it is determined that the execution of the application stop action is completed; if the return value of each command of the application stop action is non-zero, it is determined that the execution of the application stop action has failed, and the application component is terminated. Deployment process. In addition, if there is no application stopping action in the standard deployment execution action, the deployment process of the application component is also ended.
- step 205 Perform a pre-deployment action in the standard deployment execution action, and detect whether the execution is completed. If the execution is completed, step 206 is performed; if the execution fails, step 210 is performed.
- the step 205 may specifically include: executing the pre-deployment action to execute the application component pre-installation command to perform the application component Pre-installed.
- the pre-deployment action may include a pre-deployment action print command and an application component pre-installation command
- the step 205 may specifically include: executing the pre-deployment action to first execute the pre-deployment action print command and print out a Information before installation ....; then execute the application component pre-installation command to pre-install the application component, create a backup of the previous version of the application component, detect dependent resource packages, etc.
- executing the pre-deployment actions can sequentially execute the commands defined by it. Specifically, each command line execution statement is executed. After the execution of any command line execution statement is completed, the corresponding return value can be 0. After describing each command in the pre-deployment action, the return value of each command can be received, that is, it can be determined whether the pre-deployment action is completed by detecting whether the return value corresponding to the pre-deployment action is 0.
- the return value of each command of the pre-deployment action is 0, it is determined that the execution of the pre-deployment action is completed; if the return value of each command of the pre-deployment action is non-zero, it is determined that the execution of the pre-deployment action has failed, and the application component is terminated. Deployment process. In addition, if there is no pre-deployment action in the standard deployment execution action, the deployment process of the application component is also ended.
- step 206 Deploy the to-be-deployed file to the to-be-deployed server according to the deployment path, perform post-deployment actions, and check whether execution is complete. If the execution is completed, step 207 is performed; if the execution fails, step 210 is performed.
- the step of deploying the file to be deployed to the server to be deployed according to the deployment path may specifically include: copying the file to be deployed to the deployment path to complete the deployment of all files
- the file to be deployed is deployed to the server to be deployed, and the deployment path is the deployment path of the file to be deployed on the server to be deployed.
- the app.jar file can be copied to the / app path of the server to be deployed; if the file to be deployed is a config file, the config file can be copied to all The / etc path of the server to be deployed is described; if the file to be deployed is a bin file, the bin file may be copied to the / app path of the server to be deployed; if the file to be deployed is a log file, the log may be logged Files are copied to the / var / log path of the server to be deployed, etc.
- the step 206 may specifically include: performing the post-deployment action to execute the application component related permission configuration or change command , Configure or change related permissions of application components.
- the step 206 may specifically include: executing the post-deployment action to first execute the post-deployment action print command and print out A message after_install action ..; and then execute the application component related permission configuration or change command to configure or change the application component related permission.
- executing the post-deployment actions can sequentially execute the commands defined by it. Specifically, each command line execution statement is executed. After the execution of any command line execution statement is completed, the corresponding return value can be 0. After describing each command in the post-deployment action, the return value of each command can be received, that is, it can be determined whether the post-deployment action is completed by detecting whether the return value corresponding to the post-deployment action is 0.
- step 207 Perform an application startup action in the standard deployment execution action, and detect whether the execution is completed. If the execution is completed, step 208 is performed; if the execution fails, step 210 is performed.
- step 207 may specifically include: executing the application startup action to execute the application component startup command to start an application component.
- the step 207 may specifically include: executing the application launching action to first execute the application launching action print command, and printing out a message application start action ...; and then execute the application component startup command to start the application component.
- each command defined by it can be sequentially executed. Specifically, each command line execution statement is executed. After the execution of any command line execution statement is completed, the corresponding return value can be 0. After describing each command in the application startup action, the return value of each command can be received, that is, it can be determined whether the execution of the application startup action is completed by detecting whether the return value corresponding to the application startup action is 0. If the return value of each command of the application startup action is 0, it is determined that the execution of the application startup action is completed; if the return value of each command of the application startup action is non-zero, it is determined that the execution of the application startup action fails, and the application component is terminated. Deployment process. In addition, if there is no application startup action in the standard deployment execution action, the deployment process of the application component is also ended.
- step 208 Perform an application verification action in the standard deployment execution action, and detect whether the execution is completed. If the execution is completed, step 209 is performed; if the execution fails, step 210 is performed.
- the step 208 may specifically include: performing the application verification action to execute the application component deployment verification command to verify application component deployment.
- the step 208 may specifically include: executing the application verification action to first execute the application verification action print command and print out an information echo application health check ... Then execute the application component deployment verification command to verify application component deployment.
- each command defined by it can be sequentially executed. Specifically, each command line execution statement is executed. After the execution of any command line execution statement is completed, the corresponding return value can be 0. After describing each command in the application verification action, the return value of each command can be received, that is, it can be determined whether the execution of the application verification action is completed by detecting whether the return value corresponding to the application verification action is 0. If the return value of each command of the application verification action is 0, it is determined that the execution of the application verification action is completed; if the return value of each command of the application verification action is non-zero, it is determined that the execution of the application verification action fails, and the end of the application component is ended. Deployment process. In addition, if there is no application verification action in the standard deployment execution action, the deployment process of the application component is also ended.
- the embodiment of the present application can receive an application component deployment instruction, where the deployment instruction includes an application component identifier of an application component to be deployed;
- the application component's to-be-deployed file and deployment configuration file can be obtained according to the application component identifier, and at the same time, the deployment configuration file can be parsed to obtain the standard deployment execution action of the application component and the to-be-deployed
- the deployment path corresponding to the file execute the application stop action, pre-deployment action, post-deployment action, application start action, and application verification action in the standard deployment execution action, and deploy the to-be-deployed file to all of the files according to the deployment path
- the server to be deployed is described to complete the deployment of the application components, thereby enabling the automatic completion of application component deployment and standardization of the application component deployment process, accelerating the speed of deployment, controlling the deployment rhythm, reducing the complexity of deployment, and reducing manual operations. Errors
- an embodiment of the present application provides an application component deployment device.
- the device includes a receiving unit 31, an obtaining unit 32, a parsing unit 33, and a deployment unit 34.
- the receiving unit 31 may be configured to receive an application component deployment instruction, where the deployment instruction includes an application component identifier of an application component to be deployed.
- the receiving unit 31 is a main functional module for receiving an application component deployment instruction in the device.
- the obtaining unit 32 may be configured to obtain a to-be-deployed file and a deployment configuration file of the application component according to the application component identifier.
- the obtaining unit 32 is a main functional module in the device that obtains a to-be-deployed file and a deployment configuration file of the application component according to the application component identifier.
- the parsing unit 33 may be configured to parse the deployment configuration file to obtain a standard deployment execution action of the application component and a deployment path corresponding to the file to be deployed.
- the parsing unit 33 is a main functional module that parses the deployment configuration file in this device to obtain the standard deployment execution action of the application component and the deployment path corresponding to the file to be deployed.
- the deployment unit 34 may be configured to execute an application stop action, a pre-deployment action, a post-deployment action, an application start action, and an application verification action in the standard deployment execution action, and send the to-be-deployed file according to the deployment path. Deploying to the server to be deployed to complete deployment of the application component.
- the deployment unit 35 executes an application stop action, a pre-deployment action, a post-deployment action, an application start action, and an application verification action in the standard deployment execution action performed by the device, and sends the to-be-deployed file according to the deployment path. Deploying to the server to be deployed to complete deployment of the application component.
- the deployment unit 34 may be specifically configured to execute the application stop action; if the execution of the application stop action fails, end the deployment process of the application component; if the execution of the application stop action is completed, execute the deployment A previous action; if the execution of the pre-deployment action fails, ending the deployment process of the application component; if the pre-deployment action is completed, deploying the file to be deployed to the server to be deployed according to the deployment path, And execute a post-deployment action; if the post-deployment action fails, the application component deployment process ends; if the post-deployment action is completed, the application launch action is executed; if the application launch action fails to execute , The deployment process of the application component is ended; if the execution of the application startup action is completed, the application verification action is performed; if the execution of the application verification action fails, the deployment process of the application component is ended; if the After the execution of the application verification action is completed, it is determined to complete the deployment process of the application component.
- the apparatus in order to detect whether each action in the standard deployment execution action is completed, the apparatus further includes a detection unit 35 and a determination unit 36, as shown in FIG. 4.
- the detection unit 35 may be configured to detect whether an execution return value corresponding to the application stop action, the pre-deployment action, the post-deployment action, the application start action, or the application verification action is non-zero.
- the determining unit 36 may be configured to determine that the execution of the application stop action, the pre-deployment action, the post-deployment action, the application start action, and the application verification action is completed if it is 0. If the execution return value is non-zero, it is determined that the execution action corresponding to a non-zero execution return value is not executed.
- the deployment unit 34 may be specifically configured to execute the application stopping action to execute a stop command of an installed application component included in the application stopping action; execute the pre-deployment action to execute an application included in the pre-deployment action Component pre-installation command; executing the post-deployment action to configure or change a command with application component-related permissions included in the post-deployment action; executing the application launching action to execute an application component launching command included in the application launching action; Performing the application verification action to perform the application verification action includes an application component deployment verification command.
- the obtaining unit 32 may be specifically configured to download a deployment installation package of the application component from a preset package storage server according to the application component identifier, and the preset package storage server stores deployment installation packages corresponding to different application components; A to-be-deployed file and a deployment configuration file of the application component are parsed from the deployment installation package.
- the deployment unit 34 may be further configured to copy the file to be deployed to the deployment path to complete the deployment of the file to be deployed to the server to be deployed, and the deployment path is The deployment path of the file to be deployed on the server to be deployed is described.
- the apparatus in order to save storage space of a server to be deployed and improve application component deployment efficiency, the apparatus further includes a storage unit 37 and a deletion unit 38.
- the storage unit 37 may be configured to store a to-be-deployed file and a deployment configuration file of the application component in a local temporary storage file.
- the storage unit 37 is a main functional module in the device that stores a to-be-deployed file and a deployment configuration file of the application component into a local temporary storage file.
- the deleting unit 38 may be configured to delete a to-be-deployed file and a deployment configuration file of the application component from the temporary storage file after receiving a return value of the application component deployment completion.
- an embodiment of the present application further provides a computer non-volatile readable storage medium having computer-readable instructions stored thereon.
- the computer-readable instructions When the computer-readable instructions are executed by a processor, The following steps are implemented: receiving an application component deployment instruction, the deployment instruction including an application component identification of an application component to be deployed; obtaining a to-be-deployed file and a deployment configuration file of the application component according to the application component identification; and the deployment configuration file Perform analysis to obtain the standard deployment execution action of the application component and the deployment path corresponding to the file to be deployed; execute the application stop action, pre-deployment action, post-deployment action, application start-up action, and application in the standard deployment execution action Verify the action, and deploy the to-be-deployed file to the to-be-deployed server according to the deployment path to complete the application component deployment.
- an embodiment of the present application further provides a physical structure diagram of a computer device.
- the computer device includes: 41, a memory 42, and computer-readable instructions stored on the memory 42 and executable on a processor, wherein the memory 42 and the processor 41 are provided on a bus 43 and the processor 41 executes the computer-readable instructions
- the deployment instruction including an application component identification of an application component to be deployed
- configuring the deployment is parsed to obtain the standard deployment execution action of the application component and the deployment path corresponding to the file to be deployed; execution of the application stop action, pre-deployment action, post-deployment action, application start-up action and Apply a verification action, and deploy the file to be deployed to the service to be deployed according to the deployment path
- an application component deployment instruction can be received, where the deployment instruction includes an application component identification of an application component to be deployed; and a to-be-deployed file and a deployment configuration file of the application component can be obtained according to the application component identification, and At the same time, the deployment configuration file can be parsed to obtain the standard deployment execution action of the application component and the deployment path corresponding to the to-be-deployed file; execute the application stop action and pre-deployment action in the standard deployment execution action , Post-deployment actions, application startup actions, and application verification actions, and deploying the to-be-deployed file to the to-be-deployed server according to the deployment path to complete the application component deployment, thereby enabling automatic completion of application component deployment , And standardize the deployment process of application components, accelerate the speed of deployment, control the pace of deployment, reduce the complexity of deployment, reduce manual operations errors and risks, and then improve the efficiency and accuracy of application component deployment.
- modules or steps of the present application may be implemented by a general-purpose computing device, and they may be concentrated on a single computing device or distributed on a network composed of multiple computing devices. Above, optionally, they may be implemented with computer-readable instruction code executable by a computing device, so that they may be stored in a storage device and executed by the computing device, and in some cases, may be different from this.
- the steps shown or described are performed in sequence, either by making them into individual integrated circuit modules, or by making multiple modules or steps into a single integrated circuit module. As such, this application is not limited to any particular combination of hardware and software.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
本申请公开了一种应用组件部署方法、装置及计算机存储介质，涉及应用开发技术领域，主要目的在于能够提高应用组件部署的效率和精确度。所述方法包括：接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。本申请适用于应用组件的部署。
Description
本申请要求与2018年6月29日提交中国专利局、申请号为2018106990304、申请名称为“应用组件部署方法、装置及计算机存储介质”的中国专利申请的优先权，其全部内容通过引用结合在申请中。
本申请涉及应用开发技术领域，尤其是涉及一种应用组件部署方法、装置及计算机存储介质。
随着信息技术的不断发展和进步，为了满足人们不增长的需求，应用计算机可读指令需要不断更新功能，因此需要应用开发人员不断的开发应用组件。应用开发人员在开发完一个应用组件的代码或者修改完应用组件的一处代码后，通常需要部署应用组件并部署应用组件。
目前，通常由技术人员通过手动方式部署应用组件。然而，应用组件部署需要配置信息非常多，针对一个应用计算机可读指令可能会出现不同团队协作开发不同应用组件，而每个应用组件的开发语言及开发环境各不相同，应用组件部署方式也不会不同，且随着微服务框架的兴起，一个应用计算机可读指令上线底层可能需要部署几十甚至上百个应用组件，通过手动方式部署应用组件，会造成无法控制应用组件构部署节奏，造成应用组件部署的速度较慢，且容易增加应用组件部署的错误和风险，从而导致应用组件部署的效率和精确度较低。
发明内容
本申请提供了一种应用组件部署方法、装置及计算机存储介质，主要在于能够实现自动完成应用组件部署，以及实现应用组件部署流程的标准化，加快部署的速度，控制部署节奏，降低部署的复杂度，减少手工操作的错误和风险，从而能够提高应用组件部署的效率和精确度。
根据本申请的第一个方面，提供一种应用组件部署方法，包括：
接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；
根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；
对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署 文件对应的部署路径；
执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
根据本申请的第二个方面，提供一种应用组件部署装置，包括：
接收单元，用于接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；
获取单元，用于根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；
解析单元，用于对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；
部署单元，用于执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
根据本申请的第三个方面，提供一种计算机非易失性可读存储介质，其上存储有计算机可读指令，该计算机可读指令被处理器执行时实现以下步骤：
接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
根据本申请的第四个方面，提供一种应用组件部署装置，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现以下步骤：
接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
本申请提供的一种应用组件部署方法、装置及计算机存储介质，与目前通过手动方式部署应用组件相比，本申请能够接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；能够根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件，与此同时，能够对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署，从而能够实现自动完成应用组件部署，以及实现应用组件部署流程的标准化，加快部署的速度，控制部署节奏，降低部署的复杂度，减少手工操作的错误和风险，进而能够提高应用组件部署的效率和精确度。
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1示出了本申请实施例提供的一种应用组件部署方法流程图；
图2示出了本申请实施例提供的另一种应用组件部署方法流程图；
图3示出了本申请实施例提供的一种应用组件部署装置的结构示意图；
图4示出了本申请实施例提供的另一种应用组件部署装置的结构示意图；
图5示出了本申请实施例提供的一种计算机设备的实体结构示意图。
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
如背景技术，目前，通常由技术人员通过手动方式部署应用组件。然而，应用组件部署需要配置信息非常多，针对一个应用计算机可读指令可能会出现不同团队协作开发不同应用组件，而每个应用组件的开发语言及开发环境各不相同，应用组件部署方式也不会不同，且随着微服务框架的兴起，一个应用计算机可读指令上线底层可能需要部署几十甚至上百个应用组件，通过手动方式部署应用组件，会造成无法控制应用组件构部署节奏，造成应用组件部署的速度较慢，且容易增加应用组件部署的错误和风险，从而导致应用组件部署的效率和精确度较低。
为了解决上述问题，本申请实施例提供了一种应用组件部署方法，如图1所示，所述方法包括：101、接收应用组件部署指令。其中，所述部署指令包括待部署应用组件的应用组件标识。所述应用组件标识可以为应用组件的名称或者为应用组件的唯一编码，本申 请实施例不做限定。所述部署指令可以为在技术人员点击或者触发部署按钮或者按键时，本申请实施例的执行主体应用组件部署装置接收到的。
102、根据应用组件标识获取所述应用组件的待部署文件和部署配置文件。
需要说明的是，所述部署配置文件可以为技术人员针对所述应用组件预先编写的，所述部署配置文件可以定义描述两个部分的内容：应用组件的标准部署执行动作和所述待部署文件对应的部署路径。不同的应用组件对应不同的部署配置文件，但是不同的部署配置文件均描述上两个部分的内容，不同的应用组件的标准部署执行动作相同，标准部署执行动作中各个执行动作均可以由若干个命令组成，所述各个命令可以通过命令行执行语句表示，所述命令行执行语句可以为shell执行语句或者其他执行语句，每个执行动作下的各个命令可以根据应用组件的实际情况而定。所述标准部署执行动作可以定义有5个执行动作：应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，即针对不同的应用组件，部署配置文件可均描述上述5个执行动作。所述部署路径可以为所述待部署文件部署安装到待部署服务器上的路径。
其中，所述部署配置文件可以为通过json文本格式编写的，也可以为通过yaml、xml文本格式编写的，本申请实施例不限定于此。例如，当所述部署配置文件为通过json文本格式编写时，所述应用停止动作可以为：“app_stop action”，所述部署前动作可以为：“before_install action”，所述部署后动作可以为：“after_install action”、所述应用启动动作可以为：“app_startaction”，所述应用验证动作可以为：“health_check action”。所述部署路径可以为：“/app”、“/etc”、“/var/log”等。
103、对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径。
在本申请实施例中，所述应用停止动作可以指定停止应用组件或者删除部署准备过程中当前已安装的应用组件，所述部署前动作可以指定执行的预安装动作，如创建当前应用组件版本的备份，检查依赖资源包等；所述部署后动作可以指定安装文件部署完成后动作，如配置应用组件、更改某些相关文件权限等；所述应用启动动作可以指定启动应用组件执行动作；和所述应用验证动作可以指定验证应用组件部署是否成功。
104、执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
对于本申请实施例，若所述标准部署执行动作中均执行完成，且根据所述部署路径将所述待部署文件部署到所述待部署服务器中，则完成所述应用组件部署。若所述标准部署 执行动作中不存在上述5个执行动作中的一种，或者若所述标准部署执行动作中存在执行失败的执行动作，则结束应用组件部署流程。
本申请实施例提供的一种应用组件部署方法，与目前通过手动方式部署应用组件相比，本申请实施例能够接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；能够根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件，与此同时，能够对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署，从而能够实现自动完成应用组件部署，以及实现应用组件部署流程的标准化，加快部署的速度，控制部署节奏，降低部署的复杂度，减少手工操作的错误和风险，进而能够提高应用组件部署的效率和精确度。
进一步的，为了更好的说明上述应用组件部署的过程，作为对上述实施例的细化和扩展，本申请实施例提供了另一种应用组件部署方法，如图2所示，所述方法包括：
201、接收应用组件部署指令。
其中，所述部署指令包括待部署应用组件的应用组件标识。
202、根据应用组件标识获取所述应用组件的待部署文件和部署配置文件。
对于本申请实施例，为了能够将应用组件的待部署文件和部署配置文件一体化，简化应用组件的待部署文件和部署配置文件管理，避免待部署文件和部署配置文件需要对应的问题以及避免额外对部署配置文件进行管理，所述步骤202具体可以包括：根据所述应用组件标识从预设包存储服务器上下载所述应用组件的部署安装包，所述预设包存储服务器保存有不同应用组件对应的部署安装包；从所述部署安装包中解析出所述应用组件的待部署文件和部署配置文件。所述部署安装包可以为在技术人员编写完所述部署配置文件后，对所述待部署文件和所述部署配置文件进行打包处理得到的。具体地，可以将所述应用组件的部署安装包下载到所述待部署服务器上，所述部署安装包可以一般压缩文件包，所述可以压缩文件包为zip压缩文件包、tar压缩文件包，所述部署安装包以压缩文件包形式存在，能够方便存储、传输及分发等。
此外，为了节省待部署服务器的存储空间，提升应用组件部署效率，所述方法还包括：将所述应用组件的待部署文件和部署配置文件存储至本地临时存储文件中；当接收所述应用组件部署完成的返回值后，在所述临时存储文件中删除所述应用组件的待部署文件和部署配置文件。所述应用组件部署完成的返回值可以为0，在接收到应用组件部署的返回值为0时，说明所述应用组件部署完成，在所述临时存储文件中删除所述应用组件的待部署 文件和部署配置文件。
203、对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径。
在发明实施例中，所述标准部署执行动作可以定义有5个执行动作：应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作。所述应用停止动作可以包括应用停止命令打印命令和应用停止命令；具体地，所述依赖资源包下载命令打印命令可以为：“echo application stop..”，所述应用停止命令可以为：“./bin/stop.sh”。所述部署前动作可以包括部署前动作打印命令和应用组件预安装命令，如应用组件预安装命令可以当前版本应用组件备份创建命令、依赖资源包检测命令等，具体地，所述部署前动作打印命令可以为：“echo before_install action..”，所述应用组件预安装命令可以为：“./bin/backup.sh”。所述部署后动作可以包括部署后动作打印命令和应用组件相关权限配置或者更改命令，具体地，所述部署后动作打印命令可以为：“echo after_install action..”，应用组件相关权限配置或者更改命令可以为：“chmod a+x bin-R”。所述应用启动动作可以包括应用启动动作打印命令和应用组件启动命令，具体地，所述应用启动动作打印命令可以为：“echo application start action...”，所述应用组件启动命令可以为：“./bin/start.sh”。所述应用验证动作可以包括所述应用验证动作打印命令和所述应用组件部署验证命令，具体地，所述应用验证动作打印命令可以为：“echo application health check action...”，所述应用组件部署验证命令可以为：“test-f var/app.pid”。
204、执行所述标准部署执行动作中的应用停止动作，并检测是否执行完成。若执行完成，则执行步骤205；若执行失败，则执行步骤210。
对于本申请实施例，若所述应用停止动作包括已安装应用组件停止命令，所述步骤204具体可以包括：执行所述应用停止动作，以执行所述已安装应用组件停止命令，停止应用组件或者删除部署准备过程中当前已安装的应用组件。此外，若所述应用停止动作可以包括应用停止命令打印命令和应用停止命令，则所述步骤204具体可以包括：执行所述应用停止动作，以首先执行应用停止命令打印命令，打印输出一条信息application stop.action...；然后执行所述已安装应用组件停止命令，停止应用组件或者删除部署准备过程中当前已安装的应用组件。
需要说明的是，执行所述应用停止动作可以顺序执行其定义的各个命令，具体地，执行各个命令行执行语句，任意命令行执行语句在执行完成后，对应的返回值可以为0，执行完所述应用停止动作中的各个命令后，可以接收到所述各个命令的返回值，即可以通过检测应用停止动作对应的返回值是否为0，以确定应用停止动作是否执行完成。若应用停 止动作的各个命令的返回值均为0，则确定应用停止动作执行完成；若应用停止动作的各个命令的返回值存在非0，则确定应用停止动作执行失败，结束所述应用组件的部署流程。此外，若所述标准部署执行动作中不存在应用停止动作，则也结束所述应用组件的部署流程。
205、执行所述标准部署执行动作中的部署前动作，并检测是否执行完成。若执行完成，则执行步骤206；若执行失败，则执行步骤210。
对于本申请实施例，若所述部署前动作包括应用组件预安装命令，所述步骤205具体可以包括：执行所述部署前动作，以执行所述应用组件预安装命令，对所述应用组件进行预安装。此外，若所述部署前动作可以包括部署前动作打印命令和应用组件预安装命令，则所述步骤205具体可以包括：执行所述部署前动作，以首先执行署前动作打印命令，打印输出一条信息before install action....；然后执行所述应用组件预安装命令对所述应用组件进行预安装，创建前版本应用组件的备份、检测依赖资源包等。
同理地，执行所述部署前动作可以顺序执行其定义的各个命令，具体地，执行各个命令行执行语句，任意命令行执行语句在执行完成后，对应的返回值可以为0，执行完所述部署前动作中的各个命令后，可以接收到所述各个命令的返回值，即可以通过检测部署前动作对应的返回值是否为0，以确定部署前动作是否执行完成。若部署前动作的各个命令的返回值均为0，则确定部署前动作执行完成；若部署前动作的各个命令的返回值存在非0，则确定部署前动作执行失败，结束所述应用组件的部署流程。此外，若所述标准部署执行动作中不存在部署前动作，则也结束所述应用组件的部署流程。
206、根据所述部署路径将所述待部署文件部署到待部署服务器中，并执行部署后动作，并检测是否执行完成。若执行完成，则执行步骤207；若执行失败，则执行步骤210。
对于本申请实施例，所述根据所述部署路径将所述待部署文件部署到待部署服务器中的步骤，具体可以包括：将所述待部署文件拷贝到所述部署路径下，以完成将所述待部署文件部署到所述待部署服务器中，所述部署路径为所述待部署文件在所述待部署服务器上的部署路径。例如，若所述待部署文件为app.jar文件，可以将app.jar文件拷贝至所述待部署服务器的/app路径下；若所述待部署文件为config文件，可以将config文件拷贝至所述待部署服务器的/etc路径下；若所述待部署文件为bin文件，可以将bin文件拷贝至所述待部署服务器的/app路径下；若所述待部署文件为log文件，可以将log文件拷贝至所述待部署服务器的/var/log路径下等。
在本申请实施例中，若所述部署后动作包括应用组件相关权限配置或者更改命令，所述步骤206具体可以包括：执行所述部署后动作，以执行所述应用组件相关权限配置或者 更改命令，对应用组件相关权限进行配置或者更改。此外，若所述部署后动作包括部署后动作打印命令和应用组件相关权限配置或者更改命令，所述步骤206具体可以包括：执行所述部署后动作，以首先执行部署后动作打印命令，打印输出一条信息after_install action..；然后执行所述应用组件相关权限配置或者更改命令，对应用组件相关权限进行配置或者更改。
同理地，执行所述部署后动作可以顺序执行其定义的各个命令，具体地，执行各个命令行执行语句，任意命令行执行语句在执行完成后，对应的返回值可以为0，执行完所述部署后动作中的各个命令后，可以接收到所述各个命令的返回值，即可以通过检测部署后动作对应的返回值是否为0，以确定部署后动作是否执行完成。若应用停止动作的各个命令的返回值均为0，则确定部署后动作执行完成；若部署后动作的各个命令的返回值存在非0，则确定部署后动作执行失败，结束所述应用组件的部署流程。此外，若所述标准部署执行动作中不存在部署后动作，则也结束所述应用组件的部署流程。
207、执行所述标准部署执行动作中的应用启动动作，并检测是否执行完成。若执行完成，则执行步骤208；若执行失败，则执行步骤210。
对于本申请实施例，若所述应用启动动作包括应用组件启动命令，所述步骤207具体可以包括：执行所述应用启动动作，以执行所述应用组件启动命令，启动应用组件。此外，若所述应用启动动作包括应用启动动作打印命令和应用组件启动命令，所述步骤207具体可以包括：执行所述应用启动动作，以首先执行应用启动动作打印命令，打印输出一条信息application start action...；然后执行所述应用组件启动命令，启动应用组件。
同理地，执行所述应用启动动作可以顺序执行其定义的各个命令，具体地，执行各个命令行执行语句，任意命令行执行语句在执行完成后，对应的返回值可以为0，执行完所述应用启动动作中的各个命令后，可以接收到所述各个命令的返回值，即可以通过检测应用启动动作对应的返回值是否为0，以确定应用启动动作是否执行完成。若应用启动动作的各个命令的返回值均为0，则确定应用启动动作执行完成；若应用启动动作的各个命令的返回值存在非0，则确定应用启动动作执行失败，结束所述应用组件的部署流程。此外，若所述标准部署执行动作中不存在应用启动动作，则也结束所述应用组件的部署流程。
208、执行所述标准部署执行动作中的应用验证动作，并检测是否执行完成。若执行完成，则执行步骤209；若执行失败，则执行步骤210。
对于本申请实施例，若所述应用验证动作包括应用组件部署验证命令，所述步骤208具体可以包括：执行所述应用验证动作，以执行所述应用组件部署验证命令，验证应用组件部署。此外，若所述应用验证动作包括应用验证动作打印命令和应用组件部署验证命令， 所述步骤208具体可以包括：执行所述应用验证动作，以首先执行应用验证动作打印命令，打印输出一条信息echo application health check action...；然后执行所述应用组件部署验证命令，验证应用组件部署。
同理地，执行所述应用验证动作可以顺序执行其定义的各个命令，具体地，执行各个命令行执行语句，任意命令行执行语句在执行完成后，对应的返回值可以为0，执行完所述应用验证动作中的各个命令后，可以接收到所述各个命令的返回值，即可以通过检测应用验证动作对应的返回值是否为0，以确定应用验证动作是否执行完成。若应用验证动作的各个命令的返回值均为0，则确定应用验证动作执行完成；若应用验证动作的各个命令的返回值存在非0，则确定应用验证动作执行失败，结束所述应用组件的部署流程。此外，若所述标准部署执行动作中不存在应用验证动作，则也结束所述应用组件的部署流程。
209、确定完成所述应用组件的部署流程。
210、结束所述应用组件的部署流程。
本申请实施例提供的另一种应用组件部署方法，与目前通过手动方式部署应用组件相比，本申请实施例能够接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；能够根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件，与此同时，能够对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署，从而能够实现自动完成应用组件部署，以及实现应用组件部署流程的标准化，加快部署的速度，控制部署节奏，降低部署的复杂度，减少手工操作的错误和风险，进而能够提高应用组件部署的效率和精确度。
进一步地，作为图1的具体实现，本申请实施例提供了一种应用组件部署装置，如图3所示，所述装置包括：接收单元31、获取单元32和解析单元33和部署单元34。
所述接收单元31，可以用于接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识。所述接收单元31是本装置中接收应用组件部署指令的主要功能模块。
所述获取单元32，可以用于根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件。所述获取单元32是本装置中根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件的主要功能模块。
所述解析单元33，可以用于对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径。所述解析单元33是本装置中对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部 署路径的主要功能模块。
所述部署单元34，可以用于执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。所述部署单元35是本装置中执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
所述部署单元34，具体可以用于执行所述应用停止动作；若所述应用停止动作执行失败，则结束所述应用组件的部署流程；若所述应用停止动作执行完成，则执行所述部署前动作；若所述部署前动作执行失败，则结束所述应用组件的部署流程；若执行完所述部署前动作，则根据所述部署路径将所述待部署文件部署到待部署服务器中，并执行部署后动作；若所述部署后动作执行失败，则结束所述应用组件的部署流程；若所述部署后动作执行完成，则执行所述应用启动动作；若所述应用启动动作执行失败，则结束所述应用组件的部署流程；若所述应用启动动作执行完成，则执行所述应用验证动作；若所述应用验证动作执行失败，则结束所述应用组件的部署流程；若所述应用验证动作执行完成，则确定完成所述应用组件的部署流程。
对于本申请实施例，为了检测所述标准部署执行动作中的各个动作是否执行完成，所述装置还包括：检测单元35和确定单元36，如图4所示。
所述检测单元35，可以用于检测所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作、所述应用验证动作分别对应的执行返回值是否为非0。所述确定单元36，可以用于若为0，则确定执行完所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作和所述应用验证动作；若存在为非0的执行返回值，则确定对应执行返回值为非0的执行动作执行失败。所述部署单元34，具体可以用于执行所述应用停止动作，以执行所述应用停止动作包括的已安装应用组件停止命令；执行所述部署前动作，以执行所述部署前动作包括的应用组件预安装命令；执行所述部署后动作，以所述部署后动作包括的应用组件相关权限配置或者更改命令；执行所述应用启动动作，以执行所述应用启动动作包括的应用组件启动命令；执行所述应用验证动作，以执行所述应用验证动作包括应用组件部署验证命令。
对于本申请实施例，为了能够将应用组件的待部署文件和部署配置文件一体化，简化应用组件的待部署文件和部署配置文件管理，避免源待部署文件和部署配置文件需要对应的问题，所述获取单元32，具体可以用于根据所述应用组件标识从预设包存储服务器上下 载所述应用组件的部署安装包，所述预设包存储服务器保存有不同应用组件对应的部署安装包；从所述部署安装包中解析出所述应用组件的待部署文件和部署配置文件。此外，所述部署单元34，具体还可以用于将所述待部署文件拷贝到所述部署路径下，以完成将所述待部署文件部署到所述待部署服务器中，所述部署路径为所述待部署文件在所述待部署服务器上的部署路径。
对于本申请实施例，为了节省待部署服务器的存储空间，提升应用组件部署效率，所述装置还包括：存储单元37和删除单元38。
所述存储单元37，可以用于将所述应用组件的待部署文件和部署配置文件存储至本地临时存储文件中。所述存储单元37是本装置中将所述应用组件的待部署文件和部署配置文件存储至本地临时存储文件中的主要功能模块。所述删除单元38，可以用于当接收所述应用组件部署完成的返回值后，在所述临时存储文件中删除所述应用组件的待部署文件和部署配置文件。需要说明的是，本申请实施例提供的一种应用组件部署装置所涉及各功能模块的其他相应描述，可以参考图1所示方法的对应描述，在此不再赘述。
基于上述如图1所示方法，相应的，本申请实施例还提供了一种计算机非易失性可读存储介质，其上存储有计算机可读指令，该计算机可读指令被处理器执行时实现以下步骤：接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
基于上述如图1所示方法和如图3所示应用组件部署装置的实施例，本申请实施例还提供了一种计算机设备的实体结构图，如图5所示，该计算机设备包括：处理器41、存储器42、及存储在存储器42上并可在处理器上运行的计算机可读指令，其中存储器42和处理器41均设置在总线43上所述处理器41执行所述计算机可读指令时实现以下步骤：接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。该计算机设备还包括：总线43，被配置为耦接处理器41及存储器42。
通过本申请的技术方案，能够接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；能够根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件，与此同时，能够对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署，从而能够实现自动完成应用组件部署，以及实现应用组件部署流程的标准化，加快部署的速度，控制部署节奏，降低部署的复杂度，减少手工操作的错误和风险，进而能够提高应用组件部署的效率和精确度。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的计算机可读指令代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。
Claims (20)
- 一种应用组件部署方法，其特征在于，包括：接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
- 根据权利要求1所述的方法，其特征在于，所述执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到待部署服务器中，以完成应用组件部署，包括：执行所述应用停止动作；若所述应用停止动作执行失败，则结束所述应用组件的部署流程；若所述应用停止动作执行完成，则执行所述部署前动作；若所述部署前动作执行失败，则结束所述应用组件的部署流程；若执行完所述部署前动作，则根据所述部署路径将所述待部署文件部署到待部署服务器中，并执行部署后动作；若所述部署后动作执行失败，则结束所述应用组件的部署流程；若所述部署后动作执行完成，则执行所述应用启动动作；若所述应用启动动作执行失败，则结束所述应用组件的部署流程；若所述应用启动动作执行完成，则执行所述应用验证动作；若所述应用验证动作执行失败，则结束所述应用组件的部署流程；若所述应用验证动作执行完成，则确定完成所述应用组件的部署流程。
- 根据权利要求2所述的方法，其特征在于，所述方法还包括：检测所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作、所述应用验证动作分别对应的执行返回值是否为非0；若为0，则确定执行完所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作和所述应用验证动作；若存在为非0的执行返回值，则确定对应执行返回值为非0的执行动作执行失败。
- 根据权利要求1所述的方法，其特征在于，所述执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，包括：执行所述应用停止动作，以执行所述应用停止动作包括的已安装应用组件停止命令；执行所述部署前动作，以执行所述部署前动作包括的应用组件预安装命令；执行所述部署后动作，以所述部署后动作包括的应用组件相关权限配置或者更改命令；执行所述应用启动动作，以执行所述应用启动动作包括的应用组件启动命令；执行所述应用验证动作，以执行所述应用验证动作包括应用组件部署验证命令。
- 根据权利要求1所述的方法，其特征在于，所述根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件，包括：根据所述应用组件标识从预设包存储服务器上下载所述应用组件的部署安装包，所述预设包存储服务器保存有不同应用组件对应的部署安装包；从所述部署安装包中解析出所述应用组件的待部署文件和部署配置文件。
- 根据权利要求1所述的方法，其特征在于，所述根据所述部署路径将所述待部署文件部署到所述待部署服务器中，包括：将所述待部署文件拷贝到所述部署路径下，以完成将所述待部署文件部署到所述待部署服务器中，所述部署路径为所述待部署文件在所述待部署服务器上的部署路径。
- 根据权利要求1所述的方法，其特征在于，所述根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件之后，所述方法还包括：将所述应用组件的待部署文件和部署配置文件存储至本地临时存储文件中；当接收所述应用组件部署完成的返回值后，在所述临时存储文件中删除所述应用组件的待部署文件和部署配置文件。
- 一种应用组件部署装置，其特征在于，包括：接收单元，用于接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；获取单元，用于根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；解析单元，用于对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；部署单元，用于执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所 述待部署服务器中，以完成所述应用组件部署。
- 根据权利要求8所述的装置，其特征在于，所述部署单元，具体用于执行所述应用停止动作；若所述应用停止动作执行失败，则结束所述应用组件的部署流程；若所述应用停止动作执行完成，则执行所述部署前动作；若所述部署前动作执行失败，则结束所述应用组件的部署流程；若执行完所述部署前动作，则根据所述部署路径将所述待部署文件部署到待部署服务器中，并执行部署后动作；若所述部署后动作执行失败，则结束所述应用组件的部署流程；若所述部署后动作执行完成，则执行所述应用启动动作；若所述应用启动动作执行失败，则结束所述应用组件的部署流程；若所述应用启动动作执行完成，则执行所述应用验证动作；若所述应用验证动作执行失败，则结束所述应用组件的部署流程；若所述应用验证动作执行完成，则确定完成所述应用组件的部署流程。
- 根据权利要求9所述的装置，其特征在于，所述装置还包括：检测单元，用于检测所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作、所述应用验证动作分别对应的执行返回值是否为非0；确定单元，用于若为0，则确定执行完所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作和所述应用验证动作；若存在为非0的执行返回值，则确定对应执行返回值为非0的执行动作执行失败。
- 根据权利要求8所述的装置，其特征在于，所述部署单元，具体用于执行所述应用停止动作，以执行所述应用停止动作包括的已安装应用组件停止命令；执行所述部署前动作，以执行所述部署前动作包括的应用组件预安装命令；执行所述部署后动作，以所述部署后动作包括的应用组件相关权限配置或者更改命令；执行所述应用启动动作，以执行所述应用启动动作包括的应用组件启动命令；执行所述应用验证动作，以执行所述应用验证动作包括应用组件部署验证命令。
- 根据权利要求8所述的装置，其特征在于，所述获取单元，具体用于根据所述应用组件标识从预设包存储服务器上下载所述应用组件的部署安装包，所述预设包存储服务器保存有不同应用组件对应的部署安装包；从所述部署安装包中解析出所述应用组件的待部署文件和部署配置文件。
- 根据权利要求8所述的装置，其特征在于，所述部署单元，具体还用于将所述待部署文件拷贝到所述部署路径下，以完成将所述待部署文件部署到所述待部署服务器中，所述部署路径为所述待部署文件在所述待部署服务器上的部署路径。
- 根据权利要求8所述的装置，其特征在于，所述装置还包括：存储单元，用于将所述应用组件的待部署文件和部署配置文件存储至本地临时存储文件中；删除单元，用于当接收所述应用组件部署完成的返回值后，在所述临时存储文件中删除所述应用组件的待部署文件和部署配置文件。
- 一种计算机非易失性可读存储介质，其上存储有计算机可读指令，其特征在于，所述计算机可读指令被处理器执行时实现应用组件部署方法，包括：接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
- 根据权利要求15所述的计算机非易失性可读存储介质，其特征在于，所述计算机可读指令被处理器执行时实现所述执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到待部署服务器中，以完成应用组件部署，包括：执行所述应用停止动作；若所述应用停止动作执行失败，则结束所述应用组件的部署流程；若所述应用停止动作执行完成，则执行所述部署前动作；若所述部署前动作执行失败，则结束所述应用组件的部署流程；若执行完所述部署前动作，则根据所述部署路径将所述待部署文件部署到待部署服务器中，并执行部署后动作；若所述部署后动作执行失败，则结束所述应用组件的部署流程；若所述部署后动作执行完成，则执行所述应用启动动作；若所述应用启动动作执行失败，则结束所述应用组件的部署流程；若所述应用启动动作执行完成，则执行所述应用验证动作；若所述应用验证动作执行失败，则结束所述应用组件的部署流程；若所述应用验证动作执行完成，则确定完成所述应用组件的部署流程。
- 根据权利要求16所述的计算机非易失性可读存储介质，其特征在于，所述计算机可读指令被处理器执行时实现所述方法还包括：检测所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作、所述应用验证动作分别对应的执行返回值是否为非0；若为0，则确定执行完所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作和所述应用验证动作；若存在为非0的执行返回值，则确定对应执行返回值为非0的执行动作执行失败。
- 一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的 计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现应用组件部署方法，包括：接收应用组件部署指令，所述部署指令包括待部署应用组件的应用组件标识；根据所述应用组件标识获取所述应用组件的待部署文件和部署配置文件；对所述部署配置文件进行解析，得到所述应用组件的标准部署执行动作和所述待部署文件对应的部署路径；执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到所述待部署服务器中，以完成所述应用组件部署。
- 根据权利要求18所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时实现所述执行所述标准部署执行动作中的应用停止动作、部署前动作、部署后动作、应用启动动作和应用验证动作，并根据所述部署路径将所述待部署文件部署到待部署服务器中，以完成应用组件部署，包括：执行所述应用停止动作；若所述应用停止动作执行失败，则结束所述应用组件的部署流程；若所述应用停止动作执行完成，则执行所述部署前动作；若所述部署前动作执行失败，则结束所述应用组件的部署流程；若执行完所述部署前动作，则根据所述部署路径将所述待部署文件部署到待部署服务器中，并执行部署后动作；若所述部署后动作执行失败，则结束所述应用组件的部署流程；若所述部署后动作执行完成，则执行所述应用启动动作；若所述应用启动动作执行失败，则结束所述应用组件的部署流程；若所述应用启动动作执行完成，则执行所述应用验证动作；若所述应用验证动作执行失败，则结束所述应用组件的部署流程；若所述应用验证动作执行完成，则确定完成所述应用组件的部署流程。
- 根据权利要求19所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时实现所述方法还包括：检测所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作、所述应用验证动作分别对应的执行返回值是否为非0；若为0，则确定执行完所述应用停止动作、所述部署前动作、所述部署后动作、所述应用启动动作和所述应用验证动作；若存在为非0的执行返回值，则确定对应执行返回值为非0的执行动作执行失败。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810699030.4 | 2018-06-29 | ||
| CN201810699030.4A CN109086051B (zh) | 2018-06-29 | 2018-06-29 | 应用组件部署方法、装置及计算机存储介质 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2020000811A1 true WO2020000811A1 (zh) | 2020-01-02 |
Family
ID=64834838
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2018/111669 WO2020000811A1 (zh) | 2018-06-29 | 2018-10-24 | 应用组件部署方法、装置及计算机存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109086051B (zh) |
| WO (1) | WO2020000811A1 (zh) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114374677A (zh) * | 2020-10-15 | 2022-04-19 | 中国移动通信集团浙江有限公司 | 跨平台在线发布方法、装置、计算设备及存储介质 |
| CN118378237A (zh) * | 2024-04-26 | 2024-07-23 | 北京京航计算通讯研究所 | 一种基于开发平台的微服务组件动态鉴权方法 |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109871208B (zh) * | 2019-01-04 | 2023-10-17 | 平安科技（深圳）有限公司 | 软件系统生成方法、装置、计算机可读存储介质及服务器 |
| CN112148342A (zh) * | 2019-06-27 | 2020-12-29 | 北京达佳互联信息技术有限公司 | 组件配置方法、装置、电子设备和存储介质 |
| CN111162953B (zh) * | 2019-12-31 | 2023-04-28 | 四川省公安科研中心 | 数据处理方法、系统升级方法和服务器 |
| CN111913721B (zh) * | 2020-07-16 | 2024-06-11 | 中国民航信息网络股份有限公司 | 自动化部署方法、装置、设备及存储介质 |
| CN112698839B (zh) * | 2020-12-30 | 2024-04-12 | 深圳前海微众银行股份有限公司 | 数据中心节点部署方法、装置、系统及计算机存储介质 |
| CN113805935A (zh) * | 2021-09-16 | 2021-12-17 | 平安健康保险股份有限公司 | 代码模块发布方法、装置、计算机设备和可读存储介质 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6892382B1 (en) * | 1999-05-06 | 2005-05-10 | Sun Microsystems, Inc. | Method and apparatus for implementing deployment descriptors in an enterprise environment |
| CN1811702A (zh) * | 2004-08-16 | 2006-08-02 | 国际商业机器公司 | 开发门户应用和自动部署门户应用的系统和方法 |
| CN102360308A (zh) * | 2011-09-29 | 2012-02-22 | 用友软件股份有限公司 | 组件的分布式部署系统和方法 |
| CN104615466A (zh) * | 2015-02-05 | 2015-05-13 | 广州亦云信息技术有限公司 | 一种云平台部署方法和系统 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102404381A (zh) * | 2011-09-02 | 2012-04-04 | 西安交通大学 | 一种云计算环境下基于工作流的软件部署系统及部署方法 |
| US20160246582A1 (en) * | 2015-02-25 | 2016-08-25 | Red Hat, Inc. | Generic Semantic Configuration Service |
| CN105227379A (zh) * | 2015-10-29 | 2016-01-06 | 国家电网公司 | 一种针对java web 应用的集中监控和预警方法 |
-
2018
- 2018-06-29 CN CN201810699030.4A patent/CN109086051B/zh active Active
- 2018-10-24 WO PCT/CN2018/111669 patent/WO2020000811A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6892382B1 (en) * | 1999-05-06 | 2005-05-10 | Sun Microsystems, Inc. | Method and apparatus for implementing deployment descriptors in an enterprise environment |
| CN1811702A (zh) * | 2004-08-16 | 2006-08-02 | 国际商业机器公司 | 开发门户应用和自动部署门户应用的系统和方法 |
| CN102360308A (zh) * | 2011-09-29 | 2012-02-22 | 用友软件股份有限公司 | 组件的分布式部署系统和方法 |
| CN104615466A (zh) * | 2015-02-05 | 2015-05-13 | 广州亦云信息技术有限公司 | 一种云平台部署方法和系统 |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114374677A (zh) * | 2020-10-15 | 2022-04-19 | 中国移动通信集团浙江有限公司 | 跨平台在线发布方法、装置、计算设备及存储介质 |
| CN114374677B (zh) * | 2020-10-15 | 2023-12-26 | 中国移动通信集团浙江有限公司 | 跨平台在线发布方法、装置、计算设备及存储介质 |
| CN118378237A (zh) * | 2024-04-26 | 2024-07-23 | 北京京航计算通讯研究所 | 一种基于开发平台的微服务组件动态鉴权方法 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109086051B (zh) | 2022-03-25 |
| CN109086051A (zh) | 2018-12-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020000811A1 (zh) | 应用组件部署方法、装置及计算机存储介质 | |
| US20210349706A1 (en) | Release lifecycle management system for multi-node application | |
| US10114637B1 (en) | Automatically updating a shared project build platform | |
| CN108399083B (zh) | 一种系统部署方法、装置、电子设备和存储介质 | |
| US10067863B1 (en) | Feature targeting of test automation lab machines | |
| US9003392B2 (en) | Use of cloning in maintenance of virtual appliances | |
| US20040060035A1 (en) | Automated method and system for building, deploying and installing software resources across multiple computer systems | |
| CN113703730A (zh) | 持续集成方法、装置、计算机设备及存储介质 | |
| US20190073292A1 (en) | State machine software tester | |
| KR20060051932A (ko) | 소프트웨어를 실행 동안 업데이트하는 시스템, 방법 및컴퓨터-판독가능 매체 | |
| CN111198695A (zh) | 微服务治理管理平台的自动化部署方法和电子设备 | |
| CN111324522A (zh) | 一种自动化测试系统及方法 | |
| CN102541596A (zh) | 一种操作系统升级方法及装置 | |
| WO2017041499A1 (zh) | 一种软件升级方法、系统和计算机可读存储介质 | |
| CN112953983A (zh) | Sftp传输方法及装置 | |
| CN109683905A (zh) | 一种系统自动发布方法 | |
| CN113721957B (zh) | 对嵌入式设备固件部署升级的自动测试方法、装置和系统 | |
| US10866803B2 (en) | Generating interaction libraries | |
| CN109558147A (zh) | 一种基于Jenkins和Gitlab的持续集成平台构建方法 | |
| US10459698B2 (en) | Framework for generating adapters in an integrated development environment | |
| CN112363731A (zh) | 一种应用自动化部署方法、装置和计算机可读存储介质 | |
| WO2024174904A1 (zh) | 容器实例的管理迁移方法、装置和电子设备及存储介质 | |
| US20220222125A1 (en) | Enforcing system configuration freeze of services deployed via continuous delivery on datacenters configured in cloud platforms | |
| WO2020000810A1 (zh) | 应用组件构建打包方法、装置及计算机存储介质 | |
| CN115357258B (zh) | 应用的部署方法、装置、存储介质及电子装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18924543 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 29/03/2021) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 18924543 Country of ref document: EP Kind code of ref document: A1 |