CN112583897A - Data destination creating method and device of rule engine, electronic equipment and storage medium - Google Patents

Data destination creating method and device of rule engine, electronic equipment and storage medium Download PDF

Info

Publication number
CN112583897A
CN112583897A CN202011383967.4A CN202011383967A CN112583897A CN 112583897 A CN112583897 A CN 112583897A CN 202011383967 A CN202011383967 A CN 202011383967A CN 112583897 A CN112583897 A CN 112583897A
Authority
CN
China
Prior art keywords
data destination
data
destination
instruction
rule engine
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.)
Pending
Application number
CN202011383967.4A
Other languages
Chinese (zh)
Inventor
张扬扬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Baidu Netcom Science and Technology Co Ltd
Original Assignee
Beijing Baidu Netcom Science and Technology Co Ltd
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 Beijing Baidu Netcom Science and Technology Co Ltd filed Critical Beijing Baidu Netcom Science and Technology Co Ltd
Priority to CN202011383967.4A priority Critical patent/CN112583897A/en
Publication of CN112583897A publication Critical patent/CN112583897A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/242Query formulation
    • G06F16/2433Query languages
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/953Querying, e.g. by the use of web search engines
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/546Message passing systems or structures, e.g. queues
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/141Setup of application sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/146Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Software Systems (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mathematical Physics (AREA)
  • Computational Linguistics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application discloses a data destination creating method and device of a rule engine, electronic equipment and a storage medium, and relates to the technical field of Internet of things, wherein the method comprises the following steps: receiving a data destination establishing instruction input by a user; the data destination creation instruction includes a connection address of a first data destination, the first data destination being an external data destination; responding to the data destination creating instruction, and performing connectivity test on the first data destination according to the connection address of the first data destination; if the connectivity test result indicates that the first data destination is available, adding connection information of the first data destination to a data destination list of a rules engine. The method and the device can establish the external data destination for the rule engine, provide technical support for data circulation between the rule engine and the external data destination, and enable the data circulation of the rule engine to be no longer limited to the internal data destination.

Description

Data destination creating method and device of rule engine, electronic equipment and storage medium
Technical Field
The application relates to the technical field of internet of things, in particular to a rule engine data destination technology, and specifically relates to a rule engine data destination creation method and device, electronic equipment and a storage medium.
Background
Data flow of the current internet of things is generally limited to an internal data destination of the rule engine, that is, data flow between the rule engine and a data destination under the same platform or the same account can be realized. However, with the technological development of the internet of things, the data flow requirements of the rules engine are not limited to only internal data destinations.
Disclosure of Invention
The application provides a data destination creating method and device of a rule engine, electronic equipment and a storage medium.
According to a first aspect, the present application provides a data destination creation method of a rules engine, comprising:
receiving a data destination establishing instruction input by a user; the data destination creation instruction comprises connection information of a first data destination, the connection information of the first data destination comprises a connection address of the first data destination, and the first data destination is an external data destination of the rule engine;
responding to the data destination creating instruction, and performing connectivity test on the first data destination according to the connection address of the first data destination;
if the connectivity test result indicates that the first data destination is available, adding connection information of the first data destination to a data destination list of the rules engine.
According to a second aspect, the present application provides a data destination creation apparatus of a rules engine, comprising:
the first receiving module is used for receiving a data destination establishing instruction input by a user; the data destination creation instruction comprises connection information of a first data destination, the connection information of the first data destination comprises a connection address of the first data destination, and the first data destination is an external data destination of the rule engine;
the testing module is used for responding to the data destination establishing instruction and carrying out connectivity testing on the first data destination according to the connection address of the first data destination;
a first adding module, configured to add connection information of the first data destination to a data destination list of the rule engine if a connectivity test result indicates that the first data destination is available.
According to a third aspect, the present application provides an electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform any one of the methods of the first aspect.
According to a fourth aspect, the present application provides a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform any of the methods of the first aspect.
According to the technology of the application, the external data destination can be created for the rule engine, technical support is provided for data circulation between the rule engine and the external data destination, and the data circulation of the rule engine is not limited to the internal data destination.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present application, nor do they limit the scope of the present application. Other features of the present application will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
FIG. 1 is a schematic flow diagram of a data destination creation method of a rules engine according to a first embodiment of the present application;
FIG. 2 is a block diagram of a rule engine data flow system architecture according to a first embodiment of the present application;
FIG. 3 is a schematic diagram of a data destination creation apparatus of a rules engine according to a second embodiment of the present application;
fig. 4 is a block diagram of an electronic device for implementing a data destination creation method of a rules engine according to an embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
The following first explains the related terms referred to in the present application.
Rule Engine (Rule Engine): the rule engine of the application refers to a rule engine for data circulation of the internet of things. Specifically, by using the rule engine of the application, the data message of the internet of things device can be forwarded to the data destination for storage or processing, so that data transfer between the internet of things device and the data destination is realized.
In specific implementation, Structured Query Language (SQL) may be written in the rule engine to implement data conversion processing on data by the rule engine, and a forwarding condition may be configured in the rule engine to implement filtering and forwarding of the processed data to other devices or cloud services by the rule engine.
By way of example, the following provides several application scenarios for the rules engine: the rule engine may forward data of one device to another device, enabling device-to-device internet of things (M2M) communication; alternatively, the rules engine may forward the data to a Time Series Database (TSDB) for storage; alternatively, the rule engine may forward the data to a Baidu Messaging System (BMS) for flow computation; and so on.
The rule engine of the application can be a public cloud rule engine and can also be a private cloud rule engine.
Data destination: and the rule engine carries out data stream forwarding on the target address. The data destination may be a cloud product of storage, computing, message queues, and the like.
Internal data destination: data destinations on the same platform or account as the rules engine. For example, the public cloud data destination is an internal data destination of the public cloud rules engine.
External data destination: a data destination of a different platform than the rules engine, or a data destination of a different account than the rules engine. For example. The private cloud (or non-public cloud) data destination is an external data destination of the public cloud rules engine.
In the prior art, data flow of the internet of things is generally limited to the internal data destination of the rule engine, however, with the technical development of the internet of things, the data flow requirement of the rule engine is not limited to the internal data destination.
In order to solve the above technical problems in the prior art, the present application provides a data destination creation method of a rule engine, a data destination creation apparatus of a rule engine, an electronic device, and a storage medium.
Exemplary embodiments of the present application are described below.
As shown in fig. 1, the data destination creation method of the rule engine includes the following steps:
step 101: receiving a data destination establishing instruction input by a user; the data destination creation instruction comprises connection information of a first data destination, the connection information of the first data destination comprises a connection address of the first data destination, and the first data destination is an external data destination of the rule engine;
step 102: responding to the data destination creating instruction, and performing connectivity test on the first data destination according to the connection address of the first data destination;
step 103: if the connectivity test result indicates that the first data destination is available, adding connection information of the first data destination to a data destination list of the rules engine.
Typically, only the internal data destinations of the rule engine are included in the data destination list of the rule engine. In the embodiment of the present application, through the above steps, it can be implemented that an available external data destination (i.e. a first data destination) is created for the rule engine, and the connection information of the first data destination is added to the data destination list of the rule engine, that is, the available external data destination is created for the rule engine. The data destination list of the rule engine may be used exclusively for storing external data destinations of the rule engine, and may also be used for storing internal data destinations of the rule engine, which is not limited in the present application.
In the embodiment of the present application, the type of the first data destination is not limited, and the first data destination may be, for example, a rockmq data destination.
In a specific implementation, a data destination creating module may be configured for the rule engine to create the external data destination for the rule engine, and the data destination creating module may receive a data destination creating instruction input by a user, and perform a connectivity test on a connection address of the external data destination to be created according to the data destination creating instruction to determine whether the external data destination to be created is available. In the event that it is determined that an external data destination to be created is available, the data destination creation module can add connection information such as a connection address of the external data destination to be created to the data destination list of the rules engine. A connectivity test module can also be additionally configured for the rule engine to realize the connectivity test of the data destination.
By creating the external data destination by the user, the external data destination can be flexibly configured for the rule engine, and the diversity and configurability of the rule engine data destination are improved. By performing connectivity test on the external data destination to be created, the user can obtain the connectivity of the corresponding data destination in time, and the availability of the external data destination is ensured.
According to the embodiment of the application, the external data destination can be created for the rule engine, technical support is provided for data circulation between the rule engine and the external data destination, and the data circulation of the rule engine is not limited to the internal data destination.
Optionally, after the adding the connection information of the first data destination to the data destination list of the rule engine, the method further includes:
receiving a data destination selection instruction input by a user, wherein the data destination selection instruction indicates that the first data destination is selected;
in response to the data destination selection instruction, adding connection information for the first data destination to a rule of the rules engine.
After the first data destination is created for the rule engine, a corresponding data destination may also be added for the rule engine based on a data destination selection instruction input by a user. If the user selects the first data destination for the rule engine, the connection information of the first data destination may be added to the rule of the rule engine.
In a specific implementation, the data destination selection instruction input by the user may be a user selection operation on a data destination list of the rule engine, and the user may select a first data destination from the data destination list of the rule engine. The data destination list and the public cloud service destination list query module can be provided for a user, and the user can conveniently obtain all available destination service lists.
In specific implementation, the data destination selected by the user can be added to the rule of the rule engine through the rule editing module of the rule engine. After adding the data destination to the rules of the rules engine, the rules engine may send the data to the data destination.
By selecting the external data destination for the rule engine by the user, the external data destination can be flexibly configured for the rule engine, and the diversity and configurability of the rule engine data destination are improved.
In the embodiment of the application, the external data destination is created and added for the rule engine, so that the rule engine can perform data flow transfer with the external data destination, and the data flow of the rule engine is not limited to the internal data destination.
Optionally, after adding the connection information of the first data destination to the rule of the rule engine, the method further includes:
receiving a data destination deleting instruction input by a user, wherein the data destination deleting instruction indicates that the first data destination is deleted;
in response to the data destination delete instruction, deleting the connection information for the first data destination from the rules of the rules engine.
After the user selects an external data destination for the rules engine, the user can delete the previously selected external data destination from the rules of the rules engine based on the specific requirements, regardless of whether the rules engine is data-streaming with the external data destination.
After the connection information of the first data destination is deleted from the rule of the rule engine, the connection information of the first data destination may be continuously retained in the data destination list of the rule engine, and may be added to the rule of the rule engine again when needed later, or may be directly deleted from the data destination list of the rule engine, which is not limited in the present application.
By deleting the external data destination of the rule engine by the user, the external data destination can be flexibly adjusted for the rule engine, and the diversity and configurability of the rule engine data destination are improved.
Optionally, after adding the connection information of the first data destination to the rule of the rule engine, the method further includes:
receiving a data transmission instruction, the data transmission instruction instructing transmission of first data to the first data destination;
and responding to the data sending instruction, establishing connection between the rule engine and the first data destination, and sending the first data to the first data destination.
After the user selects the first data destination for the rule engine, the rule engine may establish a connection with the first data destination and send the first data to the first data destination if the rule engine receives a data sending instruction to send the first data to the first data destination.
In specific implementation, a special data transmission module for an external data destination can be configured for the rule engine, so that the rule engine can send data to the external data destination; alternatively, the rule engine may be implemented to send data to an external data destination via a rule processing module of the rule engine.
In this application, the operation of the rule engine to send data to the data destination may be referred to as a data destination operation, which is the final data operation in which the rule engine forwards the received device message to the data destination.
The embodiment realizes the data flow transfer between the rule engine and the external data destination, so that the data flow of the rule engine is not limited to the internal data destination.
Optionally, the first data destination is a rockmq data destination, and the connection information of the first data destination further includes Topic information of the rockmq data destination; the data send instruction indicates to send the first data to a target Topic of the RockettMQ data destination;
the establishing a connection between the rule engine and the first data destination and sending the first data to the first data destination in response to the data sending instruction includes:
responding to the data sending instruction, establishing connection between the rule engine and the RocktMQ data destination, adding the identification corresponding to the target Topic to the first data, and then sending the first data to the RocktMQ data destination.
The RocktMQ is an open-source distributed message middleware, is a message middleware of a queue model, has the characteristics of high performance, high reliability, high real-time performance, distribution and the like, and supports transaction messages, sequential messages, batch messages, timing messages, message backtracking and the like. The RocketMQ mainly comprises a Producer, a Broker and a Consumer, wherein the Producer is responsible for producing messages, the Consumer is responsible for consuming messages, and the Broker is responsible for storing messages. The Broker corresponds to a server in the actual deployment process, each Broker may store a plurality of Topic messages, and each Topic message may also be stored in different brokers in pieces. The Message Queue is used for storing the physical addresses of the messages, and the Message address in each Topic is stored in a plurality of Message queues. The Consumer Group is composed of multiple Consumer instances.
In other words, a rockmq data destination is typically configured with multiple topics, different topics being available to receive different types of messages or data. When a user sends a message to a rockmq data destination, it is necessary to specify which Topic of the rockmq data destination to send the message.
In view of the above-described characteristics of the RocketMQ data destination, when creating the RocketMQ data destination, the Topic information of the RocketMQ data destination may be carried in the data destination creation instruction, that is, the connection information of the RocketMQ data destination includes the Topic information of the RocketMQ data destination in addition to the connection address. And the target Topic of the rockmq data destination may be carried in the data sending instruction, that is, the first data is sent to the target Topic of the rockmq data destination in an instruction.
When first data is sent to the rockmq data destination, an identifier (tag) corresponding to the target Topic may be added to the first data, so that after the rockmq data destination receives the first data, the corresponding target Topic may be determined according to the identifier carried in the first data, thereby facilitating the rockmq data destination to process (e.g., store or calculate) the first data in the target Topic according to user requirements.
By the implementation mode, the high efficiency and the high directivity of the rule engine for sending data to the RockettMQ data destination can be improved, and the data circulation flow between the rule engine and the RockettMQ data destination is optimized.
To further illustrate the overall flow of creation, addition, and data flow of external data destinations, an exemplary description of the rules engine data flow system architecture provided below in connection with FIG. 2 is provided.
As shown in fig. 2, the rule engine is configured with a data destination creation module 201, a rule creation module 202, a rule editing module 203 and a rule processing module 204, wherein the data destination creation module 201 can receive a data destination creation instruction input by a user and implement creation of an external data destination for the rule engine according to the data destination creation instruction. The rule creation module 202 may receive a rule creation instruction input by a user and create a rule for the rule engine according to the rule creation instruction. The rule editing module 203 can receive a data destination selection instruction input by a user and add connection information of an external data destination selected by the user to a rule of the rule engine according to the data destination selection instruction. The rule processing module 204 is configured to process related data flow rules including an external data destination to implement data flow between the rule engine and the data destination, and specifically, the rule processing module 204 may receive related data or messages sent by the device 206 through the message center 205, and after performing rule processing on the data or messages, flow the data or messages to the external data destination 207 or the internal data destination 208.
It should be noted that, the present application is not limited to this application, and various optional embodiments in the data destination creation method of the rule engine may be implemented in combination with each other or implemented separately.
The above embodiments of the present application have at least the following advantages or benefits:
according to the embodiment of the application, the external data destination can be created for the rule engine, technical support is provided for data circulation between the rule engine and the external data destination, and the data circulation of the rule engine is not limited to the internal data destination.
As shown in fig. 3, the present application provides a data destination creation apparatus 300 of a rules engine, comprising:
a first receiving module 301, configured to receive a data destination creation instruction input by a user; the data destination creation instruction comprises connection information of a first data destination, the connection information of the first data destination comprises a connection address of the first data destination, and the first data destination is an external data destination of the rule engine;
a testing module 302, configured to perform a connectivity test on the first data destination according to a connection address of the first data destination in response to the data destination creation instruction;
a first adding module 303, configured to add connection information of the first data destination to a data destination list of the rule engine if the connectivity test result indicates that the first data destination is available.
Optionally, the data destination creating apparatus 300 of the rule engine further includes:
a second receiving module, configured to receive a data destination selection instruction input by a user, where the data destination selection instruction indicates that the first data destination is selected;
a second adding module, configured to add the connection information of the first data destination to the rule of the rule engine in response to the data destination selection instruction.
Optionally, the data destination creating apparatus 300 of the rule engine further includes:
a third receiving module, configured to receive a data destination deleting instruction input by a user, where the data destination deleting instruction indicates to delete the first data destination;
a deletion module to delete the connection information of the first data destination from the rules of the rules engine in response to the data destination deletion instruction.
Optionally, the data destination creating apparatus 300 of the rule engine further includes:
a fourth receiving module, configured to receive a data sending instruction, where the data sending instruction instructs to send first data to the first data destination;
and the sending module is used for responding to the data sending instruction, establishing connection between the rule engine and the first data destination, and sending the first data to the first data destination.
Optionally, the first data destination is a rockmq data destination, and the connection information of the first data destination further includes Topic information of the rockmq data destination; the data send instruction indicates to send the first data to a target Topic of the RockettMQ data destination;
the sending module is specifically configured to:
responding to the data sending instruction, establishing connection between the rule engine and the RocktMQ data destination, adding the identification corresponding to the target Topic to the first data, and then sending the first data to the RocktMQ data destination.
The data destination creating apparatus 300 of the rule engine provided in the present application can implement each process in the above-described data destination creating method embodiment of the rule engine, and can achieve the same beneficial effects, and for avoiding repetition, details are not described here again.
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
As shown in fig. 4, it is a block diagram of an electronic device of a data destination creation method of a rule engine according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 4, the electronic apparatus includes: one or more processors 401, memory 402, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 4, one processor 401 is taken as an example.
Memory 402 is a non-transitory computer readable storage medium as provided herein. The memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method for creating a data destination for a rules engine provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to execute the data destination creation method of the rules engine provided by the present application.
The memory 402, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the data destination creation method of the rule engine in the embodiment of the present application (for example, the first receiving module 301, the testing module 302, and the first adding module 303 shown in fig. 3). The processor 401 executes various functional applications and data processing of the data destination creation means of the rule engine, that is, implements the data destination creation method of the rule engine in the above-described method embodiments, by running the non-transitory software programs, instructions, and modules stored in the memory 402.
The memory 402 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created by use of the electronic device according to the data destination creation method of the rule engine, and the like. Further, the memory 402 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 402 may optionally include memory located remotely from the processor 401, and these remote memories may be connected over a network to the electronic device of the rules engine's data destination creation method. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the data destination creation method of the rule engine may further include: an input device 403 and an output device 404. The processor 401, the memory 402, the input device 403 and the output device 404 may be connected by a bus or other means, and fig. 4 illustrates an example of a connection by a bus.
The input device 403 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device of the data destination creation method of the rules engine, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointing stick, one or more mouse buttons, a track ball, a joystick, or the like. The output devices 404 may include a display device, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), the internet, and blockchain networks.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The Server may be a cloud Server, which is also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service extensibility in the conventional physical host and Virtual Private Server (VPS) service.
According to the technical scheme of the embodiment of the application, the external data destination can be created for the rule engine, technical support is provided for data circulation between the rule engine and the external data destination, and the data circulation of the rule engine is not limited to the internal data destination.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (12)

