Business process orchestration methods, devices, storage media and electronic equipment

Abstract

This application discloses a business process orchestration method, apparatus, storage medium, and electronic device, relating to the field of computer technology. The method includes: instantiating atomic capability components from a registration file based on attribute information, including grayscale rules corresponding to multiple instance versions, and isolating and saving the atomic capability instances; then creating a business process template, in which process steps are bound to atomic capability components using API interfaces associated with the atomic capability components; executing the business process based on the business process template, and by calling the bound API interfaces, searching for target instances required for process steps from the isolated and saved atomic capability instances, and obtaining the execution result based on the target instances. This application provides a business process orchestration method based on a soft grayscale mechanism, enabling soft grayscale release management of atomic capability components in the field of business process orchestration.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a business process orchestration method, apparatus, storage medium, and electronic device. Background Technology

[0002] Most existing solutions for canary releases only achieve canary releases at the product level, such as through A / B testing or user traffic distribution.

[0003] However, there is currently no good solution for canary deployment management of atomic service (AS, or atomic capability service, etc.) components in the business process orchestration field. Summary of the Invention

[0004] In view of this, this application provides a business process orchestration method, apparatus, storage medium and electronic device, the main purpose of which is to improve the technical problem that there is no good solution for the grayscale management of atomic capability components in the field of business process orchestration.

[0005] Firstly, this application provides a business process orchestration method, including:

[0006] Obtain the registration file of the atomic capability component. The registration file stores the attribute information of at least one atomic capability component. The attribute information includes grayscale rules corresponding to multiple instance versions. The atomic capability component has associated API interfaces.

[0007] Based on the attribute information, the atomic capability component in the registration file is instantiated, and the atomic capability instance of the atomic capability component is isolated and saved.

[0008] Create a business process template, in which the process steps of the business process are bound to the atomic capability components using the API interfaces associated with the atomic capability components;

[0009] In response to executing a business process based on the business process template, the system calls the bound API interface to find the target instance required for the process step from the isolated and saved atomic capability instances, and obtains the execution result based on the target instance.

[0010] Secondly, this application provides a business process orchestration apparatus, comprising:

[0011] The acquisition module is configured to acquire the registration file of the atomic capability component. The registration file stores the attribute information of at least one atomic capability component. The attribute information includes grayscale rules corresponding to multiple instance versions. The atomic capability component has an associated API interface.

[0012] The processing module is configured to instantiate the atomic capability component in the registration file according to the attribute information, and to isolate and save the atomic capability instance of the atomic capability component.

[0013] The creation module is configured to create business process templates, in which the business process templates utilize API interfaces associated with atomic capability components to bind the process steps of the business process to the atomic capability components;

[0014] The execution module is configured to respond to the execution of a business process based on the business process template by calling the bound API interface to find the target instance required for the process step from the isolated and saved atomic capability instances, and obtain the execution result based on the target instance.

[0015] Thirdly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect.

[0016] Fourthly, this application provides an electronic device including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the computer program to implement the method described in the first aspect.

[0017] By employing the above technical solution, this application provides a business process orchestration method, apparatus, storage medium, and electronic device. First, a registration file for atomic capability components is obtained. This registration file stores attribute information for at least one atomic capability component, including grayscale rules corresponding to multiple instance versions. The atomic capability components have associated API interfaces. Based on the attribute information of the atomic capability components, the atomic capability components in the registration file are instantiated, and the atomic capability instances of the atomic capability components are isolated and saved. Then, a business process template is created. The business process template uses the API interfaces associated with the atomic capability components to bind the process steps of the business process to the atomic capability components. In response to executing the business process based on the business process template, the target instance required for the process step is found from the isolated and saved atomic capability instances by calling the bound API interface, and the execution result is obtained based on the target instance. Compared with existing technologies, this application essentially provides a business process orchestration method based on a soft grayscale mechanism, providing a grayscale management solution for atomic capability components in the field of business process orchestration. This involves designing a "soft isolation" atomic capability operation model, which will analyze the "soft grayscale" implementation method of atomic capability granularity from the perspective of actual business system construction and at the code level. This will achieve "soft isolation" of atomic capabilities used between different versions of business processes.

