Update Method, Device, Server, Medium and Product for Process Orchestration

Abstract

An embodiment of the present invention provides a method, device, server, medium, and product for updating process orchestration. The method includes: determining a process node to be opened in a target process body; generating corresponding foreground access specification interface data according to the process node to be opened, where the foreground access specification interface data includes a parameter of a foreground service identity; if a data acquisition request sent by a foreground server is received, sending the foreground access specification interface data to the foreground server, where the foreground access specification interface data is used to instruct the foreground server to generate a corresponding development data packet to be updated, and the development data packet to be updated includes a foreground service identity; if it is monitored that a development data packet update condition for the process node to be opened is satisfied, updating the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding foreground service identity. The decoupling between the middleware server and the foreground server is realized, and the efficiency of meeting business requirements is effectively improved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the technical field of data processing, and in particular, to an update method, device, server, medium, and product for process orchestration. Background Art

[0002] With the development of the large-middle-small-front architecture and the prevalence of process orchestration, in order to precipitate general services, the middle platform generally provides a unified and standardized process body. The front end then realizes personalized customization of some process nodes in the process body according to business needs to jointly achieve business requirements.

[0003] Currently, there are mainly two methods for the middle platform to interact with the front-end process nodes when precipitating the general service process body to jointly achieve process orchestration. One is that the front end gives the personalized requirements of the process nodes. The middle platform not only needs to manually develop the process body but also needs to manually develop the process nodes with personalized requirements according to the personalized requirements of the process nodes. The other is that the front end independently develops personalized process nodes according to business needs and provides a remote call interface (abbreviation: rpc interface). The middle platform accesses the rpc interface and requires a small amount of manual development and update to meet business needs.

[0004] In the process of implementing the present invention, the inventor found that there are at least the following problems in the prior art: As long as the business requirements of the front end change, the middle platform needs to manually perform adaptive development and update to meet the business needs. Therefore, the human support cost of the middle platform is relatively large, the coupling degree between the middle platform and the front end is relatively high, and the efficiency of meeting business needs is relatively low. Summary of the Invention

[0005] The embodiments of the present invention provide an update method, device, server, medium, and product for process orchestration to solve the technical problems in the prior art that the human support cost of the middle platform is relatively large, the coupling degree between the middle platform and the front end is relatively high, and the efficiency of meeting business needs is relatively low.

[0006] In a first aspect, the embodiments of the present invention provide an update method for process orchestration. The method is applied to a middle platform server, and the method includes:

[0007] Determine the process nodes to be opened in the target process body;

[0008] Generate corresponding front-end access specification interface data according to the process nodes to be opened. The front-end access specification interface data includes parameters of the front-end business identity identifier;

[0009] If a data acquisition request sent by the front - end server is received, the front - end access specification interface data is sent to the front - end server. The front - end access specification interface data is used to instruct the front - end server to generate a corresponding development data packet to be updated, and the development data packet to be updated includes a front - end service identity.

[0010] If it is monitored that the development data packet update condition for the to - be - opened process node is met, the development data packet of the to - be - opened process node is updated according to the development data packet to be updated and the corresponding front - end service identity.

[0011] In a second aspect, an embodiment of the present invention provides a method for updating process orchestration. The method is applied to a front - end server, and the method includes:

[0012] Send a data acquisition request corresponding to the to - be - opened process node to the middle - end server;

[0013] Receive the front - end access specification interface data corresponding to the to - be - opened process node sent by the middle - end server. The access specification interface data includes parameters of the front - end service identity;

[0014] Generate a corresponding development data packet to be updated according to the front - end access specification interface data. The development data packet to be updated includes a front - end service identity, so that the middle - end server updates the development data packet of the to - be - opened process node according to the development data packet to be updated and the corresponding front - end service identity.

[0015] In a third aspect, an embodiment of the present invention provides an apparatus for updating process orchestration. The apparatus is located in the middle - end server, and the apparatus includes:

[0016] A determination module, configured to determine the to - be - opened process node in the target process subject;

[0017] A generation module, configured to generate corresponding front - end access specification interface data according to the to - be - opened process node. The front - end access specification interface data includes parameters of the front - end service identity;

[0018] A sending module, configured to, if a data acquisition request sent by the front - end server is received, send the front - end access specification interface data to the front - end server. The front - end access specification interface data is used to instruct the front - end server to generate a corresponding development data packet to be updated, and the development data packet to be updated includes a front - end service identity;

[0019] An update module, configured to, if it is monitored that the development data packet update condition for the to - be - opened process node is met, update the development data packet of the to - be - opened process node according to the development data packet to be updated and the corresponding front - end service identity.

[0020] Fourth aspect, an embodiment of the present invention provides an update device for process orchestration. The device is located in the front-end server and includes:

[0021] A sending module, configured to send a data acquisition request corresponding to a process node to be opened to the middle-tier server;

[0022] A receiving module, configured to receive the front-end access specification interface data corresponding to the process node to be opened sent by the middle-tier server, where the access specification interface data includes parameters of the front-end service identity;

[0023] A generating module, configured to generate a corresponding development data packet to be updated according to the front-end access specification interface data. The development data packet to be updated includes the front-end service identity, so that the middle-tier server updates the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front-end service identity.

[0024] Fifth aspect, an embodiment of the present invention provides a middle-tier server, including: at least one processor, a memory, and a transceiver;

[0025] The processor, the memory, and the transceiver are interconnected through a circuit;

[0026] The memory stores computer execution instructions; the transceiver is configured to send and receive data with the front-end server;

[0027] The at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the method described in any item of the first aspect.

[0028] Sixth aspect, an embodiment of the present invention provides a front-end server, including: at least one processor, a memory, and a transceiver;

[0029] The processor, the memory, and the transceiver are interconnected through a circuit;

[0030] The memory stores computer execution instructions; the transceiver is configured to send and receive data with the middle-tier server;

[0031] The at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the method described in any item of the second aspect.

[0032] Seventh aspect, an embodiment of the present invention provides a computer-readable storage medium, in which computer execution instructions are stored. When the computer execution instructions are executed by a processor, they are used to implement the method described in any item of the first aspect or the second aspect.

[0033] In an eighth aspect, an embodiment of the present invention provides a computer program product, including a computer program which, when executed by a processor, implements the method described in any one of the first aspect or the second aspect.