1. A data destination creation method of a rules engine, comprising:
receiving a data destination establishing instruction input by a user; the data destination creation instruction comprises connection information of a first data destination, the connection information of the first data destination comprises a connection address of the first data destination, and the first data destination is an external data destination of the rule engine;
responding to the data destination creating instruction, and performing connectivity test on the first data destination according to the connection address of the first data destination;
if the connectivity test result indicates that the first data destination is available, adding connection information of the first data destination to a data destination list of the rules engine.
2. The method of claim 1, after the adding connection information for the first data destination to a data destination list of the rules engine, the method further comprising:
receiving a data destination selection instruction input by a user, wherein the data destination selection instruction indicates that the first data destination is selected;
in response to the data destination selection instruction, adding connection information for the first data destination to a rule of the rules engine.
3. The method of claim 2, after adding the connection information for the first data destination to the rules of the rules engine, the method further comprising:
receiving a data destination deleting instruction input by a user, wherein the data destination deleting instruction indicates that the first data destination is deleted;
in response to the data destination delete instruction, deleting the connection information for the first data destination from the rules of the rules engine.
4. The method of claim 2, after adding the connection information for the first data destination to the rules of the rules engine, the method further comprising:
receiving a data transmission instruction, the data transmission instruction instructing transmission of first data to the first data destination;
and responding to the data sending instruction, establishing connection between the rule engine and the first data destination, and sending the first data to the first data destination.
5. The method of claim 4, wherein the first data destination is a RockettMQ data destination, the connection information of the first data destination further comprising Topic information of the RockettMQ data destination; the data send instruction indicates to send the first data to a target Topic of the RockettMQ data destination;
the establishing a connection between the rule engine and the first data destination and sending the first data to the first data destination in response to the data sending instruction includes:
responding to the data sending instruction, establishing connection between the rule engine and the RocktMQ data destination, adding the identification corresponding to the target Topic to the first data, and then sending the first data to the RocktMQ data destination.
6. A data destination creation apparatus of a rules engine, comprising:
the first receiving module is used for receiving a data destination establishing instruction input by a user; the data destination creation instruction comprises connection information of a first data destination, the connection information of the first data destination comprises a connection address of the first data destination, and the first data destination is an external data destination of the rule engine;
the testing module is used for responding to the data destination establishing instruction and carrying out connectivity testing on the first data destination according to the connection address of the first data destination;
a first adding module, configured to add connection information of the first data destination to a data destination list of the rule engine if a connectivity test result indicates that the first data destination is available.
7. The apparatus of claim 6, further comprising:
a second receiving module, configured to receive a data destination selection instruction input by a user, where the data destination selection instruction indicates that the first data destination is selected;
a second adding module, configured to add the connection information of the first data destination to the rule of the rule engine in response to the data destination selection instruction.
8. The apparatus of claim 7, further comprising:
a third receiving module, configured to receive a data destination deleting instruction input by a user, where the data destination deleting instruction indicates to delete the first data destination;
a deletion module to delete the connection information of the first data destination from the rules of the rules engine in response to the data destination deletion instruction.
9. The apparatus of claim 7, further comprising:
a fourth receiving module, configured to receive a data sending instruction, where the data sending instruction instructs to send first data to the first data destination;
and the sending module is used for responding to the data sending instruction, establishing connection between the rule engine and the first data destination, and sending the first data to the first data destination.
10. The apparatus of claim 9, wherein the first data destination is a rockmq data destination, the connection information of the first data destination further comprising Topic information of the rockmq data destination; the data send instruction indicates to send the first data to a target Topic of the RockettMQ data destination;
the sending module is specifically configured to:
responding to the data sending instruction, establishing connection between the rule engine and the RocktMQ data destination, adding the identification corresponding to the target Topic to the first data, and then sending the first data to the RocktMQ data destination.
11. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 5.
12. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1 to 5.
CN202011383967.4A 2020-11-30 2020-11-30 Data destination creating method and device of rule engine, electronic equipment and storage medium Pending CN112583897A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011383967.4A CN112583897A (en) 2020-11-30 2020-11-30 Data destination creating method and device of rule engine, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011383967.4A CN112583897A (en) 2020-11-30 2020-11-30 Data destination creating method and device of rule engine, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112583897A true CN112583897A (en) 2021-03-30