[0018] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A flowchart illustrating a business process orchestration method provided in an embodiment of this application is shown.

[0022] Figure 2 A flowchart illustrating a business process orchestration method provided in an embodiment of this application is shown.

[0023] Figure 3 A schematic diagram illustrating an example provided in an embodiment of this application is shown;

[0024] Figure 4 A schematic diagram illustrating an example provided in an embodiment of this application is shown;

[0025] Figure 5 A schematic diagram illustrating an example provided in an embodiment of this application is shown;

[0026] Figure 6 A schematic diagram of the structure of a business process orchestration device provided in an embodiment of this application is shown. Detailed Implementation

[0027] The embodiments of this application will now be described in more detail with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0028] To address the current lack of effective solutions for the canary release management of atomic capability components in the business process orchestration field, this embodiment provides a business process orchestration method. It involves the concepts of dedicated line business process orchestration and the definition, isolation, and invocation of business-related atomic capabilities, representing a research scheme for the soft canary release of atomic capabilities. Figure 1 As shown, the method includes:

[0029] Step 101: Obtain the registration file for the Atomic Capability Component.

[0030] The registration file stores attribute information for at least one atomic capability component, which includes grayscale rules corresponding to multiple instance versions. The atomic capability component has associated API interfaces.

[0031] The registration file can be a registration file in Extensible Markup Language (XML) format. In this embodiment, the registration file of the atomic capability component can be predefined. Each atomic capability component is associated with an external API interface. The attributes of each atomic capability include grayscale features, specified instance version, etc.

[0032] Step 102: Based on the attribute information of the atomic capability component, instantiate the atomic capability component in the registration file and save the atomic capability instance of the atomic capability component in isolation.

[0033] This embodiment can instantiate atomic capability components based on their attribute information, resulting in multiple instances of atomic capability. These instances are then isolated and stored, such as in thread-independent data slots. In other words, this embodiment designs a "soft-isolated" atomic capability operation model.

[0034] Step 103: Create a business process template.

[0035] In the business process template, the process steps (or automated steps) of the business process are bound to the atomic capability components using the API interfaces associated with the atomic capability components. The purpose is to obtain the required target instance by calling the corresponding bound API interface when the process step is executed, and to obtain the execution result based on the target instance, specifically the process shown in step 104.

[0036] Step 104: In response to the execution of the business process based on the business process template, the target instance required for the process step is found from the isolated and saved atomic capability instances by calling the bound API interface, and the execution result is obtained based on the target instance.

[0037] For canary deployment management of atomic capability components (hereinafter referred to as AS), most implementations only achieve canary deployment at the product or system level, rarely involving granular canary deployment at the AS level. For large-scale internet systems, product-level canary deployment capabilities are mainly manifested through A / B testing. For carrier capability center systems, canary deployment capabilities are more reflected at the system level. Spring Cloud & Alibaba cloud architecture systems generally use load balancing or API-Gateway to distribute traffic to different system versions. However, granular canary deployment at the AS level can often only be implemented at the code level, and there are generally no universal, off-the-shelf solutions.

[0038] In some embodiments, canary releases primarily address A / B testing or user traffic distribution issues. However, this embodiment focuses on a completely different problem. This embodiment aims to analyze and resolve capability support management at the AS unit capability component level, achieving "soft isolation" of AS capabilities through a "soft canary release" approach (it should be noted that this is not a canary release method, but rather an implementation method similar to canary release), rather than a canary release software implementation method.

[0039] Currently, there is no good solution for handling canary release management at the granular level of ActionScript (AS). Generally, existing technical solutions often use system-level canary release management to solve AS management problems. This coarse-grained canary release is simple and crude. Although it can detect and alleviate system problems caused by AS capability degradation and failure to some extent, it also has many drawbacks. First, the coarser the granularity of the canary release, the more hardware resources the system needs. Canary release management itself is a solution that consumes a lot of server resources, and system-level canary release consumes a huge amount of resources. Second, since AS capabilities are shared by various business processes, code upgrades will inevitably cause business process interruptions. Third, system-level canary releases generally do not require AS capability decomposition, and this strong coupling between AS and business processes is one of the root causes of code maintenance difficulties.