[0034] The method, apparatus, server, medium and product for updating process orchestration provided by the embodiments of the present invention determine the process nodes to be opened in the target process body; generate corresponding front-end access specification interface data according to the process nodes to be opened, and the front-end access specification interface data includes parameters of the front-end service identity; if a data acquisition request sent by the front-end server is received, the front-end access specification interface data is sent to the front-end server, and the front-end access specification interface data is used to instruct the front-end server to generate a corresponding development data packet to be updated, and the development data packet to be updated includes the front-end service identity; if it is monitored that the development data packet update condition of the process node to be opened is satisfied, the development data packet of the process node to be opened is updated according to the development data packet to be updated and the corresponding front-end service identity. Since in the process of updating process orchestration, the front-end server is only responsible for the personalized customization of the process nodes to be developed, that is, generating the development data packet to be updated. The middleware server is only responsible for updating the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front-end service identity, realizing the decoupling between the middleware server and the front-end server, and the middleware server does not require human support and can be updated automatically, thereby effectively improving the efficiency of meeting business requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present disclosure and, together with the specification, are used to explain the principles of the present disclosure.

[0036] Figure 1 is a network architecture diagram that can implement the method for updating process orchestration according to the embodiments of the present invention;

[0037] Figure 2 is an application scenario diagram that can implement the method for updating process orchestration according to the embodiments of the present invention;

[0038] Figure 3 is another application scenario diagram that can implement the method for updating process orchestration according to the embodiments of the present invention;

[0039] Figure 4 is a flowchart of the method for updating process orchestration provided by an embodiment of the present invention;

[0040] Figure 5 is a flowchart of the method for updating process orchestration provided by another embodiment of the present invention;

[0041] Figure 6 It is a flowchart of the method for updating process orchestration provided by another embodiment of the present invention;

[0042] Figure 7 It is a flowchart of the method for updating process orchestration provided by still another embodiment of the present invention;

[0043] Figure 8 It is a structural diagram of the device for updating process orchestration provided by an embodiment of the present invention;

[0044] Figure 9 It is a structural diagram of the device for updating process orchestration provided by another embodiment of the present invention;

[0045] Figure 10 It is a structural diagram of the middle - tier server for implementing the method for updating process orchestration according to an embodiment of the present invention;

[0046] Figure 11 It is a structural diagram of the front - end server for implementing the method for updating process orchestration according to an embodiment of the present invention;

[0047] Figure 12 It is a block diagram of the server for implementing the method for updating process orchestration according to an embodiment of the present invention.

[0048] Through the above - mentioned drawings, the clear embodiments of the present disclosure have been shown, and there will be more detailed descriptions hereinafter. These drawings and written descriptions are not intended to limit the scope of the concept of the present disclosure in any way, but to illustrate the concept of the present disclosure to those skilled in the art by referring to specific embodiments. Detailed implementation manners

[0049] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present disclosure. On the contrary, they are merely examples of the devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0050] First, the terms related to the embodiments of the present invention are explained:

[0051] Large middle - tier and small front - end architecture: The middle - tier is responsible for precipitating general services and generally provides unified and standardized processes. The front - end customizes some process nodes in the process according to business needs. The middle - tier and the front - end together achieve process orchestration to meet business requirements.

[0052] To clearly understand the technical solution of the present application, the solutions of the prior art are first introduced in detail.

[0053] At present, there are two main methods for the middle platform to realize process orchestration by interacting with the front-end process nodes when precipitating the general service process body. One is that the front-end gives the personalized requirements of the process nodes. The middle platform not only needs to manually develop the process body, but also needs to manually develop the process nodes according to the personalized requirements of the process nodes. In this process orchestration method, the coupling degree between the middle platform and the front-end is very high. No matter what updates the personalized requirements of the process nodes by the front-end, the middle platform will cause the middle platform to manually develop adaptive process nodes. Therefore, with the development of business needs, the middle platform needs a lot of manpower to support it, resulting in a large cost of manpower support for the middle platform and low efficiency in meeting business needs.

[0054] The other is that the front desk develops personalized process nodes according to business needs and provides a remote call interface (referred to as: rpc interface). The middle desk accesses the rpc interface and requires a small amount of manual development and updates to meet business needs. Although the coupling degree of this process orchestration method is lower than that of the first process orchestration method, it still has a high degree of coupling. Every time the front desk has new business needs, the middle desk will be incompatible with the new business needs. Upgrade, so manual adaptive development and updates are still required. Therefore, the manpower support cost of the middle desk is still large, and the efficiency of meeting business needs is low.

[0055] Therefore, when facing the technical problems of the prior art, the inventor discovered through creative research that in order to achieve the decoupling of the front desk and the middle desk in the process orchestration, the middle desk server is required to provide the front desk access specification interface data for each process node to be opened, and use the parameters of the front desk business identity as parameters in the front desk access specification interface data. So that the front desk server generates a development data packet to be updated according to the front desk access specification interface data, and includes the front desk business identity in the development data packet to be updated. When the middle desk server monitors that the development data packet update conditions of the process node to be opened are met, the development data packet to be updated is obtained, and the development data packet of the process node to be opened is updated according to the development data packet to be updated and the corresponding foreground business identity, so as to complete the update of the process orchestration. In this process, there is no need for the middle desk server to manually perform adaptive development or update, and the front desk server is only responsible for the personalized customization of the process node to be developed, that is, generating the development data packet to be updated. The middle-office server is only responsible for updating the development data packages of the open process nodes according to the development data packages to be updated and the corresponding front-end business identity identifiers, thereby realizing the decoupling between the middle-office server and the front-end server. Moreover, the middle-office server does not require manpower support and can be updated automatically, thereby effectively improving the efficiency of meeting business needs.

[0056] Therefore, based on the above creative findings, the inventor proposed the technical solution of the embodiment of the present invention. Next, the network architecture and application scenarios of the process orchestration update method provided by the embodiment of the present invention will be introduced.