Family

ID=75126708

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011383967.4A Pending CN112583897A (en) 2020-11-30 2020-11-30 Data destination creating method and device of rule engine, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112583897A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113824645A (en) * 2021-08-18 2021-12-21 北京百度网讯科技有限公司 Data transmission method, device, equipment and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101794295A (en) * 2010-01-06 2010-08-04 哈尔滨工程大学 Regular expression-oriented multi-mode matching hardware engine and generating method
US20140157244A1 (en) * 2009-06-17 2014-06-05 Phillip J. Windley Rule engine system controlling devices of disparate types and protocols
CN105630617A (en) * 2015-12-28 2016-06-01 山东中创软件工程股份有限公司 Business processing method and system based on rule engine
CN108270602A (en) * 2016-12-30 2018-07-10 中兴通讯股份有限公司 A kind of detection method of data link, apparatus and system
CN110471970A (en) * 2019-08-08 2019-11-19 紫光云技术有限公司 A kind of regulation engine data forwarding method that can flexibly match
CN110557304A (en) * 2019-09-20 2019-12-10 腾讯科技(深圳)有限公司 Address detection method and device and computer readable storage medium
CN110704049A (en) * 2019-10-09 2020-01-17 紫光云技术有限公司 Simple and easy-to-use rule engine condition configuration method

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140157244A1 (en) * 2009-06-17 2014-06-05 Phillip J. Windley Rule engine system controlling devices of disparate types and protocols
CN101794295A (en) * 2010-01-06 2010-08-04 哈尔滨工程大学 Regular expression-oriented multi-mode matching hardware engine and generating method
CN105630617A (en) * 2015-12-28 2016-06-01 山东中创软件工程股份有限公司 Business processing method and system based on rule engine
CN108270602A (en) * 2016-12-30 2018-07-10 中兴通讯股份有限公司 A kind of detection method of data link, apparatus and system
CN110471970A (en) * 2019-08-08 2019-11-19 紫光云技术有限公司 A kind of regulation engine data forwarding method that can flexibly match
CN110557304A (en) * 2019-09-20 2019-12-10 腾讯科技(深圳)有限公司 Address detection method and device and computer readable storage medium
CN110704049A (en) * 2019-10-09 2020-01-17 紫光云技术有限公司 Simple and easy-to-use rule engine condition configuration method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
阿里云: "设备消息通过RocketMQ流转到服务器_消息通信_最佳实践_阿里云物联网平台", 《阿里云技术文档》 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113824645A (en) * 2021-08-18 2021-12-21 北京百度网讯科技有限公司 Data transmission method, device, equipment and storage medium