[0040] This embodiment aims to address the problem of designing a "soft-isolated" AS (Application System) runtime model. From the perspective of actual business system construction, it analyzes the implementation method of "soft grayscale" AS granularity at the code level, as well as the feasibility of batch upgrade management. This achieves "soft isolation" of AS used by different versions of business processes. When releasing new business processes or upgrading Business Process Modeling (BPM) templates, no code modification or system restart is required; AS switching and rollback can be achieved through configuration, ensuring no impact on existing business and guaranteeing the continuity and reliability of safe production.

[0041] This embodiment can initiate and execute a business process based on a business process template, and obtain the returned results by calling the bound API interface. Compared with existing technologies, this embodiment provides a business process orchestration method based on a soft grayscale mechanism, offering a grayscale management solution for atomic capability components in the field of business process orchestration. Specifically, it designs a "soft-isolated" atomic capability operation model, analyzing the "soft grayscale" implementation method of atomic capability granularity from the perspective of actual business system construction at the code level. This achieves "soft isolation" of atomic capabilities used between different versions of the business process.

[0042] To further illustrate the specific implementation process of the method in this embodiment, this embodiment provides the following: Figure 2 The specific method shown includes:

[0043] Step 201: Obtain the registration file for the Atomic Capability Component.

[0044] The registration file contains attribute information for at least one atomic capability component. The attribute information includes grayscale rules corresponding to multiple instance versions, and the atomic capability component has associated API interfaces.

[0045] For example, such as Figure 3 As shown, this embodiment mainly performs four key steps, including: defining an atomic capability registration file XML, associating each component with an external API, and specifying the grayscale feature and template version for each atomic capability; loading the registration file XML in the control center and supporting "dynamic refresh"; defining a process template and binding automatic steps to atomic capability components; starting and executing the process and finding the required atomic capability services through the control center.

[0046] This embodiment allows for the pre-definition of registration files for atomic capability components. The definition and registration of atomic capability components are based on XML syntax, describing a typical example of atomic capability and its attribute definition. The pseudocode is as follows:

[0047]

[0048] In the example above, the `component` node represents multiple grayscale instance versions of an atomic capability, bound to the API and process stages. The `class` attribute is the package path of the AS implementation class. Defining AS as the package path of the Java class allows for runtime assembly using Java reflection tools to obtain instances of AS. Dynamic proxies can be implemented using JDK native reflection or Ciglib tools, avoiding hard coding; this is a common practice for decoupling API calls. This design references the Spring framework's Bean injection method, with the default atomic instance being a singleton, equivalent to a `singleton` scope.

[0049] The `darkFeature` attribute can be used to design a complex set of grayscale rules, such as allocating access traffic based on user ID, city / district / county, or IP address range. This proposal primarily aims to analyze and resolve the soft isolation issue of AS components. To simplify the analysis and facilitate understanding, the `darkFeature` attribute is simplified to a grayscale range setting: `{target, 70%}` indicates that this defined AS will handle 70% of the call traffic. In the AS control center, using a probabilistic algorithm, it is easy to achieve a specified probability of hit for different versions of AS instances.

[0050] The `modeler` attribute has the highest design priority. It can specify the process version number. When an AS (Application Server) specifies a `modeler`, the process instance will prioritize finding the AS instance by the `modeler` during execution, without performing grayscale range filtering. How the `modeler` is specifically bound to the process instance will be further explained in Step 3.

[0051] In some embodiments, the method of this embodiment may further include: monitoring the registration file through a polling mechanism; when an update is detected in the registration file, dynamically refreshing the registration file based on the updated registration file, so as to continue executing the business process according to the atomic capability components in the updated registration file.

[0052] Because atomic capability services are separated and independently registered in the control center module, there is naturally no correlation or impact between different process versions or different process instances when business processes are upgraded. When atomic capability services are upgraded, a "dynamic refresh" mechanism is used, eliminating the need to notify the business process engine module to restart the service, allowing for a seamless switch to the new service.