[0057] As Figure 1 shown, the network architecture of the process orchestration update method provided by the embodiment of the present invention includes at least one front-end server and a middle-tier server 2. In Figure 1 it, the front-end server includes a first front-end server 11 and a second front-end server 12. Among them, each front-end server can be composed of a server cluster. The middle-tier server 2 can also be composed of a server cluster. The middle-tier server 2 develops the target process body, and the target process body includes multiple process nodes. At least one process node requires the front-end server to perform personalized development of the process node. For each process node, according to different business requirements, multiple front-end servers can also perform different personalized development of the process node. Each front-end server corresponds to a front-end business identity identifier. Each front-end server is communicatively connected to the middle-tier server 2. Each front-end server can store the to-be-updated development data packet for personalized development into the maven server 3, and the middle-tier server 2 obtains the to-be-updated development data packet from the maven server 3.

[0058] Next, the application scenario will be introduced by taking the target process body as the order process body as an example. The process nodes included in the order process body can be successively: pulling product details, querying real-time inventory, obtaining preferential electronic vouchers, calculating prices, etc. If the to-be-opened process node determined by the middle-tier server is querying real-time inventory. In one application scenario, as Figure 2 shown, both the first front-end server 11 with pharmaceutical business requirements and the second front-end server 12 with supermarket business requirements have personalized development requirements for the to-be-opened process node. Then the first front-end server 11 and the second front-end server 12 respectively obtain the front-end access specification interface data from the middle-tier server 2. And generate the corresponding to-be-updated development data packets. The first front-end business identity identifier is included in the to-be-updated development data packet with pharmaceutical business requirements. The second front-end business identity identifier is included in the to-be-updated development data packet with supermarket business requirements. The first front-end server 11 and the second front-end server 12 store the to-be-updated development data packets into the maven server 3 according to, and the to-be-updated development data packets all have corresponding maven coordinates. After the middle-tier server detects that the development data packet update condition for the to-be-opened process node is met, it obtains the to-be-updated development data packet from the maven server, and updates the development data packet of the to-be-opened process node according to the to-be-updated development data packet and the corresponding front-end business identity identifier. As in Figure 2In this case, in the process node of querying real-time inventory, the development data packets to be updated with pharmaceutical front desk business requirements and the development data packets to be updated with supermarket business requirements are loaded into the process node of querying real-time inventory.

[0059] In another application scenario, as Figure 3 shown, when the process node to be opened in the middle platform server is to query real-time inventory, the development data packets that meet pharmaceutical requirements and the development data packets that meet supermarket requirements have been loaded in this process node to be opened. However, the pharmaceutical requirements have been updated. Therefore, the first front desk server 11 needs to update the original development data packet that meets pharmaceutical requirements. Then, the first front desk server 11 generates a development data packet to be updated according to the interface data of the front desk access specification, and the first front desk business identity identifier is included in the development data packet to be updated. The first front desk server 11 stores the development data packet to be updated in the maven server 3. After the middle platform server 2 detects that the development data packet update condition of the process node to be opened is met, it obtains the development data packet to be updated from the maven server 3, and updates the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front desk business identity identifier. For example, in Figure 3 the original development data packet is replaced with the development data packet to be updated.

[0060] It can be understood that when introducing the application scenario, the main body of the order process is taken as an example for illustration, and it can also be applied to other process main bodies, and the application scenario can also be other scenarios, which are not limited in the embodiments of the present invention.

[0061] Next, specific embodiments are used to describe in detail the technical solution of the present invention and how the technical solution of the present invention solves the above technical problems. These specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. Next, the embodiments of the present invention will be described with reference to the drawings.

[0062] Embodiment 1

[0063] Figure 4 is a flowchart of a method for updating process choreography provided by an embodiment of the present invention. As Figure 4 shown, the execution subject of the method for updating process choreography provided in this embodiment is a device for updating process choreography, and this device for updating process choreography is located in the middle platform server. Then, the method for updating process choreography provided in this embodiment includes the following steps:

[0064] Step 101, determine the process node to be opened in the target process main body.

[0065] In this embodiment, the target process entity is the process entity that needs to have its process orchestration updated. The target process entity includes multiple process nodes. Among the multiple process nodes, the process nodes that need to be personalized developed are determined, and the process nodes that need to be personalized developed are determined as the to-be-opened process nodes.

[0066] In this embodiment, when determining the to-be-opened process nodes in the target process entity, for each process node, it is judged whether there is a process node opening request initiated by the front-end server. If it is determined that there is a process node opening request initiated by the front-end server, then it is determined that this process node is a to-be-opened process node. Or other methods can also be used to determine the to-be-opened process nodes in the target process entity, and this embodiment does not make any limitations in this regard.

[0067] Step 102: Generate corresponding front-end access specification interface data according to the to-be-opened process nodes. The front-end access specification interface data includes parameters of the front-end business identity identifier.

[0068] In this embodiment, the front-end access specification interface data can be determined according to the common characteristics of the to-be-opened process nodes in each business requirement. The front-end access specification interface data can be represented in the form of a java interface.

[0069] Among them, the front-end access specification interface data can include: the input parameters when the front-end server accesses, the output parameters fed back by the middle-tier server to the front-end server, and the method name for the front-end server to generate the to-be-updated development data packet according to the front-end access specification interface data, etc.

[0070] Among them, the front-end access specification interface data includes the parameter of the front-end business identity identifier, and this parameter is an input parameter.

[0071] Step 103: If a data acquisition request sent by the front-end server is received, then send the front-end access specification interface data to the front-end server. The front-end access specification interface data is used to instruct the front-end server to generate a corresponding to-be-updated development data packet, and the to-be-updated development data packet includes the front-end business identity identifier.

[0072] In this embodiment, after generating the front-end access specification interface data of the process node to be opened, the front-end interface specification interface data is opened, and each front-end server can access the front-end access specification interface data. Specifically, the front-end server sends a data acquisition request, and the data acquisition request may include the identification information of the process node to be opened. The middle platform server obtains the corresponding front-end access specification interface data according to the identification information of the process node to be opened, and sends the front-end access specification interface data to the front-end server. The front-end server generates a development data packet to be updated that meets the requirements of the front-end access specification interface data and the current business requirements. Among them, the front-end business identity identifier is included in the data packet to be updated to indicate which front-end business identity the data packet to be updated corresponds to.

[0073] Step 104, if it is detected that the update condition of the development data packet of the process node to be opened is met, the development data packet of the process node to be opened is updated according to the development data packet to be updated and the corresponding front-end business identity identifier.

