WO2021093674A1 - 工作流系统中的bi节点执行方法、装置、设备及计算机可读存储介质 - Google Patents

工作流系统中的bi节点执行方法、装置、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2021093674A1
WO2021093674A1 PCT/CN2020/126827 CN2020126827W WO2021093674A1 WO 2021093674 A1 WO2021093674 A1 WO 2021093674A1 CN 2020126827 W CN2020126827 W CN 2020126827W WO 2021093674 A1 WO2021093674 A1 WO 2021093674A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
result set
execution
workflow
workflow system
Prior art date
Application number
PCT/CN2020/126827
Other languages
English (en)
French (fr)
Inventor
黄山
尹强
王和平
刘有
杨峙岳
冯朝阁
邸帅
卢道和
Original Assignee
深圳前海微众银行股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳前海微众银行股份有限公司 filed Critical 深圳前海微众银行股份有限公司
Publication of WO2021093674A1 publication Critical patent/WO2021093674A1/zh

Links

Classifications

    • 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]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context

Definitions

  • This application relates to the field of data processing technology of financial technology (Fintech), and in particular to a method, device, device, and computer-readable storage medium for executing BI nodes in a workflow system.
  • the existing BI (Business Intelligence (Business Intelligence) system workflow implementation mainly relies on the following methods: After the execution of the pre-node of the BI node corresponding to the BI system, a certain state is changed as a signal to trigger the execution of the BI node (may be written to a file , Send a message to the queue, call an interface, etc.).
  • the pre-node is the node before the BI node in the workflow of the workflow system
  • the post-node is the node after the BI node in the workflow.
  • the cost of connecting the BI node with its pre-node and post-node is too high.
  • each node is an external system with each other, and the data and code logic are both Isolated from each other, only limited signal and data exchange can be carried out through the realization of some interfaces.
  • the external system corresponding to each pre-node must specifically implement a signal transmission logic, and the external system corresponding to each pre-node supports different signal transmission methods, so it is used as a signal
  • the BI system itself has to adapt to various forms of signals, which greatly increases the complexity and the probability of errors.
  • the main purpose of this application is to provide a BI node execution method, device, equipment and medium in a workflow system, aiming to solve the difficulty of data transmission between corresponding nodes in different systems in the existing workflow system, and the success rate Low, high data transmission cost technical issues.
  • the BI node execution method in the workflow system includes the steps:
  • the scheduler corresponding to the workflow system executes the pre-node corresponding to the BI system to obtain the first result set in the corresponding table format;
  • the second result set is sent to the BI node, so that the BI node generates a third result set according to the second result set, and stores the job identifier corresponding to the third result set in the work Context information corresponding to the stream system.
  • the step of executing the BI node corresponding to the BI system according to the first result set to generate a second result set in a picture format includes:
  • the execution of the BI system dashboard is triggered according to the view model information, the view content information, and the dashboard information, so as to execute the BI node corresponding to the BI system to generate a second result set in a picture format.
  • the method before the step of extracting metadata in the first result set and using the metadata as a calling parameter to call the execution interface of the BI system, the method further includes:
  • the step of the scheduler corresponding to the workflow system executing the pre-node corresponding to the BI system to obtain the first result set in the corresponding table format includes:
  • the scheduler corresponding to the workflow system invokes the execution method of the pre-node corresponding to the BI system, and calls the external system corresponding to the pre-node according to the execution method to execute a preset script to obtain an execution result set in a preset format;
  • the execution result set is converted into a first result set in a table format.
  • the step of calling an external system corresponding to the pre-node according to the execution method to execute a preset script to obtain an execution result set in a preset format includes:
  • the execution request is sent to the external system corresponding to the front node, so that the external system executes the preset script corresponding to the script name according to the execution request to obtain an execution result set in a preset format.
  • the method before the step of executing the BI node corresponding to the BI system according to the first result set to generate a second result set in a picture format, the method further includes:
  • a storage path for storing the corresponding first result set is determined according to the job identifier, and the corresponding first result set is acquired in the storage system according to the storage path.
  • the method before the step of executing the pre-node corresponding to the BI system by the scheduler corresponding to the workflow system to obtain the first result set in the corresponding table format, the method further includes:
  • the present application also provides a BI node execution device in a workflow system, and the BI node execution device in the workflow system includes:
  • the execution module is used to execute the pre-node corresponding to the BI system to obtain the first result set in the corresponding table format;
  • a generating module configured to execute the BI node corresponding to the BI system according to the first result set to generate a second result set in a picture format
  • the sending module is configured to send the second result set to the BI node, so that the BI node generates a third result set according to the second result set, and identifies the job corresponding to the third result set It is stored in the context information corresponding to the workflow system.
  • the present application also provides a BI node execution device in a workflow system.
  • the BI node execution device in the workflow system includes a memory, a processor, and a device stored on the memory and available in all locations.
  • the BI node execution program in the workflow system running on the processor, and the BI node execution program in the workflow system is executed by the processor to implement the steps of the BI node execution method in the workflow system as described above .
  • the present application also provides a computer-readable storage medium on which is stored the BI node execution program in the workflow system, and the BI node execution program in the workflow system is stored on the computer-readable storage medium.
  • the steps of the BI node execution method in the workflow system as described above are realized.
  • This application executes the pre-node corresponding to the BI system through the scheduler corresponding to the workflow system to obtain the first result set corresponding to the table format, and executes the BI node corresponding to the BI system according to the first result set to generate the second result set in the image format , Send the second result set to the BI node for the BI node to generate the third result set according to the second result set, and store the job identifier corresponding to the third result set in the context information corresponding to the workflow system, changing the work The execution body of the flow system.
  • the external system corresponding to each node in the workflow directly interacts with data.
  • the workflow only plays a role of series connection and scheduling, and the workflow needs to actively adapt to each external system.
  • this embodiment It is based on the workflow itself, the workflow of the workflow system is responsible for the series connection, and the scheduler of the workflow system is responsible for scheduling to realize the resource sharing and data transmission between each node corresponding to the external system. Each node corresponds to the external system. Special logic for signal transmission is required, and there is no need to adapt multiple forms of signals, which reduces the difficulty and data transmission cost of data transmission between external systems corresponding to workflow nodes, and because external systems do not need to adapt multiple forms of signals , Reduce the error rate of data transmission between external systems.
  • Fig. 1 is a schematic flowchart of a first embodiment of a BI node execution method in a workflow system of the present application.
  • Fig. 2 is a schematic flowchart of a third embodiment of the BI node execution method in the workflow system of the present application.
  • FIG. 3 is a functional schematic diagram and module diagram of a preferred embodiment of the BI node execution device in the workflow system of the present application.
  • Figure 4 is a schematic structural diagram of a hardware operating environment involved in a solution of an embodiment of the present application
  • FIG. 1 is a schematic flowchart of a first embodiment of the method for executing a BI node in a workflow system of this application.
  • the embodiment of the application provides an embodiment of the BI node execution method in the workflow system. It should be noted that although the logical sequence is shown in the flowchart, in some cases, the sequence may be different from here. Perform the steps shown or described.
  • the BI node execution method in the workflow system includes:
  • Step S10 The scheduler corresponding to the workflow system executes the pre-node corresponding to the BI system to obtain the first result set in the corresponding table format.
  • the workflow system corresponds to a scheduler, and both the external system and the BI system have corresponding nodes in the workflow system, and the nodes corresponding to the BI system are denoted as BI nodes.
  • the node before the BI node is called the pre-node
  • the node after the BI node is the post-node.
  • the BI system is also an external system corresponding to the workflow system.
  • the scheduler executes the pre-node corresponding to the BI system, that is, executes the node before the BI node in the workflow, and obtains the first result set in the corresponding table format. It should be noted that the execution instruction can be triggered by the user as needed, or triggered by a timing task in the workflow system.
  • the scheduler schedules the corresponding nodes of each external system in the workflow system, and executes the components of each node.
  • Each pre-node will have a corresponding first result set, but the specific first result sets in the input BI node are determined by the execution method corresponding to the BI node. For example, it is possible to send the first result set of the preceding node in front of the BI node to the BI node, or send the first result set of the three preceding nodes in front of the BI node to the BI node.
  • step S10 includes:
  • Step a The scheduler corresponding to the workflow system calls the execution method of the pre-node corresponding to the BI system, and calls the external system corresponding to the pre-node to execute the preset script according to the execution method, and obtains the execution result set in the preset format.
  • Step b Convert the execution result set into a first result set in a table format.
  • the scheduler of the workflow system executes the pre-node
  • the scheduler invokes the execution method of the BI system corresponding to the pre-node, and according to the execution method, schedules the external system corresponding to the pre-node to execute the preset script to obtain the preset The execution result set of the format.
  • each node has a corresponding executor, and each executor has a corresponding execution method.
  • the execution method is preset, and the execution method of different nodes may be different.
  • the parameter generation method in the process of executing the preset script, the calling logic for calling the execution interface of the corresponding external system, the first result set adaptation and other logics are preset.
  • the executor is a part of the scheduler, and an executor is an execution thread.
  • the preset script is preset in the execution method.
  • the preset format of the execution result set can be set according to specific needs. For example, the preset format can be set to the JSON (JavaScript Object Notation, JS object notation) format to get the JSON format Result set of the execution, or set the preset format to CSV (Comma-Separated Values).
  • the scheduler obtains the execution result set, it converts the execution result set into the first result set in the table format, that is, the execution result set is stored in the table format.
  • the metadata is the corresponding field name and field type in the execution result set.
  • Each row in the first result set contains field values corresponding to each field, that is, in the first result set, a record is a row. If there are A and B fields in the execution result set, the first record is A1 and B1, the first record is A2 and B2, A1 and A2 are the field values corresponding to the A field, and B1 and B2 are the field values corresponding to the B field. Then in the first result set, A1 and B1 are a row in the table, and A2 and B2 are a row in the table.
  • the scheduler calls the execution method of each node of the workflow, a corresponding job identifier is generated for each node.
  • the job identifier is an integer, and the user can set the job identifier to which integer according to specific needs.
  • the scheduler executes the preceding node again, the scheduler will increase the job ID by 1, that is, every time the scheduler executes the node, the job ID corresponding to the node will increase by 1.
  • the job ID of the node in the workflow is globally unique, and the job ID is stored in the context information of the workflow system.
  • the scheduler when the scheduler obtains the execution result set, the scheduler will convert the execution result set into a table format preset in the workflow system, obtain the first result set in the table format, and obtain the preset root directory,
  • the user name and job identifier corresponding to the front node generate the storage path of the first result set according to the root directory, user name, and job identifier, that is, the storage path of the first result set is: root directory+user name+job identifier.
  • the scheduler determines the storage path of the first result set, the first result set is stored in the storage system according to the storage path.
  • each pre-node has a corresponding user name.
  • the root directory corresponding to each node is the same, that is, the root of all the first result set storage paths
  • the directories are the same, and the user name and storage path are different.
  • the step of calling an external system corresponding to the pre-node according to the execution method to execute a preset script to obtain an execution result set in a preset format includes:
  • step b1 the execution interface of the external system corresponding to the front node is called according to the execution method, and the script name of the preset script corresponding to the front node is written as a parameter into the execution request through the execution interface.
  • Step b2 Send the execution request to the external system corresponding to the pre-node, so that the external system executes the preset script corresponding to the script name according to the execution request to obtain an execution result set in a preset format .
  • the scheduler calls the execution interface of the external system corresponding to the corresponding pre-node according to the execution method, and based on the execution interface, determines the corresponding pre-node corresponding to the corresponding pre-node by the execution method.
  • the script name of the script is preset
  • the obtained script name is written as a parameter in the execution request
  • the execution request carrying the script name is sent to the external system corresponding to the front node.
  • the scheduler obtains the script name in the execution request, executes the preset script corresponding to the script name, and obtains the execution result set in the preset format.
  • the execution interface is HTTP (HyperText Transfer Protocol (Hypertext Transfer Protocol) protocol transmits data.
  • the execution interface may also use other communication protocols to transmit data.
  • each preset script has a corresponding script name.
  • the preset script can be pre-stored in the corresponding external system or stored in a specific storage system. , Such as can be stored in HDFS (Hadoop In Distributed File System (Hadoop Distributed File System), the external system can obtain the corresponding preset script in the storage system through the script name, and then execute the obtained preset script to obtain the execution result set in the preset format.
  • HDFS Hadoop In Distributed File System
  • the external system can obtain the corresponding preset script in the storage system through the script name, and then execute the obtained preset script to obtain the execution result set in the preset format.
  • each node in the workflow system stores the entity information corresponding to the external system.
  • the entity information can be the storage path of the preset script.
  • node A stores the storage path "/user/student.sql" of the preset script in the Spark-SQL system
  • the execution method of the executor corresponding to node A has preset the parameter generation method in the process of executing the preset script, Invoke the call logic of the execution interface of the corresponding external system and the logic of the first result set adaptation and so on.
  • the execution method of the A node executor call the execution interface (HTTP protocol) of the Spark-SQL system, and put the script name as a parameter in the HTTP execution request.
  • the Spark-SQL system receives the execution request, it executes the corresponding preset script (such as executing select * from students) to get the execution result set.
  • the content of the execution result set is the name and score fields of the students table, and these two Field value corresponding to each field, and convert the execution result set into JSON format, and return it to the executor of node A in the HTTP response, so as to return the execution result set in JSON format to the scheduler, so that the scheduler can obtain the execution result Set, such as the execution result set is ⁇ columns:["name","score”], rows:[["wangming","90"],[ "Xiaozhang”,”92]] ⁇ .
  • the scheduler will ⁇ columns:["name”,”score”], rows:[["wangming”,”90”],["xiaozhang”,”92]] ⁇
  • the execution result set in JSON format is converted into a table, and the metadata contains a name of name and type of string (string) And a field whose name is score (information) and type is number, and there are two rows with field values of "wangming", "90 and "xiaozhang”," 92 respectively, which will convert the execution result set into the first result set in a table format.
  • Step S20 Execute the BI node corresponding to the BI system according to the first result set to generate a second result set in a picture format.
  • the scheduler After the scheduler obtains the first result set, the scheduler schedules the execution method of the BI node executor corresponding to the BI system, executes the execution method according to the first result set, and generates a second result set in a picture format.
  • step S20 includes:
  • Step c Extract metadata in the first result set, and call the execution interface of the BI system using the metadata as a calling parameter.
  • Step d Update the field name and field type in the metadata to the view model information corresponding to the BI system through the execution interface, and update the storage path of the first result set to the BI system In the view content information of the corresponding view.
  • the scheduler extracts the metadata in the first result set, uses the metadata as a call parameter to call the execution interface of the BI system, and updates the field name and field type in the metadata to the corresponding view of the BI system through the execution interface
  • the model information the updated view model information is obtained, the storage path of the first result set is obtained, and the storage path of the first result set is updated to the view content information of the corresponding view in the BI system to obtain the updated view content information.
  • the view model information and view content information are preset. In the view model information, the field name and field type corresponding to the filling position are set. The scheduler only needs to fill in the field name and field type in the view model information.
  • the execution interface can be expressed as the /api/rest_s/v1/vangogh/views/ ⁇ id ⁇ interface.
  • Step e Invoking the display interface corresponding to the BI system to obtain the dashboard information corresponding to the BI system.
  • the scheduler calls the display interface corresponding to the BI system, and obtains the dashboard information corresponding to the BI system through the display interface.
  • the dashboard information includes but is not limited to the dashboard ID, view ID, and item name.
  • the scheduler finds the JSON object corresponding to the dashboard through the dashboard identifier, and obtains the view identifier from the JSON object.
  • the presentation form of the dashboard identifier and view identifier is not limited.
  • Each BI system has a corresponding dashboard identifier.
  • the view identifier is used to indicate that the view corresponding to the second result set is generated, and the item name is the second result.
  • the display interface can be the /api/rest_s/v1/vangogh/displays interface.
  • Step f Trigger execution of the BI system dashboard according to the view model information, view content information, and the dashboard information to execute the BI node corresponding to the BI system to generate a second result set in a picture format.
  • the scheduler obtains the dashboard information, the updated view model information and the updated view content information
  • the scheduler obtains the field value corresponding to the field name in the updated view model information according to the updated view content information.
  • the field type of the field value is determined by the field type of the corresponding field name in the updated view model information. It should be noted that there is a storage path for storing the first result set in the updated view content information. According to the storage path and the field name and field type in the updated view model information, the second result set can be obtained in the storage system.
  • the data required by the result set is the field value corresponding to the field name.
  • the scheduler After the scheduler obtains the field value corresponding to the field name, the scheduler triggers the execution of the BI system dashboard according to the dashboard information, that is, executes the BI node corresponding to the BI system to generate the second result set in the image format. Specifically, the scheduler identifies the view interface that needs to be scheduled according to the dashboard identification in the dashboard information, and then triggers the execution of the chart corresponding to the dashboard identification through the view interface to generate the field value corresponding to the obtained field name.
  • the second result set of the project name and view ID The second result set can be represented in the shape of a histogram or a pie chart.
  • the image format of the second result set includes but is not limited to PNG (Portable Network Graphics, portable network graphics), BMP (BitMaP, bitmap) and TIF (TagImage FileFormat, tag image file format).
  • the view interface can be expressed as the /api/rest_s/v1/vangogh/displays/ ⁇ id ⁇ /preview interface.
  • Step S30 Send the second result set to the BI node for the BI node to generate a third result set according to the second result set, and store the job identifier corresponding to the third result set in The context information corresponding to the workflow system.
  • the scheduler After the scheduler obtains the second result set, the scheduler sends the second result set to the BI node through the HTTP interface. After the BI node receives the second result set, the BI node generates the third result set according to the second result set, that is, reads the second result set in the image format as encoded text to obtain the third result set.
  • the third result set is Base64 encoded text. In other embodiments, the third result set may also be other forms of encoded text. Base64 is one of the most common encoding methods used to transmit 8Bit bytecode on the Internet. Base64 is a method of representing binary data based on 64 printable characters.
  • the metadata information is the result set type, field-related information, and coded text.
  • the result set type of the third result set metadata information is PNG; the field related information in the third result set is empty; if the third result set is Base64 encoded text, Then the value of the encoded text in the third result set is a line of Base64 encoded text.
  • the BI node After the BI node obtains the third result set, the BI node obtains its corresponding job identifier, and stores the job identifier in the context information corresponding to the workflow system.
  • the BI node obtains its user name, generates a storage path based on the root directory, user name, and job ID, that is, the storage path is: root directory + user name + job ID, and stores the third result set in the storage system according to the storage path.
  • the user name and job identifier in the third result set are the user name and job identifier of the BI node.
  • the job identification of each node in the workflow is stored in the context information of the workflow system, so that the job identification of each node is uniformly maintained through the context information.
  • the scheduler will call the execution method of the post node corresponding to the BI node, and execute the post node according to the third result set.
  • the scheduler corresponding to the workflow system executes the pre-node corresponding to the BI system to obtain the first result set corresponding to the table format, and executes the BI node corresponding to the BI system according to the first result set to generate the second result in the image format.
  • Set send the second result set to the BI node for the BI node to generate the third result set according to the second result set, and store the job identifier corresponding to the third result set in the context information corresponding to the workflow system, which changes The executive body of the workflow system.
  • the external system corresponding to each node in the workflow directly interacts with data.
  • the workflow only plays the role of serialization and scheduling. The workflow needs to actively adapt to each external system.
  • the workflow itself is the main one
  • the workflow of the workflow system is responsible for the series connection
  • the scheduler of the workflow system is responsible for scheduling to realize the resource sharing and data transmission between each node corresponding to the external system, and each node corresponds to the external system
  • the workflow system provides a unified interface for external systems to access.
  • the external system For a node of a successful workflow, the external system only needs to have the interface logic specified by the workflow framework preset in the workflow system. It can adapt to the workflow system, reducing the difficulty of adapting the external system and the workflow system.
  • an interactive page-level system integration method is provided, so that users can seamlessly jump to the page of the BI system on the same page when editing the workflow node in the workflow system. After completing a series of operations in the BI system, return to the page of the workflow system.
  • Step f Generate an interface call request carrying the login status information of the BI system and send it to the gateway corresponding to the workflow system, so that the gateway can confirm that the login status information in the interface call request is correct, and then send the interface
  • the call request is sent to the BI system to call the interface of the BI system according to the interface call request.
  • the scheduler Before the scheduler executes the BI node, the scheduler generates an interface call request carrying the login status information of the BI system, and sends the interface call request to the corresponding gateway of the workflow system.
  • the login status information can be a specific identifier, and the login status information of different external systems is inconsistent.
  • the workflow system will store the login status information of the BI system.
  • the gateway receives the interface call request, the gateway obtains the login state information in the interface call request.
  • the request is sent to the BI system to call the interface of the BI system according to the interface call request; if the obtained login state information is inconsistent with the stored login state information, the gateway determines that the login state information in the interface call request is wrong and does not call the interface The request is sent to the BI system. It should be noted that the login status information of each external system is stored in the gateway.
  • the interface call request may be an HTTP request.
  • the scheduler may calculate the hash value of the login state information, and add the hash value of the login state information to the interface call request.
  • the scheduler can use MD5 (Message Digest Algorithm (Information Digest Algorithm) calculates the hash value of the login state information.
  • the scheduler may also calculate the hash value of the login state information through other methods of calculating the hash value.
  • the gateway receives the interface call request, the gateway obtains the hash value in the interface call request, and calculates the hash value of its stored login status information.
  • the gateway determines that the login state information in the interface call request is correct; if the hash value in the interface call request is inconsistent with the calculated hash value, the gateway determines that the login state information in the interface call request is wrong. It should be noted that the calculation method for the gateway to calculate the hash value of the login state information is consistent with the calculation method for the scheduler to calculate the hash value of the login state information.
  • the BI system is connected to the gateway where the workflow system is located, and the interface calls from the workflow system to the BI system are no longer in the form of direct point-to-point calls, but unified first after the gateway service is requested, the gateway recognizes the interface call request , So as to decide whether to send the interface call request to the BI system.
  • the scheduler executes the workflow corresponding to other nodes, it can also use the login status information of the corresponding external system for login verification, avoiding different external systems. Different login authentication methods are used, and the communication between external systems needs to process a lot of log-in information management logic, which reduces the difficulty of communication between the external systems of the corresponding nodes of the workflow system.
  • the BI node execution method in the workflow system further includes:
  • Step g Store the first result set in a preset storage system.
  • Step h After detecting that all the front-end nodes corresponding to the BI system are in a successful state, determine the job identifier corresponding to the front-end node.
  • Step i Determine a storage path for storing the corresponding first result set according to the job identifier, and obtain the corresponding first result set in the storage system according to the storage path.
  • the scheduler When the scheduler obtains the first result set, the scheduler stores the first result set in a preset storage system. Specifically, the scheduler obtains the user name and job ID corresponding to the front node, according to the root directory, user name and job ID A storage path for storing the first result set is determined, and the corresponding first result set is stored in a preset storage system according to the storage path. It can be understood that, because the user names and job identifiers corresponding to the various front nodes are inconsistent, the storage paths corresponding to the first result sets are also inconsistent.
  • the scheduler detects whether all the front nodes corresponding to the BI system are in a successful state. It is understandable that when the first result set corresponding to the predecessor node is obtained, it indicates that the predecessor node is in a successful state. If the scheduler detects that all pre-nodes are in a successful state, the scheduler obtains the job ID corresponding to the pre-node from the context information corresponding to the workflow system, and determines the storage path for storing the corresponding first result set according to the job ID. The path obtains the first result set corresponding to the job identifier in the storage system.
  • the BI node by storing the first result set obtained by the scheduler executing the pre-node in the storage system, and storing the job identifier corresponding to the pre-node in the context information of the workflow system, it is possible to execute the execution according to the first result set.
  • the user does not need to manually record the relevant information of the external system corresponding to the front node and input it into the BI system corresponding to the BI node.
  • the success rate of BI node execution and reduces the sense of separation between users using external systems.
  • the difference between the third embodiment of the BI node execution method in the workflow system and the first and/or the second embodiment of the BI node execution method in the workflow system is that, referring to FIG. 2, the workflow system
  • the BI node execution method also includes:
  • Step S40 Read each node in the workflow corresponding to the workflow system, and determine the execution sequence of each node according to the dependency relationship between each node.
  • Step S50 Determine the front node corresponding to the BI system according to the execution sequence.
  • the scheduler After the scheduler receives the execution instruction, the scheduler reads each node in the workflow system corresponding to the workflow, and determines the execution order of each node according to the dependency relationship between each node, and determines the front-end corresponding to the BI system according to the execution order. ⁇ Node.
  • the dependency between each node is preset. Nodes without any pre-dependency are executed first, and nodes without any post-dependency are executed last. It is understandable that nodes without any pre-dependence are the first node in the workflow, and there is no post-dependency.
  • the node of is the last node in the workflow.
  • the pre-node is the node before the BI node in the workflow.
  • the nodes behind the workflow will only be executed after the nodes in front of the workflow are in a successful state.
  • the scheduler executes each node in the workflow, the scheduler will call the execution method of the corresponding node.
  • the execution order of each node is determined according to the dependency relationship between each node in the workflow, and the pre-node corresponding to the BI system is determined according to the execution sequence, so that the BI system is executed when the pre-nodes are in a successful execution state.
  • the corresponding BI node execute the BI node in time.
  • the present application also provides a BI node execution device in a workflow system.
  • the BI node execution device in the workflow system includes:
  • the execution module 10 is used to execute the pre-node corresponding to the BI system to obtain the first result set in the corresponding table format;
  • the generating module 20 is configured to execute the BI node corresponding to the BI system according to the first result set to generate a second result set in a picture format;
  • the sending module 30 is configured to send the second result set to the BI node, so that the BI node generates a third result set according to the second result set, and assigns the job corresponding to the third result set
  • the identifier is stored in the context information corresponding to the workflow system.
  • the generating module 20 includes:
  • An extraction unit configured to extract metadata in the first result set, and call the execution interface of the BI system using the metadata as a calling parameter;
  • the update unit is configured to update the field name and field type in the metadata to the view model information corresponding to the BI system through the execution interface, and update the storage path of the first result set to the In the view content information of the corresponding view of the BI system;
  • the first calling unit is configured to call the display interface corresponding to the BI system to obtain dashboard information corresponding to the BI system;
  • a generating unit configured to trigger the execution of the BI system dashboard according to the view model information, view content information, and the dashboard information, so as to execute the BI node corresponding to the BI system, and generate a second result set in a picture format .
  • the generating module 20 is also configured to generate an interface call request carrying the login status information of the BI system and send it to the gateway corresponding to the workflow system, so that the gateway can confirm the login status in the interface call request. After the information is correct, the interface call request is sent to the BI system to call the interface of the BI system according to the interface call request.
  • execution module 10 includes:
  • the second calling unit is used for the scheduler corresponding to the workflow system to call the execution method of the front node corresponding to the BI system;
  • the execution unit is configured to invoke the external system corresponding to the pre-node to execute a preset script according to the execution method to obtain an execution result set in a preset format;
  • the conversion unit is configured to convert the execution result set into a first result set in a table format.
  • execution unit includes:
  • the calling subunit is configured to call the execution interface of the external system corresponding to the front node according to the execution method, and write the script name of the preset script corresponding to the front node as a parameter into the execution request through the execution interface;
  • the sending subunit is configured to send the execution request to the external system corresponding to the pre-node, so that the external system can execute the preset script corresponding to the script name according to the execution request to obtain a preset format Execute the result set.
  • the BI node execution device in the workflow system further includes:
  • a storage module configured to store the first result set in a preset storage system
  • the first determining module is configured to determine the job ID corresponding to the front node after detecting that all the front nodes corresponding to the BI system are in a successful state; and determine the storage corresponding to the first result set according to the job ID path;
  • the obtaining module is configured to obtain the corresponding first result set in the storage system according to the storage path.
  • the BI node execution device in the workflow system further includes:
  • a reading module which is used to read each node in the workflow system
  • the second determining module is configured to determine the execution order of each node according to the dependency relationship between the nodes; and determine the front node corresponding to the BI system according to the execution order.
  • FIG. 4 is a schematic structural diagram of the hardware operating environment involved in the solution of the embodiment of the present application.
  • FIG. 4 can be a schematic structural diagram of the hardware operating environment of the BI node execution device in the workflow system.
  • the BI node execution device in the workflow system of the embodiment of the present application may be a terminal device such as a PC and a portable computer.
  • the BI node execution device in the workflow system may include: a processor 1001, such as a CPU, a memory 1005, a user interface 1003, a network interface 1004, and a communication bus 1002.
  • the communication bus 1002 is used to implement connection and communication between these components.
  • the user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface.
  • the network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory), such as disk storage.
  • the memory 1005 may also be a storage device independent of the aforementioned processor 1001.
  • the BI node execution device in the workflow system may also include a camera, an RF (Radio Frequency, radio frequency) circuit, a sensor, an audio circuit, a WiFi module, and so on.
  • RF Radio Frequency, radio frequency
  • the structure of the BI node execution device in the workflow system shown in FIG. 4 does not constitute a limitation on the BI node execution device in the workflow system, and may include more or less than that shown in the figure. Components, or a combination of certain components, or different component arrangements.
  • the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a BI node execution program in a workflow system.
  • the operating system is a program that manages and controls the BI node execution device hardware and software resources in the workflow system, and supports the operation of the BI node execution program and other software or programs in the workflow system.
  • the user interface 1003 is mainly used to connect to the client and perform data communication with the client;
  • the network interface 1004 is mainly used to communicate with the background server and perform data communication with the background server;
  • the processor 1001 may be used to call the BI node execution program in the workflow system stored in the memory 1005, and execute the steps of the BI node execution method in the workflow system as described above.
  • the specific implementation of the BI node execution device in the workflow system of the present application is basically the same as each embodiment of the BI node execution method in the workflow system described above, and will not be repeated here.
  • an embodiment of the present application also proposes a computer-readable storage medium, the computer-readable storage medium stores a BI node execution program in a workflow system, and the BI node execution program in the workflow system is processed by a processor. During execution, the steps of the BI node execution method in the workflow system as described above are implemented.
  • the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to enable a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method described in each embodiment of the present application.
  • a terminal device which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请公开了一种工作流系统中的BI节点执行方法、装置、设备及计算机可读存储介质，涉及金融科技领域，该方法包括步骤：工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集；根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集；将所述第二结果集发送给所述BI节点，以供所述BI节点根据所述第二结果集生成第三结果集，并将所述第三结果集对应的作业标识存储在所述工作流系统对应的上下文信息中。

Description

工作流系统中的BI节点执行方法、装置、设备及计算机可读存储介质
本申请要求于2019年11月15日申请的、申请号为201911118545.1、名称为“工作流系统中的BI节点执行方法、装置、设备及介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及金融科技（Fintech）的数据处理技术领域，尤其涉及一种工作流系统中的BI节点执行方法、装置、设备及计算机可读存储介质。
 背景技术
随着计算机技术的发展，越来越多的技术应用在金融领域，传统金融业正在逐步向金融科技（Fintech）转变，数据处理技术也不例外，但由于金融行业的安全性、实时性要求，也对技术提出的更高的要求。
现有的BI（Business Intelligence，商业智能）系统的工作流实现，主要依靠以下方式：BI系统对应的BI节点的前置节点执行完毕后，改变某种状态，作为触发BI节点执行的信号（可能是写入某个文件、往队列中发送某个消息、调用某接口等方式）。其中，前置节点为工作流系统工作流中在BI节点之前的节点，后置节点为工作流中在BI节点之后的节点。BI节点与其前置节点和后置节点的对接成本过高，虽然BI节点与其前置节点和后置节点在同一工作流上，但各个节点之间都互为外部系统，数据和代码逻辑都是相互隔离的，只能通过一些接口的实现来进行有限的信号和数据的交换。对于需要给BI节点发送信号的前置节点，每个前置节点对应的外部系统要专门实现一次信号传输的逻辑，而且每个前置节点对应的外部系统支持的信号发送方式不同，因此作为信号接收方，BI系统本身也不得不适配多种形式的信号，大大增强复杂度和出错的概率，这些复杂的逻辑对系统本身的业务逻辑毫无益处，且会造成大量开发成本的浪费。
由此可知，在工作流系统中，不同系统对应节点之间数据传输难度大，成功率低，数据传输成本高。
 技术解决方案
本申请的主要目的在于提供一种工作流系统中的BI节点执行方法、装置、设备及介质，旨在解决现有的在工作流系统中，不同系统对应节点之间数据传输难度大，成功率低，数据传输成本高的技术问题。
为实现上述目的，本申请提供一种工作流系统中的BI节点执行方法，所述工作流系统中的BI节点执行方法包括步骤：
工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集；
根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集；
将所述第二结果集发送给所述BI节点，以供所述BI节点根据所述第二结果集生成第三结果集，并将所述第三结果集对应的作业标识存储在所述工作流系统对应的上下文信息中。
在一实施例中，所述根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集的步骤包括：
提取所述第一结果集中的元数据，将所述元数据作为调用参数调用所述BI系统的执行接口；
通过所述执行接口将所述元数据中的字段名称和字段类型更新到所述BI系统对应的视图模型信息中，并将所述第一结果集的存储路径更新到所述BI系统对应视图的视图内容信息中；
调用所述BI系统对应的显示接口获取所述BI系统对应仪表盘信息；
根据所述视图模型信息、视图内容信息和所述仪表盘信息触发所述BI系统仪表盘的执行，以执行所述BI系统对应的BI节点，生成图片格式的第二结果集。
在一实施例中，所述提取所述第一结果集中的元数据，将所述元数据作为调用参数调用所述BI系统的执行接口的步骤之前，还包括：
生成携带所述BI系统登录态信息的接口调用请求发送给所述工作流系统对应的网关，以供所述网关确认所述接口调用请求中的登录态信息正确后，将所述接口调用请求发送给所述BI系统，以根据所述接口调用请求调用所述BI系统的接口。
在一实施例中，所述工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集的步骤包括：
工作流系统对应的调度器调用BI系统对应前置节点的执行方法，根据所述执行方法调用所述前置节点对应的外部系统执行预设脚本，得到预设格式的执行结果集；
将所述执行结果集转换为表格格式的第一结果集。
在一实施例中，所述根据所述执行方法调用所述前置节点对应的外部系统执行预设脚本，得到预设格式的执行结果集的步骤包括：
根据所述执行方法调用所述前置节点对应外部系统的执行接口，通过所述执行接口将所述前置节点对应预设脚本的脚本名称作为参数写入执行请求中；
将所述执行请求发送给所述前置节点对应的外部系统，以供所述外部系统根据所述执行请求执行所述脚本名称对应的预设脚本，得到预设格式的执行结果集。
在一实施例中，所述根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集的步骤之前，还包括：
将所述第一结果集存储到预设的存储系统中；
当检测到所述BI系统对应的所有前置节点处于成功状态后，确定所述前置节点对应的作业标识；
根据所述作业标识确定存储对应第一结果集的存储路径，根据所述存储路径在所述存储系统中获取对应的所述第一结果集。
在一实施例中，所述工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集的步骤之前，还包括：
读取所述工作流系统中的各个节点，并根据各个节点之间的依赖关系确定各个节点的执行顺序；
根据所述执行顺序确定所述BI系统对应的前置节点。
此外，为实现上述目的，本申请还提供一种工作流系统中的BI节点执行装置，所述工作流系统中的BI节点执行装置包括：
执行模块，用于执行BI系统对应的前置节点，得到对应表格格式的第一结果集；
生成模块，用于根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集；
发送模块，用于将所述第二结果集发送给所述BI节点，以供所述BI节点根据所述第二结果集生成第三结果集，并将所述第三结果集对应的作业标识存储在所述工作流系统对应的上下文信息中。
此外，为实现上述目的，本申请还提供一种工作流系统中的BI节点执行设备，所述工作流系统中的BI节点执行设备包括存储器、处理器和存储在所述存储器上并可在所述处理器上运行的工作流系统中的BI节点执行程序，所述工作流系统中的BI节点执行程序被所述处理器执行时实现如上所述的工作流系统中的BI节点执行方法的步骤。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有工作流系统中的BI节点执行程序，所述工作流系统中的BI节点执行程序被处理器执行时实现如上所述的工作流系统中的BI节点执行方法的步骤。
本申请通过工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集，根据第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集，将第二结果集发送给BI节点，以供BI节点根据第二结果集生成第三结果集，并将第三结果集对应的作业标识存储在工作流系统对应的上下文信息中，改变了工作流系统的执行主体，现有技术中由工作流中各个节点对应的外部系统直接进行数据交互，工作流只起到串联和调度作用，需要工作流主动去适配各个外部系统，而本实施例是由工作流本身为主，由工作流系统的工作流负责串联，工作流系统的调度器负责调度，来实现各个节点对应外部系统之间的资源共享、数据传输等，各个节点对应外部系统不需要信号传输的专门逻辑，也不需要适配多种形式的信号，降低了工作流节点对应外部系统之间数据传输的难度和数据传输成本，且由于外部系统不需要适配多种形式的信号，降低了外部系统之间数据传输的出错率。
 附图说明
图1是本申请工作流系统中的BI节点执行方法第一实施例的流程示意图。
图2是本申请工作流系统中的BI节点执行方法第三实施例的流程示意图。
图3是本申请工作流系统中的BI节点执行装置较佳实施例的功能示意图模块图。
图4是本申请实施例方案涉及的硬件运行环境的结构示意图
 本发明的实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请提供一种工作流系统中的BI节点执行方法，参照图1，图1为本申请工作流系统中的BI节点执行方法第一实施例的流程示意图。
本申请实施例提供了工作流系统中的BI节点执行方法的实施例，需要说明的是，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
工作流系统中的BI节点执行方法包括：
步骤S10，工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集。
在本申请实施例中，工作流系统对应着一个调度器，外部系统和BI系统在工作流系统中都存在对应的节点，BI系统对应的节点记为BI节点。在工作流系统的工作流中，将BI节点之前的节点称为前置节点，BI节点之后的节点称为后置节点。可以理解的是，BI系统也为工作流系统对应的一个外部系统。当工作流系统接收到执行指令时，工作流系统会启动其调度器，该调度器会根据该执行指令按照预先设置好的执行顺序执行对应工作流中的各个节点。调度器执行BI系统对应的前置节点，即执行工作流中BI节点之前的节点，得到对应表格格式的第一结果集。需要说明的是，执行指令可由用户根据需要而触发，或者由工作流系统中的定时任务触发。调度器为工作流系统中调度各个外部系统对应节点，执行各个节点的组件。每个前置节点都会存在对应的第一结果集，但是输入BI节点中具体是那几个第一结果集是由BI节点对应的执行方法决定。如可能将BI节点前面那个前置节点的第一结果集发送给BI节点，或者将BI节点前面三个前置节点的第一结果集发送给BI节点。
进一步地，步骤S10包括：
步骤a，工作流系统对应的调度器调用BI系统对应前置节点的执行方法，根据所述执行方法调用所述前置节点对应的外部系统执行预设脚本，得到预设格式的执行结果集。
步骤b，将所述执行结果集转换为表格格式的第一结果集。
具体地，工作流系统的调度器在执行前置节点过程中，调度器调用BI系统对应前置节点的执行方法，根据该执行方法调度前置节点对应的外部系统执行预设脚本，得到预设格式的执行结果集。需要说明的是，在工作流系统的工作流中，每个节点都存在对应的执行器，每个执行器存在对应的执行方法，执行方法是预先设置好的，不同节点的执行方法可能不一样。执行方法中预先设置好了执行预设脚本过程中的参数生成方法、调用对应外部系统的执行接口的调用逻辑和第一结果集适配等逻辑等。
执行器为调度器的一部分，一个执行器就是一个执行线程。预设脚本是预先设置在执行方法中的，执行结果集的预设格式可根据具体需要而设置，如可将预设格式设置为JSON（JavaScript Object Notation，JS对象简谱）格式，即得到JSON格式的执行结果集，或者将预设格式设置为CSV（Comma-Separated Values，逗号分隔值）。当调度器得到执行结果集后，将执行结果集转换为表格格式的第一结果集，即将执行结果集以表格格式存储。在第一结果集中，元数据为执行结果集中对应的字段名称和字段类型，第一结果集中每一行中都存在各个字段对应的字段值，即在第一结果集中，一条记录为一行。如执行结果集中存在A和B字段，第一条记录为A1和B1，第一条记录为A2和B2，A1和A2是A字段对应的字段值，B1和B2是B字段对应的字段值，则在第一结果集中，A1和B1为表格中的一行，A2和B2为表格中的一行。
进一步地，在调度器调用工作流各个节点的执行方法过程中，会为各个节点生成对应的作业标识，本实施例中作业标识是一个整数，用户可以根据具体需要将作业标识设置为何种整数。当调度器再次执行该前置节点时，调度器会将该作业标识增加1，即调度器每执行一次节点，该节点对应的作业标识就会增加1。工作流中节点的作业标识是全局唯一的，作业标识是存储在工作流系统的上下文信息中的。
进一步地，当调度器获得执行结果集后，调度器会将执行结果集转换为工作流系统中预先设置好的表格格式，得到表格格式的第一结果集，并获取预先设置好的根目录、前置节点对应的用户名和作业标识，根据根目录、用户名和作业标识生成第一结果集的存储路径，即第一结果集的存储路径为：根目录+用户名+作业标识。当调度器确定第一结果集的存储路径后，根据该存储路径将第一结果集存储至存储系统中。可以理解的是，在工作流系统中，每一个前置节点都存在对应的用户名，在工作流系统中，各个节点对应的根目录是相同的，即所有第一结果集存储路径中的根目录都是相同，用户名和存储路径是不一样的。
进一步地，所述根据所述执行方法调用所述前置节点对应的外部系统执行预设脚本，得到预设格式的执行结果集的步骤包括：
步骤b1，根据所述执行方法调用所述前置节点对应外部系统的执行接口，通过所述执行接口将所述前置节点对应预设脚本的脚本名称作为参数写入执行请求中。
步骤b2，将所述执行请求发送给所述前置节点对应的外部系统，以供所述外部系统根据所述执行请求执行所述脚本名称对应的预设脚本，得到预设格式的执行结果集。
具体地，调度器在调用前置节点对应的执行方法后，调度器根据执行方法调用对应前置节点对应的外部系统的执行接口，并基于该执行接口，通过执行方法确定对应前置节点对应的预设脚本的脚本名称，将所获取的脚本名称作为参数写入执行请求中，将携带脚本名称的执行请求发送给前置节点对应的外部系统。当外部系统接收到执行请求后，调度器获取执行请求中的脚本名称，执行该脚本名称对应的预设脚本，得到预设格式的执行结果集。在一实施例中，在本实施例中，执行接口是以HTTP（HyperText Transfer Protocol，超文本传输协议）协议传输数据的，在其它实施例中，执行接口也可以采用其它通信协议传输数据。
可以理解的是，每一个预设脚本都存在对应的脚本名称，通过脚本名称，可以唯一确定一个预设脚本，预设脚本可以预先存储在对应的外部系统中，也可以存储在特定的存储系统中，如可以存储在HDFS（Hadoop Distributed File System，Hadoop分布式文件系统）中，外部系统可以通过该脚本名称在存储系统中获取对应的预设脚本，然后执行所获取的预设脚本，得到预设格式的执行结果集。
为了便于理解，以下举例说明以Spark-SQL（ Structured Query Language，结构化查询语言）系统对应的A节点作为前置节点举例说明。调度器调用A节点的执行器的执行方法，生成一个作业标识，该作业标识全局唯一。在本实施例中，工作流系统中的每个节点都存储了对应外部系统的实体信息，该实体信息可为预设脚本的存储路径，在将执行请求发送给外部系统时，可以将预设脚本的存储路径一起发送给外部系统，以供外部系统根据该存储路径快速查找到存储预设脚本的文件夹，然后根据脚本名称确定对应的预设脚本，以提高获取预设脚本的获取速度。
如A节点存储了Spark-SQL系统中预设脚本的存储路径“/user/student.sql”，A节点对应的执行器的执行方法中预先设置好了执行预设脚本过程中的参数生成方法、调用对应外部系统的执行接口的调用逻辑和第一结果集适配等逻辑等。通过A节点执行器的执行方法，调用Spark-SQL系统的执行接口（HTTP协议），将脚本名称作为参数，放入HTTP的执行请求中，。Spark-SQL系统收到执行请求后，执行对应的预设脚本（如执行select * from students），得到执行结果集，如执行结果集的内容为students表的name和score两个字段，以及这两个字段对应的字段值，并将执行结果集转换成JSON格式，放在HTTP的响应中里返回给A节点的执行器，以将JSON格式的执行结果集返回给调度器，使调度器获得执行结果集，如该执行结果集为{columns:[“name”,”score”], rows:[[“wangming”,”90”],[ “xiaozhang”,”92]]}。调度器将{columns:[“name”,”score”], rows:[[“wangming”,”90”],[ “xiaozhang”,”92]]}JSON格式的执行结果集，转换成为类型为表格、元数据包含一个名称为name类型为string（字符串）和一个名称为score（整形）类型为number的字段、有两行分别为“wangming”，”90和“xiaozhang”，”92的字段值，即将执行结果集转换成表格格式的第一结果集。
步骤S20，根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集。
当调度器得到第一结果集后，调度器调度BI系统对应BI 节点执行器的执行方法，根据第一结果集执行该执行方法，生成图片格式的第二结果集。
进一步地，步骤S20包括：
步骤c，提取所述第一结果集中的元数据，将所述元数据作为调用参数调用所述BI系统的执行接口。
步骤d，通过所述执行接口将所述元数据中的字段名称和字段类型更新到所述BI系统对应的视图模型信息中，并将所述第一结果集的存储路径更新到所述BI系统对应视图的视图内容信息中。
具体地，调度器提取第一结果集中的元数据，将该元数据作为调用参数调用BI系统的执行接口，并通过该执行接口将元数据中的字段名称和字段类型更新到BI系统对应的视图模型信息中，得到更新后的视图模型信息，并获取第一结果集的存储路径，将第一结果集的存储路径更新到BI系统对应视图的视图内容信息中，得到更新后的视图内容信息。其中，视图模型信息和视图内容信息是预先设置好的，在视图模型信息中，设置有字段名称和字段类型对应的填写位置，调度器只需将字段名称和字段类型填写到视图模型信息中对应的填写位置即可；在视图内容信息中，设置有存储路径的填写位置，调度器也只需将存储路径填写到视图内容信息中对应的填写路径即可。如上述例子，字段名称为“name”和“number”，“name”对应的字段类型为“string”；“number”对应的字段类型为“score”。执行接口可表示为/api/rest_s/v1/vangogh/views/{id}接口。
步骤e，调用所述BI 系统对应的显示接口获取所述BI系统对应仪表盘信息。
当调度器得到第一结果集后，调度器调用BI系统对应的显示接口，通过该显示接口获取BI系统对应的仪表盘信息，其中，仪表盘信息包括但不限于仪表盘标识、视图标识和项目名称。具体地，调度器通过仪表盘标识找到仪表盘对应的JSON对象，在JSON对象中获取视图标识。在本实施例中，不限制仪表盘标识和视图标识的表现形式，每一BI系统都存在对应的仪表盘标识，视图标识用于表示生成第二结果集对应的视图，项目名称为第二结果集对应项目的名称，在图片格式的第二结果集中，包括项目名称。如显示接口可为/api/rest_s/v1/vangogh/displays接口。
步骤f，根据所述视图模型信息、视图内容信息和所述仪表盘信息触发所述BI系统仪表盘的执行，以执行所述BI系统对应的BI节点，生成图片格式的第二结果集。
当调度器获取到仪表盘信息，以及得到更新后的视图模型信息和更新后的视图内容信息后，调度器根据更新后的视图内容信息获取更新后视图模型信息中字段名称对应的字段值，该字段值的字段类型由更新后视图模型信息中对应字段名称的字段类型决定。需要说明的是，在更新后的视图内容信息中有存储第一结果集的存储路径，根据该存储路径和更新后的视图模型信息中的字段名称和字段类型可以在存储系统中获取生成第二结果集所需的数据，即获取到字段名称对应的字段值。
当调度器获取到字段名称对应的字段值后，调度器根据仪表盘信息触发BI系统仪表盘的执行，即执行BI系统对应的BI节点，以生成图片格式的第二结果集。具体地，调度器根据仪表盘信息中的仪表盘标识所需调度的视图接口，然后通过该视图接口触发仪表盘标识对应的图表的执行，以根据所获取的字段名称对应的字段值，生成含有项目名称和视图标识的第二结果集。第二结果集可以柱状图或者扇形图等形状来表示，第二结果集的图片格式包括但不限于PNG（Portable Network Graphics，便携式网络图形）、BMP（BitMaP，位图）和TIF（TagImage FileFormat，标签图像文件格式）。视图接口可表示为/api/rest_s/v1/vangogh/displays/{id}/preview接口。
步骤S30，将所述第二结果集发送给所述BI节点，以供所述BI节点根据所述第二结果集生成第三结果集，并将所述第三结果集对应的作业标识存储在所述工作流系统对应的上下文信息中。
当调度器得到第二结果集后，调度器将第二结果集通过HTTP接口发送给BI节点。当BI节点接收到第二结果集后，BI节点根据第二结果集生成第三结果集，即将图片格式的第二结果集读取为编码文本，得到第三结果集。在一实施例中，第三结果集为Base64的编码文本，在其它实施例中，第三结果集也可为其它形式的编码文本。Base64是网络上最常见的用于传输8Bit字节码的编码方式之一，Base64就是一种基于64个可打印字符来表示二进制数据的方法。在第三结果集中，元数据信息为结果集类型、字段相关信息和编码文本。具体地，若第二结果集是PNG图片格式，则第三结果集元数据信息的结果集类型为PNG；第三结果集中的字段相关信息为空；若第三结果集是Base64的编码文本，则第三结果集中的编码文本的值为一行Base64编码的文本。
当BI节点得到第三结果集后，BI节点获取其对应的作业标识，将作业标识存储在工作流系统对应的上下文信息中。BI节点并获取其用户名，根据根目录、用户名和作业标识生成存储路径，即存储路径为：根目录+用户名+作业标识，根据该存储路径将第三结果集存储至存储系统中。需要说明的是，存储第三结果集中的用户名和作业标识是BI节点的用户名和作业标识。可以理解的是，在本实施例中，工作流中各个节点的作业标识都是存储在工作流系统的上下文信息中的，以便于通过上下文信息统一维护各个节点的作业标识。
可以理解的是，当调度器执行完       BI节点之后，调度器将调用BI节点对应后置节点的执行方法，根据第三结果集执行后置节点。
本实施例通过工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集，根据第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集，将第二结果集发送给BI节点，以供BI节点根据第二结果集生成第三结果集，并将第三结果集对应的作业标识存储在工作流系统对应的上下文信息中，改变了工作流系统的执行主体，现有技术中由工作流中各个节点对应的外部系统直接进行数据交互，工作流只起到串联和调度作用，需要工作流主动去适配各个外部系统，而本实施例是由工作流本身为主，由工作流系统的工作流负责串联，工作流系统的调度器负责调度，来实现各个节点对应外部系统之间的资源共享、数据传输等，各个节点对应外部系统不需要信号传输的专门逻辑，也不需要适配多种形式的信号，降低了工作流节点对应外部系统之间数据传输的难度和数据传输成本，且由于外部系统不需要适配多种形式的信号，降低了外部系统之间数据传输的出错率。
进一步地，在本实施例中，工作流系统提供统一的接口供外部系统接入，成功工作流的一个节点，外部系统只需存在工作流系统中预先设置好的工作流框架规定的接口逻辑，即可适配工作流系统，降低了外部系统与工作流系统的适配难度。在工作流系统中，提供交互页面层次的系统集成方法，使用户能够在工作流系统中编辑工作流节点时，在同一页面无缝跳转到BI系统的页面。在完成在BI系统中的一系列操作后，回到工作流系统的页面中。
进一步地，提出本申请工作流系统中的BI节点执行方法第二实施例。
所述工作流系统中的BI节点执行方法第二实施例与所述工作流系统中的BI节点执行方法第一实施例的区别在于，所述工作流系统中的BI节点执行方法还包括：
步骤f，生成携带所述BI系统登录态信息的接口调用请求发送给所述工作流系统对应的网关，以供所述网关确认所述接口调用请求中的登录态信息正确后，将所述接口调用请求发送给所述BI系统，以根据所述接口调用请求调用所述BI系统的接口。
在调度器执行BI节点之前，调度器生成携带BI系统登录态信息的接口调用请求，并将该接口调用请求发送给工作流系统对应的网关。其中，登录态信息可为特定的标识，不同外部系统的登录态信息不一致。在BI系统作为BI节点接入到工作流系统中时，工作流系统会存储该BI系统的登录态信息。当网关接收到接口调用请求后，网关获取接口调用请求中的登录态信息，若所获取的登录态信息与其存储的登录态信息一致，则确定接口调用请求中的登录态信息正确，将接口调用请求发送给BI系统，以根据该接口调用请求调用BI系统的接口；若所获取的登录态信息与其存储的登录态信息不一致，网关则确定接口调用请求中的登录态信息错误，不将接口调用请求发送给BI系统。需要说明的是，在网关中，存储有各个外部系统的登录态信息。接口调用请求可为HTTP请求。
具体地，调度器可计算登录态信息的散列值，将登录态信息的散列值添加至接口调用请求中。在一实施例中，调度器可通过MD5（Message Digest Algorithm，信息摘要算法）计算出登录态信息的散列值，在其它实施例中，调度器也可通过其它计算散列值的方法计算出登录态信息的散列值。当网关接收到接口调用请求后，网关获取接口调用请求中的散列值，并计算其存储登录态信息的散列值，若接口调用请求中的散列值和计算所得的散列值一致，网关则确定接口调用请求中的登录态信息正确；若接口调用请求中的散列值和计算所得的散列值不一致，网关则确定接口调用请求中的登录态信息错误。需要说明的是，网关计算登录态信息散列值的计算方法与调度器计算登录态信息散列值的计算方法一致。
本实施例通过BI系统接入工作流系统所在的网关，从工作流系统到BI系统的接口调用，不再以直接点对点调用的形式，而是统一先请求网关服务后，由网关识别接口调用请求，从而决定是否将接口调用请求发送至BI系统中，需要说明的是，调度器在执行工作流对应其它节点之前，也可以采用对应外部系统的登录态信息进行登录验证，避免了由于不同外部系统采用登录验证方式不同，外部系统之间的通信需要处理很多登录态信息的管理逻辑的情况出现，降低了工作流系统对应节点的外部系统之间的通信难度。
进一步地，所述工作流系统中的BI节点执行方法还包括：
步骤g，将所述第一结果集存储到预设的存储系统中。
步骤h，当检测到所述BI系统对应的所有前置节点处于成功状态后，确定所述前置节点对应的作业标识。
步骤i，根据所述作业标识确定存储对应第一结果集的存储路径，根据所述存储路径在所述存储系统中获取对应的所述第一结果集。
当调度器得到第一结果集后，调度器将第一结果集存储到预设的存储系统中，具体地，调度器获取前置节点对应的用户名和作业标识，按照根目录、用户名和作业标识确定存储第一结果集的存储路径，根据该存储路径将对应的第一结果集存储到预设的存储系统中。可以理解的是，由于各个前置节点对应的用户名和作业标识不一致，各个第一结果集对应的存储路径也不一致。
调度器检测BI系统对应的所有前置节点是否处于成功状态。可以理解的是，当得到前置节点对应的第一结果集后，则表明前置节点处于成功状态。若调度器检测到所有前置节点处于成功状态，调度器则从工作流系统对应的上下文信息中获取前置节点对应的作业标识，根据作业标识确定存储对应第一结果集的存储路径，根据存储路径在存储系统中获取作业标识对应的第一结果集。
本实施例通过将调度器执行前置节点所得第一结果集存储至存储系统中，并将前置节点对应的作业标识存储在工作流系统的上下文信息中，实现了在根据第一结果集执行BI节点时，不需要用户手动记录前置节点对应的外部系统的相关信息输入至BI节点对应的BI系统中，降低了在执行BI节点过程中，外部系统相关信息输入错误的情况出现，提高了BI节点执行的成功率，且降低了用户使用外部系统之间割裂感。
进一步地，提出本申请工作流系统中的BI节点执行方法第三实施例。
所述工作流系统中的BI节点执行方法第三实施例与所述工作流系统中的BI节点执行方法第一和/或第二实施例的区别在于，参照图2，所述工作流系统中的BI节点执行方法还包括：
步骤S40，读取所述工作流系统对应工作流中的各个节点，并根据各个节点之间的依赖关系确定各个节点的执行顺序。
步骤S50，根据所述执行顺序确定所述BI系统对应的前置节点。
调度器在接收到执行指令后，调度器读取工作流系统对应工作流中的各个节点，并根据各个节点之间的依赖关系确定各个节点的执行顺序，根据该执行顺序确定BI系统对应的前置节点。其中，各个节点之间的依赖关系是预先设置好的。无任何前置依赖的节点在最先执行，无任何后置依赖的节点在最后执行，可以理解的是，无任何前置依赖的节点为工作流中的第一个节点，无任何后置依赖的节点为工作流中的最后一个节点。前置节点为工作流中在BI节点之前的节点。需要说明的是，在工作流中，只有工作流前面的节点处于成功状态后，才会执行工作流后面的节点。在工作流中，也可能会存在多个节点同时执行，只要满足对应节点的执行条件即可。在调度器执行工作流中的各个节点过程中，调度器会调用对应节点的执行方法。
本实施例通过根据工作流中各个节点之间的依赖关系确定各个节点的执行顺序，根据该执行顺序确定BI系统对应的前置节点，以在前置节点都处于执行成功状态时，执行BI系统对应的BI节点，以及时执行BI节点。
此外，参照图3，本申请还提供一种工作流系统中的BI节点执行装置，所述工作流系统中的BI节点执行装置包括：
执行模块10，用于执行BI系统对应的前置节点，得到对应表格格式的第一结果集；
生成模块20，用于根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集；
发送模块30，用于将所述第二结果集发送给所述BI节点，以供所述BI节点根据所述第二结果集生成第三结果集，并将所述第三结果集对应的作业标识存储在所述工作流系统对应的上下文信息中。
进一步地，所述生成模块20包括：
提取单元，用于提取所述第一结果集中的元数据，将所述元数据作为调用参数调用所述BI系统的执行接口；
更新单元，用于通过所述执行接口将所述元数据中的字段名称和字段类型更新到所述BI系统对应的视图模型信息中，并将所述第一结果集的存储路径更新到所述BI系统对应视图的视图内容信息中；
第一调用单元，用于调用所述BI 系统对应的显示接口获取所述BI系统对应仪表盘信息；
生成单元，用于根据所述视图模型信息、视图内容信息和所述仪表盘信息触发所述BI系统仪表盘的执行，以执行所述BI系统对应的BI节点，生成图片格式的第二结果集。
进一步地，所述生成模块20还用于生成携带所述BI系统登录态信息的接口调用请求发送给所述工作流系统对应的网关，以供所述网关确认所述接口调用请求中的登录态信息正确后，将所述接口调用请求发送给所述BI系统，以根据所述接口调用请求调用所述BI系统的接口。
进一步地，所述执行模块10包括：
第二调用单元，用于工作流系统对应的调度器调用BI系统对应前置节点的执行方法；
执行单元，用于根据所述执行方法调用所述前置节点对应的外部系统执行预设脚本，得到预设格式的执行结果集；
转换单元，用于将所述执行结果集转换为表格格式的第一结果集。
进一步地，所述执行单元包括：
调用子单元，用于根据所述执行方法调用所述前置节点对应外部系统的执行接口，通过所述执行接口将所述前置节点对应预设脚本的脚本名称作为参数写入执行请求中；
发送子单元，用于将所述执行请求发送给所述前置节点对应的外部系统，以供所述外部系统根据所述执行请求执行所述脚本名称对应的预设脚本，得到预设格式的执行结果集。
进一步地，所述工作流系统中的BI节点执行装置还包括：
存储模块，用于将所述第一结果集存储到预设的存储系统中；
第一确定模块，用于当检测到所述BI系统对应的所有前置节点处于成功状态后，确定所述前置节点对应的作业标识；根据所述作业标识确定存储对应第一结果集的存储路径；
获取模块，用于根据所述存储路径在所述存储系统中获取对应的所述第一结果集。
进一步地，所述工作流系统中的BI节点执行装置还包括：
读取模块，用于读取所述工作流系统中的各个节点；
第二确定模块，用于根据各个节点之间的依赖关系确定各个节点的执行顺序；根据所述执行顺序确定所述BI系统对应的前置节点。
需要说明的是，工作流系统中的BI节点执行装置的各个实施例与上述工作流系统中的BI节点执行方法的各实施例基本相同，在此不再详细赘述。
此外，本申请还提供一种工作流系统中的BI节点执行设备。如图4所示，图4是本申请实施例方案涉及的硬件运行环境的结构示意图。
需要说明的是，图4即可为工作流系统中的BI节点执行设备的硬件运行环境的结构示意图。本申请实施例工作流系统中的BI节点执行设备可以是PC，便携计算机等终端设备。
如图4所示，该工作流系统中的BI节点执行设备可以包括：处理器1001，例如CPU，存储器1005，用户接口1003，网络接口1004，通信总线1002。其中，通信总线1002用于实现这些组件之间的连接通信。用户接口1003可以包括显示屏（Display）、输入单元比如键盘（Keyboard），可选用户接口1003还可以包括标准的有线接口、无线接口。网络接口1004可选的可以包括标准的有线接口、无线接口（如WI-FI接口）。存储器1005可以是高速RAM存储器，也可以是稳定的存储器（non-volatile memory），例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
可选地，工作流系统中的BI节点执行设备还可以包括摄像头、RF（Radio Frequency，射频）电路，传感器、音频电路、WiFi模块等等。
本领域技术人员可以理解，图4中示出的工作流系统中的BI节点执行设备结构并不构成对工作流系统中的BI节点执行设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
如图4所示，作为一种计算机存储介质的存储器1005中可以包括操作系统、网络通信模块、用户接口模块以及工作流系统中的BI节点执行程序。其中，操作系统是管理和控制工作流系统中的BI节点执行设备硬件和软件资源的程序，支持工作流系统中的BI节点执行程序以及其它软件或程序的运行。
在图4所示的工作流系统中的BI节点执行设备中，用户接口1003主要用于连接客户端，与客户端进行数据通信；网络接口1004主要用于后台服务器，与后台服务器进行数据通信；处理器1001可以用于调用存储器1005中存储的工作流系统中的BI节点执行程序，并执行如上所述的工作流系统中的BI节点执行方法的步骤。
本申请工作流系统中的BI节点执行设备具体实施方式与上述工作流系统中的BI节点执行方法各实施例基本相同，在此不再赘述。
此外，本申请实施例还提出一种计算机可读存储介质，所述计算机可读存储介质上存储有工作流系统中的BI节点执行程序，所述工作流系统中的BI节点执行程序被处理器执行时实现如上所述的工作流系统中的BI节点执行方法的步骤。
本申请计算机可读存储介质具体实施方式与上述工作流系统中的BI节点执行方法各实施例基本相同，在此不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质（如ROM/RAM、磁碟、光盘）中，包括若干指令用以使得一台终端设备（可以是手机，计算机，服务器，空调器，或者网络设备等）执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (10)

  1. 一种工作流系统中的商业智能BI节点执行方法，其中，所述工作流系统中的BI节点执行方法包括以下步骤：
    工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集；
    根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集；
    将所述第二结果集发送给所述BI节点，以供所述BI节点根据所述第二结果集生成第三结果集，并将所述第三结果集对应的作业标识存储在所述工作流系统对应的上下文信息中。
  2. 如权利要求1所述的工作流系统中的BI节点执行方法，其中，所述根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集的步骤包括：
    提取所述第一结果集中的元数据，将所述元数据作为调用参数调用所述BI系统的执行接口；
    通过所述执行接口将所述元数据中的字段名称和字段类型更新到所述BI系统对应的视图模型信息中，并将所述第一结果集的存储路径更新到所述BI系统对应视图的视图内容信息中；
    调用所述BI系统对应的显示接口获取所述BI系统对应仪表盘信息；
    根据所述视图模型信息、视图内容信息和所述仪表盘信息触发所述BI系统仪表盘的执行，以执行所述BI系统对应的BI节点，生成图片格式的第二结果集。
  3. 如权利要求2所述的工作流系统中的BI节点执行方法，其中，所述提取所述第一结果集中的元数据，将所述元数据作为调用参数调用所述BI系统的执行接口的步骤之前，还包括：
    生成携带所述BI系统登录态信息的接口调用请求发送给所述工作流系统对应的网关，以供所述网关确认所述接口调用请求中的登录态信息正确后，将所述接口调用请求发送给所述BI系统，以根据所述接口调用请求调用所述BI系统的接口。
  4. 如权利要求1所述的工作流系统中的BI节点执行方法，其中，所述工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集的步骤包括：
    工作流系统对应的调度器调用BI系统对应前置节点的执行方法，根据所述执行方法调用所述前置节点对应的外部系统执行预设脚本，得到预设格式的执行结果集；
    将所述执行结果集转换为表格格式的第一结果集。
  5. 如权利要求4所述的工作流系统中的BI节点执行方法，其中，所述根据所述执行方法调用所述前置节点对应的外部系统执行预设脚本，得到预设格式的执行结果集的步骤包括：
    根据所述执行方法调用所述前置节点对应外部系统的执行接口，通过所述执行接口将所述前置节点对应预设脚本的脚本名称作为参数写入执行请求中；
    将所述执行请求发送给所述前置节点对应的外部系统，以供所述外部系统根据所述执行请求执行所述脚本名称对应的预设脚本，得到预设格式的执行结果集。
  6. 如权利要求1所述的工作流系统中的BI节点执行方法，其中，所述根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集的步骤之前，还包括：
    将所述第一结果集存储到预设的存储系统中；
    当检测到所述BI系统对应的所有前置节点处于成功状态后，确定所述前置节点对应的作业标识；
    根据所述作业标识确定存储对应第一结果集的存储路径，根据所述存储路径在所述存储系统中获取对应的所述第一结果集。
  7. 如权利要求1至6任一项所述的工作流系统中的BI节点执行方法，其中，所述工作流系统对应的调度器执行BI系统对应的前置节点，得到对应表格格式的第一结果集的步骤之前，还包括：
    读取所述工作流系统中的各个节点，并根据各个节点之间的依赖关系确定各个节点的执行顺序；
    根据所述执行顺序确定所述BI系统对应的前置节点。
  8. 一种工作流系统中的BI节点执行装置，其中，所述工作流系统中的BI节点执行装置包括：
    执行模块，用于执行BI系统对应的前置节点，得到对应表格格式的第一结果集；
    生成模块，用于根据所述第一结果集执行BI系统对应的BI节点，生成图片格式的第二结果集；
    发送模块，用于将所述第二结果集发送给所述BI节点，以供所述BI节点根据所述第二结果集生成第三结果集，并将所述第三结果集对应的作业标识存储在所述工作流系统对应的上下文信息中。
  9. 一种工作流系统中的BI节点执行设备，其中，所述工作流系统中的BI节点执行设备包括存储器、处理器和存储在所述存储器上并可在所述处理器上运行的工作流系统中的BI节点执行程序，所述工作流系统中的BI节点执行程序被所述处理器执行时实现如权利要求1至7中任一项所述的工作流系统中的BI节点执行方法的步骤。
  10. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有工作流系统中的BI节点执行程序，所述工作流系统中的BI节点执行程序被处理器执行时实现如权利要求1至7中任一项所述的工作流系统中的BI节点执行方法的步骤。
PCT/CN2020/126827 2019-11-15 2020-11-05 工作流系统中的bi节点执行方法、装置、设备及计算机可读存储介质 WO2021093674A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911118545.1 2019-11-15
CN201911118545.1A CN110839079B (zh) 2019-11-15 2019-11-15 工作流系统中的bi节点执行方法、装置、设备及介质

Publications (1)

Publication Number Publication Date
WO2021093674A1 true WO2021093674A1 (zh) 2021-05-20

Family

ID=69575058

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/126827 WO2021093674A1 (zh) 2019-11-15 2020-11-05 工作流系统中的bi节点执行方法、装置、设备及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN110839079B (zh)
WO (1) WO2021093674A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110839079B (zh) * 2019-11-15 2022-02-08 深圳前海微众银行股份有限公司 工作流系统中的bi节点执行方法、装置、设备及介质
CN112367363A (zh) * 2020-10-23 2021-02-12 深圳前海微众银行股份有限公司 一种信息共享方法、装置、服务器及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110295795A1 (en) * 2010-05-28 2011-12-01 Oracle International Corporation System and method for enabling extract transform and load processes in a business intelligence server
CN103229198A (zh) * 2010-11-29 2013-07-31 国际商业机器公司 商业智能工具中的数据挖掘及预测洞察力的快速、动态、数据驱动的报告部署
CN107423907A (zh) * 2017-08-01 2017-12-01 江苏云光智慧信息科技有限公司 一种基于低功耗蓝牙技术的商业智能系统
CN109492056A (zh) * 2018-10-24 2019-03-19 江苏满运软件科技有限公司 一种商业智能数据查询的方法和系统
CN110839079A (zh) * 2019-11-15 2020-02-25 深圳前海微众银行股份有限公司 工作流系统中的bi节点执行方法、装置、设备及介质

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080036767A1 (en) * 2006-08-10 2008-02-14 Business Objects, S.A. Apparatus and method for selecting visualizations of multidimensional data
US20110225565A1 (en) * 2010-03-12 2011-09-15 Van Velzen Danny Optimal incremental workflow execution allowing meta-programming
US8806346B2 (en) * 2010-03-30 2014-08-12 Itxc Ip Holdings S.A.R.L. Configurable workflow editor for multimedia editing systems and methods therefor
US20140025425A1 (en) * 2012-07-17 2014-01-23 Winshuttle, Llc Bulk business workflow systems and methods
US20140214495A1 (en) * 2012-09-30 2014-07-31 iVedix, Inc. Business intelligence systems and methods
US9336288B2 (en) * 2013-06-03 2016-05-10 Bank Of America Corporation Workflow controller compatibility
US9563771B2 (en) * 2014-01-22 2017-02-07 Object Security LTD Automated and adaptive model-driven security system and method for operating the same
CN104809537A (zh) * 2014-01-27 2015-07-29 北京中油瑞飞信息技术有限公司 一种用于商务智能分析平台的工作流程实现方法
CN110333940A (zh) * 2019-06-25 2019-10-15 深圳前海微众银行股份有限公司 基于条件的任务调度方法、装置、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110295795A1 (en) * 2010-05-28 2011-12-01 Oracle International Corporation System and method for enabling extract transform and load processes in a business intelligence server
CN103229198A (zh) * 2010-11-29 2013-07-31 国际商业机器公司 商业智能工具中的数据挖掘及预测洞察力的快速、动态、数据驱动的报告部署
CN107423907A (zh) * 2017-08-01 2017-12-01 江苏云光智慧信息科技有限公司 一种基于低功耗蓝牙技术的商业智能系统
CN109492056A (zh) * 2018-10-24 2019-03-19 江苏满运软件科技有限公司 一种商业智能数据查询的方法和系统
CN110839079A (zh) * 2019-11-15 2020-02-25 深圳前海微众银行股份有限公司 工作流系统中的bi节点执行方法、装置、设备及介质

Also Published As

Publication number Publication date
CN110839079B (zh) 2022-02-08
CN110839079A (zh) 2020-02-25

Similar Documents

Publication Publication Date Title
CN108205442B (zh) 边缘计算平台
EP3011442B1 (en) Method and apparatus for customized software development kit (sdk) generation
US5327559A (en) Remote and batch processing in an object oriented programming system
CN111026931B (zh) 一种数据查询方法、装置、设备及介质
CN106874334B (zh) 一种数据处理方法及装置、资讯处理系统
US10956667B2 (en) Operational transformations proxy for thin clients
WO2017041649A1 (zh) 一种应用部署方法及设备
WO2021027592A1 (zh) 文件处理方法、装置、设备及计算机可读存储介质
WO2021093674A1 (zh) 工作流系统中的bi节点执行方法、装置、设备及计算机可读存储介质
CN112363913B (zh) 一种并行测试任务调度寻优的方法、装置和计算设备
US9128886B2 (en) Computer implemented method, computer system, electronic interface, mobile computing device and computer readable medium
CN113434175A (zh) 数据处理方法、装置、存储介质及设备
CN111881385A (zh) 推送内容生成方法、装置、设备和可读存储介质
WO2021093672A1 (zh) 外部系统的嵌入方法、工作流系统、设备及计算机可读存储介质
CN113900650A (zh) 一种数据处理的方法、装置、电子设备及可读存储介质
CN107277146B (zh) 一种分布式存储业务流量模型生成方法及系统
US9665416B1 (en) Asynchronous execution of computer operations
US11704168B2 (en) Templates for mapping data events to API calls
WO2023208132A1 (zh) Api转换系统及其访问请求处理方法、电子设备及介质
CN111327680B (zh) 认证数据同步方法、装置、系统、计算机设备和存储介质
US20210409809A1 (en) Data processing method and device, storage medium, electronic device
CN115982257A (zh) 接口创建方法以及相关设备
CN117632395A (zh) 工作流处理方法、装置、设备、存储介质和程序产品
CN110262912B (zh) 一种过程调用gRPC的调用方法及装置
US20140101280A1 (en) Generic serializer framework

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20888456

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20888456

Country of ref document: EP

Kind code of ref document: A1