[0053] This embodiment supports batch AS upgrade capability: This embodiment proposes to define AS using XML, which is clear and easy to modify. Combined with a dynamic refresh mechanism, batch AS upgrades can be achieved without the business process being aware of or interrupted.

[0054] Step 202: Based on the attribute information of the atomic capability component, instantiate the atomic capability component in the registration file and save the atomic capability instance of the atomic capability component in isolation.

[0055] For example, such as Figure 3As shown, the AS Power Centre module is primarily responsible for loading and parsing the AS registration file using an XML parser. It supports hot reloading (reloadRule), and its implementation principle is similar to the Nacos long polling mechanism. A listener can be designed to monitor data changes, thereby achieving dynamic refresh based on the XML rule file. The advantage of dynamic refresh is that when an atomic capability deteriorates or fails, its canary configuration can be repaired, adjusted, or switched in real time, thus avoiding system restarts and business interruptions.

[0056] In some embodiments, the attribute information of the atomic capability component also includes a class attribute corresponding to multiple instance versions, where the class attribute is the package path of the JAVA class implementing the atomic capability; accordingly, the atomic capability component in the registration file is instantiated according to the attribute information of the atomic capability component, including: assembling multiple instance versions of the atomic capability component using JAVA reflection tools according to the class attribute to obtain multiple atomic capability instances of the atomic capability component.

[0057] This embodiment can store atomic capability instances in a repository. In some embodiments, atomic capability instances of atomic capability components are stored in isolation, including: storing multiple atomic capability instances of an atomic capability component in the form of key-value pairs in thread-independent data slots.

[0058] For example, the architecture diagram of the AS capability control center can be as follows: Figure 4 As shown, to achieve AS isolation, each AS instance is placed in a thread-independent data slot (implemented using ConcurrentHashMap). During process execution (as shown in steps 205a and 205b), the specified AS instance is first searched using the process version parameter and API parameter. If no instance is specified, the control center matches each AS version according to the canary release rules and returns the specific execution result. It should be noted that AS parameters and execution results can be passed using the process instance context. The definition of multiple versions of the same AS is a prerequisite for the canary release of AS capabilities. During runtime, JDK reflection is used to assemble all AS versions at once, storing them in a ConcurrentHashMap in key-value pairs.

[0059] The AS control center, to enhance the load capacity of AS calls, can be designed as a microservice deployment. It employs a typical probabilistic algorithm to select the appropriate AS instance. A unified APIManager interface class is responsible for querying and proxying AS capabilities.

[0060] Step 203: Create a business process template.

[0061] The business process template uses API interfaces associated with atomic capability components to bind the process steps of the business process to the atomic capability components.

[0062] For example, taking a "automatic SMS activation" business process as an example, the process engine uses the Flowable engine, illustrating how to bind the automated steps with the ActionScript (AS). Here is a modeler design diagram for an automatic SMS activation process: Figure 5 As shown.

[0063] Using the Business Process Modeling Notation (BPMN) design tool provided by the Flowable process engine, API variables can be directly bound to the RequestURL attribute of the template. When the first automatic step of the process, "Create Service," is executed, the Flowable engine will automatically call the API bound to the RequestURL attribute, notifying the control center to find the necessary Action Service (AS) capabilities and obtain the return. The API value is passed here using the variable ${createServiceUrl} primarily to increase the flexibility of the call; it can be passed through a page or configuration, avoiding hardcoding in the BPMN file.

[0064] In the BPMN process description file, the description of the AS being bound is as follows: The definitions node describes the XML specification that this file must conform to, which is also the BPMN specification; the process node is the main content of this file, first defining the process identifier id and name; (the process ID name usually includes version information, such as T005AutoInstall indicating version 005, and the modeler attribute in the AS registration file XML mentioned above is bound to this version information).

[0065] The process node defines the start event startEvent, the end event endEvent, and the execution order of events and stages, sequenceFlow; among them, serviceTask is an automatic process stage, which defines the stage identifier id, name, and the bound atomic service API (usually passed as a variable ${createServiceUrl}).

[0066] Step 204: In response to the execution of the business process based on the business process template, determine whether there is an atomic capability instance of the specified instance version of the target atomic capability component bound to the API interface, based on the process version parameters and API interface parameters.