[0074] In this embodiment, the middle platform server can monitor at preset time intervals whether the update condition of the development data packet of the process node to be opened is met. If it is determined that the update condition of the development data packet of the process node to be opened is met, the development data packet to be updated is obtained, and the development data packet of the process node to be opened is updated according to the development data packet to be updated and the front-end business identity identifier.

[0075] Among them, when updating the development data packet of the process node to be opened according to the development data packet to be updated and the front-end business identity identifier, if there is no original development data packet with the front-end business identity identifier at the process node to be opened, the development data packet to be updated is directly loaded. If there is an original development data packet with the front-end business identity identifier at the process node to be opened, the corresponding original development data packet is replaced with the development data packet to be updated.

[0076] The process orchestration update method provided in this embodiment determines the process nodes to be opened in the target process body; generates corresponding front-end access specification interface data according to the process nodes to be opened, and the front-end access specification interface data includes parameters of the front-end business identity; if a data acquisition request sent by the front-end server is received, the front-end access specification interface data is sent to the front-end server, and the front-end access specification interface data is used to instruct the front-end server to generate a corresponding development data packet to be updated, and the development data packet to be updated includes the front-end business identity; if it is monitored that the development data packet update condition for the process node to be opened is met, the development data packet of the process node to be opened is updated according to the development data packet to be updated and the corresponding front-end business identity. Since in the process of updating the process orchestration, the front-end server is only responsible for the personalized customization of the process nodes to be developed, that is, generating the development data packet to be updated. The middle platform server is only responsible for updating the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front-end business identity, realizing the decoupling between the middle platform server and the front-end server, and the middle platform server does not require human support and can be updated automatically, thereby effectively improving the efficiency of meeting business requirements.

[0077] Embodiment 2

[0078] Figure 5 is a schematic flowchart of the process orchestration update method provided by another embodiment of the present invention. As Figure 5 shown, the process orchestration update method provided in this embodiment further refines steps 101 - step 102 and step 104 on the basis of the process orchestration update method provided in Embodiment 1 of the present invention, and further includes other steps. Then the process orchestration update method provided in this embodiment includes the following steps:

[0079] Step 201, determine the process nodes to be opened in the target process body.

[0080] As an optional implementation manner, in this embodiment, step 201 includes the following steps:

[0081] Step 2011, receive a process node opening request sent by a certain front-end server, and the process node opening request includes the identification information of the process node.

[0082] Specifically, in this embodiment, after the middle platform service develops the data packet corresponding to the target process body and the general data packets corresponding to each process node, it does not determine which process nodes are the process nodes to be opened. And if a certain front-end server has personalized business requirements for a certain process node, it sends a process node opening request to the middle platform server.

[0083] Among them, the process node identification information is included in the process node opening request, and the process node identification information can be the serial number, name, etc. of the process node, which is the information that uniquely represents a certain process node.

[0084] Step 2012, determine the process node corresponding to the process node identification information as the process node to be opened.

[0085] In this embodiment, the middleware server determines the process node corresponding to the process node identification information from the target process main body as the process node to be opened.

[0086] Step 202, generate corresponding front-end access specification interface data according to the process node to be opened, and the front-end access specification interface data includes parameters of the front-end service identity.

[0087] As an optional implementation manner, in this embodiment, step 202 includes the following steps:

[0088] Step 2021, determine the input parameters, output parameters and method name in the front-end access specification interface data according to the process node to be opened, and the input parameters include the front-end service identity.

[0089] Step 2022, generate the front-end access specification interface data according to the input parameters, output parameters and method name.

[0090] In this embodiment, the middleware server determines the input parameters when the front-end server accesses, the output parameters fed back by the middleware server to the front-end server, and the method name for the front-end server to generate the development data packet to be updated according to the common characteristics of the process node to be opened in each business requirement, and can generate the front-end access specification interface data according to the input parameters, output parameters and method name in a preset format.

[0091] Among them, the front-end access specification interface data can be represented in the form of a java interface.

[0092] Step 203, send a development data packet configuration page to the front-end server, and the development data packet configuration page is used to instruct the front-end server to display and receive the storage area identification information corresponding to the development data packet to be updated input by the user.

[0093] In this embodiment, after sending the front-end access specification interface data to the front-end server, the development data packet configuration page can also be sent to the front-end server. Or when sending the front-end access specification interface data to the front-end server, carry the link address of the development data packet configuration page in the front-end access specification interface data, and the front-end server sends a page acquisition request to the middleware server by the user clicking the link address, and the middleware server sends the development data packet configuration page to the front-end server.

[0094] Among them, in the development data packet configuration page, the user can configure the storage area identification information of the development data packet to be updated. Among them, the development data packet to be updated can be a jar package, so the storage area identification information is the maven coordinate. The user inputs the maven coordinate of the development data packet to be updated in the development data packet configuration page.

[0095] Step 204: Receive the storage area identification information sent by the front-end server and store the storage area identification information in the common storage area.

[0096] In this embodiment, after the user inputs the storage area identification information through the development data packet configuration interface, by triggering the confirmation component, the front-end server sends the storage area identification information to the middle-tier server. After receiving the storage area identification information, the middle-tier server stores the storage area identification information in the common storage area.

[0097] Among them, the common storage area can be a redis cache or other common storage areas, which are not limited in this example.

[0098] Step 205: Obtain the storage area identification information of the development data packet to be updated stored in the common storage area.

[0099] In this embodiment, every time the front-end server generates a development data packet to be updated, a unique maven coordinate will be configured for the development data packet to be updated. Therefore, the maven coordinates stored by the middle-tier server in the common storage area will be continuously updated.

[0100] Step 206: Determine whether to update the storage area identification information. If so, execute Step 207; otherwise, after an interval of a preset time period, continue to execute Step 205.

[0101] In this embodiment, if the middle-tier server is a server cluster, each server obtains the stored maven coordinates from the common storage area at intervals of a preset time period. Determine whether the maven coordinates obtained this time are updated compared with the maven coordinates obtained last time. If there is an update, it is determined that the development data packet of the development process node to be developed needs to be updated, that is, the update condition of the development data packet of the to-be-opened process node is satisfied. Otherwise, after an interval of a preset time period, continue to obtain the storage area identification information of the development data packet to be updated stored in the common storage area.

