WO2019218470A1

WO2019218470A1 - Service data processing method and apparatus, electronic device and medium

Info

Publication number: WO2019218470A1
Application number: PCT/CN2018/097314
Authority: WO
Inventors: 张家峰; 邹国忠
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-05-14
Filing date: 2018-07-27
Publication date: 2019-11-21
Also published as: CN108664289B; CN108664289A

Abstract

The present application is applicable to the field of artificial intelligence technology, and provides a service data processing method and apparatus, an electronic device, and a medium. The method comprises: receiving request data inputted by a user; parsing a deployment descriptor in the request data, to determine a servlet interface that the user requests to access, and loading an application.xml file by means of the servlet interface; invoking, on the basis of the application.xml file, more than one script component from a component library, so as to generate a service component; processing the request data by means of the service component, and controlling a distributed middleware zookeeper to detect whether a processing error occurs; if a processing error occurs, locating an abnormal script component, rolling back the abnormal script component to update the service component, and returning to execute the step of processing the request data by means of the service component and controlling the distributed middleware zookeeper to detect whether a processing error occurs; if no processing error occurs, outputting a processing result of the request data, so as to reduce the difficulty and workload of engineers in processing service data whilst facilitating monitoring and maintaining processing programs.

Description

Method, device, electronic device and medium for processing business data

The present application claims priority to Chinese Patent Application No. 201810456930.6, entitled "Processing Method for Business Data and Electronic Equipment", filed on May 14, 2018, the entire contents of which is incorporated herein by reference. in.

Technical field

The present application belongs to the field of artificial intelligence technologies, and in particular, to a method for processing service data and an electronic device.

Background technique

When a web application system provides an accessible application, the mapping relationship between the application identifier of the application and each processor is generally configured in web.xml or context.xml. After the web application system receives the request, according to the mapping relationship between the application identifier of the application and each processor, the corresponding processor is searched through the interface of each processor, and the request is forwarded to the corresponding processor.

However, the existing processing method of sending a request to the corresponding processor is cumbersome. When the routing rule changes, it is difficult to adjust the routing rule according to the setting of the application. In addition, when a new application is dynamically added in a processor during system operation, the system receives the request and cannot be processed by the newly added application. Therefore, the processing method of the business data has technical problems of poor flexibility and low processing efficiency.

technical problem

In the prior art, when the service data is processed, the amount of processed data is too large, and the maintenance and repair cost is high.

Technical solution

A first aspect of the embodiments of the present application provides a method for processing service data, including:

Receiving request data input by the user; parsing the deployment descriptor in the request data to determine a servlet interface requested by the user, and loading the application.xml file through the servlet interface; and acquiring more than one based on the application.xml file a script component in the component library, generating a service component; processing the request data by the service component, and controlling whether the distributed middleware zookeeper monitors whether a processing error occurs; if a processing error occurs, the abnormal script component is located And rolling back the abnormal script component to update the service component, and returning to perform processing on the request data by the service component, and controlling the distributed middleware zookeeper to monitor whether a processing error occurs If the processing error does not occur, the processing result of the request data is output.

A second aspect of the embodiments of the present application provides a service data processing apparatus, where the service data processing apparatus includes a module for executing the processing method of the service data according to the first aspect.

A third aspect of the embodiments of the present application provides an electronic device including a memory and a processor, wherein the memory stores computer readable instructions executable on the processor, the processor executing the computer The steps of the processing method of the business data as described in the first aspect are implemented when the instruction is read.

A fourth aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions, the computer readable instructions being executed by a processor to implement the first aspect as described in the first aspect The steps of the method of processing business data.

Beneficial effect

In the embodiment of the present application, the request data input by the user is received; the deployment descriptor in the request data is parsed to determine a servlet interface requested by the user, and the application.xml file is loaded through the servlet interface; The .xml file retrieves a script component in more than one component library, generates a service component, processes the request data through the service component, and controls whether the distributed middleware zookeeper monitors whether a processing error occurs; if a processing error occurs, Or positioning an abnormal script component, and rolling back the abnormal script component to update the service component, and returning execution to process the request data by using the service component, and controlling the distributed middleware zookeeper The step of monitoring whether a processing error occurs; if no processing error occurs, the processing result of the requested data is outputted, so as to reduce the difficulty and workload of the engineering personnel in processing the business data, and at the same time, it is advantageous to monitor and maintain the processing program.

