Abstract: Methods and apparatus, including computer program products, are provided for handling database table changes. The method may include receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: Methods and apparatus, including computer program products, are provided for handling database table changes. The method may include receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems for allowing provisioning of open data protocol (OData) services on top of a generic interaction layer (GenIL). One computer-implemented method includes receiving an OData-compliant request for data, determining a GenIL data provider to receive the OData-compliant request for data, determining the memory location of the data, requesting the data from the determined memory location, receiving the requested data from the determined memory location, converting, using at least one computer, the received data into an OData-compliant format, rendering an OData-compliant response, and transmitting the OData-compliant response.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems for allowing provisioning of open data protocol (OData) services on top of a generic interaction layer (GenIL). One computer-implemented method includes receiving an OData-compliant request for data, determining a GenIL data provider to receive the OData-compliant request for data, determining the memory location of the data, requesting the data from the determined memory location, receiving the requested data from the determined memory location, converting, using at least one computer, the received data into an OData-compliant format, rendering an OData-compliant response, and transmitting the OData-compliant response.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems for allowing provisioning of open data protocol (OData) services on top of a generic interaction layer (GenIL). One computer-implemented method includes receiving an OData-compliant request for data, determining a GenIL data provider to receive the OData-compliant request for data, determining the memory location of the data, requesting the data from the determined memory location, receiving the requested data from the determined memory location, converting, using at least one computer, the received data into an OData-compliant format, rendering an OData-compliant response, and transmitting the OData-compliant response.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems for allowing provisioning of open data protocol (OData) services on top of a generic interaction layer (GenIL). One computer-implemented method includes receiving an OData-compliant request for data, determining a GenIL data provider to receive the OData-compliant request for data, determining the memory location of the data, requesting the data from the determined memory location, receiving the requested data from the determined memory location, converting, using at least one computer, the received data into an OData-compliant format, rendering an OData-compliant response, and transmitting the OData-compliant response.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems for allowing provisioning of open data protocol (OData) services on top of a generic interaction layer (GenIL). One computer-implemented method includes receiving an OData-compliant request for data, determining a GenIL data provider to receive the OData-compliant request for data, determining the memory location of the data, requesting the data from the determined memory location, receiving the requested data from the determined memory location, converting, using at least one computer, the received data into an OData-compliant format, rendering an OData-compliant response, and transmitting the OData-compliant response.

Abstract: A method includes: providing a composition engine as a service configured to receive requests from multiple service consumers using any of multiple service consumer protocols; receiving a first request in the composition engine as a service conforming to a service consumer protocol from a service consumer operated by a customer; generating a second request to each of one or more provider systems, the second request conforming to a provider system protocol, the composition engine as a service configured to generate requests conforming to any of multiple provider system protocols; receiving, by the composition engine as a service, information from the provider system, and adapting the received information to conform to the service consumer protocol; and exposing, by the composition engine as a service, a web service that makes the adapted information available to the service consumer.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems for allowing provisioning of open data protocol (OData) services on top of a generic interaction layer (GenIL). One computer-implemented method includes receiving an OData-compliant request for data, determining a GenIL data provider to receive the OData-compliant request for data, determining the memory location of the data, requesting the data from the determined memory location, receiving the requested data from the determined memory location, converting, using at least one computer, the received data into an OData-compliant format, rendering an OData-compliant response, and transmitting the OData-compliant response.

Abstract: Methods and apparatus, including computer program products, for selecting client adapters. A client abstraction layer identifies one or more selection data elements in a client request and selects an adapter to communicate with the client based on the selection data elements, wherein each selection data element specifies an adapter type, a client type, or data describing the client. The adapter can be selected based on a multi-stage selection process that involves performing an adapter-request process for selecting an adapter based on the selection data elements that specify the adapter type; if the adapter-request process fails to select an adapter, performing a client-identification process for selecting an adapter based on the selection data elements that specify the client type; and if the client-identification process fails to select an adapter, performing a client-description process for selecting an adapter based on the selection data elements that specify data describing the client.

Abstract: A method includes, in a network, representing a first request from a first user as a first ClientUser, assigning the first ClientUser to a ServerSession, the ServerSession having one or more ClientSessions, each of the ClientSessions allowing a server to have a single session for all first user requests from the server. The method includes, in a client/server network, providing a session that can be common to all connections to a web server by a user.

Abstract: Methods and apparatus, including computer program products, for selecting client adapters. A client abstraction layer identifies one or more selection data elements in a client request and selects an adapter to communicate with the client based on the selection data elements, wherein each selection data element specifies an adapter type, a client type, or data describing the client. The adapter can be selected based on a multi-stage selection process that involves performing an adapter-request process for selecting an adapter based on the selection data elements that specify the adapter type; if the adapter-request process fails to select an adapter, performing a client-identification process for selecting an adapter based on the selection data elements that specify the client type; and if the client-identification process fails to select an adapter, performing a client-description process for selecting an adapter based on the selection data elements that specify data describing the client.

Abstract: A method includes, in a network, representing a first request from a first user as a first ClientUser, assigning the first ClientUser to a ServerSession, the ServerSession having one or more ClientSessions, each of the ClientSessions allowing a server to have a single session for all first user requests from the server. The method includes, in a client/server network, providing a session that can be common to all connections to a web server by a user.