[0102] Step 207: Determine that it is detected that the update condition of the development data packet of the to-be-opened process node is satisfied.

[0103] Step 208: Update the development data packet of the to-be-opened process node according to the development data packet to be updated and the corresponding front-end service identity.

[0104] As an alternative implementation, in this embodiment, step 208 includes the following steps:

[0105] Step 2081, obtain the corresponding development data packet to be updated from the maven server according to the storage area identification information of the development data packet to be updated.

[0106] In this embodiment, after the user enters the maven coordinates through the development data packet configuration page, the foreground server stores the corresponding development data packet to be updated in the maven server according to the maven coordinates. Therefore, the middle platform server obtains the corresponding development data packet to be updated from the maven server according to the maven coordinates of the development data packet to be updated.

[0107] Step 2082, create a custom class loader, load the custom class loader into a custom directory, where the custom directory is a directory other than the directory corresponding to the default loader, and set the parent loader of the custom class loader to a null value.

[0108] To prevent the default class loader in the virtual machine from scanning the development data packet to be updated and causing conflicts between the development data packet to be updated and the corresponding original development data packet when the default class loader is used to load the development data packet to be updated, in this embodiment, a custom class loader is created. The custom class loader is first loaded into a directory other than the directory corresponding to the default loader, that is, the custom directory. Then, the parent loader of the custom class loader is set to a null value (the null value is null) to avoid class conflicts caused by the parent delegation mechanism when the parent loader of the custom class loader is not set to a null value.

[0109] Step 2083, use the newly created custom class loader instance to load the development data packet to be updated, and parse out the foreground service identity in the annotation of the development data packet to be updated.

[0110] In this embodiment, after creating the custom class loader, to avoid class conflicts, the custom class loader creates a new custom class loader instance and uses the newly created custom class loader instance to load the development data packet to be updated. After loading, operations such as decompression and translation are performed. And the foreground service identity is parsed from the annotation of the development data packet to be updated.

[0111] Step 2084, update the development data packet of the to-be-opened process node according to the foreground service identity.

[0112] As an alternative implementation, in this embodiment, step 2084 includes the following steps:

[0113] Step 2084a, obtain the original opened data packet with the foreground service identity in the to-be-opened process node.

[0114] Step 2084b: Replace the original open data packet with the data packet to be updated for development.

[0115] In this embodiment, since there are multiple foreground service identity identifiers in the original open data packet at the process node to be developed, the original open data packet with the same foreground service identity identifier as the data packet to be updated for development is obtained. The original open data packet is replaced with the data packet to be updated for development. When processing a new service with a foreground service identity identifier and reaching the process node to be developed, the process node to be developed will be executed according to the data packet to be updated for development.

[0116] For the process choreography update method provided in this embodiment, when monitoring whether the update condition of the development data packet for the process node to be opened is met, by sending a development data packet configuration page to the foreground server, the development data packet configuration page is used to instruct the foreground server to display and receive the storage area identifier information corresponding to the development data packet to be updated input by the user, receiving the storage area identifier information sent by the foreground server, and storing the storage area identifier information in a common storage area, obtaining the storage area identifier information of the development data packet to be updated stored in the common storage area, and judging whether to update the storage area identifier information, it is possible that when the middle - tier server is a server cluster, each server in the cluster can accurately monitor whether the update condition of the development data packet for the process node to be opened is met.

[0117] For the process choreography update method provided in this embodiment, when updating the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding foreground service identity identifier, obtain the corresponding development data packet to be updated from the maven server according to the storage area identifier information of the development data packet to be updated, create a custom class loader, and load the custom loader into a custom directory, where the custom directory is a directory other than the directory corresponding to the default loader, set the parent loader of the custom class loader to a null value, use the newly created custom class loader instance of the custom loader to load the development data packet to be updated, and parse out the foreground service identity identifier in the annotation of the development data packet to be updated, and update the development data packet of the process node to be opened according to the foreground service identity identifier. By storing the development data packet to be updated in the maven server and the middle - tier server obtaining the development data packet to be updated from the maven server, it is possible to further decouple the foreground server and the middle - tier server. And using the newly created custom class loader instance in the custom loader to load the development data packet to be updated can effectively avoid class conflicts.

[0118] Embodiment III

[0119] Figure 6 It is a schematic flowchart of the process choreography update method provided by another embodiment of the present invention, asFigure 6 As shown, if the execution entity of the process choreography update method provided in this embodiment is the front-end server, the process choreography update method provided in this embodiment includes the following steps:

[0120] Step 301: Send a data acquisition request corresponding to the process node to be opened to the middle-tier server.

[0121] In this embodiment, after the middle-tier server generates the front-end access specification interface data corresponding to the process node to be opened, the front-end server sends a data acquisition request corresponding to the process node to be opened to the middle-tier server. Among them, the data acquisition request may include the identification information of the process node to be opened.

[0122] Step 302: Receive the front-end access specification interface data corresponding to the process node to be opened sent by the middle-tier server. The access specification interface data includes parameters of the front-end service identity.

[0123] Step 303: Generate a corresponding development data packet to be updated according to the front-end access specification interface data. The development data packet to be updated includes the front-end service identity, so that the middle-tier server can update the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front-end service identity.

[0124] In this embodiment, after the front-end server receives the front-end access specification interface data, it parses the input parameters, output parameters, and method names from the front-end access specification interface data. Among them, the input parameters include the front-end service identity. Therefore, when the front-end server generates the development data packet to be updated according to the front-end access specification interface data, it needs to write its own front-end service identity into the development data packet to be updated.

[0125] Optionally, in this embodiment, the front-end service identity is located in the annotation of the development data packet to be updated. Therefore, after obtaining the development data packet to be updated, the middle-tier server can parse the development data packet to be updated, obtain the front-end service identity from the annotation, and then update the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front-end service identity.

[0126] The method for updating process orchestration provided in this embodiment includes sending a data acquisition request corresponding to a process node to be opened to the middleware server; receiving the front-end access specification interface data corresponding to the process node to be opened sent by the middleware server, where the access specification interface data includes parameters of the front-end service identity; generating a corresponding development data packet to be updated according to the front-end access specification interface data, and the development data packet to be updated includes the front-end service identity, so that the middleware server updates the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front-end service identity. Since the front-end server is only responsible for the personalized customization of the process node to be developed, that is, generating the development data packet to be updated. The middleware server is only responsible for updating the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front-end service identity, realizing the decoupling between the middleware server and the front-end server, and the middleware server does not require human support and can be updated automatically, thereby effectively improving the efficiency of meeting business requirements.

[0127] Embodiment 4

[0128] Figure 7 is a schematic flowchart of the method for updating process orchestration provided in another embodiment of the present invention. As Figure 7 shown, on the basis of the method for updating process orchestration provided in Embodiment 3 of the present invention, the method for updating process orchestration provided in this embodiment further includes the following steps after step 302:

[0129] Step 401, receiving the development data packet configuration page sent by the middleware server and displaying the development data packet configuration page.

[0130] Specifically, in this embodiment, if the link address of the development data packet configuration page is further included in the front-end access specification interface data, the user corresponding to the front-end server sends a page acquisition request to the middleware server by clicking the link address. The middleware server acquires the development data packet configuration page according to the page acquisition request and sends it to the front-end server, and the front-end server receives and displays the development data packet configuration page sent by the middleware server. Or after the middleware server sends the front-end access specification interface data to the front-end server, it actively sends the development data packet configuration page to the front-end server, and the front-end server receives the development data packet configuration page.

[0131] Step 402, receiving the storage area identification information corresponding to the development data packet to be updated input by the user on the development data packet configuration page.

[0132] In this embodiment, the user can configure the storage area identification information of the development data packet to be updated on the development data packet configuration page. Among them, the development data packet to be updated can be a jar package, so the storage area identification information is the maven coordinate. Therefore, the user inputs the maven coordinate of the development data packet to be updated on the development data packet configuration page.

[0133] As an alternative embodiment, after step 402, it further includes:

[0134] Store the development data packet to be updated into the maven server according to the storage area identification information.

[0135] In this embodiment, the development data packets to be updated are all stored in the maven server according to the maven coordinates, so that when the middleware server determines that the update condition of the development data packet for the to-be-opened process node is met, the corresponding development data packet to be updated can be obtained from the maven server.

[0136] Step 403: Send the storage area identification information to the middleware server.

[0137] In this embodiment, the maven coordinate is sent to the middleware server, so that the middleware server stores the maven coordinate in the public storage area, and determines whether the update condition of the development data packet for the to-be-opened process node is met according to whether there is an update of the maven coordinate stored in the public area.

[0138] The update method of process orchestration provided in this embodiment receives the development data packet configuration page sent by the middleware server, displays the development data packet configuration page, receives the storage area identification information corresponding to the development data packet to be updated input by the user on the development data packet configuration page, and sends the storage area identification information to the middleware server, so that the middleware server is a server cluster. When determining whether the update condition of the development data packet for the to-be-opened process node is met, each server in the middleware server cluster can accurately monitor whether the update condition of the development data packet for the to-be-opened process node is met.

[0139] The update method of process orchestration provided in this embodiment stores the development data packet to be updated into the maven server according to the storage area identification information, so that the middleware server can obtain the development data packet to be updated from the maven server, and can further decouple the front-end server and the middleware server.

[0140] Embodiment 5

[0141] Figure 8 It is a schematic structural diagram of an update device for process orchestration provided by an embodiment of the present invention, as Figure 8As shown in the figure, the process orchestration update device provided in this embodiment is located in the middleware server. The process orchestration update device 50 provided in this embodiment includes: a determination module 51, a generation module 52, a sending module 53, and an update module 54.

[0142] Among them, the determination module 51 is used to determine the process nodes to be opened in the target process body. The generation module 52 is used to generate corresponding front-end access specification interface data according to the process nodes to be opened. The front-end access specification interface data includes parameters of the front-end service identity. The sending module 53 is used to send the front-end access specification interface data to the front-end server if a data acquisition request sent by the front-end server is received. The front-end access specification interface data is used to instruct the front-end server to generate a corresponding development data packet to be updated. The development data packet to be updated includes the front-end service identity. The update module 54 is used to update the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding front-end service identity if it is detected that the development data packet update condition of the process node to be opened is met.

[0143] Optionally, the determination module 51 is specifically used for:

[0144] Receive a process node opening request sent by a certain front-end server. The process node opening request includes the identification information of the process node; determine the process node corresponding to the identification information of the process node as the process node to be opened.

[0145] Optionally, the generation module 52 is specifically used for:

[0146] Determine the input parameters, output parameters, and device name in the front-end access specification interface data according to the process nodes to be opened. The input parameters include the front-end service identity; generate the front-end access specification interface data according to the input parameters, output parameters, and device name.

[0147] Optionally, the process orchestration update device provided in this embodiment further includes: an acquisition module and a judgment module.

[0148] Among them, the acquisition module is used to acquire the storage area identification information of the development data packet to be updated stored in the public storage area. The judgment module is used to judge whether to update the storage area identification information. The determination module 51 is further used to determine that the development data packet update condition of the process node to be opened is detected if it is determined to update the storage area identification information.

[0149] Optionally, the process orchestration update device provided in this embodiment further includes: a receiving module.

[0150] The sending module 53 is further configured to send a development data packet configuration page to the front-end server, where the development data packet configuration page is used to instruct the front-end server to display and receive the storage area identification information corresponding to the development data packet to be updated input by the user. The receiving module is configured to receive the storage area identification information sent by the front-end server and store the storage area identification information in the public storage area, where the storage area identification information is the maven coordinate.

[0151] Optionally, the updating module 54 is specifically configured to:

[0152] Obtain the development data packet to be updated corresponding to the storage area identification information of the development data packet to be updated from the maven server; load the development data packet to be updated by using a newly created custom class loader instance, and parse out the front-end service identity in the annotation of the development data packet to be updated; update the development data packet of the to-be-opened process node according to the front-end service identity.

[0153] Optionally, when the updating module 54 updates the development data packet of the to-be-opened process node according to the front-end service identity, it is specifically configured to:

[0154] Obtain the original opened data packet with the front-end service identity in the to-be-opened process node; replace the original opened data packet with the development data packet to be updated.

[0155] Optionally, the process choreography updating device provided in this embodiment further includes: a creating module and a setting module.