DRAWINGS

1 is a flowchart of an implementation of a method for processing service data provided by an embodiment of the present application;

2 is a flowchart of generating a script component provided by an embodiment of the present application;

FIG. 3 is a specific implementation flowchart of a method for processing service data S104 according to an embodiment of the present application;

4 is a structural block diagram of a processing apparatus for service data provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of an electronic device according to an embodiment of the present application.

Embodiments of the invention

In order to explain the technical solutions described in the present application, the following description will be made by way of specific embodiments.

FIG. 1 shows an implementation flow of a method for processing service data provided by an embodiment of the present application, where the method process includes steps S101 to S106. The specific implementation principle of each step is as follows.

S101: Receive request data input by a user.

In the embodiment of the present application, the user first inputs the request data that needs to be processed to the processing electronic device of the service data, where the request data includes the service data and the deployment descriptor. It can be understood that the business data is data that the user actually needs to process. For example, in the financial system, if a customer wishes to handle the loan business, the business data can be the customer information of the customer and the loan request data. In addition, the deployment descriptor in the request data is used to describe the deployment of a web application, including: servlet initialization parameters, servlet declarations, servlet mapping, and session configuration. It can be understood that the processing electronic device of the business data can acquire what kind of data the user wishes to process by requesting the data, and through which program the data is processed.

S102. Parse the deployment descriptor in the request data to determine a servlet interface requested by the user, and load the application.xml file through the servlet interface.

Optionally, the embodiment of the present application processes the request data by using a JavaEE program.

Optionally, after the request data is obtained, a unique servlet interface can be determined according to the servlet declaration, the servlet mapping, and the session configuration in the deployment descriptor, and a unique application.xml file can be loaded through the servlet interface. Notably, in the embodiment of the present application, the application.xml file includes configuration information of multiple component libraries, such as an engine configuration and a Visit configuration.

It can be understood that, in the embodiment of the present application, more than one script component is actually used to process the service data in the request data, and the configuration information in the application.xml file can be used to find and call the script component. Component library.

Notably, in order to reduce the development and compilation of the script component by the engineering staff when processing the same or similar business data, the embodiment of the present application pre-writes and stores a plurality of script components before step S101.

As an embodiment of the present application, as shown in FIG. 2, before the request data input by the user is received, a process of generating a script component is further included as follows:

S201. Store a script component written in the Groovy language in the component library after naming, and register a component specification of the script component in a .library file, where the component specification is used to define a path of the script component.

Understandably, the Groovy language is a JVM-based agile development language that combines many of the features of Python, Ruby, and Smalltalk, and Groovy code can be combined with Java code and can be used to extend existing code. In addition, the Groovy language is an object-oriented programming language that can be used both for object-oriented programming and purely scripting languages, and is well suited for use in financial systems to handle massively distributed storage. Data that can be processed by logic.

Optionally, after writing a script component in the Groovy language, the component specification of the script component is registered in the .library file. In the embodiment of the present application, the component specification defines the path of the script component, and the .library file serves as a library project folder. By registering each component specification, the processing electronic device of the business data can be conveniently invoked in a subsequent step.

S202. Register configuration information of the component library in the application.xml file.

It can be understood that, in the embodiment of the present application, when the script component needs to be invoked, the electronic device first determines a corresponding application.xml file through the servlet interface, and invokes the corresponding component library according to the configuration information in the application.xml file. Then, each component specification is registered in the .library file to determine the script components for processing the request data. Therefore, in the subsequent processing of the business data, the servlet interface can directly call these pre-written script components without repeatedly writing a script component for each request data, thereby improving the processing efficiency of the service data in the request data. At the same time, labor costs are reduced.

Further, in the embodiment of the present application, the method for processing the service data is further characterized by: after receiving the notification of the change of the script component, starting the update thread, loading the updated script component in the component library, and refresh cache.

It can be understood that, in the embodiment of the present application, although the script components are pre-written and generated, it is not required to write a new script component every time the request receipt is received, but the script components are not constant. Change, the specific logic and code there is the possibility of updating. Therefore, when the engineer modifies a script component, the electronic device in the embodiment of the present application receives a script component to notify, and then loads the updated script component and updates the cache.

