WO2019221234A1 - Dispositif de génération de logique de conversion, système d'exécution de procédé http, procédé d'exécution de procédé http et programme de génération de logique de conversion - Google Patents

Dispositif de génération de logique de conversion, système d'exécution de procédé http, procédé d'exécution de procédé http et programme de génération de logique de conversion Download PDF

Info

Publication number
WO2019221234A1
WO2019221234A1 PCT/JP2019/019511 JP2019019511W WO2019221234A1 WO 2019221234 A1 WO2019221234 A1 WO 2019221234A1 JP 2019019511 W JP2019019511 W JP 2019019511W WO 2019221234 A1 WO2019221234 A1 WO 2019221234A1
Authority
WO
WIPO (PCT)
Prior art keywords
processing
database
http method
command
conversion logic
Prior art date
Application number
PCT/JP2019/019511
Other languages
English (en)
Japanese (ja)
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 WO2019221234A1 publication Critical patent/WO2019221234A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2452—Query translation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9538—Presentation of query results
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication

Definitions

  • the present invention relates to a conversion logic generation device, an HTTP method execution system, an HTTP method execution method, and a conversion logic generation program that generate conversion logic data for converting an HTTP method received from an application execution device into a database command.
  • APIs Applications Programming Interfaces
  • APIs Applications Programming Interfaces
  • REST REpresentational State Transfer
  • the REST API uses HTTP (Hypertext Transfer Protocol), and each CRUD operation (C: Create, R: Read, U: Update, D: for a resource uniquely represented by a URI (Uniform Resource Identifier)) Delete) corresponds to HTTP POST / GET / PUT (PATCH) / DELETE.
  • HTTP Hypertext Transfer Protocol
  • Delete a resource representation of the REST API
  • a data format having a high affinity with web technologies such as JSON (JavaScript (registered trademark) Object Notation) and XML (Extensible Markup Language) is used.
  • JSON JavaScript (registered trademark) Object Notation
  • XML Extensible Markup Language
  • Patent Document 1 there is a method for operating the data managed by the DBM using an API.
  • the method described in Patent Document 1 converts a sequence and a REST including a protocol included in the DBM.
  • Patent Document 1 must use the API after knowing the correspondence between DBM and REST, and even web engineers who only want to use the DBM from the API have knowledge and know-how about the specifications of the DBM. It may be necessary to grasp and raise the barrier of API utilization.
  • Non-Patent Document 1 and Non-Patent Document 2 there are tools that replace operations on DBM with HTTP methods and the like (Non-Patent Document 1 and Non-Patent Document 2).
  • This tool converts a CRUD operation on the DBM into each HTTP method of REST, converts each table and view of the DBM into a URI, and converts a DBM record and attribute into a JSON or XML expression.
  • This tool if there is a DB managed by an existing DBM, it can be provided as an API without any special development, so web engineers can manage it without any special DBM knowledge or know-how. Data can be used.
  • CA "CA Live API Creator-3.1”, [online], [Search May 10, 2018], Internet ⁇ URL: https://docops.ca.com/ca-live-api-creator/3- 1 / en> Tomohiro Kada, “CA Live API Creator Product Description” [online], August 24, 2017, [May 10, 2018 search], Internet ⁇ URL: https://techplay.jp/slide/ 170422>
  • Patent Document 1 and Non-Patent Documents 1 and 2 describe a method for determining a processing type to be performed by synchronous processing or asynchronous processing.
  • an object of the present invention is to provide a conversion logic generation device, an HTTP method execution system, an HTTP method execution method, and a conversion logic generation program that can optimally select synchronous processing or asynchronous processing when creating an API from an HTTP method. That is.
  • a first feature of the present invention relates to a conversion logic generation apparatus that generates conversion logic data for converting an HTTP method received from an application execution apparatus into a database command.
  • the conversion logic generation device stores selection logic data in which a processing type indicating whether a command for a database table is performed in synchronous processing or asynchronous processing and a condition for applying the processing type are associated with each other A table, a command that matches the condition, and a processing type with reference to the selection logic data, an HTTP method corresponding to the specified command, a processing target of the HTTP method corresponding to the specified table, A conversion logic generation unit that outputs conversion logic data associated with the processing type of the identified command is provided.
  • the selection logic data may be associated with an asynchronous process as a process type for a condition that takes time to execute on the table.
  • the selection logic data may associate asynchronous processing as a processing type with a condition involving access to other tables in the database.
  • the selection logic data is data in which a command to the database and a processing type of the command for the table are associated with each table of the database
  • the conversion logic generation unit receives HTTP from the application execution device from the selection logic data.
  • a processing type is specified from the command corresponding to the method and the table corresponding to the processing target of the HTTP method, and the conversion logic data in which the HTTP method, the processing target of the HTTP method, and the processing type of the specified command are associated with each other is obtained. It may be output.
  • the second feature of the present invention is that a conversion logic generating device for generating conversion logic data for converting an HTTP method received from an application execution device into a command of a database, and an HTTP method based on the conversion logic data are stored in the database.
  • the present invention relates to an HTTP method execution system that includes an HTTP method execution device that converts and executes a command, and a database management device that manages a database.
  • the conversion logic generation device has a processing type indicating whether a command for a database table is executed in a synchronous process or an asynchronous process, and a condition for applying the process type
  • a storage device that stores selection logic data associated with each other, a table and a command that meet the conditions and a processing type are identified with reference to the selection logic data, an HTTP method that corresponds to the identified command, and the identified table
  • a conversion logic generation unit that outputs conversion logic data in which the processing target of the corresponding HTTP method is associated with the processing type of the specified command is provided.
  • the HTTP method execution device receives the HTTP method and the processing target from the application execution device.
  • App request that receives processing request including
  • the processing request and conversion logic data are referenced to convert the processing request into a database request for the database, and the command processing type is determined from the HTTP method included in the processing request and the processing target included in the processing request.
  • a conversion unit and a database request processing unit that processes a database request based on the processing type determined by the conversion unit are provided.
  • the database request processing unit transmits a database request to the database management device, and transmits a processing result received from the database management device to the application execution device.
  • a processing response including an inquiry URI that provides a processing result for the processing request is transmitted to the application execution device, and a database request is transmitted to the database management device, and database management is performed.
  • An asynchronous processing unit that holds the processing result received from the device in association with the inquiry URI may be provided.
  • a third feature of the present invention is that a conversion logic generation device that generates conversion logic data for converting an HTTP method received from an application execution device into a database command, and an HTTP method based on the conversion logic data are stored in the database.
  • the present invention relates to an HTTP method execution method used for an HTTP method execution system that includes an HTTP method execution device that converts and executes a command and a database management device that manages a database.
  • the HTTP method execution method includes a process type indicating whether the conversion logic generation device performs a command for a database table in a synchronous process or an asynchronous process, and a condition for applying the process type Storing the selection logic data associated with each other, the conversion logic generation device refers to the selection logic data, identifies the table and command that match the conditions, and the processing type, and the HTTP method corresponding to the identified command;
  • Receiving a processing request including:
  • the TTP method execution device refers to the conversion logic data, converts the processing request into a database request for the database, and determines the processing type of the command from the HTTP method included in the processing request and the processing target included in the processing request.
  • an HTTP method execution device includes a step of processing a database request based on the determined processing type.
  • the fourth feature of the present invention relates to a conversion logic generation program for causing a computer to function as the conversion logic generation device described in the first feature of the present invention.
  • a conversion logic generation device capable of optimally selecting synchronous processing or asynchronous processing when creating an API from an HTTP method. Can do.
  • the information processing system 9 includes an HTTP method execution system 5, an application development device 6, and an application execution device 7.
  • the HTTP method execution system 5, the application development device 6, and the application execution device 7 are connected to each other via a communication network 8 such as the Internet so as to be able to communicate with each other.
  • the application development device 6 generates an application using the API according to the embodiment of the present invention. Further, the application development apparatus 6 registers information related to the API used in the generated application in the HTTP method execution system 5.
  • the application execution device 7 executes the application generated by the application development device 6, uses the API to access the HTTP method execution system 5 in the application, requests processing, and receives the processing result from the HTTP method execution system 5. .
  • the HTTP method execution system 5 converts the API transmitted by the application execution device 7 into a command for accessing the data managed by the database management device 3, processes the data, and transmits the processing result to the application execution device 7. .
  • the HTTP method execution system 5 includes a conversion logic generation device 1, an HTTP method execution device 2, and a database management device 3.
  • the conversion logic generation device 1, the HTTP method execution device 2, and the database management device 3 are connected to each other via a communication network 4 such as a LAN (Local Area Network).
  • a communication network 4 such as a LAN (Local Area Network).
  • LAN Local Area Network
  • the conversion logic generation device 1 generates conversion logic data L for converting the HTTP method received from the application execution device 7 into a database command.
  • the conversion logic generation device 1 generates, based on the API-related information received from the application development device 6, the conversion logic data L converted into an HTTP method transmitted in advance by the application and a command for a database corresponding to the HTTP method.
  • the HTTP method execution device 2 When receiving the HTTP method processing request from the application execution device 7, the HTTP method execution device 2 accesses and processes the database with a command corresponding to the HTTP method based on the conversion logic data L, and executes the result. Transmit to device 7.
  • the database management device 3 is a DBM that manages data accessed by the application execution device 7.
  • the database management device 3 holds data in the form of a plurality of tables or views, and functions as an interface for accessing the data by SQL (Structured Query) Language.
  • the database management device 3 receives a database request (DB request) from the HTTP method execution device 2 and transmits a database response (DB response) including a processing result to the HTTP method execution device 2.
  • API means REST API.
  • an HTTP method that can be converted into an SQL command
  • a URI that identifies a table or view of the database management apparatus 3
  • a parameter in JSON format or query format that can identify an attribute of the table or view, and the like are specified.
  • the HTTP method execution system 5 determines a processing type indicating whether the API received from the application execution device 7 is to be performed synchronously or asynchronously in accordance with the conversion logic data L created in advance.
  • the HTTP method is executed with the determined processing type.
  • HTTP method execution method With reference to FIG. 2, the HTTP method execution method according to the embodiment of the present invention will be described.
  • step S1 the application execution device 7 transmits a processing request to the HTTP method execution device 2.
  • This processing request includes an HTTP method and a processing target.
  • This processing target is information for specifying data managed by the database management device 3.
  • the HTTP method execution device 2 acquires the conversion logic data L from the conversion logic generation device 1 in step S2.
  • the HTTP method execution device 2 may acquire the conversion logic data L in advance.
  • step S3 the HTTP method execution device 2 converts the processing request received from the application execution device 7 into a database request.
  • the database request includes a database command corresponding to the HTTP method included in the processing request and a processing target for specifying data in the database corresponding to the processing target included in the processing request.
  • step S4 the HTTP method execution device 2 specifies the processing type of the received processing request according to the conversion logic data L, and switches the processing according to the processing type specified in step S5.
  • the HTTP method execution device 2 transmits the database request converted in step S3 to the database management device 3 in step S11.
  • the database management device 3 processes the database request received in step S11, and transmits a database response including the processing result to the HTTP method execution device 2 in step S12.
  • the HTTP method execution device 2 converts the database response received in step S12 into a process response addressed to the application execution device 7.
  • step S ⁇ b> 13 the HTTP method execution device 2 transmits a processing response to the application execution device 7 as a response to the processing request received in step S ⁇ b> 1.
  • the HTTP method execution device 2 transmits a response in which the inquiry URI is set to the application execution device 7 as a response to the processing request received in step S1 in step S21.
  • the inquiry URI is used for the application execution device 7 to receive a processing result for the processing request transmitted in step S1.
  • the HTTP method execution device 2 transmits the database request converted in step S3 to the database management device 3 in step S22.
  • the database management device 3 processes the database request received in step S22, and transmits a database response including the processing result to the HTTP method execution device 2 in step S23.
  • the HTTP method execution device 2 stores the inquiry URI transmitted in step S21 and the processing result received in step S23 in association with each other.
  • the HTTP method execution device 2 displays the processing result associated with the received inquiry URI in step S26. To the application execution device 7. Although not shown, if the application execution device 7 transmits an inquiry request to the HTTP method execution device 2 before holding the processing result in step S24, the HTTP method execution device 2 indicates that the processing has not yet been completed. Return to the application execution device 7.
  • the conversion logic generation device 1 is a general computer including a storage device 10, a processing device 20, and a communication control device 30.
  • the functions shown in FIG. 3 are realized by a general computer executing the conversion logic generation program.
  • the storage device 10 is a read only memory (ROM), a random access memory (RAM), a hard disk or the like, and stores various data such as input data, output data, and intermediate data for the processing device 20 to execute processing.
  • the processing device 20 is a CPU (Central Processing Unit) that reads / writes data stored in the storage device 10 and inputs / outputs data to / from the communication control device 30 to perform processing in the conversion logic generation device 1.
  • the communication control device 30 is an interface for the conversion logic generation device 1 to be communicably connected to the HTTP method execution device 2 and the database management device 3.
  • the storage device 10 stores table structure data 11, selection logic data 12, and conversion logic data L.
  • the table structure data 11 is structure data of a table managed by the database management device 3.
  • the table structure data 11 is described in DDL (Database Definition Language).
  • the format of the table structure data 11 is shown in, for example, each (a) of FIGS. 10 to 12, but the format shown in these drawings is not necessary.
  • the selection logic data 12 is data in which a process type indicating whether a command for a database table managed by the database management apparatus 3 is performed in a synchronous process or an asynchronous process and a condition for applying the process type are associated with each other.
  • the selection logic data 12 is created in advance by an administrator of the HTTP method execution system 5 or the like.
  • the selection logic data 12 associates “asynchronous processing” as the processing type with the condition “it takes time to execute the table”.
  • the selection logic data 12 associates “asynchronous processing” as the processing type with the condition “with access to other tables in the database”.
  • the selection logic data 12 may associate “synchronization processing” as the default processing type for cases outside the specified conditions.
  • the selection logic data 12 may be data in which, for each table managed by the database management device 3, a command to the database is associated with a processing type of this command for this table.
  • the selection logic data 12 can specify the processing type for each command (INSERT, SELECT, UPDATE, and DELETE) for each table.
  • the conversion logic data L is data that the conversion logic generation device 1 according to the embodiment of the present invention outputs to the HTTP method execution device 2.
  • the conversion logic data L is data in which the HTTP method received from the application execution device 7, the processing target of the HTTP method, and the processing type of the command corresponding to the HTTP method are associated with each other.
  • the conversion logic data L includes a column related to an API received from an application and a column related to SQL for processing a database.
  • Each sub-item of the item related to API and each sub-item of the item related to SQL are associated with each other so that they can be converted to each other.
  • the items related to the API include the URI of the processing target specified by the API and the small items of parameters for specifying the attributes in the table.
  • the parameters include a format in which parameters included in the API are described in the JSON format and a format described in the query format.
  • the items related to SQL include the table name corresponding to the small item of the processing target URI of the item related to API, and each small item described in the database table of the attribute specified by the parameter small item.
  • the conversion logic data L has an HTTP method specified by the API in an item related to the API, and a database command corresponding to the HTTP method is associated in the item related to the SQL. As shown in FIG. 5, the relationship between the HTTP method specified by the API and the database command corresponding to each HTTP method is predetermined.
  • the conversion logic data L associates a processing type indicating whether a command for the table is performed by synchronous processing or asynchronous processing.
  • the HTTP method “GET” corresponds to the SQL command “SELECT” and is a synchronization process.
  • the HTTP method “POST” corresponds to the SQL command “INSERT” and is an asynchronous process.
  • the processing device 20 includes a table structure acquisition unit 21, a conversion logic generation unit 22, and a conversion logic provision unit 24.
  • the table structure acquisition unit 21 acquires the table structure data 11 for each table in the database used in the API processing and stores it in the storage device 10.
  • the application development apparatus 6 specifies the DBM IP address, port number, and the like, specifies the target database by the table structure acquisition unit 21, and sets the table structure data 11 for each table accommodated in the specified database. You may get
  • the conversion logic generation unit 22 generates conversion logic data L with reference to the table structure data 11 and the selection logic data 12.
  • the conversion logic generation unit 22 performs (1) conversion of an HTTP method and a command for manipulating DBM data, (2) conversion of a URI and DBM table or view specified by HTTP, and (3) HTTP, as in the past.
  • the parameter specified in (1) and the DBM attribute are converted.
  • the conversion logic generation unit 22 according to the embodiment of the present invention further includes (4) a processing type determination unit 23 that sets a processing type to be performed by synchronous processing or asynchronous processing.
  • the process type determination unit 23 refers to the selection logic data 12 and identifies a database table and command that match the conditions of the selection logic data 12 and the process type. In the conversion logic data L, the processing type determination unit 23 associates the HTTP method corresponding to the specified command, the processing target of the HTTP method corresponding to the specified table, and the processing type of the specified command. When determining the processing type according to the table structure, the processing type determination unit 23 also considers the table structure data 11. The processing type determination unit 23 refers to the table structure data 11 or other necessary data in order to determine whether or not the command for the database table satisfies the condition defined by the selection logic data 12. You may do it.
  • the process type determination unit 23 identifies a command and a table that require time to execute To do.
  • the processing type determination unit 23 updates the conversion logic data L by associating asynchronous processing as the processing type with the HTTP method corresponding to this command and the processing target for this table for the specified command and table.
  • the process type determining unit 23 executes the command for the table. Identify commands and tables to access other tables.
  • the processing type determination unit 23 updates the conversion logic data L by associating asynchronous processing as the processing type with the HTTP method corresponding to this command and the processing target for this table for the specified command and table.
  • the processing type determination unit 23 determines from the selection logic data 12, The processing type is specified from the command corresponding to the HTTP method received from the application execution apparatus 7 and the table corresponding to the processing target of the HTTP method.
  • the process type determination unit 23 outputs conversion logic data L in which the specified HTTP method, the processing target of the specified HTTP method, and the process type of the specified command are associated with each other.
  • the process type determination unit 23 refers to the selection logic data 12 and associates the conversion logic data L with the HTTP method and the process target corresponding to the command and the table by associating the asynchronous process or the synchronous process as the process type. Update.
  • the process type determination unit 23 assigns a synchronous process in principle, and an asynchronous process is exceptionally assigned to a command that takes a long time to process. Thereby, even when the application developer does not have knowledge of DBM, the application execution device 7 can avoid a situation in which a timeout occurs in the application and appropriately acquire the result.
  • the conversion logic providing unit 24 transmits the conversion logic data L generated by the conversion logic generation unit 22 to the HTTP method execution device 2.
  • the conversion logic providing unit 24 may transmit the conversion logic data L to the HTTP method execution device 2 when the conversion logic data L is generated, or transmit it to the HTTP method execution device 2 when there is a request from the HTTP method execution device 2. May be.
  • step S101 the conversion logic generation unit 22 associates an HTTP method to be converted with a DB command.
  • step S102 the conversion logic generation unit 22 associates the processing target transmitted from the application with the DB table and attribute.
  • the processes in steps S101 and S102 are performed in the same manner as in the past using the table shown in FIG.
  • step S103 the conversion logic generation unit 22 determines whether each table and database command corresponding to the processing target specified by the API is performed in a synchronous process or an asynchronous process according to the selection logic data 12. Specify the processing type to be shown. Alternatively, the conversion logic generation unit 22 may specify a table and a command to be executed by asynchronous processing according to the selection logic data 12, and may specify each processing type when the other table and command are executed by asynchronous processing.
  • step S104 the conversion logic generation unit 22 generates the conversion logic data L based on the processing results in steps S101 to S103.
  • the conversion logic generation unit 22 sets the processing type when executing the command corresponding to the HTTP method for the table and the attribute corresponding to the processing target for the HTTP method and the processing target.
  • the conversion logic data L is generated in association with the processing type specified in S103.
  • the HTTP method execution device 2 is a general computer including a storage device 50, a processing device 60, and a communication control device 70.
  • a general computer executes the HTTP method execution program to realize the functions shown in FIG.
  • the storage device 50 is a read only memory (ROM), a random access memory (RAM), a hard disk, and the like, and stores various data such as input data, output data, and intermediate data for the processing device 60 to execute processing.
  • the processing device 60 is a CPU (Central Processing Unit) and reads / writes data stored in the storage device 50 and inputs / outputs data to / from the communication control device 70 to perform processing in the HTTP method execution device 2.
  • the communication control device 70 is an interface for allowing the HTTP method execution device 2 to connect to the conversion logic generation device 1 and the database management device 3 so that they can communicate with each other.
  • Storage device 50 stores conversion logic data L and processing result data 51.
  • the conversion logic data L is data generated by the conversion logic generation device 1 and described with reference to FIG.
  • the processing result data 51 holds the processing result when the asynchronous processing is performed on the database. As shown in FIG. 8, the processing result data 51 holds an inquiry URI assigned to the asynchronous processing performed on the database in association with the identifier (link) of the processing result of the asynchronous processing.
  • the processing device 60 includes a conversion logic acquisition unit 61, an application request processing unit 62, a conversion unit 63, and a database request processing unit 64.
  • the conversion logic acquisition unit 61 acquires the conversion logic data L from the conversion logic generation device 1 and stores it in the storage device 50.
  • the conversion logic acquisition unit 61 may acquire the conversion logic data L when receiving a processing request from the application execution device 7 or may acquire the conversion logic data L in advance.
  • the application request processing unit 62 receives a request including an HTTP method and a processing target from the application execution device 7. The application request processing unit 62 further returns the processing request processing result to the application execution device 7.
  • the conversion unit 63 refers to the conversion logic data L, converts the processing request into a database request for the database, and determines the processing type of the command from the HTTP method included in the processing request and the processing target included in the processing request. To do.
  • the conversion unit 63 converts the HTTP method specified in the processing request into a database command, and converts the processing target specified in the processing request into an attribute of a database table. Furthermore, the conversion unit 63 specifies a processing type indicating whether to perform synchronous processing or asynchronous processing on the HTTP method and processing target specified in the processing request.
  • the database request processing unit 64 processes the database request converted by the conversion unit 63 based on the processing type determined by the conversion unit 63.
  • the database request processing unit 64 includes a synchronous processing unit 65 that accesses the database by synchronous processing, and an asynchronous processing unit 66 that accesses the database by asynchronous processing.
  • the synchronization processing unit 65 immediately processes the database request and returns it to the application execution device 7. Specifically, when the processing type determined by the conversion unit 63 is synchronous processing, the synchronization processing unit 65 transmits a database request to the database management device 3 and transmits a processing result received from the database management device to the application execution device 7. To do.
  • the asynchronous processing unit 66 creates an inquiry URI and returns it to the application execution device 7 without processing the database request immediately, and processes the database request. Specifically, when the processing type determined by the conversion unit 63 is asynchronous processing, the asynchronous processing unit 66 transmits a processing response including an inquiry URI that provides a processing result for the processing request to the application execution device 7. In addition, the synchronization processing unit 65 transmits a database request to the database management device 3 and stores the processing result received from the database management device 3 in the processing result data 51 in association with the inquiry URI.
  • the asynchronous processing unit 66 When the asynchronous processing unit 66 receives an inquiry request including an inquiry URI from the application execution device 7 before holding the processing result received from the database management device 3 in the processing result data 51, the asynchronous processing unit 66 indicates that the processing is incomplete. Return to execution device 7. On the other hand, when the asynchronous processing unit 66 holds the processing result received from the database management device 3 in the processing result data 51 and then receives an inquiry request including the inquiry URI from the application execution device 7, the asynchronous processing unit 66 sends the processing result to the application execution device 7. return.
  • the conversion logic generation device 1 asynchronously processes the command for the condition “with access to other tables in the database”. An example of determining that will be described.
  • FIG. 9 is an example of a customer table T1, a product table T2, and an order list table T3 managed by the database management apparatus 3.
  • the “customer address” in the order list table T3 has a relationship with the “customer ID” in the customer table T1
  • the “product name” in the order list table T3 has a relationship with the “product ID” in the product table T2. .
  • the table structure data of the customer table T1 is shown in FIG. 10 (a), and the correspondence between the notation in the table structure data and the notation in FIG. 9 is shown in FIG. 10 (b).
  • the table structure data is shown in FIG. 11A and FIG. 12A, and the correspondence between the notation in the table structure data and the notation in FIG. It is shown in b) and FIG.
  • the table structure data of the order name list table T3 shown in FIG. 12A indicates that “customer address (customer_address)” and “product name (product_name)” are “FOREIGN KEY”. Each item indicates that “customer_id” and “product_id” in another table are referred to.
  • the process type determination unit 23 determines that the HTTP method POST and PUT corresponding to INSERT and UPDATE are to be performed asynchronously for the order name list table T3 shown in FIG.
  • the processing type determination unit 23 determines that the HTTP method GET and DELETE corresponding to the commands other than INSERT and UPDATE are to be performed in a synchronous process with respect to the order name list table T3 shown in FIG.
  • the selection logic data 12 described here is an example, and the present invention is not limited to this.
  • the selection logic data 12 it may be set that asynchronous processing is performed for the condition “with access to two or more other tables in the database”.
  • the condition of “command for a table having a predetermined number of records or more” may be set to be asynchronous processing.
  • the conversion logic generation device 1 corresponds to the selection logic data 12 in advance with a table and a processing type indicating whether a command for the table is an asynchronous process or a synchronous process. Put it on. Since the conversion logic generation device 1 outputs the conversion logic data L in which the processing type is associated with the HTTP method and the processing target based on the selection logic data 12, the HTTP method execution device 2 receives the API from the HTTP method. When creating, synchronous processing or asynchronous processing can be optimally selected. As a result, the developer of the application that transmits the API does not need to set the processing type of the synchronous process or the asynchronous process for the API command, and therefore specifies the processing type of the API command even if the database mechanism is not well known. be able to. In addition, since the processing type can be set appropriately, the application execution device 7 can acquire the result without causing a shortage such as a timeout occurring in the application.
  • the conversion logic generation device described in the embodiment of the present invention may be configured on one piece of hardware as shown in FIG. 3, or on a plurality of pieces of hardware according to the functions and the number of processes. It may be configured. Moreover, you may implement