[0156] Wherein, the creating module is configured to create a custom class loader and load the custom class loader into a custom directory, where the custom directory is a directory other than the directory corresponding to the default loader. The setting module is configured to set the parent loader of the custom class loader to a null value.

[0157] The process choreography updating device provided in this embodiment can execute Figures 4 - 5 the technical solution of the method embodiment shown, and its implementation principle and technical effect are similar to Figures 4 - 5 the method embodiment shown, and will not be elaborated here one by one.

[0158] Embodiment Six

[0159] Figure 9 is a schematic structural diagram of a process choreography updating device provided by another embodiment of the present invention. As shown in Figure 9 shown, the process choreography updating device provided in this embodiment is located in the front-end server. Then the process choreography updating device 60 provided in this embodiment includes: a sending module 61, a receiving module 62, and a generating module 63.

[0160] Among them, the sending module 61 is used to send a data acquisition request corresponding to the process node to be opened to the middleware server. The receiving module 62 is used to receive the foreground access specification interface data corresponding to the process node to be opened sent by the middleware server, and the access specification interface data includes parameters of the foreground service identity. The generating module 63 is used to generate a corresponding development data packet to be updated according to the foreground access specification interface data. The development data packet to be updated includes the foreground service identity, so that the middleware server can update the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding foreground service identity.

[0161] The process orchestration update device provided in this embodiment can execute Figures 6 - 7 the technical solution of the method embodiment shown, and its implementation principle and technical effect are similar to Figures 6 - 7 the method embodiment shown, and will not be elaborated here one by one.

[0162] Embodiment Seven

[0163] Figure 10 is the first block diagram of the middleware server for implementing the process orchestration update method of the embodiment of the present invention. As Figure 10 shown, the middleware server 70 provided in this embodiment includes: a memory 71, a processor 72, and a transceiver 73.

[0164] The processor 72, the memory 71, and the transceiver 73 are interconnected by a circuit;

[0165] The memory 71 stores computer execution instructions; the transceiver 73 is used to send and receive data with the foreground server;

[0166] At least one processor 72 executes the computer execution instructions stored in the memory, so that at least one processor executes the method in Embodiment 1 or Embodiment 2 above.

[0167] Embodiment Eight

[0168] Figure 11 is the structural schematic diagram of the foreground server for implementing the process orchestration update method of the embodiment of the present invention. As Figure 11 shown, the foreground server provided in this embodiment includes: a memory 81, a processor 82, and a transceiver 83.

[0169] The processor 82, the memory 81, and the transceiver 83 are interconnected by a circuit;

[0170] The memory 81 stores computer execution instructions; the transceiver 83 is used to send and receive data with the middleware server;

[0171] At least one processor 82 executes computer-executable instructions stored in memory, such that the at least one processor performs the method in the third or fourth embodiment above.

[0172] Embodiment Nine

[0173] Figure 12 is a block diagram of a server for implementing the update method of process choreography in an embodiment of the present invention. As Figure 12 shown, the server provided in this embodiment is a middleware server or a front-end server.

[0174] The server 900 may include one or more of the following components: a processing component 902, a memory 904, a power supply component 906, a multimedia component 908, an audio component 910, an input / output (I / O) interface 912, a sensor component 914, and a communication component 916.

[0175] The processing component 902 generally controls the overall operation of the server 900, such as operations associated with display, telephone calls, data communication, camera operations, and recording operations. The processing component 902 may include one or more processors 920 to execute instructions to complete all or part of the steps of the above method. In addition, the processing component 902 may include one or more modules to facilitate the interaction between the processing component 902 and other components. For example, the processing component 902 may include a multimedia module to facilitate the interaction between the multimedia component 908 and the processing component 902.

[0176] The memory 904 is configured to store various types of data to support the operation of the server 900. Examples of these data include instructions for any application or method operating on the server 900, contact data, phone book data, messages, pictures, videos, etc. The memory 904 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disk.

[0177] The power supply component 906 provides power to various components of the server 900. The power supply component 906 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the server 900.

[0178] The multimedia component 908 includes a screen that provides an output interface between the server 900 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions but also detect the duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 908 includes a front camera and / or a rear camera. When the server 900 is in an operation mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

[0179] The audio component 910 is configured to output and / or input audio signals. For example, the audio component 910 includes a microphone (MIC) that is configured to receive external audio signals when the server 900 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals can be further stored in the memory 904 or transmitted via the communication component 916. In some embodiments, the audio component 910 further includes a speaker for outputting audio signals.

[0180] The I / O interface 912 provides an interface between the processing component 902 and a peripheral interface module, which can be a keyboard, a click wheel, buttons, etc. These buttons can include but are not limited to: a home button, a volume button, a power button, and a lock button.

[0181] The sensor component 914 includes one or more sensors for providing status assessments of various aspects of the server 900. For example, the sensor component 914 can detect the on / off state of the server 900, the relative positioning of components, such as the display and keypad of the server 900. The sensor component 914 can also detect a change in the position of the server 900 or a component of the server 900, the presence or absence of user contact with the server 900, the orientation or acceleration / deceleration of the server 900, and the temperature change of the server 900. The sensor component 914 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor component 914 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 914 can further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0182] The communication component 916 is configured to facilitate communication, in a wired or wireless manner, between the server 900 and other devices. The server 900 can access a communication standard-based wireless network, such as WiFi, 2G, or 3G, or a combination thereof. In an exemplary embodiment, the communication component 916 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 916 further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0183] In an exemplary embodiment, the server 900 can be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the above-described method.

[0184] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 904 including instructions, and the above instructions can be executed by a processor 920 of the server 900 to complete the above-described method. For example, the non-transitory computer-readable storage medium can be a ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0185] A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by a processor of the server, enables the terminal device to execute the update method for the process orchestration of the above server.

[0186] In an exemplary embodiment, a computer program product is also provided, including a computer program, and the computer program is executed by a processor to perform the method provided in any one of the first to fourth embodiments above.

[0187] Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses, or adaptations of the present disclosure, which follow the general principles of the present disclosure and include known common knowledge or conventional technical means in the technical field not disclosed by the present disclosure. The specification and embodiments are only to be considered as exemplary, and the true scope and spirit of the present disclosure are pointed out by the following claims.