S103. Acquire a script component in one or more component libraries based on the application.xml file to generate a service component.

In the embodiment of the present application, the service data included in one request data may need to be processed by multiple script components together, so the processing electronic device of the service data supports the stitching superposition of the script components.

According to the above embodiment, in the process of generating the script component, a plurality of configuration information is registered in the application.xml file, and according to the configuration information, the corresponding component library can be locked, and then according to the .library file corresponding to each component library. In the component specification, the script component is called. In the embodiment of the present application, a plurality of called script components are combined as a service component.

S104. Process the request data by using the service component, and control the distributed middleware zookeeper to monitor whether a processing error occurs.

In the embodiment of the present application, since there is a possibility that the request component is processed by the service component after the automatic generation of the service component is generated, a control distributed middleware zookeeper is set for monitoring whether a processing error occurs.

Understandably, zooKeeper is a distributed open source distributed middleware that is an important component of Hadoop and Hbase. Zookeeper is a middleware that provides consistent services for distributed applications, for example, to monitor the processing and results of service components.

As an embodiment of the present application, as shown in FIG. 3, the foregoing S104 includes:

S1041: Generate a path node for each script component in the service component, and register each of the path nodes in the distributed middleware zookeeper.

Notably, in order to facilitate locking the abnormal script component in the subsequent process, in this step, each script component in the service component is assigned a unique path node, and the path node is not necessarily the script component is stored. The real path node in .

S1042. Receive, by the distributed middleware zookeeper, a notification that includes an execution status of the script component, and synchronize the execution state to the path node corresponding to the script component.

Understandably, zookeeper as a distributed middleware will receive notification of the execution status of each script component, and the notification is used to indicate whether the script component is working properly. In addition, the distributed middleware zookeeper will associate each notification with the path node and then cache it.

S1043. Subscribe to an event cached by each path node in the distributed middleware zookeeper, where the event includes an execution status of the script component to monitor whether a processing error occurs.

Notably, in the embodiment of the present application, in consideration of the need to send a notification for indicating a processing error to each device in time, the electronic device is required to subscribe to an event cached by each path node in the distributed middleware zookeeper. Through the above method, the electronic device involved in the embodiment of the present application can know the execution status of each script component in time.

S105. If a processing error occurs, locate an abnormal script component, and roll back the abnormal script component to update the service component, and return execution to process the request data by using the service component. And control the distributed middleware zookeeper to monitor whether there is a processing error step.

As described in the foregoing embodiment, in the embodiment of the present application, the script component has an update, so if a script component is locked as an execution error by the zookeeper, it proves that the script component has a problem after the update, so the script component is rolled back to the previous one. version. Furthermore, since a script component contained in the service component is rolled back, it is equivalent to updating the current service component.

After the above-mentioned rollback process is completed, the embodiment of the present application still monitors whether a processing error occurs in real time.

Optionally, if a processing error occurs, an exception stack log is generated and the exception stack log is synchronized to the log platform.

S106. If no processing error occurs, outputting the processing result of the request data.

Optionally, if no processing error occurs, the control user interaction interface presents the processing result of the request data to the user.

Comprehensibly, by receiving request data input by the user; parsing the deployment descriptor in the request data to determine a servlet interface requested by the user, and loading an application.xml file through the servlet interface; based on the application.xml The file retrieves the script component in more than one component library, generates a service component, processes the request data through the service component, and controls whether the distributed middleware zookeeper monitors whether a processing error occurs; if a processing error occurs, the file is located. Executing an abnormal script component, and rolling back the abnormal script component to update the service component, and returning execution to process the request data through the service component, and controlling whether the distributed middleware zookeeper monitors whether The processing error occurs; if no processing error occurs, the processing result of the requested data is outputted, so as to reduce the difficulty and workload of the engineering personnel in processing the business data, and at the same time, it is beneficial to monitor and maintain the processing program.

Corresponding to the processing method of the service data described in the foregoing embodiment, FIG. 4 is a structural block diagram of the processing apparatus for the service data provided by the embodiment of the present application. For the convenience of description, only the related to the embodiment of the present application is shown. section.