Abstract

L'invention concerne un dispositif de génération de logique de conversion 1 comprenant : un dispositif de stockage 10 destiné à stocker des données de logique de sélection 12 dans lesquelles une classification de processus indiquant s'il faut effectuer une commande par rapport à une table de base de données avec un processus synchrone ou un processus asynchrone est associée à une condition pour appliquer la classification de processus ; et une partie de génération de logique de conversion 22 pour se référer aux données de logique de sélection 12, identifier la table, la commande et la classification de processus qui satisfont la condition, et délivrer en sortie des données de logique de conversion L dans lesquelles un procédé HTTP correspondant à la commande identifiée et un sujet pour un traitement par le procédé HTTP correspondant à la table identifiée sont associés à la classification de processus de la commande identifiée.
PCT/JP2019/019511 2018-05-18 2019-05-16 Dispositif de génération de logique de conversion, système d'exécution de procédé http, procédé d'exécution de procédé http et programme de génération de logique de conversion WO2019221234A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2018-096100 2018-05-18
JP2018096100A JP2019200691A (ja) 2018-05-18 2018-05-18 変換ロジック生成装置、ｈｔｔｐメソッド実行システム、ｈｔｔｐメソッド実行方法および変換ロジック生成プログラム

Publications (1)

Publication Number Publication Date
WO2019221234A1 true WO2019221234A1 (fr) 2019-11-21

