CN111966744B - Workflow deployment method and device, computer equipment and storage medium - Google Patents
Workflow deployment method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111966744B CN111966744B CN202011128708.7A CN202011128708A CN111966744B CN 111966744 B CN111966744 B CN 111966744B CN 202011128708 A CN202011128708 A CN 202011128708A CN 111966744 B CN111966744 B CN 111966744B
- Authority
- CN
- China
- Prior art keywords
- workflow
- deployment
- configuration file
- warehouse
- listener
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/48—Indexing scheme relating to G06F9/48
- G06F2209/484—Precedence
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5021—Priority
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application relates to a workflow deployment method, a workflow deployment device, computer equipment and a storage medium. The method applied to the workflow deployment server comprises the following steps: reading a configuration file corresponding to a workflow to be deployed; reading a newly added listener in the configuration file to read local warehouse parameters corresponding to the workflow, wherein the priority of the newly added listener is higher than that of a default listener, and the default listener is a listener for calling a front-end workbench to issue the workflow; reading warehouse element parameters in the configuration file; searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compilation package; and loading the searched target compiling package into a container to complete the deployment of the workflow. The method applied to the calling system comprises the following steps: receiving a workflow issuing instruction, wherein the workflow issuing instruction carries a workflow identifier; and (4) according to the workflow identification query and the method, deploying the corresponding workflow. By adopting the method, the research and development workload can be reduced.
Description
Technical Field
The present application relates to the field of workflow technologies, and in particular, to a workflow deployment method and apparatus, a computer device, and a storage medium.
Background
With the development of computer technology, workflow technology appears, and there are two using ways of existing workflows, one is to embed the core package of a workflow into a calling system: the scene is suitable for a service scene which needs to make a large amount of customization on the process flow; another is to expose the interface to the calling system using the workflow engine as an independently deployed service provider.
The solution in which the workflow engine is an independently deployed service provider is generally that kie-wb service integrates operations of development, release, update of processes, and initiation, circulation, etc. of page segment workflows and reporting functions.
However, in the current kie-wb service method, kie-wb service is deployed independently, the resource occupation of single service is high, 2 front-end entries for calling the system become, that is, one is a business front end of the calling system itself, and the other is a self-contained front-end page of kie-wb, and the two page styles cannot be customized, so that the page style is inconsistent with the calling system. Kie-wb service can be integrated into the front end of the calling system, but the calling system front end framework does not match kie-wb, the integration workload is large, the difficulty is high, and the kie-wb service has high internal functional coupling and is not suitable for split integration.
Disclosure of Invention
In view of the above, it is necessary to provide a workflow deployment method, apparatus, computer device and storage medium capable of reducing the development workload in view of the above technical problems.
A workflow deployment method is applied to a workflow deployment server, and comprises the following steps:
reading a configuration file corresponding to a workflow to be deployed;
reading the newly added listener in the configuration file to read the local warehouse parameters corresponding to the workflow through the newly added listener, wherein the priority of the newly added listener is higher than that of a default listener, and the default listener is a listener for calling a front-end workbench to issue the workflow;
reading warehouse element parameters in the configuration file;
searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compiling package;
and loading the searched target compiling package into a container to complete the deployment of the workflow.
In one embodiment, the method for generating the configuration file includes:
acquiring an initial configuration file of a workflow in a workflow deployment server, and deleting a binding parameter between the initial configuration file and a front-end workbench;
newly adding local warehouse parameters and workflow release parameters;
receiving an input workflow, and compiling the workflow to obtain a current compiling packet;
storing the current compiled package into a warehouse corresponding to the local warehouse parameters;
acquiring warehouse element parameters corresponding to the workflow, and storing the warehouse element parameters into the workflow release parameters;
and adding a new listener for monitoring the local warehouse parameters and the workflow release parameters, and configuring the priority of the listener to be higher than the priority of the default listener in the initial configuration file.
In one embodiment, the reading a newly added listener in the configuration file to read a workflow in a local warehouse parameter through the newly added listener includes:
reading a newly added listener in the configuration file, and reading local warehouse parameters to replace default warehouse parameters of the workflow deployment server through the newly added listener;
and acquiring a warehouse corresponding to the local warehouse parameters.
A workflow deployment method is applied to a calling system, and the workflow publishing method comprises the following steps:
receiving a workflow issuing instruction, wherein the workflow issuing instruction carries a workflow identifier;
and inquiring and deploying the corresponding workflow according to the workflow identification, wherein the deployment of the workflow is carried out by the workflow deployment method.
In one embodiment, the workflow issuance instruction further carries a workflow issuance type; the querying and deploying the corresponding workflow according to the workflow identification comprises the following steps:
inquiring corresponding workflow according to the workflow identification;
determining a deployment mode of the workflow according to the workflow release type;
and deploying the corresponding workflow according to the deployment mode.
In one embodiment, the determining the deployment mode of the workflow according to the workflow release type includes at least one of the following:
when the workflow release type is stop release, determining that the deployment mode of the workflow is to restart the workflow deployment server, determining a new configuration file corresponding to the workflow, and deploying the corresponding workflow according to the new configuration file;
when the workflow release type is real-time release, determining that the deployment mode of the workflow is an interface for calling the workflow deployment server to release in real time, reading a new configuration file corresponding to the workflow to be deployed through the interface, and deploying the corresponding workflow according to the new configuration file;
and when the workflow release type is timing release, determining that the deployment mode of the workflow is to call an interface released by the workflow deployment server at timing time, reading and deploying a new configuration file corresponding to the workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
In one embodiment, the invoking an interface issued by the workflow deployment server at a fixed time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file includes:
and when the timing time is up, calling an interface issued by the workflow deployment server, reading a new configuration file corresponding to the workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
A workflow deployment apparatus, the apparatus comprising:
the configuration file reading module is used for reading a configuration file corresponding to the workflow to be deployed;
a local warehouse parameter reading module, configured to read a newly added listener in the configuration file, so as to read a local warehouse parameter corresponding to the workflow through the newly added listener, where a priority of the newly added listener is higher than a priority of a default listener, and the default listener is a listener for invoking a front-end workstation to issue the workflow;
the warehouse element parameter reading module is used for reading warehouse element parameters in the configuration file;
the compiled package query module is used for searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compiled package;
and the first deployment module is used for loading the searched target compiling package into the container so as to complete the deployment of the workflow.
A computer device comprising a memory storing a computer program and a processor implementing the steps of the method of any of the above embodiments when the processor executes the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any of the above embodiments.
The workflow deployment method, the workflow deployment device, the computer equipment and the storage medium configure the deployment of the workflow on the workflow server, namely, reading a configuration file, wherein a listener is added in the configuration file, the priority of the newly added listener is higher than the priority of the calling of the front-end workbench, thus, the newly added local warehouse parameters and the warehouse element parameters are read by using the newly added monitor instead of the front-end workbench, thereby reading the target compiling package, loading the searched target compiling package into a container to complete the deployment of the workflow, not performing the workflow deployment on a front-end workbench, thus not needing to research and develop two sets of front ends, or the front-end workbench is embedded into the front end of the calling system, so that the research and development workload is reduced, in addition, the deployment of the workflow is configured on the workflow server, the workflow and the calling system are decoupled, and the expense of the server is reduced.
Drawings
FIG. 1 is a diagram of an application environment for a workflow deployment method in one embodiment;
FIG. 2 is a flow diagram that illustrates a method for workflow deployment in one embodiment;
FIG. 3 is a flowchart illustrating a workflow deployment method according to another embodiment;
FIG. 4 is an interface diagram of a calling system front end interface in one embodiment;
FIG. 5 is a flow diagram of a workflow deployment method in yet another embodiment;
FIG. 6 is a block diagram of a workflow deployment apparatus in one embodiment;
FIG. 7 is a block diagram showing the construction of a workflow deployment apparatus according to another embodiment;
FIG. 8 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The workflow deployment method provided by the application can be applied to the application environment shown in fig. 1. Where calling system 102 communicates with workflow deployment server 104. Wherein the workflow deployment server 104 is used for implementing development, release, update, and the like of the workflow. For example, when the calling system 102 needs to deploy a certain workflow, the calling system calls the workflow deployment server 104, so that the workflow deployment server 104 can wait for deployment of a configuration file corresponding to the workflow; reading a newly added listener in the configuration file to read local warehouse parameters corresponding to the workflow through the newly added listener, wherein the priority of the newly added listener is higher than that of a default listener, and the default listener is a listener for calling a front-end workbench to issue the workflow; continuously reading warehouse element parameters in the configuration file; searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compilation package; and loading the searched target compiling package into a container to complete the deployment of the workflow. So that the calling system 102 can call the deployed workflow for business processing. According to the workflow deployment method, the deployment of the workflow is configured on the workflow server, the workflow deployment is not performed on the front-end workbench, so that two sets of front ends do not need to be researched and developed, or the front-end workbench is embedded into the front end of the calling system, and the research and development workload is reduced. The calling system 102 may adopt a B/S architecture, that is, access is performed through a browser, and the workflow deployment server 104 may be implemented by an independent server or a server cluster composed of a plurality of servers. Alternatively, the workflow deployment server is kie-server.
In an embodiment, as shown in fig. 2, a workflow deployment method is provided, which is described by taking the method as an example applied to the workflow deployment server in fig. 1, and includes the following steps:
s202: and reading a configuration file corresponding to the workflow to be deployed.
Specifically, the workflow to be deployed may be a newly added workflow or a workflow that is modified from the past workflow, a front-end page of the calling system may add a workflow deployment button, such as a real-time hot release button, a shutdown release button, or a timing hot release button, to determine the workflow to be deployed and a corresponding deployment type manner according to a selection of a user. The configuration file is corresponding to the workflow, and is a file in the workflow deployment server for storing attributes and the like related to the release of the workflow.
S204: and reading the newly added listener in the configuration file so as to read the local warehouse parameters corresponding to the workflow through the newly added listener, wherein the priority of the newly added listener is higher than that of the default listener, and the default listener is used for calling a front-end workbench to issue the workflow.
Specifically, after the project is started, the SpringBoot traverses all entity classes implementing the CommandLineRunner (the interface implements the function executed after the project is started) and executes the run method, and the execution sequence is indicated by using an @ Order annotation on the entity classes. The execution order of the newly added listener is configured to be 1, that is, the priority is the highest, so that the newly added listener is ensured to execute before other listeners, which is higher than kie-server defaults to pass through the default listener of the flow deployed by the front-end workbench kie-wb.
The local warehouse parameter is a preset local warehouse address, that is, the workflow deployment server loads an attribute in a configuration file to which the workflow deployment server kie-server belongs in a run method of the CommandLineRunner class, and reads a local warehouse parameter localRepository, which may be specifically/' x/m 2 _.
S206: and reading warehouse element parameters in the configuration file.
Specifically, the warehouse element parameter refers to a directory hierarchy of a local warehouse corresponding to the workflow, and the warehouse element parameter is preset in the configuration file. The warehouse element parameters may be ab.cd.ef.hi: gk:1.0.4, which is to find the ab/cd/ef/hi/gk/1.0.4/catalog under the local warehouse parameter localRepository.
S208: and searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compiling package.
Specifically, the compiling packages corresponding to the workflows are stored in the warehouse corresponding to the local warehouse parameters and stored according to the warehouse addresses, so that the workflow deployment server can determine the corresponding warehouse addresses according to the warehouse element parameters, and can acquire the corresponding target compiling packages.
S210: and loading the searched target compiling package into a container to complete the deployment of the workflow.
Specifically, when multiple warehouse element parameters exist, the workflow deployment server may cyclically invoke a preset method to create a container, and load the found target compilation package into the container to complete the deployment of the workflow, where the target compilation package includes configuration information such as a workflow flowchart, jar package configuration on which the flowchart depends, and a persistence policy. For example, the workflow deployment server circularly calls kie-server internal interface to realize the createContainer method of the class org.
The workflow deployment method configures the deployment of the workflow on the workflow server, namely reads the configuration file, the newly added monitor is added in the configuration file, the priority of the newly added monitor is higher than the calling priority of the front-end workbench, so that the newly added monitor is used to read the newly added local warehouse parameters and the warehouse element parameters without using the front-end workbench, thereby reading the target compiling package, and the searched target compiling package is loaded into the container to complete the deployment of the workflow instead of the front-end workbench, thus two sets of front ends do not need to be researched and developed (namely the front end corresponding to the business system and the kie-wb front end do not need to be researched and developed simultaneously) or the front-end workbench is embedded into the front end of the calling system (namely the front end corresponding to the business system does not need to be embedded into the front end of the calling system), thereby reducing the research and development workload, in addition, the deployment of the workflow is configured on the workflow server, the workflow is decoupled from the calling system, and the expense of the server is reduced.
In one embodiment, the method for generating the configuration file comprises the following steps: acquiring an initial configuration file of a workflow in a workflow deployment server, and deleting a binding parameter between the initial configuration file and a front-end workbench; newly adding local warehouse parameters and workflow release parameters; receiving an input workflow, and compiling the workflow to obtain a current compiling packet; storing the current compiled package into a warehouse corresponding to the local warehouse parameters; acquiring warehouse element parameters corresponding to the workflow, and storing the warehouse element parameters into workflow release parameters; and adding a listener for monitoring the local warehouse parameters and the workflow release parameters, and configuring the priority of the listener to be higher than the priority of the default listener in the initial configuration file.
Specifically, the initial configuration file is an original configuration file in the workflow deployment server, and the initial row location file, i.e., setev.sh, is a configuration file used by kie-server service deployed in tomcat middleware, and is mainly used for defining configuration information such as a memory size, a database dialect, a transaction mechanism, and a kie-wb address. The workflow deployment server removes the binding parameter dorg.kie.server.controller configuration item of the front-end working platform kie-wb in the environment configuration of kie-server, so that the workflow deployment server kie-server does not automatically search the front-end working platform kie-wb.
Then, adding a local warehouse parameter, here represented by localrepositivity, and adding a workflow release parameter, here represented by releaseIds.
The localrepositivity parameter specifies kie a root directory where the regular jar packets or the flow are read by the server, so as to uniformly maintain the jar packets related to the workflow. After receiving a new workflow sent by a research and development terminal, compiling the workflow to obtain a current compiling packet; storing the current compiling package into a warehouse corresponding to the local warehouse parameters, namely under the root directory, so as to obtain a releaseIds parameter, wherein the releaseIds parameter designates a warehouse three-element id set corresponding to a flow to be deployed, such as a maven warehouse three-element id set, and if a business system uses a price inquiry flow, items are configured in a configuration file: ab.cd.ef.bpm: quotation:1.0.0, if more, continuing to add configuration items later in the profile set writing specification.
And adding a new listener to the workflow deployment server, realizing a CommandLineRunner interface of the spring framework, configuring the execution sequence to be 1, ensuring that the execution is performed before other listeners and is prior to kie-server to be superior to the listener of the deployment flow through kie-wb by default.
In the embodiment, the deployment of the workflow is realized by the workflow deployment server by modifying the configuration file, so that two sets of front ends do not need to be developed, or a front-end workbench is embedded into the front end of the calling system, the development workload is reduced, and in addition, the deployment of the workflow is configured on the workflow server, the workflow and the calling system are decoupled, and the overhead of the server is reduced.
In one embodiment, reading a newly added listener in the configuration file to read the workflow in the local warehouse parameters through the newly added listener includes: reading a newly added listener in the configuration file, and reading local warehouse parameters to replace default warehouse parameters of the workflow deployment server through the newly added listener; and acquiring a warehouse corresponding to the local warehouse parameters.
Specifically, the workflow deployment server loads an attribute in a configuration file to which kie-server belongs in a run method of a CommandLineRunner class, reads a localRepository attribute, puts the localRepository attribute into an attribute set of java.
Because the warehouse stores the dependency packages called by all the business systems, the dependency packages are in the server level, the process renaming condition may exist with other business services, if the renaming occurs, the original jar package can be covered by the newly uploaded jar package, and therefore the file isolation of the process library and the warehouse is achieved by covering the address of the warehouse, and the confusion with other business systems is avoided.
In one embodiment, a specific example is given to explain a workflow deployment method, which specifically includes:
the workflow deployment server loads the attribute in the configuration file of the kie-server in the run method of the Command LineRunner class, reads the localRepeatory attribute, puts the localRepeatory attribute into the attribute set of java.
And the workflow deployment server reads the releaseIDs attributes as a set, rewrites the container creating logic and loads each jar packet corresponding to the releaseIDs into the KieContainerResource object.
The workflow deployment server circularly calls kie-server internal interface realization type org.kie.server.services.impl.KieServer impl realization type createContainer method, creates a flow container of jar packets corresponding to releaseIDs, defaults to automatically deploy and issue flows after the creation is successful, and then the flows are called by a calling system through kie-server exposed flows and task operation API interfaces.
In one embodiment, as shown in fig. 3, a workflow deployment method is provided, which is described by taking the application of the method to the calling system in fig. 1 as an example, and includes the following steps:
s302: and receiving a workflow issuing instruction, wherein the workflow issuing instruction carries the workflow identification.
Specifically, the workflow issuance instruction may be received through a front-end page of the calling system, and the front-end page of the calling system may add a workflow deployment button, such as a real-time hot issue button, a shutdown issue button, or a timing hot issue button, and determine a workflow to be deployed and a corresponding deployment type manner according to a selection of a user, for example, determine a corresponding workflow according to a workflow identifier.
S304: and inquiring and deploying the corresponding workflow according to the workflow identification, wherein the deployment of the workflow is carried out by the workflow deployment method in any embodiment.
Specifically, the deployment of the workflow may be as described above, and is not described herein. For the query, the API interface provided by the workflow deployment server may be queried according to the corresponding workflow identifier, and the deployment of the workflow through the API interface includes real-time deployment, shutdown deployment, and timed deployment.
According to the workflow deployment method, the deployment of the workflow is configured on the workflow server, namely the configuration file is read, the newly added monitor is added in the configuration file, the priority of the newly added monitor is higher than the calling priority of the front-end workbench, so that the front-end workbench is not used, the newly added local warehouse parameters and the warehouse element parameters are read by the newly added monitor, the target compiling package is read, the searched target compiling package is loaded into the container to complete the deployment of the workflow, the workflow deployment is not carried out on the front-end workbench, two sets of front ends do not need to be researched and developed, or the front-end workbench is embedded into the front end of the calling system, the research and development workload is reduced, in addition, the deployment of the workflow is configured on the workflow server, the workflow is decoupled from the calling system, and the expense of the server is reduced.
In one embodiment, the workflow issuance instruction further carries a workflow deployment type; inquiring and deploying the corresponding workflow according to the workflow identification, wherein the method comprises the following steps: inquiring corresponding workflow according to the workflow identification; determining a deployment mode of the workflow according to the deployment type of the workflow; and deploying the corresponding workflow according to the deployment mode.
Specifically, workflow deployment types include, but are not limited to: real-time hot distribution, timed hot distribution, and shutdown distribution. The deployment mode of the workflow includes but is not limited to restarting the workflow deployment server to re-read the configuration file for deployment, and without restarting the workflow deployment server, re-reading the configuration file for deployment through an interface provided by the workflow deployment server.
Thus, different deployment modes are determined according to different deployment types, and deployment confusion can be avoided.
In one embodiment, determining the deployment mode of the workflow according to the deployment type of the workflow comprises at least one of the following: when the workflow deployment type is shutdown release, determining that the deployment mode of the workflow is restarting the workflow deployment server, determining a new configuration file corresponding to the workflow, and deploying the corresponding workflow according to the new configuration file; when the workflow deployment type is released in real time, determining that the deployment mode of the workflow is an interface which is released by a workflow deployment server and called in real time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file; and when the workflow deployment type is timed release, determining that the deployment mode of the workflow is to call an interface released by a workflow deployment server at a timed time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
Specifically, the shutdown release is to restart the workflow deployment server, so that the workflow deployment server reads all the configuration files again, deploys the workflow, and the calling system can call the corresponding workflow.
The real-time hot release (after the hot release is successful, the newly created process flows are circulated according to the newly released process flow chart, and the generated process flow data is not influenced) and the timed release are both interfaces for calling the workflow deployment server to release, the new configuration file corresponding to the deployment workflow is read through the interfaces, the corresponding workflow is deployed according to the new configuration file, and the difference is that one real-time process is timed.
Specifically, the framework adopted by the calling system is a micro-service framework, the framework is composed of micro-services of a plurality of specific service modules and a plurality of public component micro-services, the workflow deployment server kie-server is also taken as a service provider to be incorporated into the micro-service framework system, a hot release button is additionally arranged in a front-end page of the micro-service of the calling system, after the button is clicked, a front-end js calls a compiling flow exposed by the workflow deployment server kie-server to release an API interface, the configuration file is read again, and updating is deployed.
Optionally, in the timed hot release, an interface released by the workflow deployment server is called at a timed time, a new configuration file corresponding to the deployment workflow is read through the interface, and the corresponding workflow is deployed according to the new configuration file, including: and when the timing time is up, calling an interface issued by the workflow deployment server, reading a new configuration file corresponding to the workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
The scheduling microservice is a public component microservice of a calling system, mainly provides operations of timing task configuration, execution and the like, creates a timing task configuration item aiming at a flow issuing action, then adds a timing issuing flow function item configuration automatic task in a scheduling task system of the calling system on a front-end page, is used for setting specific issuing effective triggering time when selecting timing thermal issuing, as shown in fig. 4, triggers a timing task when a specified time is reached, calls an interface of a workflow deployment server kie-server microservice by a background, reads a configuration file again, and deploys and updates.
Specifically, referring to fig. 5, fig. 5 is a flowchart of a workflow deployment method in yet another embodiment, where the workflow deployment method may include:
the method comprises the steps that a developer draws or updates a workflow at a workflow deployment server, compiles the workflow, stores a compilation package in a localreposition directory, and then modifies a configuration file.
The calling system receives the workflow identification and the workflow deployment type input by the calling system through the front-end interface, and judges according to the workflow deployment type, for example, whether the workflow deployment is stopped for issuing is judged firstly, if so, kie-server service is restarted, and then automatic deployment is performed according to the mode. If the workflow is not issued in a halt mode, whether the workflow is issued in a timing mode or not is continuously judged, if the workflow is issued in a timing mode, an interface issued by the workflow deployment server is called when the timing time is up, a new configuration file corresponding to the workflow is read through the interface, and the corresponding workflow is deployed according to the new configuration file. And if the workflow is released in real time, determining that the deployment mode of the workflow is an interface released by a real-time calling workflow deployment server, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
It should be understood that although the steps in the flowcharts of fig. 2, 3 and 5 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2, 3 and 5 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 6, there is provided a workflow deployment apparatus applied to a workflow deployment server, including: a configuration file reading module 100, a local warehouse parameter reading module 200, a warehouse element parameter reading module 300, a compiled package query module 400, and a first deployment module 500, wherein:
a configuration file reading module 100, configured to read a configuration file corresponding to a workflow to be deployed;
a local warehouse parameter reading module 200, configured to read a newly added listener in the configuration file, so as to read a local warehouse parameter corresponding to the workflow through the newly added listener, where a priority of the newly added listener is higher than a priority of a default listener, and the default listener is a listener for invoking a front-end workstation to issue the workflow;
a warehouse element parameter reading module 300, configured to read warehouse element parameters in the configuration file;
the compiled package query module 400 is configured to search, according to the warehouse element parameters, a warehouse corresponding to the local warehouse parameters to obtain a corresponding target compiled package;
a first deployment module 500, configured to load the found target compilation package into a container to complete deployment of the workflow.
In one embodiment, the workflow deployment apparatus may further include:
the binding parameter deleting module is used for acquiring an initial configuration file of the workflow in the workflow deployment server and deleting the binding parameters with the front-end workbench in the initial configuration file;
the newly-added module is used for newly adding local warehouse parameters and workflow release parameters;
the compiling module is used for receiving the input workflow and compiling the workflow to obtain a current compiling package;
the compiling package storage module is used for storing the current compiling package into a warehouse corresponding to the local warehouse parameters;
the warehouse element parameter storage module is used for acquiring the warehouse element parameters corresponding to the workflow and storing the warehouse element parameters into the workflow release parameters;
and the listener newly-added module is used for newly adding a listener for monitoring the local warehouse parameters and the workflow release parameters, and the priority of the configured listener is higher than the priority of the default listener in the initial configuration file.
In one embodiment, the local warehouse parameter reading module 200 may include:
the replacing unit is used for reading a newly added listener in the configuration file so as to read the local warehouse parameters through the newly added listener to replace the default warehouse parameters of the workflow deployment server;
and the reading unit is used for acquiring the warehouse corresponding to the local warehouse parameters.
In one embodiment, as shown in fig. 7, there is provided a workflow deployment apparatus, applied to a calling system, including: a receiving module 600 and a second deployment module 700, wherein:
a receiving module 600, configured to receive a workflow issuing instruction, where the workflow issuing instruction carries a workflow identifier;
the second deployment module 700 is configured to query and deploy a corresponding workflow according to the workflow identifier, where the deployment of the workflow is performed by the workflow deployment method according to any of the embodiments described above.
In one embodiment, the workflow issuance instruction further carries a workflow deployment type; the second deployment module 700 may include:
the workflow inquiry unit is used for inquiring the corresponding workflow according to the workflow identification;
the deployment mode determining unit is used for determining the deployment mode of the workflow according to the deployment type of the workflow;
and the deployment unit is used for deploying the corresponding workflow according to the deployment mode.
In one embodiment, the deployment mode determining unit is configured to determine that the deployment mode of the workflow is to restart the workflow deployment server, determine a new configuration file corresponding to the workflow, and deploy the corresponding workflow according to the new configuration file when the deployment type of the workflow is shutdown release; when the workflow deployment type is released in real time, determining that the deployment mode of the workflow is an interface which is released by a workflow deployment server and called in real time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file; and when the workflow deployment type is timed release, determining that the deployment mode of the workflow is to call an interface released by a workflow deployment server at a timed time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
In one embodiment, the deployment unit includes:
and the deployment subunit is used for calling an interface issued by the workflow deployment server when the timing time is reached, reading a new configuration file corresponding to the workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
For specific definition of the workflow deployment apparatus, reference may be made to the above definition of the workflow deployment method, which is not described herein again. The various modules in the workflow deployment apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 8. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used to store configuration files. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a workflow deployment method.
Those skilled in the art will appreciate that the architecture shown in fig. 8 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program: reading a configuration file corresponding to a workflow to be deployed; reading a newly added listener in the configuration file to read local warehouse parameters corresponding to the workflow through the newly added listener, wherein the priority of the newly added listener is higher than that of a default listener, and the default listener is a listener for calling a front-end workbench to issue the workflow; reading warehouse element parameters in the configuration file; searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compilation package; and loading the searched target compiling package into a container to complete the deployment of the workflow.
In one embodiment, a method for generating a configuration file involved in execution of a computer program by a processor includes: acquiring an initial configuration file of a workflow in a workflow deployment server, and deleting a binding parameter between the initial configuration file and a front-end workbench; newly adding local warehouse parameters and workflow release parameters; receiving an input workflow, and compiling the workflow to obtain a current compiling packet; storing the current compiled package into a warehouse corresponding to the local warehouse parameters; acquiring warehouse element parameters corresponding to the workflow, and storing the warehouse element parameters into workflow release parameters; and adding a listener for monitoring the local warehouse parameters and the workflow release parameters, and configuring the priority of the listener to be higher than the priority of the default listener in the initial configuration file.
In one embodiment, the reading of the new listener in the configuration file by the processor when executing the computer program to read the workflow in the local warehouse parameter by the new listener comprises: reading a newly added listener in the configuration file, and reading local warehouse parameters to replace default warehouse parameters of the workflow deployment server through the newly added listener; and acquiring a warehouse corresponding to the local warehouse parameters.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program: receiving a workflow issuing instruction, wherein the workflow issuing instruction carries a workflow identifier; and inquiring and deploying the corresponding workflow according to the workflow identification, wherein the deployment of the workflow is performed by the workflow deployment method in any embodiment.
In one embodiment, the workflow issuance instruction involved in the execution of the computer program by the processor also carries the workflow deployment type; querying and deploying a corresponding workflow according to a workflow identification, which is implemented when a processor executes a computer program, includes: inquiring corresponding workflow according to the workflow identification; determining a deployment mode of the workflow according to the deployment type of the workflow; and deploying the corresponding workflow according to the deployment mode.
In one embodiment, determining a deployment of the workflow according to the deployment type of the workflow, implemented when the processor executes the computer program, includes at least one of: when the workflow deployment type is shutdown release, determining that the deployment mode of the workflow is restarting the workflow deployment server, determining a new configuration file corresponding to the workflow, and deploying the corresponding workflow according to the new configuration file; when the workflow deployment type is released in real time, determining that the deployment mode of the workflow is an interface which is released by a workflow deployment server and called in real time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file; and when the workflow deployment type is timed release, determining that the deployment mode of the workflow is to call an interface released by a workflow deployment server at a timed time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
In one embodiment, the invoking of an interface issued by a workflow deployment server at a regular time, which is implemented when a processor executes a computer program, reads a new configuration file corresponding to a deployment workflow through the interface, and deploys the corresponding workflow according to the new configuration file includes: and when the timing time is up, calling an interface issued by the workflow deployment server, reading a new configuration file corresponding to the workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: reading a configuration file corresponding to a workflow to be deployed; reading a newly added listener in the configuration file to read local warehouse parameters corresponding to the workflow through the newly added listener, wherein the priority of the newly added listener is higher than that of a default listener, and the default listener is a listener for calling a front-end workbench to issue the workflow; reading warehouse element parameters in the configuration file; searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compilation package; and loading the searched target compiling package into a container to complete the deployment of the workflow.
In one embodiment, a method of generating a configuration file involved in execution of a computer program by a processor comprises: acquiring an initial configuration file of a workflow in a workflow deployment server, and deleting a binding parameter between the initial configuration file and a front-end workbench; newly adding local warehouse parameters and workflow release parameters; receiving an input workflow, and compiling the workflow to obtain a current compiling packet; storing the current compiled package into a warehouse corresponding to the local warehouse parameters; acquiring warehouse element parameters corresponding to the workflow, and storing the warehouse element parameters into workflow release parameters; and adding a listener for monitoring the local warehouse parameters and the workflow release parameters, and configuring the priority of the listener to be higher than the priority of the default listener in the initial configuration file.
In one embodiment, a computer program, when executed by a processor, that reads a new listener in a configuration file to read a workflow in a local warehouse parameter via the new listener, comprises: reading a newly added listener in the configuration file, and reading local warehouse parameters to replace default warehouse parameters of the workflow deployment server through the newly added listener; and acquiring a warehouse corresponding to the local warehouse parameters.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving a workflow issuing instruction, wherein the workflow issuing instruction carries a workflow identifier; and inquiring and deploying the corresponding workflow according to the workflow identification, wherein the deployment of the workflow is performed by the workflow deployment method in any embodiment.
In one embodiment, the workflow issuance instructions involved in the execution of the computer program by the processor also carry the workflow deployment type; querying and deploying a corresponding workflow according to a workflow identification, implemented when the computer program is executed by a processor, includes: inquiring corresponding workflow according to the workflow identification; determining a deployment mode of the workflow according to the deployment type of the workflow; and deploying the corresponding workflow according to the deployment mode.
In one embodiment, determining a deployment of a workflow according to a workflow deployment type, implemented when the computer program is executed by a processor, includes at least one of: when the workflow deployment type is shutdown release, determining that the deployment mode of the workflow is restarting the workflow deployment server, determining a new configuration file corresponding to the workflow, and deploying the corresponding workflow according to the new configuration file; when the workflow deployment type is released in real time, determining that the deployment mode of the workflow is an interface which is released by a workflow deployment server and called in real time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file; and when the workflow deployment type is timed release, determining that the deployment mode of the workflow is to call an interface released by a workflow deployment server at a timed time, reading a new configuration file corresponding to the deployment workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
In one embodiment, an interface issued by a workflow deployment server is called at a timing when a computer program is executed by a processor, a new configuration file corresponding to a deployment workflow is read through the interface, and the corresponding workflow is deployed according to the new configuration file, including: and when the timing time is up, calling an interface issued by the workflow deployment server, reading a new configuration file corresponding to the workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A workflow deployment method is applied to a workflow deployment server, and comprises the following steps:
reading a configuration file corresponding to a workflow to be deployed;
reading the newly added listener in the configuration file to read the local warehouse parameters corresponding to the workflow through the newly added listener, wherein the priority of the newly added listener is higher than that of a default listener, and the default listener is a listener for calling a front-end workbench to issue the workflow;
reading warehouse element parameters in the configuration file;
searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compiling package;
and loading the searched target compiling package into a container to complete the deployment of the workflow.
2. The method according to claim 1, wherein the method for generating the configuration file comprises:
acquiring an initial configuration file of a workflow in a workflow deployment server, and deleting a binding parameter between the initial configuration file and a front-end workbench;
newly adding local warehouse parameters and workflow release parameters;
receiving an input workflow, and compiling the workflow to obtain a current compiling packet;
storing the current compiled package into a warehouse corresponding to the local warehouse parameters;
acquiring warehouse element parameters corresponding to the workflow, and storing the warehouse element parameters into the workflow release parameters;
and adding a new listener for monitoring the local warehouse parameters and the workflow release parameters, and configuring the priority of the listener to be higher than the priority of the default listener in the initial configuration file.
3. The method of claim 2, wherein reading the newly added listener in the configuration file to read the workflow in the local warehouse parameters through the newly added listener comprises:
reading a newly added listener in the configuration file, and reading local warehouse parameters to replace default warehouse parameters of the workflow deployment server through the newly added listener;
and acquiring a warehouse corresponding to the local warehouse parameters.
4. A workflow deployment method is applied to a calling system, and comprises the following steps:
receiving a workflow issuing instruction, wherein the workflow issuing instruction carries a workflow identifier;
inquiring and deploying the corresponding workflow according to the workflow identification, wherein the deployment of the workflow is carried out by the workflow deployment method of any one of claims 1 to 3.
5. The method of claim 4, wherein the workflow issuance instruction further carries a workflow issuance type; the querying and deploying the corresponding workflow according to the workflow identification comprises the following steps:
inquiring corresponding workflow according to the workflow identification;
determining a deployment mode of the workflow according to the workflow release type;
and deploying the corresponding workflow according to the deployment mode.
6. The method of claim 5, wherein determining the deployment of the workflow according to the workflow release type comprises at least one of:
when the workflow release type is stop release, determining that the deployment mode of the workflow is to restart the workflow deployment server, determining a new configuration file corresponding to the workflow, and deploying the corresponding workflow according to the new configuration file;
when the workflow release type is real-time release, determining that the deployment mode of the workflow is an interface for calling the workflow deployment server to release in real time, reading a new configuration file corresponding to the workflow to be deployed through the interface, and deploying the corresponding workflow according to the new configuration file;
and when the workflow release type is timing release, determining that the deployment mode of the workflow is an interface released by calling the workflow deployment server when the timing time is reached, reading and deploying a new configuration file corresponding to the workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
7. The method according to claim 6, wherein the invoking an interface issued by the workflow deployment server at a regular time, reading a new configuration file corresponding to the deployment of the workflow through the interface, and deploying the corresponding workflow according to the new configuration file comprises:
and when the timing time is up, calling an interface issued by the workflow deployment server, reading a new configuration file corresponding to the workflow through the interface, and deploying the corresponding workflow according to the new configuration file.
8. A workflow deployment apparatus, the apparatus comprising:
the configuration file reading module is used for reading a configuration file corresponding to the workflow to be deployed;
a local warehouse parameter reading module, configured to read a newly added listener in the configuration file, so as to read a local warehouse parameter corresponding to the workflow through the newly added listener, where a priority of the newly added listener is higher than a priority of a default listener, and the default listener is a listener for invoking a front-end workstation to issue the workflow;
the warehouse element parameter reading module is used for reading warehouse element parameters in the configuration file;
the compiled package query module is used for searching a warehouse corresponding to the local warehouse parameters according to the warehouse element parameters to obtain a corresponding target compiled package;
and the first deployment module is used for loading the searched target compiling package into the container so as to complete the deployment of the workflow.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 3 or 4 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 3 or 4 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011128708.7A CN111966744B (en) | 2020-10-21 | 2020-10-21 | Workflow deployment method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011128708.7A CN111966744B (en) | 2020-10-21 | 2020-10-21 | Workflow deployment method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111966744A CN111966744A (en) | 2020-11-20 |
| CN111966744B true CN111966744B (en) | 2021-01-15 |
Family
ID=73387113
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011128708.7A Active CN111966744B (en) | 2020-10-21 | 2020-10-21 | Workflow deployment method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111966744B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112463141B (en) * | 2020-11-25 | 2021-12-14 | 北京航空航天大学 | BPMN-based micro-service workflow deployment method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104133685A (en) * | 2014-08-05 | 2014-11-05 | 广州唯品会网络技术有限公司 | Method and system for front-end development of website |
| CN110275811A (en) * | 2019-05-24 | 2019-09-24 | 北京指掌易科技有限公司 | A kind of method of mobile terminal H5 application behavior monitoring |
| CN110874278A (en) * | 2019-11-13 | 2020-03-10 | 深圳前海微众银行股份有限公司 | Embedding method of external system, workflow system, device and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10021062B2 (en) * | 2005-07-01 | 2018-07-10 | Cirius Messaging Inc. | Secure electronic mail system |
| US7865510B2 (en) * | 2006-07-12 | 2011-01-04 | LitCentral, Inc | Internet user-accessible database |
| US10303538B2 (en) * | 2015-03-16 | 2019-05-28 | Microsoft Technology Licensing, Llc | Computing system issue detection and resolution |
-
2020
- 2020-10-21 CN CN202011128708.7A patent/CN111966744B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104133685A (en) * | 2014-08-05 | 2014-11-05 | 广州唯品会网络技术有限公司 | Method and system for front-end development of website |
| CN110275811A (en) * | 2019-05-24 | 2019-09-24 | 北京指掌易科技有限公司 | A kind of method of mobile terminal H5 application behavior monitoring |
| CN110874278A (en) * | 2019-11-13 | 2020-03-10 | 深圳前海微众银行股份有限公司 | Embedding method of external system, workflow system, device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111966744A (en) | 2020-11-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110912724B (en) | Parameter-driven automatic service arrangement method and device | |
| CN108829459B (en) | Nginx server-based configuration method and device, computer equipment and storage medium | |
| CN109032631B (en) | Application program patch package obtaining method and device, computer equipment and storage medium | |
| CN111068328B (en) | Game advertisement configuration form generation method, terminal equipment and medium | |
| US20040088397A1 (en) | System and method for management of software applications | |
| CN110427258B (en) | Resource scheduling control method and device based on cloud platform | |
| CN110321131B (en) | Service component packaging method, system and server | |
| CN111897539A (en) | Method and device for deploying applications according to service roles | |
| KR20090056238A (en) | System and method for operating domain profile using database in a core framework for sdr mobile terminals | |
| CN112685091A (en) | Service request processing method, device, equipment and medium based on big data | |
| US20100313207A1 (en) | Service provider management device, service provider management program, and service provider management method | |
| CN104699503A (en) | Method and device for replacing function execution logic in Android system | |
| CN111399860B (en) | Light application deployment method, light application deployment device, computer equipment and storage medium | |
| CN111966744B (en) | Workflow deployment method and device, computer equipment and storage medium | |
| CN114443294B (en) | Big data service component deployment method, system, terminal and storage medium | |
| CN116911588A (en) | Business process execution method, device, equipment and storage medium | |
| CN112596746B (en) | Application installation package generation method and device, computer equipment and storage medium | |
| CN114020840A (en) | Data processing method, device, server, storage medium and product | |
| JP2006065462A (en) | Software system, software stopping method, program, and storage medium | |
| CN110806891B (en) | Method and device for generating software version of embedded device | |
| CN116680003A (en) | Front-end plug-in system | |
| CN111124386B (en) | Animation event processing method, device, equipment and storage medium based on Unity | |
| CN113867776A (en) | Method and device for publishing middle station application, electronic equipment and storage medium | |
| CN106775629B (en) | Search file generation method and device | |
| CN112558975B (en) | Method and device for switching codes of components, electronic equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |