CN109062548B - Web service expansion method and system based on workflow construction - Google Patents
Web service expansion method and system based on workflow construction Download PDFInfo
- Publication number
- CN109062548B CN109062548B CN201810726354.2A CN201810726354A CN109062548B CN 109062548 B CN109062548 B CN 109062548B CN 201810726354 A CN201810726354 A CN 201810726354A CN 109062548 B CN109062548 B CN 109062548B
- Authority
- CN
- China
- Prior art keywords
- workflow
- function
- web
- layer
- flow
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the technical field of workflow, in particular to a method and a system for Web service expansion based on workflow construction, which are different in that: the method comprises the following steps: creating a class library project, adding a function code according to a function required to be realized by the process, and compiling to generate a shared dynamic link library file; registering a shared dynamic link library file, and a functional module and a function thereof on a Web node of a functional warehouse; building a workflow on a visual interface; deploying a workflow onto a service manager; the Web end asynchronously calls the workflow and returns the result to the Web end; the system comprises a dynamic link library file generation layer, a function registration layer, a function test layer, a workflow building layer, a workflow distribution layer and a Web service expansion layer. The invention accurately and rapidly asynchronously calls the workflow, realizes the sharing of data and functional resources, has low popularization cost and is easy to spread.
Description
Technical Field
The invention relates to the technical field of workflow, in particular to a method and a system for Web service expansion based on workflow construction.
Background
The workflow technology originates from the office and production field, and refers to the idea that a transaction is proposed by running according to a certain specific flow; for example, in the field of production organization, production activities have various forms, and the production activities are divided into a plurality of contents to complete tasks, such as rule making, personnel roles, flow arrangement, task execution time and the like; the workflow technology starts in the 70 s of the 20 th century, the research work starts in the 80 s, and the FileNet company develops office products using the workflow technology at the earliest, and mainly links graph scanning, keyword indexing and the like together, so that an integrated assembly is generated, and the assembly provides a direction for the development of the workflow technology; after 90 s, due to the rapid development of computer network technology, the research and development of workflow technology has entered a new period, and many large software companies began to develop specialized workflow devices;
in 1993, the international Workflow Management alliance (WfMC) was established in europe, which marks the beginning of Workflow technology into a relatively mature stage; in order to realize the interoperation between different workflow products, the WfMC establishes a series of standards in terms of related terms, architecture, application programming interfaces and the like of a workflow management device; the workflow definition given by the workflow alliance is: the workflow refers to full automation or semi-automation of the whole or part of the operation process under the support of a computer; in practice, all processes whose execution is controlled by a computer software means (workflow management means) can be more broadly called workflows;
web (world Wide web), a global Wide area network, also called world Wide web, is a hypertext and HTTP based, global, dynamic interactive, cross-platform distributed graphical information device, is a network service established on the Internet, provides a graphical, easy-to-access visual interface for a browser to search and browse information on the Internet, wherein documents and hyperlinks organize information nodes on the Internet into a mutually-associated mesh structure;
in 1989, a new protocol for the Internet and a document device using the protocol were submitted by a group led by Tim Berners-Lee in CERN (european particle physics institute), which named the new device WordWide Web, aiming to enable global scientists to communicate their own work documents using the Internet, designed to allow any user on the Internet to search and retrieve documents from the databases of many document service computers; the basic framework of this new device was developed and implemented in one computer in CERN by the end of 1990, and it was transplanted to other computer platforms and formally released in 1991;
the five biggest characteristics of the Web are: imaging, platform independence, distribution, dynamics and interactivity;
and (3) Web graphical: an important reason for the popularity of the Web is that the Web can simultaneously display colorful graphics and texts on one page, information on the Internet before the Web is only in a text form, and the Web can provide the characteristic of integrating graphics, audio and video information into a whole, namely the imaging of the Web;
the web is platform independent: whatever the device platform of the user, you can access the WWW through the Internet, and the device platform is not limited by WWW browsing, and the WWW can be accessed from the Windows platform, the UNIX platform, the Macintosh platform and other platforms, and the access to the WWW is realized by software called a browser (browser), such as Firefox of Mozilla, Chrome of Google, Internet Explorer of Microsoft and the like;
distributed nature of the Web: a large amount of graphic, audio and video information occupies a considerable disk space, and even the amount of information cannot be predicted; for Web, all information does not need to be put together, the information can be put on different sites, and only the site needs to be indicated in a browser, the information of one site is not necessarily logically integrated physically, and the information is integrated from the perspective of a user, so that the distributed characteristic of the Web is embodied;
the dynamic property of the Web: because the information of each Web site contains the information of the site itself, the information provider can update the information on the site frequently, such as the development status of a certain agreement, the advertisement of a company and the like, and each information site generally guarantees the timeliness of the information as much as possible, the information on the Web site is dynamic and updated frequently, which is guaranteed by the information provider;
interactivity of the Web: the interactivity of Web is firstly shown on a hyperlink of the Web, the browsing sequence and the destination of a user are completely determined by the user, in addition, dynamic information can be obtained from a server side through a FORM, the user can submit a request to the server by filling the FORM, and the server can return corresponding information according to the request of the user;
at present, the workflow construction of the stage is mostly at the client, and the service extension constructed by the workflow is more so, but the service extension constructed by the workflow of the client is not flexible to release and deploy, and meanwhile, the popularization cost is high; the system is not easy to propagate because of the limitation of the platform;
in view of the above, to overcome the above drawbacks, providing a method and a system for expanding a Web service built based on a workflow becomes an urgent problem to be solved in the art.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a method and a system for Web service expansion built based on workflow, which can accurately and quickly asynchronously call the workflow, realize data and functional resource sharing, have low popularization cost and are easy to propagate.
In order to solve the technical problems, the technical scheme of the invention is as follows: a Web service expansion method based on workflow construction is different in that the method comprises the following steps:
step A: creating a class library project, adding a function code according to a function required to be realized by the process, and compiling to generate a shared dynamic link library file;
and B: registering a shared dynamic link library file, and a functional module and a function thereof on a Web node of a functional warehouse;
and C: building a workflow on a visual interface;
step D: deploying the workflow to a service manager, specifically comprising the steps of: if the deployment is distributed, copying the workflow file to a service manager of a server to be deployed, and adding a function library flow template in a function warehouse; if the deployment is native, the workflow can be automatically registered in a function warehouse of the service manager without any operation;
step E: the method comprises the following steps that the Web end asynchronously calls a workflow and returns a result to the Web end, and the method specifically comprises the following steps: the Web terminal accesses the address of the server, the port number of the service and the flow number of the workflow through the ajax technology to asynchronously call the workflow, and the workflow returns to the Web terminal as a result in the form of a callback function.
According to the scheme, after registering the shared dynamic link library file, the functional module and the function thereof in the step B, whether the function which is successfully registered can operate correctly needs to be tested; if the registered function can not be correctly operated after the test, adding a breakpoint at a proper position of the code; if it can work correctly, the workflow is set up.
According to the scheme, the step C specifically comprises the following steps:
step C1: creating a flow template on a system flow directory of a workflow editor, and inputting corresponding parameters to create a new functional flow;
step C2: setting process parameter information necessary for creating a flow;
step C3: adding workflow process start and stop nodes and workflow function nodes, and setting a sequential migration relationship between the nodes;
step C4: setting a return value parameter and a parameter source type of a workflow function node;
step C5: debugging and running the workflow.
A Web service expansion system built based on workflow is different in that the system comprises:
the dynamic link library file generation layer is used for creating class library engineering, adding functional codes according to functions required to be realized by the flow and compiling to generate a shared dynamic link library file;
the function registration layer is used for registering the shared dynamic link library file, and the functional module and the function thereof;
the function test layer is used for testing whether the function which is successfully registered can correctly run or not so as to ensure the correctness of the function;
the workflow building layer is used for building a workflow on the visual interface;
the workflow distribution layer is used for deploying the workflow to the service manager, copying the workflow file to the service manager of the server to be deployed if the workflow is distributed, and adding a function library flow template in the function warehouse; if the deployment is native, the workflow can be automatically registered in a function warehouse of the service manager without any operation;
and the Web service extension layer is used for asynchronously calling the workflow by the Web end and returning the result to the Web end, the Web end asynchronously calls the workflow by accessing the address of the server, the port number of the service and the flow number of the workflow through the ajax technology, and the workflow returns to the Web end as the result in the form of a callback function.
According to the scheme, the workflow building layer comprises:
the template creating unit is used for setting corresponding parameters on the system process catalog to create a new functional process;
a process parameter setting unit for setting process parameter information necessary for creating a flow;
a node adding unit for adding a workflow starting and ending node and a workflow function node and setting a sequential migration relationship between the nodes;
the function parameter setting unit is used for setting a return value parameter and a parameter source type of the workflow function node;
and
and the workflow running unit is used for debugging and running the workflow.
By the scheme, the service expansion method and the service expansion system break through the barrier that the traditional technology can only synchronously call the workflow, support the remote asynchronous call of the workflow, better realize the sharing of various data and functional resources, and flexibly release and deploy services, thereby well solving the problem of low working efficiency caused by that the workflow can only be synchronously called under mass data; and the popularization cost is low, the method is not limited by any limit, and the method is easy to spread.
Drawings
FIG. 1 is a schematic flow chart of a workflow-based Web service expansion method according to the present invention;
FIG. 2 is a schematic flow diagram of "building a workflow" in a workflow-based Web service expansion method according to the present invention;
FIG. 3 is a schematic flow diagram of "issuing workflow" in a workflow-based Web service extension method according to the present invention;
FIG. 4 is a schematic flow diagram of "call workflow" in a workflow-based Web service extension method according to the present invention;
FIG. 5 is a schematic structural diagram of a workflow-based Web service expansion system according to the present invention;
wherein: the system comprises a 1-dynamic link library file generation layer, a 2-function registration layer, a 3-function test layer, a 4-workflow construction layer (401-template creation unit, 402-process parameter setting unit, 403-node addition unit, 404-function parameter setting unit, 405-workflow operation unit), a 5-workflow distribution layer and a 6-Web service extension layer.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Many aspects of the invention are better understood with reference to the following drawings. The components in the drawings are not necessarily to scale. Instead, emphasis is placed upon clearly illustrating the components of the present invention. Moreover, in the several views of the drawings, like reference numerals designate corresponding parts.
The word "exemplary" or "illustrative" as used herein means serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" or "illustrative" is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described below are exemplary embodiments provided to enable persons skilled in the art to make and use the examples of the disclosure and are not intended to limit the scope of the disclosure, which is defined by the claims. In other instances, well-known features and methods are described in detail so as not to obscure the invention. For purposes of the description herein, the terms "upper," "lower," "left," "right," "front," "rear," "vertical," "horizontal," and derivatives thereof shall relate to the invention as oriented in fig. 1. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification are simply exemplary embodiments of the inventive concepts defined in the appended claims. Hence, specific dimensions and other physical characteristics relating to the embodiments disclosed herein are not to be considered as limiting, unless the claims expressly state otherwise.
Referring to fig. 1 to 4, the present invention is a method for expanding a Web service built based on a workflow, including the following steps:
step A: creating class library engineering, adding function codes according to functions required to be realized by the process, and compiling to generate a shared dynamic link library file, namely a shared DLL file;
and B: registering a shared dynamic link library file, and a functional module and a function thereof on a Web node of a functional warehouse; testing whether the function can operate correctly after the registration function is completed; if the registered function can not be correctly operated after the test, adding a breakpoint at a proper position of the code; otherwise, if the operation can be correctly carried out, a workflow is set up;
and C: building a workflow on a visual interface; as shown in fig. 2, the method comprises the following specific steps:
step C1: creating a flow template on a system flow directory of a workflow editor, and inputting corresponding parameters to create a new functional flow;
step C2: setting process parameter information necessary for creating a flow;
step C3: adding a workflow starting and ending node and a GIS workflow function node (also called an intermediate node), and setting a sequential migration relationship between the nodes; the flow starting and ending nodes are used for restricting the entry point and the exit point of the workflow execution; the intermediate node is set up by the function to be realized;
step C4: setting a return value parameter and a parameter source type of a workflow function node;
step C5: debugging and running the workflow.
Step D: deploying a workflow onto a service manager; as shown in fig. 3, if the deployment is distributed, the workflow file is copied to the service manager of the server to be deployed, and a function library flow template is added to the function repository; if the deployment is native, the workflow can be automatically registered in a function warehouse of the service manager without any operation;
step E: as shown in fig. 4, the Web side accesses the address of the server, the port number of the service, and the flow number of the workflow through ajax technology to asynchronously invoke the workflow, and the workflow returns to the Web side in the form of a callback function as a result.
Correspondingly, the invention also provides a Web service expansion system built based on the workflow, as shown in fig. 5, the difference is that: the system comprises a dynamic link library file generation layer 1, a function registration layer 2, a function test layer 3, a workflow construction layer 4, a workflow distribution layer 5 and a Web service expansion layer 6; the dynamic link library file generation layer 1 is used for creating class library engineering, adding functional codes according to functions required to be realized by a flow and compiling to generate a shared DLL file; the function registration layer 2 is used for registering the shared dynamic link library file, and registering the functions required to be realized by the process through the functional modules and the functions thereof; the function testing layer 3 is used for testing in advance after the function registration is successful, and testing whether the function which is successfully registered can run correctly or not so as to ensure the correctness of the function; the workflow building layer 4 is used for building a workflow model on a visual interface, and comprises a template building unit 401, a process parameter setting unit 402, a node adding unit 403, a function parameter setting unit 404 and a workflow running unit 405; the template creating unit 401 is configured to set corresponding parameters on the device process directory to create a new functional process; the process parameter setting unit 402 is configured to set process parameter information necessary for creating a process; the node adding unit 403 is configured to add workflow starting and ending nodes, that is, a start node, an end node, and workflow function nodes, and set a sequential migration relationship between the nodes; the function parameter setting unit 404 is configured to set a return value parameter and a parameter source type of a workflow function node; the workflow running unit 405 is used for debugging and running a workflow; the workflow distribution layer 5 is used for deploying the workflow to the server service; and the Web service expansion layer 6 is used for the browser to call the background workflow through the ajax technology and return the result to the Web end.
In order to make the method and system of the present invention better understood, a specific implementation of the Web service extension method built based on workflow of the present invention is further described by taking a functional Web service extension for implementing two digital additions as an example.
Step A:
the dynamic link library file generation layer 1 in the Web service expansion system built based on the workflow is used for newly building C # class library engineering and is named as Addition;
after the Class library engineering is established, adding codes in a Class1 to realize the function of adding two numbers;
compiling engineering, namely, calling the generated addition.dll shared file as a dynamic link library file, and copying the dynamic link library file to a Program \ MapGIS.Server.WorkFlow \ function library \ GIS \ web \ dll folder of a MapGIS installation directory;
and B:
a function registration layer 2 in the Web service expansion system built based on the workflow registers the dynamic link library file generated in the step A on a Web node of a function warehouse, registers a function module and a function of the dynamic link library file, and is used for building the workflow;
firstly, opening a workflow editor, registering a file addition.dll on a Web node of a function warehouse, registering a function module on an added DLL shared file, selecting an addition.Class1 class, and finally registering an added 'addDNA' function on the added addition.Class1 class;
after the function registration is successful, a function test layer 3 in the Web service expansion system built based on the workflow needs to be tested in advance to ensure the correctness of the function; setting the value of the parameter a of the successfully registered addNum function to be 1.2 and the value of the parameter b to be 1.3, then testing the function to obtain a test result, wherein the test result of the addition function is correct, and the test is finished;
and C:
the workflow construction layer 4 in the Web service expansion device constructed based on the workflow is used for creating a workflow model on a visual interface, and the specific steps are as follows:
step C1: the template creating unit 401 in the workflow building layer 4 is used for creating a new flow on a system flow directory panel of the workflow editor and inputting corresponding parameters to create a new functional flow;
step C2: the process parameter setting unit 402 of the workflow building layer 4 creates process parameters necessary for the process, the required process parameters are the same as those included In the add method, the parameter types are also the same, the parameters which need to be input by a user are called input type parameters In the workflow editor, the parameter direction is In, a parameter c is added here, the parameter c is used for receiving the return value of the add method, the parameter is an output type parameter, and the parameter direction is Out;
step C3: the node adding unit 403 in the workflow building layer 4 adds a start node, an end node, a function node and a sequential migration relationship among the nodes of the flow;
step C4: a function parameter setting unit 404 in the workflow building layer 4 sets a return value of an addNum function process node as a parameter c, sets a parameter source type of the parameter a as "Processpara", sets a process parameter as "parameter 1" (corresponding to the process parameter), sets a parameter source type of the parameter b as "Processpara", and sets a process parameter as "parameter 2" (corresponding to the process parameter); if there is a return value, setting a return value parameter corresponding to the process parameter;
step C5: thus, the addition workflow is already built; then, a workflow operation unit 405 in the workflow building layer 4 stores a workflow template and operates the flow, a parameter 1 is set to be 1.2, a parameter 2 is set to be 1.3, and an operation result is 2.5; by the tracking debugging of the step, the workflow can be ensured to operate correctly;
step D:
the workflow distribution layer 5 in the Web service expansion system built based on the workflow can realize the distribution of the workflow on the basis of ensuring the correct operation of the workflow; if distributed deployment is needed, copying the workflow file to a service manager of a server needing deployment, and adding a function library flow template in a function warehouse; if the deployment is native, the workflow can be automatically registered in a function warehouse of the service manager without any operation;
step E:
after the workflow is successfully issued, the Web end can asynchronously and efficiently call the workflow, as shown in fig. 4, a Web service extension layer 6 in the Web service extension device built based on the workflow calls the workflow at the Web end through ajax technology;
and after the workflow is executed, the server returns the result to the visual interface of the Web end in the json format.
The technical scheme realizes the service expansion of the Web-end workflow and solves the technical problem of the invention; based on the solution, the barrier that the workflow can only be called synchronously in the traditional technology is broken through, the Web end can accurately and quickly call the workflow asynchronously, the sharing of various data and functional resources can be better realized, and the service can be flexibly released and deployed, so that the problem of low working efficiency caused by that the workflow can only be called synchronously under mass data is well solved; and the popularization cost is low, the method is not limited by any limit, and the method is easy to spread.
The foregoing is a more detailed description of the present invention that is presented in conjunction with specific embodiments, and the practice of the invention is not to be considered limited to those descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (5)
1. A Web service expansion method built based on workflow is characterized by comprising the following steps:
step A: creating a class library project, adding a function code according to a function required to be realized by the process, and compiling to generate a shared dynamic link library file;
and B: registering a shared dynamic link library file, and a functional module and a function thereof on a Web node of a functional warehouse;
and C: building a workflow on a visual interface;
step D: deploying the workflow to a service manager, specifically comprising the steps of: if the deployment is distributed, copying the workflow file to a service manager of a server to be deployed, and adding a function library flow template in a function warehouse; if the deployment is native, the workflow can be automatically registered in a function warehouse of the service manager without any operation;
step E: the method comprises the following steps that the Web end asynchronously calls a workflow and returns a result to the Web end, and the method specifically comprises the following steps: the Web terminal accesses the address of the server, the port number of the service and the flow number of the workflow through the ajax technology to asynchronously call the workflow, and the workflow returns to the Web terminal as a result in the form of a callback function.
2. The workflow-based Web service expansion method according to claim 1, wherein: in the step B, after registering the shared dynamic link library file and the functional modules and functions thereof, whether the function which is successfully registered can operate correctly needs to be tested; if the registered function can not be correctly operated after the test, adding a breakpoint at a proper position of the code; if it can work correctly, the workflow is set up.
3. The workflow-based Web service expansion method according to claim 1, wherein: the step C is specifically as follows:
step C1: creating a flow template on a system flow directory of a workflow editor, and inputting corresponding parameters to create a new functional flow;
step C2: setting process parameter information necessary for creating a flow;
step C3: adding workflow process start and stop nodes and workflow function nodes, and setting a sequential migration relationship between the nodes;
step C4: setting a return value parameter and a parameter source type of a workflow function node;
step C5: debugging and running the workflow.
4. A Web service expansion system built based on workflow is characterized by comprising the following components:
the dynamic link library file generation layer is used for creating class library engineering, adding functional codes according to functions required to be realized by the flow and compiling to generate a shared dynamic link library file;
the function registration layer is used for registering the shared dynamic link library file, and the functional module and the function thereof;
the function test layer is used for testing whether the function which is successfully registered can correctly run or not so as to ensure the correctness of the function;
the workflow building layer is used for building a workflow on the visual interface;
the workflow distribution layer is used for deploying the workflow to the service manager, copying the workflow file to the service manager of the server to be deployed if the workflow is distributed, and adding a function library flow template in the function warehouse; if the deployment is native, the workflow can be automatically registered in a function warehouse of the service manager without any operation;
and the Web service extension layer is used for asynchronously calling the workflow by the Web end and returning the result to the Web end, the Web end asynchronously calls the workflow by accessing the address of the server, the port number of the service and the flow number of the workflow through the ajax technology, and the workflow returns to the Web end as the result in the form of a callback function.
5. The workflow-based Web service expansion system according to claim 4, wherein: the workflow building layer comprises:
the template creating unit is used for setting corresponding parameters on the system process catalog to create a new functional process;
a process parameter setting unit for setting process parameter information necessary for creating a flow;
a node adding unit for adding a workflow starting and ending node and a workflow function node and setting a sequential migration relationship between the nodes;
the function parameter setting unit is used for setting a return value parameter and a parameter source type of the workflow function node;
and
and the workflow running unit is used for debugging and running the workflow.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810726354.2A CN109062548B (en) | 2018-07-04 | 2018-07-04 | Web service expansion method and system based on workflow construction |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810726354.2A CN109062548B (en) | 2018-07-04 | 2018-07-04 | Web service expansion method and system based on workflow construction |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109062548A CN109062548A (en) | 2018-12-21 |
| CN109062548B true CN109062548B (en) | 2020-06-30 |
Family
ID=64819114
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810726354.2A Active CN109062548B (en) | 2018-07-04 | 2018-07-04 | Web service expansion method and system based on workflow construction |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109062548B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109857380B (en) * | 2019-01-25 | 2022-07-05 | 中国银行股份有限公司 | Workflow file compiling method and device |
| CN110969414A (en) * | 2019-11-27 | 2020-04-07 | 中国地质大学（武汉） | Cross-platform workflow implementation method and system based on Java |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106547519A (en) * | 2015-09-16 | 2017-03-29 | 中国移动通信集团公司 | Information processing method and system |
| CN106598584A (en) * | 2016-12-08 | 2017-04-26 | 广州华多网络科技有限公司 | Resource file processing method, apparatus and system |
| CN106790455A (en) * | 2016-12-08 | 2017-05-31 | 中国科学院软件研究所 | A kind of distributed cloud management system and method based on mixed mode |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005106666A1 (en) * | 2004-04-29 | 2005-11-10 | International Business Machines Corporation | A system and method for modeling and dynamically deploying services into a distributed networking architecture |
-
2018
- 2018-07-04 CN CN201810726354.2A patent/CN109062548B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106547519A (en) * | 2015-09-16 | 2017-03-29 | 中国移动通信集团公司 | Information processing method and system |
| CN106598584A (en) * | 2016-12-08 | 2017-04-26 | 广州华多网络科技有限公司 | Resource file processing method, apparatus and system |
| CN106790455A (en) * | 2016-12-08 | 2017-05-31 | 中国科学院软件研究所 | A kind of distributed cloud management system and method based on mixed mode |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109062548A (en) | 2018-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10956013B2 (en) | User interface for automated flows within a cloud based developmental platform | |
| CN101699393B (en) | Network-facing intelligent software interface dynamic generation method | |
| US10101972B1 (en) | Data modelling and flow engine for building automated flows within a cloud based developmental platform | |
| CN105046408A (en) | Configurable workflow realization method and system | |
| CN111241454A (en) | Method, system and device for generating webpage code | |
| EP3454203A1 (en) | Data modelling and flow engine for building automated flows within a cloud based developmental platform | |
| CN111068328A (en) | Game advertisement configuration table generation method, terminal device and medium | |
| CN103646023A (en) | Page and control increasing method based on WEB | |
| CN109062548B (en) | Web service expansion method and system based on workflow construction | |
| CN115454417A (en) | Web front-end project building method | |
| CN113626128B (en) | Audio-visual media micro-service third-party module access method, system and electronic equipment | |
| Amendola et al. | Adapting CRM systems for mobile platforms: An MDA perspective | |
| CN106656552A (en) | Extension method, system and electronic device for data platform system | |
| Engel et al. | Formal pattern specifications to facilitate semi-automated user interface generation | |
| CN104461893A (en) | Data processing method and data processing device | |
| Fujima | Building a meme media platform with a JavaScript MVC framework and HTML5 | |
| CN112799742B (en) | Machine learning practical training system and method based on micro-service | |
| US9477492B2 (en) | Deploying multi-channel or device agnostic applications | |
| Dumez et al. | Model-driven engineering of composite web services using uml-s | |
| CN113515263A (en) | Industrial APP mechanism model deployment method, device, equipment and readable storage medium | |
| Alves | Getting Started with Oracle Event Processing 11g | |
| Zhang | A practical approach to developing a web-based geospatial workflow composition and execution system | |
| Silingas et al. | Towards uml-intensive framework for model-driven development | |
| Adeniji Kehinde et al. | Web Application Development Using Visual Basic .NET and Microsoft SQL for Mobile and PC Devices | |
| Hautaviita | Developing a web application on the MEVN stack: the architecture of a full-stack JavaScript application |
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 |