Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for a message queuing application to access a specific application programming interface (API) service, comprising: responsive to an API bridge service detecting a request message placed in a request queue of a message queuing network by a message queuing application, retrieving, by the API bridge service, the request message from the request queue, wherein the request message comprises a generic API message request, wherein the generic API message request comprises an API service request in a message queue format independent of any specific API specification; formatting, by the API bridge service, the generic API message request in the request message into a particular API call for at least one specific API; calling, by the API bridge service, the at least one specific API with the particular API call; responsive to the API bridge service receiving at least one API specific response from the at least one specific API, formatting, by the API bridge service, the at least one API specific response into a response message comprising a generic API response; and placing, by the API bridge service, the response message in a response queue of the message queuing network, wherein the message queuing application listens to the response queue for the response message and retrieves the response message to receive a specific API service from the at least one specific API without calling the at least one specific API.
A method enables a message queue application to use external APIs without directly calling them. An API bridge service monitors a request queue for new messages from the application. When a message containing a generic API request (independent of specific API formats) is detected, the bridge service retrieves it. The service then reformats this generic request into a specific API call and executes that call. After receiving a response from the external API, the bridge service translates the API-specific response into a generic response message and places it in a response queue. The message queue application monitors this queue, retrieves the generic response, and processes it, effectively using the external API without direct integration.
2. The method of claim 1 , wherein responsive to an API bridge service detecting a request message placed in a request queue of a message queuing network by a message queuing application, retrieving, by the API bridge service, the request message from the request queue, wherein the request message comprises a generic API message request further comprises: listening, by the API bridge service, to the request queue for the request message placed in the request queue by the message queuing application, wherein the generic API message request of the request message comprises a structured data message specified by API request definitions for the API bridge service, wherein the API request definitions specify a format independent of any particular API from among a plurality of APIs callable by the API bridge service, wherein the structured data message comprises a structured data message format comprising an extensible markup cage (XML) format.
In the method where a message queue application accesses a specific API service, involving an API bridge service detecting and retrieving a generic API request message from a request queue, the API bridge service listens to the request queue for messages from the queuing application. The generic API request is a structured data message, conforming to API request definitions that are independent of any specific API. This structure could be based on XML. The API bridge service then transforms this structured, API-agnostic request into a specific API call understood by the intended external service.
3. The method of claim 1 , wherein responsive to an API bridge service detecting a request message placed in a request queue of a message queuing network by a message queuing application, retrieving, by the API bridge service, the request message from the request queue, wherein the request message comprises a generic API message request further comprises: listening, by the API bridge service, to the request queue for the request message placed in the request queue by the message queuing application, wherein the generic API message request of the request message is not a call to invoke a specific API from among a plurality of APIs callable by the API bridge service.
In the method where a message queue application accesses a specific API service, involving an API bridge service detecting and retrieving a generic API request message from a request queue, the API bridge service listens to the request queue for messages from the queuing application. The generic API request is not a direct call to any specific API the bridge service is capable of using. Instead, it is an abstract request handled by the bridge to determine the appropriate specific API call.
4. The method of claim 1 , further comprising: listening, by the API bridge service, to the request queue for the request message placed in the request queue by calling a message queue API of the message queuing network.
The method where a message queue application accesses a specific API service, involving an API bridge service detecting and retrieving a generic API request message from a request queue, also includes the API bridge service actively listening to the request queue for new messages. This listening action is performed by invoking a message queue API provided by the message queuing network.
5. The method of claim 1 , further comprising: listening, by the message queuing application, to the response queue asynchronously from placement, by the message queuing application, of the request message in the request queue; and responsive to the message queuing application detecting the response message placed in the response queue, retrieving, by the message queuing application, the response message from the response queue.
The method where a message queue application accesses a specific API service involves the queuing application asynchronously monitoring the response queue after placing a request. This means the application doesn't wait for an immediate response. When the application detects a new message in the response queue, it retrieves the message containing the API response.
6. The method of claim 1 , further comprising: responsive to the message queuing application requiring the specific API service, building, by the message queuing application, the request message with the generic API message request for the specific API service according to at least one API request definition specified by the API bridge service; requesting, by the message queuing application, placement of the request message in the API request queue by calling a message queue API of the message queuing network; calling, by the message queuing application, the message queue API of the message queuing network to open a listener on the response queue; responsive to the listener detecting the response message on the response queue, retrieving, by the message queuing application, the response message from the response queue for the message queuing application; and processing, by the message queuing application, the response message.
In the method where a message queue application accesses a specific API service, when the queuing application requires a specific API service, it builds a generic API request message based on API request definitions provided by the API bridge service. It then sends this request to the request queue via the message queuing network's API. The application also uses the message queue API to open a listener on the response queue. Once a response is detected, the application retrieves it and processes the contained information.
7. A system for a message queuing application to access a specific application programming interface (API) service, comprising: an API bridge service, comprising at least one processor and a memory, responsive to an API bridge service detecting a request message placed in a request queue of a message queuing network by a message queuing application, operative to retrieve, the request message from the request queue, wherein the request message comprises a generic API message request, wherein the generic API message request comprises an API service request in a message queue format independent of any specific API specification; the API bridge service operative to format the generic API message request in the request message into a particular API call for at least one specific API; the API bridge service operative to call the at least one specific API with the particular API call; the API bridge service, responsive to the API bridge service receiving at least one API specific response from at least one specific API, operative to translate the at least one API specific response into a response message comprising a generic API response; and the API bridge service operative to place the response message in a response queue of the message queuing network, wherein the message queuing application listens to the response queue for the response message and retrieves the response message to receive a specific API service from the at least one specific API without calling the at least one specific API.
A system enables a message queue application to use external APIs without direct calls. It includes an API bridge service (processor and memory) that monitors a request queue for generic API requests from the application. Upon detecting a request, the bridge service retrieves and reformats it into a specific API call, then executes that call. When the external API responds, the bridge service translates the response into a generic response message and places it in a response queue. The message queue application monitors the response queue, retrieves the generic response, and processes it, effectively using the external API without direct integration.
8. The system of claim 7 , wherein the API bridge service, responsive to an API bridge service detecting a request message placed in a request queue of a message queuing network by a message queuing application, operative to retrieve the request message from the request queue, wherein the request message comprises a generic API message request further comprises: the API bridge service operative to listen to the request queue for the request message placed in the request queue by the message queuing application, wherein the generic API message request of the request message comprises a structured data message specified by API request definitions for the API bridge service, wherein the API request definitions specify a format independent of any particular API from among a plurality of APIs callable by the API bridge service, wherein the structured data message comprises a structured data message format comprising an extensible markup cage (XML) format.
In the system where a message queue application accesses a specific API service, involving an API bridge service detecting and retrieving a generic API request message from a request queue, the API bridge service actively listens to the request queue. The generic API request from the application is a structured data message, defined by API request definitions that are API-agnostic. These definitions are not specific to any one API but allow the bridge service to translate the generic request. The structured data message might use XML format.
9. The system of claim 7 , wherein the API bridge service, responsive to detecting a request message placed in a request queue of a message queuing network by a message queuing application, operative to retrieve the request message from the request queue, wherein the request message comprises a generic API message request further comprises: the API bridge service operative to listen to the request queue for the request message placed in the request queue by the message queuing application, wherein the generic API message request of the request message is not a call to invoke a specific API from among a plurality of APIs callable by the API bridge service.
In the system where a message queue application accesses a specific API service, involving an API bridge service detecting and retrieving a generic API request message from a request queue, the generic API request from the application is not a direct invocation of any specific API the bridge service could use. It is instead a generalized instruction requiring interpretation by the bridge service.
10. The system of claim 7 , further comprising: the API bridge service operative to listen to the request queue for the request message placed in the request queue by calling a message queue API of the message queuing network.
The system where a message queue application accesses a specific API service, involving an API bridge service detecting and retrieving a generic API request message from a request queue, also includes the API bridge service listening to the request queue by calling a message queue API of the message queuing network.
11. The system of claim 7 , further comprising: the message queuing application operative to listen to the response queue asynchronously from placement, by the message queuing application, of the request message in the request queue; and the message queuing application, responsive to detecting the response message placed in the response queue, operative to retrieve the response message from the response queue.
In the system where a message queue application accesses a specific API service, the message queuing application monitors the response queue asynchronously after sending a request. When a new message is detected, it is retrieved.
12. The system of claim 7 , further comprising: the message queuing application, responsive to the message queuing application requiring the specific API service, operative to build the request message with the generic API message request for the specific API service according to at least one API request definition specified by the API bridge service; the message queuing application operative to request placement of the request message in the API request queue by calling a message queue API of the message queuing network; the message queuing application operative to call the message queue API of the message queuing network to open a listener on the response queue; the message queuing application, responsive to the listener detecting the response message on the response queue, operative to retrieve the response message from the response queue for the message queuing application; and the message queuing application operative to process the response message.
In the system where a message queue application accesses a specific API service, when a specific API service is needed, the message queuing application constructs a generic API request based on definitions provided by the API bridge service. It then places this request on the request queue using the message queue API. The application also opens a listener on the response queue using the message queue API. When a response arrives, it is retrieved and processed by the application.
13. A computer program product for a message queuing application to access a specific application programming interface (API) service, comprising: one or more computer-readable, tangible storage devices; program instructions, stored on at least one of the one or more storage devices, responsive to an API bridge service detecting a request message placed in a request queue of a message queuing network by a message queuing application, to retrieve, by the API bridge service, the request message from the request queue, wherein the request message comprises a generic API message request, wherein the generic API message request comprises an API service request in a message queue format independent of any specific API specification; program instructions, stored on at least one of the one or more storage devices to format, by the API bridge service, the generic API message request in the request message into a particular API call for at least one specific API; program instructions, stored on at least one of the one or more storage device to call, by the API bridge service, the at least one specific API with the particular API call; program instructions, stored on at least one of the one or more storage devices, responsive to the API bridge service receiving at least one API specific response from the at least one specific API, to translate, by the API bridge service, the at least one API specific response into a response message comprising a generic API response; and program instructions, stored on at least one of the one or more storage devices, to place, by the API bridge service, the response message in a response queue of the message queuing network, wherein the message queuing application listens to the response queue for the response message and retrieves the response message to receive a specific API service from the at least one specific API without calling the at least one specific API.
A computer program product allows a message queuing application to access external APIs. Instructions are stored on computer-readable media to perform the following: When an API bridge service detects a request in the queue (placed by a message queuing application), it retrieves that request. The request contains a generic API message that is independent of any specific API. The instructions then format this generic request into a specific API call and initiate it. Upon receiving a response, the instructions translate it into a generic response message. Finally, the generic response is placed in a response queue for the queuing application to retrieve.
14. The computer program product of claim 13 , further comprising: program instructions, stored on at least one of the one or more storage devices, to listen, by the API bridge service, to the request queue for the request message placed in the request queue by the message queuing application, wherein the generic API message request of the request message comprises a structured data message specified by API request definitions for the API bridge service, wherein the API request definitions specify a format independent of any particular API from among a plurality of APIs callable by the API bridge service, wherein the structured data message comprises a structured data message format comprising an extensible markup language (XML) format.
The computer program product where a message queue application accesses a specific API service, where the API bridge service detects and retrieves a generic API request from the queue, also includes instructions for the API bridge to listen to the queue. The request message contains a generic API request with structured data specified by API request definitions. These definitions are independent of specific APIs and potentially use XML format.
15. The computer program product of claim 13 , further comprising: program instructions, stored on at least one of the one or more storage devices, to listen, by the API bridge service, to the request queue for the request message placed in the request queue by the message queuing application, wherein the generic API message request of the request message is not a call to invoke a specific API from among a plurality of APIs callable by the API bridge service.
The computer program product where a message queue application accesses a specific API service, where the API bridge service detects and retrieves a generic API request from the queue, includes program instructions to listen to the request queue, wherein the generic API request isn't a direct call to any API accessible via the bridge service.
16. The computer program product of claim 15 , further comprising: program instructions, stored on at least one of the one or more storage devices, to listen, by the API bridge service, to the request queue for the request message placed in the request queue by calling a message queue API of the message queuing network.
The computer program product that includes instructions for the API bridge service to listen to the request queue from the previous claim also includes instructions to utilize a message queue API provided by the queuing network for the listening process.
17. The computer program product of claim 15 , further comprising: program instructions, stored on at least one of the one or more storage devices, to listen, by the message queuing application, to the response queue asynchronously from placement, by the message queuing application, of the request message in the request queue; and program instructions, stored on at least one of the one or more storage devices, responsive to the message queuing application detecting the response message placed in the response queue, to retrieve, by the message queuing application, the response message from the response queue.
The computer program product where a message queue application accesses a specific API service and where the generic API request isn't a direct call to any API accessible via the bridge service includes instructions to listen asynchronously and retrieve the response by the message queuing application.
18. The computer program product of claim 15 , further comprising: program instructions, stored on at least one of the one or more storage devices, responsive to the message queuing application requiring the specific API service, to build, by the message queuing application, the request message with the generic API message request for the specific API service according to at least one API request definition specified by the API bridge service; program instructions, stored on at least one of the one or more storage devices, to request, by the message queuing application, placement of the request message in the API request queue by calling a message queue API of the message queuing network; program instructions, stored on at least one of the one or more storage devices, to call, by the message queuing application, the message queue API of the message queuing network to open a listener on the response queue; program instructions, stored on at least one of the one or more storage devices, responsive to the listener detecting the response message on the response queue, to retrieve, by the message queuing application, the response message from the response queue for the message queuing application; and program instructions, stored on at least one of the one or more storage devices, to process, by the message queuing application, the response message.
The computer program product where a message queue application accesses a specific API service and where the generic API request isn't a direct call to any API accessible via the bridge service further contains instructions: to create a request message with a generic API request (based on API definitions provided by the API bridge service); to place the request message in the request queue via the message queue API; to open a listener on the response queue; to retrieve the response message (upon detection by the listener); and to process the response message.
19. A method for a message queuing application accessing a specific application programming interface (API) service, comprising: building, by a message queuing application, a request for a specific API service from among a plurality of API services in a generic API message request validated using API request definitions available to the message queuing application and available to an API bridge service, wherein the generic API message request comprises an API service request in a message queue format, wherein the generic API message request of the request message comprises a structured data message specified by the API request definitions for the API bridge service, wherein the API request definitions specify a message format independent of a protocol specified for any articular API call for the plurality of API services, wherein the structured data message comprises a structured data message format comprising an extensible markup (XML) format; placing by the message queuing application, the generic API message request on a request message queue of a message queuing network configured to provide a generic API interface for accessing the plurality of API services; listening, by an API bridge service of the generic API interface, to the message queue; responsive to the API bridge service detecting the generic API message request in the message queue, retrieving, by the API bridge service, the generic API message request from the message queue, formatting the generic API message request from the API service request in the message queue format into a call to a specific API from among the plurality of API services, calling the specific API, formatting a result returned by the specific API from the particular format protocols specified for the specific API into a generic API response message validated using API response definitions available to the message queuing application and available to the API bridge service, wherein the generic API response comprises an API server response in a message queue format, and placing the generic API response message in a response message queue of the message queuing network of the generic API interface; retrieving, by the message queuing application, the generic API response message from the response message queue; and processing the generic API response message, wherein the processed response message provides the message queuing application with the specific API service.
A method describes a queuing application's interaction with APIs using a message queue. The queuing application creates a generic API request for a specific API service. This request is validated against API request definitions shared with an API bridge service, is formatted for the message queue, and independent of the specific API's protocol. The request can be structured as XML and then placed on the message queue. The API bridge service listens to the message queue, retrieves requests, and reformats them into specific API calls. The bridge service calls the API, then converts the API's response into a generic response message, validated using API response definitions shared with the message queuing application, and places it on a response queue. The queuing application retrieves and processes the generic response.
Unknown
December 9, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.