[0067] Step 205a: If the target atomic capability component has an atomic capability instance of a specified instance version, then the atomic capability instance of the specified instance version is used as the target instance required by the process step found from the isolated and saved atomic capability instances.

[0068] In step 205b, which is parallel to step 205a, if there is no atomic capability instance of the specified instance version of the target atomic capability component, then the grayscale range is filtered according to the grayscale rules corresponding to the multiple instance versions of the target atomic capability component, so as to find the target instance required by the process step from the isolated and saved atomic capability instances.

[0069] Step 206: Obtain the execution result by passing parameters through the process instance context based on the target instance.

[0070] After designing and deploying the BPMN process description file as shown in the above embodiment, the process is started and executed. Taking a "automatic SMS activation" process as an example, the first automatic step, "Service Creation," will notify the control center through the setting of the RequestURL attribute to call the AS component for creating the service. At this time, the AS repository in the control center has been pre-instantiated. To simplify the problem, all AS instances are stateless beans by default, and all parameters and response results are passed through the context of their respective process instances.

[0071] A. If the "Create Service" version modeler attribute is not specified in the AS registration file, the control center will find the instance based on the grayscale range of multiple AS versions and return the execution result.

[0072] B. If the "Create Service" version modeler attribute is specified in the AS registration file, the control center will directly obtain the AS instance of the specified version and return the execution result;

[0073] C. In case of abnormal situations, if the control center cannot find a suitable AS, then notify the operation and maintenance personnel to intervene.

[0074] This embodiment primarily analyzes and explains how to define grayscale rules for different versions of ActionScript (AS), how to dynamically load and refresh AS, how to use BPMN tools to design the binding between processes and AS, and the AS call process executed by the processes. Key technologies involved in this embodiment include: JDK reflection, XML definition and parsing, long-polling monitoring of file data sources, and using ConcurrentHashMap to resolve rule inconsistencies that may result from hot refreshes.

[0075] This embodiment uses XML files to define and register ActionScript (AS), and can dynamically refresh the registration file by listening to the data source through long polling. An AS instantiation scheme is provided: when defining and registering an AS, different versions of the AS service class are used from the Java classpath, and during runtime, AS instances are obtained through JDK reflection assembly, and then placed into a ConcurrentHashMap data slot according to Key-Value pairs. In addition, this embodiment provides a method for binding AS to a BPMN: the Flowable workflow engine can bind the corresponding AS API through the RequestURL attribute of the automatic process.

[0076] This embodiment primarily analyzes, defines, and registers multiple versions of Active Directory (AS), supporting the setting of gray-scale rules and optional specification of process versions to solve the isolation problem of shared AS capabilities when different process instance stages are executed. The areas this embodiment addresses are mainly in the field of business process orchestration, etc. It should be noted that the AS concept in this embodiment refers to AS in orchestrating business processes, not atomic capabilities in a broader sense. Therefore, the AS in this embodiment can only achieve the above-mentioned implementation objectives when used in conjunction with a process.

[0077] Existing technical solutions largely fail to address how to define and isolate AS components in the process orchestration field. They mostly focus on facilitating rapid, system-level canary deployments, which are completely different from the analysis methods, code design, and implementation goals of this embodiment. Compared to existing technical solutions, this embodiment abstracts and defines and registers AS components in the orchestration process, enabling the release of different versions of the same AS through code. This code-level granular canary deployment scheme significantly saves server resources compared to system-level canary deployment schemes.

[0078] This embodiment proposes the design and construction of an independent capability control center. Through a long-polling listening mechanism, AS configurations can be dynamically added or modified, achieving truly seamless upgrades. Furthermore, the modular centralized management of AS capabilities proposed in this embodiment, through AOP monitoring, allows for real-time tracking of the execution performance and anomalies of each AS version, achieving truly refined AS management.

[0079] Furthermore, as Figure 1 and Figure 2 The specific implementation of the method shown in this embodiment provides a business process orchestration device, such as... Figure 6 As shown, the device includes: an acquisition module 31, a processing module 32, a creation module 33, and an execution module 34.