Referring to Figure 4, the apparatus includes:

The receiving module 401 is configured to receive request data input by a user;

The parsing module 402 is configured to parse the deployment descriptor in the request data to determine a servlet interface requested by the user, and load the application.xml file through the servlet interface;

The calling module 403 is configured to retrieve a script component in one or more component libraries based on the application.xml file to generate a service component;

The monitoring module 404 is configured to process the request data by using the service component, and control whether the distributed middleware zookeeper monitors whether a processing error occurs;

a first execution module 405, configured to locate an abnormal script component if a processing error occurs, and roll back the abnormal script component to update the service component, and return to execute the service component pair Describe the request data for processing, and control the distributed middleware zookeeper to monitor whether there is a processing error step;

The second execution module 406 is configured to output a processing result of the request data if a processing error does not occur.

Further, before the receiving the request data input by the user, the method further includes:

a script component written in the Groovy language is stored in the component library after naming, and a component specification of the script component is registered in a .library file, the component specification is used to define a path of the script component;

Registering the configuration information of the component library in the application.xml file.

Further, it also includes:

After receiving the script component change notification, the update thread is started, the updated script component is loaded in the component library, and the cache is updated.

Further, the controlling distributed middleware zookeeper monitors whether a processing error occurs, including:

Generating a path node for each script component in the service component, and registering each of the path nodes in the distributed middleware zookeeper;

Receiving, by the distributed middleware zookeeper, a notification containing an execution status of the script component, and synchronizing the execution state to the path node corresponding to the script component;

An event of each path node cache in the distributed middleware zookeeper is subscribed, and the event includes an execution status of the script component to monitor whether a processing error occurs.

Further, it also includes:

If a processing error occurs, an exception stack log is generated and the exception stack log is synchronized to the logging platform.

If no processing error occurs, the control user interaction interface presents the processing result of the request data to the user.

In the embodiment of the present application, it is understood that the request data input by the user is received; the deployment descriptor in the request data is parsed to determine a servlet interface requested by the user, and the application.xml file is loaded through the servlet interface. Retrieving a script component in one or more component libraries based on the application.xml file, generating a service component; processing the request data by the service component, and controlling whether the distributed middleware zookeeper monitors whether a processing error occurs; If a processing error occurs, locate an abnormal script component, and roll back the abnormal script component to update the service component, and return execution to process the request data through the service component, and control The distributed middleware zookeeper monitors whether there is a processing error step; if no processing error occurs, the processing result of the requested data is outputted, so as to reduce the difficulty and workload of the engineering personnel processing the business data, and at the same time, it is beneficial to monitor and maintain the processing program. .

FIG. 5 is a schematic diagram of an electronic device according to an embodiment of the present application. As shown in FIG. 5, the electronic device 5 of this embodiment includes a processor 50, a memory 51, and computer readable instructions 52 stored in the memory 51 and operable on the processor 50, such as business data. Processing program. The processor 50 executes the computer readable instructions 52 to implement the steps in the foregoing method for processing various service data, such as steps 101 to 106 shown in FIG. Alternatively, the processor 50, when executing the computer readable instructions 52, implements the functions of the various modules/units in the various apparatus embodiments described above, such as the functions of the units 401 through 406 shown in FIG.

Illustratively, the computer readable instructions 52 may be partitioned into one or more modules/units that are stored in the memory 51 and executed by the processor 50, To complete this application. The one or more modules/units may be a series of computer readable instruction instructions segments capable of performing a particular function, the instruction segments being used to describe the execution of the computer readable instructions 52 in the electronic device 5.

The electronic device 5 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The electronic device may include, but is not limited to, a processor 50, a memory 51. It will be understood by those skilled in the art that FIG. 5 is only an example of the electronic device 5, and does not constitute a limitation on the electronic device 5, and may include more or less components than those illustrated, or combine some components, or different components. For example, the electronic device may further include an input and output device, a network access device, a bus, and the like.