Family

ID=68540393

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/019511 WO2019221234A1 (fr) 2018-05-18 2019-05-16 Dispositif de génération de logique de conversion, système d'exécution de procédé http, procédé d'exécution de procédé http et programme de génération de logique de conversion

Country Status (2)

Country Link
JP (1) JP2019200691A (fr)
WO (1) WO2019221234A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011232893A (ja) * 2010-04-26 2011-11-17 Canon Inc 印刷データ作成サーバ及び印刷装置及び印刷システム
WO2015145762A1 (fr) * 2014-03-28 2015-10-01 株式会社日立製作所 Système de gestion de base de données, ordinateur et procédé de gestion de base de données

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011232893A (ja) * 2010-04-26 2011-11-17 Canon Inc 印刷データ作成サーバ及び印刷装置及び印刷システム
WO2015145762A1 (fr) * 2014-03-28 2015-10-01 株式会社日立製作所 Système de gestion de base de données, ordinateur et procédé de gestion de base de données

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KAWAMURA, KOJI ET AL.: "NoSQL guide for RDB engineers", SHUWA SYSTEM CO., LTD, 24 February 2016 (2016-02-24), pages 358 - 364 *

Also Published As

Publication number Publication date
JP2019200691A (ja) 2019-11-21

Similar Documents