Similar Documents

Publication Publication Date Title
CN111753997B (en) Distributed training method, system, device and storage medium
CN112181683A (en) Concurrent consumption method and device for message middleware
CN112102448A (en) Virtual object image display method and device, electronic equipment and storage medium
CN110619002A (en) Data processing method, device and storage medium
CN110750419B (en) Offline task processing method and device, electronic equipment and storage medium
CN112561332B (en) Model management method, device, electronic equipment, storage medium and program product
CN111625195A (en) Method and device for server capacity expansion
CN112540914A (en) Execution method, execution device, server and storage medium for unit test
CN111610972A (en) Page generation method, device, equipment and storage medium
CN112311597A (en) Message pushing method and device
CN111770176A (en) Traffic scheduling method and device
CN110765075A (en) Storage method and equipment of automatic driving data
CN112583897A (en) Data destination creating method and device of rule engine, electronic equipment and storage medium
CN111683140B (en) Method and apparatus for distributing messages
CN111767149A (en) Scheduling method, device, equipment and storage equipment
WO2023169193A1 (en) Method and device for generating smart contract
CN112532528A (en) Message routing method and device for rule engine
CN112486644A (en) Method, apparatus, device and storage medium for generating information
CN112395126A (en) Fault log processing method and device, electronic equipment and storage medium
CN112084000A (en) Container cluster testing method and device
JP2022078129A (en) Data labeling method, apparatus, electronic device, computer readable storage medium, and computer program
CN112887803B (en) Session processing method, device, storage medium and electronic equipment
CN112099933B (en) Task operation and query method and device, electronic equipment and storage medium
CN115277428A (en) Method and apparatus for configuring a network
CN112527635A (en) Fault injection method and device, electronic equipment and storage medium

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
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20210330