[0080] The acquisition module 31 is configured to acquire the registration file of the atomic capability component. The registration file stores the attribute information of at least one atomic capability component. The attribute information includes grayscale rules corresponding to multiple instance versions. The atomic capability component has an associated API interface.

[0081] The processing module 32 is configured to instantiate the atomic capability component in the registration file according to the attribute information, and to isolate and save the atomic capability instance of the atomic capability component.

[0082] Module 33 is configured to create a business process template, in which the business process template uses the API interface associated with the atomic capability component to bind the process steps of the business process to the atomic capability component;

[0083] The execution module 34 is configured to respond to the execution of a business process based on the business process template by calling the bound API interface to find the target instance required for the process step from the isolated and saved atomic capability instances, and obtain the execution result based on the target instance.

[0084] In some examples of this embodiment, the execution module 34 is specifically configured to determine whether the target atomic capability component bound to the API interface has an atomic capability instance of a specified instance version based on the process version parameters and API interface parameters; if the target atomic capability component has an atomic capability instance of a specified instance version, then the atomic capability instance of the specified instance version is used as the target instance.

[0085] In some examples of this embodiment, the execution module 34 is further configured to, if the target atomic capability component does not have an atomic capability instance of a specified instance version, perform grayscale range filtering according to the grayscale rules corresponding to the multiple instance versions of the target atomic capability component to find the target instance.

[0086] In some examples of this embodiment, the attribute information also includes class attributes corresponding to multiple instance versions, where the class attribute is the package path of the JAVA class implementing the atomic capability; correspondingly, the processing module 32 is specifically configured to assemble multiple instance versions of the atomic capability component using JAVA reflection tools based on the class attribute to obtain multiple atomic capability instances of the atomic capability component.

[0087] In some examples of this embodiment, the processing module 32 is further configured to store multiple atomic capability instances of the atomic capability component in the form of key-value pairs in thread-independent data slots.

[0088] In some examples of this embodiment, the processing module 32 is also configured to monitor the registration file through a polling mechanism; when an update is detected in the registration file, it dynamically refreshes the file based on the updated registration file so as to continue executing the business process according to the atomic capability components in the updated registration file.

[0089] In some examples of this embodiment, the execution module 34 is further configured to obtain the execution result based on the target instance through the process instance context parameters.

[0090] It should be noted that, for other corresponding descriptions of the various functional units involved in the business process orchestration device provided in this embodiment, please refer to... Figure 1 and Figure 2 The corresponding descriptions in [the document] will not be repeated here.

[0091] Based on the above, Figure 1 and Figure 2 Accordingly, this embodiment also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described method. Figure 1 and Figure 2 The method shown.

[0092] Based on this understanding, the technical solution of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as CD-ROM, USB flash drive, mobile hard drive, etc.) and includes several instructions to cause a computer device (such as personal computer, server, or network device, etc.) to execute the methods of various implementation scenarios of this application.

[0093] Based on the above, Figure 1 and Figure 2 The method shown, and Figure 6 To achieve the above objectives, the present application also provides an electronic device, such as a personal computer, server, laptop computer, intelligent robot, or other intelligent terminal, as illustrated in the virtual device embodiment. This device includes a storage medium and a processor; the storage medium stores a computer program; the processor executes the computer program to implement the above-described virtual device. Figure 1 and Figure 2 The method shown.

[0094] Optionally, the aforementioned physical devices may also include a user interface, a network interface, a camera, radio frequency (RF) circuitry, sensors, audio circuitry, a Wi-Fi module, etc. The user interface may include a display screen, input units such as a keyboard, etc., and optional user interfaces may also include USB interfaces, card reader interfaces, etc. The network interface may optionally include standard wired interfaces, wireless interfaces (such as Wi-Fi interfaces), etc.

[0095] Those skilled in the art will understand that the physical device structure provided in this embodiment does not constitute a limitation on the physical device, and may include more or fewer components, or combine certain components, or have different component arrangements.

[0096] The storage medium may also include an operating system and a network communication module. The operating system is a program that manages the hardware and software resources of the aforementioned physical device, supporting the operation of information processing programs and other software and / or programs. The network communication module is used to enable communication between the various components within the storage medium, as well as communication with other hardware and software in the information processing physical device.