[0188] It should be understood that the present disclosure is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.

Claims

1. A method for updating process orchestration, characterized in that, The method is applied to a middle - tier server, and the method includes: Determine the process nodes to be opened in the target process body; Generate corresponding front - end access specification interface data according to the process nodes to be opened, where the front - end access specification interface data includes parameters of the front - end service identity; If a data acquisition request sent by the front - end server is received, then send the front - end access specification interface data to the front - end server, and the front - end access specification interface data is used to instruct the front - end server to generate a corresponding development data packet to be updated, and the development data packet to be updated includes the front - end service identity; If it is monitored that the development data packet update condition for the process nodes to be opened is met, then obtain the corresponding development data packet to be updated from the maven server according to the storage area identification information of the development data packet to be updated; load the development data packet to be updated by using a newly created custom class loader instance, and parse out the front - end service identity in the annotation of the development data packet to be updated; update the development data packet of the process nodes to be opened according to the front - end service identity.

2. The method according to claim 1, wherein The determining the process nodes to be opened in the target process body includes: Receive a process node opening request sent by a certain front - end server, where the process node opening request includes the identification information of the process node; Determine the process node corresponding to the identification information of the process node as the process node to be opened.

3. The method according to claim 1, wherein The generating corresponding front - end access specification interface data according to the process nodes to be opened includes: Determine the input parameters, output parameters and method name in the front - end access specification interface data according to the process nodes to be opened, and the input parameters include the front - end service identity; Generate the front - end access specification interface data according to the input parameters, the output parameters and the method name.

4. The method according to any one of claims 1 to 3, characterized in that, Before the step of, if it is monitored that the development data packet update condition for the process nodes to be opened is met, then update the development data packet of the process nodes to be opened according to the development data packet to be updated and the corresponding front - end service identity, further includes: Obtain the storage area identification information of the development data packet to be updated stored in the public storage area; Judge whether to update the storage area identification information; If it is determined to update the storage area identification information, then determine that the development data packet update condition for the process nodes to be opened is met.

5. The method according to claim 4, wherein Before the step of obtaining the storage area identification information of the development data packet to be updated stored in the public storage area, further includes: Send a development data packet configuration page to the front - end server, and the development data packet configuration page is used to instruct the front - end server to display and receive the storage area identification information corresponding to the development data packet to be updated input by the user; Receive the storage area identification information sent by the front - end server, and store the storage area identification information in the public storage area, and the storage area identification information is the maven coordinate.

6. A method for updating process orchestration, characterized in that, The method is applied to a front - end server, and the method includes: Send a data acquisition request corresponding to the process nodes to be opened to the middle - tier server; Receive the foreground access specification interface data corresponding to the process nodes to be opened sent by the middleware server, where the access specification interface data includes parameters of the foreground service identity identifier; Generate a corresponding development data packet to be updated according to the foreground access specification interface data, where the development data packet to be updated includes the foreground service identity identifier, so that the middleware server obtains the corresponding development data packet to be updated from the maven server according to the storage area identifier information of the development data packet to be updated; load the development data packet to be updated by using a newly created custom class loader instance, and parse out the foreground service identity identifier in the annotation of the development data packet to be updated; update the development data packet of the process node to be opened according to the foreground service identity identifier.

7. The method according to claim 6, wherein The foreground service identity identifier is located in the annotation of the development data packet to be updated.

8. The method according to claim 6 or 7, characterized in that, Further includes: Receive the development data packet configuration page sent by the middleware server, and display the development data packet configuration page; Receive the storage area identifier information corresponding to the development data packet to be updated input by the user on the development data packet configuration page; Send the storage area identifier information to the middleware server.

9. An update device for process orchestration, characterized in that, The device is located in the middleware server, and the device includes: A determination module, configured to determine the process nodes to be opened in the target process main body; A generation module, configured to generate corresponding foreground access specification interface data according to the process nodes to be opened, where the foreground access specification interface data includes parameters of the foreground service identity identifier; A sending module, configured to, if a data acquisition request sent by the foreground server is received, send the foreground access specification interface data to the foreground server, where the foreground access specification interface data is used to instruct the foreground server to generate a corresponding development data packet to be updated, and the development data packet to be updated includes the foreground service identity identifier; An update module, configured to, if it is monitored that the development data packet update condition of the process node to be opened is met, update the development data packet of the process node to be opened according to the development data packet to be updated and the corresponding foreground service identity identifier; The update module is specifically configured to obtain the corresponding development data packet to be updated from the maven server according to the storage area identifier information of the development data packet to be updated; load the development data packet to be updated by using a newly created custom class loader instance, and parse out the foreground service identity identifier in the annotation of the development data packet to be updated; update the development data packet of the process node to be opened according to the foreground service identity identifier.

10. An update device for process orchestration, characterized in that, The device is located in the foreground server, and the device includes: A sending module, configured to send a data acquisition request corresponding to the process node to be opened to the middleware server; A receiving module, configured to receive the foreground access specification interface data corresponding to the process node to be opened sent by the middleware server, where the access specification interface data includes parameters of the foreground service identity identifier; A generation module, configured to generate a corresponding development data packet to be updated according to the foreground access specification interface data. The development data packet to be updated includes a foreground service identity, so that the middleware server can obtain the corresponding development data packet to be updated from the maven server according to the storage area identification information of the development data packet to be updated; load the development data packet to be updated by using a newly created custom class loader instance, and parse out the foreground service identity in the annotation of the development data packet to be updated; update the development data packet of the to-be-opened process node according to the foreground service identity.

11. A middle platform server, characterized in that, Comprising: At least one processor, a memory and a transceiver; The processor, the memory and the transceiver are interconnected through circuits; The memory stores computer-executable instructions; the transceiver is used for sending and receiving data with the foreground server; The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the method according to any one of claims 1-5.

12. A front-end server, characterized in that, Comprising: At least one processor, a memory and a transceiver; The processor, the memory and the transceiver are interconnected through circuits; The memory stores computer-executable instructions; the transceiver is used for sending and receiving data with the middleware server; The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the method according to any one of claims 6-8.

13. A computer-readable storage medium, characterized in that, Computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the method according to any one of claims 1-5 or 6-8.

14. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method according to any one of claims 1-5 or 6-8.

Images