Accessing and editing virtually-indexed message flows using structured query langauge (SQL)

US10133766B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10133766-B2
Application numberUS-201615167331-A
CountryUS
Kind codeB2
Filing dateMay 27, 2016
Priority dateSep 23, 2011
Publication dateNov 20, 2018
Grant dateNov 20, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

At least one message flow file that stores a message flow is read by a processor. The message flow stored within the at least one message flow file is parsed. The message flow is organized within a memory as a message flow database structure. Entries within the message flow database structure represent nodes, connections, and properties used by the message flow. The message flow database structure is edited in response to receipt of a structured query language (SQL) statement that specifies a change to the message flow database structure.

First claim

Opening claim text (preview).

What is claimed is: 1. A method, comprising: reading, via a processor, at least one message flow file that stores a message flow; parsing the message flow stored within the at least one message flow file to obtain parsed message flow information; organizing the message flow, based at least in part upon the parsed message flow information, within a memory as a message flow database structure, where in-memory entries within the message flow database structure represent nodes, connections, and properties used by the message flow; and editing the message flow database structure by changing at least one of the in-memory entries in response to receipt of a structured query language (SQL) statement that specifies an SQL command to execute to change the message flow database structure within the memory; where the parsing and organizing of the message flow file into the message flow database structure within the memory allows localized in-memory SQL editing of the message flow without requiring runtime load operations to load the message flow database structure into a database and thereby improves real-time message flow editing technology while additionally reducing resource utilization. 2. The method of claim 1 , where editing the message flow database structure by changing the at least one of the in-memory entries in response to receipt of the SQL statement that specifies the SQL command to execute to change the message flow database structure comprises invoking a database connectivity driver to process the SQL command to edit the message flow database structure within the memory. 3. The method of claim 2 , where the database connectivity driver comprises a virtual database driver. 4. The method of claim 1 , where editing the message flow database structure by changing the at least one of the in-memory entries in response to receipt of the SQL statement that specifies the SQL command to execute to change the message flow database structure comprises: detecting user entry of the SQL statement that comprises the SQL command to execute to change the message flow database structure via one of a command-line user interface and a graphical user interface (GUI); and processing the SQL statement against the message flow database structure within the memory in response to detection of the user entry of the SQL statement that comprises the SQL command to execute to change the message flow database structure to edit the message flow database structure within the memory according to the SQL command. 5. The method of claim 1 , where the SQL command comprises one of an SQL UPDATE command and an SQL INSERT command, and where editing the message flow database structure by changing the at least one of the in-memory entries in response to receipt of the SQL statement that specifies the SQL command to execute to change the message flow database structure comprises: modifying, within the memory, at least one of a represented node, connection, and property within a table that organizes the message flow database structure within the memory in response to the SQL statement comprising the SQL UPDATE command; and adding, within the memory, at least one message flow object to the message flow database structure within the memory in response to the SQL statement comprising the SQL INSERT command. 6. The method of claim 1 , further comprising one of: deploying the edited message flow database structure as a runtime message flow within a message broker runtime environment; and storing, within the memory, the edited message flow database structure to at least one new message flow file in a format usable as a runtime message flow within a message broker runtime environment. 7. The method of claim 1 , where: reading, via the processor, the at least one message flow file that stores the message flow comprises reading, via the processor, the at least one message flow file from a message broker runtime environment where the message flow is deployed; and editing the message flow database structure by changing the at least one of the in-memory entries in response to receipt of the SQL statement that specifies the SQL command to execute to change the message flow database structure comprises processing the SQL statement against the message flow deployed within the message broker runtime environment to edit the deployed message flow according to the SQL command during runtime message processing. 8. A system, comprising: a memory; and a processor programmed to: read at least one message flow file that stores a message flow; parse the message flow stored within the message flow file to obtain parsed message flow information; organize the message flow, based at least in part upon the parsed message flow information, within the memory as a message flow database structure, where in-memory entries within the message flow database structure represent nodes, connections, and properties used by the message flow; and edit the message flow database structure by changing at least one of the in-memory entries in response to receipt of a structured query language (SQL) statement that specifies an SQL command to execute to change the message flow database structure within the memory; where the parsing and organizing of the message flow file into the message flow database structure within the memory allows localized in-memory SQL editing of the message flow without requiring runtime load operations to load the message flow database structure into a database and thereby improves real-time message flow editing technology while additionally reducing resource utilization. 9. The system of claim 8 , where in being programmed to edit the message flow database structure by changing the at least one of the in-memory entries in response to receipt of the SQL statement that specifies the SQL command to execute to change the message flow database structure, the processor is programmed to invoke a database connectivity driver to process the SQL command to edit the message flow database structure within the memory, where the database connectivity driver comprises a virtual database driver. 10. The system of claim 8 , where in being programmed to edit the message flow database structure by changing the at least one of the in-memory entries in response to receipt of the SQL statement that specifies the SQL command to execute to change the message flow database structure, the processor is programmed to: detect user entry of the SQL statement that comprises the SQL command to execute to change the message flow database structure via one of a command-line user interface and a graphical user interface (GUI); and process the SQL statement against the message flow database structure within the memory in response to detection of the user entry of the SQL statement that comprises the SQL command to execute to change the message flow database structure to edit the message flow database structure within the memory according to the SQL command. 11. The system of claim 8 , where the SQL command comprises one of an SQL UPDATE command and an SQL INSERT command, and where in being programmed to edit the message flow database structure by changing the at least one of the in-memory entries in response to receipt of the SQL statement that specifies the SQL command to execute to change the message flow database structure, the processor is programmed to: modify, within the memory, at least one of a represented node, connection, and property within a table that organizes the message flow database within the memory in response to the SQL statement comprising the SQL UPDATE command; and add, within the memory, at least one message flow object to the message flow database st

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10133766B2 cover?
At least one message flow file that stores a message flow is read by a processor. The message flow stored within the at least one message flow file is parsed. The message flow is organized within a memory as a message flow database structure. Entries within the message flow database structure represent nodes, connections, and properties used by the message flow. The message flow database struct…
Who is the assignee on this patent?
IBM
What technology area does this patent fall under?
Primary CPC classification G06F17/30345. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Nov 20 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).