CN117421071B - Visual package method and integrated system for plug-in service - Google Patents
Visual package method and integrated system for plug-in service Download PDFInfo
- Publication number
- CN117421071B CN117421071B CN202311732719.XA CN202311732719A CN117421071B CN 117421071 B CN117421071 B CN 117421071B CN 202311732719 A CN202311732719 A CN 202311732719A CN 117421071 B CN117421071 B CN 117421071B
- Authority
- CN
- China
- Prior art keywords
- plug
- service
- integrated
- ins
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 230000000007 visual effect Effects 0.000 title claims abstract description 8
- 238000011161 development Methods 0.000 claims abstract description 43
- 238000004806 packaging method and process Methods 0.000 claims abstract description 18
- 238000012545 processing Methods 0.000 claims abstract description 17
- 230000007246 mechanism Effects 0.000 claims abstract description 14
- 230000008569 process Effects 0.000 claims description 44
- 238000004590 computer program Methods 0.000 claims description 13
- 238000012800 visualization Methods 0.000 claims description 12
- 230000010354 integration Effects 0.000 claims description 8
- 238000005538 encapsulation Methods 0.000 claims description 4
- 230000002159 abnormal effect Effects 0.000 claims 2
- 238000013506 data mapping Methods 0.000 description 8
- 238000007726 management method Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000000889 atomisation Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000010276 construction Methods 0.000 description 2
- 238000000354 decomposition reaction Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012858 packaging process Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 238000004064 recycling Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention provides a visual packaging method and an integrated system for plug-in service, which relate to the technical field of enterprise informatization data processing, are based on an integrated development platform of a configured plug-in management and flow designer, provide a foundation framework support for the rapid development of the integrated service for enterprise-level information management products, and simplify the development flow of an integrated interface by abstracting and packaging the integrated service and unifying the development mode of the integrated interface; by the integrated service designer for realizing the flow program, the integrated interface is combined, and the whole development and implementation of the integrated service are simplified. The framework layer expansion mechanism is realized, and the rapid development of the integrated service based on the configuration file and the plug-in mechanism is supported.
Description
Technical Field
The disclosure relates to the technical field of enterprise informatization data processing, in particular to a plug-in service visualization packaging method and an integration system.
Background
The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.
Along with the continuous improvement of enterprise informatization degree, in order to break the information island of each application system in the industrial enterprise, the integration requirement of customers on the multi-heterogeneous system is also continuously increased, and in the development process of the information system in the facing industrial industry, the integration mode and the content of each subsystem are different, so that each development product cannot be reused, and considerable development and implementation cost is occupied. In particular, basic functions of integrated development, such as management of integrated interfaces, planning and development of business processes and the like, are handled by each customization project, and lack of unified standards and frameworks, so that repeated development is caused, and problems are not solved.
The traditional custom business development process is to write codes for adaptation according to the client demands of specific projects, and has no standard module division and functional encapsulation mechanism, so that the development results of the existing projects are difficult to effectively multiplex, and the repeated investment of resources and the prolonged construction period are caused; although the plug-in mechanism can be used for packaging and recycling the service, the existing plug-in mechanism of the platform only provides the functions of acquiring and instantiating the plug-in object according to the category and name, and does not provide a calling framework, so that the loading execution process of the plug-in class can only be simplified, but the plug-in cannot be further abstracted to standardize and simplify the development of the specific integrated service node.
In addition, the inventors have found that the flow engine present in existing ICP platforms relies on persisted master data (e.g., objects to be approved), running only one node each time an execution interface is invoked. The integrated business process is only a data flow from the input to the return value, does not depend on persistent main data, and needs to run the whole process once calling, and the existing workflow engine cannot meet the requirement.
Disclosure of Invention
In order to solve the problems, the present disclosure provides a plug-in service visualization packaging method and an integrated system, inherit and extend the existing plug-in mechanism of the existing ICP platform, define plug-ins by using a set configuration file, abstract plug-ins in the integrated service development process into service plug-ins and functional plug-ins, define specific categories in the configuration file, and directly return to the instance of corresponding interface package when obtaining plug-ins according to the categories.
According to some embodiments, the present disclosure employs the following technical solutions:
a visual package method for plug-in service includes:
entering a call inlet to acquire parameter entering and integrated service information;
calling service nodes one by one, using data parameters input during calling to connect the whole integrated service flow calling process in series, executing configured plug-ins one by one, wherein the data objects are the execution results of the last node and serve as the data parameters of the next node;
and the data object is read and modified by the business logic of the plug-in unit, and the execution result returned by the last node is used as the execution result of the whole operation.
Furthermore, when in call, a single interface is adopted, and the whole integrated service is completely operated by single call.
Further, the configured plug-ins are executed node by node, and the plug-ins are abstracted into service plug-ins and functional plug-ins.
Further, a specific class of the plug-in is defined in the configuration file, the exception handling plug-in defines an exception type to be handled, and the class of the plug-in corresponds to an interface which needs to be realized by the class of the plug-in strictly.
Further, when the plug-in is obtained according to the plug-in category, the instance of the corresponding interface package is returned directly.
Further, the plug-in registration is performed by using a hard coding, visual configuration and database storage mode.
Furthermore, when executing the business process, the input parameters are stored or cached in the special memory area in a drop way to replace the data objects in the process of executing the process.
According to some embodiments, the present disclosure employs the following technical solutions:
a plug-in business visualization package integration system, comprising:
the interface calling module is used for entering a calling inlet and acquiring the parameter entering and integrated service information;
the service execution module is used for calling service nodes one by one, connecting the data parameters input during calling with the whole integrated service flow calling process in series, executing configured plug-ins one by one, wherein the data objects are the execution results of the last node and serve as the data parameters of the next node;
and the data object is read and modified by the business logic of the plug-in unit, and the execution result returned by the last node is used as the execution result of the whole operation.
According to some embodiments, the present disclosure employs the following technical solutions:
a non-transitory computer readable storage medium for storing computer instructions which, when executed by a processor, implement the plug-in service visualization packaging method.
According to some embodiments, the present disclosure employs the following technical solutions:
an electronic device, comprising: a processor, a memory, and a computer program; the processor is connected with the memory, the computer program is stored in the memory, and when the electronic equipment runs, the processor executes the computer program stored in the memory so as to enable the electronic equipment to execute and realize the plug-in service visualization packaging method.
Compared with the prior art, the beneficial effects of the present disclosure are:
the plug-in service visualization packaging method provided by the disclosure inherits and expands the existing plug-in mechanism of the ICP platform, and plug-in definition is carried out by adopting a set configuration file. The plug-in the integrated service development process is abstracted into a service plug-in and a functional plug-in (including progress callback and exception handling sub-categories), and the plug-in is classified into the service plug-in and the functional plug-in, so that the loading execution process of the plug-in class can be simplified, the coupling degree and the relativity of each link in the platform can be enhanced, and the whole plug-in service packaging process is optimized. The specific categories are defined in the configuration file, such as exception types which can be processed by the exception processing plug-in, the categories of the plug-ins strictly correspond to interfaces which are needed to be realized by the plug-ins, when the plug-ins are obtained according to the categories, the examples of corresponding interface packages are directly returned, standards and specifications are provided for the atomization decomposition and plug-in atomization packaging of the integrated service, the development process of the integrated service can be simplified, and the development resource investment is saved by multiplexing the packaged plug-ins.
The integrated development platform based on the configuration plug-in management and the flow designer is realized, the foundation framework support for the rapid development of the integrated service is provided for the enterprise-level information management product, and the integrated interface development flow is simplified by abstracting and packaging the integrated service and unifying the integrated interface development mode; by the integrated service designer for realizing the flow program, the integrated interface is combined, and the whole development and implementation of the integrated service are simplified. The framework layer expansion mechanism is realized, and the rapid development of the integrated service based on the configuration file and the plug-in mechanism is supported.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate and explain the exemplary embodiments of the disclosure and together with the description serve to explain the disclosure, and do not constitute an undue limitation on the disclosure.
FIG. 1 is a block diagram of a method of the present disclosure;
Detailed Description
The disclosure is further described below with reference to the drawings and examples.
It should be noted that the following detailed description is illustrative and is intended to provide further explanation of the present disclosure. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments in accordance with the present disclosure. As used herein, the singular is also intended to include the plural unless the context clearly indicates otherwise, and furthermore, it is to be understood that the terms "comprises" and/or "comprising" when used in this specification are taken to specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof.
Term interpretation:
integration business: generally refers to the process of integrating data with other service platforms to perform a particular service.
An integrated service plug-in: in short, the plug-in packages the atomized integrated business into a standardized plug-in, performs a specific business process or basic operation, and can also comprise more complex business processes.
Integrating the business flow: the process is called as unit, and the complete integrated business process executed in one call can include the combination of various business nodes such as data acquisition, processing, pushing and the like.
And integrating the service node: the node for short forms a basic unit of a business process, and each node comprises a business plug-in, may comprise a data processing plug-in and may comprise one or more exception processing plug-ins.
An operation frame: and the core logic framework is responsible for receiving a call request, creating a flow instance, running plug-ins on a node-by-node basis, and processing services such as exception capture, progress callback, automatic log and the like.
Flow example: when the business flow is called, an instance object is created in the operation framework, and the instance object comprises flow template information and necessary information of the operation, such as SessionPara user identity information, SQLTransactiontransaction information, original parameters, data objects and the like.
Data object: also called dataObj, is an object that is circulated during the operation of a business process. The data object comes from the parameters that are transferred in when the flow is called, is processed in each node, and then is transferred to the next node, and finally is used as the return value of the call entry.
Example 1
An embodiment of the present disclosure provides a method for visualizing and packaging a plug-in service, including:
entering a call inlet to acquire parameter entering and integrated service information;
calling service nodes one by one, using data parameters input during calling to connect the whole integrated service flow calling process in series, executing configured plug-ins one by one, wherein the data objects are the execution results of the last node and serve as the data parameters of the next node;
and the data object is read and modified by the business logic of the plug-in unit, and the execution result returned by the last node is used as the execution result of the whole operation.
As an embodiment, the present disclosure aims to implement an integrated development platform based on a configurable plug-in management and flow designer, provide a foundation framework support for rapid development of integrated services for enterprise-level information management products, unify an integrated interface development mode by abstract packaging of the integrated services, and simplify an integrated interface development flow; by the integrated service designer for realizing the flow program, the integrated interface is combined, and the whole development and implementation of the integrated service are simplified. The framework layer expansion mechanism is realized, and the rapid development of the integrated service based on the configuration file and the plug-in mechanism is supported.
Specifically, the integrated development platform comprises an interface calling module, a calling port and a service integrating module, wherein the interface calling module is used for entering a calling port to acquire parameter entering and service integrating information;
the service execution module is used for calling service nodes one by one, connecting the data parameters input during calling with the whole integrated service flow calling process in series, executing configured plug-ins one by one, wherein the data objects are the execution results of the last node and serve as the data parameters of the next node;
and the data object is read and modified by the business logic of the plug-in unit, and the execution result returned by the last node is used as the execution result of the whole operation.
As one example, when calling, a single interface is adopted, and the whole integrated service is completely operated by single call.
Further, the configured plug-ins are executed node by node, and the plug-ins are abstracted into service plug-ins and functional plug-ins.
The plugins in the integrated service development process are abstracted into service plugins and functional plugins (including progress callback and exception handling sub-categories). The specific categories are defined in the configuration file, such as exception types which can be processed by the exception processing plug-in, the categories of the plug-ins strictly correspond to interfaces which are needed to be realized by the plug-ins, when the plug-ins are obtained according to the categories, the examples of corresponding interface packages are directly returned, standards and specifications are provided for the atomization decomposition and plug-in atomization packaging of the integrated service, the development process of the integrated service can be simplified, and the development resource investment is saved by multiplexing the packaged plug-ins.
Further, a specific class of the plug-in is defined in the configuration file, the exception handling plug-in defines an exception type to be handled, and the class of the plug-in corresponds to an interface which needs to be realized by the class of the plug-in strictly.
The integrated interface development method is unified through abstract encapsulation of integrated services, so that the integrated interface development flow is simplified;
further, when the plug-in is obtained according to the plug-in category, the instance of the corresponding interface package is returned directly.
Further, the plug-in registration is performed by using a hard coding, visual configuration and database storage mode.
Furthermore, when executing the business process, the input parameters are stored or cached in the special memory area in a drop way to replace the data objects in the process of executing the process.
As one example, when a business plug-in or progress plug-in throws an exception, the runtime framework captures the exception and matches the exception handling plug-in according to the following rules:
1. the basic way to match exception handling plug-ins is to match the back end of the PluginType field in the exception plug-in configuration (PluginType= "ExceptionHandler: system. Exception") to the current exception class name in full words.
2. Exception handling plug-ins that first match configurations on current nodes
3. If the matching is not achieved, the parent class name of the current exception is taken, and the matching is carried out again until the matching is achieved or the matching is traced back to the system
4. If the exception handling plugin configured on the node fails to match successfully, the exception handling plugin configured on the flow is fetched, and then the steps 2 and 3 are repeated
5. If the exception handling Plugin is still not matched, default exception handling Plugin (PluginType= "ExceptionHandler: default") configured in \Server\platform\integration\Config\Plugin\Default.
After the plugins are successfully matched, the operation framework calls a processing method of the exception processing plugins by taking the exception objects and the current data objects as parameters.
The exception handling method should do necessary processing such as repairing data objects or rollback error operations, etc., based on the parameters. And then returns a bool value. When the method returns true, the operation framework can simulate that the exception is not thrown (but the HadException is marked as true in the return value), and the current value of the data object is transferred to the next service node; when returning to false, the operation framework interrupts the flow operation and returns to SucesFalse.
If the exception handling plug-in throws out the exception, the exception handling plug-in is no longer matched, but is handled by the default exception handling mechanism of the framework.
As one embodiment, the operational flow includes:
1) After the new flow, only the start and end nodes should first start to create service nodes or data mapping nodes.
2) After creating the service node, the service plug-in should be selected first, and then the next operation can be performed. When there are other verification failure problems with the unselected service nodes or property editing areas, no other operations are responded to.
3) After creating the data mapping node, determining the type of the data input and output by the node according to the direction, the mapping type and the set of the data mapping, and matching corresponding front and rear nodes or calling parameters, wherein the method for determining the type of the data input and output by the node comprises the following steps:
a) The Web and timing entry only support the String type input parameters, so if the current configuration of the data mapping node does not accept String input, a node must be connected in series in front to convert the input String parameters into the type supported by the data mapping node; conversely, when the data mapping node is the first node, it can only be configured to receive the state of String input.
b) The Web portal only supports output parameters of String type, and the same is true, either the data mapping node is configured to output String type, or the tandem node performs data serialization thereafter.
c) The flow called by using the background service interface is not limited by input and output types, but the code of the call flow needs to be matched with the flow definition so as to avoid the call error caused by unmatched input and output data types.
4) Each node is connected in turn. Branches and loops cannot exist.
5) According to the service design, functional plug-ins, extension attributes and the like are configured for the nodes and the processes, and the data mapping nodes are configured according to the requirements.
6) And setting available entry of the flow and synchronous and asynchronous according to the requirement.
7) The new flow defaults to an enabled state. If the drawing is not completed and temporary storage is needed, the 'starting' can be canceled, otherwise, the incomplete flow cannot pass the verification.
As one embodiment, the integrated service management includes a timing rule, an entity of each integrated timing task is a timing rule, the timing rule is in a many-to-one relationship with the service flow, an entry of the timing rule management page is located in a system management-integrated service management-timing rule, and the timing rule editing flow includes:
1. the business process uses the reference popup window to select, the selection range is the business process which selects the timing entrance and is in the starting state. And after the selection, carrying out process names and codes, and automatically filling the business process names into the timing rule name field. The business process and the timing rule name are necessary to be filled, and the timing rule name can be edited manually.
2. The timing period is an integer, and the units are sequentially pulled down from year to second. The timing period is a fill and defaults to "day".
3. The execution start time is the time when this timed task is first run. The new construction cannot be performed earlier than the current time.
4. The timing rules may be optionally executed indefinitely. If not infinitely, execution will not be performed after a specified number of executions.
5. When the execution is not infinite, the last execution time or the filling execution times can be selected, one of the execution times is input, and the value of the other is automatically calculated. If the input is executed 10 times, the last execution time is automatically valued as the execution start-stop time+the execution period x (10-1).
6. When the last execution time is manually set, it cannot be earlier than the first execution time and the current time.
7. When executing infinitely, the last execution time and execution times are gray, and the values are ignored.
8. When the selected last execution time is not the exact execution time, the last execution time earlier than the selected time is automatically taken. In particular, when the execution cycle is accurate to seconds, since the display accuracy of the last execution time is minutes, the last execution time is not necessarily accurately displayed.
9. If a task to be executed at 4 am every day is required to be set, the execution start time can be set to be 4 am next, and the period can be set to be 1 day. The rest of the cases can be pushed in this way.
10. The timing task is loaded in the form of a timer based on time intervals. Namely: when loading the timing task, calculating the interval from the current server time to the next execution time, and setting a timer at the interval. If the server time is modified after loading, the loaded timing tasks are not affected. Reloading of the timed task needs to be triggered.
11. The executing timing rule or its bound business process is modified to take effect the next time the timing rule is executed.
12. Editing the save timing rules, switching the timing rules to enable or disable, will trigger the reloading of the timing tasks immediately.
13. The call parameters are equivalent to parameters that are entered when the business process is directly invoked.
Example 2
In one embodiment of the present disclosure, a package integration system for visualizing plug-in services is provided, including:
the interface calling module is used for entering a calling inlet and acquiring the parameter entering and integrated service information;
the service execution module is used for calling service nodes one by one, connecting the data parameters input during calling with the whole integrated service flow calling process in series, executing configured plug-ins one by one, wherein the data objects are the execution results of the last node and serve as the data parameters of the next node;
and the data object is read and modified by the business logic of the plug-in unit, and the execution result returned by the last node is used as the execution result of the whole operation.
Example 3
In one embodiment of the disclosure, a non-transitory computer readable storage medium is provided, where the non-transitory computer readable storage medium is configured to store computer instructions that, when executed by a processor, implement the plug-in service visualization packaging method.
Example 4
In one embodiment of the present disclosure, there is provided an electronic device including: a processor, a memory, and a computer program; the processor is connected with the memory, the computer program is stored in the memory, and when the electronic equipment runs, the processor executes the computer program stored in the memory so as to enable the electronic equipment to execute and realize the plug-in service visualization packaging method.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the specific embodiments of the present disclosure have been described above with reference to the drawings, it should be understood that the present disclosure is not limited to the embodiments, and that various modifications and changes can be made by one skilled in the art without inventive effort on the basis of the technical solutions of the present disclosure while remaining within the scope of the present disclosure.
Claims (6)
1. The plug-in service visualization packaging method is characterized by comprising the following steps of:
entering a call inlet to acquire parameter entering and integrated service information;
calling service nodes one by one, using data parameters input during calling to connect the whole integrated service flow calling process in series, executing configured plug-ins one by one, wherein the data objects are the execution results of the last node and serve as the data parameters of the next node; executing configured plug-ins from node to node, wherein the plug-ins are abstracted into service plug-ins and functional plug-ins;
when the integrated service is called, a single interface is adopted, and the whole integrated service is completely operated by single call;
defining a specific class of the plug-in the configuration file, and defining an abnormal type of the processing by the exception processing plug-in, wherein the class of the plug-in strictly corresponds to an interface which needs to be realized by the class of the plug-in; when obtaining the plug-in according to the plug-in category, directly returning to the instance of the corresponding interface package;
the data object is read and modified by the business logic of the plug-in unit, and the execution result returned by the last node is used as the execution result of the whole operation;
the integrated interface development method is unified through abstract encapsulation of integrated services, so that the integrated interface development flow is simplified; the integrated service designer for realizing the flow program combines the integrated interfaces, so that the integral development and implementation of the integrated service are simplified, and the expansion mechanism of the framework layer is realized; the integrated service management comprises timing rules, the entity of each integrated timing task is the timing rules, the timing rules are in a many-to-one relation with the service flow, and the entrance of the timing rule management page is positioned in the system management-integrated service management-timing rules.
2. The method for visual package of plug-in service according to claim 1, wherein the plug-in registration is performed by using hard coding, visual configuration and database storage modes.
3. The method for visualizing package for plug-in service according to claim 1, further comprising: when executing the business process, the input parameters are stored or cached in the special area of the memory in a drop way to replace the data objects in the process of executing the process.
4. A plug-in service visualization package integration system, comprising:
the interface calling module is used for entering a calling inlet and acquiring the parameter entering and integrated service information;
the service execution module is used for calling service nodes one by one, connecting the data parameters input during calling with the whole integrated service flow calling process in series, executing configured plug-ins one by one, wherein the data objects are the execution results of the last node and serve as the data parameters of the next node; executing configured plug-ins from node to node, wherein the plug-ins are abstracted into service plug-ins and functional plug-ins;
when the integrated service is called, a single interface is adopted, and the whole integrated service is completely operated by single call;
defining a specific class of the plug-in the configuration file, and defining an abnormal type of the processing by the exception processing plug-in, wherein the class of the plug-in strictly corresponds to an interface which needs to be realized by the class of the plug-in; when obtaining the plug-in according to the plug-in category, directly returning to the instance of the corresponding interface package;
the data object is read and modified by the business logic of the plug-in unit, and the execution result returned by the last node is used as the execution result of the whole operation;
the integrated interface development method is unified through abstract encapsulation of integrated services, so that the integrated interface development flow is simplified; the integrated service designer for realizing the flow program combines the integrated interfaces, so that the integral development and implementation of the integrated service are simplified, and the expansion mechanism of the framework layer is realized; the integrated service management comprises timing rules, the entity of each integrated timing task is the timing rules, the timing rules are in a many-to-one relation with the service flow, and the entrance of the timing rule management page is positioned in the system management-integrated service management-timing rules.
5. A non-transitory computer readable storage medium storing computer instructions which, when executed by a processor, implement a plug-in service visualization packaging method according to any of claims 1-3.
6. An electronic device, comprising: a processor, a memory, and a computer program; wherein the processor is connected to the memory, and the computer program is stored in the memory, and when the electronic device is running, the processor executes the computer program stored in the memory, so that the electronic device executes a method for realizing the plug-in service visualization packaging according to any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311732719.XA CN117421071B (en) | 2023-12-18 | 2023-12-18 | Visual package method and integrated system for plug-in service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311732719.XA CN117421071B (en) | 2023-12-18 | 2023-12-18 | Visual package method and integrated system for plug-in service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117421071A CN117421071A (en) | 2024-01-19 |
| CN117421071B true CN117421071B (en) | 2024-03-29 |
Family
ID=89531084
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311732719.XA Active CN117421071B (en) | 2023-12-18 | 2023-12-18 | Visual package method and integrated system for plug-in service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117421071B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103870274A (en) * | 2014-03-14 | 2014-06-18 | 浪潮集团山东通用软件有限公司 | Visual development assembly for realizing data interaction between heterogeneous systems based on web service technology |
| CN104331289A (en) * | 2014-10-31 | 2015-02-04 | 北京思特奇信息技术股份有限公司 | Method and device for applying plug-in design application to flow processing |
| CN111176645A (en) * | 2019-12-30 | 2020-05-19 | 国电南瑞科技股份有限公司 | Power grid big data application-oriented data integration management system and implementation method thereof |
| CN113157792A (en) * | 2021-05-10 | 2021-07-23 | 中国工商银行股份有限公司 | Interface document management system and working method thereof |
| CN113469647A (en) * | 2021-06-23 | 2021-10-01 | 广州鲁邦通智能科技有限公司 | Enterprise information integration system and business processing method |
| CN113918457A (en) * | 2021-10-13 | 2022-01-11 | 珠海市新德汇信息技术有限公司 | Unified integration method based on various acquisition devices |
| CN115934180A (en) * | 2022-10-18 | 2023-04-07 | 上海易立德信息技术股份有限公司 | Workflow engine implementation method, system, device and medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7519976B2 (en) * | 2002-05-01 | 2009-04-14 | Bea Systems, Inc. | Collaborative business plug-in framework |
| US7627631B2 (en) * | 2002-05-02 | 2009-12-01 | Bea Systems, Inc. | Systems and methods for collaborative business plug-ins |
-
2023
- 2023-12-18 CN CN202311732719.XA patent/CN117421071B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103870274A (en) * | 2014-03-14 | 2014-06-18 | 浪潮集团山东通用软件有限公司 | Visual development assembly for realizing data interaction between heterogeneous systems based on web service technology |
| CN104331289A (en) * | 2014-10-31 | 2015-02-04 | 北京思特奇信息技术股份有限公司 | Method and device for applying plug-in design application to flow processing |
| CN111176645A (en) * | 2019-12-30 | 2020-05-19 | 国电南瑞科技股份有限公司 | Power grid big data application-oriented data integration management system and implementation method thereof |
| CN113157792A (en) * | 2021-05-10 | 2021-07-23 | 中国工商银行股份有限公司 | Interface document management system and working method thereof |
| CN113469647A (en) * | 2021-06-23 | 2021-10-01 | 广州鲁邦通智能科技有限公司 | Enterprise information integration system and business processing method |
| CN113918457A (en) * | 2021-10-13 | 2022-01-11 | 珠海市新德汇信息技术有限公司 | Unified integration method based on various acquisition devices |
| CN115934180A (en) * | 2022-10-18 | 2023-04-07 | 上海易立德信息技术股份有限公司 | Workflow engine implementation method, system, device and medium |
Non-Patent Citations (2)
| Title |
|---|
| StkTokens: enforcing well-bracketed control flow and stack encapsulation using linear capabilities;Lau Skorstengaard;Proceedings of the ACM on Programming Languages;20190102;全文 * |
| 基于SOA的中小制造企业业务流程的集成;简斌;闫光荣;朱心雄;;计算机辅助设计与图形学学报;20070120(第01期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117421071A (en) | 2024-01-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108614770B (en) | Automatic test assertion method, device, storage medium and equipment | |
| CN107273286B (en) | Scene automatic test platform and method for task application | |
| CN113032244B (en) | Interface test method, device, computer system and computer readable storage medium | |
| CN112035363A (en) | Automatic interface testing method and device | |
| CN103186463B (en) | Determine the method and system of the test specification of software | |
| CN115422063A (en) | Low-code interface automation system, electronic equipment and storage medium | |
| Wahler et al. | CAST: Automating software tests for embedded systems | |
| CN113961332A (en) | Method and device for realizing workflow engine, electronic equipment and storage medium | |
| CN113868120A (en) | Industrial software debugging method and device, computer equipment and storage medium | |
| CN115860451A (en) | Flow operation method and device, electronic equipment and storage medium | |
| CN117421071B (en) | Visual package method and integrated system for plug-in service | |
| KR100994070B1 (en) | A Reserved Component Container Based Software Development Method and Apparatus | |
| CN113254350A (en) | Flink operation testing method, device, equipment and storage medium | |
| CN112463143A (en) | DAG-based dynamic rearrangement method | |
| CN111752806A (en) | Method for acquiring IO (input/output) indexes of virtual disk in cloud environment | |
| CN111897738A (en) | Automatic testing method and device based on atomic service | |
| CN115113909A (en) | Project automation operation and maintenance method, system, electronic equipment and storage medium | |
| CN115292072A (en) | Visual business flow arrangement method, device and storage medium | |
| CN109933308A (en) | The customed general-purpose system of remote sensing satellite data prediction flow path visual based on MPI+CUDA | |
| CN113987044A (en) | Asset data import processing method and device and electronic equipment | |
| CN114564213A (en) | Pre-installed software deployment method, system, terminal and storage medium | |
| Heijstek et al. | Effort distribution in model-based development | |
| CN110727475A (en) | Intelligent service calling method based on configuration | |
| CN111401020A (en) | Interface loading method and system and computing equipment | |
| CN115292418B (en) | Cross-system business process automatic processing method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |