CN118312296B - Visual multi-machine scheduling system based on workflow - Google Patents
Visual multi-machine scheduling system based on workflow Download PDFInfo
- Publication number
- CN118312296B CN118312296B CN202410740833.5A CN202410740833A CN118312296B CN 118312296 B CN118312296 B CN 118312296B CN 202410740833 A CN202410740833 A CN 202410740833A CN 118312296 B CN118312296 B CN 118312296B
- Authority
- CN
- China
- Prior art keywords
- workflow
- visual
- equipment
- service
- function
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/904—Browsing; Visualisation therefor
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a visual multi-machine scheduling system based on workflow, which comprises: WEB pages, process background, functional agents and devices; and the user initiates tasks through the WEB page, the process background service receives and processes the tasks, and then the function interface of the equipment is called through the function agent, so that the execution of the tasks is finally realized. The whole system has high cohesiveness, and each functional module has definite responsibility and is easy to maintain and expand. Meanwhile, the system fully considers the constraint of the implementation technology, and ensures the reliability and convenience of the system. The technology of the invention has obvious advantages in the aspects of usability, flexibility, expandability, convenience, reliability, stability and the like, and provides a solution which is efficient, flexible, stable and easy to use for the field of multi-machine scheduling.
Description
Technical Field
The invention relates to the technical field of multi-machine scheduling systems, in particular to a visual multi-machine scheduling system based on workflow.
Background
With the continuous development of technology, the functions of devices and systems are more and more complex, and a multi-machine scheduling system capable of rapidly and efficiently scheduling the functions of devices is needed. Multi-machine scheduling systems typically involve the co-operation of multiple machines or devices, with complex system architecture and flow. This results in users facing higher learning curves in designing and configuring scheduling tasks, and it is difficult to quickly understand and master the operation and configuration of the system. Existing multi-machine scheduling systems are generally designed for specific application scenarios and requirements, and have limited scalability. As business requirements change and technology evolves, it may be difficult for the system to accommodate new application scenarios and requirements. Failure of any one node or device in a multi-machine scheduling system may affect the stable operation of the overall system. The existing system may have defects in fault detection, prevention and recovery, and high reliability and stability cannot be ensured.
Disclosure of Invention
Aiming at the problems, the invention aims to provide a visual multi-machine scheduling system based on workflow, which improves performances of the system in aspects of usability, convenience, flexibility, expandability, reliability, stability and the like by solving the defects of the prior art.
In order to achieve the above purpose, the present invention provides the following technical solutions:
a workflow-based visual multi-machine scheduling system, the system comprising:
the WEB page is a main interface for the interaction between the user and the system, and the user performs visual arrangement of equipment functions through the WEB page and monitors the execution state of the process; the WEB page provides an intuitive operation interface, so that a user can quickly iterate out new equipment services combined by equipment functions under the condition of writing no or few codes;
The process background is a core part of the system and is used for managing and scheduling the whole workflow, receiving visual arrangement instructions of users and converting the visual arrangement instructions into actual task scheduling, and the process background also needs to process various events and anomalies in the process of executing the process so as to ensure the reliability and stability of the process;
The function agent is a middleware and is used for realizing the agent of the function of the equipment, and the function agent abstracts the complex equipment operation through a service class interface and a tool class interface, so that a user can visually arrange the equipment on a WEB page in a simple and visual mode; the development difficulty of the system is greatly reduced, and the maintainability and the expandability of the system are improved;
The equipment is an entity for actually executing tasks, and is abstracted into reusable functional units through a functional agent, wherein the functional units are freely combined on a WEB page so as to meet different service requirements; the system realizes remote control and task scheduling of the equipment by calling the function interface of the equipment.
As a further technical scheme of the invention, the construction method of the business process background service comprises the following steps:
s101, starting; the starting point of the whole business process, from which the operation of the process background service starts;
S102, ensuring that Springboot engineering can be started normally; ensuring normal operation;
S103, introducing a maven dependence of activiti; maven is activiti is an open source workflow engine that provides a complete set of business process management solutions;
S104, restarting the project; verifying activiti whether the workflow engine is correctly integrated into Springboot engineering, and ensuring normal starting and operation of a process background service;
s105, checking whether a database query library table structure is generated;
After the integration of the Activiti workflow engine and the normal start of the process background service are completed, whether the table structure in the database is generated or not needs to be checked, the table structure in the database including the table name, the field and the data type is checked to ensure that the table structure is matched with the requirements of the Activiti workflow engine, and whether the database is used for checking whether the table structure is generated or not is checked to ensure that the process background service correctly processes data and interacts with other systems when running.
As a further technical scheme of the invention, the construction method for the visual arrangement of the business process comprises the following steps:
s201: starting; the operation of visualizing the orchestration starts here from the beginning of the whole business process.
S202: starting a VUE item; before starting the visualization arrangement, the VUE item needs to be started. VUE is a front end framework for building user interfaces and single page applications.
S203: introducing a flow arranging component; tools or components for process design and orchestration are introduced, which typically provide graphical interfaces so that users can intuitively create and edit business processes by dragging, wiring, etc.
S204: writing a component support service; after introducing the flow orchestration component, a component support service needs to be written. This service is to support the normal operation of the flow orchestration component and to provide the necessary functionality. It typically involves back-end programming and development of API interfaces.
S205: restarting the VUE item; after the component support service is written, the VUE item needs to be restarted to validate the new support service. Restarting projects is a very common operation during development to ensure that all changes have been properly loaded and applied;
S206: logging and verifying; after restarting the VUE item, login verification is required. This is to ensure that only authorized users can access and edit the business process. Login authentication generally involves the handling of a user name, password, and authentication mechanism;
s207: and (5) ending. And finishing the construction of the visual arrangement.
As a further technical scheme of the invention, the construction method for the convenient intervention of the business process comprises the following steps:
s301: starting; this is the starting point of the entire business process from which the operation of the easy intervention begins.
S302: writing a functional proxy class; before convenient intervention can begin, functional proxy classes need to be written. This class is a tool for implementing easy intervention functions that provides various operations and commands to intervene and manage tasks.
S303: an orchestration function; after the function proxy class is written, the functions need to be orchestrated. This step involves combining the different functions and operations to form a complete workflow for efficient intervention and management of tasks.
S304: saving the function and calling; after the functions are programmed, the functions need to be saved and called. This includes deploying functional proxy classes into the system and ensuring that they can be invoked and executed correctly.
S305: performing pause resume cancellation on the task; it allows the user to pause, resume and cancel the task being performed. These operations allow the user to flexibly adjust the execution flow of tasks according to actual situations so as to meet different requirements and conditions.
S306: and (5) ending. And (5) ending the convenient intervention.
The terms involved in the present invention are explained as follows:
The workflow: a series of interrelated and automated tasks and activities to achieve a particular business objective or process. It is commonly used to describe automation and standardization of business processes to improve efficiency and quality.
And (3) visualization: the process of converting data, information and knowledge into visual form for more intuitive presentation and interpretation. The visualizations may be presented by graphics, charts, images, and other visual elements.
A multi-machine scheduling system: a computer system for managing and optimizing task scheduling and resource allocation for a plurality of computers or devices. It may allocate tasks according to different priorities, resource availability and constraint conditions to improve overall performance and efficiency.
The aim of the arrangement is to ensure that each module, component or service is executed according to specific rules and conditions so as to achieve the aim of completing the whole task by combining and scheduling different modules, components or services to realize the preset logic flow or task execution sequence.
Service class interface: and the application program interface is used for defining the communication specification between the client and the server and realizing data exchange and function call. It provides a standardized way to enable different systems and applications to interact and integrate through these interfaces.
Tool class interface: a special type of interface provides a common set of methods or functions for a certain tool class or framework so that other classes or modules can use the functions of the tool class or framework. The tool class interface typically defines some common tool methods, such as string processing, date processing, encryption and decryption, etc. By implementing a tool class interface, other classes or modules may invoke these tool methods, thereby simplifying code writing and reducing duplication of work.
WEB page: typically referred to as a Web page on the internet, which is part of a Web application. Web pages use hypertext markup language (HTML) to define their content and structure and CSS to define their style. Web pages typically contain text, images, video, audio, and other media content that a user can view and interact through a Web browser.
Vue is a progressive JavaScript framework for building user interfaces. The method adopts a componentization development mode, and each component has own HTML, CSS and JavaScript. The Vue also provides functions such as instruction and data binding, so that a developer can operate DOM and binding data more conveniently. The design concept of Vue is that the Vue is applied layer by layer from bottom to top, is easy to be put on hand, and is convenient to integrate with a third party library or an existing project.
Spring Boot is a framework for creating independent, production-level Spring applications. It simplifies the configuration and deployment of Spring applications and provides many out-of-box functions and plug-ins
Spring: is an open source Java application framework for building enterprise-level applications. It provides a lightweight development environment that allows developers to more easily build extensible, flexible, and maintainable applications. Spring frameworks cover various aspects such as dependency injection, AOP, web development, data access, messaging, and the like.
High cohesiveness refers to the close correlation and high degree of functional correlation between elements (e.g., classes, methods, etc.) within a module or assembly. High cohesiveness means that elements within a module or component together perform a particular function and are highly interdependent with each other. A highly cohesive module or assembly is easier to understand, maintain and expand.
Activiti an open source enterprise level workflow engine for building and executing various complex workflows.
Functional proxy class: a design model that aims to encapsulate some functions in proxy classes to simplify access and use of the original object. A functional proxy class typically represents another object and provides additional functionality, which may be enhancements, modifications, or encapsulation to the original object. By using a function proxy class, access to the original object can be better managed and controlled, while the functionality of the object can also be easily extended and modified. This design pattern is very common in software design and can help improve maintainability and extensibility of code.
Compared with the prior art, the invention has the beneficial effects that:
Ease of use: by abstracting and packaging the technical details of the bottom layer, the technology of the invention enables non-professional personnel to easily carry out multi-machine scheduling operation, thereby reducing the technical threshold and expanding the application range of the system.
Flexibility and scalability: the visual multi-machine scheduling system based on the workflow utilizes a service class interface, a tool class interface and a WEB page to realize the proxy and visual arrangement of the equipment functions, thereby being capable of quickly iterating out new equipment services combined by the equipment functions. This flexibility enables the system to quickly adapt to changing business needs.
Convenience, reliability and stability: the system is particularly focused on the balance of convenience and reliability in design, and can provide stable performance while meeting various functional requirements. This allows for greater availability and maintainability of the inventive technique in a complex multi-machine environment.
In summary, compared with the prior art, the technology of the invention has obvious advantages in the aspects of usability, flexibility, expandability, convenience, reliability, stability and the like, and provides an efficient, flexible, stable and easy-to-use solution for the field of multi-machine scheduling.
Drawings
Fig. 1 is a flowchart of a method for setting up a business process background service in a visual multi-machine scheduling system based on a workflow.
Fig. 2 is a flowchart of a construction method for visual arrangement of service flow of a visual multi-machine scheduling system based on workflow.
Fig. 3 is a flowchart of a method for constructing a convenient intervention of a business process in a visual multi-machine scheduling system based on a workflow.
Fig. 4 is a system block diagram of a workflow-based visual multi-machine scheduling system.
Detailed Description
The technical scheme of the patent is further described in detail below with reference to the specific embodiments.
Referring to fig. 4, as an embodiment provided by the present invention, a workflow-based visual multi-machine scheduling system includes:
S401: the WEB page is a main interface for the interaction between the user and the system, and the user performs visual arrangement of equipment functions through the WEB page and monitors the execution state of the process; the WEB page provides an intuitive operation interface, so that a user can quickly iterate out new equipment services combined by equipment functions under the condition of writing no or few codes;
S402: the process background is a core part of the system and is used for managing and scheduling the whole workflow, receiving visual arrangement instructions of users and converting the visual arrangement instructions into actual task scheduling, and the process background also needs to process various events and anomalies in the process of executing the process so as to ensure the reliability and stability of the process;
S403: the function agent is a middleware and is used for realizing the agent of the function of the equipment, and the function agent abstracts the complex equipment operation through a service class interface and a tool class interface, so that a user can visually arrange the equipment on a WEB page in a simple and visual mode; the development difficulty of the system is greatly reduced, and the maintainability and the expandability of the system are improved;
S404: the equipment is an entity for actually executing tasks, and is abstracted into reusable functional units through a functional agent, wherein the functional units are freely combined on a WEB page so as to meet different service requirements; the system realizes remote control and task scheduling of the equipment by calling the function interface of the equipment.
The system completes the proxy of the equipment function through the service class interface, the tool class interface and the WEB page, and performs visual arrangement on the equipment function so as to realize the rapid iteration of new equipment service combined by the equipment function under the condition of writing no code or writing few codes.
And the user initiates tasks through the WEB page, the process background service receives and processes the tasks, and then the function interface of the equipment is called through the function agent, so that the execution of the tasks is finally realized. The whole system has high cohesiveness, and each functional module has definite responsibility and is easy to maintain and expand. Meanwhile, the system fully considers the constraint of the implementation technology, and ensures the reliability and convenience of the system.
Referring to fig. 1, in this embodiment, a method for setting up a business process background service in a workflow-based visual multi-machine scheduling system includes the following steps:
s101, starting; the starting point of the whole business process, from which the operation of the process background service starts;
S102, ensuring that Springboot engineering can be started normally; ensuring normal operation;
S103, introducing a maven dependence of activiti; maven is activiti is an open source workflow engine that provides a complete set of business process management solutions;
S104, restarting the project; verifying activiti whether the workflow engine is correctly integrated into Springboot engineering, and ensuring normal starting and operation of a process background service;
s105, checking whether a database query library table structure is generated;
After the integration of the Activiti workflow engine and the normal start of the process background service are completed, whether the table structure in the database is generated or not needs to be checked, the table structure in the database including the table name, the field and the data type is checked to ensure that the table structure is matched with the requirements of the Activiti workflow engine, and whether the database is used for checking whether the table structure is generated or not is checked to ensure that the process background service correctly processes data and interacts with other systems when running.
Referring to fig. 2, in this embodiment, a method for constructing a business process visualization layout in a workflow-based visualization multi-machine scheduling system includes the following steps:
s201: starting; the operation of visualizing the orchestration starts here from the beginning of the whole business process.
S202: starting a VUE item; before starting the visualization arrangement, the VUE item needs to be started. VUE is a front end framework for building user interfaces and single page applications.
S203: introducing a flow arranging component; tools or components for process design and orchestration are introduced, which typically provide graphical interfaces so that users can intuitively create and edit business processes by dragging, wiring, etc.
S204: writing a component support service; after introducing the flow orchestration component, a component support service needs to be written. This service is to support the normal operation of the flow orchestration component and to provide the necessary functionality. It typically involves back-end programming and development of API interfaces.
S205: restarting the VUE item; after the component support service is written, the VUE item needs to be restarted to validate the new support service. Restarting projects is a very common operation during development to ensure that all changes have been properly loaded and applied;
S206: logging and verifying; after restarting the VUE item, login verification is required. This is to ensure that only authorized users can access and edit the business process. Login authentication generally involves the handling of a user name, password, and authentication mechanism;
s207: and (5) ending. And finishing the construction of the visual arrangement.
Referring to fig. 3, in this embodiment, a method for constructing a convenient intervention of a business process in a visual multi-machine scheduling system based on a workflow includes the following steps:
s301: starting; this is the starting point of the entire business process from which the operation of the easy intervention begins.
S302: writing a functional proxy class; before convenient intervention can begin, functional proxy classes need to be written. This class is a tool for implementing easy intervention functions that provides various operations and commands to intervene and manage tasks.
S303: an orchestration function; after the function proxy class is written, the functions need to be orchestrated. This step involves combining the different functions and operations to form a complete workflow for efficient intervention and management of tasks.
S304: saving the function and calling; after the functions are programmed, the functions need to be saved and called. This includes deploying functional proxy classes into the system and ensuring that they can be invoked and executed correctly.
S305: performing pause resume cancellation on the task; it allows the user to pause, resume and cancel the task being performed. These operations allow the user to flexibly adjust the execution flow of tasks according to actual situations so as to meet different requirements and conditions.
S306: and (5) ending. And (5) ending the convenient intervention.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.
Furthermore, it should be understood that although the present disclosure describes embodiments, not every embodiment is provided with a separate embodiment, and that this description is provided for clarity only, and that the disclosure is not limited to the embodiments described in detail below, and that the embodiments described in the examples may be combined as appropriate to form other embodiments that will be apparent to those skilled in the art.
Claims (2)
1. A workflow-based visual multi-machine scheduling system, the system comprising:
the WEB page is used for visually arranging the functions of the equipment by a user, and monitoring the execution state of the process; the WEB page provides an intuitive operation interface, so that a user can quickly iterate out new equipment services combined by equipment functions under the condition of writing no or few codes;
The process background is used for managing and scheduling the whole workflow, receiving the visual arrangement instruction of the user and converting the visual arrangement instruction into actual task scheduling, and is also required to process various events and anomalies in the process of executing the process, so as to ensure the reliability and stability of the process;
The function agent is used for realizing the agent of the equipment function, and abstracting the complex equipment operation through the service class interface and the tool class interface, so that the user can carry out visual arrangement on the WEB page in a simple and visual mode;
The equipment is abstracted into reusable functional units through the functional agent, and the functional units are freely combined on the WEB page so as to meet different service requirements; the system realizes remote control and task scheduling of the equipment by calling a functional interface of the equipment;
The construction method of the business process background service in the visual multi-machine scheduling system comprises the following steps:
S101, starting;
s102, ensuring that Springboot engineering can be started normally;
S103, introducing a maven dependence of activiti; maven is activiti is an open source workflow engine that provides a complete set of business process management solutions;
S104, restarting the project; verifying activiti whether the workflow engine is correctly integrated into Springboot engineering, and ensuring normal starting and operation of a process background service;
s105, checking whether a database query library table structure is generated;
After integration of Activiti workflow engines and normal starting of flow background services are completed, checking whether a table structure in a database is generated or not, checking the table structure in the database, including table names, fields and data types, to ensure that the table structures are matched with requirements of an Activiti workflow engine, checking whether the table structure of the database is generated or not, and ensuring that the flow background services correctly process data and interact with other systems when running;
the construction method for the convenient intervention of the service flow in the visual multi-machine scheduling system comprises the following steps:
s301: starting;
S302: writing a functional proxy class; writing a functional agent class before starting convenient intervention; this class is a tool for implementing a convenient intervention function that provides various operations and commands to intervene and manage tasks;
s303: an orchestration function; after the function proxy class is written, the functions need to be arranged; combining different functions and operations to form a complete workflow for effective intervention and management of tasks;
s304: saving the function and calling; after the functions are programmed, the functions need to be saved and called, which involves deploying the function proxy class into the system and ensuring that they can be correctly called and executed;
s305: suspending, restoring and canceling the task; allowing a user to pause, resume and cancel the task being executed;
S306: and (5) ending the convenient intervention.
2. The workflow-based visual multi-machine scheduling system according to claim 1, wherein the construction method of the visual arrangement of the business processes in the visual multi-machine scheduling system comprises the following steps:
S201: starting;
s202: starting a VUE item; before starting the visual arrangement, the VUE item needs to be started; VUE is a front end framework for building user interfaces and single page applications;
s203: introducing a flow arranging component; components for process design and orchestration are introduced, which typically provide a graphical interface that allows users to intuitively create and edit business processes;
S204: writing a component support service; after the process orchestration component is introduced, a component support service is required to be written, wherein the component support service is used for supporting the normal operation of the process orchestration component and providing necessary functions;
s205: restarting the VUE item; after the component support service is written, the VUE item needs to be restarted to enable the new support service to be effective;
S206: logging and verifying; after restarting the VUE item, login verification is required;
S207: and finishing the construction of the visual arrangement.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410740833.5A CN118312296B (en) | 2024-06-11 | 2024-06-11 | Visual multi-machine scheduling system based on workflow |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410740833.5A CN118312296B (en) | 2024-06-11 | 2024-06-11 | Visual multi-machine scheduling system based on workflow |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN118312296A CN118312296A (en) | 2024-07-09 |
| CN118312296B true CN118312296B (en) | 2024-08-23 |
Family
ID=91728551
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410740833.5A Active CN118312296B (en) | 2024-06-11 | 2024-06-11 | Visual multi-machine scheduling system based on workflow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118312296B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115480753A (en) * | 2022-08-19 | 2022-12-16 | 望海康信(北京)科技股份公司 | Application integration system and corresponding computer device and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030004746A1 (en) * | 2001-04-24 | 2003-01-02 | Ali Kheirolomoom | Scenario based creation and device agnostic deployment of discrete and networked business services using process-centric assembly and visual configuration of web service components |
| CN116307757B (en) * | 2023-01-18 | 2024-02-20 | 辽宁荣科智维云科技有限公司 | Intelligent data interaction method, interaction system, computer equipment and application |
| CN116954754A (en) * | 2023-07-27 | 2023-10-27 | 上海微盟企业发展有限公司 | Business process arranging method, device, equipment and readable storage medium |
-
2024
- 2024-06-11 CN CN202410740833.5A patent/CN118312296B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115480753A (en) * | 2022-08-19 | 2022-12-16 | 望海康信(北京)科技股份公司 | Application integration system and corresponding computer device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN118312296A (en) | 2024-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103336705B (en) | Automatic transcoding between script process and Workflow system and semantic self adaptation | |
| US7093247B2 (en) | Installation of a data processing solution | |
| US8621419B2 (en) | Automating the life cycle of a distributed computing application | |
| US7451403B1 (en) | System and method for developing user interfaces purely by modeling as meta data in software application | |
| Emmerich | Distributed component technologies and their software engineering implications | |
| von Laszewski et al. | Workflow concepts of the java cog kit | |
| US20170255886A1 (en) | Workflow execution | |
| US20020144256A1 (en) | Method of deployment for concurrent execution of multiple versions of an integration model on an integration server | |
| US20100281456A1 (en) | System and method for application process automation over a computer network | |
| CN101384995A (en) | Administration automation in application servers | |
| US20090144703A1 (en) | Method and system for versioning a software system | |
| US8752030B1 (en) | Process abstraction and tracking, systems and methods | |
| US20030140126A1 (en) | Method of deployment for concurrent execution of multiple versions of an integration model | |
| CN112564979B (en) | Execution method and device of construction task, computer equipment and storage medium | |
| Rellermeyer et al. | Building, deploying, and monitoring distributed applications with eclipse and r-osgi | |
| CN118312296B (en) | Visual multi-machine scheduling system based on workflow | |
| CN111522623A (en) | Multi-process running system of modular software | |
| Bennour et al. | A reconfiguration framework for distributed components | |
| Bertoncello et al. | Explicit exception handling variability in component-based product line architectures | |
| Ying et al. | Modeling and verifying configuration in service deployment | |
| Cao et al. | Distributed supply chain simulation using a generic job running framework | |
| CN119621021B (en) | A method, device and computing device cluster for generating an execution plan | |
| Hugues et al. | From MDD to full industrial process: building distributed real-time embedded systems for the high-integrity domain | |
| Bureš et al. | CoCoME in SOFA | |
| Schlatow et al. | Automating integration under emergent constraints for embedded systems |
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 |