The so-called processor 50 can be a central processing unit (Central Processing Unit, CPU), can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 51 may be an internal storage unit of the electronic device 5, such as a hard disk or a memory of the electronic device 5. The memory 51 may also be an external storage device of the electronic device 5, such as a plug-in hard disk equipped on the electronic device 5, a smart memory card (SMC), and a secure digital (SD). Card, flash card (Flash Card) and so on. Further, the memory 51 may also include both an internal storage unit of the electronic device 5 and an external storage device. The memory 51 is configured to store the computer readable instructions and other programs and data required by the electronic device. The memory 51 can also be used to temporarily store data that has been output or is about to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units as needed. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above. Each functional unit and module in the embodiment may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit, and the integrated unit may be hardware. Formal implementation can also be implemented in the form of software functional units. In addition, the specific names of the respective functional units and modules are only for the purpose of facilitating mutual differentiation, and are not intended to limit the scope of protection of the present application. For the specific working process of the unit and the module in the foregoing system, reference may be made to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the above embodiments, the descriptions of the various embodiments are different, and the parts that are not detailed or described in a certain embodiment can be referred to the related descriptions of other embodiments.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions, which may be stored in a computer readable storage medium. in.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims

A method for processing business data, comprising:

Receiving request data input by a user;

Parsing the deployment descriptor in the request data to determine a servlet interface requested by the user, and loading the application.xml file through the servlet interface;

Retrieving a script component in one or more component libraries based on the application.xml file to generate a service component;

Processing the request data by the service component, and controlling whether the distributed middleware zookeeper monitors whether a processing error occurs;

If a processing error occurs, locate an abnormal script component, and roll back the abnormal script component to update the service component, and return execution to process the request data through the service component, and control The distributed middleware zookeeper monitors whether there is a processing error step;

If no processing error occurs, the processing result of the request data is output.
The method for processing service data according to claim 1, wherein before the receiving the request data input by the user, the method further comprises:

a script component written in the Groovy language is stored in the component library after naming, and a component specification of the script component is registered in a .library file, the component specification is used to define a path of the script component;

Registering the configuration information of the component library in the application.xml file.
The method for processing service data according to claim 2, further comprising:

After receiving the script component change notification, the update thread is started, the updated script component is loaded in the component library, and the cache is updated.
The method for processing service data according to claim 1, wherein the controlling the distributed middleware zookeeper monitors whether a processing error occurs, including:

Generating a path node for each script component in the service component, and registering each of the path nodes in the distributed middleware zookeeper;

Receiving, by the distributed middleware zookeeper, a notification containing an execution status of the script component, and synchronizing the execution state to the path node corresponding to the script component;

An event of each path node cache in the distributed middleware zookeeper is subscribed, and the event includes an execution status of the script component to monitor whether a processing error occurs.
The method for processing service data according to claim 1, further comprising:

If a processing error occurs, an exception stack log is generated and the exception stack log is synchronized to the logging platform.

If no processing error occurs, the control user interaction interface presents the processing result of the request data to the user.
A device for processing business data, comprising:

a receiving module, configured to receive request data input by a user;

a parsing module, configured to parse a deployment descriptor in the request data, to determine a servlet interface requested by the user, and load an application.xml file through the servlet interface;

a calling module, configured to retrieve a script component in one or more component libraries based on the application.xml file, and generate a service component;

a monitoring module, configured to process the request data by using the service component, and control whether the distributed middleware zookeeper monitors whether a processing error occurs;

a first execution module, configured to locate an abnormal script component if a processing error occurs, and roll back the abnormal script component to update the service component, and return execution to the service component Requesting data for processing and controlling the distributed middleware zookeeper to monitor whether there is a processing error step;

And a second execution module, configured to output a processing result of the request data if a processing error does not occur.
The apparatus for processing service data according to claim 6, wherein before the receiving the request data input by the user, the method further comprises:

a script component written in the Groovy language is stored in the component library after naming, and a component specification of the script component is registered in a .library file, the component specification is used to define a path of the script component;

Registering the configuration information of the component library in the application.xml file.
The apparatus for processing business data according to claim 7, further comprising:

After receiving the script component change notification, the update thread is started, the updated script component is loaded in the component library, and the cache is updated.
The apparatus for processing service data according to claim 6, wherein the controlling the distributed middleware zookeeper monitors whether a processing error occurs, including:

Generating a path node for each script component in the service component, and registering each of the path nodes in the distributed middleware zookeeper;

Receiving, by the distributed middleware zookeeper, a notification containing an execution status of the script component, and synchronizing the execution state to the path node corresponding to the script component;

An event of each path node cache in the distributed middleware zookeeper is subscribed, and the event includes an execution status of the script component to monitor whether a processing error occurs.
The apparatus for processing business data according to claim 6, further comprising:

If a processing error occurs, an exception stack log is generated and the exception stack log is synchronized to the logging platform.

If no processing error occurs, the control user interaction interface presents the processing result of the request data to the user.
An electronic device, comprising: a memory and a processor, wherein the memory stores computer readable instructions executable on the processor, and the processor implements the following steps when the computer readable instructions are executed :

Receiving request data input by a user;

Parsing the deployment descriptor in the request data to determine a servlet interface requested by the user, and loading the application.xml file through the servlet interface;

Retrieving a script component in one or more component libraries based on the application.xml file to generate a service component;

Processing the request data by the service component, and controlling whether the distributed middleware zookeeper monitors whether a processing error occurs;

If a processing error occurs, locate an abnormal script component, and roll back the abnormal script component to update the service component, and return execution to process the request data through the service component, and control The distributed middleware zookeeper monitors whether there is a processing error step;

If no processing error occurs, the processing result of the request data is output.
The electronic device according to claim 11, wherein before the receiving the request data input by the user, the method further comprises:

a script component written in the Groovy language is stored in the component library after naming, and a component specification of the script component is registered in a .library file, the component specification is used to define a path of the script component;

Registering the configuration information of the component library in the application.xml file.
The electronic device according to claim 12, further comprising:

After receiving the script component change notification, the update thread is started, the updated script component is loaded in the component library, and the cache is updated.
The electronic device according to claim 11, wherein the controlling distributed middleware zookeeper monitors whether a processing error occurs, including:

Generating a path node for each script component in the service component, and registering each of the path nodes in the distributed middleware zookeeper;

Receiving, by the distributed middleware zookeeper, a notification containing an execution status of the script component, and synchronizing the execution state to the path node corresponding to the script component;

An event of each path node cache in the distributed middleware zookeeper is subscribed, and the event includes an execution status of the script component to monitor whether a processing error occurs.
The electronic device according to claim 11, further comprising:

If a processing error occurs, an exception stack log is generated and the exception stack log is synchronized to the logging platform.

If no processing error occurs, the control user interaction interface presents the processing result of the request data to the user.
A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by at least one processor, implement the following steps:

Receiving request data input by a user;

Parsing the deployment descriptor in the request data to determine a servlet interface requested by the user, and loading the application.xml file through the servlet interface;

Retrieving a script component in one or more component libraries based on the application.xml file to generate a service component;

Processing the request data by the service component, and controlling whether the distributed middleware zookeeper monitors whether a processing error occurs;

If a processing error occurs, locate an abnormal script component, and roll back the abnormal script component to update the service component, and return execution to process the request data through the service component, and control The distributed middleware zookeeper monitors whether there is a processing error step;

If no processing error occurs, the processing result of the request data is output.
The computer readable storage medium according to claim 16, wherein before the receiving the request data input by the user, the method further comprises:

a script component written in the Groovy language is stored in the component library after naming, and a component specification of the script component is registered in a .library file, the component specification is used to define a path of the script component;

Registering the configuration information of the component library in the application.xml file.
The computer readable storage medium of claim 17, further comprising:

After receiving the script component change notification, the update thread is started, the updated script component is loaded in the component library, and the cache is updated.
The computer readable storage medium of claim 16, wherein the controlling the distributed middleware zookeeper monitors whether a processing error occurs, including:

Generating a path node for each script component in the service component, and registering each of the path nodes in the distributed middleware zookeeper;

Receiving, by the distributed middleware zookeeper, a notification containing an execution status of the script component, and synchronizing the execution state to the path node corresponding to the script component;

An event of each path node cache in the distributed middleware zookeeper is subscribed, and the event includes an execution status of the script component to monitor whether a processing error occurs.
The computer readable storage medium of claim 16 further comprising:

If a processing error occurs, an exception stack log is generated and the exception stack log is synchronized to the logging platform.

If no processing error occurs, the control user interaction interface presents the processing result of the request data to the user.