[0097] Through the above description of the implementation methods, those skilled in the art can clearly understand that this application can be implemented using software plus necessary general-purpose hardware platforms, or it can be implemented through hardware. By applying the solution of this embodiment, compared with the existing technology, this embodiment abstracts and defines and registers the AS in the orchestration business, and realizes the release of different versions of the same AS through code. This code-level granular gray-scale solution will greatly save server resources compared with the system-level gray-scale implementation. This embodiment proposes to design and build an independent capability control center. Through the design of a long-polling listening mechanism, AS configurations can be dynamically added or modified, truly achieving seamless upgrades. Moreover, the modular centralized management of AS capabilities proposed in this embodiment, through AOP monitoring, can track the execution performance and anomalies of each version of AS in real time, truly achieving refined management of AS.

[0098] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0099] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A business process orchestration method, characterized in that, include: Obtain the registration file of the atomic capability component. The registration file stores the attribute information of at least one atomic capability component. The attribute information includes grayscale rules corresponding to multiple instance versions. The atomic capability component has associated API interfaces. Based on the attribute information, the atomic capability component in the registration file is instantiated, and the atomic capability instance of the atomic capability component is isolated and saved. Create a business process template, in which the process steps of the business process are bound to the atomic capability components using the API interfaces associated with the atomic capability components; In response to executing a business process based on the business process template, the system calls the bound API interface to find the target instance required for the process step from the isolated and saved atomic capability instances, and obtains the execution result based on the target instance.

2. The method according to claim 1, characterized in that, The step of retrieving the target instance required for a process step from the isolated and stored atomic capability instances by calling the bound API interface includes: Based on the process version parameters and API interface parameters, determine whether the target atomic capability component bound to the API interface has an atomic capability instance of the specified instance version; If a specified instance version of the target atomic capability component exists, then the specified instance version of the atomic capability instance is used as the target instance.

3. The method according to claim 2, characterized in that, After determining whether an atomic capability instance of the specified instance version exists for the target atomic capability component bound to the API interface based on the process version parameters and API interface parameters, the process also includes: If the target atomic capability component does not have a specified instance version of the atomic capability instance, then the grayscale range is filtered according to the grayscale rules corresponding to the multiple instance versions of the target atomic capability component to find the target instance.

4. The method according to claim 1, characterized in that, The attribute information also includes a class attribute corresponding to multiple instance versions, where the class attribute is the package path of the JAVA class that implements atomic capabilities; The step of instantiating the atomic capability component in the registration file based on the attribute information includes: Based on the class attribute, multiple instance versions of the atomic capability component are assembled using JAVA reflection tools to obtain multiple atomic capability instances of the atomic capability component.

5. The method according to claim 4, characterized in that, The method of isolating and saving atomic capability instances of atomic capability components includes: Multiple atomic capability instances of an atomic capability component are stored as key-value pairs in thread-independent data slots.

6. The method according to claim 1, characterized in that, The method further includes: The registration files are monitored through a polling mechanism; When an update is detected in the registration file, the system is dynamically refreshed based on the updated registration file to continue executing the business process according to the atomic capability components in the updated registration file.

7. The method according to any one of claims 1 to 6, characterized in that, The step of obtaining the execution result based on the target instance includes: The execution result is obtained by passing parameters through the process instance context based on the target instance.

8. A business process orchestration device, characterized in that, include: The acquisition module is configured to acquire the registration file of the atomic capability component. The registration file stores the attribute information of at least one atomic capability component. The attribute information includes grayscale rules corresponding to multiple instance versions. The atomic capability component has an associated API interface. The processing module is configured to instantiate the atomic capability component in the registration file according to the attribute information, and to isolate and save the atomic capability instance of the atomic capability component. The creation module is configured to create business process templates, in which the business process templates utilize API interfaces associated with atomic capability components to bind the process steps of the business process to the atomic capability components; The execution module is configured to respond to the execution of a business process based on the business process template by calling the bound API interface to find the target instance required for the process step from the isolated and saved atomic capability instances, and obtain the execution result based on the target instance.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 7.

10. An electronic device comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 7.

Images