Publication Publication Date Title
CN108628661B (zh) 云制造服务的自动建置方法、云制造系统
EP3709227B1 (fr) Système et procédé de communication interopérable d'un composant de système d'automatisation avec de multiples sources d'informations
JP6065008B2 (ja) 制御装置
JP6016808B2 (ja) Ｗｅｂアクセスを実装するための方法およびサーバシステム
CN112367211B (zh) 一种设备命令行生成配置模板方法、装置及存储介质
JP2011165148A (ja) データストア切替装置、データストア切替方法およびデータストア切替プログラム
CN112286628B (zh) 一种统一纳管Kubernetes异构应用的系统及运行方法
CN103390018A (zh) 一种基于SDD的Web服务数据建模与搜索方法
CN102255969B (zh) 一种基于表述性状态转移的网络服务安全模型
CN104461893B (zh) 数据处理方法与数据处理装置
US20190205436A1 (en) System and method for executing database operations on a database
CN104572638B (zh) 数据读写方法及装置
WO2019221234A1 (fr) Dispositif de génération de logique de conversion, système d'exécution de procédé http, procédé d'exécution de procédé http et programme de génération de logique de conversion
JP4522413B2 (ja) リソース管理プログラム、リソース管理方法、およびリソース管理装置
Athanasopoulos et al. Service substitution revisited
JP4529766B2 (ja) 情報提供システム、情報提供方法、サーバ及び情報提供プログラム
KR20210122212A (ko) 이더리움 가상머신의 트랜잭션 처리 방법, 장치, 설비, 프로그램 및 매체
KR101270746B1 (ko) 웹 서비스 중개 장치 및 방법
JP5351746B2 (ja) データ処理装置及び方法
Kanagasundaram et al. Exposing resources as web services: A performance oriented approach
CN111124923B (zh) 运行状态查询方法、装置、服务器设备及存储介质
JP2003263375A (ja) データサーバ
WO2022230429A1 (fr) Système de commande, procédé de fourniture de données et programme de traitement de relais
US20170185684A1 (en) Generation of complementary applicatons
JP5589726B2 (ja) ジョブ管理システム、ジョブ管理システム制御方法およびその制御用プログラム

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: 19804109

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: 19804109

Country of ref document: EP

Kind code of ref document: A1